-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: V4.0_WD01
-
Fix Version/s: V4.0_WD01
-
Component/s: ATOM Format, JSON Format
-
Labels:None
-
Environment:
[Applied]
-
Proposal:
-
Resolution:
Right now we use a common literal format based on "Well Known Text" for literals within URLs, serializing in ATOM, and serializing in JSON.
Well-known-text defines a convenient format for URLs, yowever, both Atom and JSON have "native" representations of geo types. The most natural representation in ATOM is the xml representation GML. GeoJSON appears to be the most broadly accepted way to encode geo types in JSON. It works very well in JSON.
It would be unfortunate to force consumers in XML or JSON to have to understand formats that are not common in each environment, and unfortunate to have extra brackets or curly braces in URLs
| Field | Original Value | New Value |
|---|---|---|
| Environment | [Proposed | [Resolved] |
| Status | New [ 10000 ] | Open [ 1 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Component/s | OData ATOM Format [ 10271 ] | |
| Environment | [Resolved] | [Applied to JSON] |
| Summary | Use GeoJSON to format geo types in JSON | Use GeoJSON in JSON and GML in Atom to represent geo types |
| Environment | [Applied to JSON] | [Applied] |
| Resolution |
https://www.oasis-open.org/committees/document.php?document_id=48966&wg_abbrev=odata https://www.oasis-open.org/committees/document.php?document_id=48965&wg_abbrev=odata |
|
| Status | Resolved [ 5 ] | Applied [ 10002 ] |