Re: [office] Agenda for ODF TC teleconference 29 June 2020

Patrick,

Am Mo., 29. Juni 2020 um 16:03ÂUhr schrieb Patrick Durusau <patrick@durusau.net>:

Svante,

I agree with adding Regina's statement of use, perhaps before the other issues?

Yes.Â

As far as your #9:

ODT2XHTML XSL transformation that had been used for ODF 1.2

DefaultValueExtractor XSL transformation that had been used for ODF 1.2

An ODF 1.2 Formular testing spreadsheet from 14 years ago, which might need some further inspection, but Regina already volunteered to take a lookÃat it.

What do you mean by "DefaultValueExtractor?" that did what?

In ODF 1.2 we removed the XML default values from the RelaxNG grammar, AFAIR as XML parser/validators use to insert those defaults back into the XML and blowing up the content.

To be able to have still programmatic easy access to those values, we annotated them in our ODF 1.2 specification by certain template character styles, called "Default Value".

This character style got lost on its way to ODF 1.2.

The XSLT script I mentioned searches for that template style and if found, gathers information about the attribute and element the default value is specifiedÂand returns this data.

You can find the XSLT script in the ODF Toolkit XSLT-Runner (which allows executing XSLT on the zipped ODT document), see

https://github.com/tdf/odftoolkit/blob/1.0.0_SNAPSHOT/xslt-runner/src/test/resources/xslt/getAttributeDefaults.xslÂ

We have 373 default values in ODF, I have listed those values for code generation purposes here, starting from line 218:

https://github.com/tdf/odftoolkit/blob/1.0.0_SNAPSHOT/odfdom/src/codegen/resources/config.xml#L218ÂÂ

A good reason to be able to extract those values is to be certain that our human-readable and machine-readable specification is in synch.

In the future, it is likely that the human-readable part is generated from the machine-readable part to have the specification as the blueprint of software back aligned in modern CI/CD processes.

"Patrick, you might have some generator for the grey boxes of schema description in the specification.Ã Anyone who also some tooling should mention it and upload it either to a new directory"

Thanks to Francis Cave we have a new script that was used on ODF 1.3 to extract the schema information for the grey boxes. - Can upload.

Great!Â

Anything else?

My uncertainty was the reason to put this topic on the agenda.

We can switch them at the TC's pleasure but let's have specific items in mind.

Sure!Â

Hope you are at the start of a great week!

Igualmente, let's talk soon!

SvanteÂ

Patrick

On 6/29/20 5:55 AM, Svante Schubert wrote:

Hello Patrick,

I would rather prefer to talk about the shorter, more limited topics at the beginning of the meeting.

Therefore it seems more appropriate to switch the order from #9 to #4.

At the beginningÂof these topics, let's start with Regina's "statement of use" proposal:

https://lists.oasis-open.org/archives/office/202006/msg00034.htmlÂÂ

Best regards,

Svante

Am Mo., 29. Juni 2020 um 03:20ÂUhr schrieb Patrick Durusau <patrick@durusau.net>:

Greetings!

Below you find a draft agenda for our TC call on Monday, 2020-06-29

Time of meeting: https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=6&day=29&hour=16&min=0&sec=0&p1=25&p2=37

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 712 770 5505

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): Approve minutes of 22 June 2020 https://www.oasis-open.org/apps/org/workgroup/office/email/archives/202006/msg00033.html

4. OFFICE-4073 Page-content-bottom vertical relation https://issues.oasis-open.org/browse/OFFICE-4073

5. (new) Be more precise about the values 'text', 'char' and 'line' in style:vertical-rel https://issues.oasis-open.org/browse/OFFICE-4076

6. (new) Not clear, to which elements attributes vertical-rel and vertical-pos can be applied https://issues.oasis-open.org/browse/OFFICE-4077

7. (new) The technical term "baseline" is not defined. https://issues.oasis-open.org/browse/OFFICE-4078

8. Svante's manifest corruption email (not an easy topic) https://www.oasis-open.org/apps/org/workgroup/office/email/archives/202006/msg00037.html (I will try to summarize what I have already said about options before the meeting, it's not complicated but then it isn't straight forward either.)

9. Github access/artifacts - https://www.oasis-open.org/apps/org/workgroup/office/email/archives/202006/msg00038.html BTW, maintainers take on additional responsibilities and so I have NOT requested everyone be added as a maintainer. Should anyone else wish to be a maintainer, please post to the office list.

10. Other business?

11. Adjournment.

Hope everyone is at the start of a great week!

Patrick

5. )

--
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
-- 
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 

office message