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

Re: SAX Infoset Mapping

• To: John Cowan <cowan@c...>
• Subject: Re: SAX Infoset Mapping
• From: Mike Fitzgerald <mikefz@w...>
• Date: Wed, 05 May 2004 08:34:38 -0600
• Cc: xml-dev@l...
• In-reply-to: <20040505142116.GF8572@c...>
• References: <4098DC9E.3030406@e...> <4098E75B.50704@w...> <20040505142116.GF8572@c...>
• User-agent: Mozilla Thunderbird 0.5 (Windows/20040207)

In the appendix, David walks through all the information items and suggests what callbacks 
can be used to return properties. For example, for attribute info items, he suggests using 
Attribute.getURI() to obtain the [namespace name] property, Attributes.getLocalName() to 
get [local name], and Attributes.getQName() to get [prefix], and so on. He also points out 
where SAX cannot help you with the infoset. What I meant by an implementation is an 
implementation of all the calls the David suggests in his appendix.

Mike

John Cowan wrote:

> Mike Fitzgerald scripsit:
> 
>>In Appendix B of the book SAX2 [1], David Brownell describes a mapping of 
>>SAX to the infoset, but I am unaware of an implementation of this mapping.
> 
> 
> SAX parsers are themselves an implementation of the mapping between SAX
> and the Infoset; that's (one of) the whole points of the Infoset, that
> it's independent of APIs.
> 
> That said, I haven't read the appendix in question.
> 

• References:
  • SAX Infoset Mapping
    • From: Robin Berjon <robin.berjon@e...>
  • Re: SAX Infoset Mapping
    • From: Mike Fitzgerald <mikefz@w...>

• Prev by Date: Re: Models and containers
• Next by Date: RE: You call that a standard?
• Previous by thread: Re: SAX Infoset Mapping
• Next by thread: Re: SAX Infoset Mapping
• Index(es):
  • Date
  • Thread