process:sameValues redefined

Hi,

regarding the issue raised in 
http://lists.w3.org/Archives/Public/www-ws/2003Mar/0019.html, I would like 
to make a suggestion for enhancing the concept behind 'process:sameValues'. 
  According to my idea, we may express a statement like (cp. 
http://www.daml.org/services/owl-s/0.9/CongoProcessDataFlow.owl):

   <process:sameValues rdf:parseType="Collection">
     <process:ValueOf process:atClass="#FullCongoBuy"
                      process:theProperty="#fullCongoBuyBookName"/>
     <process:ValueOf process:atClass="#LocateBook"
                      process:theProperty="#bookName"/>
   </process:sameValues>

this way (the new property and class names are supposed to come from the 
'process' ontology):

   <process:dataFlow>
     <process:ValuePipe>
       <process:source>
         <process:ValueOf process:atClass="#FullCongoBuy"
              process:theProperty="#fullCongoBuyBookName"/>
       </process:source>
       <process:sink>
         <process:ValueOf process:atClass="#LocateBook"
                        process:theProperty="#bookName"/>
       </process:sink>
       <process:pipes rdf:resource="&process;allValues"/>
     </process:ValuePipe>
   </process:dataFlow>

This would make it possible to define another alternative for 
'process:pipes', namely "&process;someValues" which would solve my problem 
with restricting input depending on output.

Could this be used as an initial idea for enhancing DAML-S in terms of 
dealing with data flow?

Regards,

-- Saied Tazari

P.S. I wonder if we could rewrite the above in the following abbreviated form:

   <process:dataFlow>
     <process:ValuePipe>
       <process:source rdf:resource="#FullCongoBuy.fullCongoBuyBookName"/>
       <process:sink rdf:resource="#LocateBook.bookName"/>
       <process:pipes rdf:resource="&process;allValues"/>
     </process:ValuePipe>
   </process:dataFlow>

Received on Monday, 19 May 2003 12:40:16 UTC