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?
This is a variant of the OPTIONS approach above which does not violate the sanctity of the web authority’s namespace as would a more general syntactic transformation, as each web authority is free to specify their own transformation as they see fit. It shares, though, the shortcomings of the other OPTIONS approach in that it incurs multiple requests and requires explicit identity of all descriptions. It also has the additional drawback of placing both a greater implementational burden as well as a heavier runtime burden on clients in that they will have to be able to apply the transformations locally. Such concerns are particularly relevant for mobile clients.
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?
- Can I order the basic North Frontier™ SCBA with any options, like ones that are standard on the regular North Frontier™ SCBA?
