[OASIS Issue Tracker] Commented: (ODATA-540) Explicitly state that the Context URL locates (a specific portion of) the metadata document

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35050#action_35050 ] 

Martin Zurmuehl commented on ODATA-540:
---------------------------------------

The RFC 3986 (Uniform Resource Identifier (URI): Generic Syntax) see http://tools.ietf.org/html/rfc3986#section-3.5 states in the fifth paragraph:
   "Fragment identifiers have a special role in information retrieval
   systems as the primary form of client-side indirect referencing,
   allowing an author to specifically identify aspects of an existing
   resource that are only indirectly provided by the resource owner.  As
   such, the fragment identifier is not used in the scheme-specific
   processing of a URI; instead, the fragment identifier is separated
   from the rest of the URI prior to a dereference, and thus the
   identifying information within the fragment itself is dereferenced
   solely by the user agent, regardless of the URI scheme."

Based on this spec (at least to my understanding) a response to a GET on the ContextURL always must return the metadata document. If we want to change this we can't use the URI fragment to encode the information like set, type, path, cardinality, projection, etc. in the ContextURL, we have to find a different way.

> Explicitly state that the Context URL locates (a specific portion of) the metadata document
> -------------------------------------------------------------------------------------------
>
>                 Key: ODATA-540
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-540
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol 
>    Affects Versions: V4.0_CS01
>         Environment: [Applied]
>            Reporter: Evan Ireland
>             Fix For: V4.0_CSD03
>
>
> It appears that Context URL is just a description, not a location, of a resource. Thus the term "URL" may be inappropriate, and "URI" may be more appropriate.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira