[Oslc-Automation] Oslc-Automation Digest, Vol 16, Issue 12

[Daniel Berg]

Charles,

Thanks for the reminder. I thought there was a reason for the link the way
it was but I couldn't remember the exact reason.
The specification also states that for the AutomationResult there is a
reference called oslc_auto:producedByAutomationRequest with a zero-to-one
multiplicity. Thus it is to be expected that a request will not always be
returned from a result.

Regards,
Daniel Berg
STSM, Master Inventor
IBM Rational, DevOps Lead
1-919-486-0047 | Cell: 1-919-637-8570



From:	Charles Rankin/Austin/IBM
To:	David N Brauneis/Raleigh/IBM at IBMUS,
Cc:	Daniel Berg/Raleigh/IBM at IBMUS,
            oslc-automation at open-services.net,
            oslc-automation-bounces at open-services.net, Pramod K Chandoria
            <pchandor at in.ibm.com>
Date:	07/02/2012 12:59 PM
Subject:	Re: [Oslc-Automation] Oslc-Automation Digest, Vol 16, Issue 12


oslc-automation-bounces at open-services.net wrote on 06/30/2012 06:47:24 AM:

> From: David N Brauneis/Raleigh/IBM at IBMUS
>
> Then you are making the assumption that the parameters passed on the
> request are cloned into the result (I do not believe that semantic
> is true for all automation providers).

The specification, as currently written states that the inputParameters to
the Automation Request are cloned to the Automation Result.

> From:        Daniel Berg/Raleigh/IBM at IBMUS
>
> It is fine if the AutomationRequest has a relationship to the
> AutomationResult versus the other way around if we want to avoid
> dangling references. However, we need to have the request parameter
> values captured and stored with the AutomationResult for audit purposes.

I thought one of the reasons that we needed to have the reference the other
way around (from Result to Request) was so that an async style request
could do a query to determine which Automation Result was associated with
the Automation Request it generated (in the case where Automation Requests
have a shorter lifespan than Automation Results).  If the link is from
request to result there is a timing window where the consumer creates the
request (but there is no associated result yet) and the request gets
deleted.  At that point, the consumer has no way to determine which result
goes with their request.  At least with the link going from result to
request, even if the reference is dangling, the reference itself is still
accurate, and allows the needed query.

Charles Rankin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120702/59c6f171/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120702/59c6f171/attachment.gif>