Why not use a link in the representation to provide the URI via which the description can be accessed?
First, this requires that you download the entire representation to get to that link, which is simply inefficient. Secondly, the insertion of the link would be encoding specific and not all encodings facilitate such links. Thirdly, the solution would not be consistent across all encodings, and for each new encoding, yet another way to embed/encode that link would have to be devised. Finally, it precludes processing of descriptions by agents who do not support the particular encodings yet can still operate on RDF/XML descriptions.
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 a link in the representation to provide the URI via which the description can be accessed?
- Why not use DDDS (DNS) to get another URI via which the description can be accessed?
