If one is willing to accept that there may possibly be value in having
mixed human/machine-readable content at the end of a namespace-URI, RDDL
looks like a pretty good tool.
There was some discussion at XML 2001 about ways to improve RDDL, and
they seemed to come from two related directions:
1) Creating clusters of resources rather than a flat list
2) Describing sequences for resource processing to define pipelines
In some ways these are the same thing, just with sequence mattering in
the second version.
I think it's roughly possible to do these using current RDDL syntax, but
I suspect it might be worth some further exploration of how best to make
these work. Number 2 in particular could take RDDL much deeper into
computer interactions than has typically been the case so far.
Thoughts?
--
Simon St.Laurent
Ring around the content, a pocket full of brackets
Errors, errors, all fall down!
http://simonstl.com
