Why not have a standardized suffix, prefix, or other URI transformation that allows one to derive from a resource URI another URI via which the resource description can be accessed?
Such an approach both violates the sanctity of the web authority’s URI space, since an agent has no way of knowing whether the web authority subscribes to such a transformation. It also violates the principle of URI opacity. Finally, such a transformation would have to work with any URI scheme whatsoever, which may very well not be feasible.
Related Questions
- Why not have a standardized suffix, prefix, or other URI transformation that allows one to derive from a resource URI another URI via which the resource description can be accessed?
- Why not use OPTIONS to get the definition of a regular transformation to apply to the resource URI in order to generate another URI via which the description can be accessed?
- Why not use DDDS (DNS) to get another URI via which the description can be accessed?
