Hi Jan, Jan Hackel <[EMAIL PROTECTED]> wrote on 07/25/2005 02:48:04 AM:
> Hi Michael, > > thanks for the help. > > > For Xerces, references property fixup is a no-op. As far as I know, > > neither SAX or DOM have native support for this property, though the DOM > > specification [2] describes how it can be computed. I'm curious about how > > you were expecting to access this information. > > Actually I did not think much about how the reference property fixupcould be > done by the parser. Though I did not expect it to be a trivial task > implementing such a "higher order" feature, as it requires access to the > schema and manipulation of the whole document tree. I was quite blinded by my > hopes: Reference fixup would be a *great* help for unitizing large documents, > especially those produced in a collaborative but loosly coupled manner. > > From your statement I conclude that reference property fixup is a inherently > hard to implement feature for any current XML-parser? Is there actually a > parser that has the capability to do it? I think the lack of API support for the [references] property is the issue. I don't know of any APIs which support it. What value is there in fixing up references if there's nowhere to report them? An application interested in the value of the [references] property is able to compute it from the information available in SAX (though only once the entire document has been read) and DOM. Since this would be computed on the result of XInclude, the values would be the same as the result of references property fixup. > Regards > Jan Hackel > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Thanks. Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
