[Oslc-Automation] Availability Spec review - my feedback - OSLC Actions - thread 4 Availability Group (AG)

[John Arwe]

MP> dcterms:modified: Do we want to make it explicit that new members 
added to the group update this?
TF> Do you think its enough to describe this in the properties description 
or ...

Honestly, I'd say we say so in the normative text (at least SHOULD, 
possibly MUST) and say it for ALL the collections.
...and queue it up to the Core TC for inclusion in 3.0-Core specs.  I 
think we want it to be pretty consistent.
...and feed it back into W3C LDP WG.  They might want to weigh in as well, 
in spec or in best practices.

MP> AEC: Does the HRG AEC have an RDF vocab/representation?
TF> ...I also have not really an idea if this could cause somehow 
copyright problems?

Sound like a valid discussion point.  wrt copyright, that's for each WG 
members' legal dept to handle.  No one in the WG is qualified to have 
their own opinion.  If everyone's legal says it's ok, then it's 
good-enough presumably.  My (non-legal) understanding is that linking on 
its own is rarely an issue; I think there was a fairly recent EU ruling on 
this.  If we were to draft a vocabulary document that reproduces or is 
based on their work, that's less obvious and requires legal opinion.

MP> currentlyActive: This predicate name doesn't indicate "count".
TF> what is the general "OSLC way" here to do things? Is this kind of 
"redundancy" a problem?

I've rarely heard it come up, aside from the specific context of 
duplicating links (in the sense of the member/memberOf discussion) which 
Link Guidance addresses (don't do that).  Typically the "computable" 
output form would be optional, which makes it easy for server implementers 
to agree to (at the cost of clients not being able to depend on its 
presence).

MP> "maxActiveTarget", "minActiveTarget". 
TF> Maybe I've chosen the wrong wording here, maybe "goal" is better?

I don't think it's a "choice of word" issue.  Probably handle it in the 
explanation.  I could tilt my head and think of those both as being part 
of a "policy" resource too (in this can an availability policy, but there 
be other reasonable xxx policy usages).


Best Regards, John

Voice US 845-435-9470  BluePages
Cloud and Smarter Infrastructure OSLC Lead
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140514/a5e5d583/attachment-0003.html>