Hello, I'm using OSLC Actions now in the Availability draft. I've pasted the relevant sections of the draft at the end of this mail, so that you do not need to search for it.
@Martin: I would be available for discussion of the new things (Availability vocabulary, use of OSLC Actions) this Thursday. So if someone find the time to have a look at it, we can use this week's meeting for discussion. If you think time's to short, we can schedule the meeting next week on July 3th. (I'm in vacation on July 10th.) Thanks! New parts in the Availability Draft related to Action: (1) New property for oslc-availability:AvailabilityComponent: oslc:action Occurs: zero-or-many Read-only: unspecified Value-type: Resource Representation: Either Range: any Description: An action on the subject resource, i.e. it links to an action that the provider asserts is currently available for execution by clients . A typical scenario for an action on an AvailabilityResource is to change its condition, e.g. to update its oslc-availability:desiredState so that a resource, representing a stopped software system, will be started. In a distributed system, clients can lose race conditions that result in an “available”-appearing action’s execution requests being rejected. It is likely that the target resource will be an oslc-availability:ChangeConditionAction, but that is not necessarily the case; when it is anoslc-availability:ChangeConditionAction, it will have at least one binding since it is currently available. (2) New Section "Availabilty Definitions"-section: OSLC Actions and Availability Accordant to the OSLC Actions 2.0 specification, Actions provide “a means of advertising actions (or operations) that can be performed on (or in the context of) a specific resource”. In the context of the Availability specification, Actions are very likely to be used to change the oslc-availability:AvailabilityCondition of an oslc-availability:AvailabilityResource. If such a resource represents for example a software system, a typical action may to start or stop it. Change condition action type This specification defines the RDF class oslc-availability:ChangeConditionAction, as an rdfs:subClassOf oslc:Action, with the meaning that any action of this type MUST have the semantics of changing the condition of a resource in the context of Availability. It is likely that the execution of such an action changes the states of a resource's oslc-availability:AvailabilityCondition, but this MAY not be the case. Profiles The following specification profiles are suggested to be chosen by provider implementations. Profile: Create a HTTP request with an oslc-availability:AvailabilityCondition as request body As described in http://open-services.net/wiki/core/Actions-2.0/#pattern-resource-shape A client can change the condition of a resource in the context of Availability by sending a HTTP request with an oslc-availability:AvailabilityCondition as body, that represents the new condition of the resource. Profile: Create an Automation Request As described in http://open-services.net/wiki/core/Actions-2.0/#profile_automation_request Favored profile if the resources in the context of Availability are automated and the provider also implements the OSLC Automation Specification, see http://open-services.net/wiki/automation/OSLC-Automation-Specification-Version-2.0/ To change the condition of a resource, the client creates an oslc_auto:AutomationRequest to execute an oslc_auto:AutomationPlan, handling all the necessary steps to change the condition of the resource. It is very likely, that as a side effect the oslc-availability:AvailabilityCondition of the resource will be changed. Profile: Use delegated UI dialog for immediate execution As described in http://open-services.net/wiki/core/Actions-2.0/#pattern-immed-dialog The client displays a delegated UI dialog to a user to perform an action immediately, that will change the condition of a resource in the context of Availability. Mit freundlichen Grüßen / Kind regards Tim Friessinger System Automation for z/OS Development IBM Software Group, Tivoli IBM Lab Boeblingen, Germany Phone: 49-7031-16-2535 IBM Deutschland (Embedded image moved to file: pic51729.gif) E-Mail: [email protected] Schoenaicher Str. 220 71032 Boeblingen Germany IBM Deutschland Research & Development GmbH / Vorsitzende des Aufsichtsrats: Martina Koederitz Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
