You are viewing a plain text version of this content. The canonical link for it is here.
Posted to qa@openoffice.apache.org by "Dennis E. Hamilton" <de...@acm.org> on 2015/06/05 02:01:49 UTC

FW: DChanges 2014 Papers and ODF Conformance/Compliance Assurance

In the activities referenced in this note, the contribution of a coherent QA process is critical.  It is important for the formulation of tests, for the application of assessment procedures, and for the addition of tests found necessary as the result of incident reports and other cases found not covered by an evolving suite of tests.

 - Dennis 

-----Original Message-----
From: Dennis E. Hamilton [mailto:dennis.hamilton@acm.org] 
Sent: Thursday, June 4, 2015 16:24
To: dev@openoffice.apache.org
Subject: DChanges 2014 Papers and ODF Conformance/Compliance Assurance

I took advantage of Corinthia as a place to build up materials on ODF Conformance/Compliance Assurance testing of software products, since creating profiles of feature compliance figures in the scope of the Apache Corinthia (incubating) project.

The material is relevant, of course, to Apache OpenOffice and other implementations of ODF.

The proposed structure for development of files, procedures, and assessments is at <https://cwiki.apache.org/confluence/display/Corinthia/ODF>.

I have updated the ODF Conformance/Compliance Assurance Helix sketch there.  The connected treatment of ODF 1.2 Conformance that has been linked from that sketch has also been updated.  That overview is at <http://nfoworks.org/notes/2014/06/n140602.htm> and a trial diagram of the different conformance layers is at <http://nfoworks.org/notes/2014/06/n140602b.htm>.

I am starting to put more effort into this material, including coming up with minimal test cases as baby steps.

My papers from DChanges 2014 are also relevant to this effort.  Although the "Anti-Pattern" paper is about repairing change-tracking, a key conclusion is that one can't achieve an envelope within which interoperable interchange of changed-tracked documents is possible without have a surrounding envelope in which there is reliable interchange without any change tracking.  The "Anti-Pattern" paper provides a sketch of how one can establish that, and some principles that must be honored.  

I have not put authors versions of my DChanges 2014 papers on-line yet.  I will do so in the coming week.

 - Dennis

-----Original Message-----
From: Dennis E. Hamilton [mailto:dennis.hamilton@acm.org] 
Sent: Tuesday, May 12, 2015 10:50
To: dev@corinthia.incubator.apache.org
Subject: DChanges 2014 Papers Available

The final versions of papers on change-tracking from DChanges2014 have been published.  You can see the table of contents of the proceedings at <http://dl.acm.org/citation.cfm?id=2723147> by selecting to see the "Table of Contents."

[ ... ]


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org


Re: FW: DChanges 2014 Papers and ODF Conformance/Compliance Assurance

Posted by Pedro Lino <pe...@gmail.com>.
Good morning Dennis

