Currently, the oslc_auto:parameter attribute in an automation planned is defined as having a range of =oslc:property=.
The Automation workgroup wanted to see what the minimum definition of a simple name/value pair would look like under this approach.
The following test plan contains a parameter definition for a required string parameter named “StringParam1” using the minimum required attributes.
http://open-services.net/ns/auto#ParameterDefinition would have to be defined in the OSLC vocabulary.
<?xml version="1.0"?>
<rdf:RDF xmlns:oslc="http://open-services.net/ns/core#"
xmlns:oslc_auto="http://open-services.net/ns/auto#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dcterms="http://purl.org/dc/terms/">
<oslc_auto:AutomationPlan rdf:about="http://example.org/autoPlans/plan1">
<dcterms:title>Automation Plan 1</dcterms:title>
<dcterms:identifier>1</dcterms:identifier>
<oslc_auto:parameter>
<rdf:Description>
<oslc:name>StringParm1</oslc:name>
<oslc:occurs>http://open-services.net/ns/core#Exactly-one</oslc:occurs>
<oslc:propertyDefinition rdf:resource="http://open-services.net/ns/auto#ParameterDefinition" />
<oslc:valueType>http://www.w3.org/2001/XMLSchema#string</oslc:valueType>
</rdf:Description>
</oslc_auto:parameter>
</oslc_auto:AutomationPlan>
</rdf:RDF>
