Re: [Fwd: SAWSDL]

Hi all,

after discussing it a while with Jack I think we do not need a specific
piece of XML for this purpose. Here the line of argumentation:

a) We also need to provide a mechanism to annotate external WSDL files
(WSDL import mechanism) this can be either the case if someone
implements a specific porttype (interface) defined by someone else or if
a third party wants to add some annotations to a WSDL (assuming some
kind of registry that adds categorization information).

b) thinking about what we want to annotate (especially for the WSDL
case) we do want to annotate components (e.g. the "order" operation in
the "Order" interface) and not the first "wsdl:operation" occurrence
within a "wsdl:interface". In exact we want to say something about
components and not about their syntactic encoding.

b1) There might be changes to the XML representation of the components
that do not change the the meaning of the WSDL (e.g. flipping the order
in which operations are defined), but might break a specific xpath
statement.

b2) WSDL WG is already working on URIs that identify a specific
operation (e.g. the "order" operation in the "Order" interface):
http://www.w3.org/2002/ws/sawsdl/spec/wsdl/order#wsdl.interface(Order,wsdl.interfaceOperation(order))
(or something like this, Jacek will correct me here)

Similar to WSDL WG also XML Schema WG defines URI which exactly define
components.

c) Following this argument, XPath might not be the best way to annotate
some external component (WSDL or XSD), instead a URI (component
identifier) can be used. This would lead an XML similar to:

<sawsdl:externalModelReferene
sawsdl:component="http://www.w3.org/2002/ws/sawsdl/spec/wsdl/order#wsdl.interface(Order,wsdl.interfaceOperation(order))"
sawsdl:modelReference="http://www.w3.org/2002/ws/sawsdl/spec/ontology/purchaseorder#Order"/>

This essentially boils down to annotate a URI with a property. This in
turn is exactly what RDF does. Thus we could achieve the same by not
defining a new XML Element, but by reusing the RDF syntax we defined,
leading to a triple like:

http://www.w3.org/2002/ws/sawsdl/spec/wsdl/order#wsdl.interface(Order,wsdl.interfaceOperation(order))
sawsdl:modelReference
http://www.w3.org/2002/ws/sawsdl/spec/ontology/purchaseorder#Order

I would argue for explaining this use of rdf, instead of introducing a
new element.

best
  Holger

Jacek Kopecky wrote:
> Hi all, Karthik has sent a proposal for external annotations in SAWSDL,
> see the attached MS Word document.
> Jacek
> 
> -------- Forwarded Message --------
> From: Karthik Gomadam <karthik.gomadam@gmail.com>
> To: Jacek Kopecky <jacek.kopecky@deri.org>, Amit Sheth @ LSDIS
> <amit@cs.uga.edu>
> Subject: SAWSDL
> Date: Mon, 11 Dec 2006 21:04:57 -0500
> 
> Hi Jack,
> Please find the SAWSDL document attached.
> 

-- 
Holger Lausen

Digital Enterprise Research Institute (DERI)
http://www.deri.org/

Tel:   +43 512 5076464
Mail: holger.lausen@deri.org
WWW: http://holgerlausen.net