- From: Jonathan Borden <jonathan@openhealth.org>
- Date: Tue, 2 Jul 2002 10:32:23 -0400
- To: "Graham Klyne" <GK@NineByNine.org>, <www-tag@w3.org>, "Paul Grosso" <pgrosso@arbortext.com>
Paul Grosso wrote: > > But can an application such as RDF redefine the semantic of > an embedded URI reference in such a way that it predetermines > (overrides) the MIME type of the referenced resource regardless > of how the resource is labeled? > > And if it can't, then RDF cannot redefine how to interpret the > fragment identifier; rather, the fragment identifier must be > interpreted according to how the MIME type says it should. Presumably the "referenced resource" doesn't itself have a MIME type, rather the MIME type is assigned during the process of returning a representation of the resource back to the user agent which is resolving a URI. In RDF, there is no such URI resolution going on. Given an arbitrary URI reference which is just sitting there (i.e. as a string) how can one interpret the fragment identifier w.r.t the URI when there is no MIME type? (Remember: the URI is not being resolved.) Jonathan
Received on Tuesday, 2 July 2002 10:37:59 UTC