14:57:28 RRSAgent has joined #rdf-wg 14:57:28 logging to http://www.w3.org/2011/07/06-rdf-wg-irc 14:58:18 zwu2 has joined #rdf-wg 14:58:20 mbrunati has joined #rdf-wg 14:58:30 zakim, code? 14:58:31 sorry, davidwood, I don't know what conference this is 14:58:47 zakim, I agree with Pat. You can be hopeless at times. 14:58:47 I don't understand you, davidwood 14:59:32 zakim, this will be rdf 14:59:32 ok, gavinc, I see SW_RDFWG()11:00AM already started 14:59:53 Zakim, who is on the phone? 14:59:53 On the phone I see +44.207.923.aaaa, ??P11, ??P16, davidwood 15:00:03 +??P22 15:00:04 zakim, ??P16 is me 15:00:04 +AndyS; got it 15:00:06 Zakim, +44.207.923.aaaa is yvesr 15:00:06 +yvesr; got it 15:00:11 Zakim, mute me 15:00:12 (maybe) 15:00:13 +gavinc 15:00:13 yvesr should now be muted 15:00:23 zakim, mute me 15:00:23 AndyS should now be muted 15:00:27 +Scott_Bauer 15:00:34 zakim, who is talking? 15:00:45 davidwood, listening for 10 seconds I heard sound from the following: Scott_Bauer (5%) 15:00:45 mischat_ has joined #rdf-wg 15:00:49 zakim, ??P22 is me 15:00:49 +cmatheus; got it 15:00:52 +??P34 15:01:01 +OpenLink_Software 15:01:03 zakim, unmute me 15:01:03 AndyS should no longer be muted 15:01:06 Zakim, OpenLink_Software is temporarily me 15:01:06 +MacTed; got it 15:01:08 Zakim, mute me 15:01:08 MacTed should now be muted 15:01:16 zakim, ??P34 is me 15:01:16 +mbrunati; got it 15:01:19 zakim, who is on the phone? 15:01:19 On the phone I see yvesr (muted), ??P11 (muted), AndyS, davidwood, cmatheus, gavinc, Scott_Bauer, mbrunati, MacTed (muted) 15:01:22 +LeeF 15:01:32 AlexHall has joined #rdf-wg 15:01:35 zakim, ??P11 is me 15:01:35 +pchampin; got it 15:01:36 +??P38 15:01:42 tomayac has joined #rdf-wg 15:01:44 zakim, ??P38 is me 15:01:44 +mischat_; got it 15:01:48 zakim, mute me 15:01:48 mischat_ should now be muted 15:01:49 hello, I'm am here and ready to scribe. 15:01:52 hello 15:01:53 Thanks 15:02:11 scribe: cmatheus 15:02:11 + +1.443.212.aabb 15:02:15 iand has joined #rdf-wg 15:02:24 zakim, aabb is me 15:02:24 +AlexHall; got it 15:02:36 zakim, scribe: cmatheus 15:02:36 I don't understand 'scribe: cmatheus', cmatheus 15:02:36 zakim, code? 15:02:38 the conference code is 73394 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), zwu2 15:02:50 regrets: sandro 15:02:51 Scribe: cmatheus 15:02:51 scribe: cmatheus 15:03:04 +tomayac 15:03:17 I was expecting a confirmation from Zakim but haven't seen one. 15:03:18 sandro: We could use your help with the 22 June telecon minutes if you can. Please see email for details. 15:03:23 +zwu2 15:03:28 zakim, mute me 15:03:28 zwu2 should now be muted 15:03:31 zakim a bit confused? #41 not working? Very very delayed? 15:03:46 -AndyS 15:03:46 Scribe: Christopher Matheus 15:03:54 is there a way to confirm that am the scribe? 15:03:57 scribenick: cmatheus 15:04:07 done, davidwood 15:04:11 +??P16 15:04:16 zakim, ??P16 is me 15:04:16 +AndyS; got it 15:04:21 cmatheus, That is an RRSAgent function, not a Zakim function. 15:04:26 +iand 15:04:28 sandro, thanks! 15:04:39 thanks 15:04:43 np 15:04:51 Zakim, who is here? 15:04:51 On the phone I see yvesr (muted), pchampin (muted), davidwood, cmatheus, gavinc, Scott_Bauer, mbrunati, MacTed (muted), LeeF, mischat_ (muted), AlexHall, tomayac, zwu2 (muted), 15:04:55 ... AndyS, iand 15:05:17 scribe: cmatheus 15:05:50 davidwood: telecom minutes from June 22 -- I don't see them 15:06:16 sandro, URL for the 22 June minutes? I don't see them... 15:06:53 Were there minutes from the graph terminology RDF/SPARQL telecon? 15:06:56 PROPOSED to accept the minutes of the 29 June telecon: 15:06:56 http://www.w3.org/2011/rdf-wg/meeting/2011-06-29 15:07:02 in mean time... propose to accept minutes form June 29 15:07:21 OK - thx davidwood. 15:07:28 does anyone object to them being accepted? 15:07:35 davidwood, http://www.w3.org/2011/rdf-wg/meeting/2011-06-22 15:07:41 (not cleaned up AT ALL thought) 15:07:42 okay, accpet the June 29 minutes as written 15:08:04 Resolution: minutes June 29 acceptted 15:08:36 i did 15:08:45 davidwood: Richard was going to fix the minutes but is on holiday 15:09:08 typical of summer so we'll leave in his hands 15:09:44 http://www.w3.org/2011/rdf-wg/meeting/2011-06-22 haven't you know read them 15:09:50 I'm no longer in member acl so some things I cannot edit 15:10:12 we now have minutes for 22 June meeting -- please look through them so we can resolve them 15:10:54 no resolutions but thought there were some action items taken 15:11:26 one thing from meeting was we agreed to defer issue 32 until next meeting 15:11:36 discussed on June 29 but no resolution was proposed 15:11:42 I am, but there are people talking in my office 15:11:57 ISSUE-32? 15:11:57 ISSUE-32 -- Can we identify both g-boxes and g-snaps? -- open 15:11:57 http://www.w3.org/2011/rdf-wg/track/issues/32 15:12:02 is Lee here today? do you have any comment on issue 32? 15:12:29 Zakim, please dial ericP-office 15:12:29 ok, ericP; the call is being made 15:12:30 LeeF: I think we discussed it a bunch but we said we had to wait on actions from graph telecomm 15:12:30 +EricP.a 15:12:35 +PatHayes 15:12:54 things seemed close but there were actions on Righard and a few others to make a proposal to align things 15:13:11 davidwood: with that taken care of are there objections to June 22 minutes? 15:13:23 abstain (was no there) 15:13:28 abstain (was not there) 15:13:30 resolution: accept minutes for June 22 15:13:35 Turtle Editors Draft 15:13:35 http://dvcs.w3.org/hg/rdf/raw-file/tip/rdf-turtle/index.html 15:13:35 ▪ Discuss existing issues, notes. 15:13:35 ▪ Any other issues to raise? 15:13:56 davidwood: move on to turtle discussion 15:14:26 cygri has joined #rdf-wg 15:14:39 zakim, what's the code? 15:14:39 the conference code is 73394 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), cygri 15:14:44 eric or gavin, which would like to go through document in terms of issues and notes? 15:14:47 +cygri 15:15:03 ericp: gavin more tapped in than me 15:15:13 PatH has joined #rdf-wg 15:15:16 cygri, hi. Have you been able to create minutes for the RDF/SPARQL telecon? 15:15:45 gavinc: out standing issue 13 around xsd strings and plain literals, some language about it in the draft 15:16:02 issue about escape sequences being allowed 15:16:09 david, if that was meant for me, not yet. 15:16:10 and the grammar table has issues 15:16:24 davidwood, no, totally forgot about it, sorry. i have the log and will do it first thing tomorrow 15:16:26 -pchampin 15:16:30 in the production of the table (editorial issue) 15:16:48 davidwood: associate issue in doc with working group issues 15:17:02 gavin: I didnt see an issue for the one Eric added? 15:17:11 ericP has changed the topic to: RDF-WG weekly meeting - Agenda: http://www.w3.org/2011/rdf-wg/wiki/Meetings:Telecon2011.07.06 15:17:16 ericP: I'm not sure there's an issue for that 15:17:30 davidwood: there's an issue that hasn't been openned and we should 15:17:38 AndyS, where? 15:17:57 +??P11 15:18:00 gavin: if there is one it would be could to be able to link to it 15:18:03 gavinc - in the abstract (in tip) 15:18:06 zakim, ??P11 is me 15:18:06 +pchampin; got it 15:18:30 davidwood: we have 9 issues that have been raised and not openned 15:18:34 gavinc - not a block on FPWD 15:19:12 I'd rather use tracker to track issues so we should raise issues for these 15:19:42 http://www.w3.org/2011/rdf-wg/track/issues/new 15:19:46 ISSUE-13? 15:19:46 ISSUE-13 -- Review RDF XML Literals -- open 15:19:46 http://www.w3.org/2011/rdf-wg/track/issues/13 15:19:56 gavinc: why don't I create a place holder one and we can use that 15:20:22 davidwood: issue 12 has been closed 15:21:14 -cmatheus 15:21:26 cygri: issue 12 isn't closed 15:21:46 Zakim, who is here? 15:21:46 On the phone I see yvesr (muted), davidwood, gavinc, Scott_Bauer, mbrunati, MacTed (muted), LeeF, mischat_ (muted), AlexHall, tomayac, zwu2 (muted), AndyS, iand, EricP.a, PatHayes, 15:21:49 ... cygri, pchampin (muted) 15:21:52 I JUST LOST MY PHONE CONNECTION -- COULD SOMEONE SCRIBE UNTIL I GET BACK ON? 15:22:28 + +33.4.72.69.aacc 15:22:35 zakim, aacc is me 15:22:35 +pchampin; got it 15:22:54 gavinc: : sandro asked about a change to turtle to allow or
 elements. Embedding in a script element  will not be displayed by browsers, while 
 turtle here 
