Re: [office-collab] Generic CT proposal - an implementer's look atit

[Frank Meies <frank.meies@oracle.com>]

Hi Thorsten

On 01.04.2011 03:37, Thorsten Behrens wrote:

Here's the crux: because the proposal relies solely on generic
modifications of the xml info set (both structurally, by changing
the tree, and by modifying attributes), and all those operations are
considered valid (section 3, items 6 and 7 of the
generic-ct-proposal), the set of semantically distinct editing
operations *is unbounded*.

Which is a fundamental problem, for all applications that need to
map the change tracking markup into their internal,
optimized-for-editing document models - because what you have here,
is a limited set of editing operations, that are closely related to
concrete user actions ("insert" an object, "delete" an object,
"merge" two objects - with a very application-specific meaning, that
may not map 1:1 to the xml representation).

I'm not sure if I got you correctly. You consider it problematic that there might be change transactions in the document that do not match basic user actions. So you are basically referring to a) the ability of grouping arbitrary changes because this most like does not match any basic user action and b) the ability to add/delete/change attributes of an element, right? Because all the other cases seem to represent concrete office productivity user actions.

Regards,

Frank

--

Frank Meies | Software Developer
Phone: +49 49 23646 500
Oracle OFFICE GBU

ORACLE Deutschland B.V. & Co. KG | Nagelsweg 55 | 20097 Hamburg

ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603

Komplementärin: ORACLE Deutschland Verwaltung B.V.
Rijnzathe 6, 3454PV De Meern, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Jürgen Kunz, Marcel van de Molen, Alexander van der Ven

Oracle is committed to developing practices and products that help protect the environment