Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] Should we include the XML prolog in the XPath datamodel, or DOM

From: COUTHURES Alain <alain.couthures@---------.--->
To: Mukul Gandhi <gandhi.mukul@-----.--->
Date: 9/20/2008 1:48:00 PM
Hello,



From my point of view, the prolog is just useful for parsing :


  version="1.0" : just in case another version would exist in the
future (multiple roots, multiple relationships,...)
  encoding="..." : so the parser can interpret correctly and
convert the following characters !

  

DOM is just concerned by the document in memory where just one encoding
is used (UTF-32 for example).



XPath expressions are written as strings which could use a different
encoding...



The result tree of DOM API calls or of XSL transformations is usually
saved or transfered : another encoding is necessary so the prolog has
to be written when serializing.



Alain COUTHURES

<agenceXML>

http://www.agencexml.com

Bordeaux, France



Mukul Gandhi a &eacute;crit :
7870f82e0809200524j372de030o9346bf7789124ec4@m..."
 type="cite">
  Hi all,
   I wrote the following blog post. This is perhaps a weird thought,
for people having worked with XML for long.

http://mukulgandhi.blogspot.com/2008/09/should-we-include-version10-in-xpath.html

This is a short description of the points I have in mind.

Could you please let us know, if my logic have any merit.


transparent
Print
Mail
Like It
Disclaimer
.

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.

.
.

transparent

transparent