• From: "Michael Kay" <mike@s...>
• To: "'Mukul Gandhi'" <gandhi.mukul@g...>,"'bryan rasmussen'" <rasmussen.bryan@g...>
• Date: Mon, 22 Sep 2008 17:29:25 +0100

> As I wrote earlier, XML prolog information could be 
> properties of the document node in XPath (2.x). It's upto the 
> applications to make use of this information.

Why would you want to tell the application about the encoding of the
document entity, without also revealing the encoding of every other entity?

How could you supply information about entities without including entities
in the data model? If you included them in the model, how would they relate
to the other objects in the model?

It's wrong to make these things properties of the document node when they
are actually properties of an entity. I'm not saying it would be wrong to
provide information about entities in the model, but it would add a lot of
extra complexity for a questionable return.

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

• Follow-Ups:
  • Re: Should we include the XML prolog in the XPath data model, or DOM
    • From: richard@i... (Richard Tobin)

• References:
  • Should we include the XML prolog in the XPath data model, or DOM
    • From: "Mukul Gandhi" <gandhi.mukul@g...>
  • Re: Should we include the XML prolog in the XPath datamodel, or DOM
    • From: Philippe Poulard <philippe.poulard@s...>
  • Re: Should we include the XML prolog in the XPath data model, or DOM
    • From: "Mukul Gandhi" <gandhi.mukul@g...>
  • Re: Should we include the XML prolog in the XPath data model, or DOM
    • From: "bryan rasmussen" <rasmussen.bryan@g...>
  • Re: Should we include the XML prolog in the XPath data model, or DOM
    • From: "Mukul Gandhi" <gandhi.mukul@g...>