- From: David Martin <martin@ai.sri.com>
- Date: Mon, 05 May 2003 18:45:11 -0700
- To: Daniel Elenius <danel698@student.liu.se>
- CC: www-ws@w3.org
Daniel - The new soon-to-be-announced release changes the range of damlsParameter to be a new class called ParameterPowerSet. I think this will clear up the error you noted with JTP (but I haven't actually tried it). Regards, David Martin Daniel Elenius wrote: > Hi! > > In Grounding.daml, "damlsParameter" is defined as follows: > > <daml:ObjectProperty rdf:ID="damlsParameter"> > <rdfs:comment> > An input or output property of an atomic process. > </rdfs:comment> > <rdf:type > rdf:resource="http://www.daml.org/2001/03/daml+oil#UniqueProperty"/> > <rdfs:domain rdf:resource="#WsdlMessageMap"/> > <rdfs:range rdf:resource="&process;#parameter"/> > </daml:ObjectProperty> > > This implies that "&process;#parameter" must be a Class, right? > But in Process.daml we find: > > <daml:Property rdf:ID="parameter"> > <rdfs:domain rdf:resource="#Process"/> > <rdfs:range > rdf:resource="http://www.daml.org/2001/03/daml+oil#Thing"/> > </daml:Property> > > So, parameter is a Property. What gives? (This gives me an error in JTP, > and that's what I'm trying fix). > > I can see that the idea is that the damlsParameter should point to an > input/ouput in the process model. I can't see a simple solution though. > Perhaps the easiest thing to do is to have the range of damlsParameter > be "&daml;#Thing" > > Have I misunderstood something? > > Regards, > Daniel
Received on Monday, 5 May 2003 21:49:50 UTC