Altova Mailing List Archives


RE: [xml-dev] Lesson Learned: Use namespaces for both markup anddata

From: "Michael Kay" <mike@--------.--->
To: "'Elliotte Rusty Harold'" <elharo@-------.--->, "'Paul Spencer'"
Date: 1/3/2010 12:34:00 AM
> I am 95% certain that the 
> pain caused by allowing prefix declarations only on the root 
> element would be far less than the pain caused by allowing 
> redeclarations of prefixes.

That would mean an XSLT processor would have to build the result tree in
memory rather than serializing it on the fly. The cost of that for people
transforming large documents is quite significant.

(But the question is academic. If we were changing this rule, we would want
to change lots of other rules at the same time.)

Regards,

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


_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@l...
subscribe: xml-dev-subscribe@l...
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

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.