W3C home > Mailing lists > Public > public-ws-semann@w3.org > November 2006

Comment from Ajith Ranabahu

From: Jacek Kopecky <jacek.kopecky@deri.org>
Date: Sun, 12 Nov 2006 16:01:12 -0500
To: SAWSDL public list <public-ws-semann@w3.org>
Message-Id: <1163365272.3791.17.camel@localhost>

Hi all, 
this is a comment from Ajith Ranabahu, will become Last Call issue 13.
The use case here is that one might want to import a third-party XML
Schema and annotate it using a private ontology, therefore Ajith asks
for external annotations.
Best regards,
Jacek


-------- Original Message --------
Subject: 	Re: [Fwd: SAWSDL Spec is now frozen for F2F]
Date: 	Wed, 8 Nov 2006 10:39:54 -0500
From: 	Ajith Ranabahu <ajith.ranabahu@gmail.com>
To: 	Amit Sheth <apsheth@bellsouth.net>
CC: 	DOUGLAS CARL BREWER <twisted@uga.edu>, Karthik Gomadam 
<karthik.gomadam@gmail.com>, Kunal Verma <kunal.verma1@gmail.com>
References: 	<4551E6A5.6020206@bellsouth.net>



Hi,
One concern I have is that the schema annotations such as simpletype
and complextype annotations, may limit the usability of certian
schemas. I think I've mentioned this to Dr Sheth once but for the
benifit of others here is an explanation. This is not a *problem* per
se but it seems that to me that if the spec suggests something, more
like a recommended approach on this, it would be better.

The usual practice in the industry is to include/import schemas into
the WSDL documents rather than including them inline. An orgnization
may use  a variety of schemas that are reused in many webservices with
different semantics. This gets complicated further if standard schemas
are included (Say from W3C) which can be used for many different
purposes with different semantics. One can always find a workaround ,
the easiest being copying the schema and annotating the copy , but
that would mean a considerable effort for  porting existing services
(I guess the thinking behind the SAWSDL approach is to minimize the
effort to port existing applications)
If we can come up with an alternative approach that allows the
specification of model references without actually putting the
modereference inside the schema type (the original approach will be
also valid but we suggest an alternate approach also that allows
'external annotations' that can be used to deal with imports and
includes easily)
One way I can thing of this is to have schema level modelreference
entries that has both the Qname and the reference.

Ajith

On 11/8/06, Amit Sheth <apsheth@bellsouth.net> wrote:
> Doug, Ajith:
> If you have comments I would love to hear them.
> Amit
>
>
Received on Sunday, 12 November 2006 21:01:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 17 April 2012 12:14:27 GMT