OpenDocument - Adv Document Collab SC

Hi all, while trying to get familiar with the extended-change-tracking-proposal I created a document giving a brief overview of how some of the use cases are handled by the two proposals. If you find this useful, we can upload the file and anyone who feels to do so can add more use cases. Best 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 ct_proposal_comparison.odt

Thanks, Frank ?? this is a handy start for a side-by-side.
 
I think there is one correction to note, though.  Row 4 indicates the ??extended ? proposal has no construct to support ??delete an element but not its content ?. 
Or, in a document-centric context, removing a style from a piece of text.  That can be directly extrapolated from the patterns established by the
Add a New Style examples, which demonstrate more complex cases.
 
Example document content:
Remove bold
à Remove bold
Starting markup:
< text:p > Remove

   < text:span
text:style-name = " BoldStyle " > bold </ text:span >
</ text:p >
Ending markup:
< text:p > Remove
bold </ text:p >
Change-tracked markup:
< text:tracked-changes >
   < text:changed-region
text:id = " 1 " >
       < text:format-change >
          < office:change-info >
?¦ </ office:change-info >
          < text:span
text:style-name = " BoldStyle " >
       </ text:format-change >
   </ text:changed-region >
</ text:tracked-changes >
< text:p > Remove
   < ct:format-change-start
ct:id = " 1 " /> bold
   < ct:format-change-end
ct:id = " 1 " />
</ text:p >
Thanks,
John
 


From: Frank Meies [mailto:frank.meies@oracle.com]

Sent: Friday, March 25, 2011 6:13 AM
To: office-collab@lists.oasis-open.org
Subject: [office-collab] Comparison generic-ct-proposal and extended-ct-proposal


 
Hi all,

while trying to get familiar with the extended-change-tracking-proposal I created a document giving a brief overview of how some of the use cases are handled by the two proposals. If you find this useful, we can upload the file and anyone who feels to do so
can add more use cases.

Best 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

Hi John, thank you for your input, I'll change the document accordingly, see attachment. The most common use case for delete an element but not its content is removing a styled span, so you are right, this can be expressed using text:format-change. Another use case for remove-leaving-content is removing a text:section without removing its content. Do we want to handle this as a text:format-change as well? Regards, Frank On 29.03.2011 01:40, John Haug wrote: 91C4760493E4094B9871E5A496374DA2320ED993@DF-M14-02.exchange.corp.microsoft.com type= cite > Thanks, Frank €“ this is a handy start for a side-by-side.   I think there is one correction to note, though.   Row 4 indicates the €œextended € proposal has no construct to support €œdelete an element but not its content €.   Or, in a document-centric context, removing a style from a piece of text.   That can be directly extrapolated from the patterns established by the Add a New Style examples, which demonstrate more complex cases.   Example document content: Remove bold à Remove bold Starting markup: < text:p > Remove     < text:span text:style-name = BoldStyle > bold </ text:span > </ text:p > Ending markup: < text:p > Remove bold </ text:p > Change-tracked markup: < text:tracked-changes >     < text:changed-region text:id = 1 >             < text:format-change >                   < office:change-info > €¦ </ office:change-info >                   < text:span text:style-name = BoldStyle >             </ text:format-change >     </ text:changed-region > </ text:tracked-changes > < text:p > Remove     < ct:format-change-start ct:id = 1 /> bold     < ct:format-change-end ct:id = 1 /> </ text:p > Thanks, John   From: Frank Meies [ mailto:frank.meies@oracle.com ] Sent: Friday, March 25, 2011 6:13 AM To: office-collab@lists.oasis-open.org Subject: [office-collab] Comparison generic-ct-proposal and extended-ct-proposal   Hi all, while trying to get familiar with the extended-change-tracking-proposal I created a document giving a brief overview of how some of the use cases are handled by the two proposals. If you find this useful, we can upload the file and anyone who feels to do so can add more use cases. Best 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 -- 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 ct_proposal_comparison.odt

I think there are complications around ODF <text:section> that may not make it amenable to simple trackable changes, and it is definitely more serious than a style change, because it may be an insertion point for content derived elsewhere. When there are manipulations of <text:section> elements by users, the question becomes which one(s) is/are being edited when there is section linking involved. Also, to remove a derived <text:section> it may in effect be a replacement of the <text:section> by whatever the source provides, but breaking the connection. (Note: the source need not be in the content.xml part or it can be conveniently placed there but marked as not shown.) Removing a source <text:section> leads to questions about what happens to the ones that are derived from it by linking, etc. So there are edits of a <text:section> with derived content that are more like editing a field. There's other editing that may really be of the source (and how does that reflect in the derived copy?) and so on. (Side note: replications of section content can't be identical because of constraints on xml:id and, along with that, prospects for current/extended change marks existing in the source of the replication when the source is obtained by linking to another <text:section>.) See ODF 1.2 CS01 Part 1 section 5.4. Also, see the schema. Note that the content that is present is a possibly-empty run of text-content elements. In places where the <text:section> appears as text-content, it might be possible to just drop the <text:section> tags. This doesn't work for all places where <text:section> is allowed, depending on what the text-content run is within the <text:section>. Also, some <text:section> occurrences (such as in header-footer-content) are not as text-content. There are probably more variations to deal with than the ones I found in a cursory inspection of the schema (and recollection of my struggling to understand <text:section> in the work on ODF 1.2). Handling of nested <test:section> elements is left as an exercise for the student. - Dennis
Original Message----- From: Frank Meies [ mailto:frank.meies@oracle.com ] Sent: Tuesday, March 29, 2011 00:17 To: office-collab@lists.oasis-open.org Subject: Re: [office-collab] Comparison generic-ct-proposal and extended-ct-proposal Hi John, thank you for your input, I'll change the document accordingly, see attachment. The most common use case for "delete an element but not its content" is removing a styled span, so you are right, this can be expressed using text:format-change. Another use case for remove-leaving-content is removing a text:section without removing its content. Do we want to handle this as a text:format-change as well? [ ... ]

John, Please would you update the wiki page for Use Cases to indicate for each Use Case whether or not this is covered in your proposal or not? I suggest if a Use Case is covered (i.e. included in your proposal document) but not demonstrated (i.e. worked example available), you indicate 'To do'. If it is not covered by your proposal mark as 'Out of scope', or other comment that may be appropriate. From the email discussions it appears that a category 'In scope but not yet defined' might be appropriate. I am requesting this as SC Chair in order that the members have the best possible information on which to base a decision. It is important that all members understand the scope of the extended-ct-proposal. It would he helpful to have this information as soon as possible, so if you can complete it this week (by 3rd April) that would be good. Thanks, Robin -- -- ----------------------------------------------------------------- Robin La Fontaine, Director, DeltaXML Ltd Change control for XML 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