Minutes for 2012-10-02
Attending: Nick, John, Peter, David, Gray, Mike
- Nick thanked David for running the last two meetings. We then discussed the minutes of previous two meetings, so that Nick could catch up.
- Nick asked about baselines just being a set of resources with some tag, and suggested we should require such providers to construct a baseline resource to represent the results of a query over such resources - the idea being to keep configurations and baselines both pretty much the same resource type, to keep things simple. The group did not object to this approach.
- Nick mentioned that there were ways of implementing ‘Compare’ that did not require enumeration of baseline or configuration contents - we could just ask each provider to return an HTML page showing a difference, and not define a way to parse that returned value. However, such an approach would not satisfy all our use cases. Mike mentioned that a separate ‘release object’ could carry the structure information. We agreed to come back to the topic of enumerating the contents of a baseline or configuration on another day, as it was a complex subject.
- David mentioned that a link to the W3C provenance group has been added to the main page.
- We discussed check out , and agreed to make it optional - but we need to review the scenarios to ensure each one can be addressed whether or not checkout is provided.
- We then went on to discuss terminology. Gray mentioned we should be careful about defining resources vs. terms - e.g. version vs. version resource, where there is a difference.
- We agreed to remove baseline as a separate type - but keep it as a term to be defined. Baselines would be represented as configurations, and we would provide a state predicate (like in OSLC Change Management) to define immutability.
