OASIS Open Document Format for Office Applications (OpenDocument) TC

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear TC members, Below you find a draft agenda for our TC call on Monday, 2015-11-23. I will send out the final agenda, hopefully with more minutes listed, on the Friday before the meeting. A new spreadsheet is attached with issues to be addressed in this call. The spreadsheet has three columns: Column A: Issue Number as Hyperlink to JIRA Column B: A re-written (in most cases) description of the issue Column C: My suggested disposition of the issue (feel free to disagree, it is just a starting point for discussion, seriously) Comments or suggestions about this new presentation of the issues welcom e. The Open Document Format Technical Committee will have its next TC Coordination Call on November 23rd at 1430 UTC. http://www.timeanddate.com/worldclock/meetingdetails.html?year=2015&mont h=11&day=23&hour=14&min=30&sec=0&p1=25&iv=1800 The call counts towards voter eligibility. Teleconference Numbers Canada - (use US number) Denmark - +45 78 77 25 34 Germany - +49 30 255550324 Hungary - +36 1 987 6874 The Netherlands - +31 6 35205016 USA - +1 641-715-3580 Access code (for all numbers): 438-387 Chat room for meeting is at: http://webconf.soaphub.org/conf/room/odf Agenda - ------ 1. Dial-In, Roll Call, Determination of Quorum and Voting Rights 2. Motion (simple majority): Approve the Agenda 3. Motion (simple majority): Approve the Minutes from former TC calls - - - 2015-08-03 - working call - pending - - 2015-09-14 - pending - - 2015-09-28 - pending - - 2015-10-12 - pending - - 2015-10-26 - pending - - 2015-11-09 - attached, ODF-TC-Minutes-09November-2015-draft.txt (I will upload to the repository after approval.) 4. Jos van den Oever - report on plugfest 5. JIRA Issues for discussion: Spreadsheet attached, JIRA-Issues-ODF-TC-23November2015.ods 6. New comments on the comments list since last TC call [none so far] 7. Next meeting: 2015-12-07 at 14:30 UTC. 8. Adjournment Hope everyone is at the start of a great week! Patrick - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJWQjzMAAoJEFPGsgi3MgycU+AP+gNR7+T8nzl7ZIrdVufgdlBG p++GXAU1hCVi8yTb2fgY7p2oa2TGwun2YWm01fNlIGJjyGWsGcBTYKosw+2pi8bL ZoW2oocZUnha5Q+aB8wrPX7mscZlHwWMdYKChsbhyXVu0ZgTEf+py3wTdt/Ywrec 1uxo09qxyF5aLhxTRXAzRfCCK2ecnOndMO0Qa5LhFwq+/tqHDqBR4R/9u36n1doF Cr7wIOgdAoIGrn7cpib55ZOsaByjw9GKaVpxu/46po7tnysjOZqp9jMkg7ZoYacd u0kL8NJd8gqUa8yVT3BOii/coZs7DEWZwVnGLEqw1IiL+VSBIV14vQzJ7hB2XFFH VwpCbfj0I+oz2lZeDxoZlO4Tb+dbEexGta5xQs0Tfc4OMvlpe5UnM3sttT9sWH5b I2sY5QQmPYsi/7v47TXhPKUWOU/D12fC9vMLJvKiZwjUshAX1qvraWqPRpHHkjXR m5wBGZ9bDbDOIGDWmlDiJn+Bhi21Lx8JeDV8ygqDfsLTLA/mPplVk0RUCE+IQYAV bnW5hG0ESadBjumurJc7DA19jHmUbPkEgk9MYe8LFHq9j01ItfDnYrzuiv86u191 lQ0XDZe9uIeU+YFtk7c+me+5OyVK8upE3ZahKWs6uJv+7zJZI9LHct4qBIWXSYaU HdkTNwm242Ti1uB7C83j =fTup -----END PGP SIGNATURE----- Attachment: JIRA-Issues-ODF-TC-09November2015.ods Description: application/vnd.oasis.opendocument.spreadsheet ODF-TC-Minutes-09-November-2015 1. Dial-In, Roll Call, Determination of Quorum and Voting Rights 9:00 AM 9:05 roll-call Quorum +Thorsten Behrens +Andreas Guelzow +Regina Henschel Darrin House Svante Schubert +Michael Stahl +Andras Timar +Patrick Durusau Names of voting members preceded by "+" Voting members 5 out of 8 - 62% 62 percent quorum 2. Motion (simple majority): Approved, unanimous consent. 3. Pending prior minutes: 3. Motion (simple majority): Approve the Minutes from former TC calls - - 2015-08-03 - working call - pending - 2015-09-14 - pending - 2015-09-28 - pending - 2015-10-12 - pending - 2015-10-26 - pending No action. 4. Help with 2015-10-26 minutes - Patrick lost his chat log, request for a copy held by other members. (Post-meeting Regina forwarded her copy of the chat log from 2015-10-26) 5. Outstanding JIRA Issues (in issue order): (A note on the syntax for disposing of issues. Where a block ends with Patrick: followed by an issue disposition, the question was put to the attending TC members and the action listed was by unanimous consent. I have included links to the issues so my entry of the dispositions can be tracked.) https://issues.oasis-open.org/browse/OFFICE-638 , https://issues.oasis-open.org/browse/OFFICE-657 , https://issues.oasis-open.org/browse/OFFICE-659 Michael Stahl: what i remember is that in the cluster OFFICE-638, OFFICE-657, OFFICE-659, we wanted to ask Andreas about which issue to resolve as duplicate of which issue Andreas Guelzow will review this cluster of issues and advise on which one should remain open and he will be assigned the open issue. ***** https://issues.oasis-open.org/browse/OFFICE-645 - Regina - put to ODF-Later, if someone implements it we would support it. Patrick: ODF-Later ***** https://issues.oasis-open.org/browse/OFFICE-688 Regina - close - if someone wants to look for alternatives, can re-open the issue Patrick: Close - Office-688 ***** https://issues.oasis-open.org/browse/OFFICE-730 Regina - suggests close - can implement in a namespace if someone wants it Patrick: Close - Office-730 ***** https://issues.oasis-open.org/browse/OFFICE-734 Andreas Guelzow - confuses application feature with ODF function Patrick: Close - Office-734 ***** https://issues.oasis-open.org/browse/OFFICE-737 Patrick - incompatible attribute name change from 1.2 Patrick: Close Office-737 ***** https://issues.oasis-open.org/browse/OFFICE-737 Regina - close office - 740 Patrick: Close - office - 740 ***** https://issues.oasis-open.org/browse/OFFICE-742 Patrick: Close Office-742 ***** https://issues.oasis-open.org/browse/OFFICE-747 Andreas - would be a compatibility issue, everything would start breaking Patrick: Close office-747 ***** https://issues.oasis-open.org/browse/OFFICE-752 Patrick: Office-752 is dup of Office-734 Patrick: Close Office-752 ***** https://issues.oasis-open.org/browse/OFFICE-758 Patrick: Office-758 set to ODF-LATER ***** https://issues.oasis-open.org/browse/OFFICE-765 Regina Henschel: close as duplicate of 742 Patrick: Office-765 is dup of Office-742 and close Patrick: Close Office-765 ***** https://issues.oasis-open.org/browse/OFFICE-779 Regina: I don't see a use case, and I'm not sure whether the "fo"-namespace would be correct. Patrick: Andreas suggests ODF-Later Patrick: Move Office-779 to ODF-Later ***** We stopped processing issues at this point due to numerous dial-in issues. Better dial-in services would be appreciated. Last issue outstanding from today's list: https://issues.oasis-open.org/browse/OFFICE-898 6. New comments on the comments list since last TC call [none so far] 7. Next meeting: 2015-11-23 at 14:30 UTC. 8. Adjournment - 15:28 UTC by unanimous consent.

Here are some comments on issues that were not discussed in the meeting yet. OFFICE-1439 Automatic styles (ODF all versions) Issue contains a discussion on clarifying the distinction between common styles and automatic styles. Suggestion: 1.3 Major OFFICE-1437 text:lists vs text:numbered-paragraph (ODF all versions) == Note: Numbered paragraphs form an equivalent, alternative way of specifying lists. A list in <text:list> representation can be converted into a list in <text:numbered-paragraph> representation and vice versa. == http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#element-text_numbered-paragraph It makes sense to deprecate <text:numbered-paragraph>. We could add text to the specification on how that would work which suggests that the recommended way to store lists is with <text:list>. This issue is rightly categorized as minor for 1.3. Suggestion: 1.3 Minor OFFICE-1436 Suggestion: 1.3 Store versions of a document in one file. LibreOffice supports saving of previous versions into the same ODF. This can be done via File->Versions. Suggestion: ODF Later, unless change-tracking SC picks it up. OFFICE-1435 Andrzej Hunt worked on this for LibreOffice. He used common number styles to store the unit information. http://conference.libreoffice.org/2015/the-program/talks/quality-assurance/#Unit%20Verification%20and%20Dimensional%20Analysis%20for%20error%20detection%20in%20LibreOffice%20Calc So, in theory it is already possible. It would be a great, but non-trivial addition to the specification. Suggestion: ODF Later OFFICE-1431 SVG Integration The proposal suggests to use SVG more prominently. The situation now is better than at the time of the comment. The text in ODF 1.2 says 'should'. === Note: While the image data may have an arbitrary format, vector graphics should be stored in the [SVG] format and bitmap graphics in the [PNG] format. === http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#element-draw_image Suggestion: ODF Later to specify interaction between SVG images and the host documents. OFFICE-1426 Greek Numbering Notation The issue concerns the correctness of greek numbering of lists in ODF. ODF does not explicitly support greek numbering at the moment, so it cannot be wrong. LibreOffice uses the non-standard string style:num-format="a, ß, ... (gr)" to specify greek numbering. Suggestion: ODF Later

