Lists Home |
Date Index |
Thanks for information. We were not aware of the WS-Inspection effort.
The defined format looks interesting and bears watching. I am not a
fan of the publication/discovery method they describe in section 6
however. As I'm sure you realize we specifically crafted our
architecture so that it could support efforts like this, RDDL and other
metadata aggregation formats without having to choose a winner.
WS-Inspection asks users to look around the interested URL for an
inspection.wsil document. This feels messy and error prone because the
standard does not guarantee where to find the document but instead asks
the publisher to scatter the inspection document to whereever they think
a user might look for it. Of course it also presumes that a wsil
document is THE answer.
Thanks for your comments,
Chiusano Joseph wrote:
>Regarding the following point from the web page:
>Services may be described in many ways - using XHTML, WSDL, RDF, DAML,
>OWL, etc. The registry architecture must support these various formats.
>You may want to consider tracking the WS-Inspection (Web Services
>Inspection Language) specification written by IBM and Microsoft:
>This is considered part of Microsoft's Global XML Web Services
>Architecture (GXA), of which WS-Security (now under OASIS) is a part.
>Some additional points:
>- WS-Inspection provides an XML format for assisting in the inspection
>of a site for available services and a collection of rules for how
>inspection-related information should be made available for consumption;
>- A WS-Inspection document provides a means for aggregating references
>to pre-existing service description documents which have been authored
>in any number of formats;
>These inspection documents are then made available at the
>point-of-offering of the service as well as through references which may
>be placed within a context medium such as HTML;
>Booz | Allen | Hamilton