diff --git a/docs/odata-json-format/odata-json-format.html b/docs/odata-json-format/odata-json-format.html index 39cd77bac..51ff69cd4 100644 --- a/docs/odata-json-format/odata-json-format.html +++ b/docs/odata-json-format/odata-json-format.html @@ -743,11 +743,7 @@

7.1

Values of type Edm.Binary, Edm.Date, Edm.DateTimeOffset, Edm.Duration, Edm.Guid, and Edm.TimeOfDay are represented as JSON strings whose content satisfies the rules binaryValue, dateValue, dateTimeOffsetValue, durationValue, guidValue, and timeOfDayValue respectively, in OData-ABNF.

Primitive values that cannot be represented, for example due to server conversion issues or IEEE754 limitations on the size of an Edm.Int64 or Edm.Decimal value, are annotated with the Core.ValueException term. In this case, the payload MAY include an approximation of the value and MAY specify a string representation of the exact value in the value property of the annotation.

Enumeration values are represented as JSON strings whose content satisfies the rule enumValue in OData-ABNF. The preferred representation is the enumerationMember. If no enumerationMember (or combination of named enumeration members) is available, the enumMemberValue representation may be used.

-

Geography and geometry values are represented as geometry types as defined in RFC7946, with the following modifications:

- +

Geography and geometry values are represented as geometry types as defined in RFC7946.

Geography and geometry types have the same representation in a JSON payload. Whether the value represents a geography type or geometry type is inferred from its usage or specified using the type control information.

Example 12:

@@ -2011,8 +2007,6 @@
[RFC8259]

A.2 Informative References

[ECMAScript]

ECMAScript 2023 Language Specification, 14th Edition, June 2023. Standard ECMA-262. https://www.ecma-international.org/publications-and-standards/standards/ecma-262/.

-
[GeoJSON-2008]
-

Butler, H., Daly, M., Doyle, A., Gillies, S., Schaub, T., and C. Schmidt, “The GeoJSON Format Specification”, June 2008 http://geojson.org/geojson-spec.html.

Appendix B. Safety, Security and Privacy Considerations

This specification raises no security issues.

diff --git a/docs/odata-json-format/odata-json-format.md b/docs/odata-json-format/odata-json-format.md index 4a71f489f..b0ee09d9d 100644 --- a/docs/odata-json-format/odata-json-format.md +++ b/docs/odata-json-format/odata-json-format.md @@ -1388,15 +1388,7 @@ combination of named enumeration members) is available, the `enumMemberValue` representation may be used. Geography and geometry values are represented as geometry types as -defined in [RFC7946](#rfc7946), with the following -modifications: - -- Keys SHOULD be ordered with type first, then coordinates, then any other keys -- If the optional [CRS - object](http://geojson.org/geojson-spec.html#named-crs) is present, it - MUST be of type `name`, where the value of the - `name` member of the contained `properties` object - is an EPSG SRID legacy identifier, see [[GeoJSON-2008](#GeoJSON-2008)]. +defined in [RFC7946](#rfc7946). Geography and geometry types have the same representation in a JSON payload. Whether the value represents a geography type or geometry type @@ -3780,10 +3772,6 @@ https://www.rfc-editor.org/info/rfc8259. ###### [ECMAScript] _ECMAScript 2023 Language Specification, 14th Edition_, June 2023. Standard ECMA-262. https://www.ecma-international.org/publications-and-standards/standards/ecma-262/. -###### [GeoJSON-2008] -_Butler, H., Daly, M., Doyle, A., Gillies, S., Schaub, T., and C. Schmidt, "The GeoJSON Format Specification", June 2008_ -http://geojson.org/geojson-spec.html. - ------- # Appendix B. Safety, Security and Privacy Considerations diff --git a/odata-json-format/7 Structural Property.md b/odata-json-format/7 Structural Property.md index b98aae8cf..d7b56f083 100644 --- a/odata-json-format/7 Structural Property.md +++ b/odata-json-format/7 Structural Property.md @@ -54,15 +54,7 @@ combination of named enumeration members) is available, the `enumMemberValue` representation may be used. Geography and geometry values are represented as geometry types as -defined in [RFC7946](#rfc7946), with the following -modifications: - -- Keys SHOULD be ordered with type first, then coordinates, then any other keys -- If the optional [CRS - object](http://geojson.org/geojson-spec.html#named-crs) is present, it - MUST be of type `name`, where the value of the - `name` member of the contained `properties` object - is an EPSG SRID legacy identifier, see [[GeoJSON-2008](#GeoJSON-2008)]. +defined in [RFC7946](#rfc7946). Geography and geometry types have the same representation in a JSON payload. Whether the value represents a geography type or geometry type diff --git a/odata-json-format/Appendix.md b/odata-json-format/Appendix.md index 6aea417d2..6d50ee3a9 100644 --- a/odata-json-format/Appendix.md +++ b/odata-json-format/Appendix.md @@ -80,10 +80,6 @@ https://www.rfc-editor.org/info/rfc8259. _ECMAScript 2023 Language Specification, 14th Edition_, June 2023. Standard ECMA-262. https://www.ecma-international.org/publications-and-standards/standards/ecma-262/. -###### [GeoJSON-2008] -_Butler, H., Daly, M., Doyle, A., Gillies, S., Schaub, T., and C. Schmidt, "The GeoJSON Format Specification", June 2008_ -http://geojson.org/geojson-spec.html. - ------- # Appendix ##asec Safety, Security and Privacy Considerations