13:02:12 <RRSAgent> RRSAgent has joined #awwsw
13:02:12 <RRSAgent> logging to http://www.w3.org/2010/05/25-awwsw-irc
13:02:16 <Zakim> Zakim has joined #awwsw
13:02:22 <jar> zakim, this is awwsw
13:02:22 <Zakim> ok, jar; that matches TAG_(AWWSW)9:00AM
13:02:52 <Zakim> + +1.216.445.aaaa
13:04:07 <dbooth2> dbooth2 has joined #awwsw
13:04:27 <jar> zakim, aaaa is dbooth2
13:04:27 <Zakim> +dbooth2; got it
13:04:57 <mhausenblas> heya
13:05:20 <mhausenblas> sorry, bit late (editing RDB2RDF Use Cases for today's meeting ATM)
13:05:27 <mhausenblas> will dial in in a sec
13:05:48 <dbooth2> zakim, who is here?
13:05:48 <Zakim> On the phone I see [CubeSpace], dbooth2
13:05:49 <Zakim> On IRC I see dbooth2, Zakim, RRSAgent, jar, mhausenblas, trackbot
13:06:12 <jar> zakim, cubespace is jar
13:06:12 <Zakim> +jar; got it
13:06:28 <Zakim> +mhausenblas
13:08:37 <jar> dbooth: An update at the TAG F2F would be a good idea
13:08:53 <jar> ... What we've done so far
13:09:00 <jar> ... what the current issues are
13:11:08 <jar> jar: Larry M's confusion about what we're doing
13:11:32 <jar> ... Dan C has prepared an RDF model theory primer
13:11:44 <jar> dbooth: Need motivating examples
13:14:34 <jar> jar: LM has always pushed against use of http: for anything other than HTTP
13:14:56 <jar> mh: People *are* using http: URIs
13:15:05 <jar> mh: e.g. linked data cloud
13:15:12 <jar> dbooth: RDF semantics *permits*
13:15:27 <mhausenblas> http://www.w3.org/TR/rdf-mt/
13:16:51 <jar> jar: But the LOD cloud is mostly # URIs, and mostly not "metadata subjects"
13:17:36 <jar> mh: Let's list the usages in the wild
13:17:42 <jar> mh: Web services?
13:18:07 <dbooth2> dbooth: we should simply stipulate that http uris are used for non-web things.
13:18:16 <mhausenblas>  <soap:binding style="document" transport="http://example.com/smtp"/>
13:18:47 <dbooth2> jar: Also xml namespaces
13:19:13 <jar> db: Can't convince anyone about http: URIs...
13:19:26 <jar> jar: but we could at least maybe convince someone that it's consistent / coherent ?
13:23:12 <dbooth2> dbooth: some outstanding issues: 1. how do URIs become bound to resources as names?  2. What do redirects mean in RDF semantics?  
13:23:49 <jar> how might one treat redirects formally
13:24:08 <dbooth2> dbooth: 3. What kinds of resources should return 200 responses?
13:25:13 <dbooth2> dbooth: 4. Authority in HTTPbis: rfc2616 says 203 response is non-authoritative, but it doesn't define "non-authoritative"
13:28:16 <dbooth2> dbooth: 5. How does an RDF consumer determine what resource is intended to be bound to each URI?
13:29:17 <jar> residesAt(R,U,t)
13:29:21 <dbooth2> jar: http spec talks about a resource residing at a location.  Maybe that can change over time.
13:29:26 <jar> R = resident(U,t)
13:30:35 <jar> X = resident(U,t)    the thing resident at U at time t
13:31:18 <jar> to formulate a GET  asking for W(X, ...)  I need a URI
13:31:28 <jar> so we want a URI U such that X = resident(U,t)
13:32:27 <dbooth2> dbooth: 6. For a given resource, how does one know what URI can be used to access a representation of it?
13:38:19 <jar> 6 is the same as 1
13:39:23 <dbooth2> dbooth: no, #6 is for things that can have representations.
13:39:41 <jar> 6'. For a given resource, how does one choose a URI that can be used to refer to the resource?
13:40:32 <dbooth2> dbooth: In TAG mtg, I think you should point to the draft doc you gave to show what we've done so far.
13:46:38 <jar> for any advice around (3), it would be nice if the advice were justified (as the solution to some real problem)
13:48:08 <jar> dbooth2: for certain things, such as journal articles or books, what kind of URI should be used to name them?
13:52:12 <jar> For those who want to use the 303 hack for a non-IR, does it work to put the 303 URI as the target of a 302 (e.g. from purl.org)?
13:53:21 <mhausenblas> http://lab.linkeddata.deri.ie/alodin/agent/
13:53:51 <jar> GET U1 -> 302 Location: U2,  GET U2 -> 303 Location: U3,   GET U3 -> 200 description of <U1>
13:54:44 <mhausenblas> http://purl.org/NET/dady
13:57:21 <dbooth2> ACTION: jar to draft TAG overview of where the AWWSW group is and what issues we're still facing
13:57:21 <trackbot> Created ACTION-37 - Draft TAG overview of where the AWWSW group is and what issues we're still facing [on Jonathan Rees - due 2010-06-01].
13:57:49 <dbooth2> Meeting: AWWSW
13:57:55 <dbooth2> Chair: Jonathan Rees (jar)
13:58:22 <mhausenblas> ACTION: mhausenb send memo re LD clients to the list/jar
13:58:22 <trackbot> Created ACTION-38 - Send memo re LD clients to the list/jar [on Michael Hausenblas - due 2010-06-01].
13:58:29 <dbooth2> i/sorry, bit late/Topic: TAG Meeting prep
13:58:34 <Zakim> -mhausenblas
13:58:35 <Zakim> -dbooth2
13:58:39 <Zakim> -jar
13:58:40 <Zakim> TAG_(AWWSW)9:00AM has ended
13:58:42 <Zakim> Attendees were +1.216.445.aaaa, dbooth2, jar, mhausenblas
13:58:44 <dbooth2> rrsagent, make logs public
13:58:51 <dbooth2> rrsagent, draft minutes
13:58:51 <RRSAgent> I have made the request to generate http://www.w3.org/2010/05/25-awwsw-minutes.html dbooth2
14:00:00 <dbooth2> Present: Jonathan Rees, David Booth, Michael Hausenblas
14:00:58 <dbooth2> rrsagent, draft minutes
14:00:58 <RRSAgent> I have made the request to generate http://www.w3.org/2010/05/25-awwsw-minutes.html dbooth2
14:21:59 <jar> jar has joined #awwsw
15:27:38 <Zakim> Zakim has left #awwsw
15:31:42 <hhalpin> hhalpin has joined #awwsw