14:32:06 RRSAgent has joined #rdf-wg 14:32:06 logging to http://www.w3.org/2012/06/20-rdf-wg-irc 14:32:08 RRSAgent, make logs world 14:32:08 Zakim has joined #rdf-wg 14:32:10 Zakim, this will be 73394 14:32:10 ok, trackbot; I see SW_RDFWG()11:00AM scheduled to start in 28 minutes 14:32:11 Meeting: RDF Working Group Teleconference 14:32:11 Date: 20 June 2012 14:52:03 SW_RDFWG()11:00AM has now started 14:52:10 +??P9 14:52:42 Zakim, ??P9 is me 14:52:42 +yvesr; got it 14:55:41 cgreer has joined #rdf-wg 14:58:14 +mhausenblas 14:58:25 zakim, mhausenblas is temporarily me 14:58:25 +cygri; got it 14:58:27 + +1.707.318.aaaa 14:58:35 zakim, aaaa is me 14:58:35 +cgreer; got it 14:58:45 pchampin has joined #rdf-wg 14:59:04 SteveH__ has joined #rdf-wg 14:59:32 +??P13 14:59:36 zakim, ??P13 is me 14:59:36 +AndyS; got it 14:59:38 trackbot-ng, start telecon 14:59:40 RRSAgent, make logs world 14:59:42 Zakim, this will be 73394 14:59:42 ok, trackbot; I see SW_RDFWG()11:00AM scheduled to start in 1 minute 14:59:43 Meeting: RDF Working Group Teleconference 14:59:43 Date: 20 June 2012 14:59:55 scribenick: cgreer 15:00:02 ScottB has joined #rdf-wg 15:00:15 chair: davidwood 15:00:24 Arnaud has joined #rdf-wg 15:00:32 zakim, what is the code? 15:00:32 the conference code is 73394 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), pchampin 15:01:14 zakim, who is here? 15:01:14 I notice SW_RDFWG()11:00AM has restarted 15:01:15 On the phone I see yvesr, cygri, cgreer, AndyS, OpenLink_Software, ??P18 15:01:15 On IRC I see Arnaud, ScottB, SteveH, pchampin, cgreer, Zakim, RRSAgent, ivan, danbri, MacTed, AndyS, LeeF, Guus, cygri, gavinc, manu1, davidwood, manu, yvesr, NickH, gkellogg, 15:01:16 ... sandro, trackbot, ericP 15:01:24 Zakim, ??P18 is me 15:01:26 +??P4 15:01:28 zakim, dial ivan-voip 15:01:29 +SteveH; got it 15:01:32 ok, ivan; the call is being made 15:01:35 +Ivan 15:01:39 + +1.408.996.aabb 15:01:46 +Tony 15:01:50 zakim, ??P4 is me 15:01:51 zakim, aab is me 15:01:58 +pchampin; got it 15:01:59 AZ has joined #rdf-wg 15:02:02 sorry, Arnaud, I do not recognize a party named 'aab' 15:02:03 Zakim, Tony is temporarily me 15:02:03 Zakim, OpenLink_Software is temporarily me 15:02:05 Zakim, mute me 15:02:11 +??P27 15:02:15 +ScottB; got it 15:02:15 zakim, ??P27 is me 15:02:16 +MacTed; got it 15:02:18 MacTed should now be muted 15:02:20 zakim, ??aabb is me 15:02:28 +gkellogg; got it 15:02:36 sorry, Arnaud, I do not recognize a party named '??aabb' 15:02:56 +sandro 15:02:59 zakim, ??bb is me 15:03:12 sorry, Arnaud, I do not recognize a party named '??bb' 15:03:16 + +1.540.898.aacc 15:03:19 zwu2 has joined #rdf-wg 15:03:24 Zakim, aacc is me 15:03:25 +davidwood; got it 15:03:26 zakim, code? 15:03:27 +EricP 15:03:30 the conference code is 73394 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), zwu2 15:03:40 +??P36 15:03:58 scribenick: cgreer 15:04:01 Chair: David Wood 15:04:01 zakim, aabb is me 15:04:01 zakim, ??P36 is me 15:04:03 +Arnaud; got it 15:04:05 +AZ; got it 15:04:26 Topic: Admin 15:04:29 topic: Admin 15:04:31 + +1.443.212.aadd 15:04:35 + +1.650.265.aaee 15:04:35 PROPOSED to accept the minutes of the 13 Jun telecon: 15:04:35 http://www.w3.org/2011/rdf-wg/meeting/2012-06-13 15:04:41 +??P37 15:04:45 +1 15:04:49 zakim, I am ??P37 15:04:49 +manu1; got it 15:04:54 zakim, +1.650.265.aaee is me 15:04:54 +zwu2; got it 15:04:56 Topic: Action Items 15:04:57 RESOLVED accepted minutes 15:04:59 + +1.707.861.aaff 15:05:04 zakim, mute me 15:05:04 zwu2 should now be muted 15:05:05 Review of action items 15:05:05 http://www.w3.org/2011/rdf-wg/track/actions/pendingreview 15:05:05 http://www.w3.org/2011/rdf-wg/track/actions/open 15:05:06 AlexHall has joined #rdf-wg 15:05:12 Zakim, aaff is me 15:05:12 +gavinc; got it 15:05:23 davidwood: look at open action items 15:05:43 davidwood: eric youve forgotten about frbr 15:05:59 ericp: frbr didnt have appropriate use cases 15:06:09 davidwood: please end email about that 15:06:25 s/end/send/ 15:06:54 davidwood: guus is going to work on rdf spaces document and identify controversy 15:07:17 davidwood: he'll split it into rdf concepts and rdf semantics. It will hopefully be ready by next wednesday 15:07:39 Reminder: Summer schedule for telecons: 27 Jun, 11 July, 25 July, 8 August, 22 August, 5 September. 15:07:53 Tpoic: Turtle Last Call 15:07:55 davidwood: we will have meeting next week. The next will be 11 July. Summer schedule, plan accordingly. 15:07:56 regrets for next week, will be on a trip, and then on vacations in July... 15:08:03 Topic: Turtle LC 15:08:04 s/Tpoic/Topic/ 15:08:15 Regrets for next week 15:08:40 ??: There's still more discussion to have about the grammar, issues around what grammar will communicate decisions best. 15:08:51 s/??/ericP 15:08:59 zakim, mute me 15:08:59 Ivan should now be muted 15:09:30 + +1.617.553.aagg 15:09:31 ericP: the BNF drops parans where it needs them. One other issue is text about tokens. 15:09:39 q+ 15:09:39 davidwood: how much left? 15:09:45 ericp: done by friday. 15:10:11 gcarothers: no comments. 15:10:22 s/gcarothers/gavinc 15:10:40 davidwood: Turtle will be better for this work 15:11:05 gkellogg: Have been working with L17, still an open issue: predicate-object list. 15:11:24 ericp: I mocked up an LL grammar. Greg thinks it's a tool issue. 15:11:25 s/L17/LL(1) 15:11:36 s/L17/LL1()/ 15:11:55 ericp: I believe this should highlight behavior that Greg's tool should be exhibiting. 15:11:55 predicateObjectList ::= verb objectList (';' verb objectList)* ';'? is ambiguos - I proposed a better way to write it. 15:12:26 gavinc: I don't think this grammar is the only grammar that can parse turtle. If it turns out to be not LL1 that's not a bug. 15:12:39 gavinc: There are other grammars that can parse Turtle documents. 15:12:45 +Souri 15:12:59 davidwood: There's more than one way. Do we know for certain that there is really an LL1 grammar? 15:13:01 Souri has joined #rdf-wg 15:13:08 gavinc: Yes, it's just not in the specification. 15:13:36 gkellogg: There's an older version, with caveat that it allows multiple semicolons... 15:13:54 gkellogg: I'm successful with a production that allows infinite semicolons. 15:14:05 -> http://codepad.org/9TlTfIfd an LL(1) of the form A (B C D)* B? -- (a single-letter representation of [7]) 15:14:30 gkellogg: If it's not LL1 grammar, and the group intends to have one, we need to address that. 15:14:47 gkellogg: Every other grammar I've used have been parsed with 'this type of parser' 15:14:56 davidwood: no matter what we come up with, there will be other ways to do it. 15:15:16 gkellogg: It this grammar is NOT LL1, then we need to see what the intention of the group is. 15:15:27 how would you prove that the grammar we publish, and some hypothetical LL(1) grammar were the same? 15:15:53 sandro: Some people want LALR, some people want LL1. It doesn't make sense to provide both. It would be a bad idea to provide both. 15:16:04 q+ to address LL-ness vs. LALR-ness 15:16:05 q+ 15:16:10 ??: Is there some preference for LL1? 15:16:11 q 15:16:18 ack gkellogg 15:16:19 s/??/sandro/ 15:16:22 ack ericp 15:16:22 ericP, you wanted to address LL-ness vs. LALR-ness 15:16:56 ericp: Previous versions of SPARQL (neither LL1 nor LALR), but you can turn it into one of these grammars. 15:17:45 ericp: Has checked with peers about state table. Is the tool generating the state table correctly? I think not. 15:18:12 ack AndyS 15:18:23 ericp: The difference between LL1 and LALR handling was * and + 15:18:42 AndyS: Whether it's *+ not the issue. There's an ambiguity about semicolon. 15:19:05 AndyS: Most LL1 also have a pragmatic rule -- longer match over shorter match. 15:19:06 -zwu2 15:19:16 s/LL1/LALR/ 15:19:18 AndyS: I'll take action to make a rule. 15:19:20 +1 15:19:31 +1 15:19:48 [7] predicateObjectList ::= verb objectList (';' verb objectList)* ';'? 15:19:51 The rule in question 15:20:00 ACTION AndyS Draft a rule for predicateObjectList 15:20:00 Created ACTION-175 - Draft a rule for predicateObjectList [on Andy Seaborne - due 2012-06-27]. 15:20:06 + +1.603.438.aahh 15:20:12 my alternate: [7] predicateObjectList ::= verb objectList ( ";" ( verb objectList)? )* 15:20:24 zakim, +1.603.438.aahh is me 15:20:24 +zwu2; got it 15:20:26 q? 15:20:42 gavinc: Richard, could you talk about your feedback after call? 15:21:01 davidwood: Friday still reasonable? 15:21:09 gavinc: yes... 15:21:10 gkellog - yes - that is what SPARQL has an accepts many trailing ";" which seems (1) no big deal and (2) better for SPARQL/Turtle compatibility. 15:21:59 erikp: No more convenient expression of this rule. A reformulation will not make it easier for LALR parser. 15:22:26 AndyS: The reason the rule is a problem -- when you have verb-object list there are two branches for ';' 15:22:37 AndyS: Either new object list or end. 15:23:00 I found predicateObjectList ::= verb objectList ( ";" ( verb objectList)? )* to be perfectly fine 15:23:28 ericp: But you don't communicate with BNF. The ambiguity goes away with pasted grammar. 15:23:59 q? 15:24:05 AndyS: I use LL1 tool to generate SPARQL grammar. I can see why bison would accept it. 15:24:43 ericp: I've been working in an LL parser -- perl parse:rectisense 15:24:54 ??: This is not LL1 15:25:07 ericp: What if I try rewriting it. 15:25:14 q+ 15:25:36 ack ivan 15:26:15 This document WILL be done by the end of the week. 15:26:15 ivan: Will Eric be gone next week? What this means is that, if this doc is not done, we won't be done til August. 15:26:34 davidwood: publication freeze? 15:26:37 I withdraw my action. 15:27:19 davidwood: why did you withdraw your action? 15:27:46 ericp: If you want to supply the rule, I'm happy to have it. 15:27:55 s/parse:rectisense/Parse::RecDescent/ 15:28:29 AndyS: We've given our feedback. 15:28:57 gavinc: I don't mind restoring previous rule. It allows for multiple semicolons. Many existing parsers already allow this. SPARQL also doesn't have a limitation. 15:29:11 gavinc: I see no problem with infinite ';' following this production. 15:29:23 ericp: I don't much care either. 15:29:51 davidwood: If there's a clean way to do it, great. We won't hold up LC for this though. 15:30:21 ericp: There's a debate about -- whether to have rule that states that base and token are permitted as language tags. 15:30:43 q+ 15:30:51 gavinc: Other than riot, no existint turtle parser allows @base or @prefix as languate token. 15:31:30 gavinc: any parsers that tries to specify this needs to allow for language tags that are not permissible. 15:31:32 ack cygri 15:32:29 richard: For 1.1, the reference for language tag has changed. The current one defines two things. The generic grammar... 15:32:35 http://tools.ietf.org/html/bcp47#section-2.2.9 15:32:43 richard: and spells out in detail the admissible words and abbreviations. 15:33:16 richard: So since '@prefix' is not a language it's not a valid language tag. 15:34:11 ivan: We're spending time on very minute corner cases. 15:34:14 +1 to Ivan!!! 15:34:19 ivan: What's simpler to write down and move on? 15:34:24 +1 to ivan 15:35:00 ericp: So if we don't care, there's a simple way to write it. 15:35:02 -> http://www.w3.org/2005/01/yacker/uploads/turtleAwesome?lang=perl&markup=html#prod-turtleAwesome-RDFLiteral 15:35:31 ericp: If you want to make it explicit... negative is harder than positive. 15:35:46 ivan: Whatever is simpler. Let's take first case where we don't care. 15:35:50 or we could say that it's undefined behaviour 15:36:09 +1 not making any statement 15:36:09 ericp: Stating that it can happen is simpler. This may be simpler than no statement at all. 15:36:32 ivan: Whatever is simpler for editors. 15:36:32 +1 to SteveH 15:36:57 davidwood: If we define it we'd need a test case that could break parsers. 15:37:07 s/davidwood/Sandro/ 15:37:07 gavinc: And it would break compatibility with RDF 1.1 15:37:25 suggest that it is specifically disallowed 15:37:25 sandro: I don't see that. 15:37:39 davidwood: And if it's undefined behavior? 15:38:02 ericp: The production for language tag subsumes @base and @prefix. Parsers may or may not accept it. 15:38:04 is this accurate summary? 15:38:04 1. state it can happen. requires test cases... or statement that resulting behavior is undefined. 15:38:04 2. state it cannot happen. requires test cases. 15:38:04 3. say nothing. 15:38:46 ignore that, if problem is solved... 15:38:46 MacTed, it requires a comment, otherwise people will wonder 15:38:48 oh, by the way, +1 to ivan :-) 15:39:04 Don't test. 15:39:09 yeah, don't test 15:39:14 ericp: We're not saying whether it can happen. 'Don't Test' 15:39:15 +1 15:39:33 davidwood: LC on Turtle LC 15:40:03 ericp: This simplifies rules we have to adopt from SPARQL. Lexer is expected to parse longest terminal it can. 15:40:10 @base and @prefix are "reserved for future extensions" or "discouraged" in BCP47 15:40:11 q+ 15:41:13 ack ivan 15:41:15 BTW -- RIOT is recursive decent which is how it does @base as a language. 15:41:39 ivan: We seem to have resolution. Where are we for LC? 15:42:05 ericp: We're needing some text about @base and about terminals. 15:42:33 gavinc: Only remaining issue is resolving things with Richard. 15:42:41 ivan: Can we vote last call next week? 15:42:49 gavinc: We will have a document by Friday. 15:43:16 gavinc: Confident about agreement with Richard by end of day. 15:43:17 As far as I am concerned, publishing with the right language but not-ideal grammar for that language is "editorial" and can grammar change after LC IMHO. 15:43:37 AndyS - especially if we mark it as an issue in the document. 15:43:41 q? 15:43:46 Topic: JSON-LD 15:43:52 manu - good idea 15:43:52 Actually, the editors should /definitely/ mark the grammar as an issue and say that it could change. 15:43:54 AndyS++ 15:44:06 AndyS++ 15:44:18 q+ to provide an overview 15:44:29 q- 15:45:04 manu1: We have four reviews in. This is good coverage. 15:45:31 manu1: Most reviews have both major and minor issues, but nothing to hold up. 15:45:36 FPWD 15:46:01 -Arnaud 15:46:10 sorry, I have to drop off 15:46:25 manu1: What issues markers we want to put in, we must decide. Today, we need to hear from Eric about what issued need to be outlined. (and other reviewers) 15:47:03 manu1: We're talking grammar fixes, nothing major. Then the documents will move into the final CG stamp, handing to this group within next week. 15:48:11 manu1: With the IPR-- two issues. We need to hear what the issue markers are, and then we'll finalize and do IPR. 15:48:53 manu1: The w3c form for IPR document is not working. Once Greg has edited the spec, then the documents will be frozen and we'll get the IPR committments. 15:49:19 davidwood: how comfortable that nobody else will have issues? 15:49:42 manu1: Comfortable. Anyone who opened an issue has been accomodated. 15:50:14 q+ to say i have two proposals: 1. move 1.3 to SOTD 2. in §3.1 ¶2, add "Issue: the term "object" is used represent both JSON objects and terms in the object position of RDF triples." 15:50:16 manu1: All the people who have contributed more than a paragraph have committed to IPR preliminarily. 15:50:33 ack ericp 15:50:33 ericP, you wanted to say i have two proposals: 1. move 1.3 to SOTD 2. in §3.1 ¶2, add "Issue: the term "object" is used represent both JSON objects and terms in the object 15:50:36 ... position of RDF triples." 15:53:15 gkellogg: Use 'JSON Object' to avoid ambiguity of word 'object' 15:53:51 AndyS: Section 3.1 needs discussion by WG, but that's not a document issue. 15:54:13 -SteveH 15:54:45 We are tracking the issues here, btw: 15:54:47 https://github.com/json-ld/json-ld.org/issues/135 15:54:49 https://github.com/json-ld/json-ld.org/issues/136 15:54:51 https://github.com/json-ld/json-ld.org/issues/137 15:55:37 AZ: My issues can wait for version of document. The term 'property' is an issue for me, but there may have been other discussion. "Property" is not an "edge". 15:55:49 AZ: Property is the lable of the edge, not the edge itself. 15:55:54 +1 15:55:57 s/lable/label/ 15:56:25 cgreer, it's pchampin speaking 15:57:39 pchampin: We needed to position JSON-LD spec so as not to be explicitly linked to RDFa. 15:57:39 s/AZ/pchampin/ 15:58:02 q? 15:58:47 q+ 15:58:56 http://json-ld.org/spec/latest/json-ld-syntax/#rdf 15:59:08 davidwood: We do need to make the relationship between RDF and JSON-LD more clear. However, this doesn't need to affect your activities. 15:59:33 manu1: We did agree to put a section on RDF in the spec. 15:59:54 davidwood: We need something up front in the introduction. Even if it's a short paragraph with links. 16:00:04 q+ 16:00:05 manu1: We thought this would scare people away. 16:00:10 Zakim, unmute me 16:00:12 MacTed should no longer be muted 16:00:22 ack pchampin 16:00:29 davidwood: I'm sure we can manage a sentence or two that wouldn't be scary to web developers. 16:00:54 zakim, who is speaking? 16:01:00 sentence that talk about "compatibility" might work. 16:01:02 AndyS - both Semantic Web /and/ RDF scares people away (because they associate RDF with RDF/XML) 16:01:11 cgreer, listening for 10 seconds I heard sound from the following: LeeF (48%), pchampin (100%), MacTed (60%), gkellogg (9%), EricP (4%) 16:01:20 clarification: we're not discussing a prerequisite for FPWD, right? 16:01:22 q+ 16:01:25 come on, it is OWL Full that is scary 16:01:35 ack me 16:01:36 pchampin: We can figure out some non-scary way to mention RDF. 16:02:31 davidwood: There was similar discussion about Turtle, and Dave B. made objection, Turtle will be better for the argument. RDF WG will have to mention RDF somewhere beyond the appendix. 16:03:01 manu1: I'm concerned more about marketing of the spec. We want it adopted as quietly as possible 16:03:32 ack MacTed 16:04:09 MacTed: This is not a blocker for FPWD. Bait-and-switch doesn't do what we want. 16:04:32 davidwood: I said, just one or two sentences. 16:04:51 MacTed: But if it's not part of the FPWD process, we can not hold it up for this. 16:04:51 ack ivan 16:04:55 +1 to discuss the language later 16:05:09 Err.. it's going to say RDF in the STOD... yeah, what Ivan is saying :D 16:05:22 ivan: So the point is -- if you look at the document status. The RDF-WG will be right at the top of the document. 16:05:34 at the top of document it WILL say "This document was published by the RDF Working Group as an Editor's Draft. If you wish to make comments regarding this document, please send them to public-rdf-comments@w3.org (subscribe, archives). All feedback is welcome." 16:05:38 ehhh -- NO ONE EVER reads the SOTD. :-) 16:05:46 ivan: A warning to Manu that this will happen. 16:05:54 From the current Turtle ED: "This document was published by the RDF Working Group as an Editor's Draft. If you wish to make comments regarding this document, please send them to public-rdf-comments@w3.org (subscribe, archives). All feedback is welcome." 16:06:26 I do *not* think that the Abstract needs to state, as the Turtle ED does, with "The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web." 16:06:30 ivan: It's not completely hidden. If you want to add in the SOTD, that might be the best place to add RDF terminology. 16:06:50 manu1: Can we let this go for now? It should not affect FPWD. 16:06:59 davidwood: We can leave to editors. 16:07:04 the SOTD could downplay it even more, like: "This document was published by the W3C JSON LD Task Force, under the supervision of the RDF Working Group, " 16:07:26 or "with approval by the ... " 16:07:37 i propose we add "we got you, sucka" after B.1 16:07:49 lol @ericP 16:08:01 ISSUE: Mention RDF in the JSON-LD Syntax Introduction. 16:08:01 Created ISSUE-92 - Mention RDF in the JSON-LD Syntax Introduction. ; please complete additional details at http://www.w3.org/2011/rdf-wg/track/issues/92/edit . 16:08:23 "suckas" if we're feeling particularly cocky 16:08:24 If you talk about RDF Compatibility as one of the advantages of JSON-LD, I don't think it'll bug anyone. 16:08:47 manu1: We'll get these edits done and have document by Wednesday. 16:09:17 davidwood: We need to close the issue, but it doesn't have to be a big issue. 16:10:49 manu1: It's important for RDF community to understand how people are adopting RDF. There are fringe communities, anti-RDF, who come around. 16:11:04 hey, danbri, your anti RDF? ;) 16:11:15 no, not danbri! 16:11:28 /other/ people at Google :) 16:12:02 :) 16:12:04 What is Linked Data? http://www.youtube.com/watch?v=4x_xzT5eF5Q&feature=g-upl 16:12:10 q+ to ask if there are folks who have a way to evaluate these trade-offs 16:12:15 What is JSON-LD? http://www.youtube.com/watch?v=vioCbTo3C-4&feature=g-upl 16:12:19 ack ericP 16:12:19 ericP, you wanted to ask if there are folks who have a way to evaluate these trade-offs 16:12:31 MacTed: There are people who build things similar to RDF, then come around realize it's really got something to bring to the table. 16:12:48 ericp: Who is good at such marketing? 16:13:05 manu1: The HTML5 people. They're great at marketing, speaking, telling people how easy it is. 16:13:18 Topic: RDF Spaces and Datasets 16:13:26 Deferred until next week 16:13:33 Topic: AOB 16:13:44 I think we have Defered Graphs not Named Graphs 16:13:56 Deferred too 16:14:05 No, we won't talk about Turtle 16:14:08 bye 16:14:08 -yvesr 16:14:16 -Souri 16:14:17 bye 16:14:18 -gkellogg 16:14:19 -AZ 16:14:19 -Ivan 16:14:21 -zwu2 16:14:23 rssagent, generate minutes 16:14:23 -manu1 16:14:24 -ScottB 16:14:24 -pchampin 16:14:25 -davidwood 16:14:26 -EricP 16:14:27 -AlexHall 16:14:29 -LeeF 16:14:32 -sandro 16:14:34 -MacTed 16:14:36 -gavinc 16:14:38 -cgreer 16:14:41 RRSAgent, draft minutes 16:14:41 I have made the request to generate http://www.w3.org/2012/06/20-rdf-wg-minutes.html MacTed 16:14:42 gavinc? 16:15:00 AlexHall has left #rdf-wg 16:15:09 -AndyS 16:15:12 -cygri 16:15:18 SW_RDFWG()11:00AM has ended 16:15:22 Attendees were yvesr, cygri, +1.707.318.aaaa, cgreer, AndyS, SteveH, Ivan, +1.408.996.aabb, pchampin, ScottB, MacTed, gkellogg, sandro, +1.540.898.aacc, davidwood, EricP, Arnaud, 16:15:24 ... AZ, +1.443.212.aadd, manu1, zwu2, +1.707.861.aaff, gavinc, AlexHall, +1.617.553.aagg, LeeF, Souri 16:17:11 rssagent, draft minutes 16:17:30 davidwood: Note, the reason I mentioned those two videos is that I stay away from mentioning RDF until a very small section of the JSON-LD intro... and then, only at the very end. 16:18:24 davidwood: To flip the question on its head - instead of asking "Why doesn't the Introduction say anything about RDF?"... why not ask "What does putting RDF in the Introduction buy us?" 16:19:34