[OASIS Issue Tracker] Updated: (ODATA-408) 11.2.3 OData services MAY/SHOULD/MUST expose their data model

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

     [ http://tools.oasis-open.org/issues/browse/ODATA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-408:
-----------------------------

        Fix Version/s: V4.0_CSD02
    Affects Version/s: V4.0_CSD01
                           (was: V4.0_WD01)

> 11.2.3 OData services MAY/SHOULD/MUST expose their data model
> -------------------------------------------------------------
>
>                 Key: ODATA-408
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-408
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol 
>    Affects Versions: V4.0_CSD01
>            Reporter: Patrick Durusau
>             Fix For: V4.0_CSD02
>
>
> Checking against the conformance clauses:
> OData Minimal Conformance Level is missing: "MAY publish metadata at /$metadata according to [OData-CSDL] (section Metadata Document Request)"
> OData Intermediate Conformance Level has: "SHOULD publish metadata at /$metadata according to [OData-CSDL] (section Metadata Document Request)"
> OData Advanced Conformance Level has: "MUST publish metadata at /$metadata according to [OData-CSDL] (section Metadata Document Request)"
> Suggest defining OData Metadata Service at 11.2.3, therefore delete: "OData services MAY/SHOULD/MUST expose their data model as an OData Metadata Service." and let the conformance clauses refer to this section to say may, should or must.
> Just a nit, I would say "A" metadata service..., since not every conforming OData implementation will offer a metadata service. And "A" Metadata Service Document URL, same reasoning.

-- 
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