[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Namespaces, W3C XML Schema (was Re: ANN: SAX Filters forNamespacePro

• From: Leigh Dodds <ldodds@i...>
• To: Aaron Skonnard <aarons@d...>, Xml-Dev <xml-dev@l...>
• Date: Wed, 01 Aug 2001 10:22:09 +0100

> -----Original Message-----
> From: Aaron Skonnard [mailto:aarons@d...]
> Sent: 01 August 2001 05:21
> To: Xml-Dev
> Subject: Namespaces, W3C XML Schema (was Re: ANN: SAX Filters for
> NamespaceProcessing)
[...]

> As an example, consider the version attribute in XSLT. When used on a
> literal result element, it must be qualified. But when used on the
> xsl:transform element, it must be unqualified, depending completely on
> context.

Actually I believe its version on stylesheet and transform, and xsl:version
on the 'Literal Result Element as Stylesheet' form [1].

RDF has the same usage (or ambiguity). rdf attributes on non rdf elements
are prefixed, otherwise they aren't. This means that RDF applications have
to deal with both forms. The RDF Core WG decided recently that they were
going
to enforce prefixed attributes everywhere.

So the inconsistencies continue...

On reflection I think I'd prefer it if XSLT followed suit...

[1]. http://www.w3.org/TR/xslt#result-element-stylesheet

Cheers,

L.

• References:
  • RE: Namespaces, W3C XML Schema (was Re: ANN: SAX Filters forNamespaceProcessing)
    • From: Aaron Skonnard <aarons@d...>

• Prev by Date: Re: Namespaces,
• Next by Date: RE: ANN: SAX Filters for Namespace Processing
• Previous by thread: RE: Namespaces, W3C XML Schema (was Re: ANN: SAX Filters forNamespaceProcessing)
• Next by thread: RE: Namespaces, W3C XML Schema (was Re: ANN: SAX Filters forNamespaceProcessing)
• Index(es):
  • Date
  • Thread