![]() ![]() OData services are encouraged to follow the URL path construction rules (in addition to the required query string rules) as such consistency promotes a rich ecosystem of reusable client components and libraries. The resource path construction rules defined in this section are optional. The service document is required to be returned from the root of an OData service to provide clients with a simple mechanism to enumerate all of the collections of resources available for the data service. OData: JSON Format specifies such an alternate JSON-based representation of a service document. The resource identified by this URL MUST be an AtomPub Service Document (as specified in ) and follow the OData conventions for AtomPub Service Documents (or an alternate representation of an Atom Service Document if a different format is requested). The service root URL identifies the root of an OData service. Service root URL resource path query options The following are two example URLs broken down into their component parts: Additional URL constructs (such as a fragment) MAY be present in a URL used by an OData service however, this specification applies no further meaning to such additional constructs. URL ComponentsĪ URL used by an OData service has at most three significant parts: the service root URL, resource path and query options. Servers are encouraged to follow the URL construction conventions defined in this specification when possible as consistency promotes an ecosystem of reusable client components and libraries. The and documents specify 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. 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 Open Data Protocol (OData) enables the creation of REST-based data services, which allow resources, identified using Uniform Resource Identifiers (URLs) and defined in a data model, to be published and edited by Web clients using simple HTTP messages. OData V4 has been standardized by OASIS and has many features not included in OData Version 3.0. It does not store any personal data.URL Conventions (OData Version 3.0) OData Version 4.0 is the current recommended version of OData. ![]() The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. The cookie is used to store the user consent for the cookies in the category "Performance". This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |