Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] Accurate line and column numbers for elements and attributes in Java

From: "Michael Kay" <mike@--------.--->
To: "'Klotz, Leigh'" <Leigh.Klotz@-----.--->,"'John Snelson'" <john.snelson@------.--->
Date: 6/6/2008 7:35:00 PM
> For the record, with saxon9 I'm able to use the 
> AugmentedSource and obtain line numbers for attributes 
> retrieved from XPath expressions, just not column numbers as 
> they're not in the NodeInfo API. 

In 9.1 Saxon will retain column numbers as well; though I fear that this
will lead to false expectations. Certainly for reporting errors in schema
and stylesheet documents, it would be really nice to have accurate line and
column information for every attribute.

I don't really accept the arguments about attribute value normalization. I
think the real reason parsers (and APIs) don't provide more information is
an obsession with performance, not realizing that for many applications,
parser performance is not the #1 objective.

Michael Kay
http://www.saxonica.com/


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