[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=60964#comment-60964 ] 

James Amsden commented on OSLCCORE-25:
--------------------------------------

Nick, one possible issue with the proposal is that shapes (i.e., constraints) have two dimensions - 1) different versions of a particular set of constraints and 2) different constraints on the same vocabulary for different usages. 

For the OSLC shapes, we probably don't need to worry about case 2) since we are only defining shapes for one purpose - OSLC. But this could arise if for example different domains needed to put different constraints on OSLC Core vocabulary.

So we may want to consider adding a path entry for "context", "usage" or something like that, including the version. The domain short name might already play that role for our purposes.

Note the First Public Working Draft of the Shapes Constraints Language (SHACL):
http://www.w3.org/TR/2015/WD-shacl-20151008/ has been submitted. We should understand the implications of this on OSLC in general, and in particular how it might impact how constraints are published.


> 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
>              Labels: URI
>
> 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)