Part 2: URL Conventions Committee Specification 01 30 January 2018 Specification URIs This version: Authoritative Previous version: Authoritative Latest version: Authoritative Technical Committee: Chairs: Ralf Handl , Michael Pizzo , Editors: Michael Pizzo , Ralf Handl , Martin Zurmuehl , : This prose specification is one component of a Work Product that also includes: · OData Version 4. · OData Version 4. Part 2: URL Conventions this document. · ABNF components: OData ABNF Construction Rules Version 4. Edited by Michael Pizzo, Ralf Handl, and Martin Zurmuehl. This specification is related to: · OData Vocabularies Version 4. Edited by Michael Pizzo, Ralf Handl, and Ram Jeyaraman. · OData Common Schema Definition Language CSDL JSON Representation Version 4. Edited by Michael Pizzo, Ralf Handl, and Martin Zurmuehl. · OData Common Schema Definition Language CSDL XML Representation Version 4. Edited by Michael Pizzo, Ralf Handl, and Martin Zurmuehl. · OData JSON Format Version 4. Edited by Ralf Handl, Michael Pizzo, and Mark Biamonte. · OData Extension for Data Aggregation Version 4. Edited by Ralf Handl, Hubert Heijkers, Gerald Krause, Michael Pizzo, and Martin Zurmuehl. Abstract: The Open Data Protocol OData enables the creation of REST-based data services, which allow resources, identified using Uniform Resource Locators URLs and defined in a data model, to be published and edited by Web clients using simple HTTP messages. This specification defines a set of recommended but not required rules for constructing URLs to identify the data and metadata exposed by an OData service as well as a set of reserved URL query string operators. Status: This document was last revised or approved by the OASIS Open Data Protocol OData TC on the above date. The level of approval is also listed above. Any other numbered Versions and other technical work produced by the Technical Committee TC are listed at. Note that any machine-readable content declared Normative for this Work Product is provided in separate plain text files. In the event of a discrepancy between any such plain text file and display content in the Work Product's prose narrative document s , the content in the separate plain text file prevails. Part 2: URL Conventions. Edited by Michael Pizzo, Ralf Handl, and Martin Zurmuehl. Notices Copyright © OASIS Open 2018. The full may be found at the OASIS website. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns. OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so. OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see for above guidance. The Open Data Protocol OData enables the creation of REST-based data services, which allow resources, identified using Uniform Resource Locators URLs and defined in a data model, to be published and edited by Web clients using simple HTTP messages. This specification defines a set of recommended but not required rules for constructing URLs to identify the data and metadata exposed by an OData service as well as a set of reserved URL query string operators, which if accepted by an OData service, MUST be implemented as required by this document. The document specifies the format of the resource representations that are exchanged using OData and the document describes the actions that can be performed on the URLs optionally constructed following the conventions defined in this document embedded in those representations. Services are encouraged to follow the URL cons
