[Oslc-Automation] Summary of Availability Discussion in WG meeting yesterday - Martin's notes

[Martin P Pain]

Only two things to add from my notes (I think these are just 
clarifications of what you've already said):

> (8) How to express in the spec that a service provider should define 
it?s
> own property values but possibly define a small set of values, that are
> enforced (like online/ offline and starting/ stopping for currentState).
> -> Question was due to a misunderstanding of Tim how to interpret the 
Auto
> spec, because this is done there, too (for example for the 
oscl_auto:state
> property). Availability Draft will
> handle it in the same way.

> (2) compoundState - replace with/ additionally introduce consistentState
> with type boolean?
> -> We decided to transform the compoundState into a better usable
> structure. Details will be figured out,
> but its likely that we will introduce a "consistentState" property of 
type
> boolean that signals if everything is ok or if there is a problem,
> and an additional field with a reference as type, that can be used by
> implementors to provide (own defined) Strings with additional 
information.

We also realised that one option for (2) would be to treat compoundState 
the same way as currentState, that is: the same way as state in 
Automation, that is: providers MUST provide one of the spec-defined 
values, but they MAY have two triples on the resource with the "state" 
predicate - one with the spec-defined value, and one with the 
server-specific value. (At least that it my understanding of the spec.)

(We could also clarify that point in the Automation 2.0 spec by adding an 
example of it.)


> (7) Not sure about consequences of memberOf vs. member (direction of
> linkage between a group and it?s members).
> -> Advice to elaborate the "Guidelines" section for the Availability 
Draft,
> in particular considering questions like how a client will handle 
groups.
> When this questions can be answered exhaustingly, the problem can be
> discussed again on the mailing list.

My suggestion was to write down the steps that a client (/consumer) would 
have to go through to execute one or two of the Availablility scenarios, 
detailing exactly how they get and what they do with the resource URLs in 
the process. I expect this will illustrate that whichever way rounf this 
link is, we will still need to rely on either:
a) using the query capability to follow the links in the reverse 
direction, or
b) saying providers MUST put the triples in both resources' graphs (but I 
expect some pro-named-graphs LD-purists would hate that - but personally I 
don't mind)


Martin Pain
Software Developer - Green Hat
Rational Test Virtualization Server, Rational Test Control Panel
OASIS Open Services for Lifecycle Collaboration - Automation technical 
committee chair

E-mail: martinpain at uk.ibm.com
Find me on:  and within IBM on:  




IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU



Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140718/eb7d6a98/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 518 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140718/eb7d6a98/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1208 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140718/eb7d6a98/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 360 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140718/eb7d6a98/attachment.gif>