Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Simple touch-ups where "." needed and fixed a typo

...

  1. Conformance Requirements
    Conformance cases for ODF documents are complex.  A matrix of the overall conformance cases is used to characterize how the major format variations are treated
  2. Single File Documents
    The ODF Specification provides for single XML files as carriers of complete ODF documents.  Such documents are not quite as flexible as their multi-part counterparts carried inside of an ODF Package (a special usage of Zip).  The single file documents are very useful, however:
    • Single-file documents are easy to create and employ for the creation of tests that exercise essential features using simple, annotated XML files.  These are useful in controlling the variations among features, making test cases more precise and isolating observed deviations in processing.
    • Single-file documents are appealing for automatic generation of documents from databases or other processes for mechanically producing ODF documents from other data.
    • Single-file documents are often preferable for embedded documents inside of ODF Packages for overall documents (a case that is not adequately verifedverified).
    • Single-file documents can be simpler and preferable as template documents and as parts of master documents
    • Single-file documents are useful as a form for conveying the essential simple structure of ODF document files for familiarization and for more-isolated testing of implementation functionality.
    • Single-file documents are a basis for familiarization with the ODF 1.2 schemas and their feature-level connection with semantic information in the specification.
  3. ODF Packaging
    The specific format employed for ODF Documents conveyed in ODF 1.2 Packages requires iterative development of features and their verification for the packaging structures themselves, as defined in ODF 1.2 Part 3 and supplemented by a few requirements in other parts.  There are a number of unique features (such as application of digital signatures and use of encryption/decryption) that apply for packages.  These are defined for use more broadly than to specific application as a carrier of ODF 1.2 documents.
  4. Multi-Part ODF Document Packages
    Single-file documents all have multi-part flavors that employ ODF Packaging  There are portions of Assurance Helix for those cases  Multi-part forms have important additional cases involving use of embedded materials, cross-references among materials, and additional ways of linking and carrying meta-data information  These are the most-common form of ODF documents "in the wild."  Mulit-Part documents will be the stress cases for interoperability, successful round-trip usage in collaborative work, and ability to substitute implementations while preserving fidelity to the intended document.
  5. Extended Features and Extension Mechanisms
    There are systematic provisions for the presence of extensions in the file formats for ODF documents. Providing benign or gracefully-reduced functions in the face of extensions that are not understood is an important factor in both the definition of extensions and in the recognition of them.  Extensions can be peppered almost anywhere in the above cases and are provided for in the conformance requirements.  The identification of extensions, the source of their definitions, and behavior in the face of them are also factors in the development of compliance information.

...