14:55:42 RRSAgent has joined #rdf-wg 14:55:42 logging to http://www.w3.org/2013/07/10-rdf-wg-irc 14:55:44 RRSAgent, make logs world 14:55:44 Zakim has joined #rdf-wg 14:55:46 Zakim, this will be 73394 14:55:46 ok, trackbot; I see SW_RDFWG()11:00AM scheduled to start in 5 minutes 14:55:47 Meeting: RDF Working Group Teleconference 14:55:47 Date: 10 July 2013 14:55:52 SW_RDFWG()11:00AM has now started 14:55:53 +EricP 14:58:28 +??P0 14:58:29 pfps has joined #rdf-wg 14:58:31 -EricP 14:58:32 +EricP 14:58:38 zakim, I am ??P0 14:58:38 +gkellogg; got it 14:59:13 +[GVoice] 14:59:19 http://w3.org/brief/MzM4 14:59:25 Arnaud1 has joined #rdf-wg 14:59:46 +davidwood 15:00:02 Zakim, who is barking? 15:00:02 I don't understand your question, davidwood. 15:00:13 Zakim, who is here? 15:00:13 On the phone I see EricP, gkellogg, [GVoice], davidwood 15:00:15 On IRC I see Arnaud1, pfps, Zakim, RRSAgent, gkellogg, TallTed, trackbot, davidwood, manu, yvesr, mischat, ericP, sandro 15:01:04 AZ has joined #rdf-wg 15:01:07 +OpenLink_Software 15:01:12 Zakim, OpenLink_Software is temporarily me 15:01:12 +TallTed; got it 15:01:14 Zakim, mute me 15:01:15 TallTed should now be muted 15:01:23 TallTed has changed the topic to: RDF-WG -- http://www.w3.org/2011/rdf-wg/ -- agenda http://www.w3.org/2011/rdf-wg/wiki/Meetings:Telecon2013.07.10 15:02:12 is anyone successfully calling Zakim via SIP? 15:02:27 it isn't working for me 15:02:28 + +081165aaaa 15:02:28 markus has joined #rdf-wg 15:02:38 Zakim, aaaa is me 15:02:38 +AZ; got it 15:02:59 gavinc has joined #rdf-wg 15:03:00 +Sandro 15:03:21 scribenick: ericP 15:03:48 + +1.707.861.aabb 15:03:49 Zakim, who is here? 15:03:50 On the phone I see EricP, gkellogg, [GVoice], davidwood, TallTed (muted), AZ, Sandro, +1.707.861.aabb 15:03:50 On IRC I see gavinc, markus, AZ, Arnaud, pfps, Zakim, RRSAgent, gkellogg, TallTed, trackbot, davidwood, manu, yvesr, mischat, ericP, sandro 15:03:56 aabb is me 15:04:04 Zakim, aabb is me 15:04:04 +gavinc; got it 15:04:47 +[IPcaller] 15:04:57 PROPOSED to accept the minutes of the 3 July telecon: 15:04:57 15:04:57 https://www.w3.org/2013/meeting/rdf-wg/2013-07-03 15:05:04 Zakim, IPCaller is me 15:05:04 +Arnaud; got it 15:05:16 +??P15 15:05:19 RESOLVED to accept the minutes of the 3 July telecon: https://www.w3.org/2013/meeting/rdf-wg/2013-07-03 15:05:19 zakim, ??P15 is me 15:05:19 +markus; got it 15:05:28 PROPOSED: accept https://www.w3.org/2013/meeting/rdf-wg/2013-07-03 as a record of the last meeting 15:05:30 Review of action items 15:05:30 http://www.w3.org/2011/rdf-wg/track/actions/pendingreview 15:05:30 http://www.w3.org/2011/rdf-wg/track/actions/open 15:06:21 ACTION-278? 15:06:21 ACTION-278 -- Eric Prud'hommeaux to create new grammar for TriG that includes optional graph keywords and make {} optional around the default graph -- due 2013-07-10 -- OPEN 15:06:21 http://www.w3.org/2011/rdf-wg/track/actions/278 15:06:25 ACTION-279? 15:06:25 ACTION-279 -- Sandro Hawke to propose text for TriG feature at risk for both GRAPH keywords and {} being optional around the default graph -- due 2013-07-10 -- OPEN 15:06:25 http://www.w3.org/2011/rdf-wg/track/actions/279 15:06:35 zwu2 has joined #rdf-wg 15:06:44 close ACTION-278 15:06:44 Closed ACTION-278 Create new grammar for TriG that includes optional graph keywords and make {} optional around the default graph. 15:06:50 close ACTION-279 15:06:50 Closed ACTION-279 Propose text for TriG feature at risk for both GRAPH keywords and {} being optional around the default graph. 15:07:25 Reminder: The next telecon will be Wednesday, 24 July 15:07:30 (biweekly) 15:07:30 davidwood: staring bio-weekly schedule so next telecon Wed 24 July 15:07:39 +AZ.a 15:09:17 pchampin has joined #rdf-wg 15:09:28 where would this paragraph go? 15:09:28 topic: describe relationship between RDF Concepts and RDF Semantics in Concepts 15:09:51 davidwood: do you think it should be verbose? 15:10:03 pfps: not sure where it should go 15:10:12 pfps: previous version didn't include this 15:10:26 ... propose: do nothing 15:10:36 I'm of the opinion that the right thing is to do nothing. 15:10:38 davidwood: we mention semantics in the intro (as a link) 15:10:49 ... then under entailment and consistency 15:11:18 ... markus noted that 1.7 seems out of place. i agree 15:11:33 ... could be fixed if we clarified the relationship between the two documents 15:11:56 Souri has joined #rdf-wg 15:12:02 ... markus, would clarifying the relationshop between the two docs improve 1.7? 15:12:13 markus: i'd like to move this all to semantics 15:12:26 ... it's not relevent to a newcomer and not complete enough 15:12:43 davidwood, but it does include refs which introduces it to readers of concepts 15:13:01 markus: my goal is to simplify Concepts to not scare off new readers 15:13:20 davidwood: first read should be the primer 15:13:44 markus: agreed, but most specs will ref Concepts so folks will read that before reading the Primer 15:13:58 davidwood: pfps, how do you feel about moving 1.7 to Semantics? 15:14:09 Zakim, unmute me 15:14:09 TallTed should no longer be muted 15:14:11 pfps: something has to reference Semantics 15:14:11 you could put a note in the intro recommending to read the primer first 15:14:45 just make sure the primer doesn't send people back to concepts from the get-go :) 15:15:03 q+ to say that I agree with markus that concepts readers should be able to read a data model without the hard stuff 15:15:30 davidwood: [at al,] yes, we should point to the primer but we don't have one 15:15:51 TallTed: if there's an intended order of reading, that should be indicated at the beginning 15:16:00 q? 15:16:04 ack ericP 15:16:04 ericP, you wanted to say that I agree with markus that concepts readers should be able to read a data model without the hard stuff 15:16:55 davidwood: in the beginning of Concepts, we reference these other documents 15:17:41 Zakim, mute me 15:17:41 TallTed should now be muted 15:17:49 ... if we move 1.7 to semantics and define entailment and consistency there, Concepts will have few refs to Semantics 15:18:10 Zakim, who's speaking? 15:18:15 ... in that section, we just define some terms. 15:18:22 AZ, listening for 10 seconds I heard sound from the following: [GVoice] (79%), davidwood (68%) 15:18:32 ... should a readers of Concepts understand those terms 15:19:39 pfps: i'm uncomfortable with moving 1.7 from Concepts and into Semantics 15:20:20 markus: are these terms used again in Concepts? 15:20:44 ... i see one later ref to "entailment" in an example 15:20:56 "Two RDF graphs A and B are equivalent if they make the same claim about the world. A is equivalent to B if and only if A entails B and B entails A." That one's important 15:20:59 ... you could argue that it's basic knowledge for RDF, but... 15:22:36 Zakim, who's here? 15:22:36 On the phone I see EricP, gkellogg, [GVoice], davidwood, TallTed (muted), AZ, Sandro, gavinc, Arnaud, markus, AZ.a 15:22:38 On IRC I see Souri, pchampin, zwu2, gavinc, markus, AZ, Arnaud, pfps, Zakim, RRSAgent, gkellogg, TallTed, trackbot, davidwood, manu, yvesr, mischat, ericP, sandro 15:23:41 https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html#entailment 15:25:55 +Souri 15:26:13 http://json-ld.org/spec/latest/json-ld/#data-model 15:26:19 http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jun/0126.html 15:26:21 If we are making changes to 1.7, I would make some non-controversial editorial changes. I would also remove the stuff on union and merge (which might be somewhat more controversial). I'll send out a message on this. 15:26:53 Consensus on everything except my worries about JSON numbers. 15:27:17 http://json-ld.org/spec/latest/json-ld/#relationship-to-rdf 15:27:29 markus: we discussed an unambiguos mapping from JSON datatypes to RDF datatypes 15:27:44 ... that addressed pfps's concearns 15:27:58 ... i just updated the spec 10 mins ago. everything should be in place 15:28:59 pfps: i'd have been content yesterday 15:29:08 ... this is all painful 15:29:40 ... JSON is a loose spec which does thousands of things with numbers 15:29:46 ... e.g. 32 bit integers 15:29:56 Guus_ has joined #rdf-wg 15:30:15 sandro: here we're improving JSON by using RDF's [really XML Schema's] precise definitions 15:30:49 pfps: implementations on the ground are likely to use "JSON number" 15:31:06 sandro: JSON-LD steers you away from "number" if you care about round-tripping 15:31:50 pfps: JSON has a notion of a fraction number, e.g. 12.3 has a fractional part of "3" 15:32:56 markus: 1.1E1 is the canonical form of "11"^^xsd:double 15:33:04 s/markus/pfps/ 15:33:08 ... that ".1" is the fractional part 15:34:08 ... if that part's nailed down, i think JSON-LD provides a consistent and coherent view of the world 15:34:26 ... no idea what the JSON reception would be 15:34:59 http://tools.ietf.org/html/draft-staykov-hu-json-canonical-form-00#section-2.1.1 btw 15:36:27 Peter's quote: ... "without, of course, getting bogged down on things like how many Unicode surrogate characters can dance on the head of a JSON string" :-) 15:36:46 pfps: we talk about unicode codepoints but JSON talks about unicode characters 15:38:16 davidwood: what will the JSON-LD group do with this? 15:38:29 markus: we spend a long time on round-tripping 15:39:00 ... i think the spec is clear anough about it. some corner cases like "1.0" becomes an integer 15:39:01 the point is that the syntax for JSON numbers uses frac and fraction part for the .1 in 1.1E1 so fractional part needs to be distinguished from that 15:39:23 ... but the RDF-to-JSON defaults to using the string representation so you default to clean round-tripping 15:39:49 davidwood: so don't expect many changes between now and REC 15:40:23 well, I would still be happy to say something about RDF/JSON 15:40:33 Zakim, who is here? 15:40:33 On the phone I see EricP, gkellogg, pfps, davidwood, TallTed (muted), AZ, Sandro, gavinc, Arnaud, markus, AZ.a, Souri 15:40:35 On IRC I see Guus_, Souri, zwu2, gavinc, markus, AZ, Arnaud, pfps, Zakim, RRSAgent, gkellogg, TallTed, trackbot, davidwood, manu, yvesr, mischat, ericP, sandro 15:40:55 +q to say something about RDF/JSON 15:41:03 ack Arnaud 15:41:03 Arnaud, you wanted to say something about RDF/JSON 15:41:08 q? 15:41:11 By the way, when are Semantics and Concepts going to LC publication? 15:41:13 Topic: RDF/JSON 15:41:56 Arnaud: after reading pierre antoine and andy's comments, i don't think they're serious obstacles 15:42:12 NB: +1 15:42:15 ... before editing the spec, i want to know whether it's likely to proceed 15:43:13 davidwood: gregg proposed an alternative format to JSON-LD, which i don't think this group has time 15:43:30 Arnaud: i discussed this with Gregg at SemTech 15:43:49 ... he said that they have a rep which is essentially similar to RDf/JSON 15:44:15 davidwood: putting RDF/JSON out as a note makes it easy for folks to translate 15:44:34 ... someone can later make that REC-track 15:45:15 gkellogg: we'd need a internal step which creates an ID map when flattening 15:45:33 markus: you can have the same shape, but you need a top-level node 15:45:44 PROPOSED: The WG will publish RDF/JSON as a Note 15:45:56 +1 15:45:57 +1 15:46:28 PROPOSED: The WG will pursue publication of RDF/JSON as a Note 15:46:35 +1 15:46:36 -0.5 15:46:36 +1 15:46:36 +1 15:46:37 +1 15:46:37 +1 15:46:38 +1 15:46:39 +0.5 15:46:43 +1 15:46:45 +0 15:46:46 (to be clear -- this is NOT a decision to publish) 15:46:50 +1 15:47:04 +0.5 15:47:18 markus: i find it confusing that the same WG publishes two competing JSON formats 15:47:21 Hey! I'm WRITING 4 competing formats :P 15:47:38 (agreed, there's some confusion with JSON-LD -- but Arnaud has promised the document will be clear about it) 15:47:42 davidwood: yeah, but in the first year, we had lots of discussion 15:47:51 I already added this to the RDF/JSON draft: "On the other hand, the RDF Working Group decided to put JSON-LD on the Recommendation track (see resolution of May 30, 2012). If you have no specific reason to use this document instead of JSON-LD, you are therefore encouraged to use JSON-LD." 15:48:07 ... the use cases for these two serializations were completely separate. (that's why i'm not concearned) 15:48:17 RESOLVED: The WG will pursue publication of RDF/JSON as a Note 15:48:29 I hope this addresses some of Markus's concern which I fully understand 15:49:14 swh has joined #rdf-wg 15:49:25 -pfps 15:50:24 topic: NTriples and NQuads 15:50:50 davidwood: propose to move from persuing a Note to persuing a Rec 15:51:13 PROPOSED: The WG will pursue N-Triples/N-Quads as a Rec instead of a Note 15:51:14 sandro: i understand this doesn't bind us, just advice to editor 15:51:18 +∞ 15:51:21 +1 15:51:22 +1 15:51:28 +0.5 15:51:28 +1 15:51:43 +[GVoice] 15:51:52 zakim, gvoice is me 15:51:52 +pfps; got it 15:52:08 +0.5 15:52:10 eric: Does this raise the bar on what an RDF Implementation is? 15:52:57 eric: Is there a presumption that every RECOMMENDED syntax is supported by every system? 15:53:10 Arnaud, quick question just out of curiosity: does RDF/JSON serialize all numbers as strings? 15:53:17 eric: Do we have too many syntaxes? 15:53:32 Gavin: Yes, but N-Triples and N-Quads aren't the ones 15:54:01 eric: Yes, but in 2004 N-Triples was specified, but they DIDNT tell the world to expose their data as N-Triples. 15:54:04 swh_ has joined #rdf-wg 15:54:45 davidwood: Eric, this is RESOLVED, and Eric please raise an issue about this 15:55:05 s/persuing/pursuing/ 15:55:07 +0 15:55:12 eric: you're saying we have another avenue for guidance about syntaxes, not just "Every Recommendation". 15:55:41 davidwood: Now we have all these different syntaxes, so we should make some statement, in Concepts, about what you should comply with. 15:55:58 davidwood: I'd say N-Triples and N-Quads and everything else is optional 15:56:00 ?!?!?!?! 15:56:06 -1 to that 15:56:26 eric; I'd say w3.org/TR is how you know which syntaxes to implement 15:56:46 davidwood: but practically we have so many 15:57:08 sandro: LDP says "you have to use Turtle" 15:57:43 ... you're saying that every government has to expose as NTriples to guarantee interop" 15:57:52 davidwood: i have to think about it 15:58:09 Simple, name an RDF implementation that DOESN'T implement N-Triples 15:58:48 N-TRIPLES is really popular 15:59:05 Oracle parses N-Triples and N-Quads 15:59:24 ... if we have a half dozen serialization formats, we can't call an impl that doesn't implement them all "non-compliant" 16:00:22 [discussion of proliferation of NTriples and NQuads] 16:01:40 the one advantage of having all these formats is that it should make it clear to anyone that RDF isn't RDF/XML :) 16:03:23 that's actually a significant advantage :-) 16:03:38 ISSUE: guidance to RDF users and developers about which syntaxes to parse and publish 16:03:38 Created ISSUE-138 - Guidance to RDF users and developers about which syntaxes to parse and publish; please complete additional details at . 16:04:09 btw OWL/XML is a REC and OWL implementations do *not* have to support it 16:04:23 scribe: sandro 16:04:42 topic: TriG 16:05:07 http://www.w3.org/2005/01/yacker/uploads/trigS_new?lang=perl 16:05:27 (except for the part where RDF/XML seems to be the only serialization that includes "RDF" [and not just "R"] in its name) 16:05:37 eric: I created a grammar that takes care of (1) blank nodes as graph identifiers, (2) allow the GRAPH keyword, (3) allow { } to be optional around default graph 16:05:53 eric: I made an LALR(1) grammar for this 16:06:19 blank nodes as graph identifiers are already in the Grammar in the the current ED 16:06:22 eric: interesting grammatical points. 16:06:23 Also LL(1) 16:06:47 eric: Noticed one could do: [ :a :b ] { .... } 16:07:12 Also, possibly (1 2) { … } 16:07:21 eric: Andy pushed back, saying this syntac might be used for something else, and exceeds sparql 16:07:39 gavin: Aligning with SPARQL, and then going right past it..... 16:09:34 ASK { {

} GRAPH { ... } } 16:09:35 eric: Resolved that it's fine to make GRAPH optional and make { ... } optional 16:09:51 ASK { {

