[oslc-scm] Making OSLC SCM less file-centric

[Frank Schophuizen]

*Remark 12: Baseline of baselines*
The oslc_scm:baseline property should be defined differently. Whether a
baseline is incremental or full is a matter of implementation by the
provider. In both cases, the baseline is a complete configuration. So I
would not waste a property on it.
On the other hand, a baseline should be per definition (and the text may be
adapted accordingly) a "previous" baseline + changes relative to the
"previous" baseline. In this case, the property oslc_scm:baseline specifies
the previous baseline and the property oslc_scm:changesets specifies the
changes relative to the previous baseline.

*Remark 13: Baseline recursion*
This is something I don't understand. A baseline is a (frozen) configuration
and a configuration is a set of VersionedObjects (CompositeVersionedObjects
and AtomicVersionedObjects). If we freeze a configuration, then I would
assume that the whole configuration is frozen. So why do we need recursion
to be on or off? If the baseline does not contain the complete
configuration, then it is no good!

*Remark 14: Baseline get*
Don't we need more operations?

Frank.

-- 
TOPIC Embedded Systems
P.O. box 440, NL-5680 AK Best
Netherlands
Phone (+31) 499 336979
Fax   (+31) 499 336970
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-scm_open-services.net/attachments/20100223/7e4ef16c/attachment-0003.html>