OASIS Open Document Format for Office Applications (OpenDocument) TC

 View Only
  • 1.  References to ADC SC work on requirements for change tracking for Patrick

    Posted 02-06-2012 16:31
    Patrick, Following up the TC conference call today, this may be useful to you in drawing up a list of change tracking requirements (some links may be internal not public, the system makes it difficult to get public links though all are public). We did start off looking at requirements [1][2] and compared the two approaches based on these[3]. As we got further into our discussions, it was clear that there were requirements issues at a higher level that had not been addressed/agreed/specified, and these were pulled out in the 'consensus' report [4][5]. 1. Charter of the ADC SC http://www.oasis-open.org/apps/org/workgroup/office-collab/description.php 2. Initial conference call to discuss requirements http://www.oasis-open.org/apps/org/workgroup/office-collab/email/archives/201012/msg00013.html 3. SC wiki on requirements http://wiki.oasis-open.org/office/Change%20Tracking%20Requirements There are also a number of use cases there which give requirements at a more detailed level (related specifically to ODF 1.2), but this is less relevant to you I believe, though worth looking at for background: http://wiki.oasis-open.org/office/ChangeTrackingUseCases 4. ODF Change Tracking: Analysis and Proposals Version 1.0 As submitted to TC: http://www.oasis-open.org/apps/org/workgroup/office-collab/download.php/44676/odf-ct-v1.0-wd04.odt In particular, see the Conclusions which ask a number of questions about requirements. See also the WD05 version of this report with Svante's updates which introduce more on requirements for collaboration. 5. Thorsten makes some specific comments on requirements section of above report in his email: http://www.oasis-open.org/apps/org/workgroup/office-collab/email/archives/201201/msg00027.html Similarly, some issues that Andreas raises may be useful to you: http://lists.oasis-open.org/archives/office-collab/201201/msg00024.html Enjoy! Robin -- -- ----------------------------------------------------------------- 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


  • 2.  References to ADC SC work on change tracking for Select Committee

    Posted 04-18-2012 14:17
    I thought this list of reference material may be useful for those considering being on the Select Committee. The message copied below is a useful starting point for requirements. Item 4 is the 'consensus report' which was not approved by the TC but it is a document that has had most discussion and refinement by the subcommittee as a whole and as at version WD04 (as submitted to TC) the ECT and GCT authors were happy that it was a reasonable reflection of those approaches - as noted, version WD05 has additions from Svante (for MCT) which we have not discussed in the subcommittee. Additions: 6. Since the email, Svante has added documents on MCT: Presentation of Merge-enabled Change Tracking (MCT)   http://www.oasis-open.org/committees/document.php?document_id=45161&wg_abbrev=office-collab Example use cases solved with MCT    http://www.oasis-open.org/committees/document.php?document_id=45463&wg_abbrev=office-collab 7. GCT Proposal (Generic Change Tracking) Generic CT Proposal Presentation    http://www.oasis-open.org/committees/document.php?document_id=41725&wg_abbrev=office-collab Proposal for generic representation of tracked changes for ODF   http://www.oasis-open.org/committees/document.php?document_id=43517&wg_abbrev=office-collab 8. ECT Proposal (Extended Change Tracking) Extended CT Proposal Presentation    http://www.oasis-open.org/committees/document.php?document_id=41812&wg_abbrev=office-collab Proposal for extending existing ODF change tracking   http://www.oasis-open.org/committees/document.php?document_id=41699&wg_abbrev=office-collab Proposal for extending existing ODF change tracking - Supplement 1   http://www.oasis-open.org/committees/document.php?document_id=41816&wg_abbrev=office-collab Essential reading includes 4,6,7,8. There is of course a lot of other material and documents, http://www.oasis-open.org/apps/org/workgroup/office-collab/documents.php and these include over 60 worked examples (all implemented for GCT, 10 or so for ECT and see 6 above for those in MCT). It is a fair bit or reading matter but this is a complex and important issue. Robin References to ADC SC work on requirements for change tracking for Patrick On 06/02/2012 16:31, Robin LaFontaine wrote: Patrick, Following up the TC conference call today, this may be useful to you in drawing up a list of change tracking requirements (some links may be internal not public, the system makes it difficult to get public links though all are public). We did start off looking at requirements [1][2] and compared the two approaches based on these[3]. As we got further into our discussions, it was clear that there were requirements issues at a higher level that had not been addressed/agreed/specified, and these were pulled out in the 'consensus' report [4][5]. 1. Charter of the ADC SC http://www.oasis-open.org/apps/org/workgroup/office-collab/description.php 2. Initial conference call to discuss requirements http://www.oasis-open.org/apps/org/workgroup/office-collab/email/archives/201012/msg00013.html 3. SC wiki on requirements http://wiki.oasis-open.org/office/Change%20Tracking%20Requirements There are also a number of use cases there which give requirements at a more detailed level (related specifically to ODF 1.2), but this is less relevant to you I believe, though worth looking at for background: http://wiki.oasis-open.org/office/ChangeTrackingUseCases 4. ODF Change Tracking: Analysis and Proposals Version 1.0 As submitted to TC: http://www.oasis-open.org/apps/org/workgroup/office-collab/download.php/44676/odf-ct-v1.0-wd04.odt In particular, see the Conclusions which ask a number of questions about requirements. See also the WD05 version of this report with Svante's updates which introduce more on requirements for collaboration. Submitted to TC: http://www.oasis-open.org/committees/document.php?document_id=44677&wg_abbrev=office 5. Thorsten makes some specific comments on requirements section of above report in his email: http://www.oasis-open.org/apps/org/workgroup/office-collab/email/archives/201201/msg00027.html Similarly, some issues that Andreas raises may be useful to you: http://lists.oasis-open.org/archives/office-collab/201201/msg00024.html Enjoy! Robin -- -- ----------------------------------------------------------------- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: office-unsubscribe@lists.oasis-open.org For additional commands, e-mail: office-help@lists.oasis-open.org -- -- ----------------------------------------------------------------- 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


  • 3.  Re: [office] References to ADC SC work on change tracking for Select Committee

    Posted 04-23-2012 13:40
    Robin, Thanks! I was just about to assemble a reading list for myself but you have saved me the trouble! And you are right, it is a complex issue. But all the interesting issues are complex ones. ;-) Hope you are having a great week! Patrick On 04/18/2012 10:17 AM, Robin LaFontaine wrote: I thought this list of reference material may be useful for those considering being on the Select Committee. The message copied below is a useful starting point for requirements. Item 4 is the 'consensus report' which was not approved by the TC but it is a document that has had most discussion and refinement by the subcommittee as a whole and as at version WD04 (as submitted to TC) the ECT and GCT authors were happy that it was a reasonable reflection of those approaches - as noted, version WD05 has additions from Svante (for MCT) which we have not discussed in the subcommittee. Additions: 6. Since the email, Svante has added documents on MCT: Presentation of Merge-enabled Change Tracking (MCT)   http://www.oasis-open.org/committees/document.php?document_id=45161&wg_abbrev=office-collab Example use cases solved with MCT    http://www.oasis-open.org/committees/document.php?document_id=45463&wg_abbrev=office-collab 7. GCT Proposal (Generic Change Tracking) Generic CT Proposal Presentation    http://www.oasis-open.org/committees/document.php?document_id=41725&wg_abbrev=office-collab Proposal for generic representation of tracked changes for ODF   http://www.oasis-open.org/committees/document.php?document_id=43517&wg_abbrev=office-collab 8. ECT Proposal (Extended Change Tracking) Extended CT Proposal Presentation    http://www.oasis-open.org/committees/document.php?document_id=41812&wg_abbrev=office-collab Proposal for extending existing ODF change tracking   http://www.oasis-open.org/committees/document.php?document_id=41699&wg_abbrev=office-collab Proposal for extending existing ODF change tracking - Supplement 1   http://www.oasis-open.org/committees/document.php?document_id=41816&wg_abbrev=office-collab Essential reading includes 4,6,7,8. There is of course a lot of other material and documents, http://www.oasis-open.org/apps/org/workgroup/office-collab/documents.php and these include over 60 worked examples (all implemented for GCT, 10 or so for ECT and see 6 above for those in MCT). It is a fair bit or reading matter but this is a complex and important issue. Robin References to ADC SC work on requirements for change tracking for Patrick On 06/02/2012 16:31, Robin LaFontaine wrote: Patrick, Following up the TC conference call today, this may be useful to you in drawing up a list of change tracking requirements (some links may be internal not public, the system makes it difficult to get public links though all are public). We did start off looking at requirements [1][2] and compared the two approaches based on these[3]. As we got further into our discussions, it was clear that there were requirements issues at a higher level that had not been addressed/agreed/specified, and these were pulled out in the 'consensus' report [4][5]. 1. Charter of the ADC SC http://www.oasis-open.org/apps/org/workgroup/office-collab/description.php 2. Initial conference call to discuss requirements http://www.oasis-open.org/apps/org/workgroup/office-collab/email/archives/201012/msg00013.html 3. SC wiki on requirements http://wiki.oasis-open.org/office/Change%20Tracking%20Requirements There are also a number of use cases there which give requirements at a more detailed level (related specifically to ODF 1.2), but this is less relevant to you I believe, though worth looking at for background: http://wiki.oasis-open.org/office/ChangeTrackingUseCases 4. ODF Change Tracking: Analysis and Proposals Version 1.0 As submitted to TC: http://www.oasis-open.org/apps/org/workgroup/office-collab/download.php/44676/odf-ct-v1.0-wd04.odt In particular, see the Conclusions which ask a number of questions about requirements. See also the WD05 version of this report with Svante's updates which introduce more on requirements for collaboration. Submitted to TC: http://www.oasis-open.org/committees/document.php?document_id=44677&wg_abbrev=office 5. Thorsten makes some specific comments on requirements section of above report in his email: http://www.oasis-open.org/apps/org/workgroup/office-collab/email/archives/201201/msg00027.html Similarly, some issues that Andreas raises may be useful to you: http://lists.oasis-open.org/archives/office-collab/201201/msg00024.html Enjoy! Robin -- -- ----------------------------------------------------------------- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: office-unsubscribe@lists.oasis-open.org For additional commands, e-mail: office-help@lists.oasis-open.org -- -- ----------------------------------------------------------------- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: office-unsubscribe@lists.oasis-open.org For additional commands, e-mail: office-help@lists.oasis-open.org -- Patrick Durusau patrick@durusau.net Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) OASIS Technical Advisory Board (TAB) - member Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau


  • 4.  RE: [office] References to ADC SC work on requirements for change tracking for Patrick

    Posted 04-20-2012 18:15
    One thing I’m not finding in any of this material is any user data. Other than the one or two public comments on the 1.2 drafts, have any of the implementers seen or shared any feedback from customers on: 1.       How much CT is being used in ODF? 2.       What features users are requesting? 3.       Any current features users are having difficulty using? 4.       Anything related to customer comments (not comments from developers or other associates within the community, but actual customers)?   Creating yet another SC to make a decision seems a bit over the top to me. If the current SC is unable to make a recommendation, then they should lay the issues out to the TC, which should be able to then take a vote. But having actual usage and user data should be part of the info included. Otherwise we’re guessing about what is needed for a standard to support products and trying to be smart on behalf of those users, which almost never works in software.   Chérie Ekholm Senior Standards Professional Microsoft Office Standards & Interoperability Phone: 425-706-1425 Fax: 425-936-7329 Redmond, WA   From: office@lists.oasis-open.org [mailto:office@lists.oasis-open.org] On Behalf Of Robin LaFontaine Sent: Monday, February 06, 2012 8:31 AM To: Patrick Durusau Cc: office@lists.oasis-open.org Subject: [office] References to ADC SC work on requirements for change tracking for Patrick   Patrick, Following up the TC conference call today, this may be useful to you in drawing up a list of change tracking requirements (some links may be internal not public, the system makes it difficult to get public links though all are public). We did start off looking at requirements [1][2] and compared the two approaches based on these[3]. As we got further into our discussions, it was clear that there were requirements issues at a higher level that had not been addressed/agreed/specified, and these were pulled out in the 'consensus' report [4][5]. 1. Charter of the ADC SC http://www.oasis-open.org/apps/org/workgroup/office-collab/description.php 2. Initial conference call to discuss requirements http://www.oasis-open.org/apps/org/workgroup/office-collab/email/archives/201012/msg00013.html 3. SC wiki on requirements http://wiki.oasis-open.org/office/Change%20Tracking%20Requirements There are also a number of use cases there which give requirements at a more detailed level (related specifically to ODF 1.2), but this is less relevant to you I believe, though worth looking at for background: http://wiki.oasis-open.org/office/ChangeTrackingUseCases 4. ODF Change Tracking: Analysis and Proposals Version 1.0 As submitted to TC: http://www.oasis-open.org/apps/org/workgroup/office-collab/download.php/44676/odf-ct-v1.0-wd04.odt In particular, see the Conclusions which ask a number of questions about requirements. See also the WD05 version of this report with Svante's updates which introduce more on requirements for collaboration. 5. Thorsten makes some specific comments on requirements section of above report in his email: http://www.oasis-open.org/apps/org/workgroup/office-collab/email/archives/201201/msg00027.html Similarly, some issues that Andreas raises may be useful to you: http://lists.oasis-open.org/archives/office-collab/201201/msg00024.html Enjoy! Robin -- -- ----------------------------------------------------------------- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: office-unsubscribe@lists.oasis-open.org For additional commands, e-mail: office-help@lists.oasis-open.org


  • 5.  Re: [office] References to ADC SC work on requirements for change tracking for Patrick

    Posted 04-23-2012 13:37
    Cherie, Good point on user data. Can you provide a summary on the use of MS change tracking features by customers? Thinking for interchange purposes the closer change tracking is the same the better. Thanks! Hope you are at the start of a great week! Patrick On 04/20/2012 02:15 PM, Cherie Ekholm wrote: One thing I’m not finding in any of this material is any user data. Other than the one or two public comments on the 1.2 drafts, have any of the implementers seen or shared any feedback from customers on: 1.       How much CT is being used in ODF? 2.       What features users are requesting? 3.       Any current features users are having difficulty using? 4.       Anything related to customer comments (not comments from developers or other associates within the community, but actual customers)?   Creating yet another SC to make a decision seems a bit over the top to me. If the current SC is unable to make a recommendation, then they should lay the issues out to the TC, which should be able to then take a vote. But having actual usage and user data should be part of the info included. Otherwise we’re guessing about what is needed for a standard to support products and trying to be smart on behalf of those users, which almost never works in software.   Chérie Ekholm Senior Standards Professional Microsoft Office Standards & Interoperability Phone: 425-706-1425 Fax: 425-936-7329 Redmond, WA   From: office@lists.oasis-open.org [ mailto:office@lists.oasis-open.org ] On Behalf Of Robin LaFontaine Sent: Monday, February 06, 2012 8:31 AM To: Patrick Durusau Cc: office@lists.oasis-open.org Subject: [office] References to ADC SC work on requirements for change tracking for Patrick   Patrick, Following up the TC conference call today, this may be useful to you in drawing up a list of change tracking requirements (some links may be internal not public, the system makes it difficult to get public links though all are public). We did start off looking at requirements [1][2] and compared the two approaches based on these[3]. As we got further into our discussions, it was clear that there were requirements issues at a higher level that had not been addressed/agreed/specified, and these were pulled out in the 'consensus' report [4][5]. 1. Charter of the ADC SC http://www.oasis-open.org/apps/org/workgroup/office-collab/description.php 2. Initial conference call to discuss requirements http://www.oasis-open.org/apps/org/workgroup/office-collab/email/archives/201012/msg00013.html 3. SC wiki on requirements http://wiki.oasis-open.org/office/Change%20Tracking%20Requirements There are also a number of use cases there which give requirements at a more detailed level (related specifically to ODF 1.2), but this is less relevant to you I believe, though worth looking at for background: http://wiki.oasis-open.org/office/ChangeTrackingUseCases 4. ODF Change Tracking: Analysis and Proposals Version 1.0 As submitted to TC: http://www.oasis-open.org/apps/org/workgroup/office-collab/download.php/44676/odf-ct-v1.0-wd04.odt In particular, see the Conclusions which ask a number of questions about requirements. See also the WD05 version of this report with Svante's updates which introduce more on requirements for collaboration. 5. Thorsten makes some specific comments on requirements section of above report in his email: http://www.oasis-open.org/apps/org/workgroup/office-collab/email/archives/201201/msg00027.html Similarly, some issues that Andreas raises may be useful to you: http://lists.oasis-open.org/archives/office-collab/201201/msg00024.html Enjoy! Robin -- -- ----------------------------------------------------------------- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: office-unsubscribe@lists.oasis-open.org For additional commands, e-mail: office-help@lists.oasis-open.org -- Patrick Durusau patrick@durusau.net Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) OASIS Technical Advisory Board (TAB) - member Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau