- From: Pat Hayes <phayes@ihmc.us>
- Date: Wed, 10 Jun 2009 08:18:03 -0500
- To: Alan Ruttenberg <alanruttenberg@gmail.com>
- Cc: Jonathan Rees <jar@creativecommons.org>, noah_mendelsohn@us.ibm.com, AWWSW TF <public-awwsw@w3.org>, "Williams, Stuart (HP Labs, Bristol)" <skw@hp.com>
On Jun 9, 2009, at 4:45 PM, Alan Ruttenberg wrote: >> Why not, "can emit a response to some kind of access protocol" ? >> That seems >> to handle all the present and all the likely future cases, be >> unambiguous, >> and (by philosophical standards) vividly clear and unambiguous. And >> it has >> the great merit of talking about the **actual resource** rather >> than an >> awww:representation of it, which (latter) is what gets conveyed in >> messages, >> in fact. > > What does "can emit a response to some kind of access protocol" > the answer to? > Notably, it doesn't include things like text files with html in them. > Right, and a text file with html in it cannot "be on the web" either, unless it is somehow incorporated into something larger that CAN respond to a transfer protocol request; and then, that larger (in some appropriate sense...) thing is what is actually on the Web, is involved with Web architecture, is a REST resource, etc. etc.. If bare text files were on the Web, you could read my hard disc from where you are sitting now. Pat > -Alan > > ------------------------------------------------------------ IHMC (850)434 8903 or (650)494 3973 40 South Alcaniz St. (850)202 4416 office Pensacola (850)202 4440 fax FL 32502 (850)291 0667 mobile phayesAT-SIGNihmc.us http://www.ihmc.us/users/phayes
Received on Wednesday, 10 June 2009 13:19:36 UTC