- From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
- Date: 08 Feb 2000 13:49:39 +0000
- To: "Roger L. Costello" <costello@mitre.org>
- Cc: xml-dev@xml.org, www-xml-schema-comments@w3c.org, "Schneider,John C." <jcs@mitre.org>, "Cokus,Michael S." <msc@mitre.org>
"Roger L. Costello" <costello@mitre.org> writes:
> Hi Folks,
>
> In the XML Schema spec all the examples use a default namespace for the
> XML Schema vocabulary. For example,
>
> <schema xmlns="http://www.w3.org/1999/XMLSchema" ...>
> <element name="BookCatalogue">
> ...
> </element>
> ...
> </schema>
>
> This example uses the XML Schema namespace as the default namespace.
> This meams, of course, that an XML Schema parser would then know that
> all non-qualified elements are from the XML Schema namespace. Thus, it
> would recognize "element" as a member of the XML Schema namespace.
>
> The XML Namespace document states (section 5.2 [1]) that attributes are
> not part of a default namespace, "Note that default namespaces do not
> apply directly to attributes." So, the "name" attribute above is not
> part of the XML Schema namespace. Matter of fact, "name" is in no
> namespace. I believe that it is an error for "name" to not be part of
> the XML Schema namespace. Right? We want an XML Schema parser to
> recognize "name" as being part of the XML Schema namespace. Right?
But "name" is scoped to its containing element, whether that uses
explicit (prefixed) or implicit (default) qualification. It's already
just like XSLT, where you see in the examples, e.g.
<xsl:template match='xyzzy'>...</xsl:template>
No qualification on 'match'.
ht
--
Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
W3C Fellow 1999--2001, part-time member of W3C Team
2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
Received on Tuesday, 8 February 2000 08:49:56 UTC