[OASIS Issue Tracker] (OSLCCORE-25) Define a stable URI for OSLC Shape resources

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

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

Nick Crossley commented on OSLCCORE-25:
---------------------------------------

But how would a client know which URIs to read?  With Martin's suggestion, the URIs for the shapes for a given version of the spec would be an arbitrary mix of shape versions - you'd have to invent an LDPC of shapes to find them - though that might not be a bad idea: http://open-services.net/ns/[vocab short name]/shapes/[SPEC-version] is an LDPC of the shapes for that version, which may then reference shapes that are shared across other LDPCs for other versions.
Yes, with the original proposal some shapes might be copied or redirected. Is that a problem?  Note this approach also provides an easier way for a client to find one specific shape - the container approach mentioned above would require a client to traverse the LDPC contents to find a specific shape.

> Define a stable URI for OSLC Shape resources
> --------------------------------------------
>
>                 Key: OSLCCORE-25
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-25
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>            Reporter: Nick Crossley
>            Assignee: Nick Crossley
>
> In the same way that we publish stable vocabularies to open-services.net/ns, we need to be able to publish OSLC Shape resources with stable URIs.



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