[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: Rick Jelliffe <ricko@a...>
• To: Xml-Dev <xml-dev@l...>
• Date: Mon, 20 Aug 2001 13:59:29 +1000

 From: "Ronald Bourret" <rpbourret@r...>
 
> I think the real culprit here isn't whether local element type names are
> qualified or not. It's that local element types exist at all. In the XML

Yes, it perhaps was a failure in architecture. In the vacuum at W3C (which 
hopefully now the TAG group will rectify, unless the horse has already bolted) 
there should have been clear policy made that local element names need not
be supported.  

Certainly I think developers should steer clear of local names: even if they 
are using a path-aware schema language such as Schematron which can 
cope with all kinds of contextual variation, the name of an element should 
describe its genus in some clear namespace. 

Otherwise we need PSVI (i.e. explicit context-based typing) or path-based 
processing (implicit context-based typing).  

Cheers
Rick Jelliffe 

• References:
  • RE: Namespaces, W3C XML Schema (was Re: ANN: SAX Filters for NamespaceProcessing)
    • From: "Fuchs, Matthew" <matthew.fuchs@c...>
  • Re: Namespaces, W3C XML Schema (was Re: ANN: SAX Filters forNamespaceProcessing)
    • From: Ronald Bourret <rpbourret@r...>

• Prev by Date: Re: XML.COM: How I Learned to Love daBomb
• Next by Date: Re: XML.COM: How I Learned to Love daBomb
• 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 for NamespaceProcessing)
• Index(es):
  • Date
  • Thread