OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Namespaces in XML and schemas

[ Lists Home | Date Index | Thread Index ]


This could be a stupid question, but I will chance it anyway because I have 
a hard time finding a clear answer...

"Namespaces in XML" states:

We envision applications of Extensible Markup Language (XML) where a single 
XML document may contain elements and attributes (here referred to as a 
"markup vocabulary") that are defined for and used by multiple software 
modules. One motivation for this is modularity; if such a markup vocabulary 
exists which is well-understood and for which there is useful software 
available, it is better to re-use this markup rather than re-invent it.
Such documents, containing multiple markup vocabularies, pose problems of 
recognition and collision. Software modules need to be able to recognize 
the tags and attributes which they are designed to process, even in the 
face of "collisions" occurring when markup intended for some other software 
package uses the same element type or attribute name.

Hence, in accordance with the specification of namespaces, the following 
document (a stylesheet fragment) is said to be valid (I am not sure if 
"valid" applies here, in fact.):

<xsl:stylesheet version="1.1"

<xsl:strip-space elements="doc chapter section"/>

<xsl:template match="doc">
        <xsl:value-of select="title"/>

Now, this is swell and all but an assumed schema for XHTML would not allow 
the "xsl:value-of" element as part of the content of the "title" element.

Therefore, my questions are:

1) Are stylesheets supposed to be valid documents?
2) How can one consider the possibility of multischema documents, granted 
that 2 schemas can conflict with each other?

Finally, I am asking these questions because I would like to define the 
schema of a minimal language that I would use to create document templates. 
Among other things, this minimal language would involve elements that are 
not allowed as part of the content of certain XHTML (for instance) 
elements, but that must exists as such to provided the desired templating 

Thank you for your attention.




News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS