|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: SAX-ext proposal #4: feature/property discovery
How about just simple "hasFeature" and "hasProperty" methods? Or perhaps "supportsFeature" and "supportsProperty". That way code seeking support for a particular feature or property can just ask the parser regarding the specific feature/property rather than doing a linear search through a list for the feature/property in question. Either way, though, I think this would be a good addition. > -----Original Message----- > From: David Brownell [mailto:david-b@p...] > Sent: Tuesday, August 07, 2001 10:05 AM > To: sax-devel@l...; xml-dev@l... > Subject: SAX-ext proposal #4: feature/property discovery > > > Feature/Property discovery > > - There's no way to find out what features a given XMLReader > recognizes. > > Given an XMLReader, it's basically possible to find out what values > it supports (modulo when-to-set sequencing constraints) since they > can only be true or false (and might be read-only). > > - Similarly with properties, though there's no way to determine the > range of values. > > PROPOSAL: > > - Define a new standard property ID: > > http://xml.org/sax/properties/supported-features > Read-only > > Returns an array of Strings for all the features > supported by this XMLReader. > > - Define a new standard property ID: > > http://xml.org/sax/properties/supported-properties > Read-only > > Returns an array of Strings for all the properties > supported by this XMLReader. >
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||

Cart








