Meeting notes from 18 Dec 2017

[Jos van den Oever <Jos.Oever@koop.overheid.nl>]

Agenda
------

1. Dial-In, Roll Call, Determination of Quorum and Voting Rights

2. Motion (simple majority): Approve the Agenda

3. Motion (simple majority): Notice of minutes from prior TC calls - pending

4. Meeting time for 2017-12-11 - 
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=12&day=18&hour=17&min=0&sec=0&p1=25&p2=37

5. Issues for Dec. 18, 2017:

a. https://issues.oasis-open.org/browse/OFFICE-3901 Non-normative text
to illustrate the use of RDF to include DC metadata

b. https://issues.oasis-open.org/browse/OFFICE-3900  OFFICE-3900 Rework
usage of SVG keywords to avoid redefinition

c. https://issues.oasis-open.org/browse/OFFICE-3899  OFFICE-3899 Rework
usage of SVG namespace usages of NCNames to conform with SVG requirements

d. https://issues.oasis-open.org/browse/OFFICE-3898  OFFICE-3898
Reference SVG 1.1 and SVG Tiny 1.2 as mandated formats for ODF-1.3

e. https://issues.oasis-open.org/browse/OFFICE-3897  OFFICE-3897 Extract
ODF-only features missing from SVG, liaise with W3C about that

f. https://issues.oasis-open.org/browse/OFFICE-3896  OFFICE-3896 Require
svg support for linked and inline images


6. Next meeting: 2018-01-08.

7.  Adjournment

Jos van den Oever: Remarks on the agenda. Michael would like to add a 
remark about the ForcedArray issue: Eike is not happy about our 
resultion and would like to have this discussed a subsequent meeting.

Regina Henschel: https://issues.oasis-open.org/browse/OFFICE-3943

Jos van den Oever: Regina suggests a short issue to start with ^

Jos van den Oever: agenda approved, on the issue proposed by regina

Jos van den Oever: Jos: In case of a flat ODF, there is no mimetype when 
the image is base64 encoded.

Jos van den Oever: Jos: perhaps it's better to put the mimetype on 
<office:binary-data>

Jos van den Oever: (Thomas O'Reilly joined)

Jos van den Oever: Regina: when you have an SVG graphic, there is no 
<office:binary-data>, but <svg:svg>

Jos van den Oever: Michael: in current LO, the svg is written as binary-data

Jos van den Oever: Regina: I'll discuss this suggestion with the developer

Jos van den Oever: next: a. 
https://issues.oasis-open.org/browse/OFFICE-3901 Non-normative text
to illustrate the use of RDF to include DC metadata

Jos van den Oever: This issues is waiting for Jos to write a 
non-normative text about use of Dublin Core.

Jos van den Oever: Michael suggests to reassign to Tom O'Reilly. Tom agrees.

Jos van den Oever: Use of DC that's not in the standard currently would 
require RDF syntax.

Jos van den Oever: b. https://issues.oasis-open.org/browse/OFFICE-3900 
OFFICE-3900 Rework
usage of SVG keywords to avoid redefinition

Jos van den Oever: Thorsten: not enthousiastic because it's not 
backwards compatible.

Jos van den Oever: Michael agrees.

Jos van den Oever: Thorsten: is standards purity vs pain on implementors 
is worth it. For 1.3 this is rejected on grounds of incompatibility.

Jos van den Oever: Regina: I've sent a mail as a response to these issues.

Jos van den Oever: Regina: in some client-side image maps the 
relationship between bounding-box and svg-height and svg-width

Jos van den Oever: is not clear

Jos van den Oever: 
https://lists.oasis-open.org/archives/office/201712/msg00016.html is the 
mail with the document that discusses 3900

Jos van den Oever: Jos: we can have the issue discussion underneath the 
issue and you can still link to the mail with attachment there

Jos van den Oever: Jos: the first issue in the linked document is 
related to OFFICE-3943 which we've deferred to the next meeting

Jos van den Oever: That's the improvements to 9.3.2

Jos van den Oever: The rest of the documen pertains to OFFICE-3896.

Jos van den Oever: about places to allow inline svg

Jos van den Oever: e.g. for charts

Jos van den Oever: d. https://issues.oasis-open.org/browse/OFFICE-3898 
OFFICE-3898
Reference SVG 1.1 and SVG Tiny 1.2 as mandated formats for ODF-1.3

Jos van den Oever: this is not addressed in the document so we can have 
a discussion about that now

Jos van den Oever: currently we link to 
https://www.w3.org/TR/2003/REC-SVG11-20030114/ but not to svg Tiny 1.2

Jos van den Oever: (https://www.w3.org/TR/SVGTiny12/)

Jos van den Oever: Regina: in a regular image you can have any SVG you like

Jos van den Oever: Regina: we cannot replace <draw:*> elements with svg, 
because draw has text supports but svg does not

Jos van den Oever: SVG 1.1 is still that latest recommendation

Jos van den Oever: if svg tiny 1.2 is a subset of svg 1.1, then we do 
not need to do anything

Jos van den Oever: except perhaps mention that it is also ok to use svg 
1.2 tiny

Jos van den Oever: Regina: SVG 1.2 tiny has new features so adding that 
to the specification would add more features to odf 1.3

Jos van den Oever: Since any file format is allowed, would it make sense 
to explicitly mention svg tiny 1.2?

Jos van den Oever: Jos: what are the new features in tiny 1.2?

Jos van den Oever: Regina: the new features are not explicitly 
meantioned in the recommendation

Jos van den Oever: Jos: there is no mention of it in the change history.

Jos van den Oever: Jos: I'll try to find a list of new features that are 
in 1.2 so we can decide

Jos van den Oever: Next meeting will 2018.