OpenDocument - Adv Document Collab SC

Our next meeting will be on the 30th of July: http://www.timeanddate.com/worldclock/meetingdetails.html?year=2014&month=07&day=30&hour=14&min=30&sec=0&p1=179&p2=37&p3=136&p4=234&iv=1800 The teleconference login data for next call will be found in the OASIS calendar event: Phone numbers are listed in the calendar invite:   https://www.oasis-open.org/apps/org/workgroup/office/calendar.php Chat room for meeting is at:   http://webconf.soaphub.org/conf/room/odf Please find the IRC log of today's meeting below: Attendees: Oliver-Rainer, Patrick, Peter Rakyta, John Haug, Svante [16:26]  Oliver-Rainer Wittmann: hi Peter [16:29]  Peter Rakyta: Hi Oliver [16:42]  Svante Schubert: https://lists.oasis-open.org/archives/office-comment/201407/msg00003.html https://lists.oasis-open.org/archives/office-comment/201406/msg00003.html A notable missing feature of ODF (in comparison with OOXML) https://lists.oasis-open.org/archives/office-comment/201407/msg00001.html [16:43]  Svante Schubert: Before we start the abstract of the paper: [16:43]  Svante Schubert: ABSTRACT This work-in-progress report shows how the run-time complexity of handling file change can be reduced dramatically by defining the changes beforehand at design time. Related change scenarios such as versioning, change-tracking, undo/redo, real-time collaboration and file merge are getting easy to handle, when the changes of the file format are being defined. The following paper shows the principle design steps and change behavior run-time on the example of an office file format, the OpenDocument format (ODF), which is currently under ongoing specification by the subcomittee of the OASIS ODF standardization committee. [16:48]  Svante Schubert: At position 1 we add an A [16:48]  Svante Schubert: At position 2 we add an B [16:48]  Svante Schubert: At position 3 we add an C [16:49]  Svante Schubert: the same document can to be achieved by [16:49]  Svante Schubert: At position 1 we add an C [16:49]  Svante Schubert: At position 1 we add an B [16:49]  Svante Schubert: At position 1 we add an A [16:49]  Svante Schubert: Bot have the same result [16:49]  Svante Schubert: Bot have the same result [16:49]  Svante Schubert: two lists of operations that are equal [16:49]  Svante Schubert: and can be transformed to each other by using OT (operational transformation) [16:50]  Oliver-Rainer Wittmann: equivalent instead of equal. right? [16:50]  Svante Schubert: yes [16:51]  Svante Schubert: https://lists.oasis-open.org/archives/office-comment/201407/msg00003.html [16:59]  Svante Schubert: Oliver: Explained the issue [16:59]  Svante Schubert: Oliver: Will create a new issue and state what he had explained [17:00]  Svante Schubert: Oliver: Will ask Dennis for further feed-back on the second part [17:01]  Svante Schubert: https://lists.oasis-open.org/archives/office-comment/201406/msg00003.html [17:05]  Svante Schubert: https://issues.oasis-open.org/browse/OFFICE-3373 [17:06]  Svante Schubert: I will take this over. [17:06]  Svante Schubert: Submit a new issue. [17:06]  Svante Schubert: And do a wording proprosal. [17:07]  Svante Schubert: Last one: [17:07]  Svante Schubert: A notable missing feature of ODF (in comparison with OOXML) https://lists.oasis-open.org/archives/office-comment/201407/msg00001.html [17:10]  Svante Schubert: .. 0,125. So far so good. Now I want the extra 3rd digit only to be displayed when actually used [17:10]  Svante Schubert: ^^ [17:11]  Svante Schubert: A missing display option of number in ODF [17:11]  Svante Schubert: I would say, out-of-our change-tracking scope [17:13]  Oliver-Rainer Wittmann: just for the record - next meeting I will not attend due to my vacation [17:14]  Svante Schubert: I will ask Rob to dial in for us [17:14]  Svante Schubert: thanks and good-bye! Best regards, Svante

The following issue I would like to discuss with you on our next call: Am 19.07.2014 um 00:03 schrieb Svante Schubert: [17:01]  Svante Schubert: https://lists.oasis-open.org/archives/office-comment/201406/msg00003.html [17:05]  Svante Schubert: https://issues.oasis-open.org/browse/OFFICE-3373 I have looked into this issue. Allow me to summarize: In Section 5.5.2 on <text:changed-region> the last paragraph says    A <text:changed-region> can be referenced by more than one    change, but the corresponding referencing change mark elements    shall be of the same change type - insertion, format change or    deletion. see http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#element-text_changed-region The problem is that there is not such thing as change type . The idea was to say that those who are referencing to the same ID, should of course also represent the same change. To me it seems redundant and therefore I would suggest to remove the underspecified part: Because in XML multiple IDREF may refer to the same ID and it is obvious that they will refer to the same information. Therefore no additional info is given only confusion added. PS: With change types the following elements have been referred to: <define name= text-changed-region-content >     <choice>         <element name= text:insertion >             <ref name= office-change-info />         </element>         <element name= text:deletion >             <ref name= office-change-info />             <zeroOrMore>                 <ref name= text-content />             </zeroOrMore>         </element>         <element name= text:format-change >             <ref name= office-change-info />         </element>     </choice> </define> Best regards, Svante