[OASIS Issue Tracker] Updated: (ODATA-540) Can clients GET a Context URL? If not, please rename it Context URI.

[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:all-tabpanel ]

Ralf Handl updated ODATA-540:
-----------------------------

        Fix Version/s: V4.0_CS01
    Affects Version/s: V4.0_CS01

Clients can GET a context URL. It will retrieve the metadata document of the service. The client / user agent can then use the fragment portion of the context URL to identify the relevant section of the metadata document.

I propose to close this issue without action.

> Can clients GET a Context URL? If not, please rename it Context URI.
> --------------------------------------------------------------------
>
>                 Key: ODATA-540
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-540
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>    Affects Versions: V4.0_CS01
>            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