The problem that I see right now for AutomationPlan being an implementation of an action is that the POST behaviour seems to be defined on the predicate, not on the Action resource type. If we suggested they move that so that the action predicate can in theory point to anything, then on inspection of its target if it's an Action resource you can POST to it, if it's an AutomationPlan (or our other intermediate resource) you can submit a request. (And providers could multi-type it and support both... but we're still getting into multiple ways of doing things. Although you could look at the Action approach as a way of saying "you can use the classic REST HTTP primatives")
However, for the case of Action resources, this would require either an extra GET on the part of the client (unless they already needed to do that to determine which one has the target state that they are interested in) or for the Action resource to be included inline in the resources that link to it. Martin From: John Arwe <[email protected]> To: [email protected], Date: 30/08/2013 13:06 Subject: Re: [Oslc-Automation] Reusing Cm's Actions for teardown/operations Sent by: "Oslc-Automation" <[email protected]> > I don't like this "two ways of doing things" Nor I; that's actually the EXACT reason I'm poking this with a pointy stick. Right now we DO have this case in general; Automation makes 2 (classic REST updates via HTTP primitives being the first). I think they each have cases they handle better than the alternative, but the interaction models are so different I just cut to the chase and call them incompatible (assuming one is talking about resources at the same level of abstraction). My intent is to construct an example where an Automation Plan is the *implementation of* an Action, to show that is POSSIBLE not that it is required. I am working on a concrete example on the side; either I'll succeed so we'll know it's possible, or I'll fail and (unless someone else sees a way past whatever roadblocks I find) give up on it. Best Regards, John Voice US 845-435-9470 BluePages Tivoli OSLC Lead - Show me the Scenario _______________________________________________ Oslc-Automation mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-automation_open-services.net 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
