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


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-ccm message

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

Subject: [OASIS Issue Tracker] (OSLCCCM-35) Resource shape for creating streams

David Honey created OSLCCCM-35:

             Summary: Resource shape for creating streams
                 Key: OSLCCCM-35
                 URL: https://issues.oasis-open.org/browse/OSLCCCM-35
             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
          Issue Type: Improvement
            Reporter: David Honey

The recommended approach in the OSLC Configuration Management spec to create a new stream of a component is to perform a GET on the component to get its streams LDPC. A client can then POST content to that LDPC. However, if the client wants to know what properties it can include in the POSTed RDF, how can it discover the resource shape?

There are a number of approaches we might consider:

1) Declare a creation factory for every component, and each factory can declare a resource shape. A significant problem with this approach is that there could be a very large number of components, and the OSLC SPC could become very large.

2) Have the RDF returned by a GET on the streams LDPC include a reference to the resource shape for new streams of that component. A significant problem with this approach is that a GET on the LDPC would, by default, return all the streams of that component and all their properties. So this seems like a heavyweight means to get the resource shape.

3) Include an additional statement in a component's RDF to the resource shape for configurations of that component. For example, include an oslc_config:streamsResourceShape or oslc_config:configurationResourceShape statement to a resource shape for creating new streams or configurations of that component. This is lightweight and keeps the discovery of the streams LDPC and its resource shape in the same place.

4) Drop support for POST on a component's streams LDPC, and instead declare a configuration creation factory for each project area specific service provider. A client would need to include oslc_config:component to specify the component for the new stream.

There is a related issue about how to discover the resource shape when creating a baseline from a stream. However, there is potentially already a method for doing so - the user could use the resource instance shape of the stream.

This message was sent by Atlassian JIRA

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