And some more comments to the issues on Patricks latest spreadsheet. OFFICE-1420 odf 12cd01,19.319 style:paper-tray-name "style:paper-tray-name should be moved to settings.xml (or removed altogether)" I dont really see the point of having this attribute. We should not remove it in 1.3. There is no implementation work needed to remove this, so ODF Later does not apply. This moves to ODF Next. OFFICE-1395 Use schematron in ODF Great idea and I've started on it in OFFICE-3887. Let's keep it as major issue for 1.3. OFFICE-1378 Requirement - reinvent the spreadsheet Clearly ODF Later OFFICE 1377 Requirement [ODF needs to be audited against the requirements of CDRF] CDR, CDRF, and WICD never made it to recommendations. Close the issue. OFFICE 1376 Requirement [ODF needs to support round-tripping of all HTML and CSS features] import HTML pages and round-trip them without loss This is an enormously big task: ODF Later OFFICE 1374 duplicate of OFFICE-1431 OFFICE-1312 Inconsistently named elements/attributes (ODF all versions) Very good comment. Logical names really help developers. Large changes. Either in ODF 1.3 while retaining deprecated names or ODF Next OFFICE-1306 is created from a reply to OFFICE-1277 There are 17 issues like this. The original post is very good. I'm not sure about the replies. Have not read them all yet. OFFICE-1286 [Remove form:control-implementation and form:properties] I very little no knowledge of XForms. Removing is not something we can do in 1.3. Only deprecating is possible. OFFICE-1283 .oth is not specified in a normative part and should be removed from the non-normative appendix C. Either .oth is added to part1 section 2.2 in 1.3 or it is removed from appendix C So this should be fixed in 1.3 OFFICE-1281 very useful comment on how to define if a document contains extended information. This ties in with the idea of using profiles. The author is concerned that there are too many ways in which one can add proprietary information in an ODF file. ODF 1.2 comes in the flavors ODF 1.2 and ODF 1.2 extended. ODF 1.2 still allows many places where undocumented formats are possible. Should we close these in 1.3? Such a minimal document model is very good for archiving and for levelling the playing field. It might be worth a shot for 1.3 and perhaps Rick Jelliffe could help. OFFICE-1277 This is a very important topic. We need a common macro language. Like OpenFormula this might be a whole part of the specification.