[ https://issues.oasis-open.org/browse/OSLCCORE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60888#comment-60888 ]
Martin Pain commented on OSLCCORE-25:
-------------------------------------
If the machine reader of the shapes needs the URIs, do we need to make the URIs readable in the spec. e.g. for implementers to copy & hard-code in their implementations.
Also, was there a discussion about having a list (container?) of all shapes that are included in a particular version of a spec? To aid programmatic consumption. I'd suggest an explicit document, rather than implicit in URIs & using directory listings. (One option could be RDFa embedded in the spec document itself, but I won't actively suggest that...)
> 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)
