Equivalency

• From: Jeffrey Winter <JeffreyWinter@crd.com>
• Date: Wed, 11 Oct 2006 10:59:04 -0400
• To: <uri@w3.org>
• Message-ID: <8307A034380BA347970711A07267275A0D5989@mail3.crd.com>

Nowhere does the spec define what constitutes equivalent
URI templates.  Does

  http://example.org/{a} == http://example.org/{b} 

for example?  Barring any further type annotations
to {a} and {b}, one would have to assume that is does.

An explicit rule would allow for validation where
URI templates are used, like WADL.  This would
seem to be a pathological condition:

<application 
 	xmlns="http://research.sun.com/wadl/2006/07">
  <resources base="http://example.org/">
    <resource path="{a}">
      <method href="#one"/>
    </resource>
    <resource path="{b}">
      <method href="#two"/>
    </resource>
  <resources>
  ...
</application>

Given the URI templates implied, there's no
way to determine which method to dispatch to.  With
a defined notion of URI template equivalency, a
validation rule could be defined for WADL processing.

- Jeff

Received on Wednesday, 11 October 2006 14:59:20 UTC