15:00:52 RRSAgent has joined #rdf-wg 15:00:52 logging to http://www.w3.org/2013/06/19-rdf-wg-irc 15:00:54 RRSAgent, make logs world 15:00:54 Zakim has joined #rdf-wg 15:00:56 Zakim, this will be 73394 15:00:56 ok, trackbot; I see SW_RDFWG()11:00AM scheduled to start now 15:00:57 Meeting: RDF Working Group Teleconference 15:00:57 Date: 19 June 2013 15:01:04 zakim, dial ivan-voip 15:01:04 ok, ivan; the call is being made 15:01:24 Chair: David Wood 15:01:29 zakim, who is here? 15:01:29 SW_RDFWG()11:00AM has not yet started, ivan 15:01:30 On IRC I see RRSAgent, pfps, gkellogg, tbaker, PatH, pchampin, manu, Guus, AndyS, TallTed, SteveH, davidwood, ivan, manu1, gavinc, yvesr, sandro, trackbot, ericP, mischat 15:01:30 Zakim? I am here... 15:02:05 TallTed has changed the topic to: RDF WG -- http://www.w3.org/2011/rdf-wg/ -- current agenda http://www.w3.org/2011/rdf-wg/wiki/Meetings:Telecon2013.06.19 15:02:07 AZ has joined #rdf-wg 15:02:19 Zakim, this is 73394 15:02:19 ok, TallTed; that matches SW_RDFWG()11:00AM 15:02:22 +[IPcaller] 15:02:23 Zakim, who's here? 15:02:24 On the phone I see +1.408.992.aaaa, ??P24, davidwood, Ivan, PatH, [IPcaller] 15:02:24 On IRC I see AZ, Zakim, RRSAgent, pfps, gkellogg, tbaker, PatH, pchampin, manu, Guus, AndyS, TallTed, SteveH, davidwood, ivan, manu1, gavinc, yvesr, sandro, trackbot, ericP, 15:02:27 ... mischat 15:02:28 zakim, IPCaller is me 15:02:28 +AndyS; got it 15:02:40 zakim, I am ??P24 15:02:43 +gkellogg; got it 15:02:53 +OpenLink_Software 15:03:26 Zakim, OpenLink_Software is temporarily me 15:03:27 +TallTed; got it 15:03:29 +Sandro 15:03:35 Zakim, mute me 15:03:35 TallTed should now be muted 15:03:44 + +081165aabb 15:03:52 Zakim, aabb is me 15:03:52 +AZ; got it 15:04:13 +GavinC 15:06:34 [[!RDF11-CONCEPTS]] 15:06:54 markus has joined #rdf-wg 15:07:36 scribenick: AndyS 15:07:43 scribe: AndyS 15:07:49 PROPOSED to accept the minutes of the 12 June telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-06-12 15:07:52 agenda: http://www.w3.org/2011/rdf-wg/wiki/Meetings:Telecon2013.06.19 15:07:57 minutes are fine 15:08:24 RESOLVED to accept the minutes of the 12 June telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-06-12 15:08:30 davidwood, i'm in the LDP F2F, but can switch over here when talking about Turtle 15:08:35 Review of action items 15:08:36 http://www.w3.org/2011/rdf-wg/track/actions/pendingreview 15:08:36 http://www.w3.org/2011/rdf-wg/track/actions/open 15:08:41 topic: Action items 15:09:13 ACTION-226? 15:09:13 ACTION-226 -- Richard Cyganiak to implement ISSUE-111 resolution -- due 2013-02-13 -- OPEN 15:09:13 http://www.w3.org/2011/rdf-wg/track/actions/226 15:09:24 pfps: Close action on ACTION-226 for ISSUE-111 15:09:36 ... no-op. 15:10:12 Close ACTION-226 15:10:12 Closed ACTION-226 Implement ISSUE-111 resolution. 15:10:53 ACTION-256? 15:10:54 ACTION-256 -- Gavin Carothers to link TriG to new text in RDF Concepts -- due 2013-05-01 -- OPEN 15:10:54 http://www.w3.org/2011/rdf-wg/track/actions/256 15:10:55 pfps: Need work on ACTION-256 15:11:11 ACTION: ericP to respond to LC issues (11, 12, 18, 37) 15:11:12 Created ACTION-273 - Respond to LC issues (11, 12, 18, 37) [on Eric Prud'hommeaux - due 2013-06-26]. 15:11:39 +??P35 15:11:40 that should close 271 15:11:42 zakim, ??P35 is me 15:11:42 +markus; got it 15:11:58 (Archaeology occurs) 15:13:26 +Souri 15:13:27 https://dvcs.w3.org/hg/rdf/raw-file/default/trig/index.html#sec-graph-statements 15:13:42 sandro: I see the resolution to issue-131 has not yet been reflected in rdf-concepts. https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html#section-dataset 15:13:47 Souri has joined #rdf-wg 15:13:49 +[IPcaller] 15:14:00 pfps: action-107 has not made it into concepts. 15:14:05 ACTION-107? 15:14:05 ACTION-107 -- Richard Cyganiak to add a note to RDF Concepts re ISSUE-75 -- due 2011-10-20 -- CLOSED 15:14:05 http://www.w3.org/2011/rdf-wg/track/actions/107 15:14:09 zakim, +[IPcaller] is me 15:14:09 sorry, Guus, I do not recognize a party named '+[IPcaller]' 15:14:30 zaki, IPCaller is me 15:14:35 gavinc: wrong action? 15:15:00 zakim, IPCaller is me 15:15:00 +Guus; got it 15:15:12 zakim, mute me 15:15:12 Guus should now be muted 15:15:27 pfps: 24 April ... blank nodes can be shared 15:15:41 gavinc: done ... need more for blank node for graph names. 15:15:43 https://www.w3.org/2013/meeting/rdf-wg/2013-06-12#resolution_1 15:16:15 davidwood: I'll do that 15:16:41 ACTION: davidwood to implement https://www.w3.org/2013/meeting/rdf-wg/2013-06-12#resolution_1 in Concepts 15:16:41 Created ACTION-274 - Implement https://www.w3.org/2013/meeting/rdf-wg/2013-06-12#resolution_1 in Concepts [on David Wood - due 2013-06-26]. 15:17:18 pfps: success on action-272 15:18:11 noisy typing 15:18:16 davidwood: proposal to deal with public comments which are discussion and formal comments 15:18:16 action-272 is closed 15:18:29 close action-272 15:18:30 Closed ACTION-272 Send email describing the differences between Antoine's view and the current draft (eg you don't know what the datatype interpretation is). 15:18:31 for the record, I closed action 271, done 15:19:02 ... list is part of the formal process but it has had "other stuff" recently (and before). Need to get under control. 15:19:26 ... danger of loosing (real) comments 15:19:35 q+ 15:19:41 s/loosing/losing/ 15:19:50 ... so please do not reply until there is a formal thing to say as decided by a chair. 15:20:10 q- because Pat said what I wanted to 15:20:15 ack pfps 15:20:25 path: std response for incoming. 15:20:34 ... will draft text 15:20:42 sandro: set up as autoreply 15:21:13 gavinc: where should be the discussion be? 15:21:28 semantic-web list is the propoer forum for many discussions 15:21:46 davidwood: else where eg. semantic-web@w3.org ... need to have a functioning comments process 15:21:52 publi-comments only for relevant design dcomments 15:21:53 +1 to this sentiment 15:22:45 Proposed autorespond text: DUring the Last Call period, this email list is restricted to change requests on the LC documents and official responses to those requests. Members of the WG will not respond to more general comments or discussions on this list. PLease re-post your comment on a different public list. THank you. 15:22:54 gavinc: e.g. discussion on turtle as has happened. 15:23:04 q+ 15:23:29 the autorespond text should be permanent, not just during last call 15:23:47 Extra list? rdf-spec-discuss? Specifically NOT comments. 15:23:51 ack pfps 15:24:19 in other groups we have always done it this way: first propose a draft response to the WG 15:24:27 SO lets add a pointer to that list in the autrespond text. 15:24:29 pfps: semantic-web@ is for this. 15:25:15 ... drive-by email lists 15:25:20 q? 15:25:59 Zakim, unmute me 15:25:59 TallTed should no longer be muted 15:26:00 davidwood: pat/text :: sandro/setup auto :: davidwood/tell list 15:26:05 the message to the chairs should normally be cc or to WG as a whole, so all can see what;s happening 15:26:46 sandro: TallTed -- please pass on this conversation to Kingsley. 15:26:53 pchampin has joined #rdf-wg 15:27:06 TallTed: OK - will try. 15:27:31 Zakim, mute me 15:27:31 TallTed should now be muted 15:27:35 topic: LC Drafts of Concepts and Semantics 15:27:58 davidwood: semantics first 15:28:06 Discussion thread on review by Antoine of Semantics: 15:28:06 http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jun/0085.html 15:28:34 (scribe has not followed this thread in email in all details) 15:29:05 zakim, who is on the phone? 15:29:05 On the phone I see +1.408.992.aaaa, gkellogg, davidwood, Ivan, PatH, AndyS, TallTed (muted), Sandro, AZ, GavinC, markus, Souri, Guus (muted) 15:30:09 +??P5 15:30:12 q+ 15:30:16 zakim, ??P5 is me 15:30:16 +pchampin; got it 15:30:17 AZ: datatype URIs -- new design has just a set of IRIs , no maps -- we need to know what they denote 15:30:44 ... second issue is entailment of set sof RDF graphs (scribe: union discussion?) 15:31:47 q? 15:31:50 ... set entails the union, it was each of the sets. Does not follow normal practice. RDF is not the same as conjunction (correct?) 15:32:26 ... will provide some proposed text that meets my concerns. 15:32:50 ack ivan 15:33:10 q 15:34:23 ivan: restrictions on datatype URIs ... normative text around it covers the conditions ... semantic conditions are not all in the maths 15:35:02 AZ: pfps argues there is not real difference as RDF 2004. But then I don't don't understand why the new design/ expression of design is better. 15:35:07 It's editorial, but important editorially. 15:35:28 there may be a point on the definition of entailment on sets of graphs 15:35:34 ivan: better exposition 15:35:59 +1 to Ivan 15:36:05 .. a big issue has been the limted readership of the doc 15:36:46 AZ: I am not saying it is the same design. 15:37:17 ack PatH 15:38:04 path: latest draft has some improvements - let's discuss relative to that 15:38:14 ... fixes a small point 15:38:31 q+ 15:38:53 ... a slight difference to 2004 is that 2004 D-mapping allows xsd:string mapping to data times 15:39:18 ... and now it is not allowed to have a different D-entailment 15:39:30 Note that LC for Semantics is on our critical path; we have to have very good reasons NOT to go there; Feature at Risk is a possibility I guess 15:39:33 ... also I belive/hope that doc is more accessible. 15:39:36 not only is it illegal to mess with, e.g, xs datatypes, the mechanism in RDF is now consonant with the mechanism in xs datatypes 15:40:05 AZ: can add a constraint that these IRIs must map to the normal meaning 15:40:28 path: but then no need for a map 15:40:38 AZ: custom datatypes 15:40:57 q+ 15:41:06 ack AZ 15:41:30 path: can only recognize IRIs that are datatypes 15:42:28 ... IF e.g. GET shows that it is a datatype, then must use that defn of the datatype. 15:42:30 "RDF processors which are not able to determine which datatype is identifier by an IRI cannot recognize that IRI, and should treat any literals type with that IRI as unknown names." this is bit we are talking about? 15:43:53 q? 15:44:02 Guus has joined #rdf-wg 15:44:29 ack pfps 15:44:59 gavinC, yes. 15:45:08 (discussion of the true purpose of the MT doc) 15:45:41 btw, I like the language on what to do when there is an unknown datatype in the new semantics document then the old one. I had no clue what to do with unknown datatypes based on the old one, and the new one is VERY clear and even uses MAY/SHOULD. It's MUCH better 15:46:16 The normal Web machinery is not existing in the current version either 15:48:10 Gentlemen, I suggest you use the queue to respond. It will assist in limiting emotion. 15:49:20 +1 to peter 15:50:55 davidwood: Thank you for the discussion. AZ - do you need time to work on a proposal. 15:51:17 q+ 15:51:31 AZ: easier for me to work on a proposal for datatypes. Will try to do it quite quickly. 15:51:36 q+ 15:51:43 ... for other issue - less clear. 15:52:03 davidwood: can we go to LC? 15:52:05 ack ivan 15:52:14 (someone) no 15:52:45 +1 Ivan 15:53:47 Antoine appears to feel that there is something wrong in the current situation, so I don't think that agrees that it is just stylistic 15:54:18 AZ: This is not me raising a new issue. 15:54:42 antoine is right about the timing, but we're just not overcoming this disagreement 15:56:35 the question here, I think, is whether there is something technically wrong in the current semantics 15:57:08 q+ to talk about entailment 15:57:39 zakim, unmute me 15:57:39 Guus should no longer be muted 15:57:53 ack pfps 15:57:53 pfps, you wanted to talk about entailment 15:59:03 Not defined in term of merge 15:59:17 pfps; I now see the point about in the "union" strand of discussion 15:59:18 zakim, mute me 15:59:18 Guus should now be muted 15:59:29 defined according to traditional conjunction 16:00:11 zaim, code? 16:00:16 zakim, code? 16:00:16 the conference code is 73394 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), manu 16:00:26 +??P53 16:00:33 q+ 16:00:34 zakim, I am ??P53 16:00:35 +manu; got it 16:01:44 pfps: example - split one graph in two , share bnode across the halfs. 16:02:03 q? 16:02:06 q+ 16:02:16 ... union rejoins the use of blank nodes ... merge looses the connection in the original big graph. 16:03:38 q? 16:03:45 q+ 16:04:38 ack PatH 16:04:43 can't we just lean on datasets? Where we SAY that blank nodes are shared inside a dataset? 16:04:46 entailments of sets of RDF graphs - 2004 effectively uses merge 2013 uses union 16:05:17 q+ 16:05:32 path: because we have said we will support shared bnodes then merge would make this meaningless. 16:06:48 ... lots of pictures in the current doc to explain this all. 16:06:51 Ahhhh. Yes, Merge is kind of .... wacky ... now. There should just be UNION and also a COPY_GRAPH operation the replace blank nodes with a fresh ones. 16:06:55 ack AZ 16:07:02 q- 16:07:09 I don't agree with this analysis by Pat - people will not determine our stance on combining graphs by the definition of entailment 16:07:16 q? 16:07:19 q+ again 16:08:06 AZ: if a system knows two bnodes are the same they can use union 16:09:03 Then, is the following correct? (users decide which of the following to use when combining) UNION => reuse bNode labels, MERGE => generate new unique bNode labels 16:09:44 +1 Pat 16:09:49 +1 to Pat 16:09:50 Example -- :mary :hasChild _:b . :john :hasChild _:b . 16:10:13 path: in that graph - mary and john have a child in common. 16:10:33 AZ, thought experiment: does a graph entail the same thing as the union of all its triples (considered as singleton graphs)? 16:10:50 AZ: in subgraphs {:mary :hasChild _:b } { :john :hasChild _:b } 16:11:02 it's not a bug! 16:11:12 Path: bug is that the idea of bnode scope is not in the definitions. 16:11:34 -Souri 16:11:49 +[GVoice] 16:11:57 Zakim, [GVoice] is me 16:11:57 +ericP; got it 16:12:24 this actually has little to do with blank nodes per se, as the same issue arises with free variables in FOL formulae if you interpret free variables existentially 16:13:00 the question is: where is the quantifier of those existential variables? 16:13:02 Zakim, mute ericP 16:13:02 ericP should now be muted 16:13:06 tlr has joined #rdf-wg 16:13:25 q+ to say that blank nodes *do* work like variables in quantifier-free first-order formulae 16:13:27 q? 16:13:28 AZ seems to assume that it is at the graph level 16:14:01 by deciding that graph can share blank nodes, my interpretation is that we decided that it could be at a higher level 16:14:21 q? 16:14:33 guys, can you get off the bridge? 16:14:35 You can't share bNodes unless they originate from the same place because of all syntax parsing havign scoped labels. 16:14:41 we're having other groups that can't get their meetings running 16:14:44 davidwood: time 16:14:48 -Guus 16:14:49 ack pfps 16:14:49 pfps, you wanted to say that blank nodes *do* work like variables in quantifier-free first-order formulae 16:14:49 take a formula P(x) and another formula Q(x), when you form their conjunction you don't change the variables, you just put an "and" over them (i.e., union them) 16:15:16 ack again 16:16:00 Next time can we progress the TriG Turtle NQ, NT which have slipped again. 16:16:12 please kill this meeting now 16:16:16 I guess I feel that I have explained my posiiton as clearly and as fully as I can, and that the current draft also explains it as clearly as I know how. I rest my case. 16:16:19 there are plenty of other calls having trouble right now 16:16:23 Should be "easy" to agree to go to publication or find a process to get there. 16:16:26 -manu 16:16:49 -PatH 16:16:52 davidwood: I have worked through pfps review of concepts 16:16:52 bye 16:16:55 -Sandro 16:16:56 -Ivan 16:16:56 - +1.408.992.aaaa 16:16:56 -gkellogg 16:16:57 -davidwood 16:16:57 -GavinC 16:16:57 ADJOURNED 16:16:58 -TallTed 16:17:00 -AZ 16:17:01 -markus 16:17:03 -AndyS 16:17:20 tlr, understood and adjourned 16:17:32 -pchampin 16:17:37 -ericP 16:17:43 SW_RDFWG()11:00AM has ended 16:17:44 Attendees were +1.408.992.aaaa, Ivan, davidwood, PatH, AndyS, gkellogg, TallTed, Sandro, +081165aabb, AZ, GavinC, markus, Souri, Guus, pchampin, manu, ericP 16:20:14 Thanks! 16:22:09 sandro? W3C team? 16:22:20 yes? 16:22:21 https://www.w3.org/2013/meeting/rdf-wg/2013-06-19 --> internal server error 16:22:26 hold on 16:22:32 loosing my edits :-( 16:22:44 #@#*(@*# 16:22:45 :( 16:23:45 the internal error was, "Can't parse chatlog line '16:13:06 tlr has joined #rdf-wg'" and it's my quick-and-dirty code that made that result in lossage. 16:24:16 I had to edit tlr lines because he's not in the WG. 16:24:30 If i avoid that, can I continue editting? 16:24:52 I believe so. 16:25:20 same error 16:25:32 No - can't click on the date link to get a fresh copy to edit. 16:26:06 seems like its written before checking for parsability 16:27:11 hold on. 16:27:55 antici... pation. 16:28:01 RRSAgent, bye 16:28:01 I see 2 open action items saved in http://www.w3.org/2013/06/19-rdf-wg-actions.rdf : 16:28:01 ACTION: ericP to respond to LC issues (11, 12, 18, 37) [1] 16:28:01 recorded in http://www.w3.org/2013/06/19-rdf-wg-irc#T15-11-11 16:28:01 ACTION: davidwood to implement https://www.w3.org/2013/meeting/rdf-wg/2013-06-12#resolution_1 in Concepts [2] 16:28:01 recorded in http://www.w3.org/2013/06/19-rdf-wg-irc#T15-16-41