You'll have to run the XML through your favorite formatter. Regards, Mike
Michael Fiedler IBM Rational Software [email protected] 919-254-4170 [email protected] wrote on 08/21/2012 01:08:24 PM: > Michael F Fiedler/Durham/IBM@IBMUS > Sent by: [email protected] > > 08/21/2012 01:08 PM > > To > > [email protected], > > cc > > Paul Slauenwhite <[email protected]> > > Subject > > Re: [Oslc-Automation] Adoption issues with inputParameter and outputParameter > > You should be able to use blank nodes (which often get represented > as inline nodes when an abbreviated XML writer is used). Example > of unabbreviated XML (hope the xml formatting comes through): > > <?xml version="1.0" encoding="UTF-8"?> > <rdf:RDF > xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"; > xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; > xmlns:dcterms="http://purl.org/dc/terms/"; > xmlns:oslc="http://open-services.net/ns/core#"; > xmlns:oslc_auto="http://open-services.net/ns/auto#"; > xmlns:my_ns="http://example.org/ns/my_ns#";> > > <rdf:Description rdf:about="http://example.org/autoResults/result1";> > <dcterms:title>Automation Result 1</dcterms:title> > <dcterms:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#integer";>1 > </dcterms:identifier> > <rdf:type rdf:resource="http://open-services.net/ns/auto#AutomationResult"/> > <oslc_auto:state>Complete</oslc_auto:state> > <oslc_auto:verdict>Success</oslc_auto:verdict> > <oslc_auto:pass>true</oslc_auto:pass> > <oslc_auto:reportsOnAutomationPlan rdf:resource="http://example.org/ > autoPlan/plan1"/> > <oslc_auto:inputParameter rdf:nodeID="node1"/> > <oslc_auto:inputParameter rdf:nodeID="node2"/> > </rdf:Description> > > <rdf:Description rdf:nodeID="node1"> > <rdf:type rdf:resource="http://open-services.net/ns/auto#ParameterInstance"/> > <oslc:name>Parm1</oslc:name> > <rdf:value>Value1</rdf:value> > </rdf:Description> > > <rdf:Description rdf:nodeID="node2"> > <rdf:type rdf:resource="http://open-services.net/ns/auto#ParameterInstance"/> > <oslc:name>Parm2</oslc:name> > <rdf:value>Value2</rdf:value> > </rdf:Description> > > </rdf:RDF> > > Same sample using unabbreviated XML: > > > <?xml version="1.0" encoding="UTF-8"?> > <rdf:RDF > xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"; > xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"; > xmlns:dcterms="http://purl.org/dc/terms/"; > xmlns:oslc="http://open-services.net/ns/core#"; > xmlns:oslc_auto="http://open-services.net/ns/auto#"; > xmlns:my_ns="http://example.org/ns/my_ns#";> > > <oslc_auto:AutomationResult rdf:about="http://example.org/autoResults/result1"; > > > <dcterms:title>Automation Result 1</dcterms:title> > <dcterms:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#integer";>1 > </dcterms:identifier> > <rdf:type rdf:resource="http://open-services.net/ns/auto#AutomationResult"/> > <oslc_auto:state>Complete</oslc_auto:state> > <oslc_auto:verdict>Success</oslc_auto:verdict> > <oslc_auto:pass>true</oslc_auto:pass> > <oslc_auto:reportsOnAutomationPlan rdf:resource="http://example.org/ > autoPlan/plan1"/> > <oslc_auto:inputParameter> > <oslc_auto:ParameterInstance> > <oslc:name>Parm1</oslc:name> > <rdf:value>Value1</rdf:value> > </oslc_auto:ParameterInstance> > </oslc_auto:inputParameter> > <oslc_auto:inputParameter> > <oslc_auto:ParameterInstance> > <oslc:name>Parm2</oslc:name> > <rdf:value>Value2</rdf:value> > </oslc_auto:ParameterInstance> > </oslc_auto:inputParameter> > </oslc_auto:AutomationResult> > > </rdf:RDF> > > > Regards, > Mike > > Michael Fiedler > IBM Rational Software > [email protected] > 919-254-4170 > > [email protected] wrote on 08/21/2012 08:52:50 AM: > > > Pramod K Chandoria <[email protected]> > > Sent by: [email protected] > > > > 08/21/2012 08:52 AM > > > > To > > > > [email protected], > > > > cc > > > > Paul Slauenwhite <[email protected]> > > > > Subject > > > > [Oslc-Automation] Adoption issues with inputParameter and outputParameter > > > > 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 > > > > [image removed] > > > > 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 > > > > [image removed] > > > > _______________________________________________ > > Oslc-Automation mailing list > > [email protected] > > http://open-services.net/mailman/listinfo/oslc-automation_open-services.net > _______________________________________________ > Oslc-Automation mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-automation_open-services.net
