W3C home > Mailing lists > Public > www-ws@w3.org > April 2003

Re: BravoAir/CongoBuy grounding question

From: David Martin <martin@ai.sri.com>
Date: Fri, 11 Apr 2003 04:34:41 -0700
Message-ID: <3E96A851.BEF8100@ai.sri.com>
To: www-ws@w3.org

Daniel Elenius wrote:

> Hi!
> I just spotted a thing that's done differently in these two files, and I
> want to know which one is the recommended style.
> In CongoGrounding.daml, all URIs to entities defined in the WSDL file
> are referenced by plain URI, for example:
> <grounding:wsdlOperation>
>    &congo_wsdl_grounding;#CongoBuy
> </grounding:wsdlOperation>
> But in BravoAir, it's done like this:
> <grounding:wsdlOperation>
>   <xsd:uriReference
> rdf:value="&BravoAirGroundingWSDL;#GetDesiredFlightDetails..."/>
> </grounding:wsdlOperation>
> The latter one has the advantage that DAMLvalidator doesn't complain...
> So, which style should I use?

Thanks for pointing this out.  The use of <xsd:uriReference = ....> is

Note, however, that in our upcoming release, this will change to
in accord with the more recent release of XML Schema.

> I also have another question. I note that in both these examples, each
> atomic process gets its own Port type in the wsdl grounding. Is this a
> requirement (for some reason) or can I have just one port for the whole
> service (say, a "Printer" service with different methods) and operations
> within that port for the different methods (like, "print document",
> "print test sheet", "set configuration")?

Sure, you can do it that way; no problem.

David Martin

> The reason I'm asking is because I'm creating my WSDL grounding based on
> what Apache Axis' Java2WSDL utility produces, and it uses the latter
> style (where the Port = the Java Class, and each operation = a Java
> method within that class).
> Regards,
> /Daniel
Received on Friday, 11 April 2003 07:33:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:37:08 UTC