Notes from 26 Feb. 2024 ODF Teleconference

[Patrick Durusau <patrick@durusau.net>]

Greetings!

If this goes through, our meeting notes from the ODF TC teleconference on 26 February 2024.

Hope everyone is at the start of a great week!

Patrick

********************************

[12:01]ÂPatrick: 1. Dial-In, Roll Call, Determination of Quorum and Voting Rights

2. Motion (simple majority): Approve minutes of 12 February 2024 -
https://lists.oasis-open.org/archives/office/202402/msg00016.html

3. Motion (simple majority): Approve the Agenda

4. Editor's work review: Update on ODF 1.4 editing progress sheet
https://docs.google.com/spreadsheets/d/1J4TDjF7T62oN9Afhz1OTA6ePOFcCGlgjBF9L2xdF47o

5. OFFICE-4153 - ODF password-based package encryption enhancements
https://issues.oasis-open.org/browse/OFFICE-4153


6. OFFICE-4124: 'clear' attribute for line breaks (Presenter: Regina)
https://issues.oasis-open.org/browse/OFFICE-4124
Do we agree on the proposal and switch the resolution to "RESOLVED"?
In addition, do we agree to switch to target ODF 1.5?

7. OFFICE-3926: Use of attribute style:list-style-name in connection with pure <text:h> element is unclear (Presenter: Svante)
https://issues.oasis-open.org/browse/OFFICE-3926
Next steps to find a proposal?

8. OFFICE-2093: Update: https://issues.oasis-open.org/browse/OFFICE-2093 (Presenter: Svante)

9. Adjournment

[12:04]ÂPatrick: Attendance: Francis Cave, Patrick Durusau, Regina Henchel, Svante Schubert, Alfred Hellstern, Michael Stahl

[12:05]ÂPatrick: quorum - yes

[12:05]ÂPatrick: Minutes of 12 Feb. 2023 - approved by consent

[12:07]ÂPatrick: Agenda - approved by consent

[12:12]ÂPatrick: 4. Francis - cleared up duplicate reference marks, working on deleted items are referenced, restore deleted heading? for reference purposes

[12:12]ÂPatrick: Regina - keep the old heading with [deleted] following

[12:12]ÂPatrick: Alfred - doing it for deprecated, so do it for deleted

[12:13]ÂPatrick: removed or deleted ?

[12:14]ÂPatrick: use removed -

[12:16]ÂPatrick: target - March 11th for TC vote to make a committee specification.

[12:17]ÂSvante Schubert: After Francis updated the ODT's to WD-02, I have updated the HTML version. I have generated a WD-02.html suffixed file, but keep the last one with a stable name (have overwritten the old version) ->
https://oasis-tcs.github.io/odf-tc/odf1.4/part1-introduction/OpenDocument-v1.4-part1-introduction.html
https://oasis-tcs.github.io/odf-tc/odf1.4/part2-packages/OpenDocument-v1.4-part2-packages.html
https://oasis-tcs.github.io/odf-tc/odf1.4/part3-schema/OpenDocument-v1.4-part3-schema.html <-- here the ODT still has "Working Draft 01" in its heading
https://oasis-tcs.github.io/odf-tc/odf1.4/part4-formula/OpenDocument-v1.4-part4-formula.html

The above links are always referenced from the README.md of https://github.com/oasis-tcs/odf-tc (just scroll down a bit - first column first table)

[12:20]ÂSvante Schubert: 5. OFFICE-4153 - ODF password-based package encryption enhancements
https://issues.oasis-open.org/browse/OFFICE-4153

[12:21]ÂPatrick: Michael - has added Regina's proposals into the proposal

[12:23]ÂMichael Stahl: 4.16.1 manifest:algorithm-name
(should we add AES-GCM here? with updated reference, it is already allowed by the first bullet item, see https://www.w3.org/TR/xmlenc-core1/#sec-AES-GCM - is that enough?)

[12:25]ÂSvante Schubert: ^^the reference is normative and from a W3C recommendation, so I yes from the standardization perspective!

[12:31]ÂPatrick: remove producers producing Blowfish

[12:31]ÂPatrick: Svante - liberal to read, conservative to produce

[12:32]ÂPatrick: consumers should support - but producers should support AES-GCM

[12:41]ÂPatrick: Svante - wants latest security to be used, Patrick asks about how does this impact conformance?

[12:41]ÂMichael Stahl: Package producers that support encryption should support the value http://www.w3.org/2009/xmlenc11#aes256-gcm. Package consumers that support encryption shall support the values http://www.w3.org/2009/xmlenc11#aes256-gcm, http://www.w3.org/2001/04/xmlenc#aes256-cbc, Blowfish CFB and urn:oasis:names:tc:opendocument:xmlns:manifest:1.0#blowfish.

[12:42]ÂMichael Stahl: Package producers that support encryption should support the value http://www.w3.org/2009/xmlenc11#aes256-gcm. Package consumers that support encryption should support the values http://www.w3.org/2009/xmlenc11#aes256-gcm, http://www.w3.org/2001/04/xmlenc#aes256-cbc, Blowfish CFB and urn:oasis:names:tc:opendocument:xmlns:manifest:1.0#blowfish.

[12:51]ÂMichael Stahl: 4.16.2 manifest:checksum (or/also deprecate it?)

[12:52]ÂMichael Stahl: same question for 4.16.3 manifest:checksum-type

[12:56]ÂSvante Schubert: https://docs.oasis-open.org/office/OpenDocument/v1.3/os/schemas/OpenDocument-v1.3-manifest-schema-rng.html#113

[12:58]ÂMichael Stahl: nobody objects to adding "deprecated"

[12:58]ÂSvante Schubert: nobody objects to making it "optional"

[12:59]ÂMichael Stahl: 4.16.5 manifest:initialisation-vector (The W3C https://www.w3.org/TR/xmlenc-core1/#sec-AES-GCM requires the IV to be stored as a prefix to the encrypted data - so it is redundant to store it in an attribute here too, but also harmless, perhaps best to leave it as it is?)

[13:03]ÂSvante Schubert: https://docs.oasis-open.org/office/OpenDocument/v1.3/os/schemas/OpenDocument-v1.3-manifest-schema-rng.html#37