In my opinion the standard does not have to say anything about an empty string, because the Constraints section says that X âshall contain at least one binary digitâ. If the document is a conforming document, X will not be empty. If one goes down the path of defining how consumers should process non-conforming documents, that way madness lies, in my opinion. The spec should only specify how to handle conforming documents. All bets are off otherwise.
The alternative is to change the constraints to allow X to be an empty string, in which case it then makes sense to say how this should be handled.
Francis
From: office@lists.oasis-open.org <office@lists.oasis-open.org> On Behalf Of Patrick Durusau
Sent: 31 October 2020 19:03
To: andreas.guelzow <andreas.guelzow@concordia.ab.ca>; ODF TC List <office@lists.oasis-open.org>
Subject: Re: [office] Question on implementation-defined - part 4 - formulas
Thanks!
It seems like awkward wording but off-hand I don't know of a better suggestion. Will think about it.
Hope you are having a great weekend!
Patrick
On 10/31/20 2:57 PM, andreas.guelzow wrote:
The intention is that there are 2 possible values and the implementation should decide and define which of these two values will be returned.
Sent from my Samsung Galaxy smartphone.
-------- Original message --------
Date: 2020-10-31 12:12 (GMT-07:00)
Subject: [office] Question on implementation-defined - part 4 - formulas
Greetings!
I'm compiling a spreadsheet of all instances of
implementation-defined/dependent and ran into an odd case in part 4:
6.19.4 BIN2DEC
...
If any digits are 2 through 9, an evaluator shall return an Error. It is
implementation-defined what happens if an evaluator is given an empty
string; evaluators may return an Error or 0 in such cases.
*****
Notice that we say "implementation-defined," but then immediately follow
with: *may* return an Error or 0 in such cases.
If we mean, "implemention-defined," isn't that all we should say and stop?
Or, are we using "implementation-defined" in a common sense and then
specifying with "may," the possible options to return?
This happens more than once in part 4.
Before I create a lot of needless JIRA issues, wanted to check with the TC.
Thanks!
Hope everyone is having a great weekend!
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
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
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