[Home] [By Thread] [By Date] [Recent Entries]

  • From: "Liam R. E. Quin" <liam@w...>
  • To: Michael Kay <mike@s...>
  • Date: Sat, 02 May 2015 00:55:19 -0400

On Sat, 2015-05-02 at 00:20 +0100, Michael Kay wrote:
> > 

> 
> We've made choices in the way we model XML for processing, for 
> example we provide a parent axis so when you are at a node, you can 
> find its parent. That's convenient for many kinds of processing, but 
> it makes it very hard for two XML trees to share a subtree, which 
> makes it expensive to make small modifications to a large tree. 


I've used two or three XML (and SGML) editors that didn't work that 
way exactly, in order to support entities that remain in place on 
export -- with the contents of each entity being shared across 
multiple entity references. Serna was one such editor.

The XDM isn't the only possible data model for XML, of course.

> I don't think there's anything in the BNF of XML or JSON that made 
> those different design choices inevitable.

Agreed.

Liam

> 
> Michael Kay
> Saxonica
> _______________________________________________________________________
> 
> 
> 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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member