Notes from 21 March 2022

[Patrick Durusau <patrick@durusau.net>]

Greetings!

Notes from the ODF TC conference call, 21 March 2022, follow below.

News on the pandemic continues to be worrisome, take care of yourselves!

Patrick

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

*Patrick:*  Quorum - yes!

*Patrick:*  agenda - approved by consent

*Patrick:*  minutes 14 March 2022 - approved by consent

*Patrick:*  5. Office-3759

*Patrick:*  5. Office-3759

*Patrick:*  5. Office-3759

*Patrick:*  5. Office-3759

*Patrick:*  5. Office-3759

*Patrick:*  5. Office-3759

*Patrick:*  5. Office-3759

*Patrick:*  4. PAS - update Patrick will contact Jamie

*Patrick:*  <rng:define name="common-value-type-attlist">
    <rng:attribute name="office:value-type">
      <rng:ref name="valueType"/>
    </rng:attribute>
</rng:define>

*Patrick:*  current text in schema

*Patrick:*  <rng:define name="common-value-type-attlist">
<rng:choice>
<rng:group>
    <rng:attribute name="office:value-type">
      <rng:ref name="valueType"/>
</rng:attribute>
</rng:group>
<rng:group>
  <rng:attribute name="office:value-type">
          <rng:value>error</rng:value>
      </rng:attribute>
      <rng:optional>
        <rng:attribute name="office:string-value">
          <rng:ref name="string"/>
        </rng:attribute>
      </rng:optional>
    </rng:group>
    <rng:group>
      <rng:attribute name="office:value-type">
          <rng:value>string</rng:value>
      </rng:attribute>
      <rng:optional>
        <rng:attribute name="office:string-value">
          <rng:ref name="string"/>
        </rng:attribute>
      </rng:optional>
    </rng:group>
  </rng:choice>
</rng:define>

*Patrick:*  My reading of Regina's suggestion for the schema

*Patrick:*  See Regina's email for the correct representation of the change requested - sorry,

*Patrick:*  Regina's solution entered into the schema

*Patrick:*  https://issues.oasis-open.org/browse/OFFICE-3761

*Patrick:*  https://lists.oasis-open.org/archives/office/202203/msg00017.html

*Patrick:*  13 elements listed as changing for the solution to Office-3761

*Patrick:*  Regina - should have two parts - each element listed with issue number and section number - we need a second list which is a reverse mapping, from issue number the affected element and attribute is listed.

*Patrick:*  Regina - all elements should be listed as well

*Patrick:*  Francis - likes Regina's idea what links to include

*Patrick:*  Regina - currently have internal link to section and external to JIRA issue, should have both in new listing

*Patrick:*  Patrick - finish the first list - then generate the second list automatically -

*Patrick:*  Regina - need to do this for each draft - for tracking changes in text -

*Patrick:*  Francis agrees its useful for cross-checking

*Patrick:*  Patrick - task to work on the transformation for the second list

*Patrick:*  Francis says the XML is pretty consistent, so should be no problem

*Patrick:*  https://issues.oasis-open.org/browse/OFFICE-3816

*Regina Henschel:*  19.171 draw:formula
If $ (U +0024) precedes an integer value, the value is an index to a draw:modifiers 19.196 attribute. The corresponding modifier value is used as value.

*Regina Henschel:*  (U +0024, DOLLAR SIGN)

*Regina Henschel:*  19.145 draw:enhanced-path
An integer value preceded by a $ (U+0024, DOLLAR SIGN) character. Such a value is an index to a draw:modifiers 19.196 attribute on the element where the draw:enhanced-path attribute appears. The corresponding modifier value is used as a parameter value.

*Regina Henschel:*  (U+0024, DOLLAR SIGN)    no blank between U and +

*Patrick:*  Eliminate the space - Patrick - insert DOLLAR SIGN

*Patrick:*  Regina's question on description of graphics depicted in OOXML but not specified:

*Patrick:*  Regina - need a language with a description for camera -

*Patrick:*  Regina - Leland won't be useful - processing - how does it specify a file format

*Patrick:*  Regina - camera can be used with diagrams, photos, objects -

*Patrick:*  Regina - need a way to describe such a camera and do it in a way that it can be used in different places

*Patrick:*  Regina - most relevant is to use it on a shape and a group - group of shapes

*Patrick:*  So all shapes in the same group use the same camera

*Patrick:*  Regina - question isn't the camera per se but how to integrate it into our specification

*Patrick:*  Regina - if I have a container with a camera, how do I put it to a group?

*Patrick:*  How to describe the relationship between the camera and the group? That the group is to be viewed via the camera?

*Patrick:*  Regina - could describe camera as camera property - would need the group to extend to refer to such cameras - or new element camera - could make it child of the group ,  or make a reference in a group to id with camera element - finding a good solution to integrate the camera -

*Patrick:*  Regina - the camera itself should be understandable by other application - simple camera - viewpoint - distance - angle - possible to transfer one description to another.

*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