[Oslc-Automation] Request for review of OSLC Automation specification

[Pramod K Chandoria]

Hi John,

The definition of rdf:type says
rdf:type zero-or-many unspecified Resource Reference n/a The resource type 
URIs. 

Essentially it says, it is URI of a resource type, means reference to 
other resource. That may not be always the case for the automationType, 
often it would be just a String value.

Also look at the core specification, to me it sounds it should contain the 
type URI of resource the resource in question and NOT a place fix for type 
of automation




Am I thinking too different?

Regards
-|- Pramod Chandoria



From:   John Arwe <johnarwe at us.ibm.com>
To:     oslc-automation at open-services.net
Date:   05/29/2012 06:16 PM
Subject:        Re: [Oslc-Automation] Request for review        of OSLC 
Automation      specification
Sent by:        oslc-automation-bounces at open-services.net



rdf:type is 0:* 
Use as many as you need. 
Or, if you prefer to back into it, riddle me this: what semantic would 
your new proposed auto:automationType predicate convey that rdf:type is 
incapable of conveying? 
Best Regards, John

Voice US 845-435-9470  BluePages 
Tivoli OSLC Lead - Show me the Scenario 




From:        Pramod K Chandoria <pchandor at in.ibm.com> 
To:        John Arwe/Poughkeepsie/IBM at IBMUS 
Cc:        oslc-automation at open-services.net, 
oslc-automation-bounces at open-services.net 
Date:        05/29/2012 08:23 AM 
Subject:        Re: [Oslc-Automation] Request for review of        OSLC   
Automation        specification 



That is a type of the resource probably the itemType of the resource in 
the repository. 

I am talking at next level of automation type where we can distinguish 
between various type of automations provided by the provider 
The first level of type is very high level, theme of the automation  i.e. 
test, build, deployment, etc... 
Similarly service provider also have different type of automation plans 
within a theme. 
e.g. RQM can provide different type of automations 
rft, robot, command line,rpt, qtp, deviceanywhere etc... 
However all automation plan maps to same rdf:type 


How client query automation of it's interest, say build automation? How a 
service provider declares what automation type service is provides in the 
catalog. Service provider might offer automation of just one type or may 
be more then one type. 

Regards, 
___________________________________________________________________________ 

-|- Pramod K Chandoria 


Advisory Software Engineer 

IBM Rational, India Software Lab 

Bangalore, India | +91-80-417-77045 | +91 99805 68253 
What's new in 4.0 RC0 | Ask Question in forum | Online Help | Download RQM 
4.0 RC0 









From:        John Arwe <johnarwe at us.ibm.com> 
To:        oslc-automation at open-services.net 
Date:        05/29/2012 05:42 PM 
Subject:        Re: [Oslc-Automation] Request for review of        OSLC   
Automation        specification 
Sent by:        oslc-automation-bounces at open-services.net 



> Automation plan: We don't have oslc_auto:automationType attribute. 
Without this we can't distinguish whether Automation is for build, test, 
deployment, cloud etc.. I think this needs to be typed. 
rdf:type is your friend 
Best Regards, John

Voice US 845-435-9470  BluePages 
Tivoli OSLC Lead - Show me the Scenario 
_______________________________________________
Oslc-Automation mailing list
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net 
_______________________________________________
Oslc-Automation mailing list
Oslc-Automation at open-services.net
http://open-services.net/mailman/listinfo/oslc-automation_open-services.net


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120529/1c83ddab/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 36504 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120529/1c83ddab/attachment.gif>
-------------- 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/20120529/1c83ddab/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 3624 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120529/1c83ddab/attachment-0002.gif>