Chat log for Feb 20, 2017

[Patrick Durusau <patrick@durusau.net>]

Greetings!

The ODF chat log for our Feb. 20, 2017 teleconference:

Andras Timar 2: Hi All!
Patrick: Hi!
Patrick: Is there something wrong with Skype? I can't hear your
responses to the roll call. Can you hear me?
Michael Stahl: i can't hear anything
Andras Timar 2: We can't hear you Patrick
Patrick: Let me dial in again with the admin password
anonymous morphed into Jos van den Oever
anonymous morphed into Thorsten
Thorsten had some trouble with the conf room today, too -
Patrick: OK I will try again
Jos van den Oever: @Patrick: are you still in the call albeit without
audio or cant you dial in?
Patrick: Ok, this should work
Patrick: <element name="text:hidden-paragraph">
<ref name="text-hidden-paragraph-attlist"/>
<text/>
</element>
Jos van den Oever: that's good news! easy fix and no known implementers
that do it wrong so no fallout
Patrick: Open separate issue on schema model for hidden-paragraphs and
check other entries.
Michael Stahl: https://issues.oasis-open.org/browse/OFFICE-2093
Jos van den Oever: http://example.com/data.csv#cell=4,1-6,2
Jos van den Oever: https://tools.ietf.org/html/rfc7111
Jos van den Oever: soffice 'file.ods#text|searchterm'   does not work ...
Svante Schubert: text:name is of type string
Svante Schubert: xml:id is of type ID
Svante Schubert: We should be careful when allowing text:name due to
encoding problems as part of the frament identifier and its multiple
usages (first might be taken)
Patrick: consumer requirements - shall would be inappropriate (Michael)
perhaps a should?
Patrick: Michael, no reason to limit to text documents -
Svante Schubert: mypresention.odp#1
Svante Schubert: similar something for spreadsheets and cells & cell-ranges
Michael Stahl: i think it's mypresentation.odp#page1 in OOo/LO
Svante Schubert: I will come up with a suggestion for presentation and
spreadsheet shortcuts - convention over configuration - to ease usage
Svante Schubert: NCName is https://www.w3.org/TR/xml-names11/#NT-NCName
Patrick: The practical restrictions of NCName are that it cannot contain
several symbol characters like :, @, $, %, &, /, +, ,, ;, whitespace
characters or different parenthesis. Furthermore an NCName cannot begin
with a number, dot or minus character although they can appear later in
an NCName.
Patrick: Svante and Michael will add to the issue and we will return to
it next week

Hope everyone is at the start of a great week!

Patrick


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