[OASIS Issue Tracker] Updated: (ODATA-595) We should define some sort of "profile" to specify which GML elements/attributes are valid with ATOM Geo-types

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/ODATA-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-595:
-----------------------------

    Fix Version/s: V4.0_CSD03
                       (was: V4.0_OS)

> We should define some sort of "profile" to specify which GML elements/attributes are valid with ATOM Geo-types
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-595
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-595
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ATOM Format 
>    Affects Versions: V4.0_CS02
>            Reporter: Evan Ireland
>            Priority: Minor
>             Fix For: V4.0_CSD03
>
>
> In regard to OData's use of GML for Geo-types with ATOM format, it is not specified if clients/servers can or should:
> (1) Use gml:pos (in particular for a set of points, an array of gml:pos as opposed to using a single gml:posList)?
> (2) Use gml:posList?
> (3) Use gml:coordinates (which is a deprecated GML element)?
> Also, there is no mention in OData of whether the GML srcDimension attribute should or must be indicated. When we are parsing a gml:posList, without knowing the dimension, it is next to impossible (without having a full database of SRID's to refer to) to separate the points, unless we assume only 2D systems.

-- 
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