|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
This document is an approved OASIS standard.
|
|
3.
|
Justification for the specific reference:
|
|
|
Normative reference.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
IPR issues on OASIS publications can be found at http://www.oasis-open.org/committees/wss/ipr.php.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
The technology described in this document is widely accepted in the market.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
The content of this standard has been stable since 2013 (see its Appendix B for details of revision history).
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
This document refers to publications of other standard bodies.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[ITU-T Y.4000] Recommendation ITU-T Y.4000/Y.2060 (2012), Overview of Internet of things./
[ISO 8601] ISO 8601:2004, Data elements and interchange formats – Information interchange - Representation of dates and times./
[OASIS OData Part 1] OASIS OData Version 4.0 (2016), Part 1: Protocol Plus Errata 03./
http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.html /
[OASIS OData Part 2] OASIS OData Version 4.0 (2016), Part 2: URL Conventions Plus Errata 03./
http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part2-url-conventions.html /
[OASIS OData JSON] OASIS OData Version 4.0 (2016), JSON Format Version 4.0 Plus Errata 03./
http://docs.oasis-open.org/odata/odata-json-format/v4.0/odata-json-format-v4.0.html /
[OASIS OData ABNF] OASIS OData Version 4.0 (2017), ABNF Construction Rules./
http://docs.oasis-open.org/odata/odata/v4.01/cs01/abnf/odata-abnf-construction-rules.txt /
[OGC/ISO 19156] OGC/ISO 19156 (2011), Abstract Specification Topic 20: Geographic information — Observations and Measurements./
http://portal.opengeospatial.org/files/?artifact_id=41579 /
[IETF RFC 2046] IETF RFC 2046, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types./
https://www.ietf.org/rfc/rfc2046.txt /
[IETF RFC 2616] IETF RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1. /
https://www.ietf.org/rfc/rfc2616.txt /
[IETF RFC 5789] IETF RFC 5789, PATCH Method for HTTP,/
https://www.ietf.org/rfc/rfc5789.txt /
[IETF RFC 6902] IETF RFC 6902, JavaScript Object Notation (JSON) Patch. /
https://www.ietf.org/rfc/rfc6902.txt /
[IETF RFC 7946] IETF RFC 7946, The GeoJSON Format. /
https://www.ietf.org/rfc/rfc7946.txt/
/
The following are non-normative references included for background and related material:/
[b-IETF RFC 5023] IETF RFC 5023, The Atom Publishing Protocol. /
https://www.ietf.org/rfc/rfc5023.txt/
[b-OGC 12-000] OGC 12-000, SensorML: Model and XML Encoding Standard./
http://www.opengeospatial.org/standards/sensorml /
[b-UCUM] UCUM (2017), Unified Code for Units of Measure, Version 2.1/
http://unitsofmeasure.org/trac/
|
|
9.
|
Qualification of
OASIS:
|
|
|
OASIS is recognized under the provisions of ITU-T Recommendations A.5 and A.4. Qualifying information is on file at TSB.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
