One of the features added to WADL in the latest revision of the specification was the ability to embed parameters in resource path definitions. E.g., the following describes a set of resources identified by a parameterized URI:
<resources base="http://example.com/">
<resource path="applications/widgets/{widget_id}">
...
</resource>
<resources>
The above extract...
