16:00:41 RRSAgent has joined #rdf-wg 16:00:41 logging to http://www.w3.org/2012/02/22-rdf-wg-irc 16:00:43 RRSAgent, make logs world 16:00:43 Zakim has joined #rdf-wg 16:00:45 Zakim, this will be 73394 16:00:45 ok, trackbot; I see SW_RDFWG()11:00AM scheduled to start now 16:00:46 Meeting: RDF Working Group Teleconference 16:00:46 Date: 22 February 2012 16:00:57 zakim, who is on the phone? 16:00:57 SW_RDFWG()11:00AM has not yet started, AndyS 16:00:59 On IRC I see RRSAgent, cgreer, Arnaud, gavinc, swh, AndyS, mischat, Guus, LeeF, MacTed, danbri, AndyS1, ivan, NickH, mdmdm, manu1, davidwood, manu, yvesr, trackbot, sandro, ericP 16:01:06 Zakim, who's on the phone? 16:01:06 SW_RDFWG()11:00AM has not yet started, swh 16:01:09 Zakim, this is 73394 16:01:11 On IRC I see RRSAgent, cgreer, Arnaud, gavinc, swh, AndyS, mischat, Guus, LeeF, MacTed, danbri, AndyS1, ivan, NickH, mdmdm, manu1, davidwood, manu, yvesr, trackbot, sandro, ericP 16:01:14 ok, gavinc; that matches SW_RDFWG()11:00AM 16:01:19 zakim, who is on the phone? 16:01:19 On the phone I see Guus, Sandro, [IPcaller], gavinc, Arnaud, +1.949.567.aaaa, OpenLink_Software 16:01:23 + +1.707.318.aabb 16:01:29 zakim, IPCaller is me 16:01:31 Zakim, OpenLink_Software is temporarily me 16:01:32 Zakim, mute me 16:01:36 +AndyS; got it 16:01:37 +MacTed; got it 16:01:40 MacTed should now be muted 16:01:40 zakim, aabb is me 16:01:45 +cgreer; got it 16:01:49 FabGandon has joined #rdf-wg 16:01:50 AZ has joined #rdf-wg 16:02:08 zakim, who is here? 16:02:08 On the phone I see Guus, Sandro, AndyS, gavinc, Arnaud, +1.949.567.aaaa, MacTed (muted), cgreer 16:02:12 On IRC I see AZ, FabGandon, Zakim, RRSAgent, cgreer, Arnaud, gavinc, swh, AndyS, mischat, Guus, LeeF, MacTed, danbri, AndyS1, ivan, NickH, mdmdm, manu1, davidwood, manu, yvesr, 16:02:14 ... trackbot, sandro, ericP 16:02:24 (regrets from me, sorry!) 16:02:51 +David_Wood 16:02:56 +FabGandon 16:03:17 AlexHall has joined #rdf-wg 16:03:24 area code 949 16:03:28 Zakim, aaaa is me 16:03:29 +swh; got it 16:03:37 +AlexHall 16:03:54 +??P7 16:03:54 bummer, danbri, but thanks for the nice perspective email. 16:04:30 Zakim, ??P7 is me 16:04:31 +AZ; got it 16:05:10 zwu2 has joined #rdf-wg 16:05:16 zakim, code? 16:05:16 the conference code is 73394 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), zwu2 16:05:16 Nick: will you be able to scribe? 16:05:38 zakim, dial ivan-voip 16:05:38 ok, ivan; the call is being made 16:05:40 +Ivan 16:05:51 11:05:14 *** NickH has been idle 772 minutes 16:05:51 I fear it falls to me... 16:05:55 Zakim, unmute me 16:05:55 MacTed should no longer be muted 16:07:53 PROPOSED: accept minutes of 15-Feb, http://www.w3.org/2011/rdf-wg/meeting/2012-02-15 16:08:11 RESOLVED: accept minutes of 15-Feb, http://www.w3.org/2011/rdf-wg/meeting/2012-02-15 16:08:23 scribenick: MacTed 16:08:56 +zwu2 16:08:57 TOPIC: open action item review, http://www.w3.org/2011/rdf-wg/track/actions/open 16:09:01 ericP sent an email claiming victory 16:09:15 action-147? 16:09:15 ACTION-147 -- Eric Prud'hommeaux to propose by next week text that replaces section 4.3 -- due 2012-02-22 -- OPEN 16:09:15 http://www.w3.org/2011/rdf-wg/track/actions/147 16:09:22 http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#sec-escapes 16:09:37 EricP: I need to slightly correct the proposal: the example of %-escaping has a \'d "-" in an IRI. I'll strike that when I no longer need to sit in judgement of my fellow man (jury duty). 16:09:43 http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#sec-strings vs http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#sec-escapes 16:11:46 zakim, who is on the phone? 16:11:46 On the phone I see Guus, Sandro, AndyS, gavinc, Arnaud (muted), swh, MacTed, cgreer, David_Wood, FabGandon, AlexHall, AZ, Ivan, zwu2 16:11:58 zakim, who is talking? 16:12:09 davidwood, listening for 10 seconds I heard sound from the following: Guus (52%), MacTed (17%), Ivan (17%) 16:12:24 Pat sent regrets yes 16:12:33 PatH, Regrets. I have to go give some talks at a local school. 16:13:48 TOPIC: RDF-ISSUE-83 (HTML-rel-meta): RDF/XML: Incorrect reference for use of HTML rel="meta" [RDF General] 16:13:52 issue-83? 16:13:52 ISSUE-83 -- RDF/XML: Incorrect reference for use of HTML rel="meta" -- raised 16:13:52 http://www.w3.org/2011/rdf-wg/track/issues/83 16:14:17 http://lists.w3.org/Archives/Public/public-rdf-wg/2012Feb/0092.html 16:16:19 ivan: issue should be retargeted against Primer 16:17:20 eric sent regrets 16:17:36 TOPIC: Named Graphs semantics 16:17:52 err, ericP has jury duty 16:18:07 starting from Pat Hayes' message and subsequent thread, http://lists.w3.org/Archives/Public/public-rdf-wg/2012Feb/0094.html 16:20:04 q? 16:20:12 + vs . according to PatH "Suppose we allow the terminal dot of a triple to be written as a plus sign, to mean that this triple is being interpreted as depending on its graph context, ie it is really a quad with the graph name as its contextual parameter. Call this a contextual triple and say that the graph is then a context. Contexts are involved in the truth of the triples they contain, so they are quad-graphs in disguise. Then two graphs can be merged just when ( 16:20:14 a) neither is a context (Ie they are normal RDF graphs) or (b) they are the same context (ie have the same graph label.)" 16:20:21 ... group effort to summarize Pat's proposal and confirm understanding thereof ... 16:20:34 q+ 16:22:31 ... consensus seems to be that typical current usage of "." is what Pat has proposed for "+" ... 16:23:22 ... goal seems to be getting a hint of the cost of merging differently contextualized graphs ... 16:24:27 q+ 16:24:35 ack sandro 16:24:37 guus proposes straw poll: who thinks it would be useful to add syntax for this, at this time? 16:25:05 s/useful/acceptable/ 16:25:12 sandro: syntax addition is needed, perhaps not the current proposal 16:25:12 ack AndyS 16:25:53 AndyS: if community perceives need for change, they'll pick up on the syntax. doesn't seem that syntax change will drive change well. 16:26:10 +1 to AndyS 16:26:32 Guus: consensus is it's worth consideration. 16:26:56 +q 16:27:16 sandro: number of things that are truly immutable is so small as to be uninteresting 16:27:37 ... need to know the context for virtually everything, it seems 16:27:57 Real world usage will continue to mix the '+' and '.' cases, so we need to be careful in defining the default case. I actually *prefer* to change the default case to being contextual. 16:28:04 ack gavinc 16:28:09 gavinc: distinction is needed between "statements which are near universally save to merge" and "statements which are likely to cause trouble if merged" 16:28:25 s/save/safe/ 16:28:29 +1 to davidwood, I prefer to contexualize the default case 16:28:36 q+ 16:29:38 AndyS: Pat seems to be saying, "in the current theory, you can always merge statements." but does that respect common practice? 16:29:57 AndyS: the graph that holds it seems to be an important aspect of a triple 16:30:14 ack davidwood 16:30:19 ack davidwood 16:30:44 davidwood: Real world usage will continue to mix the '+' and '.' cases, so we need to be careful in defining the default case. 16:30:45 davidwood: I think I actually *prefer* to change the default case to being contextual. 16:30:58 ack sandro 16:31:01 ack sandro 16:31:23 sandro: the person making the statement often doesn't think it's contextual, but changed perspective can change that perception... 16:31:24 +1 to Sandro 16:31:32 +1 16:32:13 ... big change to RDF theory, but probably not big change to RDF practice ... 16:33:07 +1 to the difference between theory and practice. people are already treating it as contextual. 16:33:32 It's entailment between graphs that relies on the universal context. 16:33:39 straw poll: "extant RDF should generally be considered to be contextual." 16:33:44 even when the context is just "the current state of my SPARQL store" 16:34:07 ... could phase as "gather some graphs together, then do current RDF stuff" 16:34:40 +1 16:34:41 +1 16:34:45 +1 16:34:45 +1 16:34:47 +1 16:34:51 +1 16:35:30 caveat the "contextual" in a maybe-weak, non technical sense, maybe "scoped" 16:35:47 +1 16:35:53 +1 to AndyS 16:35:56 +1 16:36:03 I think the question is way to vague / broad 16:36:09 +1 but I think everything is contextual, HTML pages too 16:36:10 Yes, AndyS has a good point 16:36:22 ... consensus is "yes" 16:36:39 q+ 16:36:50 In other words at least from my head "Merging RDF graphs while easier then merging SQL statements, is still hard" 16:37:19 ivan: would like to understand where this leads us. 2 lines of discussion about named graphs, but where do they meet? 16:37:19 merging graphs is easy. deciding whether it's ok to merge them is hard :-) 16:37:27 AlexHall, yes that +1 16:37:51 we can leave the decision when to merge graphs to end users :) 16:37:58 ivan: quad discussion around Pat's proposal, very interesting, came from Pat's action regarding time 16:38:14 zwu2, current semantics say it's always easy and safe 16:38:42 ivan: also typing discussion, from sandro et al 16:38:49 sandro: typing consideration was one of several proposed solutions 16:39:02 gavinc, I thought current semantics apply to graphs (of triples), not quads 16:39:46 sandro: has been concentrating on N3-style solution and [other]; Pat seems to be proposing a 6th solution 16:40:07 Guus: these discussions are different, but don't seem incompatible 16:40:26 q+ 16:40:26 Guus: typing the graph container is something that couldn't (and shouldn't) show up in semantics doc 16:41:07 Guus: one mechanism *may* be sufficient for use community 16:42:50 ivan: partially disagreeing with Sandro's "6th solution" characterization of Pat's message. concerned about new mechanism coming into picture several months into work... 16:43:49 sandro: named graphs has been a "lump in the carpet" since the early 90s. time dependence is also a big issue, which has now been raised with ties to named graphs. 16:44:21 ivan: where is line between scope of this WG and "future efforts"? 16:44:23 q+ to play Devil's advocate 16:44:38 ack ivan 16:44:38 ack ivan 16:44:44 ack davidwood 16:44:44 davidwood, you wanted to play Devil's advocate 16:44:54 sandro: may be time to review "other work" in Charter 16:45:14 davidwood: 2 chartered items that relate: named graphs and fixing semantics 16:45:52 davidwood: we seem to have made progress with these discussions. I'm inclined to let it continue a couple weeks longer. 16:46:54 Guus: further discussion requires Pat's presence... 16:48:05 sandro: maybe consensus feedback to Pat, "what's important about context?" may be helpful for progress 16:48:23 davidwood: objections have been made to "context" as an overused word... 16:49:20 davidwood: concern is that leaving separation of contextual/time-varying from non-contextual/time-invariant to publisher, is likely to be wrong 16:50:04 sandro: agreement... best practice may be to provide a "period of applicability" for a given data set, e.g., dc:temporal metadata 16:51:11 ivan: we may want to put aside the whole issue of time, for the time being... 16:52:00 ivan: in practice, in practical usage, if I have a way to properly describe "named graphs," I can describe a bunch of triples and have a vocab to describe the time-related things... that may be enough, even if not terribly precise 16:52:41 ivan: understood action on Pat to be "come up with vocabulary that would be enough for gathering sufficient time info for practical purposes" 16:53:10 sandro: practical question is whether we can satisfy multi-graph uses without addressing time question 16:53:32 ivan: ... without having a time ontology 16:54:33 ... so first pursue use cases that don't require time dependence solution 16:56:37 Hmm - create islands where current pure semantics are true. Multiverse! 16:56:52 (...scribe joins discussion and fails to summarize...) 16:58:24 AndyS: perhaps we can do both: frame RDF semantics so there are "islands" of graphs where current "pure" semantics are true, free merging should work; then merging "islands" requires contextual info about those islands 16:58:43 sounds like a research project to me :-) 17:00:16 q+ 17:00:32 sandro: "islands" seem to be larger graphs, which are collections of subgraphs 17:00:47 http://www.w3.org/2011/rdf-wg/wiki/TF-Graphs/RDF-Datasets-Proposal 17:00:58 AZ: makes me think of the propsal about semantics of data sets 17:01:52 +Sandro.a 17:02:01 Zakim, dial ericP-mobile 17:02:03 ok, MacTed; the call is being made 17:02:06 +EricP 17:02:09 -Sandro 17:02:34 AZ: (summarizes proposal, draws connections between it and "islands" terminology) 17:03:14 AndyS: asks for data set semantics to be mapped to a current use case 17:03:36 +1 Andy: AZ, please illustrate your proposal by showing how to address (some of) the use cases with it. 17:04:08 tsunami merges all graphs 17:04:25 s/tsunami merges all graphs/.../ 17:05:05 AZ: these semantics do not directly address all use cases, but at least gives framework by which to do so... 17:05:43 action on AZ to illustrate how http://www.w3.org/2011/rdf-wg/wiki/TF-Graphs/RDF-Datasets-Proposal maps to current use cases 17:05:43 Sorry, couldn't find user - on 17:06:07 leave out the 'on' 17:06:36 action on zimmerma to illustrate how http://www.w3.org/2011/rdf-wg/wiki/TF-Graphs/RDF-Datasets-Proposal maps to current use cases 17:06:36 Sorry, couldn't find user - on 17:06:41 Action AndyS: Write email about the "islands" idea 17:06:41 Created ACTION-148 - Write email about the "islands" idea [on Andy Seaborne - due 2012-02-29]. 17:06:41 azimmerm 17:06:49 action zimmerma to illustrate how http://www.w3.org/2011/rdf-wg/wiki/TF-Graphs/RDF-Datasets-Proposal maps to current use cases 17:06:49 Sorry, couldn't find user - zimmerma 17:06:58 action azimmerm to illustrate how http://www.w3.org/2011/rdf-wg/wiki/TF-Graphs/RDF-Datasets-Proposal maps to current use cases 17:06:58 Created ACTION-149 - Illustrate how http://www.w3.org/2011/rdf-wg/wiki/TF-Graphs/RDF-Datasets-Proposal maps to current use cases [on Antoine Zimmermann - due 2012-02-29]. 17:07:04 Azimmerm 17:09:07 Guus: seems we've made full progress there... ericP, can discuss action-147? 17:09:52 -AndyS 17:10:14 ericP: summarizes/restates content of email to list... linked form http://www.w3.org/2011/rdf-wg/track/actions/147 17:10:18 s/form/from/ 17:12:00 -zwu2 17:12:01 ... change to be made, further discussion for next week ... 17:12:22 -Sandro 17:12:23 -AlexHall 17:12:24 -Ivan 17:12:26 -swh 17:12:27 -EricP 17:12:27 -Arnaud 17:12:29 -Guus 17:12:31 AlexHall has left #rdf-wg 17:12:34 -FabGandon 17:12:35 -AZ 17:12:54 -cgreer 17:13:04 http://www.w3.org/2009/CommonScribe/manual.html 17:13:13 http://www.w3.org/2009/CommonScribe/panel/ 17:14:05 Oooh, better URL https://www.w3.org/2009/CommonScribe/panel/?group=rdf-wg&go=Use+This+Group 17:15:32 https://www.w3.org/2011/rdf-wg/wiki/index.php?title=Chatlog_2012-02-22&redirect=no 17:16:07 yep, then the "Preview Nicely formated version" 17:16:08 http://www.w3.org/2011/rdf-wg/meeting/2012-02-22 17:16:09 and fix 17:16:26 Scribe page on wiki is now better: http://www.w3.org/2011/rdf-wg/wiki/Scribes 17:16:31 RRSAgent, make logs public 17:16:53 trackbot, end meeting 17:16:53 Zakim, list attendees 17:16:53 As of this point the attendees have been Guus, Sandro, gavinc, Arnaud, +1.949.567.aaaa, +1.707.318.aabb, AndyS, MacTed, cgreer, David_Wood, FabGandon, swh, AlexHall, AZ, Ivan, 17:16:57 ... zwu2, EricP 17:17:01 RRSAgent, please draft minutes 17:17:01 I have made the request to generate http://www.w3.org/2012/02/22-rdf-wg-minutes.html trackbot 17:17:02 RRSAgent, bye 17:17:02 I see 1 open action item saved in http://www.w3.org/2012/02/22-rdf-wg-actions.rdf : 17:17:02 ACTION: AndyS to Write email about the "islands" idea [1] 17:17:02 recorded in http://www.w3.org/2012/02/22-rdf-wg-irc#T17-06-41