[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Review of 'change set' terms & shapes
Nick suggests we discuss these questions at this week's meeting, so here are the emails for reference. Regards, Dr. Martin Sarabura R&D Fellow, PTC From: Sarabura, Martin
Nick, there may be some issues with what you have proposed for change sets: - How to treat a selection or contribution that has been removed as part of the change set - Can a change set reference a new version of a contribution as part of the change? Why is "contribution" not part of the shape? Maybe I'm just not that clear
on the meaning of contribution. - At a more fundamental level, I suppose the question is why change sets need to be exposed as consumable external resources. Of course internally they satisfy
an important requirement which is to represent the difference between two change sets in a handy format. But will an external application need this? What is the use case? Using the term "overrides" certain suggests a particular meaning for the related configuration. Is it necessary to use that term specifically? You could use
"RelatedTo" to suggest an agnostic relationship. I assume that typically you'd want to override a configuration in a particular context, right? In which case you'd need to reference the context too. I can see how you don't feel the spec is ready to include
this property because it does open up some new issues such as context, but I can also see the benefit so maybe it's worthwhile investing the effort. In summary I would like to see why change set is required as a resource for external usage. I see the value of personal configuration and overrides though I
think you should flesh out overrides a little more and first class it if possible. On a side note, I am confused as to why there is no "Configuration shape". Configurations are definitely resources, we talk about them as such throughout the
documents. Why do they have no shape in the spec? Hope this helps, Martin Dr. Martin Sarabura R&D Fellow, PTC From: Nick Crossley [mailto:ncrossley@us.ibm.com]
The changes are in two files. First, the vocabulary at
https://tools.oasis-open.org/version-control/browse/wsvn/oslc-ccm/branches/cset/specs/config-mgt/config-vocab.ttl, where we added two classes and one property: |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]