This page list of items that have to be completed before a public review of OpenDocument v1.2 may start:

Part

Task

Responsible

Target Date

Target CD

Remark

-

Version Significance

Dennis E. Hamilton

Use of office:version and manifest:version needs to be clarified as to the degree to which they are (loosely) descriptive and restrictive and what the requirements are for down-level and up-level acceptors, including the preferable behavior of down-level processors that encounter unrecognized or unsupported features in a known or later version.

-

Specific Document and Component Types

Dennis E. Hamilton

The variety of document types and the types that may arise as internal and external components of documents need to be identified, their precise characteristic structures stipulated, and their conformance characteristics, individually and in aggregate, established

-

Style guide for description of identifiers and references in attributes

Dennis E. Hamilton

Attributes such as table:name have values that are resolved in usually unstated domains that are sources of unique identifiers independent of other domains. Attributes can be used to assign these identifiers to specific elements of a document, to refer to and supplement that element, and sometimes to be user-generatable and/or human readable. This and other aspects of domains of identification where there are referential arrangements need to be clarified with regard to specific attribute usages and their descriptions, at least in an agreed manner of explanation. Attributes having the same or different names but comprising values in the same domain should be described as such.

-

Style guide with respect to processing models and modes

Dennis E. Hamilton

There are different processing modes used informally throughout the ODF specification (e.g., mention that a feature is relevant to or sourced by user-interface interaction). There should be agreed nomenclature for differentiating when a feature is related to an abstract document-model structure (e.g., a table), when it extends to visual or graphical presentation (e.g., a color) on a medium, when it is related to interaction with the abstract document, and when it serves as guidance for certain manipulations of an existing document (e.g., default styles for addition of new rows or columns of a spreadsheet table). These roles of elements and attributes and the features they express should be stated, where applicable, using consistent language that is not prejudicial with respect to automated document processing, interactive manipulation over an user interface, mechanical generation and customization of documents, and other applications.

1

Conformance clauses

Michael Brauer

10-Dec-2008

already in progress

1

Approved proposals have to be integrated into the specification where this did not happen already

Patrick Durusau

See List of Proposals

1

Approved proposals have to be integrated into the schema where this did not happen already

Michael Brauer

5-Dec-2008

See List of Proposals

1

References to the schema have to be added

1

Validation check for schemas

Michael Brauer

ongoing

A validation check is part of each schema that is uploaded

1

Validation check for grammars that are not schemas

1

Validation check for examples

1

An appendix that describes changes from ODF 1.1 has to be prepared.

1

Where are several suggestion that it would be advantageous to use NVDL for ODF 1.2 to improve our validation possibilities. We need to decide on this. But if we want to use NVDL, then we have to prepare the style NVDL scripts.

Michael Brauer

10-Dec-2008

See here

1

Review of public comments which are defect reports

1

The "Acknowledgments" section has to be updated.

1

Proposal - Adaption of W3C RDFa standard

Svante Schubert

10-Dec-2008

From the feedback of the W3C Semantic Web group on our metadata proposal. This is one of the four ODF 1.2 change proposals that has evolved. See here

1

Proposal - Usage of W3C GRDDL standard

Svante Schubert

10-Dec-2008

From the feedback of the W3C Semantic Web group on our metadata proposal. This is one of the four ODF 1.2 change proposals that has evolved. See here

1

Proposal - Adaption of RDF mapping to relative URLs

Svante Schubert

10-Dec-2008

From the feedback of the W3C Semantic Web group on our metadata proposal. This is one of the four ODF 1.2 change proposals that has evolved. See here

1

Proposal - Using URL fragment identifiers for ODF media types

Svante Schubert

10-Dec-2008

From the feedback of the W3C Semantic Web group on our metadata proposal. This is one of the four ODF 1.2 change proposals that has evolved. See here

1

Review of IS 29500-2:2008 Open Packaging Conventions for part URI, pack: URI scheme, package nomenclature, and Zip mapping work that can be applied for ODF 1.2 package and RDF metadata specifications

