RE: [xml-dev] "Introducing MicroXML, Part 1: Explore the basicprinciples

["Rushforth, Peter" <Peter.Rushforth@NRCan-RNCan.gc.ca>]

James,

I think that's a great idea!  Count me in.

Peter

P.S. Nice to see you here again :-)
________________________________________
From: James Clark [jjc@jclark.com]
Sent: July 15, 2012 12:45 AM
To: John Cowan
Cc: xml-dev@lists.xml.org
Subject: Re: [xml-dev] "Introducing MicroXML, Part 1: Explore the basic principles of ...

I wonder whether it might be worth starting a W3C Community Group to
hash out these sort of issues and try to produce a spec that has some
degree of consensus.

James

On Sun, Jul 15, 2012 at 11:24 AM, James Clark <jjc@jclark.com> wrote:
> On Fri, Jul 13, 2012 at 10:38 PM, John Cowan <cowan@mercury.ccil.org> wrote:
>
>> I ... compromised:
>>
>> 1) PIs are in the syntax, but not in the data model.  In MicroLark,
>> if you want them, you have to use the pull or the push parser, because
>> the tree parser ignores them.  There's even a switch to turn them into
>> fatal errors, if you decide you really don't want to deal with them.
>>
>> 2) Syntactically they have to look like start-tags except for the
>> <? and ?>.  That was pragmatic: there are a lot of widely used PIs that
>> already look like that, and it made parsing them trivial.  They are
>> reported with the pseudo-attributes already nicely parsed.
>
> This is the one part of your current editor's draft that I strongly
> disagree with.
>
> Your draft says:
>
> "PIs are not part of the MicroXML data model, but processors SHOULD
> make them available to the application."
>
> But surely the data model should be the canonical way that processors
> make information the available to the application.
>
> If MicroXML users can't rely on getting PI information out from
> processors, then they can't rely on PIs to encode significant
> information, which makes PIs of little use.
>
> But if you put arbitrary PIs in the data model, you are, of course,
> significantly complicating things (going from 2 kinds of content to
> 3).
>
> The start-tag syntax restriction also means you can't encode arbitrary
> XML infosets.
>
>> I think you need support for the xml-stylesheet PI if you are going to
>> support MicroXML on the Web other than MicroXML + HTML5.
>
> I find that a much more compelling use case.
>
> The compromise I suggest is this:
>
> - allow PIs only before the root element (and perhaps only before the
> DOCTYPE if there is one), probably with the start-tag syntax
> restriction
>
> - put them in the data model, so your formal data model represents
> documents by a <pi-list, element> pair (I would similarly describe an
> element as a <name, attributes, content> triple), where the pi-list is
> a list of elements
>
> In terms of the JSON encoding, I would suggest the following:
>
> - encode elements differently: an element is represented by a JSON
> object, with each attribute represented as a property of the object;
> the element name and content would be represented by properties whose
> name starts with "$", so  that are not legal XML names but are legal
> JavaScript identifiers eg $name/$content or something shorter.
>
> - encode PIs before the root element as a "$" prefixed property of the
> root element eg $pi
>
> - consider adding DOCTYPE to the data model as well using similar
> techniques (not sure about this, but it's going to be difficult for
> serializers to know whether to output a DOCTYPE otherwise)
>
> I think this gives an encoding which is quite natural and makes it
> easy to ignore PIs.
>
> James

_______________________________________________________________________

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@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php