13:43:00 RRSAgent has joined #awwsw 13:43:00 logging to http://www.w3.org/2011/03/01-awwsw-irc 13:56:22 dbooth has joined #awwsw 13:57:18 zakim, who is here? 13:57:18 TAG_(AWWSW)9:00AM has not yet started, dbooth 13:57:19 On IRC I see dbooth, RRSAgent, Zakim, jar_, webr3, trackbot 13:57:28 Meeting: AWWSW 13:57:35 zakim, this will be awwsw 13:57:35 ok, dbooth; I see TAG_(AWWSW)9:00AM scheduled to start in 3 minutes 13:58:26 agenda+ nathan please add links to http://www.w3.org/wiki/HttpRange14Webography 13:58:36 TAG_(AWWSW)9:00AM has now started 13:58:43 +DBooth 13:59:39 +jar 14:00:59 agenda+ TAG issue tracking 14:01:24 agenda+ next steps on www-tag (doc review, or a call of some kind) 14:01:56 +[IPcaller] 14:02:09 Zakim, i am +[IPcaller] 14:02:09 sorry, webr3, I do not see a party named '+[IPcaller]' 14:02:14 agenda+ toward consensus doc from awwsw - maybe the 'requirements'? 14:03:22 agenda? 14:04:48 scribenick, webr3 14:05:02 Zakim, scribenick: webr3 14:05:02 I don't understand 'scribenick: webr3', webr3 14:07:18 scribe: nathan 14:07:48 scribenick: webr3 14:08:42 this one: http://www.w3.org/2001/tag/awwsw/ir-axioms/ 14:10:03 action: nathan to add links to wiki 14:10:03 Created ACTION-41 - Add links to wiki [on Nathan Rixham - due 2011-03-08]. 14:10:19 Topic: Requirements doc 14:10:35 zakim, take up item 1 14:10:35 agendum 1. "nathan please add links to http://www.w3.org/wiki/HttpRange14Webography" taken up [from jar_] 14:10:54 Scribe: webr3 14:11:15 zakim, take up item 2 14:11:15 agendum 2. "TAG issue tracking" taken up [from jar_] 14:12:02 http://lists.w3.org/Archives/Public/www-tag/2011Feb/0150.html 14:12:36 http://www.w3.org/2001/tag/group/track/actions/534 14:12:54 here's the relevant email re 57: http://lists.w3.org/Archives/Public/www-tag/2011Mar/0000.html 14:13:39 Change title to: "Mechanisms for obtaining information about the intended 14:13:40 meaning of a given URI" 14:14:37 jar: does anybody object to the title 14:14:42 all: no objections 14:14:46 (no particular input from group) 14:15:03 nathan thinks that's a good title 14:15:43 zakim, take up item 3 14:15:43 agendum 3. "next steps on www-tag (doc review, or a call of some kind)" taken up [from jar_] 14:16:01 jar: i had two questions 14:16:14 ... 1: next step on the broader continuation of uri-meaning work 14:16:38 ... if you guys want to give input, you can 14:17:01 dbooth: this is tag work yes, seems like we need to get a draft for tag review 14:17:33 jar: there are two things going on here, consensus doc for issue-57 review, and awwsw tf report 14:17:43 ... two different docs, w/ intertwining paths 14:18:02 dbooth: it seems ambitous to do two docs 14:18:12 jar: i think we need 2 or 3 docs 14:18:21 dbooth: so a report of where we're at or? 14:18:37 jar: produce some kind of ontology, or vocabs or 14:19:21 series #1: awwsw reports/notes (consensus within awwsw, reporting to tag & community) 14:19:46 series #2: tag reports/notes (consensus in TAG and/or in community) 14:20:07 this TF is responsible for #1 14:20:53 #2 would tag finding and/or rec track 14:21:11 s/would/would be/ 14:22:27 jar thinks intent to do #2 should be announced sooner rather than later, since otherwise situation will continue to fray 14:23:21 dbooth: wants #1 note in hand before going to www-tag. awwsw consensus 14:23:35 db: need to get over barriers of terminology and confusion 14:24:14 jar: framing the tag issue? 14:24:21 oar background? 14:24:52 nathan: 1) summary of space and views 2) consensus in awwsw re interoperability 3) axioms or ontology 14:26:12 dbooth: don't try to be too ambitious re #1... too comprehensive gets out of control... but need to say something 14:26:42 ... #3 could be separate 14:26:55 (agreement that #3 stands on its own) 14:27:18 #1 & #2 are a second document 14:27:58 nathan: can we do 3 until 2 is done? 14:28:02 dbooth #3 can be helpful in getting clarity... work on them in parallel 14:28:16 all: general agreement - sounds like a plan 14:28:24 jar: how quickly can we do this? 14:28:59 ... what do we need to do to get there? 14:30:15 dbooth: start with ir-axioms doc & owl 14:30:27 ... doesn't solve issue 57 of course 14:31:31 http://dbooth.org/2009/lifecycle/ 14:31:48 http://dbooth.org/2010/ambiguity/ 14:33:06 jar: we want documents as short as possible 14:33:17 Those documents both address the social obligations involved 14:33:53 but we could start with those documents in addressing issue-57 14:35:45 port 80 means http, without a marker... 14:36:03 200 is supposed to mean IR without a marker... but the obligation is being resisted 14:36:07 implied obligation 14:39:17 Plan A = refer to IR using its URI, refer to thing-described-by-doc using 303 URI, #, .well-known, tdb: etc 14:39:41 Plan B = refer to tdb using 200 URI, refer to IR *** UNKNOWN *** (maybe IRW or ir-axioms) 14:40:00 1) summary of space and views 14:40:32 we need a vocab that doesn't assume either plan... 14:42:09 two classes of things, OVERLAPPING. IR, and thing-described-by-document. 14:43:02 maybe instead IR, it's IR-with-reps-available-at-URI 14:45:47 agenda? 14:45:50 Topic: Axioms doc 14:46:16 http://www.w3.org/2001/tag/awwsw/ir-axioms/ 14:48:04 a simple IR is like a representation, except that it's an IR 14:50:47 simple IR is like content-location: 14:51:53 dbooth: unseasy with simple IR 14:52:32 and REST: ''Some resources are static in the sense that, when examined at any time after their creation, they always correspond to the same value set.'' 14:52:36 a simple IR is one that has only one representation (fixed resource) 14:53:47 dbooth: instead of trinity, we have 4 things, URI, IR, simple IR, representation 14:54:54 jar tbd: A simple IR has only one representation... by definition 14:55:20 the writeup says this, but not clearly enough. will fix 14:56:47 both returning the same int - /mary/age vs /bob/age 14:57:27 TimBL says these are different IRs with the same representation 14:58:43 "have different meaning" 15:00:17 dbooth: How to make this more palatable? 15:01:37 dbooth: model an IR as a function... a simple IR would be a constant function... 15:02:16 doc needs to say very plainly that a simple IR is one that has a single representation 15:03:15 nathan: Is the IRI / URI part of the simple IR? Does a simple IR 'know' its own URI? 15:03:44 source URI is like provenance 15:06:54 simple IR could be modeled as a pair (rep, prov) where rep is a represenation and prov is provenance 15:07:05 provenance might or might not involve some URI 15:07:49 provenance is history and/or material context 15:10:48 IR -> {simple IR = (rep, bits)} -> rep 15:11:03 rep may be shared, under different provenances, but 15:11:08 sorry scratch 15:11:19 IR -> {simple IR = (rep, provenance)} -> rep 15:11:51 rep (mathematical; bits) can be shared among multiple simple IRs (puns, coincidences) 15:14:37 I'm trying to frame this in terms of IR as a function from (Time x Request) to Representation, and Simple-IR is a constant function from (Time x Request) to Representation. 15:14:47 can't model simple IR as a constant function AND have 2 simple IRs with same rep 15:16:49 "Does Mary authorize this?" vs "Does Bob authorize this?" 15:17:31 SIR1, SIR2 both have same rep, but Mary authorizes one, Bob the other. 15:17:55 nathan: like having the question + the answer. 15:18:58 GET on SIR1 yields: "yes" 15:19:10 GET on SIR2 yields: "yes" 15:19:43 'speak for' is a better idea... does Mary authorize the resource to speak for her? 15:21:20 I would say that SIR1 is bound to one URI U1, and SIR2 is bound to another URI U2, and that's how you know who authorized. 15:25:36 [[ Even given an enumeration of syntactic parts, a simple IR's identity is not determined - two simple IRs might have all the same parts yet have distinct origins (provenance). ]] 15:31:32 Maybe convince TimBL and others to agree that representations are information resources?... no way 15:32:12 TimBL says, that there can be two fixedresources (simple IRs) that have the saame representation, yet are different 15:32:45 (intentional identity, not extensional) 15:33:25 two blank sheets of paper... 15:34:46 suppose Bob's doc and Mary's doc come from the same server, different URIs... 15:35:56 nathan: That seems fair 15:36:37 Suppose one IP address, multiple domain names resolving to same IP... 15:37:10 these are different resources... 15:37:56 If no host: then the requests would be identical 15:40:43 URIs have distinct meaning 15:41:06 jar__ has joined #awwsw 15:41:27 -[IPcaller] 15:41:31 -DBooth 15:41:32 -jar 15:41:32 TAG_(AWWSW)9:00AM has ended 15:41:34 Attendees were DBooth, jar, [IPcaller] 15:41:35 rrsagent, make logs public 15:41:41 Present: Jonathan Rees, Nathan, David Booth 15:41:47 rrsagent, make logs public 15:41:55 rrsagent, draft minutes 15:41:55 I have made the request to generate http://www.w3.org/2011/03/01-awwsw-minutes.html dbooth 15:47:34 jar_ has joined #awwsw 15:48:39 harry has joined #awwsw 16:30:54 mhausenblas has joined #awwsw 17:12:09 chair: Jonathan 17:12:15 rrsagent, draft minutes 17:12:15 I have made the request to generate http://www.w3.org/2011/03/01-awwsw-minutes.html dbooth