[Oslc-Automation] 2.1 open comment: short lived creation dialog results

[John Arwe]

In [1] we have this as an open note: 
Martin: Should we also have an oslc:usage value for dialogs where the 
created resources are “especially likely to be short-lived”? All deferred 
execution dialogs right now should have it, but it provides flexibility 
going forwards. Although I’m not sure what consumers would do with it 
right now… 

The "short lived" comment it refers to is at the end of that section; 
final paragraph, and note nested under it.

I think my take here is:  in order to make such a usage value useful to 
clients, we'd have to be concrete about "especially likely" and 
"short-lived".  I don't think it's feasible to be concrete enough to be 
obviously useful in the absence of scenarios that clearly call for it. So, 
KISS and do nothing now; we can always add something in the future once 
the needful scenario(s) emerge.

I don't know how to deal with "likely"; if a dialog creates some mixture 
of long and short-lived resources, and their lifetime is 
influenced/determined by creation parameters, "likely" is entirely 
dependent upon client usage so I can't see how to generalize it. 

"Short lived" really is a nice way of saying that the provider garbage 
collects (or is allowed to) on a short interval, to prevent lots of cruft 
accumulating.  We could have the provider expose its garbage collection 
interval, but that's no guarantee (in either direction); if the provider 
determines that it's running low on some resource, I don't think we can 
prevent it from reclaiming it by garbage collecting "early", nor can we 
force it to collect "on time".  I.e. it's a hint to the client. 
Conceptually I don't object to that, but we have no scenarios even asking 
for it so I'm inclined to wait until we do.

[1] 
http://open-services.net/wiki/automation/OSLC-Automation-Specification-Version-2.1/#Deferred-Execution-Creation-Dialog

Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140313/59532562/attachment-0003.html>