- From: <noah_mendelsohn@us.ibm.com>
- Date: Tue, 3 Jan 2006 18:45:46 -0500
- To: Norman Walsh <Norman.Walsh@Sun.COM>
- Cc: www-tag@w3.org
Norm: I think these minutes are mostly good, but there are two corrections that I believe necessary to get the sense of what I said on the call: <asMinuted> NM: My definition of an information resource leaves open the possibility that our httpRange-14 resolution allows me to return 200 for the namespace document. I </asMinuted> <shouldBe> NM: My definition of an information resource leaves open the possibility that our httpRange-14 resolution allows me to return 200 for the namespace itself. </shouldBe> I think we've agreed that there is so far no consensus among the TAG as to exactly what a namespace is, but I think there are at least some potential definitions that meet the Arch Doc. definition of an information resource [1]. Accordingly, my point was specifically that our resolution to httpRange-14 >might< be taken to license a 200 status code, as opposed to 302, for retrieval of the namespace itself. <asMinuted> NM: Information resource is either a synonym of document or very close document. I </asMinuted> <shouldBe> NM: My understanding is that Tim takes the view that "information resource" is either a synonym of document or very close</shouldBe> I understand that Tim prefers to use the term "document" to include everything that meets the definition of an info resource, and I'm still feeling that there are some important info resources that don't fit my commonsense associations with the word "document". In the end, that's just a discussion of exactly which definition we adopt for the word "document", since I think there is agreement on what info resource means. The scoping of the term "document" is a discussion we should indeed have at some point. I think my first point above holds in any case. I'd be grateful if you would edit the minutes. Thank you. Noah -------------------------------------- Noah Mendelsohn IBM Corporation One Rogers Street Cambridge, MA 02142 1-617-693-4036 --------------------------------------
Received on Tuesday, 3 January 2006 23:45:59 UTC