• From: Michael Brennan <Michael_Brennan@a...>
• To: 'David Brownell' <david-b@p...>, sax-devel@l...,xml-dev@l...
• Date: Tue, 07 Aug 2001 16:24:26 -0700

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.
> 

• Follow-Ups:
  • Re: [Sax-devel] RE: SAX-ext proposal #4: feature/property discovery
    • From: David Brownell <david-b@p...>

• Prev by Date: jdom vs. xerces
• Next by Date: RE: SAX-core #2: factories
• Previous by thread: SAX-ext proposal #4: feature/property discovery
• Next by thread: Re: [Sax-devel] RE: SAX-ext proposal #4: feature/property discovery
• Index(es):
  • Date
  • Thread