Re: PIs for change tracking: was Re: Few words on each of us

Claudius and Robin,

Please feel free to complete my list on the wiki if needed

http://www.w3.org/community/change/wiki/State_of_the_art

Attempts in the past to define a Change Tracking
Markup[edit<http://www.w3.org/community/change/wiki/index.php?title=State_of_the_art&action=edit&section=4>
]All information Inside the
document[edit<http://www.w3.org/community/change/wiki/index.php?title=State_of_the_art&action=edit&section=5>
]PI oriented

   - PTC :
   http://www.arbortext.com/namespace/atict/change-tracking-markup-spec.html

[edit<http://www.w3.org/community/change/wiki/index.php?title=State_of_the_art&action=edit&section=6>
]Element oriented

   - HTML : INS/DEL http://www.w3.org/TR/html401/struct/text.html#h-9.4
   - PTC :
   http://www.arbortext.com/namespace/atict/change-tracking-markup-spec.html
   - DeltaXML :
   http://lists.w3.org/Archives/Public/public-change/2013Feb/0019.html

[edit<http://www.w3.org/community/change/wiki/index.php?title=State_of_the_art&action=edit&section=7>
]Partial information inside the
document[edit<http://www.w3.org/community/change/wiki/index.php?title=State_of_the_art&action=edit&section=8>
]Information outside
(Database)[edit<http://www.w3.org/community/change/wiki/index.php?title=State_of_the_art&action=edit&section=9>
]

Mohamed


On Fri, Feb 22, 2013 at 12:47 PM, Claudius Teodorescu <
claudius.teodorescu@gmail.com> wrote:

> Hi,
>
> Also, one can also choose a 'gradual change tracking markup', namely a
> sort of light syntax (maybe with PIs) for common purposes, and a heavy
> syntax (maybe with elements/attributs) for much elaborated situations.
>
> One surely needs to consider all the existing knowledge, as you briefly
> presented it.
>
> Claudius
>
>
> On Fri, Feb 22, 2013 at 1:07 PM, Robin LaFontaine <
> robin.lafontaine@deltaxml.com> wrote:
>
>>  I changed the title so easier to follow this thread - an important
>> topic.
>>
>> There is a lot of experience and code around using PIs in editing
>> applications and IMHO a PI representation for CT (Change Tracking) is
>> necessary. My hope is that we can have the best of both worlds if we can
>> define a bi-directional and loss-less transformation between an element/attribute
>> CT representation and a PI one.
>>
>> Robin
>>  On 22/02/2013 07:51, Daniel Glazman wrote:
>>
>> On 21/02/13 22:56, Casey Jordan wrote:
>>
>> We use PI's as well, as Tom said there are many benefits. However we
>> only use the PI's to markup the regions and assign a small amount of
>> metadata (username, unique id etc), any comments or other information
>> associated with the change are stored outside the document in a
>> database. This way, if the change get's removed, accepted, or rejected,
>> the information surrounding it lives on in an audit record. This has
>> been very important for our customers.
>>
>>
>> That's _really_ interesting because the HTML zealots never consider
>> PIs as a potential solution to our real-life problems in editing
>> environments ou publishing chains, they always base all their solutions
>> on elements and attributes only, and that of course tweaks the structure
>> of the document.
>>
>> </Daniel>
>>
>>
>> --
>> -- -----------------------------------------------------------------
>> Robin La Fontaine, Director, DeltaXML Ltd  "Experts in information change"
>> T: +44 1684 592 144  E: robin.lafontaine@deltaxml.com      http://www.deltaxml.com
>> Registered in England 02528681 Reg. Office: Monsell House, WR8 0QN, UK
>>
>>
>


-- 
Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
http://www.innovimax.fr
RCS Paris 488.018.631
SARL au capital de 10.000 €