The conformance of OpenDocument Format document files is multi-dimensional. Understanding the intersecting constraints that apply to the different format cases and their conformance conditions is presented in a conformance matrix by which the different categories can be appraised visually.
The document-file conformance matrix is only for the recorded documents, not anything to do with the categories of processors that accept and produce them. Processing of document files and higher-level activities, such as arrangements for collaborative interchange of document files, all hinge on having conformance of the document format at their foundation. These are important to the context of ODF 1.2 Conformance even though they extend beyond matters of strict document-file conformance.
In the OASIS ODF 1.2 specification, "conformance clauses" are employed for both conformance and compliance cases. Here, those and several additional categories of specification are supported, although specified separately. These categories depend upon the conformance statements and conformance assessments for their additional layering.
- Conformance is applied to instances of the document-file format. An instance may qualify as conformant in more than one way. It might not qualify in any way, thereby being completely non-conformant. Deviations in otherwise conformant documents fall somewhere in the middle.
- Compliance is applied to implementations of processors that accept and/or produce conformant documents. Although the resilience of processors that encounter non-conformant documents is of interest, compliance applies to production and consumption of a supported category of conformant document files. It is possible, as is mainly the case for ODF 1.2, that there are no significant compliance provisions in the OASIS Standard ODF 1.2 specification beyond establishment of general categories of processors.
- Application Profiles provide constraints and additional requirements for specific application domains. These are not provided by the ODF 1.2 specification. Profiles typically reflect agreements formed within a particular community of use and operation for the document-file format. Processors that operate within the conditions of a profile satisfy the requirements of the specific community. Application profiles are specialized conformance cases; they may extend and restrict the formal conformance statements.
- Interoperability Scenarios are cases of interoperable usage in arrangements where application profiles are mutually honored. Based on definite application profiles, these scenarios are related to compliance within the regime of an application profile. Interoperability scenarios may extend to the treatment of out-of-profile and non-conformant documents and may be the only significant compliance cases applicable for practical usage.
- Impementation Profiles generally apply to particular individual implementations of document-processing software and how those implementations deal with non-conformant documents, conformant documents (extended or not), and particular profiles as well. The support for features may be targeted to interoperability scenarios. Implementation-profile statements may be provided by software producers in support of qualification of the software for particular usage and interoperability cases. Given a structure for testing and verifying an implementation profile, third parties may provide independent implementation assessments for independent confirmation or other purposes.
Each category has specifications and means for testing adherence, detecting deviations, and supporting trouble-shooting, forensic analysis, and maintenance.
- Test Assertions make explidit statement of measurable conditions on the achievement of a specified case. Test Assertions may also specify prohibitions and conditions on the failures of certain cases. Test Assertions are not tests, although their satisfaction can be assessed with tests.
- Test Cases are explicit test items. A test item can be applied repeatedly and reliably. Satisfaction of the case (which may constitute a negative result) may be evidence on behalf of multiple test assertions. Likewise, a test assertion may have many test cases that contribute to assessment of the assertion's satisfaction: These are generally many-to-many relationships.
- Test Fixtures are instruments employed in the conduct of of test cases which may be semi- or fully-automated. Some cases might be satisfiable by manual procedures. Forensic tools are a variation/spin-off from the development of test fixtures. There can be automated assessment and validation tools at least at the document-file conformance level.
- Test Assessments catalog the results of the application of multiple test cases, whether enumerated across products (horizontal) or over the assertions as evaluated for an individual product.
An ODF 1.2 Conformance Matrix provides links for progressive disclosure of details that apply in each grid element and its intersecting categories. The conformance and compliance aspects are keyed to the relevant passages of the ODF 1.2 specification. Additional guidance with regard to application profiling and interoperability scenarios and structuring of implementation profiles is entirely supplemental and will be cross-referenced from separate materials..
The Conformance Matrix and its links to supporting materials constitute the ODF 1.2 Conformance Analysis.
- n140602b: ODF 1.2 Conformance Analysis [latest]
- n140602c: ODF 1.2 Conformance Trial Matrix
- n140602a: Diary & Job Jar
- n080402: ODF: Open Document Format for Office Applications (OpenDocument)
- n140504: ODF 1.2 Schema Reference
- Postma, André. Methodologies to achieve Smart Grid system interoperability through standardization, system design and testing. Mandate M490 Working group Interoperability, CEN CENELEC ETSI Smart Grid Coordination Group, 2014-05-06 presentation. 804,118 byte PDF file. Accessed 2014-06-27 at
- Hamilton, Dennis E.
- ODF 1.2 Conformance. nfoWorks nfoNote folio n140602 0.04, March 28, 2016. Accessed at <http://nfoWorks.org/notes/2014/06/n140602.htm>.
created 2014-06-10-17:56 -0700 (pdt) by