[ http://tools.oasis-open.org/issues/browse/OFFICE-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21430#action_21430 ]
Patrick Durusau commented on OFFICE-3444:
-----------------------------------------
Well, a tuple can have a single value, in which case it is called a singleton. So a tuple would cover both a single value as well as multiple values, such as for geographic coordinates or even 3 (or higher) dimension coordinates.
That isn't captured other than vaguely by "numeric value."
BTW, "numeric value" does not specify a type of numeric value.
(Neither did my suggestion of tuple but I was trying to say no more than the current text.)
Two questions:
1) Should we use tuple?
2) If yes or no, what about the "type" of the value?
> 18.3.9 coordinate should not be a tuple
> ---------------------------------------
>
> Key: OFFICE-3444
> URL: http://tools.oasis-open.org/issues/browse/OFFICE-3444
> Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
> Issue Type: Bug
> Components: Graphics
> Affects Versions: ODF 1.2 CD 05
> Reporter: Andreas Guelzow
> Assignee: Patrick Durusau
> Priority: Blocker
> Fix For: ODF 1.2 CD 06
>
>
> 18.3.9 has been changed from "Like a length, except that the physical length denotes a certain point." to "A tuple of numeric values that defines a position."
> I don't think it makes sense to have a coordinate to be "a tuple". Shouldn't it just be a "A numeric value that describes a position"?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
