Uploaded image for project: 'OASIS OSLC Lifecycle Integration Core (OSLC Core) TC'
  1. OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
  2. OSLCCORE-25

Define a stable URI for OSLC Shape resources

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: None
    • Labels:
    • Proposal:
      Hide

      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

      Show
      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

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              ndjc Nick Crossley
              Reporter:
              ndjc Nick Crossley
            • Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: