14:58:13 RRSAgent has joined #rdf-wg 14:58:13 logging to http://www.w3.org/2011/04/06-rdf-wg-irc 14:58:14 regrets from me, am also in a meeting 14:58:15 RRSAgent, make logs world 14:58:15 Zakim has joined #rdf-wg 14:58:17 Zakim, this will be 73394 14:58:17 ok, trackbot; I see SW_RDFWG()11:00AM scheduled to start in 2 minutes 14:58:18 Meeting: RDF Working Group Teleconference 14:58:18 Date: 06 April 2011 14:58:23 (though within earshot of guus) 14:58:24 trackbot, this will be rdfwg 14:58:24 Sorry, LeeF, I don't understand 'trackbot, this will be rdfwg'. Please refer to http://www.w3.org/2005/06/tracker/irc for help 14:58:29 zakim, this will be rdfwg 14:58:29 ok, LeeF, I see SW_RDFWG()11:00AM already started 14:58:33 +??P24 14:58:36 mischat_ has joined #rdf-wg 14:58:41 zakim, ??P24 is me 14:58:41 +AndyS1; got it 14:58:41 zakim, who's on the phone? 14:58:42 On the phone I see FabGandon, +31.20.598.aaaa, Tony, AndyS1 14:58:45 +Sandro 14:58:47 SteveH_ has joined #rdf-wg 14:58:58 zakim, code? 14:58:58 the conference code is 73394 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), LeeF 14:59:00 +gavinc 14:59:15 +??P17 14:59:20 +LeeF 14:59:42 +Peter_Patel-Schneider 14:59:46 +??P7 14:59:48 -Tony 14:59:54 pfps has joined #rdf-wg 14:59:57 +OlivierCorby 15:00:13 zakim, ??P17 is me 15:00:13 +mbrunati; got it 15:00:16 cygri has joined #rdf-wg 15:00:22 +Tony 15:00:54 + +43.512.507.aabb 15:01:00 Zakim, ??P7 is [Garlik] 15:01:00 +[Garlik]; got it 15:01:06 AZ has joined #rdf-wg 15:01:09 Zakim, [Garlik] has SteveH and mischat 15:01:09 +SteveH, mischat; got it 15:01:28 +??P21 15:01:47 +Souri_ 15:02:03 AlexHall has joined #rdf-wg 15:02:11 Souri has joined #rdf-wg 15:02:43 +AlexHall 15:02:57 pchampin has joined #rdf-wg 15:03:08 zakim, ??P21 is me 15:03:08 +cygri; got it 15:03:20 +PatH 15:03:29 pchampin, you're scheduled to scribe today.... 15:03:31 I don't seem to be recognized on the call again: Scott Bauer 15:03:36 yes 15:03:44 struggling with zakim to dial in 15:03:52 shouldn't take too long :-/ 15:04:12 zakim, who is on the call? 15:04:12 On the phone I see FabGandon, +31.20.598.aaaa, AndyS1, Sandro, gavinc, mbrunati, LeeF, Peter_Patel-Schneider, [Garlik], OlivierCorby, Tony, +43.512.507.aabb, cygri, Souri_, 15:04:15 I had a few snags with zakim today. 15:04:15 ... AlexHall, PatH 15:04:15 [Garlik] has SteveH, mischat 15:04:47 zakim, who is here? 15:04:49 On the phone I see FabGandon, +31.20.598.aaaa, AndyS1, Sandro, gavinc, mbrunati, LeeF, Peter_Patel-Schneider, [Garlik], OlivierCorby, Tony, +43.512.507.aabb, cygri, Souri_, 15:04:51 ... AlexHall, PatH 15:04:51 [Garlik] has SteveH, mischat 15:04:53 q- 15:05:00 queue= 15:05:06 zakim, Tony is hsbauer 15:05:06 +hsbauer; got it 15:05:12 can you remind me the conference code? 15:05:12 q? 15:05:17 thanks 15:05:19 rdfwg? 15:05:20 zakim, what is the code? 15:05:20 the conference code is 73394 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), sandro 15:05:32 +Luca 15:05:33 73394 15:05:50 scribe: pchampin 15:07:01 Sorry I won't be able to be on the phone today: my phone's not working.... 15:07:09 topic: administrative 15:07:20 minutes look good 15:07:22 +Luca.a 15:07:22 last week minutes 15:07:28 +zwu2 15:07:35 m029206__ has joined #rdf-wg 15:07:43 zwu2 has joined #rdf-wg 15:07:47 RESOLUTION: minutes accepted 15:07:53 zakim, who is making noise? 15:08:03 zakim, mute me 15:08:03 zwu2 should now be muted 15:08:04 mischat, listening for 10 seconds I heard sound from the following: Luca.a (47%), +31.20.598.aaaa (76%), +43.512.507.aabb (4%) 15:08:11 http://www.w3.org/2011/rdf-wg/meeting/2011-03-30 15:08:15 zakim, mute Luca.a 15:08:15 Luca.a should now be muted 15:08:17 sorry 15:08:27 AZ has joined #rdf-wg 15:08:34 topic: open action items 15:08:49 http://www.w3.org/2011/rdf-wg/wiki/TriplestoreRDFSupport 15:09:05 http://www.w3.org/2011/rdf-wg/track/actions/open 15:09:11 +??P8 15:09:21 Most support SPARQL JSON results 15:09:29 ww has joined #rdf-wg 15:09:40 zakim, who is on the phone? 15:09:40 On the phone I see FabGandon, +31.20.598.aaaa, AndyS1, Sandro, gavinc, mbrunati, LeeF, Peter_Patel-Schneider, [Garlik], OlivierCorby, hsbauer, +43.512.507.aabb, cygri, Souri_, 15:09:43 ... AlexHall, PatH, Luca, Luca.a (muted), zwu2 (muted), ??P8 15:09:44 [Garlik] has SteveH, mischat 15:09:45 drop action-6 15:09:49 I'm unware of any that support anything else (other then Talis) 15:09:53 close action-6 15:09:53 ACTION-6 Provide use case for graphs closed 15:09:56 zakim, ??P8 is me 15:09:56 +ww; got it 15:09:58 action-6: dropped 15:09:58 ACTION-6 Provide use case for graphs notes added 15:10:01 close action-6 15:10:01 ACTION-6 Provide use case for graphs closed 15:10:02 zakim, mute me 15:10:02 ww should now be muted 15:10:15 gavin: i wasn't interested in SPARQL result formats. I was only interested in RDF imports and RDF serialisation outputted via the CONSTRUCT verb 15:10:17 action-19: done 15:10:17 ACTION-19 Make a survey on what serializations triple stores use in the wild notes added 15:10:33 zwu2: can you have a look at http://www.w3.org/2011/rdf-wg/wiki/TriplestoreRDFSupport and could you update the Oracle support 15:10:33 close action-19 15:10:33 ACTION-19 Make a survey on what serializations triple stores use in the wild closed 15:10:37 http://www.w3.org/2011/rdf-wg/wiki/N-Triples-Format 15:10:50 \me don't know who I am on the phone 15:10:52 guus: thomas is not here, so action-20 is left pending 15:11:05 close action-24 15:11:05 ACTION-24 Collect issues and write a proposal standardizing N-Triples. closed 15:11:21 topic: F2F 15:11:36 guus: an agenda has been posted on the mailing list 15:12:02 http://www.w3.org/2011/rdf-wg/wiki/F2F1#Agenda 15:12:04 q+ 15:12:06 dfensel6_ has joined #rdf-wg 15:12:13 -Luca.a 15:12:18 ... it has been suggested to shift the schedule later 15:12:24 ... to make it easier for remote participants 15:12:38 +Luca.a 15:12:51 zakim, who is talking? 15:12:57 Zakim, +Luca.a is me 15:12:57 sorry, AZ, I do not recognize a party named '+Luca.a' 15:13:01 Zakim, Luca.a is me 15:13:01 +AZ; got it 15:13:04 sandro, listening for 11 seconds I heard sound from the following: +31.20.598.aaaa (3%), +43.512.507.aabb (4%) 15:13:08 Zakim, mute me 15:13:08 AZ should now be muted 15:13:48 ... We could move it 30minutes later on the first day. 15:14:07 q+ 15:14:14 ... and 1h later on the second day. 15:14:17 PROPOSED: Move Day-1 agenda 30 minutes later, for people in other time zones, and Day-2 60 minutes later. So business starts at 10am. 15:14:42 cygri: I have a plane, so 1h later is max for me 15:15:01 peter: I also have a train on the evening 15:15:31 ... As the schedule has been announced, I think we should not change the schedule, at least on the 2nd day. 15:15:32 as remote participant, later is inconvenient for me, but i don't strongly object, defer to consensus 15:15:52 sandro: let's put the breakouts first, since remote participation probable wont work.... 15:16:03 http://www.w3.org/2011/rdf-wg/wiki/F2F1#Agenda 15:16:07 q- 15:16:10 guus: by moving the breakup, we can make it more convenient 15:16:21 UTC+2 15:16:26 http://www.w3.org/2011/rdf-wg/wiki/F2F1#Agenda 15:16:45 UTC+2, GMT changes with BST ;) 15:17:16 mmm... midnight telecon 15:17:20 guus: any objections to switch breakout and cleaning sessions on the 2nd day? 15:17:33 s/breakup/breakout/ 15:18:05 .) 15:18:06 ... or we still have the option of making the 2nd day only 30 minutes later 15:18:12 Guus: Day 2 goes until 5pm, and I'll delay the first day 30 mins. 15:18:15 thank you, Guus. 15:18:25 q+ 15:19:04 guus: Ivan is not here, we have no further detail about the phone bridge 15:19:19 at cwi, any suggestion where to go exactly? 15:19:36 sandro: I'll try to setup a video, so that remote participants can see the presents 15:19:40 q- 15:19:41 ... bandwidth permitting 15:20:23 guus: normally the breakout sessions wil have no remote participants 15:20:44 ... but I will see if we can get a 2nd speaker phone 15:21:21 pathayes 15:21:36 PatHayes +1000 15:21:42 very considerate :) 15:21:52 pathayes: it is difficult for remote participants to actually participate 15:22:19 ... we would need some "phone scribe" to ensure that they can 15:22:43 topic: graph task force 15:22:51 guus: a number of issues have been raised 15:23:05 AZ has joined #rdf-wg 15:23:18 ... I propose we have a short discussion about each of them. 15:23:43 ( Pat, I like this idea of someone who is charged with representing the remote participants. I think their title should be "The Avatar." :-) 15:23:44 ... Thanks to Richard for accepting to do a summary for the F2F. 15:23:52 http://www.w3.org/2011/rdf-wg/track/issues/raised 15:24:34 issue-5 is about defining a datatype for graph literals 15:25:01 sandro: N3 uses the {} to describe a g-snap 15:25:08 q+ 15:25:18 q+ 15:25:23 ... it could be seen as a special literal, with a special datatype 15:25:35 ... and its own lexical/value spaces 15:25:45 q? 15:25:53 ... The issue is: is this valuable? Do we want to keep that? 15:25:53 zakim, unmute me 15:25:53 ww should no longer be muted 15:26:26 ww: if we make datatypes like that, how would that affect blank node scoping rules? 15:26:45 ... (even if those rules are not completely explicit) 15:27:13 ... if a quoted graph is a literal, what happens to the bnodes it shares with the enclosing graph 15:27:16 zakim, mute me 15:27:16 ww should now be muted 15:27:20 sandto: if they are considered as literal, 15:27:23 q+ to ask about N3 graphs and variables (? log:semantics) 15:27:25 ... there would be no sharing at all 15:27:38 ack ww 15:27:44 cygri: I'm not sure it is particularly useful, 15:27:48 zakim, mute me 15:27:48 ww should now be muted 15:27:56 ack cygri 15:28:23 ... maybe this could be part of a larger solution to a larger problem? 15:28:25 ( cygri sounds like he's in an underwater cavern ) 15:28:40 ack AndyS 15:28:40 AndyS, you wanted to ask about N3 graphs and variables (? log:semantics) 15:28:56 sandro: not a solution for the moment, just something we should keep in mind 15:29:04 PatH has joined #rdf-wg 15:29:06 (sandro, it's a hallway with really bad acoustics) 15:29:07 ack me 15:29:35 andy: are you implying to also keep variables and more things from N3? 15:29:41 sandro: I was really just suggesting a quick and easy way to get SOME of what N3 gives us, using datatype for graph literals. 15:29:54 ISSUE-14? 15:29:54 ISSUE-14 -- What is a named graph and what should we call it? -- raised 15:29:54 http://www.w3.org/2011/rdf-wg/track/issues/14 15:29:58 Call it "named graph" ? 15:30:03 +1 ;) 15:30:11 +1 15:30:12 sandro: the idea is not to import those more complicated things 15:30:34 Call it a Name-Graph-Binding. 15:30:44 g-pair? 15:31:03 They have been called 'named graphs' for about a decade now. Why change anything? 15:31:07 SPARQL already refers to it as Named Graphs 15:31:33 sandro: find the term 'named graph' confusing, as for me graph means g-snap 15:32:01 named numbers... Pi, root-2, ... 15:32:25 q? 15:32:36 sandro: yes, mathematical graphs like numbers can have names 15:33:12 q+ 15:33:16 ... but it in the case of named graph, it seems to me that we want to name the binding 15:33:30 ... i.e. the graph bound to the name can change 15:33:35 i think i understand (named) graphs in a similar way to sandro 15:33:41 "Named G-Box" 15:33:43 ack cygri 15:33:53 pathayes: in the original proposal, it was indeed graphs that were named 15:34:11 named 15:34:13 ... but you suggest that in practice, the *g-box* are named? 15:34:16 sandro: yes 15:34:33 cygri: you are assuming a particular proposal where the g-box are named 15:34:33 15:34:43 ... in that case, "named graph" does not make much sense 15:35:22 ... In SPARL, there are two notions: 15:35:29 ... dataset: a set of g-snaps 15:35:42 graph store 15:35:51 graph store: a set of g-boxes 15:35:53 (sorry for poor acoustics) 15:36:12 guus: do we need a notion of named g-snaps ? 15:36:17 +q 15:36:43 I think we might need the idea of a named g-snap, yes. Need to think about this more. 15:36:48 In Anzo, we use the term "named graph' for named g-box, despite the linguistic imprecision 15:36:48 dataset can (often, does) indirect -- query over the value (g-snap) 15:36:58 sandro: I have never seen anyone with a good use case for named g-snap 15:37:04 q+ 15:37:33 i hope that whatever happens here can we make sure that we align with SPARQL 15:37:33 guus: most use cases are about provenance, which is about naming g-box 15:37:38 We can always think of a g-snap as a 'fixed' g-box. But then we would need to be able to clearly say that it is 'fixed' and what this means. 15:37:41 ... or am I over-interpreting? 15:38:05 +1 to PatH 15:38:22 i tend to think that provenance actually has more to do with g-snaps 15:38:35 dfensel6__ has joined #rdf-wg 15:38:45 sandro: off-topic announcement: the provenance WG just started, interested participants should keep an eye on it 15:39:27 s/keep an eye on it/join it 15:39:49 pat: Naming of g-snaps is just naming of read-only r-boxes 15:39:51 q+ 15:39:51 +1 15:40:11 q+ to talk about explicit metadata on gboxes & time 15:40:22 AZ has joined #rdf-wg 15:40:46 gavin: I don't think anybody ever needed to name g-snaps 15:40:55 gavin: People seem to keep naming mutable g-boxes, not immutable g-boxes. 15:41:00 q- 15:41:06 ack gavin 15:41:10 (too noisy here) 15:41:15 Point well taken. I agree. Maybe we should leave this matter to the wide world to sort out. 15:41:28 +1 15:41:42 gavin: it could be useful to truy to name g-snaps, but I don't think anybody ever tried to do that 15:42:10 i wanted to say: in sparql it's just g-snaps. sparql says nothing about what the named graph uri identifies. it's just a data structure for having multiple graphs. that's sufficient for many use cases 15:42:12 That was gavin's point about nobody having implemented this. 15:42:15 sandro: I like the idea of naming a g-box that does not change 15:42:42 ... but it is interesting also to talk about a g-box at a particulat instant in time 15:42:48 If we can say is immutable in RDF< then a box can say that it itself is immutable. 15:43:21 rdf:type eg:ImmutableGBox 15:43:27 +1 15:43:29 issue-15? 15:43:29 ISSUE-15 -- What is the relationship between the IRI and the triples in a dataset/quad-syntax/etc -- raised 15:43:29 http://www.w3.org/2011/rdf-wg/track/issues/15 15:43:58 guus: this issue has no owner 15:44:04 sandro: must be something I typed in the IRC 15:44:49 ... In several previous proposal, there is no explicit relationship between the IRI and the triples 15:45:04 ... In N3 there is a relationship, usually owl:sameAs 15:45:06 Isnt this the same issue we were just talking about? 15:45:19 OK 15:45:19 pchampin: @PathH yes, it seems to me 15:45:33 sandro: yes, they are related 15:45:38 OK to leave them separate issues. 15:45:42 trig == n3 w/ implied owl:sameAs (and no nesting) 15:45:51 ACTION: richard to write up the different options re ISSUE-15 15:45:51 Created ACTION-25 - Write up the different options re ISSUE-15 [on Richard Cyganiak - due 2011-04-13]. 15:46:21 guus: so we should open those issues, any one objecting? 15:46:40 issue-17? 15:46:40 ISSUE-17 -- How are RDF datasets to be merged? -- raised 15:46:40 http://www.w3.org/2011/rdf-wg/track/issues/17 15:46:52 guus: david on the call? 15:48:07 peter: we need to fix a problem with the SPARQL definition, sent some comment to the mailing list 15:49:12 http://lists.w3.org/Archives/Public/public-rdf-wg/2011Apr/0077.html and peter's reply at http://lists.w3.org/Archives/Public/public-rdf-wg/2011Apr/0078.html 15:49:25 Why is this our business? Surely the notion of RDF Store belongs to SPARQL , no? 15:49:39 pchampin: +1 PatH 15:50:08 SPARQL has a definition of the merge of RDF datasets. This is closely related to named graphs, which we are supposed to be dealing with. 15:50:26 The notion of 'default' for example isnt in the RDF specs anywhere. 15:50:29 - +43.512.507.aabb 15:50:45 I see comment, but no proposal for change. The editor will address the comment. 15:51:33 I was trying to not prejudice any solution (by not providing my own). I pointed out that the "defintion" allows multiple answers. 15:51:35 On the face of it, the definition in the emails does not make sense, since it presumes that one name can name two different graphs. 15:52:10 PatH: that's why i'd like to treat them as merely (URI, g-snap) pairs 15:52:10 Which if it happens should be an error condition, seems to me. 15:52:23 OK 15:52:45 open issue-17 15:52:53 graphs are closed descriptions? 15:52:55 issue-18? 15:52:55 ISSUE-18 -- How do we parse "18." in Turtle? -- raised 15:52:55 http://www.w3.org/2011/rdf-wg/track/issues/18 15:53:17 q+ 15:53:32 zakim, unmute me 15:53:32 ww should no longer be muted 15:54:01 sandro, would you like to mention bnode skolemization here? 15:54:03 PatH, perhaps the same graph is named in both those datasets with competing assertions as to the contents of that graph? 15:54:36 issue 21 15:54:43 ISSUE-21? 15:54:43 ISSUE-21 -- Can Node-IDs be shared between parts of a quad/multigraph format? -- raised 15:54:43 http://www.w3.org/2011/rdf-wg/track/issues/21 15:55:26 q+ 15:55:33 i think i'm +1 with ww 15:55:38 +1 sandro 15:55:40 +q 15:55:43 -q 15:55:47 zakim, mute me 15:55:47 ww should now be muted 15:55:51 ack sandro 15:55:51 sandro, you wanted to talk about explicit metadata on gboxes & time 15:55:51 ww: what happens if we take two files containing triples, and merge them in a format supporting quads? 15:56:00 sandro: Since you have to do bnode renaming in merging turtle, why not for quads? 15:56:00 merge is on g-snaps, not g-texts? 15:56:02 ack ww 15:56:11 zakim, mute me 15:56:11 ww should now be muted 15:56:13 ack Souri 15:56:15 sandro: you should not be able to simply merge 2 ttl files. You should rename bnodes before. 15:56:41 souri: the notion of having the same bnode in two different graphs seems odd to me 15:56:55 q+ 15:56:55 sandro: I think bnodes are scoped to the document, not to the graph 15:56:59 Blank node *identifiers* are scoped according to conventions defined by the particular format. 15:57:11 ... which is convenient for the moment as our documents contain only one graph 15:57:16 Blank nodes should be unique to a 'grpah' (= g-box) 15:57:23 q+ 15:57:27 ... but if a document was to contain several graphs, it would happen. 15:57:52 ... Consider a subgraph of a given graph; they can obviously share bnodes. 15:58:00 blank node scope comes up in several places... 15:58:00 It's not clear to me if we're discussing the scope of blank nodes, the mathematical objects, or the scope of blank node identifiers, the way of writing down the things in g-texts, or both 15:58:12 guus: isn't that another issue? 15:58:31 q- 15:58:32 +1 sandro's correction of loose language - bnode identifiers are what have scope 15:58:53 +1 sandro. 15:59:12 souri: we are talking from a storing point of view 15:59:24 Both - bnodes as variables have a scope but != bnode labels in a serialization 15:59:43 ... _:x boild down to prefixing x with the name of the graph 16:00:30 Lee; blank nodes dont have scope. They are gloablly unique. Bnode IDs have scope. 16:00:42 ... the blank node would -have- to be unique to a graph. Two graphs may exist on diffrent systems on the web, if you want their identity to be the same same USE A URI. 16:00:59 +1 to PatH's description 16:01:22 sandro: some SPARQL endpoints, like 4store, have the default graph to be the union of all other stores 16:01:27 I will try to add some text to clarify all this. 16:01:36 propose to add Pat's description to Issue 21 description 16:01:53 thx Pat 16:01:56 q+ 16:02:05 q+ 16:02:17 ... so how do we serialize this? 16:02:17 ack Souri 16:02:27 Souri, sandro, please CC me on any offline emails. 16:02:45 q- 16:03:05 pls no offline emails 16:03:17 q? 16:03:22 souri: we have to distinguish between _:x used in two different files 16:03:40 ... bnodes are scoped to the graph 16:04:15 It is possible for two RDF graphs to contain the "same" bnode, but the RDF semantics doesn't let you see any effects of this. 16:04:16 action PatH to write an description of action-21 16:04:16 Created ACTION-26 - Write an description of action-21 [on Patrick Hayes - due 2011-04-13]. 16:04:41 issue-22? 16:04:41 ISSUE-22 -- Does multigraph syntax need to support empty graphs? -- raised 16:04:41 http://www.w3.org/2011/rdf-wg/track/issues/22 16:05:22 LeeF: a quad store can be naively seens as a big table with 4 columns 16:05:43 q? 16:05:44 ... but this naive view does not allow to represent an empty graph 16:06:09 ... so should serialization support that? Some serialization can (e.g. Trig) 16:06:14 +q 16:06:16 Nah, its NIL is LISP. Yes, lets allow this. 16:06:32 +q 16:06:55 When "named X" considered, becomes more relevant 16:07:12 peter: are we going to allow necessarily empty g-*? 16:07:15 BTW, in the RDF semantics, the empty graph is (a) unique and (b) always false. 16:07:15 q+ to answer peter 16:07:33 guus, I just created ISSUE-23 to capture discussion i had with dave on the mailing list 16:07:41 ack gavin 16:07:48 AZ has joined #rdf-wg 16:08:10 suppose you have a set of quads - how to you know that you have all the triples in a particular graph? 16:08:10 gave: most document databases (e.g. mongodb) explicitly do not allow empty documents 16:08:17 gavin: XML and MongoDB don't allow empty documents. 16:08:24 ... an XML doc has to contain at least an element 16:08:27 ack PatH 16:08:37 i'm not sure that's the same issue? i'll never know that, whether i'm writing down 0 triples or 100 triples 16:08:41 right? 16:08:42 to follow this on ... all the possible empty named graphs already exist in RDF 16:09:04 PatH: I was going to vote for empty graph, mathematically more elegant 16:09:11 intuitively +1 to PatH 16:09:12 ... they are useful limit cases 16:09:22 zakim, who is making noise? 16:09:24 pchampin: +1 16:09:27 FWIW, I was trying to lay out the issue as I understand it neutrally, I do have a strong opinion on how the issue should be resolved :) 16:09:33 mischat, listening for 10 seconds I heard sound from the following: Sandro (5%), Luca (66%) 16:09:40 I think the morse code is agreeing with us. 16:09:43 sandro: most (all?) RDF syntax allow to convey the empty graph 16:09:53 ... forbidding that would be a problem 16:09:59 -ww 16:10:19 guus: position for the moment: allow empty graph unless there is a very good reason not too 16:10:25 zakim, mute luca 16:10:25 Luca should now be muted 16:10:28 the flip side is that managing graphs as first class entity creates additional complexity (like tables in an RDBMS) 16:10:32 ... but let's keep the issue open for the moment 16:10:38 ISSUE-23? 16:10:38 ISSUE-23 -- Does going from single-graph to multi-graph require new format and new media types? -- raised 16:10:38 http://www.w3.org/2011/rdf-wg/track/issues/23 16:11:36 Souri, SPARQL Update acknowledged that by trying to allow both sorts of stores likely behavior 16:11:57 LeeF, and I think that makes the SPARQL Update spec quite awkward 16:12:10 sandro: I will open issue-23 16:12:12 cygri, I don't necessarily disagree with that 16:12:25 topic: cleanup issues 16:12:37 guus: we have a face at the F2F to discuss them 16:12:37 LeeF, as a matter of principle, I think “let's allow both” is rarely the right answer in a spec 16:12:50 cygri, I also don't disagree with that 16:12:54 :-) 16:13:13 ... we need to make some progress on the issue about the "RDF Recommendation Set" 16:13:24 q? 16:13:34 ... and start thinking about editors for those documents 16:13:37 sandro has changed the topic to: Agenda: q- 16:14:05 -Peter_Patel-Schneider 16:14:07 bye 16:14:10 -AlexHall 16:14:10 thank you! bye! 16:14:13 -cygri 16:14:14 -PatH 16:14:14 -zwu2 16:14:16 -Souri_ 16:14:17 -OlivierCorby 16:14:18 -[Garlik] 16:14:19 -AZ 16:14:20 -Sandro 16:14:22 RRSagent, draft minutes 16:14:23 I have made the request to generate http://www.w3.org/2011/04/06-rdf-wg-minutes.html pchampin 16:14:24 -FabGandon 16:14:28 -gavinc 16:14:32 AlexHall has left #rdf-wg 16:14:35 ok, bye 16:14:37 FabGandon has left #rdf-wg 16:14:40 -LeeF 16:14:43 -mbrunati 16:14:49 -AndyS1 16:14:50 - +31.20.598.aaaa 16:14:59 AndyS1 has left #rdf-wg 16:15:29 -hsbauer 16:15:47 gavin has left #rdf-wg 16:17:22 AndyS has joined #rdf-wg 16:17:30 I'm on irc, but not th ephone. 16:18:27 mbrunati has left #rdf-wg 16:18:38 sure, how far did you get? 16:18:47 I basically know how to publish the minutes with RRSAgent 16:18:53 Ah. 16:18:54 which are there 16:18:55 http://www.w3.org/2011/04/06-rdf-wg-minutes.html 16:18:59 but not public 16:19:12 but I know nothing about the wiki thing 16:19:38 Take a look at this, and let me know if it's not clear: http://www.w3.org/2009/CommonScribe/manual.html 16:19:49 (you' 16:19:52 ok, thanks 16:19:56 (you're on step 3 now) 16:20:09 SteveH has joined #rdf-wg 16:21:08 yep, figured that out 16:21:12 however, I have no access to http://www.w3.org/2009/CommonScribe/panel/ 16:21:14 :-( 16:21:34 I'm *only* an invited expert, that must be why... 16:21:37 really? Can you see http://www.w3.org/Member/ 16:22:26 no 16:22:34 keeps prompting me for a login/pw 16:22:45 and would not accept my W3C credential 16:22:54 which work well on other pages 16:23:13 I see. You're a "public invited expert" not a "member invited expert". I wonder how that happened..... :-( 16:23:34 me too 16:23:45 I didn't even know about that subtle distinction... 16:23:53 where can you see that? 16:23:58 Well, for now I did step 3, so it's copied to the wiki. 16:24:02 (on a page not accesible to me, maybe ;-) 16:24:08 I see it in http://www.w3.org/2000/09/dbwg/details?group=46168&public=1 16:24:14 just under your name, 16:24:40 thks 16:24:42 I'm trying to remember why you're an IE. What's your affiliation? Is it an org that is in process of joining W3C? 16:25:23 I think you'll be able to do the editing-the-wiki and preview part of the minutes, but not the final "save", so just email me when you're ready, and I'll do that part. 16:26:59 well, I can't "preview" either :-( 16:27:08 blah..... :-( :-( 16:27:22 (thinking) 16:27:24 my university is not a member yet 16:27:35 but yes, they are in the process of joining 16:27:46 so, this is a short term problem, good. 16:28:09 :-) 16:28:14 ok, I'll do some cleaning 16:28:44 blind cleaning, that is :) 16:29:02 thanks for your help 16:30:54 The permissions for the script seem to be set to allow everyone, and I don't have time to debug it now, so yeah, thanks for cleaning-blind, sorry! 16:31:19 mischat has joined #rdf-wg 16:35:00 disconnecting the lone participant, Luca, in SW_RDFWG()11:00AM 16:35:01 SW_RDFWG()11:00AM has ended 16:35:05 Attendees were FabGandon, +31.20.598.aaaa, AndyS1, Sandro, gavinc, LeeF, Peter_Patel-Schneider, OlivierCorby, mbrunati, +43.512.507.aabb, SteveH, mischat, Souri_, AlexHall, cygri, 16:35:08 ... PatH, hsbauer, Luca, zwu2, ww, AZ 17:07:20 AndyS has joined #rdf-wg 18:10:45 mischat has joined #rdf-wg 18:19:38 Zakim has left #rdf-wg 18:21:52 danbri has joined #rdf-wg