14:01:16 RRSAgent has joined #awwsw 14:01:16 logging to http://www.w3.org/2009/11/24-awwsw-irc 14:01:32 Zakim has joined #awwsw 14:01:38 zakim, this will be awwsw 14:01:38 ok, dbooth; I see TAG_(AWWSW)9:00AM scheduled to start now 14:02:00 TAG_(AWWSW)9:00AM has now started 14:02:07 +DBooth 14:03:04 jar_ has joined #awwsw 14:03:07 hi 14:03:27 Meeting: AWWSW 14:03:31 writing email to http-wg about GET... 14:03:43 i'll be on phone in about 2 minutes 14:05:52 regrets: michael 14:06:02 + +1.781.643.aaaa 14:06:24 zakim, aaaa is jar 14:06:24 +jar; got it 14:07:04 http://esw.w3.org/topic/AwwswHome/DraftReport 14:13:22 201 CREATED only meaningful with PUT 14:13:40 or maybe POST? 14:16:30 use case: How one would use RDFa to express the choices provided in a 300 response? 14:17:26 i/Writing/Topic: Draft Report 14:17:53 i.e. 300 responses currently have to be parsed manually - there's no standard way to express choices 14:19:03 issue: how to express what 301 ways. We have URIs A and B, one obvious option is owl:sameAs . 14:19:03 Created ISSUE-1 - How to express what 301 ways. We have URIs A and B, one obvious option is owl:sameAs . ; please complete additional details at http://www.w3.org/2007/awwsw/tracker/issues/1/edit . 14:19:59 another option to invent a relationship relating and ... that would be useless 14:20:14 the only other information is that the URI "B" is preferred to the URI "A" 14:20:32 that is something we say about the URIs, not about the resources. 14:20:56 The right option may depend on one's desired granularity of modeling. 14:21:11 [a ht:UriPreference; ht:lessPreferred "A"^^xsd:anyURI; ht:morePreferred "B"^^xsd:anyURI.] 14:24:35 "The requested resource has been assigned a new permanent URI and any 14:24:35 future references to this resource SHOULD use one of the returned 14:24:35 URIs." 14:25:09 302 The requested resource resides temporarily under a different URI. 14:25:30 We don't know what a "residence" is. 14:27:37 We have target = A, redirect to B 14:27:52 What is the relation between and ? 14:28:34 issue: What is a "residence"? (302) 14:28:34 Created ISSUE-2 - What is a "residence"? (302) ; please complete additional details at http://www.w3.org/2007/awwsw/tracker/issues/2/edit . 14:29:36 I wanted to say: You can use the URI "B" to get information about the resource . 14:29:56 Stuart disagreed, he said that the "identifies" relation is what changes over time. 14:33:46 an interpretation of the URIs in a graph is most useful when it's consistent, i.e. one URI/one resource 14:35:12 so if you want to use in an RDF graph, you need to develop a theory of that resource (a set of Correspondences, etc.) that's resilient to the vagaries of all the 302s you'll get over time 14:35:42 that's why I see 302 and 307 as ways to get additional evidence of the nature of 14:35:48 and is really irrelevant 14:36:07 will have its own theory. 14:36:42 my theory is that the entity you get from GET "B" corresponds to 14:37:35 if it didn't, why would the server be telling you to do GET "B"? 14:38:32 If GET "A" -> 302 "B", and GET "B" -> 200 E, then E corresponds to both A and B (at the present time) 14:38:50 both and 14:39:30 http spec determines cachability of the 302 response 14:41:02 later, the 302 may have expired, and B's representations no longer correspond to A 14:41:35 this is how I think "resides at" *has* to be interpreted, to produce useful RDF. 14:42:23 "useful" = in conjunction with existing RDF & OWL semantics 14:47:24 307 is the same as 302 AFAIK... 307 means "I mean 302 as speced, not as usually implemented, which is like 303" 14:49:03 http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-08#section-8.3.3 14:49:50 RESOLVED: we will use httpbis 10/26 draft for reference, not RFC 2616 14:50:41 David: That sounds good for 302. 14:54:12 I really don't agree with: "A 303 response to a GET request indicates that the requested resource 14:54:12 does not have a representation of its own that can be transferred by 14:54:12 the server over HTTP." 14:55:29 the word "can" is the hedge word 14:56:20 ... but then how is "can" different from "doesn't"? 14:58:07 So GET "A" -> 303 "B" becomes powder:describedBy 14:58:22 which is what my shell script does 14:59:06 IAO has its own "is about" relation 14:59:32 IAO = Information Artifact Ontology, a big effort in OBO foundry 14:59:35 http://code.google.com/p/information-artifact-ontology/ 15:00:03 David: That looks good for 303 also. 15:01:08 304 asserts additional information (holdsUntil) on a previously known Correspondence 15:01:55 C toRepresentation R. C heldAt T1. 304 => C heldAt T2. 15:02:09 holdsAt 15:02:14 whatever 15:02:27 -DBooth 15:02:31 -jar 15:02:32 TAG_(AWWSW)9:00AM has ended 15:02:33 Attendees were DBooth, +1.781.643.aaaa, jar 15:02:37 rrsagent, make logs public 15:02:45 rrsagent, pointer 15:02:45 See http://www.w3.org/2009/11/24-awwsw-irc#T15-02-45 15:02:48 rrsagent, draft minutes 15:02:48 I have made the request to generate http://www.w3.org/2009/11/24-awwsw-minutes.html dbooth 15:03:24 Chair: Jonathan Rees (jar) 15:03:37 Present: Jonathan Rees, David Booth 15:04:10 i/writing email/Topic: Draft Report 15:04:34 s|i/Writing/Topic: Draft Report|| 15:04:59 rrsagent, draft minutes 15:04:59 I have made the request to generate http://www.w3.org/2009/11/24-awwsw-minutes.html dbooth 16:17:09 jar_ has joined #awwsw 16:33:28 Zakim has left #awwsw 16:45:34 mhausenblas has joined #awwsw