OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (OFFICE-3444) 18.3.9 coordinateshould not be a tuple

    [ http://tools.oasis-open.org/issues/browse/OFFICE-3444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21775#action_21775 ] 

Dennis Hamilton commented on OFFICE-3444:

I share the concern that Andreas has about this.

The most direct statement is the second part of Michael's suggestion: "The coordinate value specifies the distance from the origin of the coordinate system along the relevant axis."

For this to work, we need to know the origin and the orientation of the coordinate system.  We may also need to know its units in physical measures, if that is actually permitted for a given case.   (Speaking generally, it might not be for a coordinate system that lives in an embedded frame and has a transform-defined relationship to its parent system.)

Note that the SVG grammar might not prevent signed numbers (?) and the "%" option allows frame-relative coordinates.  It is also not necessary to specify fixed-size units (so presumably the framing coordinate system is applicable) and it is not clear when physical units are applicable, depending on the prevaling coordinate system (which might only be grounded on fixed units as part of a transform relative to an enclosing coordinate system).

So not all of the lexically-approved forms may provide nominally-meaningful values in individual cases, and that is a factor that is only resolveable by having more precise information about the prevaling coordinate system and the nature of its unit measures, orientation, and constraining frame in every case.

Regardless, I agree that these should not be called lenghts, they are (relative) distances of a point projected onto its respective axes.  If there was a line from the origin to the coordinate-defined  position, that line would have a length but is unlikely to be the same as one of the coordinate values (unless all of the other coordinates are 0).

> 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, Needs Discussion
>    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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]