AW: Processing instructions

That sound very reasonable.
I still think that PIs can be a huge paint point and since microXML is supposed to be like a very efficient, or lighter version of XML (right?) we could still drop or restrict them without having a bad conscience :)


. . . . . . . . . . . . . . . . . . . . . . . . . .
Developer Patrick Szabo
 Developer 
LexisNexis
A-1030 Wien, Marxergasse 25

mailto:patrick.szabo@lexisnexis.at
Tel.: +43 1 53452 1573 
Fax: +43 1 534 52 146 


-----Ursprüngliche Nachricht-----

Von: George Cristian Bina [mailto:george@oxygenxml.com] 
Gesendet: Donnerstag, 26. Juli 2012 12:01
An: Dave Pawson
Cc: MicroXML
Betreff: Re: Processing instructions

Because the schema may not provide them. PIs will work with any document 
and the default processing will just ignore them, the result being 
equivalent with processing the document without ant change tracking 
information.
Even if the schema will provide support for change tracking and 
annotations each schema may have its own way of storing that thus you 
will need a different solution for each schema.
At the DITA conference in North America there was a discussion to try to 
unify these change tracking/annotation PIs to be product independent 
because right now most of the tools provide similar PIs but with 
different names.

Best Regards,
George
--
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

On 7/26/12 12:51 PM, Dave Pawson wrote:
> On 26 July 2012 10:43, George Cristian Bina <george@oxygenxml.com> wrote:
>> FWIW we use PIs in oXygen for the following cases:
>>
>> top level PIs:
>> - associate a CSS or XSLT stylesheet with an XML document (xml-stylesheet)
>> - associate a schema with an XML document (xml-model)
>>
>> in content PIs:
>> - store track change information (oXygen specific PIs)
>> - store annotation information, user comments on a specific part of the
>> document (oXygen specific PIs)
>>
>> The later are useful when editing the document visually (rendered though
>> CSS) and are just a serialization format of the change tracking and
>> annotation information, marking the positions of inserted/deleted content of
>> of the annotated region. This information can be serialized also in a top
>> level PI but then it may get easily out of synch if the document is modified
>> by other applications, while the in content PIs are more robust.
>> Using PIs for change tracking and annotations allows implementing a single
>> solution independent of the actual XML format and does not require that
>> format to define specific elements for change tracking and annotation.
>>
>> Best Regards,
>> George
>
> Is there any reason you could not use elements and attributes for
> these purposes George?
>
> regards
>
>

Received on Thursday, 26 July 2012 10:16:00 UTC