RE: Service discovery formats

["Danny Ayers" <danny666@xxxxxxxxxxx>]

> The purpose of discovery is so the client can find the service. Which
> of these formats have good client support? WSDL does; if you flesh out
> that WSDL document with a description of the Atom API format, then
> your Java, .NET, and Perl code is magically written for you. Client
> programmers no longer need to look at the XML at all: they just say
>   "wsdl.exe http://www.blogengine.com/API.wsdl";
> and *poof* they have a .NET client with methods like
>   createPost(String author, String entry, ...)

That could be rather a big plus for encouraging adoption!

> Do any of the other discovery formats have similar client support?

I hadn't looked for a long while, but there does appear to be growing
support for the RDF alternative (as DAML-S), but most of these tools seem to
make use of WSDL anyway, maybe it might be an idea to leave the RDF version
as an optional extra.
http://www.daml.org/services/tools.html
http://www.mindswap.org/~evren/composer/

re. RSD - have to ask Mr.Berlinger.
re. RDDL - have to ask Mr. Bray.
re. AtomAPI - have to ask Mr. Gregorio ;-)

Cheers,
Danny.