Dennis E. Hamilton

Selective reference to this material may expedite reconciliation of package and URI rules for ODF 1.2. See comment on list.

1

Make Normative MIMETYPE values for Conformant document packages

Dennis E. Hamilton

The MIMETYPE MIME type values defined in the non-normative IANA-referencing Appendix are required normatively for determination of the types of conformant documents and as the value of the office:mimetype attribute for announcing the structure of an <office:document> element in all of the ways one may occur. This is needed to explain the document processing and the conformance requirements in ODF 1.2 Part 1 and also needs to be reconciled with Part 3.

1

table:protect(ed) inconsistency

Michael Brauer

8-Dec-2008

There was an inconsistency between the description and the schema for table:protect(ed). A decision how to resolve this is required. See Table-Protected proposal.

2

Conformance clauses

2

The formal part has to be restructured to meet the structure of part 1.

Patrick Durusau

2

Validation check for grammars that are not schemas

2

Validation check for examples

2

Review of public comments which are defect reports

2

The "Acknowledgments" section has to be updated.

3

Conformance clauses

Michael Brauer

3

The packages part has to be restructured to meet the structure of part 1.

Patrick Durusau

3

Approved proposals have to be integrated into the specification where this did not happen already

Patrick Durusau

See List of Proposals

3

Approved proposals have to be integrated into the schema where this did not happen already

Michael Brauer

See List of Proposals

3

Validation check for schemas

Michael Brauer

ongoing

A validation check is part of each schema that is uploaded

3

Validation check for grammars that are not schemas

3

Validation check for examples

3

Review of public comments which are defect reports

3

References to the schema have to be added

3

An appendix that describes changes from ODF 1.1 has to be prepared.

3

The "Acknowledgments" section has to be updated.

3

Improve digital signature specification

Bob Jolliffe/Jomar Silva

See List of Proposals

3

Review of IS 29500-2:2008 Open Packaging Conventions for part URI, pack: URI scheme, package nomenclature, and Zip mapping work that can be applied for ODF 1.2 package and RDF metadata specifications

Dennis E. Hamilton

Selective reference to this material may expedite reconciliation of package and URI rules for ODF 1.2. See comment on list.

3

Make Normative MIMETYPE values for Conformant document packages

Dennis E. Hamilton

The MIMETYPE MIME type values defined in the non-normative IANA-referencing Appendix are required normatively for determination of the types of conformant documents and as the value of the office:mimetype attribute for announcing the structure of an <office:document> element in all of the ways one may occur.

3

Standardize the compatiblity options important for interop. Additionally add text which suggest that implementers submit the compat options they use.

Florian Reuter

3

Standardize form control types like "com.sun.star.*"

3

Clarify whether normalization in input-fiels applies or not.

3

Clarify meaing of style:dynamic-spacing.

3

Add optional attribute which allows to write out the position relative to the page of objects for interop.

3

Submit "page-anchoring" to accessiblity SC.

3

Depricate "sub-tables".

3

Specify "Star-View-Metafiles" or discourage their use.

3

Add a "page-break" element similar to a "soft-page-break".

3

Write out default values.

3

Support odd-page, even-page and auto as an attribute of fo:break-before and fo:break-after.

3

Clarify how master-page-break and fo:break-before resp. fo:break:after interact.

3

Clarify what master-page-break="" means.

3

Specify how to distinguish between shapes and text-boxes.

3

Discourage use of "next-page-style". Instead add "style:header-first" similar to "style:header-left"

3

*Forbid* the use of the generator-id. Instead force implementors to use a compatiblity option at least.

3

Add "field-marks" or a similar mechanism.

3

Grouping for radio-buttons.

3

Clarify how fit-to-size and "nn" interact.

3

Allow anonymous master-pages.

3

Support for custom display names in data pilot tables.

http://wiki.oasis-open.org/office/display_names_in_data_pilot

OpenDocument v1.2 tasks (last edited 2008-12-01 13:04:22 by freuter)