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

Re: SAX2 and XSLT processors

• From: David Megginson <david@m...>
• To: "XSL list" <xsl-list@m...>, "XML List" <xml-dev@i...>
• Date: Thu, 20 May 1999 06:31:13 -0400 (EDT)

Oren Ben-Kiki writes:

 > I perfectly agree that the same problem exists for all relevant W3C
 > recommendations. IMVHO, it is wrong to specify such features using
 > http://my.own.company/... URIs. It would be very much in the spirit
 > of SAX to specify them under http://xml.org/... instead.

The trouble is that we've created a centralized registry bottleneck --
a single person has to approve every new feature and property name to
avoid name collision.  

Except for a few core SAX2 features and properties (and there may
already be too many), I think that there are great advantages to
letting the market decide what to use, and then (slowly) migrating
feature names into the core if there's great enough demand.


All the best,


David

-- 
David Megginson                 david@m...
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • Re: SAX2 and XSLT processors
    • From: "Oren Ben-Kiki" <oren@c...>

• Prev by Date: Re: Overloaded URIs (was Re: XLink: behavior must go!)
• Next by Date: RE: SAX2 RFD: Inheritance vs. Modification vs. Amalgamation
• Previous by thread: Re: SAX2 and XSLT processors
• Next by thread: Re: SAX2 and XSLT processors
• Index(es):
  • Date
  • Thread