OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (ODATA-413) Replace conformance clauses in URL and CSDL with references to Protocol

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

Michael Pizzo commented on ODATA-413:

The CSDL document does not rely on other parts of the work product, and defines a usable scope of work. A client library could consume the CSDL in order to understand the model, for example to codegen classes or application templates, without having to read or understand other parts of the work product.

I would propose that we keep the conformance clauses in CSDL, and
1) Clarify that the specification we are referring to is this document representing part 3 of the work product
2) in the conformance for the client, change "custom annotations defined by the service" to simply "custom annotations".

> Replace conformance clauses in URL and CSDL with references to Protocol
> -----------------------------------------------------------------------
>                 Key: ODATA-413
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-413
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData CSDL, OData URL Conventions 
>    Affects Versions: V4.0_CSD01
>         Environment: [Proposed]
>            Reporter: Patrick Durusau
>             Fix For: V4.0_CSD02
> The current text reads:
> *****
> Conforming services MUST follow all rules of this specification for the types, sets, functions, actions, containers and annotations they expose. 
> Conforming clients MUST be prepared to consume a model that uses any or all of the constructs defined in this specification, including custom annotations defined by the service, and MUST ignore any elements or attributes not defined in this version of the specification.
> *****
> It isn't clear if "this specification," (2x) or "this version of the specification" are referring to part 3 or do they mean to refer to parts 1 - 3?
> If part 3 is purely a definitional document that is relied upon by other documents, other documents that have conformance clauses, I don't know that we need a conformance clause here. Best to check with the TC Admin but definitions don't require conformance clauses, IMHO.

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]