OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Notes from 24 April 2023 ODF TC Teleconference


Greetings!

Notes from the ODF TC Teleconference, 24 April 2023, follow below.

Hope everyone is at the start of a great week!

Patrick

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

*Patrick:*  Quorum - yes

*Patrick:*  Regina - begin color transformation discussion

*Patrick:*  Patrick - update on ODF 1.3 to ISO

*Patrick:*  with those additions - agenda approved by consent

*Patrick:*  minutes of 17 April 2023 - approved by consent

*Patrick:*  4. FYI - May holidays - 15 May 2023

*Patrick:*  ISO update - Jamie to complete this week

*Patrick:*  Regina- color transformation -

*Patrick:*  Additional topic "color transformation" for today:

There is ongoing development for providing color transformations in LibreOffice. Such color transformation allows to vary a base color in a lot of ways, e.g make it darker, semi-transparent, decrease saturation, ...

Such color transformation needs an attribute for the kind of transformation and an attribute for the quantity. Only considering import from OOXML there will be about 28 transformation types.

How would you specify it?

My idea is to use an element, because the result depends on the order transformations are applied.
I thought of making the type a namespaced token and the amount as string (effectively an any).
I think of adding it as implementation-defined.
If not using "implementation-defined" the data type of the quantity depends on the type of color transformation.

"implementation-defined" or not is the same amount of work for me. I would have to do it for LibreOffice or for ODF. But using "implementation-defined" removes the duty for the ODF to maintain it, and it allows to first only specify those transformations which are actually implemented and add further ones without the need to change ODF.

*Patrick:*  Regina - do we say that non-supported elements should be retained and serialized out when saved? - Patrick doesn't remember but suspects not

*Regina Henschel:*  OOXML 20.1.2.3 Colors

*Patrick:*  Regina will work out formulas for the standard

*Patrick:*  Status of drafts - May 15th.

*Patrick:*  Freeze - elements are clear - Appendix E - needs to be finished

*Patrick:*  Regina - list of things that change, even if not in a draft -

*Patrick:*  Francis - spreadsheet on complete list of issues -

*Patrick:*  adjourned


--
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: OpenPGP_signature
Description: OpenPGP digital signature



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]