W3C home > Mailing lists > Public > public-sws-ig@w3.org > January 2005

Re: Doubt about Parameter during execution

From: David Martin <martin@AI.SRI.COM>
Date: Tue, 04 Jan 2005 21:14:09 -0800
Message-ID: <41DB77A1.90106@ai.sri.com>
To: Evren Sirin <evren@cs.umd.edu>
CC: Tatiana Vieira <tascvieira@yahoo.com.br>, public-sws-ig@w3.org



Evren Sirin wrote:

> 
> Tatiana Vieira wrote:
> 
>> Hi Evren,
>>  
>> Sorry for the inconvenience...but as far as we discuss it, I get more 
>> doubts....
>>  
>> I'm really very confused with this terminology...Indeed, OutputA is 
>> not of type books:Book as I wrote before, but it represents a data of 
>> type books:Book. So, in my understanding, OutputA just serves as a 
>> indication of the type of the output the service will generate, and 
>> not as the output data itself. Roughly speaking, OutputA doesn't have 
>> any purpose (sorry for this very "restrictive" word) during execution, 
>> because what we have to query is the produced data, I mean the 
>> books:Book info produced by the process. Ok?
> 
> 
> Yes, that is pretty much it.
> 
>>  
>> As you exemplified, I could write a piece of code to represent the 
>> data generated by the process execution. This code would contain the 
>> data itself, the Book data for instance.
>>  
>> ><PerformResult>
>> >    <performedProcess rdf:resource="#FindBook">
>> >    <hasInputValue>
>> >            <InputValue>
>> >                    <input rdf:resource="BookName"/>
>> >                    <hasDataValue rdf:datatype="&xsd;#string">Name of
>> >the book</hasDataValue>
>> >            </InputValue>
>> >     </hasInputValue>
>> >     <hasOutputValue>
>> >            <OutputValue>
>> >                    <output rdf:resource="BookInfo"/>
>> >                    <hasValue>
>> >                         <books:Book>
>> >                              <books:hasTitle>...</books:hasTitle>
>> >                              <books:hasAuthor rdf:resource="..."/>
>> >                         </books:Book>
>> >                    </hasValue>
>> >            </OutputValue>
>> >     </hasOutputValue>
>> ></PerformResult>
>>
>> At this piece of code, is "BookInfo" the Output of the process? 
>> (process:Output rdf:ID="BookInfo"...process:parameterType books:Book) 
>> ? I'm trying to understand it...
> 
> 
> Yes, exactly. What I had in mind was a process description like this:
> 
> <process:AtomicProcess rdf:ID="FindBook">
>    <process:hasInput>
>        <process:Input rdf:ID="BookName">
>            <process:parameterType 
> rdf:datatype="&xsd;anyURI">&xsd;#string</process:parameterType>
>        </process:Input>
>    </process:hasInput>
>    <process:hasOutput>
>        <process:Output rdf:ID="BookInfo">
>            <process:parameterType 
> rdf:datatype="&xsd;anyURI">&books;#Book</process:parameterType>          
> </process:Output>
>    </process:hasOutput>
> </process:AtomicProcess>
> 
>>  
>> I think the parameterType makes confusion in my mind!!!! In the same 
>> way, did now the sintax of Parameter. As described at Process.owl 
>> file, a Parameter can have at minimum one parameterType. What does it 
>> mean? If it has more than one type, doesn't it have to have also the 
>> same number of parameterValue? (I thought it as an structured 
>> parameter) How can one Parameter have more than one type?
> 
> 
> Hmm, that I don't know. I think that it should be a cardinality (not 
> minCardinality) restriction.

I also think it should  be a cardinality, and I don't remember anyone 
advocating minCardinality.  So, assuming no objections, let's fix this 
in the 1.2 release.

Regards,
David
Received on Wednesday, 5 January 2005 05:14:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 16 March 2008 00:10:59 GMT