W3C home > Mailing lists > Public > www-tag@w3.org > October 2007

RE: Resources and representations (was RE: Subgroup to handle semantics of HTTP etc?)

From: Pat Hayes <phayes@ihmc.us>
Date: Wed, 24 Oct 2007 11:30:14 -0500
Message-Id: <p06230904c345235a73b8@[10.100.0.19]>
To: "Booth, David (HP Software - Boston)" <dbooth@hp.com>
Cc: "Williams, Stuart (HP Labs, Bristol)" <skw@hp.com>, "wangxiao@musc.edu" <wangxiao@musc.edu>, W3C-TAG Group WG <www-tag@w3.org>, Alan Ruttenberg <alanruttenberg@gmail.com>, Jonathan A Rees <jar@mumble.net>, Dan Connolly <connolly@w3.org>, Tim Berners-Lee <timbl@w3.org>

>  > From: Williams, Stuart (HP Labs, Bristol)
>>  [ . . . ]
>>  The HTTP range question simply asks what sort of things can
>>  an HTTP URI refer to?
>>  And the answer given is 'any kind of thing' (whether or not
>>  their is a '#' in the spelling of the URI).
>
>True, but to be clear, the WebArch also imposes some additional 
>constraints that depend on: (a) what kind of resource is denoted; 
>and (b) the media type returned when the URI is dereferenced.  In 
>particular:
>
>  - If the URI denotes a non-information resource and the URI has a 
>fragment identifier and a 200 response is returned when the racine 
>(the part before the '#') of the URI is dereferenced, then the media 
>type returned must be a media type that permits its fragment 
>identifiers to denote arbitrary resources.   For example, you may 
>return RDF but *not* (currently) HTML, because the media type for 
>RDF permits a fragment identifier to denote anything, whereas in 
>HTML a fragment identifier denotes a location within the document.

Does the HTML spec mention denotation?

Pat
-- 
---------------------------------------------------------------------
IHMC		(850)434 8903 or (650)494 3973   home
40 South Alcaniz St.	(850)202 4416   office
Pensacola			(850)202 4440   fax
FL 32502			(850)291 0667    cell
phayesAT-SIGNihmc.us       http://www.ihmc.us/users/phayes
Received on Wednesday, 24 October 2007 16:30:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:18 UTC