[Oslc-Automation] Optional property proposal: Progress Indication

[Martin P Pain]

Hello Rupert,

Thank you for your progress indication suggestion.
The specification that the Working Group is currently working on 
("Availability" automation) has been delayed, that may allow more time to 
roll this new property in with that work and its review cycles, etc. As 
time has moved on a bit from your original suggestion, would you be any 
more available to join the WG to participate in the (hopefully minimal) 
work to get this new property in?

Whether or not you are available to join, do you have any thoughts on how 
this might be represented. Some options are:

Separate properties for percent vs date/time.
oslc_auto:percentCompleted 10;
oslc_auto:expectedCompletion "2014-06-30T12:00:00"^xsd:dateTime;

Single property with a choice of two data types:
oslc_auto:completion 0.1; //10% completed
oslc_auto:completion "2014-06-30T12:00:00"^xsd:dateTime; // Expected 
completion date

Any thoughts?

Thanks,

Martin Pain
Software Developer - Green Hat
Rational Test Virtualization Server, Rational Test Control Panel
OASIS Open Services for Lifecycle Collaboration - Automation technical 
committee chair

E-mail: martinpain at uk.ibm.com
Find me on:  and within IBM on:  




IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

"Oslc-Automation" <oslc-automation-bounces at open-services.net> wrote on 
09/05/2014 18:29:45:

> From: Schlick Rupert <Rupert.Schlick at ait.ac.at>
> To: "oslc-automation at open-services.net" 
<oslc-automation at open-services.net>, 
> Date: 09/05/2014 18:30
> Subject: [Oslc-Automation] Optional property proposal: Progress 
Indication
> Sent by: "Oslc-Automation" <oslc-automation-bounces at open-services.net>
> 
> Dear Automation Workgroup,
> 
> while working on implementing automation providers, we came up with 
> the idea of giving a progress indication for asynchronous execution 
> (while in state inProgress). This could be done by giving a 
> completion percentage or an “estimated time of arrival”. For an 
> automation consumer, it might be interesting to get that information
> and in my view, it would make sense to have this standardized as 
> optional, but predefined  fields.
> 
> Sorry for barging in like that – if there is a better place to drop 
> feedback/ideas from “specification users”, please advise me. We are 
> working on some tools acting as automation providers, but I’m not in
> a position to join the workgroup as a contributing member.
> 
> As feedback to your excellent work on the specs:
> From “outside” the 2.1 draft looks very good, but gets increasingly 
> harder to grasp.
> 
> I’m a bit concerned that both the automation specification and OSLC 
> as a whole is growing at a speed and in a form, where the original 
> goal of simplicity and sticking to what is necessary for or needed 
> by most applications, is not fulfilled anymore. (Although I admit it
> is paradox to state that in an email where I’m actually asking for 
> additional features).
> 
> Best regards
> 
> Rupert Schlick
> 
> --
> Rupert Schlick
> Scientist
> Department Safety and Security
> Business Unit Safe and Autonomous Systems

> AIT Austrian Institute of Technology GmbH
> Donau-City-Straße 1  |  1220 Vienna  | Austria
> T +43(0) 50550-4124  |  F +43(0) 50550-4150
> rupert.schlick at ait.ac.at  |  http://www.ait.ac.at
> 
> FN: 115980 i HG Wien  |  UID: ATU14703506
> http://www.ait.ac.at/Email-Disclaimer
>  _______________________________________________
> Oslc-Automation mailing list
> Oslc-Automation at open-services.net
> 
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140613/82f90421/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 518 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140613/82f90421/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1208 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140613/82f90421/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 360 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20140613/82f90421/attachment.gif>