[
Lists Home |
Date Index |
Thread Index
]
On Thu, 24 Apr 2003, Norman Walsh wrote:
> | Are there any efforts to
> | formalize other semantics for the field, for example as a way of specifying
> | alternative resolution strategies for the system identifier?
>
> Does it really make sense to put those resolution strategies in the
> document?
No, especially if they are prescriptive, in which case they probably belong
in a processing instruction.
I'm thinking of anything that an application might need to know about the
nature of an entity, which is difficult to communicate in a URI. For
example: this entity exists in multiple content types, so if you wish, you
may specify one in the accept field of your HTTP request for the entity.
Or: this entity exists in multiple locales, so append an ISO locale code if
you wish, and the best possible match will be returned (in the manner of
Java property files).
// Gregory Murphy <Gregory.Murphy@sun.com>
|
