Re: Dropping WSDL RDF mapping of unknown extensions?

Eric Prud'hommeaux <[email protected]> Thu, 15 Mar 2007 15:57:46 -0400
Newsgroups gmane.comp.web.services.description
Organization World Wide Web Consortium (W3C) - http://www.w3.org/
Message-ID <[email protected]>
* Jacek Kopecky <[email protected]> [2007-03-12 22:10+0100]
> Hi Eric,
> a long time ago, you raised the comments that the WSDL RDF mapping [1]
> should use canonicalization for the parts that stay XML, i.e.
> documentation and optional extensions, both element and attribute. After
> all the time, I'm now considering whether those parts are really (in any
> way) useful parts of the RDF form of WSDL. 
> 
> Both documentation and unknown optional extensions can be happily
> ignored in WSDL, and I'm concerned now that canonicalization would be
> undue burden on RDF mapping implementations, with no discernible benefit
> (AFAICS).

My first reflex to the request is "why drop it", but my first reflex
to your suggestions is "he must have a good reason".

Does the mapping actually produce much burden? I think sawsdl is a use
case *for* it. We defined a graph representation of the SAWSDL
attribute, but if we had relesed the mapping first, folks might have
implemented sawsdl entirely in RDF, counting on the generic mapping to
give them what they need to access these new-fangled SAWSDL
attributes.

OTOH, maybe this use case does not justify the added cost. What *is*
that cost?

> What do you think about just plain dropping these parts altogether? 
> In the WSDL RDF mapping document this would mean that the second half 
> of section 2.2.1 and the whole section 2.2.2 would disappear.
> 
> Please let me know of your opinion, (and anybody else on the WS-Desc WG
> list will be welcome to chime in),
> 
> Jacek
> 
> [1] http://www.w3.org/TR/wsdl20-rdf/
> 
> 

-- 
-eric

office: +1.617.258.5741 NE43-344, MIT, Cambridge, MA 02144 USA

([email protected])
Feel free to forward this message to any list for any purpose other than
email address distribution.
signature.asc (application/pgp-signature, 481 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBRfmlOpZX2p1ccTnpAQI3Jgf/Q+zrXRml6kHXH1T4/y44lWcVIrnKZZs6
7+ABM/MqpLUykz5zNfrHVCtQA3ghamf9FNcjgu7UZId4GN0OpEVkUsDX2JTKQmau
AoQzPCDEPknoTyUHGAVZX67eCvoX2iZnQuTIttjmYuLlDtTfbYQnviQJ1XgDZSUU
bdnRXZ0XIVznqys4DR8rpr8X57NwAZht03x6mpGsCcNZfB3fIxG/c2ge6zi96cwx
HSWidpyGpZdWi8wgRS26NAl4LIp0LfFolf0EhJcBtfFTI7r02arUutfo5VeKuegY
RFj/Dpns9isOyceX8siKfcpejOfhO7bJaDNj092RN5dtGfXzHanhGg==
=ealQ
-----END PGP SIGNATURE-----