[oslc-core] [oslc] [Oslc-Automation] OSLC Automation specification preparing to enter finalization phase

Michael F Fiedler fiedler at us.ibm.com
Mon Oct 15 08:47:40 EDT 2012


I will add this as a topic for this week's meeting, but it is correct that
this was by design.   We considered outputParameters on the Request, but
the final decision was to put it on the Result.   The concept the workgroup
and spec are trying to capture is that the outputParameter on the
Automation Result captures all parameters (supplied by the user or supplied
by the provider or its agents) used to produce the result.   The meaning of
outputParameter, as defined today, is tied to the result.

Is this an issue for your implementation?   There is nothing to prevent a
given provider from adding oslc_auto:outputParameter to the Automation
Request if it makes sense for its scenarios.   You just can't expect a
given generic Automation consumer to look for it there.   But consumers who
understand your implementation could make use of it.

Regards,
Mike

Michael Fiedler
IBM Rational Software
fiedler at us.ibm.com
919-254-4170

David N Brauneis/Raleigh/IBM wrote on 10/08/2012 09:07:28 AM:

> David N Brauneis/Raleigh/IBM
> 10/08/2012 09:07 AM
>
> To
>
> Pramod K Chandoria <pchandor at in.ibm.com>,
>
> cc
>
> community <community at open-services.net>, "Community" <community-
> bounces at open-services.net>, Michael F Fiedler/Durham/IBM at IBMUS,
> oslc-automation at open-services.net, Oslc-Automation <oslc-automation-
> bounces at open-services.net>, oslc-core at open-services.net
>
> Subject
>
> Re: [oslc] [Oslc-Automation] OSLC Automation specification preparing
> to enter finalization phase
>
> Pramod,
>
> That was by design from the discussions - the outputParameters
> should only be available as output (which is the AutomationResult).
>
> Regards,
> David
> ____________________________________________________
> David Brauneis
> STSM, Rational Software Delivery Automation Chief Architect
> email: brauneis at us.ibm.com | phone: 720-395-5659 | mobile: 919-656-0874
>
> From: Pramod K Chandoria <pchandor at in.ibm.com>
> To: Michael F Fiedler/Durham/IBM at IBMUS,
> Cc: oslc-automation at open-services.net, community <community at open-
> services.net>, Oslc-Automation <oslc-automation-bounces at open-
> services.net>, oslc-core at open-services.net
> Date: 10/08/2012 09:02 AM
> Subject: Re: [oslc] [Oslc-Automation] OSLC Automation specification
> preparing to enter finalization phase
> Sent by: "Community" <community-bounces at open-services.net>
>
> Hi Mike,
> I noticed that Automation Request does not have
> oslc_auto:outputParameter property, similar to Automation Result.
> This limits the capability to maintain variables till Automation
> Result has been created. I know it have oslc_auto:inputParameter
> property, but that is read only, often copy from Automation plan.
>
> Regards
> -|- Pramod Chandoria
>
>
>
>
> From:        Michael F Fiedler <fiedler at us.ibm.com>
> To:        oslc-automation at open-services.net, oslc-core at open-
> services.net, community <community at open-services.net>
> Date:        10/05/2012 07:45 PM
> Subject:        [Oslc-Automation] OSLC Automation specification
> preparing to enter        finalization phase
> Sent by:        "Oslc-Automation"
<oslc-automation-bounces at open-services.net>
>
>
>
> Hello,   This is to inform you that the OSLC Automation V2
> specification [1] is preparing to enter finalization phase.  All
> open issues to date have been addressed and implementations are in
> progress, including a reference implementation in the Eclipse Lyo
> project [2].  Activities remaining prior to declaring the
> specification final are:
>
> - publish final RDF vocabulary (currently published vocabulary is
> 95% complete)
> - contribute a test suite for the specification to Eclipse Lyo
> - create a primer companion to the specification with examples and
> implementation guidance
> - address any final issues from implementers and the community.
>
> If you have any comments or issues with the specification, now would
> be a good time to raise them.   Thank you.
>
> [1] - http://open-services.net/wiki/automation/OSLC-Automation-
> Specification-Version-2.0/
> [2] - http://eclipse.org/lyo
>
>
> Regards,
> Mike
>
> Michael Fiedler
> IBM Rational Software
> fiedler at us.ibm.com
> 919-254-4170_______________________________________________
> Oslc-Automation mailing list
> Oslc-Automation at open-services.net
>
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
> _______________________________________________
> Community mailing list
> Community at open-services.net
> http://open-services.net/mailman/listinfo/community_open-services.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20121015/374bb06b/attachment-0003.html>


More information about the Oslc-Core mailing list