. In the second example, you may use a class to alter display or to signify that it can be parsed as text/turtle. 15:28:37 only some minor changes but in a state to be considered as a working draft 15:28:42 surely though the graph terminology should be in Concepts, no? 15:28:55 daivdwood: I agree it's time to move it to a working draft state 15:29:07 PatH, indeed 15:29:15 ericP, that's not exactly accurate, but something like that yeah 15:29:20 I haven't looked at the document in about 10 days 15:29:49 propose we make this a topic for the next meeting, June 20th. 15:29:57 july, maybe? 15:30:12 look over the Concepts doc over the next fortnight, is that okay with you? 15:30:13 ericP, pre.example script { display:block; } for example in the turtle spec 15:30:21 cygri: yes that's great 15:30:31 davidwood: I make sure it gets on the agenda 15:30:44 gavinc, sounds good 15:31:03 daivdwood: we've now left the tutrle draft and are moving onto graphs 15:31:20 Lee, can you lead this discussion in absence of minutes? 15:31:38 LeeF: I'm sorry, I'm not prepared to lead discussion today. 15:31:52 davidwood: okay. 15:32:18 Richard, it seems you we're asked to create minutes from an ealier telecom. will you be able to do that task? 15:32:39 danbri has joined #rdf-wg 15:32:39 cygri: it completely fell off my radar so I didn't make minutes from it 15:32:43 q+ 15:32:47 will do so first thing tomorrow 15:32:49 i too think that the graph terminology should go into the concept document 15:33:04 davidwood: please send a url to the minutes when they are ready 15:33:06 ack ericP 15:33:14 ack \ 15:33:17 :) 15:33:19 ack  15:33:24 ericp: if you want something that takes minutes and dumps them as html you can pass them to me 15:33:38 cygri: sounds good, I'll do that 15:34:26 davidwood: in absense of Lee today I suggest we go through things oppened in June 29 telecom, unless someone has better idea for today's time 15:34:44 let's go to issue 14: whats a named graph and what should we call it? 15:34:56 q+ 15:35:13 sandor hs proposed the term gbox with we have consensus on 15:35:20 Zakim, who's noisy? 15:35:25 -zwu2 15:35:26 s/sandor/sandro/ 15:35:30 MacTed, listening for 10 seconds I heard sound from the following: PatHayes (15%), pchampin.a (25%), AndyS (25%), davidwood (45%) 15:35:33 we now ned to align this with SPARQL documents which are much further along 15:35:37 ack PatH 15:35:56 path: we're having discussion on email on this topic - not sure of the state they're in 15:36:17 some progress is being made, not sure what you want to do now 15:36:26 +??P22 15:36:36 davidwood: everyone seems to want to seem mintues form that telecom. 15:36:46 +zwu2 15:36:58 Zakim, ??P22 is me 15:36:58 +NickH; got it 15:37:05 let's take a quick look down issues list and see if there's one that we can make progress on 15:37:05 ISSUE-38? 15:37:05 ISSUE-38 -- What new vocabulary should be added to RDF to talk about graphs? -- raised 15:37:05 http://www.w3.org/2011/rdf-wg/track/issues/38 15:37:08 Zakim, mute me 15:37:08 NickH should now be muted 15:37:29 leef: issue 38 hasn't been discussed yet so there's nothing preventing progress on it today 15:37:46 s/leef/gavinc 15:37:53 list of issues FWIW http://www.w3.org/2011/rdf-wg/track/issues/ 15:37:56 q+ 15:37:59 davidwood: let's jump into 38 t see where we get 15:38:09 ack cygri 15:38:16 some talk on this but its a biut stale 15:38:53 cygri: rdb2rdf working talking about wheter we have a default graph and can we use that 15:39:13 q+ 15:39:16 i wonder if there is any consensus with regards to what the default graph is 15:39:17 i'm afraid of a graph name for the default graph 15:39:20 what is THE default graph? 15:39:25 can we get from the rdf-wf some concept of a default graph that we can use in SPARQL 15:39:34 PatH, it's MY default graph 15:39:48 davidwood: conflating issue 29 and 38, but it's a good point, I agree with that 15:39:51 There is no notion of default anything in the RDF model. 15:39:52 ack AndyS 15:40:21 Mmm, do DataSets need names too? /me ducks 15:40:22 file://localhost/~ ? 15:40:23 andys: there isn't a default graph, as Pat's noted 15:40:32 Ah. So default is a property of datasets whose value is a g-box. 15:40:49 rdf:defaultGraphOf 15:40:55 davidwood: you were vocal about the fact that not every default graph sits in a database 15:40:59 I think so PatH 15:41:31 when the entire graph resides in a file the file's url is the default graph -- do you recall this discussion? 15:41:34 andys: no 15:41:35 s/default// 15:42:00 q+ 15:42:10 ack PatH 15:42:12 there isn't a web addressable name for the defualt graph because it's context dependent 15:42:15 there are lots of ambiguous URLs 15:42:48 path: it's a property of data sets whose value is a graph 15:43:02 fit's into the rdf model perfectly if its a property 15:43:31 davidwood: I don't ink there's a problem with that. question is is it manditory and if the location changes does the name change? 15:43:35 ericP, not in this sense (I hope!). file://localhost/.. hides context in localhost 15:43:42 AZ has joined #rdf-wg 15:44:00 path: if the state has changed but the name stays the same here's an issue 15:44:04 AndyS, true 15:44:32 ?? :datasetbase rdb2rdf:defaultGraph [ .... ] 15:44:37 davidwood: if you hash a serilization of a graph and you tweak some property of the graph you get a differe3nt has 15:44:45 i'd expect that, if i were e.g. reading a test manifest and find n graphs asserted to be the default graph, i'd put them all into the default graph 15:44:50 path: isn't that true of any hashable arguement 15:44:55 q+ 15:44:56 davidwood: ture 15:44:57 +Vicki 15:45:00 Zakim, unmute me 15:45:00 MacTed should no longer be muted 15:45:05 zakim, I am Vicki 15:45:05 ok, AZ, I now associate you with Vicki 15:45:14 as it stands we can only sign serialisations anyway 15:45:16 q? 15:45:17 really? graphs are madness? ;) 15:45:26 the naming is metadata that's outside of the graph -- get recursion problem of meta data, and metapmeta data and there lies maddness 15:46:02 path: things that are named by uri's but are changeable but we want name to stay the same this raises a lot of issues for rdf that I don't thin we can solve 15:46:10 this would get very difficult 15:46:11 ARQ uses which is very poor modeling but very useful (as per rdb2rdf UC) GRAPH {...} works :-) 15:46:28 davidwood: if you change a graph you 've go a copy of a grph that's a very different thing 15:46:36 ack MacTed 15:46:39 I think I agree with you and it's not an issue 15:46:46 AndyS, that would work for us. We use rr:defaultGraph 15:47:05 MacTed: if we say once we name something that it never chances that we've got problems 15:47:05 cygri, as property? As resource? 15:47:17 I've been the same person all my life but I've changed over time 15:47:26 Thi sis what we have the g-box/graph distinction for. 15:47:32 the graph that desribes me changes over time but it describes me 15:47:48 GRAPHS DO NOT CHANGE. 15:47:49 AndyS: <... some mapping rules ...> rr:targetGraph rr:defaultGraph. 15:47:54 this is a problem that needs to be change - immutability of descriptions needs ot come into play soo 15:48:14 need complete set of identifiers that nail down a document at a given point in time 15:48:17 q+ 15:48:30 I'm not comfortable I have gbox and gtext names right in my head yet 15:48:48 WHO'S TALKING PLEASE? 15:48:54 Andy 15:48:55 thanks 15:49:37 q+ 15:49:45 andys: in a perfect snapshot of web (no changes, everyting static) if you give a name to the graph which is a uri it needs to go to the smae place 15:49:59 Right, so default-graph is a property even in a static Web. 15:50:04 that concept of the world doesn't work if you use a uri for the default graph 15:50:13 zakim, who is making noise ? 15:50:16 ack pchampin 15:50:23 mischat, listening for 10 seconds I heard sound from the following: pchampin.a (34%), davidwood (24%), MacTed (30%) 15:50:26 zakim, mute me 15:50:26 Vicki should now be muted 15:50:49 pchampin: I agre with pat about the DF. 15:50:52 Zakim, mute me 15:50:52 MacTed should now be muted 15:50:56 cygri - rr:defaultGraph names what resource? GET rr:defaultGraph --> ? 15:50:59 the problem comes from the misue of the default graph 15:51:27 AndyS, why presume that you can GET graph names? 15:51:32 if youink of he default graph as a gbox then things work 15:51:46 AndyS, GET rr:defaultGraph, you get the R2RML vocabulary document 15:51:52 andys: it can be a gsnap and you can freeze everything 15:52:07 davidwood: makes sense to me in a database context 15:52:22 when do we care about naming the totality of a graph? 15:52:25 The issue, I think, is that if :Store is labile, then ( :store rdf:defaultGraphIs :graph .) can change truthvalue when :store is updated. 15:52:26 defining inferential closure 15:52:27 +1 to pchampin explanation, i wonder why the RDF WG are worrying about the default graphs, surely these are triplestore/sparql related. and as far as I can tell are vendor specific in the world of triplestore 15:52:28 not true for rdf users who never use a rdf store 15:52:28 writing tests 15:52:45 cygri, conceptually, names can be resolved. I am asking if it is the name of a graph and so is GET if it's http:// 15:52:47 dange in using erms that don't apply to larger community 15:52:51 q? 15:53:13 andys: we must keep in mind that when we say graph sometimes we mean gbox, something gsnap 15:53:23 q+ 15:53:48 in this case I think it means gbox 15:53:59 ack cygri 15:54:05 i guess when you execute a sparql query on a sparql store, you are getting results on a g-snap 15:54:18 cygri: reply to Andy from earlier... 15:54:34 I don't think there's an assumption that the graph name has to resolve to the graph 15:54:44 not sure what the basis is for such a presumption 15:54:49 RDG graph is (defined to be) a set, in the mathematical sense of "set". Mathematical sets don't change. 15:55:11 from that point of view I don't see problem with assigning a uri to a graph 15:55:14 q+ 15:55:27 http://www.w3.org/2011/rdf-wg/wiki/TF-Graphs-UC 15:55:28 another point, maybe it's good to think back to use cases 15:55:42 there's a wiki page from monhs ago of really good use cases 15:55:55 +1 to think back of use cases 15:55:58 SPAQRL as it stands can address most of these use case 15:56:18 well, Richard, http://www.w3.org/TR/sparql11-http-rdf-update/ suggests that graph URIs *could*, in some situations, resolve to the content of the graph 15:56:24 might be goog to see which use cases break when we use SPARQL design 15:56:33 ack PatH 15:56:35 goog, but not good. 15:56:45 davidwood: this is fundamentally the arguement -- theiry vs. practise 15:56:55 path: I pretty much agree with Richard 15:57:22 ack me 15:57:44 (was just about default graph -- different from other naming UCs) 15:57:45 however, if we introduce rdf terminology for DG then we can say something is "DF" then its truth value can change with the datate store is changed 15:57:53 cygri; is this always the case? 15:58:02 path: no 15:58:05 linked data changes a lot... 15:58:10 like any other data on the web 15:58:11 s/is this/isn't this/ 15:58:18 look at wikipedia! 15:58:24 if these things are going to be changing their state very rapidly what's the point of creating them 15:58:27 -tomayac 15:58:51 cygri: even if triple is valid for only a few ms that's fine if that's what you need 15:58:52 FROM => one default graph ... elsewhere FROM ==> different default graph ... even in a fully static world. 15:58:58 path: let me back off and agree 15:59:20 we shouldn't make it illegal but we should draw attention to it and warn people about it 15:59:46 triples that change qucikly is different from the original intended use of RDF 16:00:07 davidwood: five years ago rdf databases were read optimized 16:00:16 we don't see that in the world now at all 16:00:24 -yvesr 16:00:34 q? 16:00:37 we store a lot of system state in an rdf database, and it's subject to frequent change. we also don't tend to expose that mutable state outside our system. 16:00:41 there are massive deletes, rapid write. this has been a sea change in the way people use rdf in the last few years 16:00:51 q+ 16:01:04 path: okay, but if we do this and start using this terminology a lot of people are going to be surprised 16:01:14 we are current doing > 2000 queries/updates per second on our live sparql store 16:01:20 I think it might be useful to have test cases that exhibit the difference between these two approaches to terminology -- what actually changes? 16:01:29 -NickH 16:01:59 path: the gbox and gsnap concepts we have we defined and gsnaps are the mathimatical graphs 16:02:14 q+ 16:02:21 q? 16:02:22 davidwood: we mean graph differently when we talk about gbox, gsnap and gtext 16:02:25 q- 16:02:39 ack cygri 16:02:48 cygri: I strongly agree 16:03:11 big problem here. have two conflicting uses of the word graph 16:03:30 rdf graph - an immutable set 16:03:47 q+ 16:03:55 named graph in sparql - a graph is soming mutable. can update it and it still has same name 16:03:59 In the Anzo APIs, we use the term "named graph" for the mutable things 16:04:01 -EricP.a 16:04:03 confusion in two uses of the word graph 16:04:20 ack AndyS 16:04:23 q+ 16:04:24 might be worth considering the sparql graph as being a container of triples 16:04:37 I doubt end users care about these differences. they probably don't even realize the differences 16:04:40 these are fundamentally different in what they mean and we need to do some about this 16:04:53 andys; named graph are not behaving like the default graph 16:05:27 Zakim, unmute me 16:05:28 the default graph is realtive to the store and are unlike what uris give us 16:05:29 MacTed should no longer be muted 16:05:31 yes 16:05:37 davidwood: I might challenge that 16:06:09 iand - can you discuss your expectations on this 16:06:09 indeed AndyS and different stores have implemented their defaults graphs in different ways 16:06:14 hard to hear 16:06:18 AndyS: i think i don't fully agree. in my graph and in your graph can be different 16:06:45 iand: garble grable... 16:07:00 cygri - true can be different but consider completely static world 16:07:02 what does named graph identifier mean 16:07:09 a tag for the graph or an identified for the graph 16:07:21 ... default graph different - not same info 16:07:23 ... Example: FROM => one default graph ... elsewhere FROM => different default graph 16:07:28 if its an identifier then you should expect the same graph where ever you are 16:07:28 q+ 16:07:49 if it's a tag you don't have the expectation that it the same graph 16:07:52 ack PatH 16:08:08 ack cygri 16:08:29 cygri: what Ian mentioned is different from the one I brought up earlier 16:08:38 AZ has joined #rdf-wg 16:09:00 regardless of whether you consider the iri in a named graph as an identifier or a tag there's still the fact the named graphs things you can update 16:09:07 rdf graphs are not like that 16:09:13 problem is, the notion of "default graph" is always relative to some context 16:09:14 mischat - yes - dft graph as union of named graphs shows its different in different places as well. 16:09:28 tomayac has joined #rdf-wg 16:09:34 but we can still name g-snaps and g-boxes, can't we?? 16:09:35 rdf graphs are more like gboxs and named graphs are more like gsnaps 16:09:50 q? 16:09:52 ... makes me nervous about it having a URI : property or class, not individual. 16:09:54 sparql doesn't make any assumptions about how you use the graph 16:10:00 q+ 16:10:25 q+ 16:10:26 I hear a number of people here pushing to the position where a global iri would be used in this name graph 16:10:53 RIGHT 16:11:01 ack me 16:11:07 davidwood:maybe we need to talk abuot naming gsnaps and gboxes in different ways 16:11:13 q+ mirroring data and portability of sparql (will type not use phone) 16:11:23 q+ to ask about mirroring data and portability of sparql (will type not use phone) 16:11:44 pchampin: it sounded like Richard was claiming we could only name one kind of graph but I think we can name both 16:11:59 but we need to keep these notion separat 16:12:08 i would like the term graph used in sparql as is, as it is used in practice, and for the RDF WG to use less ambiguous terms as spec'ed out in our previous conversation re: g-*. This discussion should probably be kept to the concepts document, and in any quad based serialisation 16:12:15 I agree that sparql doesn't make an assumption about the use of iri 16:12:34 but if you have control of an iri you can make the graph available when getting the uri 16:13:03 in sparql the iri is homogenous to a resource in the query 16:13:48 we are naming graphs with a resource not a iri 16:14:05 Leef: you can name anythiong with a uri 16:14:07 "A "g-snap" as an idealized snapshot of a g-box; " 16:14:11 davidwood: but do you have to? 16:14:16 ack PatH 16:14:29 s/LeeF/MacTed/ 16:14:32 you can name a g-snap with a literal (the corresponding g-text) 16:14:33 path: this discussion could have taken place in any context having to do with computer science 16:14:45 we have a dilema 16:14:57 1st - I agree you can name anything with an iri 16:15:00 are we just saying that there is a property sparql:graph that has a domain of sparql:Dataset and range of rdf:gsnap 16:15:04 AZ has joined #rdf-wg 16:15:06 Name g-boxes, if you want to name a specific g-snap make a new damn g-box and never change it's contents 16:15:16 most people will use iris to refere to graphs and others with use them for gboxes 16:15:18 the issue seems to be -- "how do we change 'named graph' everywhere to 'named g-box'?" 16:15:33 can't have differnt conventions for naming the two - people won't use it 16:15:48 people will want to use same name for the two types of graph 16:15:49 -iand 16:15:49 actually... currently "named graph" is used for both, g-snaps and g-boxes 16:16:00 the ambiguity of naming is going to be with us inthe real world 16:16:18 next thought - may be can have different type of property 16:16:21 PatH: Ambiguity of naming will be with us whether we like it or not. 16:16:22 +iand 16:16:37 some apply to the state some apply to the object transending the state 16:17:03 so you mean that property rdf:numberOfTriples would actually mean "number of triples in the current state of that g-box" ? 16:17:04 having coersion for the property isn't going to work 16:17:21 take rdf:type -- would have to have two different types, one for object one for state 16:17:27 +1 to macted's suggestion of changing "named graph" to "named gbox" 16:17:38 "we should learn to cope with ambiguity in URIs" 16:17:40 if a name is used ambiguously there's nothing we can do about it 16:17:49 gavinc :-) 16:18:24 jeni blogged about this stuff yesterday, worth a read http://www.jenitennison.com/blog/node/159 16:18:43 cmatheus: I need to end scribing here, sorry 16:18:48 -cygri 16:18:54 I'll wait until later tomorrow to edit the minutes 16:18:55 -MacTed 16:18:57 -zwu2 16:18:58 -Scott_Bauer 16:19:01 hi guys 16:19:04 -AZ 16:19:05 -mbrunati 16:19:06 -AlexHall 16:19:11 -mischat_ 16:19:13 mbrunati has left #rdf-wg 16:19:14 AlexHall has left #rdf-wg 16:19:17 -AndyS 16:19:19 -cmatheus 16:19:21 -gavinc 16:19:26 -LeeF 16:19:38 Current best guess for terminology is 'graph resource' for anything mutable that emits graph representations; 'graph' for snaps, and 'graph representation' for g-texts. THis fits with the REST terminology and allows the use of 'graph' for them all when people are being sloppy. 16:19:40 Process question.... how do we publish a WD of Turtle? :D 16:20:05 Ask Sandro :) 16:20:14 He said not to if we were using Respec ;) 16:20:23 -PatHayes 16:20:45 ...but we will however ;) 16:20:49 +1 to PatH (I think ...) 16:21:12 +1 to PatH 16:21:21 does the 'graph' for snaps match with the GRAPH verb in sparql 16:21:37 i guess it does when thinking about queries, not sure when thinking about updates 16:22:18 query usage and update usage are different ... query world is static so g-box/g-snap binding is fixed 16:22:26 -iand 16:23:10 SPARQL 1.0 does not fix GRAPH uri (much careful wording) and the wording is not designed for SPARQL 1.1 update 16:23:12 the GRAPH verb means a graph resource in UPDATE and a graph in SELECT/CONSTRUCT 16:23:18 ? 16:24:29 Best rewording I can make is SPARQL 1.0 "associates" a URI with a g-snap. Different apps associate differently (name of web location for data, unique nema for action of reading). 16:24:47 Anyway, be around later today and will tag a revision for the WD for the Turtle document 16:25:18 In update there is also (URI, g-box) pair which is definitely a g-box in local store. 16:25:26 gavinc, see http://dev.w3.org/2009/dap/ReSpec.js/documentation.html#configuration to change the specStatus to WD 16:25:28 agreed 16:26:20 'cos if you change it, you see the change but someone else's store does not change (or generally people get upset :-) 16:26:38 Zakim, who is here? 16:26:38 On the phone I see davidwood, pchampin, pchampin.a 16:26:46 Yeah, know how to do that David, what to do AFTER that is somewhat confusing ;) 16:26:58 Will have a tagged HTML document by the end of today 16:27:09 gavinc, is there anything else to do? I think it will auto-update the header. 16:27:31 "The specStatus is used to pick the base style sheet, as well as to configure various parts of the specification's header and Status of this Document. " 16:27:52 gavinc, when you find out how to pub respec, coudl yo ulet me know as I have a respec note to do. There is someway to get pure HTML out apparently. 16:28:07 Yeah, that will just leave it in HG and using javascript 16:28:16 step 2 is get some XHTML to publish 16:29:57 it's First Public Working Draft isn't it? 16:30:04 some process wonk around? 16:30:10 Yes, I suppose so 16:30:40 -davidwood 16:30:42 -pchampin.a 16:31:07 gavinc, I'm still reading the Respec page... 16:31:40 RRSAgent, draft minutes 16:31:40 I have made the request to generate http://www.w3.org/2011/07/06-rdf-wg-minutes.html davidwood 16:31:48 sandro, you around? 16:32:11 gavinc, http://dev.w3.org/2009/dap/ReSpec.js/documentation.html#saving-the-generated-specification 16:32:37 "The solution that is used here is that you hit the Ctrl+Shift+Alt+S key combination (this is subject to change until we agree on an option we all like). That will show a menu offering to either "Save as HTML", "Save as HTML (Source)", "Save as XHTML", or "Save as XHTML (Source)". You can hit Esc to hide it." 16:32:44 Yeah 16:33:06 Then I suppose you put it into the WG's mercurial repo. 16:33:21 mmmm 16:33:26 davidwood has left #rdf-wg 16:34:07 davidwood has joined #rdf-wg 16:34:43 Do you have the details for that? There was an email to the list... 16:34:54 Yeah, yeah 16:35:07 it's where the document is living 16:35:43 disconnecting the lone participant, pchampin, in SW_RDFWG()11:00AM 16:35:44 SW_RDFWG()11:00AM has ended 16:35:47 Attendees were davidwood, AndyS, yvesr, gavinc, Scott_Bauer, cmatheus, MacTed, mbrunati, LeeF, pchampin, mischat_, +1.443.212.aabb, AlexHall, tomayac, zwu2, iand, EricP.a, 16:35:50 ... PatHayes, cygri, +33.4.72.69.aacc, NickH, AZ 16:36:47 I think Sandro is happy to deal with publishing HTML to a URI :) 16:37:44 the short name is Turtle yes? 16:37:52 Yes 16:38:38 I suggest saving the document from Respc to XHTML, adding the saved file into the WG's hg repo and telling Sandro he needs to publish it to the appropriate URL. Does that work for you? 16:38:49 yep yep 16:38:55 I think :D 16:39:16 Richard's message with hg instructions is at: http://lists.w3.org/Archives/Public/public-rdf-wg/2011Jun/0012.html 16:39:24 Yeah, I have hg all working 16:39:28 oh, good 16:39:29 that's how we've been editing 16:39:38 and publishing EDs 16:40:10 We'll all learn something about this as you do it. Isn't it nice to be first? :) 16:41:52 Oh 16:41:53 damn 16:42:01 still have to fix biblio DB 16:43:57 oops 17:01:52 Victory! http://dvcs.w3.org/hg/rdf/raw-file/Turtle-FPWD/rdf-turtle/index.html 17:02:55 gavinc, Thanks! 17:03:10 now to save the XHTML 17:07:55 http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/built-xhtml/FPWD.html built XHTML 17:08:23 gavinc, will you be online later to chat about turtle? 17:08:35 (editing details) 17:08:39 Yes, taking kids to train park, back in the afternoon 17:08:43 cool 17:09:40 seen the train museum one stop north of san jose on caltrain? 17:10:03 Yep! 17:17:16 i always try to make connections through there. fabulously interesting and low-key museum 17:18:26 gavinc, should i pester you or ralph about topquadrant tech for embedding sparql query results in html? 17:45:32 AndyS has joined #rdf-wg 18:24:24 mischat has joined #rdf-wg 18:54:37 Zakim has left #rdf-wg 20:01:54 tomayac has joined #rdf-wg 20:54:21 gavinc, back? 21:46:01 Yes 21:46:03 ;) 21:46:30 You here? 21:51:02 ericP, ping! 21:51:42 heya 21:51:57 sounds like if we want to fix stuff in turtle, we should do it tonight 21:52:31 at least before a FPWD, yeah, ... though there is one checked in now ;) 21:53:59 One current oddity is that parts of the document (mostly the abstract at this point) talk about how compatable with N3 Turtle is, where as the compared to N3 section now (correctly?) points out that while N3 was the largest input into Turtle that compatibility isn't really a goal of Turtle any longer 21:54:41 The table for the BNF is still a bit of a mess, never did get yacker to generate what you had from before (Maybe it was hand done after yacker?) 21:56:20 Also still have the are we defining N-Triples as an appendix inside Turtle or as a separate document 22:12:25 did it 22:12:55 did the document get moved to a new place? or do we still edit what we've been editing? 22:13:07 same place 22:15:26 cool 22:16:37 the one tagged for the CfC is http://dvcs.w3.org/hg/rdf/raw-file/Turtle-FPWD/rdf-turtle/index.html but the tip is back to an ED for more editing 22:28:03 should i dink with the grammar tonight? 22:31:45 Yeah, I think the HTML needs help 22:32:03 I didn't know if I was missing something in how to get yacker to what you had it do 22:32:14 or if all the numbering and terminal spliting was done by hand 22:32:53 Did go so far as to spend about 3 hours seeing if I could parse the EBNF directly in javascript and output the HTML that way ;) 22:32:57 then I thought better of it 23:24:01 iand has joined #rdf-wg