Hi,
I have some points to put forward:
I have read the mail from Dean regarding instance Vs class representation
and I think that the instance definition format is quite appealing and
straightforward as Dean pointed out. I would like to have some clarification
though on the PAC-3 pros as defined in Dean's mail, regarding the fact that
the class defintion format provides instances as "execution traces" (and
their relationship to processes) "for free"Now for some other issue regarding the files CongoProcess.daml and
CongoProcessDataFlow.daml. The property fullCongoBuyBookISBN seems to me as
being used as a property in CongoProcessDataFlow.daml,
<process:sameValues rdf:parseType="daml:collection">
<process:ValueOf process:atClass="#FullCongoBuy"
process:theProperty="#fullCongoBuyBookISBN" />
though I think the property to use in this case would be
<daml:Property rdf:ID="fullCongoBuyBookISBNOutput">
and it is also referenced as being a Class since it is used as follows in
CongoProcess.daml
<daml:Restriction>
<daml:onProperty
rdf:resource="http://www.daml.org/services/daml-s/0.9/Process.daml#coOutput"
/>
<daml:toClass rdf:resource="#fullCongoBuyBookISBN" />
</daml:Restriction>
A similar discrepancy seems to exist the owl-s versions. Or maybe I am
missing something?
Regards,
Charlie
-------------------------------------------------
Charlie Abela
Research Student,
Dept. of Computer Science and AI
University of Malta,
MSD06. Malta
Web: http://alphatech.mainpage.net
Email: abcharl@keyworld.net