Lists Home |
Date Index |
email@example.com (Chris Wilper) writes:
>The concept is an API. If it has a URI, great. If it can be
>resolved, excellent. If I get a choice as to what representation of
>the resource I want, even better.
>I'm not sure RDDL is the right thing, as currently scoped
>as a "namespace document" -- but the idea of a resolved URI
>providing an index of descriptive representations of
>a concept/resource ... is appealing.
Interesting, though I'll admit that I cringe any time people map XML
vocabularies directly to APIs.
Is answering Simon Fell's original question about roles  enough to
deal with this, or is something more powerful needed?
I guess I can see RDDL pointing to "here's how to process this stuff"
via WSDL, but worry that WSDL itself specifies something larger than
RDDL, as most Web Services I've seen involve interactions between
multiple (and frequently more than 2) namespaces.
 - http://lists.xml.org/archives/xml-dev/200103/msg00171.html
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com -- http://monasticxml.org