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] (ODATA-886) Need a stable reference to latest/current OASIS OData vocabularies


    [ https://issues.oasis-open.org/browse/ODATA-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61561#comment-61561 ] 

Robin Cover commented on ODATA-886:
-----------------------------------

The candidate design solution I sent to the TC principals (November) was accepted, and some of the design for URI aliases is visible in the initial "starter document" sent to the TC list:

https://lists.oasis-open.org/archives/odata/201512/msg00062.html
https://lists.oasis-open.org/archives/odata/201512/msg00062/odata-vocabularies-v4.0-wd01.docx

While we do not typically create URI aliases for machine-readable files to support "Latest version" URI references (pointing in succession to each versioned instance), the OData TC requirements as documented seem to justify this kind of solution.

Solution: factor out from a Work Product:

a)  the machine-readable content that needs to be referenced by two or more Work Products and associated remote applications
b)  ... where the content (e.g., in authority files) needs to have its own revision schedule and revision identifier scheme, independent from the referencing Work Products, applicable XML namespace URIs, and and applications software
c) ... where URI references are needed for the "Latest Version" content
d) ... where conformance clauses or similar constraints are formulated to reflect awareness of the fact that the considerations in "b)" and "c)" are expected and acceptable to the referencing Work Product

Please send questions/comments if you have any: robin@oasis-open.org

- Robin Cover



> Need a stable reference to latest/current OASIS OData vocabularies
> ------------------------------------------------------------------
>
>                 Key: ODATA-886
>                 URL: https://issues.oasis-open.org/browse/ODATA-886
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: Vocabularies
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_ERRATA03
>
>
> The latest published errata for all of our specs are available at http://docs.oasis-open.org/odata/odata/v4.0/ (for the protocol specification) and at http://docs.oasis-open.org/odata/odata-json-format/v4.0/ (for the odata json specification).
> We don't have a way for applications to get to the latest versions of the vocabularies.



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


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