[OASIS Issue Tracker] (ODATA-698) Clarify rules around handling of custom query options when building URLs

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Michael Pizzo created ODATA-698:
-----------------------------------

             Summary: Clarify rules around handling of custom query options when building URLs
                 Key: ODATA-698
                 URL: https://tools.oasis-open.org/issues/browse/ODATA-698
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: OData Protocol , OData URL Conventions 
    Affects Versions: V4.0_OS
         Environment: [Proposed]
            Reporter: Michael Pizzo
            Priority: Minor
             Fix For: V4.0_ERRATA01


OData defines custom query options as an extensibility mechanism for services to support service-specific behavior. However, semantics around how services inject, and clients respect, custom query options is not clearly spelled out.

In particular, when services advertise URLs (in service document, navigation links, read/edit, and media read/edit urls) that include custom query options, clients should preserve those custom query options whether invoking those urls directly or appending segments/additional query options.

For example, if a service advertises an edit link for an entity as a url with a custom query option, and the client wants to append a property segment to retrieve an individual property from that entity, it should include the custom query option when invoking the url.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)