<feed xmlns="http://www.w3.org/2005/Atom" xmlns:foaf="http://xmlns.com/foaf/0.1/"><title>norman.walsh.name: Comments on /2003/12/12/housekeeping</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2003/12/12/housekeeping"/><id>http://norman.walsh.name/2003/12/12/housekeeping/comments.atom</id><updated>2012-02-13T09:07:58.038169Z</updated><entry><title>Comment 1 on /2003/12/12/housekeeping</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2003/12/12/housekeeping#comment0001"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0001</id><published>2003-12-14T20:47:30Z</published><updated>2003-12-14T20:47:30Z</updated><author><name>John Clark</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>I&amp;apos;d like to ask for a feed covering all of the "Technology" topic - I&amp;apos;m very interested in many of the different subtopics, which I think are nicely encapsulated by the parent topic.</p>
  </div></content></entry><entry><title>Comment 2 on /2003/12/12/housekeeping</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2003/12/12/housekeeping#comment0002"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0002</id><published>2003-12-15T15:24:51Z</published><updated>2003-12-15T15:24:51Z</updated><author><name>Ed Davies</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>I think TBL &amp;amp; DanC&amp;apos;s comment is absolutely correct.  However, the interesting question is: did they suggest any other mechanism to get to the metadata?</p>
<p>I&amp;apos;ve just read the Architecture of the World Wide Web, First Edition and can find no clues there.  I wonder if maybe an HTTP
GET-META message or something should be created.</p>
  </div></content></entry><entry><title>Comment 3 on /2003/12/12/housekeeping</title><link rel="alternate" type="text/html" href="http://norman.walsh.name/2003/12/12/housekeeping#comment0003"/><id>http://norman.walsh.name/2010/09/25/oauth#comment0003</id><published>2003-12-18T05:23:53Z</published><updated>2003-12-18T05:23:53Z</updated><author><name>David Menendez</name><foaf:mbox_sha1sum>da39a3ee5e6b4b0d3255bfef95601890afd80709</foaf:mbox_sha1sum></author><content type="xhtml"><div xmlns="http://www.w3.org/1999/xhtml">
    <p>I agree with Dan C. and Tim B.L. that a description of an essay is a different resource from the essay itself, but I don&amp;apos;t think it follows that you therefore can&amp;apos;t do content negotiation.</p>
<p>If these essays had (say) French translations, you would want to provide URIs for (1) the essay, (2) its English version, and (3) the French version. A request for (1) would return the same material as (2) or (3) depending on the language preferences of the server and client. The server indicates that (2) or (3) is being returned through the Content-Location header.</p>
<p>GET always returns a representation of a resource. If someone tries to GET this essay and says they want RDF/XML, why not send them the metadata? The Content-Location header makes it clear that the data being returned has its own identity in addition to representing the essay in some manner, and the data itself would probably describe that relation.</p>
  </div></content></entry></feed>

