Cart
[Home] [By Thread] [By Date] [Recent Entries]
Maybe the xml:json means the newXML parser can do evaluations immediately rather than relying on an XSLT/XPath processor downstream? Plus it can use the xml:json to turn the data into objects which include structure found in the values of attributes? ---- Stephen D Green On 10 December 2010 10:20, David Carlisle <davidc@n...> wrote: > On 10/12/2010 10:10, Stephen Green wrote: >> >> The xml:json would not need a schema to distinguish an unordered list or >> array >> from a sequenced one so the parser would know whether to treat the order >> as >> significant without having to load and understand a schema or be >> programmed >> with being able to read different kinds of schema language, etc. That >> seems to >> me a crucial difference and there may be others. > > yes but that doesn't answer the question as to why it would be useful to do > that in a general XML context, as in my xpath example, why would it be > useful to know it's a sequence of integers if you don't know everything else > you needed to know about evaluating xpath (or json) and if you do know how > to evaluate xpath it's not too hard to know that it is contained in > particular attributes. > > (x)html doesn't need a schema to tell it that what is in a script element is > javascript/json > > David > > ________________________________________________________________________ > The Numerical Algorithms Group Ltd is a company registered in England > and Wales with company number 1249803. The registered office is: > Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom. > > This e-mail has been scanned for all viruses by Star. The service is > powered by MessageLabs. > ________________________________________________________________________ >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
