[Oslc-Automation] Adoption issues with inputParameter and outputParameter

[John Arwe]

> 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. 

Not obvious why this would be true.  What leads you to this conclusion.
In addition to blank nodes (Michael's emails), you can use hash URIs. I.e. 
if your document has a URI of http://foo, you assign URIs like 
http://foo#Param1 and http://foo#ParamFred.  The URI fragment components 
are still part of the URI for RDF/resource identification purposes (so 
here I have a total of 3 resources each with a unique URI), although they 
do not flow to the HTTP server on HTTP requests (all 3 resources have the 
same effective HTTP request-URI).  So requests for http://foo would be 
required to return the triples for #Param1 and #ParamFred in order for 
this "trick" to work (and similarly, accepted on create/update).
Either should work.  If you find otherwise, a complete example of what you 
tried and the problems it has will be required to either convince others 
the conclusion is correct or accomplish debug if it's not.

Best Regards, John

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-automation_open-services.net/attachments/20120829/4c547488/attachment-0003.html>