Component/s: Ballot request
Submitted on Monday, January 25, 2021 - 18:35
Submitted by user:
Submitted values are:
Your name: Patrick Durusau
TC name: OASIS Open Document Format for Office Applications (OpenDocument) TC
TC email address: firstname.lastname@example.org
Title: Open Document Format for Office Applications (OpenDocument) Version
Committee Specification URI:
Committee Specification editable source URI(s):
Certification by the TC that all schema and XML instances are well-formed and
that expressions are valid: We so certify
Clear English-language summary of the specification:
Open Document Format for Office Applications (OpenDocument) Version
1.3 specifies the characteristics of an XML-based
application-independent and platform-independent digital document file
format, as well as the characteristics of software applications which
read, write and process such documents. This standard is applicable to
document authoring, editing, viewing, exchange and archiving,
including text documents, spreadsheets, presentation graphics,
drawings, charts and similar documents commonly used by personal
productivity software applications.
Relationship of this specification to similar work: See also, ISO/IEC 26300
Statements of Use-
Link to Statement of Use #1:
Link to Statement of Use #2:
Link to Statement of Use #3:
Additional Statements of Use:
First public review announcement URI:
Comment resolution log:
Additional public review announcement URIs:
Additional comment resolution log URIs:
Earlier attempts to standardize: No
Sources of explanatory information:
The editable source URL field truncates to only one URL so I just left it
The same is true for the Additional Comment Resolution Log URI field. I
one but there are two (2) such links.
BTW, the links in this from should have https:// NOT http://
On my first try:
"Committee Specification editable source URI(s) field is required.
Relationship of this specification to similar work field is required."
I can understand the first, except that it is broken. The second makes no
at all. I'll put in ISO/IEC 26300 for grins.
Good to see A/B user testing was done on the homepage for navigation.
The results of this submission may be viewed at: