 |
 |
 |
--- Elliotte Harold <elharo@m...> wrote:
> Tatu Saloranta wrote:
>
...
> > for comments was more optional), and at least
> > regarding parsers, they must be passed to handling
> > app/tool.
>
> XML doesn't really define a processing model. This
> is arguably a flaw in
> the spec. What must be passed is pretty haphazard.
Quite... but I thought that following (XML 1.0 specs,
2.6) was quite clear on this:
"PIs are not part of the document's character data,
but MUST be passed through to the application."
And this is quite different from what is said about,
say, comments:
"They are not part of the document's character data;
an XML processor MAY, but need not, make it possible
for an application to retrieve the text of comments."
Now, I do understand that just saying something should
(or MUST) be provided does not prescribe exact
mechanism... but a general-purpose API to an xml
processing tool that lacks such facility does seem
against the spirit of the specs, no?
> For instance, XML
> processors must provide default attribute values
> when no specified
> attribute is present. However there's no rule that
> says they have to
> provide specified attribute values.
:-)
-+ Tatu +-
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |