I think this needs to be re-visited in the workgroup this week. When deciding whether to use oslc:Property as the parameter definition there was some discussion on what to do about oslc:propertyDefinition. It really is not needed for the automation use case, but it is exactly-one in the resource definition. The options were a) ignore the fact that it is required, b) create a new resource that mimics oslc:Property without the propertyDefinition or c) figure out an acceptable way to set it in the context of automation. The definition of the attribute is:
"URI of the property whose usage is being described" According to the minutes (which could be incorrect due to my misinterpretation of the discussion) there was a proposal to set the the value to something in the Automation vocabulary called oslc_auto:parameterDefinition to indicate the property should be interpreted as such. When used in the context of resource shapes, the oslc:propertyDefinition points to the definition of the property in the domain vocabulary - at least in the specs I am familiar with. Example from a Test Case resource shape for its oslc_qm:testsChangeRequest attribute: <oslc:propertyDefinition rdf:resource= "http://open-services.net/ns/qm#testsChangeRequest" /> Let's discuss if your expected value makes more sense. Regards, Mike Michael Fiedler IBM Rational Software [email protected] 919-254-4170 John Arwe/Poughkeepsie /IBM@IBMUS To Sent by: [email protected], oslc-automation-b cc ounces@open-servi ces.net Subject [Oslc-Automation] Spec/Example comments: Automation Plan, 04/05/2012 08:41 parameter definition AM [1] includes 0:* oslc_auto:parameterDefinition instances, with a range of oslc:Property . So if my example AP has 2 properties, foo:bar and foo2:bar2, I would expect the corresponding oslc:propertyDefinition URIs to be foo:bar and foo2:bar2, per [2]. What my implementers observe however in [3] is a value of oslc_auto:parameterDefinition. Seems like a bug in the example. [1] http://open-services.net/bin/view/Main/AutoSpecificationV2?sortcol=table;up=#Resource_AutomationPlan [2] http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixA#Value_type_Property [3] http://open-services.net/bin/view/Main/AutoSpecificationV2Samples 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
