- From: Drew McDermott <drew.mcdermott@yale.edu>
- Date: Thu, 17 Apr 2003 21:44:19 -0400 (EDT)
- To: martin@ai.sri.com
- CC: marta@cs.vu.nl, www-ws@w3.org
Date: Wed, 09 Apr 2003 20:10:55 -0700
X-PH: V4.4@mr1
From: David Martin <martin@ai.sri.com>
X-Accept-Language: en
Cc: www-ws@w3.org
X-OriginalArrivalTime: 10 Apr 2003 03:06:41.0718 (UTC) FILETIME=[35CF0560:01C2FF0E]
X-Archived-At: http://www.w3.org/mid/3E94E0BF.BB43D2DD@ai.sri.com
Resent-From: www-ws@w3.org
X-Mailing-List: <www-ws@w3.org> archive/latest/653
X-Loop: www-ws@w3.org
Sender: www-ws-request@w3.org
Resent-Sender: www-ws-request@w3.org
X-YaleITSMailFilter: Version 1.0c (attachment(s) not renamed)
Marta Sabou wrote:
> Does anybody have some completed examples of defining complex datatypes?
Well, everything in these examples is admittedly quite simple and contrived, but you can look at SignInData, AcctInfo, and CreateAcctOutputType in CongoProcess.daml.
In general, you are not limited to looking at the DAML-S examples, because any DAML+OIL class can be used as the type of an input or output of a process.
Another way to put the same point is that you're still in the
RDF(S)[+OWL] world when you're in DAML-S. You can define records,
classes, and such as you always would
--
-- Drew McDermott
Received on Thursday, 17 April 2003 21:44:25 UTC