{ } } GRAPH { ... } } 16:10:18 sandro: ewww! 16:10:35 normal use: ASK {

GRAPH { ... } } 16:10:48 sandro: and that's what we'd like in TriG 16:11:43 david: (missed) 16:12:30 eric: { {

{ } } GRAPH { ... } } turns into {

. GRAPH { ... } } 16:13:08 eric: Resolved that it's fine to make GRAPH optional and make { ... } optional 16:14:31 eric: is there a mechanism to survey....? 16:15:21 eric: eg wiki page of implementations 16:15:27 sandro: Sure, let's link to the implementation risk in the At Risk text. 16:15:28 -Arnaud 16:16:12 gavin: I think we already resolved to add these, last meeting. I was going to normalize against existing trig grammar and include it. 16:16:25 eric: also, optional trailing dot inside curlies 16:16:42 eric: I borrow from SPARQL not TURTLE. 16:16:57 +1 16:17:13 david: We've gotten through our agenda! 16:18:52 sandro: I don't recall us actually resolving 137 16:19:03 http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0138.html 16:19:41 PROPOSED: Resolve ISSUE-137 using at risk text proposed by sandro http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0138.html and a grammar based on ericP's changes http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0099.html 16:19:52 +1 16:19:59 +1 16:20:00 +0.5 16:20:01 +1 16:20:02 +1 16:20:04 +1 16:20:24 +1 16:20:40 +1 16:20:51 RESOLVED: Resolve ISSUE-137 using at risk text proposed by sandro http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0138.html and a grammar based on ericP's changes http://lists.w3.org/Archives/Public/public-rdf-wg/2013Jul/0099.html 16:21:01 davidwood: AOB? 16:21:04 +1 16:21:24 gavin: We'll also be adding Andy's test cases to the TriG test suite. 16:22:48 bye 16:22:53 -AZ.a 16:23:03 ADJOURN 16:23:04 -AZ 16:23:09 -pfps 16:23:25 -Souri 16:23:28 bye 16:23:31 -markus 16:23:48 https://dvcs.w3.org/hg/rdf/file/0f2466565bc8/trig/tests2/trig-kw-graph-08.trig 16:23:54 https://dvcs.w3.org/hg/rdf/file/0f2466565bc8/trig/tests2 16:27:13 -EricP 16:32:20 https://dvcs.w3.org/hg/rdf/file/0f2466565bc8/trig/tests2/trig-kw-graph-01.trig 16:32:34 https://dvcs.w3.org/hg/rdf/log/0f2466565bc8/trig/tests2/trig-kw-graph-08.trig 16:34:23 -gkellogg 16:34:27 -Sandro 16:34:28 -gavinc 16:34:29 -davidwood 16:34:29 -TallTed 16:34:29 SW_RDFWG()11:00AM has ended 16:34:29 Attendees were EricP, gkellogg, davidwood, TallTed, +081165aaaa, AZ, Sandro, +1.707.861.aabb, gavinc, Arnaud, markus, Souri, pfps 16:34:35 RCS forever! 16:37:40 davidwood: can you check your ~/.hgrc ? 17:26:13 Arnaud1 has joined #rdf-wg 17:56:45 Zakim has left #rdf-wg 18:35:04 davidwood has joined #rdf-wg