> Data Model: request for simplification > > We would like to simplify the definition of the typed value > as follows. > > The typed value of a document should raise an error. > The typed value of a element with complex type with > mixed content should raise an error. > The typed error on a namespace node should raise an error. > The typed value of a processing instruction should raise an > error. The typed value of comment should raise an error. > > I do not see the rationale for supporting the cases above. > They do not > bring > any additional expressive power. Changing any of the four rules above would break most XSLT 1.0 stylesheets. Michael Kay > > The typed value only makes sense for attributes, for elements > with simple content or complex type with simple content and > for text nodes. > > In general, as a design philosophy, it is preferable to add this kind > of limitations > in V1. We can always convert an error into a real value in the next > versions, > but not a wrong kind of value into another value or error later on. >Received on Monday, 16 February 2004 05:36:03 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:14:05 GMT