OASIS Open Document Format for Office Applications (OpenDocument) TC

Greetings! Reminder: Proposals for ODF 1.3 have closed. Proposals welcome for ODF 1.4! Below you find a draft agenda for our TC call on Monday, 2018-06-18 The steps from here I list in the agenda are just preliminary and I expect and welcome suggestions and changes. Consider it to be staring point for our discussions. 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 Please send comments to the mailing list. Agenda ------ 1. Dial-In, Roll Call, Determination of Quorum and Voting Rights 2. Motion (simple majority): Approve the Agenda 3. Motion (simple majority): Notice of minutes from prior TC calls - pending 4. Meeting time for 18 June 2018 - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=6&day=18&hour=16&min=0&sec=0&p1=25&p2=37 5. Editorial tasks to finish ODF 1.3 for public review (before it becomes a committee specification, OASIS standard vote follows committee specification) a. Review current drafts and add/correct styling as appropriate. (Remember to remove references to part 5, Change Tracking; Add prose/references for OpenPGP encryption) b. Review changes as recorded in the changes appendix against the JIRA issues. c. Accept all changes and make another pass over the drafts for typos and style errors. d. Generate annotations for all elements and attributes e. Select random annotations for manual proofing against the schema f. Final review, all sections, all potential issues 6. Next meeting: ?????. I left this open because weekly meetings with no active list of issues to discuss, might not be the best use of the TCs time. Perhaps every two weeks to review progress in and through the steps listed above? 7. Adjournment Hope everyone is at the start of a great week! Patrick -- 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 Attachment: signature.asc Description: OpenPGP digital signature

Hi, I may not make the meeting today. And if I am able to I will need to leave it by 10:35 MST. Next Monday July 2nd is a holiday here in Canada: Canada Day . IF we have a meeting I am unlikely to make that meeting. Andreas On 18-06-16 01:00 PM, Patrick Durusau wrote: Greetings! Reminder: Proposals for ODF 1.3 have closed. Proposals welcome for ODF 1.4! Below you find a draft agenda for our TC call on Monday, 2018-06-18 The steps from here I list in the agenda are just preliminary and I expect and welcome suggestions and changes. Consider it to be staring point for our discussions. 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 Please send comments to the mailing list. Agenda ------ 1. Dial-In, Roll Call, Determination of Quorum and Voting Rights 2. Motion (simple majority): Approve the Agenda 3. Motion (simple majority): Notice of minutes from prior TC calls - pending 4. Meeting time for 18 June 2018 - https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=6&day=18&hour=16&min=0&sec=0&p1=25&p2=37 5. Editorial tasks to finish ODF 1.3 for public review (before it becomes a committee specification, OASIS standard vote follows committee specification) a. Review current drafts and add/correct styling as appropriate. (Remember to remove references to part 5, Change Tracking; Add prose/references for OpenPGP encryption) b. Review changes as recorded in the changes appendix against the JIRA issues. c. Accept all changes and make another pass over the drafts for typos and style errors. d. Generate annotations for all elements and attributes e. Select random annotations for manual proofing against the schema f. Final review, all sections, all potential issues 6. Next meeting: ?????. I left this open because weekly meetings with no active list of issues to discuss, might not be the best use of the TCs time. Perhaps every two weeks to review progress in and through the steps listed above? 7. Adjournment Hope everyone is at the start of a great week! Patrick -- Andreas J. Guelzow, PhD FTICA Registrar & Director of Enrolment Services Professor, Mathematical & Computing Sciences Direct: +1 780 479 9290 Toll-Free: +1 866 479 5200 concordia.ab.ca