[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Notes From March 22, 2021 ODF TC meeting
Greetings!
The notes from the ODF TC meeting, March 22, 2021 follow below.
Hope everyone is at the start of a great week!
Patrick
********************************
Patrick: quorum - yes
Andreas Guelzow: It would be nice if the agenda would include the access code.
Patrick: agenda - approved by consent
Patrick: minutes of March 15, 2021 - approved by consent
Patrick: Revision of Charter -
Patrick: The purpose of this TC is to maintain and eevolve the OpenDocumentFormat (ODF) to meet the changing needs of office software for an XML-based format for interchange and collaboration.
The Open Document Format (ODF) and its revisions must meet the following requirements:
1. be suitable for office documents containing text,
spreadsheets, charts, and graphical documents,
2. be compatible with the W3C Extensible Markup Language (XML)
v1.0 and W3C Namespaces in XML v1.0 specifications,
3. be compatible, to the extent possible, with OOXML, ISO/IEC 29500, to promote seamless interchange between software systems,
Patrick: eevolve -> evolve
Alfred Hellstern: I can hear you, but my microphone isn't working
Alfred Hellstern: trying again
Patrick: will at least to replace must on the second line
Patrick: The Open Document Format (ODF) and its revisions will at least meet the following requirements: (with the suggested language from Francis)
Patrick: 1. be suitable for office documents that may include text, spreadsheets, charts, or graphical content, - sugggested
Patrick: 1. be suitable for office documents that include, but is not limited to, text, spreadsheets, charts, or graphical content,
Patrick: 1. be suitable for office documents that include, but are not limited to, text, spreadsheets, charts, or graphical content,
Patrick: last one - ok
Patrick: databases are not excluded just not explicitly included
Patrick: 1. be suitable for office documents that include content such as, text, spreadsheets, charts, or graphical content, - Francis
Patrick: Alfred - forward looking charter - open - if present activity - a closed list
Patrick: 1. be suitable for office documents that include content such as, text, spreadsheets, charts, or graphical content, - what we are doing now and in the foreseeable future - ok
Patrick: 2. be compatible with the W3C Extensible Markup Language (XML)
v1.0 and W3C Namespaces in XML v1.0 specifications,
Patrick: #2 is ok.
Patrick: 3. be compatible, to the extent possible, with OOXML, ISO/IEC 29500, to promote seamless interchange between software systems,
Patrick: Andreas - good place to add interoperability of ODF producers and consumers of ODF ?
Patrick: Francis - be suitable for interoperable implementation in different systems
Patrick: Francis - suitable for the creation of interoperable implementations
Patrick: Francis - what we produce has to be suitable for interoperable implementation
Patrick: Andreas - need better definitions for interopreability
Patrick: Andreas - even before OOXML
Francis Cave: be conducive to the development of interoperable implementations
Patrick: 3. create definitions and conformance requirements that promote interoperable implementations
Patrick: New #3
Patrick: new #4. to promote interchange with other office formats
Francis Cave: ...with other office file format standards
Patrick: 4. to promote interchange with other office file format standards
Patrick: Svante - Feature - request - what exists in other file formats
Patrick: If it's a format feature - include reference to CSS work
Patrick: Regina - PDF as a standard -
Patrick: 4. to promote fidelity of the user experience when interchanging documents between office systems
Patrick: Andreas - developers would disagree -
Patrick: Francis - user experience is too broad for Andreas
Patrick: Svante - issue to think about:
3. extending the expressiveness of the ODF format by defining a higher-level view upon the ODF XML based on common user's perspective. One or more XML nodes will be bundled to user known ODF feature. ODF features consist of structural and behavior features. Behavior features are subfeatures (e.g. styles & metadata) which always depend on structural features (e.g. table, paragraph, image, character).
4. relevant information to ODF implementors should be automated extractable from the specification (or the specification being generated from it).
Patrick: Francis - an abstract model for office documents - may not be appropriate for our TC but interested in the work
Patrick: Svante - high level view groups nodes -
Patrick: adjourned -
-- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]