Greetings!
The chat log for the ODF teleconference, 8 July 2019 is attached.
Hope everyone is at the start of a great week!
Patrick
******* chat log ********
anonymous morphed into Alfred Hellstern
Please change your name from 'anonymous' using the Settings button
anonymous morphed into Patrick
Patrick: Wording:
https://issues.oasis-open.org/browse/OFFICE-4042
part 4, 6.15.8 OR: typo "shall returns"
Proposal: "if any are TRUE, it shall return TRUE."
Patrick: Agree present wording wrong, but suggest: "if any are TRUE, it returns TRUE." (defining a function states the result, shall is unnecessary)
Substantive:
https://issues.oasis-open.org/browse/OFFICE-3903 [Michael and Regina]
Text 6.18.30 FTEST, ODF1.2 part 2 needs improvements
Use updated proposal here: https://lists.oasis-open.org/archives/office/201809/msg00014.html
https://issues.oasis-open.org/browse/OFFICE-3867
related to: https://issues.oasis-open.org/browse/OFFICE-3708 and https://issues.oasis-open.org/browse/OFFICE-3702
Incorrect URL for XMLDsig - support both but produce only the correct one going forward?
Bad Directory Link:
[Regina] in ODF1.3 part3, section D4 'Further Guidelines' is the text:
"Additional, non-normative Accessibility Guidelines are available at: http://docs.oasis-open.org/office/office-accessibility/guidelines. That more comprehensive document will be the up-to-date set of recommendations for what all OpenDocument applications should do in order to fully support accessibility."
The mentioned directory "guidelines" does not exists, but the current structure is
http://docs.oasis-open.org/office/office-accessibility/
v1.0/
ODF_Accessibility_Guidelines-v1.0.html
ODF_Accessibility_Guidelines-v1.0.odt
ODF_Accessibility_Guidelines-v1.0.pdf
cd01/
cd02/
cs01/
My suggestion is, to add the directory "guidelines" and move the three current files into it, and keep directory v1.0 with the three subdirectories.
That way, in case these documents are updated, the links in the specification need not be changed. I think, that is better than changing the links in the specification to the current structure.
[/Regina]
Typos:
https://issues.oasis-open.org/browse/OFFICE-4044
duplicate "than"
https://issues.oasis-open.org/browse/OFFICE-3871
mis-placed "/?
https://issues.oasis-open.org/browse/OFFICE-3868
update mime type reference in text
https://issues.oasis-open.org/browse/OFFICE-4043
remove references to non-existing part5
Status update:
https://issues.oasis-open.org/browse/OFFICE-3667
Michael and Regina note applied in text but status not updated. wd-10-08-part4
Michael notes:
https://issues.oasis-open.org/browse/OFFICE-3428 and https://issues.oasis-open.org/browse/OFFICE-3034 have status "applied" when they should either say ODF-Later or close.
Open:
https://issues.oasis-open.org/browse/OFFICE-3940
Patrick: Agenda amended - no objection -
Patrick: part 4, 6.15.8 OR: typo "shall returns"
Proposal: "if any are TRUE, it shall return TRUE."
Patrick: Agree present wording wrong, but suggest: "if any are TRUE, it returns TRUE." (defining a function states the result, shall is unnecessary)
Andreas J Guelzow: "if any are TRUE, it shall return TRUE()."
Patrick: Andreas: 4.5 says true and false but doesn't say what they are - distinct from 4.3.7 where it is a subtype of number
Patrick: As a textual matter, is the suggest we define TRUE (uppercase) as equivalent to TRUE()?
Patrick: But if so, doesn't that require support of booleans as a subtype of number?
Patrick: Reading the current text of 4.5 as:
A Logical value (also called a Boolean value) is a value with one of two values: TRUE and FALSE.
Note: Logical values can be represented as a subtype of Number. 4.3.7
Patrick: Michael says to use TRUE() which will be correct however it may be implemented
Patrick: A Logical value (also called a Boolean value) is a value with one of two values: TRUE() and FALSE().
Patrick: define constants in chapter 4 for True and False -
Patrick: Andreas - if a number, true is a synonym for 1 and false is a synonym for 0
Patrick: then the semantics in 6.15.9 goes away because in 4 - new subsection
Patrick: Returns logical constant FALSE. This may be a Number or a distinct type.
Patrick: Michael says to keep the false semantics
Patrick: as a helpful reminder
Patrick: Does 4.5 become Boolean? no logical or number
Patrick: Andreas - will do a proposal to reword 4.5 - 4.3.7 will refer to 4.5 for all the details. - will need to sweep the standard for consistency with the proposal
Patrick: Patrick - to use the proposal in the email link.
Regina Henschel: 4.8.6 manifest:start-key-generation-name
Patrick: Michael, list correct and accept either?
Patrick: Pat to generate the missing text for next week.
--
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