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

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

Shape names do not have to be the same as the name of the class they are describing. So, Jim's aspect #2 is easily accommodated just by having extra shapes with both/either the domain name of the domain defining this additional usage and/or a different name for the different usage. For example, the Change Management domain could define a shape for change requests with the URI http://open-services.net/ns/cm/shapes/3.0/changerequestcreation (referenced from creation factories) and one with the URI http://open-services.net/ns/cm/shapes/3.0/changerequestquery (referenced from OSLC 2.0 compatible query capabilities).

If we think having different shapes for different purposes is a common pattern, and one that is not already addressed by the three specific OSLC 2.0 references to shapes (creation factory, query capability, and instance shape), then we might want to consider adding the optional property oslc:usage to resource shapes. However, I'm not convinced that is necessary, and given the likely future move to use SHACL, probably not something we should add to shapes at this time.


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