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: ODF TC Teleconference notes from 24 Feb. 2020


Notes from the ODF TC teleconference, 24 Feb. 2020 are below.

Hope everyone is at the start of a great week!



Please change your name from 'anonymous' using the Settings button
anonymous morphed into Patrick
Patrick: quorum yes!
Patrick: 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 10 February 2020 (below)

4. Pending Issues for ODF 1.3 - Neither Approved nor Applied - Move to ODF 1.3 errata? Whitespace between FunctionName and opening parentheses of parameter list https://issues.oasis-open.org/browse/OFFICE-3667 - Listed for ODF 1.3 Errata under https://issues.oasis-open.org/browse/OFFICE-4069

5. Draft submission for database mime type (below)

6. ODF Later issues (Preference to current TC members and cycling through their issues so no one is on the spot for all of them in a meeting), btw, limiting the search to open/deferred issues counts 134: https://issues.oasis-open.org/issues/?jql=project%20%3D%20OFFICE%20AND%20status%20in%20(Open%2C%20Deferred)%20AND%20fixVersion%20in%20(%22ODF%201.4%22%2C%20ODF-Next)%20ORDER%20BY%20reporter%20ASC )

a. draw:type and draw:engine interaction - https://issues.oasis-open.org/browse/OFFICE-3772 reporter: Andreas Guelzow

b. style:writing-mode attribute (on elements sections) - confused wording https://issues.oasis-open.org/browse/OFFICE-3792 reporter: Patrick Durusau

c. How to calculate the start and end point of an elliptical arc from given angles https://issues.oasis-open.org/browse/OFFICE-3825 reporter: Regina Henschel

d. Inability to recognize errors - https://issues.oasis-open.org/browse/OFFICE-3759 reporter: Andreas Guelzow

e. style:writing-mode (attribute) includes value: tb-lr - undefined in xsl 1.0 - https://issues.oasis-open.org/browse/OFFICE-3791 reporter: Patrick Durusau

f. Which coordinate system is used in draw:enhanced-geometry, when svg:viewBox is missing - https://issues.oasis-open.org/browse/OFFICE-3824 reporter: Regina Henschel

7. Adjournment
Patrick: Agenda changes or additions - none - approved consent
Patrick: Minutes from 10 February 2020 - changes or additions - approved by consent
Patrick: Draft on mime - Libre Office uses it
Patrick: Open Office too
Regina Henschel: Apache OpenOffice
Patrick: thanks
Michael Stahl: ODFDOM
Patrick: ok
Patrick: fragment identification - https://tools.ietf.org/html/rfc6838
Patrick: see section 4.11
Patrick: 4.11.  Fragment Identifier Requirements

   Media type registrations can specify how applications should
   interpret fragment identifiers (specified in Section 3.5 of
   [RFC3986]) associated with the media type.

Freed, et al.             Best Current Practice                [Page 18]

RFC 6838                 Media Type Registration            January 2013

   Media types are encouraged to adopt fragment identifier schemes that
   are used with semantically similar media types.  In particular, media
   types that use a named structured syntax with a registered "+suffix"
   MUST follow whatever fragment identifier rules are given in the
   structured syntax suffix registration.
Patrick: https://tools.ietf.org/html/rfc3986#section-3.5
Patrick: The fragment identifier component of a URI allows indirect
   identification of a secondary resource by reference to a primary
   resource and additional identifying information.
Patrick: Leave fragment identifier out - by consent
Patrick: 4.9.  Usage and Implementation Non-Requirements
Patrick: Therefore, universal support and implementation of a media type are
   NOT a requirement for registration.  However, if a media type is

Freed, et al.             Best Current Practice                [Page 17]

RFC 6838                 Media Type Registration            January 2013

   explicitly intended for limited use, this MUST be noted in its
   registration.  The "Restrictions on Usage" field is provided for this
Patrick: Leave restrictions blank - by consent
Patrick: https://issues.oasis-open.org/browse/OFFICE-3667
Patrick: https://issues.oasis-open.org/browse/OFFICE-4069
Patrick: Do we all agree to Regina's resolution:

Is this the correction desired for ODF 1.3 Errata:

_expression_ ::=
Whitespace* (
Number |
String |
Array |
PrefixOp _expression_ |
_expression_ PostfixOp |
_expression_ InfixOp _expression_ |
'(' _expression_ ')' |
FunctionName '(' ParameterList ')' |

Patrick: Michael, any implementation that produce whitespace between function name and parameters?
Patrick: Regina - text in 1.2 already has the correct rule - Michael asks if anyone missed that part
Patrick: Andreas - checking interoperability would have been caught this issue between EBNF and text pretty safe bet to say no space between function name and parameters
Patrick: set issue to resolved - by consent
Patrick: https://issues.oasis-open.org/browse/OFFICE-3772
Patrick: LO doesn't use draw engine - it is preserved - if present in the document
Patrick: Regina speaking about LO
Patrick: Regina - LO uses draw type to distinguish from different sources
Patrick: Regina - when import a file - powerpoint give different text in draw type
Regina Henschel: draw:type="forbidden"
Regina Henschel: draw:type="ooxml-actionButton"
Regina Henschel: draw:type="non-primitive"
Patrick: Andreas - if no engine specified, how do we interoperate?
Patrick: Andreas - if specify engine names - by agreement or at least namespaces to seperate one non-primitive from another
Patrick: <draw:enhanced-geometry>
Patrick: yes to Michael but we don't ever give a place to specify the engine, only an engine's name for a shape.
Patrick: Change the note from shape type to draw type?
Patrick: Michael - need a concrete example of something that doesn't work
Patrick: Andreas will try to construct something for next time. -
Patrick: adjourned -

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

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