Altova Mailing List Archives


Re: [xml-dev] Quiz: how many namespaces are in scope?

From: Hermann Stamm-Wilbrandt <STAMMW@--.---.--->
To: xml-dev@-----.---.---
Date: 8/30/2010 7:54:00 PM
> Lesson Learned: Implicit on the root element of every XML document is
this namespace declaration:

>       <root xmlns:xml="http://www.w3.org/XML/1998/namespace">


1) Not sure about "Implicit on the root element" (xpath++ from [1]):
$ xpath++ "count(//namespace::*)" nlist.xml
21
$ xpath++ "count(/namespace::*)" nlist.xml
0
$ xpath++ "count(//*)" nlist.xml
7
$ xpath++ "count(/|//*)" nlist.xml
8
$ xpath++ "count(/*/namespace::*)" nlist.xml
3
$


2) The implicit xml namespace declaration was the reason for
" and name()!='xml' " in this XML serialization ([2]).

    <xsl:for-each select="namespace::*">
      <xsl:if test="not(.=../../namespace::*) and name()!='xml'">
        <xsl:value-of select= "concat(' xmlns',
                                       substring(':',1 div boolean(name
())),
                                       name(),'=&quot;',.,'&quot;')" />
      </xsl:if>
    </xsl:for-each>



[1]
https://www.ibm.com/developerworks/forums/thread.jspa?messageID=14455521&#14511477
[2]
http://www.biglist.com/lists/lists.mulberrytech.com/xsl-list/archives/201008/msg00186.html

Mit besten Gruessen / Best wishes,

Hermann Stamm-Wilbrandt
Developer, XML Compiler, L3
WebSphere DataPower SOA Appliances
----------------------------------------------------------------------
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschaeftsfuehrung: Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294




From:       "Costello, Roger L." <costello@m...>
To:         "xml-dev@l..." <xml-dev@l...>
Date:       08/30/2010 08:00 PM
Subject:    [xml-dev] Quiz: how many namespaces are in scope?



Hi Folks,

Consider this XML document:

<?xml version="1.0"?>
<N1:NumberList xmlns:N1="http://www.example1.org"
               xmlns:N2=" http://www.example2.org ">
        <Number>23</Number>
        <Number>41</Number>
        <Number>70</Number>
        <Number>103</Number>
        <Number>99</Number>
        <Number>6</Number>
</N1:NumberList>

For the first child element:

        <Number>23</Number>

what namespaces are in scope?

I created an XSLT template to output the <Number> element's in-scope
namespaces:

-------------------------------------------
<xsl:template match="*">
       <xsl:for-each select="namespace::*">
           <xsl:value-of select="."/></p>
       </xsl:for-each>
</xsl:template>
-------------------------------------------

Here is the output:

      http://www.w3.org/XML/1998/namespace

      http://www.example1.org

      http://www.example2.org

There are three (3) in-scope namespaces.

Lesson Learned: Implicit on the root element of every XML document is this
namespace declaration:

      <root xmlns:xml="http://www.w3.org/XML/1998/namespace">

NOTE: it is illegal to explicitly declare the xml namespace. The xml
namespace is built into every XML application.

Since the xml namespace is implicitly declared in every XML document, you
can immediately use the xml:lang attribute and the xml:space attribute,
e.g.,

<movie>
             <title>The Laughing Cow</title>
             <title xml:lang="fr">La Vache Qui Rit</title>
</movie>

Here is an XSLT template to output the in-scope namespaces and their
prefixes:

-------------------------------------------
<xsl:template match="*">
        <xsl:for-each select="namespace::*">
            Namespace in scope = <xsl:value-of select="."/>
            Namespace prefix = <xsl:value-of select="name(.)"/>
        </xsl:for-each>
</xsl:template>
-------------------------------------------

Here is the output:

      Namespace in scope = http://www.w3.org/XML/1998/namespace
      Namespace prefix = xml

      Namespace in scope = http://www.example1.org
      Namespace prefix = N1

      Namespace in scope = http://www.example2.org
      Namespace prefix = N2

QUESTIONS

1. Have I correctly analyzed the situation (regarding in-scope namespaces)?

2. What else would you add?

/Roger

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php




_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.