I have no idea how I received this email since it did not arrive to the QA
mailing list (and I'm subscribed in no-mail mode).

However I'm glad it did because Open Document compatibility and round trip
problems (between Open Source and proprietary) are an issue that I'm daily
confronted with.

Just yesterday I submitted a bug that seems to have always been present in
LibreOffice (and possible OpenOffice.org and Apache OpenOffice) where there
is loss of track changes information if the document received is in DOC
format. I haven't tested yet what happens with an ODT (because I don't have
MS Office 2013 and going back to ODT1.1 doesn't make much sense)

https://bugs.documentfoundation.org/show_bug.cgi?id=91862

Kind regards,
Pedro


On Fri, Jun 5, 2015 at 1:01 AM, Dennis E. Hamilton <de...@acm.org>
wrote:

> In the activities referenced in this note, the contribution of a coherent
> QA process is critical.  It is important for the formulation of tests, for
> the application of assessment procedures, and for the addition of tests
> found necessary as the result of incident reports and other cases found not
> covered by an evolving suite of tests.
>
>  - Dennis
>
> -----Original Message-----
> From: Dennis E. Hamilton [mailto:dennis.hamilton@acm.org]
> Sent: Thursday, June 4, 2015 16:24
> To: dev@openoffice.apache.org
> Subject: DChanges 2014 Papers and ODF Conformance/Compliance Assurance
>
> I took advantage of Corinthia as a place to build up materials on ODF
> Conformance/Compliance Assurance testing of software products, since
> creating profiles of feature compliance figures in the scope of the Apache
> Corinthia (incubating) project.
>
> The material is relevant, of course, to Apache OpenOffice and other
> implementations of ODF.
>
> The proposed structure for development of files, procedures, and
> assessments is at <
> https://cwiki.apache.org/confluence/display/Corinthia/ODF>.
>
> I have updated the ODF Conformance/Compliance Assurance Helix sketch
> there.  The connected treatment of ODF 1.2 Conformance that has been linked
> from that sketch has also been updated.  That overview is at <
> http://nfoworks.org/notes/2014/06/n140602.htm> and a trial diagram of the
> different conformance layers is at <
> http://nfoworks.org/notes/2014/06/n140602b.htm>.
>
> I am starting to put more effort into this material, including coming up
> with minimal test cases as baby steps.
>
> My papers from DChanges 2014 are also relevant to this effort.  Although
> the "Anti-Pattern" paper is about repairing change-tracking, a key
> conclusion is that one can't achieve an envelope within which interoperable
> interchange of changed-tracked documents is possible without have a
> surrounding envelope in which there is reliable interchange without any
> change tracking.  The "Anti-Pattern" paper provides a sketch of how one can
> establish that, and some principles that must be honored.
>
> I have not put authors versions of my DChanges 2014 papers on-line yet.  I
> will do so in the coming week.
>
>  - Dennis
>
> -----Original Message-----
> From: Dennis E. Hamilton [mailto:dennis.hamilton@acm.org]
> Sent: Tuesday, May 12, 2015 10:50
> To: dev@corinthia.incubator.apache.org
> Subject: DChanges 2014 Papers Available
>
> The final versions of papers on change-tracking from DChanges2014 have
> been published.  You can see the table of contents of the proceedings at <
> http://dl.acm.org/citation.cfm?id=2723147> by selecting to see the "Table
> of Contents."
>
> [ ... ]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: qa-help@openoffice.apache.org
>
>

RE: DChanges 2014 Papers and ODF Conformance/Compliance Assurance

Posted by "Dennis E. Hamilton" <de...@acm.org>.
Here is where the link to my copy of the promised paper can be found, as well as a link (doi) to the definitive source.

     - - - - - -

The PDF of the paper about RCT (Repaired Change-Tracking), "Tracked Changes: Navigating the Document-Format Anti-Pattern," provides a pattern-like model for the interoperability assurance for WYSIWYG document using standard document-file formats.  The author's final submission version is available for download in the bibliographic entry at <http://nfoworks.org/notes/2015/06/n150601.htm>.

A key finding in this paper is that in the absence of a profiled envelope in which there is interoperability assurance when interchanging documents using a format such as ODF, there is no prospect for such interchange working properly with change-tracking in the files.  

Conditions on which such an envelope can be established and change-tracking accomplished in a dependable way are sketched.

-----Original Message-----
From: Dennis E. Hamilton [mailto:dennis.hamilton@acm.org] 
Sent: Thursday, June 4, 2015 17:02
To: qa@openoffice.apache.org
Subject: FW: DChanges 2014 Papers and ODF Conformance/Compliance Assurance

In the activities referenced in this note, the contribution of a coherent QA process is critical.  It is important for the formulation of tests, for the application of assessment procedures, and for the addition of tests found necessary as the result of incident reports and other cases found not covered by an evolving suite of tests.

 - Dennis 

-----Original Message-----
From: Dennis E. Hamilton [mailto:dennis.hamilton@acm.org] 
Sent: Thursday, June 4, 2015 16:24
To: dev@openoffice.apache.org
Subject: DChanges 2014 Papers and ODF Conformance/Compliance Assurance

I took advantage of Corinthia as a place to build up materials on ODF Conformance/Compliance Assurance testing of software products, since creating profiles of feature compliance figures in the scope of the Apache Corinthia (incubating) project.

The material is relevant, of course, to Apache OpenOffice and other implementations of ODF.

The proposed structure for development of files, procedures, and assessments is at <https://cwiki.apache.org/confluence/display/Corinthia/ODF>.

I have updated the ODF Conformance/Compliance Assurance Helix sketch there.  The connected treatment of ODF 1.2 Conformance that has been linked from that sketch has also been updated.  That overview is at <http://nfoworks.org/notes/2014/06/n140602.htm> and a trial diagram of the different conformance layers is at <http://nfoworks.org/notes/2014/06/n140602b.htm>.

I am starting to put more effort into this material, including coming up with minimal test cases as baby steps.

My papers from DChanges 2014 are also relevant to this effort.  Although the "Anti-Pattern" paper is about repairing change-tracking, a key conclusion is that one can't achieve an envelope within which interoperable interchange of changed-tracked documents is possible without have a surrounding envelope in which there is reliable interchange without any change tracking.  The "Anti-Pattern" paper provides a sketch of how one can establish that, and some principles that must be honored.  

I have not put authors versions of my DChanges 2014 papers on-line yet.  I will do so in the coming week.

 - Dennis

-----Original Message-----
From: Dennis E. Hamilton [mailto:dennis.hamilton@acm.org] 
Sent: Tuesday, May 12, 2015 10:50
To: dev@corinthia.incubator.apache.org
Subject: DChanges 2014 Papers Available

The final versions of papers on change-tracking from DChanges2014 have been published.  You can see the table of contents of the proceedings at <http://dl.acm.org/citation.cfm?id=2723147> by selecting to see the "Table of Contents."

[ ... ]


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org