W3C home > Mailing lists > Public > public-change@w3.org > February 2013

Re: Few words on each of us

From: Lech Rzedzicki <lech@kode1100.com>
Date: Thu, 21 Feb 2013 13:51:00 +0100
Message-ID: <CAAETgD21a=cKvi5JUD+73G15g65YBCiUXidCy93Ez7Rx6m5B4Q@mail.gmail.com>
To: "public-change@w3.org" <public-change@w3.org>
Hi everyone.

My name is Lech Rzedzicki. I am an independent consultant working via
my own Kode1100 Ltd, but I have joined the group on behalf of my
clients: Pearson Education, Penguin Books and Dorling Kindersley.
Just like Mohamed I try to stay active in communities around XML
(attending XML Prague) and ebooks (contributing to IDPF EPUB standard)
My clients are all publishers and store the content of the books in
various forms of XML and they need change tracking functionality.
The two main problem areas are I think already identified by this working group:
1. Interoperability of change tracking markup between various tools and editors.
2. Being able to reflect more complex change tracking scenarios:
moving text, merging adjacent changes and being able to show the
editorial changes accurately down to a single character.

In addition to that my main concern is the ability to use such change
tracking markup easily in a browser editor.
I have found that processing instructions are not a good way to work
with if you're using browser's DOM, therefore I think the best
approach is element based change tracking, on the other hand, I'd like
to keep said markup the least verbose as it means downloading less
data over HTTP. I dislike how using element based CT markup pollutes
the XML tree and this can lead to code that is more complex. For my
prototype uses I have developed a PI based markup compatible with
Oxygen CT markup and simple XSL to transform that to element based
markup - so that it is easy to process the markup in a browser. If
anyone is interested I can post the code and XML samples somewhere.
Perhaps the only thing worth thinking of in this context is whether we
want to specify two kinds of equivalent syntax for CT markup: PI and
element based, much like RelaxNG allows for XML and compact syntax.

I am really looking forward to see how this group develops, but given
that we have some contributors that have really a huge amount of
experience in this specific area - I'm looking at you DeltaXML ;) I
dare say that the CT markup I have seen at XML Prague this year is
pretty mature and well thought out and I would like to push towards
releasing usable specs that can be adopted by the tool vendors as soon
as possible.

Best regards,

Lech Rzedzicki
XML Architect
Kode1100.com

On Thu, Feb 21, 2013 at 1:06 PM, Innovimax SARL <innovimax@gmail.com> wrote:
> Dear all,
>
> I'm Mohamed Zergaoui and involved in many dimension around Markup since more
> than 10 years (member of many W3C Working Group and also at ISO) also
> co-organiser of few XML events (XML Prague, SVG Open, XQuery Meetup, etc.)
>
> I will do my best as chair of this community group
>
> I'm neither involved in a product doing Change Tracking nor Diff, but as an
> curious user I've always been interested in those two area
>
> Hence I will try to be the most objective as possible.
>
> Regards,
>
> Mohamed
>
>
>
>
>
> On Thu, Feb 21, 2013 at 1:01 PM, Innovimax SARL <innovimax@gmail.com> wrote:
>>
>> Dear all,
>>
>> Welcome to the Change Tracking Community Group
>>
>> I would like each of us to say few words on themselves (I would like to
>> put a short summary on the wiki for future newcomers)
>>
>> Thanks
>>
>> Mohamed
>> --
>> 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 
>
>
>
>
> --
> 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 
Received on Friday, 22 February 2013 17:40:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 February 2013 17:40:08 GMT