Re: ODF 1.3 CS02 candidate deliverables

[Paul Knight <paul.knight@oasis-open.org>]

Hi Svante and all,

It sounds like you are all ready to start the Committee specification approval process.

NOTE - the date shown on the documents should be the date of approval, that is, the date that the "special majority ballot" (see below) closes. That can be handled during publication.

The basic process for approving a Committee Specification is described in the TC Process document, at:

-Âhttps://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#committeeSpec

I think it's important to read that, if you haven't had a chanceÂto do it yet...

The key point is that OASIS TC Administration must start the special majority ballot for a CS (in this case, with non-material changes, I think).

The TC members need to approve requesting a ballot for a CS, so the TC should pass a motion for this. You should use the ballot language in the "TC Motion Ballot Language Templates" at:

-Âhttps://www.oasis-open.org/committees/download.php/53768Â -- see item (4).

(you can do this through email, or at a regular quorate meeting)

After the TC approves the request for a CS ballot, you will need to submit the ballot request form at:

-Âhttps://www.oasis-open.org/resources/tc-admin-requests/committee-note-ballot-request.

The form has a line to include the link to the comment log that Patrick assembled (which you cited in your email).

It also has a line to link to the minutes of the approval meeting.

I thinkÂthis is all you need to get the CS ballot started. After the ballot passes, we'll work with you to get it published, with the correct dates, etc.

Best regards,

Paul

On Mon, Oct 12, 2020 at 3:20 PM Svante Schubert <svante.schubert@gmail.com> wrote:

Hi Paul,

We did several iterations on the ZIP of our ODF CS02 deliverables:

https://www.oasis-open.org/committees/document.php?document_id=67826&wg_abbrev=office

Michael did a very good review on GitHub, finding several oversights of mine, and finally merged our pull request, which content represents our above ZIP of deliverables.

There is only one uncertainty about the date on the front-page. We assume the date is still our TC voting date the 30. August 2020, right?

Otherwise, I will fix this right away!

WhatÂare the next steps to CS02?

Patrick published the "Resolution of public comment log for OpenDocument-v1.3 cs03" on our mailing list.

Any further action requested from my side?

Regards,

Svante

Am Fr., 9. Okt. 2020 um 22:58ÂUhr schrieb Paul Knight <paul.knight@oasis-open.org>:

Hi Svante and all,

I checked over the notes on publication in the JIRA ticket (https://issues.oasis-open.org/browse/TCADMIN-3793), and verified that we did not make any changes to the ODT files after receiving them from the TC.

Svante did some great work to improve the HTML files during publication, and those HTML files were also published with justÂone change, from the ZIP archive loaded by Svante:

https://issues.oasis-open.org/secure/attachment/11724/11724_csd03-html.zip.

Change:

Part 1 - the three links to the TOC of other Parts are broken in the HTML format (became FQ links pointing to an Editor's system) Â

Fixed references to other Part TOCs from Part 1 TOC (used FQDN, and also set to link to the HTML format instead of ODT).

All other files (ODT, PDF, RNG, OWL, etc.) are from the original ZIP file, with one set of changes:
https://www.oasis-open.org/committees/download.php/67663/20-08-24-proposal00094

Change:

Fixed file names and internal documentation of names in /schemas directory (removed csd03 token)ÂÂ

So to summarize: there were no changes to the ODT files, and Svante has tracked the changes to the schema files. I think you have the latest/correct files in github!

Best regards,

Paul

On Fri, Oct 9, 2020 at 3:03 PM Svante Schubert <svante.schubert@gmail.com> wrote:

Dear TC members, Dear Paul,

I believe (again) that I have now done all the required changes in our GitHub Pull-Request:

https://github.com/oasis-tcs/odf-tc/pull/30ÂÂ

All files of deliverables are available as ZIP:

https://www.oasis-open.org/apps/org/workgroup/office/download.php/67823/cs02.zip

In addition, the HTML documents are viewable from my GitHub site:

1. https://svanteschubert.github.io/odf-tc/odf1.3/cs02/OpenDocument-v1.3-cs02-part1-introduction.html
2. https://svanteschubert.github.io/odf-tc/odf1.3/cs02/OpenDocument-v1.3-cs02-part2-packages.html
3. https://svanteschubert.github.io/odf-tc/odf1.3/cs02/OpenDocument-v1.3-cs02-part3-schema.html
4. https://svanteschubert.github.io/odf-tc/odf1.3/cs02/OpenDocument-v1.3-cs02-part4-formula.html

All files can be either be find in the deliverables directory:

https://github.com/svanteschubert/odf-tc/tree/master/docs/odf1.3/cs02

I have usedÂhttps://www.drlinkcheck.com/ to check for broken links in the above HTML (aside of the yet none existentÂdeliverable destination).

AndÂvalidated the ODT viaÂhttps://odfvalidator.org/ (and the latestÂvalidator versionÂlocal for the larger documents, as there was too much traffic)Â

Best regards,

Svante

@Paul: Sorry, I was quite cross-talking. I thought I had the latest version of all files on GitHub, but realized that you made changes to the schema files.

I have downloaded all your schema files and adjusted the IDs. As I can hardly do a DIFF on the ODT; did you changeÂanything within one of the ODT documents?Â

In case you did, we have to do this again, as I have started from the GitHub document set.

In the future, if you change something we have to overtake these files to GitHub. Still improving our process.. ;-)

--

Paul Knight....Document Process Analyst

OASIS - Advancing open standards for the information society

--

Paul Knight....Document Process Analyst

OASIS - Advancing open standards for the information society