OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

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


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


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

Nick Crossley updated OSLCCORE-25:
----------------------------------

    Proposal: 
Shapes are different than vocabularies in that shapes may change with new 
revisions of resource definitions, whereas vocabularies should evolve in place in a compatible manner.

The proposed URI pattern for each individual resource shape is:

        http://open-services.net/ns/[vocab short name]/shapes/[version]/[shape-name]

For example, for Change Management 3.0, a shape describing the base Change Request resource type might have the shape URI:

        http://open-services.net/ns/cm/shapes/3.0/changerequest

Not all shapes would necessarily be updated at the same time. To allow different versions of individual shapes to be reused in different versions of a domain specification while still allowing a client to browse the set of possible shapes, domains SHOULD provide an LDPC for all the shapes for a spec version, at:
    http://open-services.net/ns/[vocab short name]/shapes/[SPEC-version] 

For example, for Change Management 3.0, there should be a container at:
        http://open-services.net/ns/cm/shapes/3.0
with members such as:
        http://open-services.net/ns/cm/shapes/3.0/changerequest
        http://open-services.net/ns/cm/shapes/3.0/somenewshape
        http://open-services.net/ns/cm/shapes/2.0/unchangedshape


  was:
Shapes are different than vocabularies in that shapes may change with new 
revisions of resource definitions, whereas vocabularies should evolve in place in a compatible manner.

The proposed URI pattern for each individual resource shape is:

        http://open-services.net/ns/[vocab short name]/shapes/[version]/[shape-name]

For example, for Change Management 3.0 a Change Request might have the shape URI:

        http://open-services.net/ns/cm/shapes/3.0/changerequest

Not all shapes would necessarily be updated at the same time. To allow different versions of individual shapes to be reused in different versions of a domain specification, we add an LDPC for all the shapes for a spec version, at:
    http://open-services.net/ns/[vocab short name]/shapes/[SPEC-version] 


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


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