Hi All, The current definition of inputParameter ( http://open-services.net/ns/auto/auto.html#inputParameter) and outputParameter is that it is a reference to a resource of type ParameterInstrance. I think we all understand that no service providers really support a separate resource for these parameters. They are just inline in nature. Therefore we decided that such parameters will be often be inline parameters in the document. However while implementing this feature , I figured out I really need to have a unique URI if I use resource model, otherwise rdf/xml document can not be generated.
Provided that I want to know if any one have done successful implementation for these parameters? Example to use the ParameterInstance approach, I really need to have a URI as shown below. <oslc_auto:inputParameter rdf:resource="Some Unique URI for parameter Instance"/> <rdf:Description rdf:about="AutomationRequest unique URI"> ... <oslc_auto:inputParameter rdf:about="Some Unique URI for parameter Instance say InputParamURI1"/> ... </rdf:Description> <rdf:Description rdf:about="InputParamURI1"> <oslc:name rdf:datatype="http://www.w3.org/2001/XMLSchema#string ">BuildLocation</oslc:name> <rdf:value rdf:datatype="http://www.w3.org/2001/XMLSchema#string";>foo Path</rdf:value> <rdf:type rdf:resource=" http://open-services.net/ns/auto#ParameterInstance"/> </rdf:Description> Any inputs on it 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 | Ask Question in forum | Online Help | Download RQM 4.0
