15:54:25 RRSAgent has joined #rdf-wg 15:54:25 logging to http://www.w3.org/2013/01/16-rdf-wg-irc 15:54:32 Zakim, this is rdf 15:54:33 davidwood, I see SW_RDFWG()11:00AM in the schedule but not yet started. Perhaps you mean "this will be rdf". 15:54:44 Zakim, this will be rdf 15:54:44 ok, davidwood; I see SW_RDFWG()11:00AM scheduled to start in 6 minutes 15:55:05 Chair: David Wood 15:55:23 I think we will need a scribe replacement... 15:57:01 Guus has joined #rdf-wg 15:57:46 SW_RDFWG()11:00AM has now started 15:57:53 +Guus 15:58:09 +bhyland 15:58:26 Zakim, bhyland is me 15:58:27 +davidwood; got it 15:58:37 AZ has joined #rdf-wg 15:59:49 +[GVoice] 15:59:55 Zakim, GVoice is me 15:59:55 +ericP; got it 16:00:15 markus has joined #rdf-wg 16:00:31 +??P13 16:00:44 +??P14 16:00:50 Zakim, ??P14 is me 16:00:50 +SteveH; got it 16:00:53 Arnaud has joined #rdf-wg 16:01:06 AndyS has joined #rdf-wg 16:01:11 gavinc has joined #rdf-wg 16:01:35 +Arnaud 16:01:56 +GavinC 16:02:04 Zakim, who is on the phone? 16:02:04 On the phone I see Guus, davidwood, ericP, ??P13, SteveH, Arnaud, GavinC 16:02:09 Zakim, ??P13 is me 16:02:10 +yvesr; got it 16:02:15 zwu2 has joined #rdf-wg 16:02:21 +Sandro 16:02:32 + +1.617.838.aaaa 16:02:35 +??P24 16:02:40 Zakim, aaaa is me 16:02:40 +TallTed; got it 16:02:46 +[IPcaller] 16:02:47 Zakim, ??P24 is me 16:02:48 +AZ; got it 16:02:48 -[IPcaller] 16:02:49 Zakim, mute me 16:02:49 TallTed should now be muted 16:03:10 + +1.408.992.aabb 16:03:15 +[IPcaller] 16:03:25 zakim, IPCaller is me 16:03:25 +AndyS; got it 16:04:00 +cygri 16:04:03 zakim, dial ivan-voip 16:04:03 ok, ivan; the call is being made 16:04:04 +Ivan 16:04:25 +??P26 16:04:35 zakim, ??P26 is me 16:04:35 +markus; got it 16:04:49 http://www.w3.org/2011/rdf-wg/meeting/2013-01-09 16:05:34 + +1.650.265.aacc 16:05:49 zakim, +1.650.265.aacc is me 16:05:49 +zwu2; got it 16:05:51 Zakim, who is here? 16:05:51 On the phone I see Guus, davidwood, ericP, yvesr, SteveH, Arnaud, GavinC, Sandro, TallTed (muted), AZ, +1.408.992.aabb, AndyS, cygri, Ivan, markus, zwu2 16:05:52 zakim, mute me 16:05:55 On IRC I see zwu2, gavinc, AndyS, Arnaud, markus, AZ, Guus, RRSAgent, Zakim, cygri, tbaker, FabGandon, TallTed, gkellogg, ivan, SteveH, trackbot, mischat, davidwood, manu1, manu, 16:05:55 ... yvesr, sandro, ericP 16:05:55 zwu2 should now be muted 16:06:08 scribe: cygri 16:06:15 -ericP 16:06:16 PROPOSED to accept the minutes of the 9 January telecon: http://www.w3.org/2011/rdf-wg/meeting/2013-01-09 16:06:29 topic: Minutes of last meeting 16:06:47 sandro: i fixed the problem in last week's minutes 16:07:03 RESOLVED: accept the minutes of the 9 January telecon: http://www.w3.org/2011/rdf-wg/meeting/2013-01-09\ 16:07:10 Review of action items 16:07:10 http://www.w3.org/2011/rdf-wg/track/actions/pendingreview 16:07:10 http://www.w3.org/2011/rdf-wg/track/actions/open 16:07:16 s/09\/09/ 16:07:20 pfps has joined #rdf-wg 16:07:23 topic: Review of action items 16:07:33 ACTION-190 was done a while ago? 16:07:33 q+ 16:07:57 ack AZ 16:08:15 AZ: I had an action to complete for yesterday; it's not yet finished 16:08:24 … drafting the document on dataset semantics 16:08:35 … hope to have a draft by end of the week, or beginning of next 16:08:47 … how do i publish it on the w3c server? 16:09:06 ivan: you should be able to write to mercurial 16:09:15 … open a new folder, edit it there, and commit it 16:09:25 + +33.4.92.96.aadd 16:09:33 … once it becomes a proper W3C publication, webmaster copies it from mercurial 16:09:55 davidwood: we will need to extend the charter soon 16:09:59 LeeF has joined #rdf-wg 16:10:00 Zakim, +33.4.92.96.aadd is me 16:10:00 +FabGandon; got it 16:10:01 … so need to get our documents in order 16:10:14 … guus, status of the primer? 16:10:20 Guus: not much progress since last time 16:10:39 davidwood: we will need to get some work done in the next weeks to avoid embarrassment 16:10:43 Topic: Concepts 16:10:46 zakim, mute me 16:10:46 Ivan should now be muted 16:10:48 topic: Concepts 16:10:56 davidwood: we have some open issues 16:11:18 … i think some of them can be handled quickly, others may need more discussion 16:11:22 http://www.w3.org/2011/rdf-wg/track/issues/105: Graphs, datasets, authoritative representations, and content negotiation 16:11:34 ISSUE-105? 16:11:34 ISSUE-105 -- Graphs, datasets, authoritative representations, and content negotiation -- open 16:11:34 http://www.w3.org/2011/rdf-wg/track/issues/105 16:12:35 +[GVoice] 16:12:45 cygri: This is a nebulous issue, there are multiple parts. One is the media types of graphs vs datasets 16:13:03 ... this came up with JSON-LD. 16:13:38 q? 16:13:41 ... another is how do fragment identifiers work in datasets? If you have graph names with fragments does that mean anything? 16:14:24 ... I think the summary from before Christmas was that if we don't say anything that Datasets and Graphs can be used interchangeably. That's what people will do if we don't say anything anyway 16:15:00 +PatH 16:15:01 ... if we do say anything about the relationship between Datasets and Graphs we may be creeping back into defining dataset semantics which we said we wouldn't do. 16:15:19 q+ 16:15:30 ack sandro 16:15:51 davidwood: Goal is to determine if we can close this quickly 16:16:03 sandro: I think JSON-LD says something about this 16:16:48 Is Sandro saying that one can always return a trig document when an rdf graph is being requested? 16:16:58 pchampin has joined #rdf-wg 16:17:04 +[IPcaller] 16:17:11 zakim, IPcaller is me 16:17:11 +LeeF; got it 16:17:18 davidwood: No, pfps, I don't think he said that. 16:17:19 Does not reflect concern on the list from Steve IIRC. 16:17:20 zakim, mute me please 16:17:21 LeeF should now be muted 16:17:29 +??P36 16:17:36 PROPOSED: We advise people that when they are trying to get a graph and get a dataset instead (in Trig or JSON-LD), it's okay to just use the default graph as your graph, without issuing a warning or error. 16:17:44 pfps: If your asking for a graph you should never get back a dataset 16:18:04 ok 16:18:08 +1 16:18:27 + +1.415.686.aaee 16:18:33 zakim, I am aaee 16:18:33 +gkellogg; got it 16:18:35 +1 to pfps 16:18:54 pfps: If I ask for a RDF document, and I get back something else, what should I do? 16:19:18 sandro: if you can't parse the TriG document you clearly you can't do anything 16:19:20 +1 16:19:23 +1 16:19:27 ... but if you can, use the default graph 16:19:36 -1 from PatH (via phone) 16:19:43 pfps: if this is acceptable then providers will do it. 16:19:47 http://www.w3.org/2011/rdf-wg/track/issues/106: Relationship between RDF Concepts and RDF Semantics 16:19:51 should we really specify how an error is to be handled? 16:19:52 you absolutely should not interpret the default graph as if it were graph content 16:19:53 davidwood: Moving on. 16:19:54 +1 16:19:55 -1 from me because of implementation burden 16:19:56 ISSUE-106? 16:19:56 ISSUE-106 -- Relationship between RDF Concepts and RDF Semantics -- open 16:19:56 http://www.w3.org/2011/rdf-wg/track/issues/106 16:20:25 cygri: Mostly editoral. There is some content that moved between them. 16:20:47 ... I guess this is mostly editoral, but I would like to keep open until there is a RDF Semantics draft 16:21:10 davidwood: Propose to close? 16:21:42 cygri: I would like to keep it open, as there will be some work in the semantics draft... 16:22:01 PatH: I think they are all just editoral, no diffrence of opinion 16:22:45 cygri: I would like to have a marker in the concepts, so that I can refer to the fact that there isn't a semantics draft for RDF concepts to point to 16:22:47 it's useful for bookkeeping; seems reasonable to leave it and move on 16:23:11 cygri: if the chairs are happier with it closed and an action instead that's fine 16:23:35 davidwood: I prefer to close and turn into action. 16:23:44 cygri: I'll do that. 16:23:59 cygri: I raised it, I can close it? 16:24:11 davidwood: Prefer to close and refer to action 16:24:21 PatH: Ringing off 16:24:27 -PatH 16:24:56 ACTION on PatH to work with cygri to make there is no duplicated content between RDF Concepts and RDF Semantics 16:24:56 Error finding 'on'. You can review and register nicknames at . 16:25:03 ACTION PatH to work with cygri to make there is no duplicated content between RDF Concepts and RDF Semantics 16:25:03 Created ACTION-221 - Work with cygri to make there is no duplicated content between RDF Concepts and RDF Semantics [on Patrick Hayes - due 2013-01-23]. 16:25:30 CLOSE ISSUE-106 Converted to ACTION-221 16:25:47 ACTION: cygri to work with PatH to make sure there is no duplicated content between RDF Concepts and RDF Semantics 16:25:47 Created ACTION-222 - Work with PatH to make sure there is no duplicated content between RDF Concepts and RDF Semantics [on Richard Cyganiak - due 2013-01-23]. 16:25:54 CLOSE ISSUE-106 16:25:54 Closed ISSUE-106 Relationship between RDF Concepts and RDF Semantics. 16:25:57 ACTION-222? 16:25:57 ACTION-222 -- Richard Cyganiak to work with PatH to make sure there is no duplicated content between RDF Concepts and RDF Semantics -- due 2013-01-23 -- OPEN 16:25:57 http://www.w3.org/2011/rdf-wg/track/actions/222 16:26:30 http://www.w3.org/2011/rdf-wg/track/issues/107: Revised definition of blank nodes 16:26:31 ISSUE-107 16:26:31 ISSUE-107 -- Revised definition of blank nodes -- open 16:26:31 http://www.w3.org/2011/rdf-wg/track/issues/107 16:26:34 q+ 16:26:34 trackbot, associate ACTION-222 with ISSUE-106 16:26:35 ACTION-222 (Work with PatH to make sure there is no duplicated content between RDF Concepts and RDF Semantics) associated with ISSUE-106. 16:27:00 cygri: We didn't resolve this in the last WD 16:27:26 trackbot, associate ACTION-221 with ISSUE-106 16:27:26 ACTION-221 (Work with cygri to make there is no duplicated content between RDF Concepts and RDF Semantics) associated with ISSUE-106. 16:27:30 ... next step to work with AZ to take one of the proposals and make both of us happy with it. 16:27:47 ack az 16:28:00 AZ: drafted a mail but didn't send it 16:28:12 ... I just have to find it and complete it in the next few days 16:28:18 http://www.w3.org/2011/rdf-wg/track/issues/109: What's the consequence of a literal being ill-typed? 16:28:21 i'm getting pressure to go to another call and don't think i'm critical here 16:28:25 ISSUE-109 16:28:25 ISSUE-109 -- What's the consequence of a literal being ill-typed? -- open 16:28:25 http://www.w3.org/2011/rdf-wg/track/issues/109 16:28:49 davidwood: Lots of disciusion, no resolution 16:29:12 cygri: One way of doing this is making it part of the semantics. PatH said there was a way of doing that that makes sense to him. 16:29:24 ... there would also need to be a small edit to RDF Concepts to make it happen. 16:29:26 s/disciusion/discussion/ 16:29:35 -> https://dvcs.w3.org/hg/rdf/file/tip/rdf-turtle/coverage/tests/ atomic tests for Turtle 16:29:42 (committed after much pain) 16:29:46 ... it might be controversial 16:29:52 -ericP 16:30:12 ... some clarification about what applications are supposed to do with malformed typed literals? is it an error or not? 16:30:20 q? 16:30:24 pfps: If it's an error then where is the error message? 16:30:30 ... it's NOT an error! 16:30:43 ... It's perfectly fine as far as RDF is concerned 16:30:46 ... what's the issue? 16:30:58 cygri: The issue is that the datatype can't assign a value. 16:31:23 ... it clearly is an error, someone did something wrong publishing that data. 16:31:37 ... You shouldn't be publishing that kind of data. 16:31:51 ... is this an error or not? The current spec doesn't say one way or another 16:31:59 pfps: I think everything is perfectly clear. 16:32:07 pfps: It isn't an error. 16:32:13 pfps: How can it be an error? 16:32:31 +1 with cygri - we should be clear on that, and it should be flagged by applications 16:32:35 davidwood: any time the spec talks about an inconsistent graph... 16:32:48 q+ 16:32:49 sandro: An error is when someone does something they aren't supposed to do. 16:32:59 pfps: an error is when the system barfs 16:33:02 If we don't agree on what an error is then it doesn't seem so productive to discuss whether this condition is an error or not :) 16:33:06 RDF 2004 says: "Such a case, while in error, is not syntactically ill-formed." 16:33:14 a mistyped literal, like "abc" typed as a datetime. that seems like an error... 16:33:27 Quote text. 16:33:33 q- 16:33:40 q? 16:33:58 sandro: Lexical space provided by a regular expression... 16:34:09 pfps: if you go outside, stuff happens, but it's not an error 16:34:22 ... then you need to have an error condition and error return 16:34:38 cygri: RDF Concepts says there is an error 16:34:43 pfps: Then RDF Concepts is wrong. 16:34:51 ... there should be some handling method for that error 16:35:02 s/RDF Concepts says there is an error/2004 RDF Concepts says there is an error/ 16:35:20 cygri: No, it doesn't say what happens when you use a language tag that isn't a language, it doesn't say what to do if you use an IRI that isn't an IRI 16:35:34 pchampin: A data model can have an illtyped literal 16:36:06 cygri: RDF 2004 says that in the case of an ill-typed it is an error but not a syntax error 16:36:20 s/pchampin/pfps 16:36:30 pfps: It's a stupid thing to do, but not an "error" 16:36:39 cygri: I would like it to be an error 16:36:47 should we do a strawpoll on whether we think it should be an error or not? 16:36:53 pfps: That would be a change to the RDF Semantics 16:36:57 I would like it to be an inconsistency as well 16:37:11 yvesr, we know now that we will not agree... 16:37:20 sandro: Do I have to accept it? Do I have to ignore it? What do I do? 16:37:25 pfps: I'd like to keep doing what I do today, I accept it. 16:38:11 AZ, can you please put that in the minutes? 16:38:40 so it's "in error" but not "an error" ? 16:38:40 I think that RDF 2004 saying "... while in error, is not syntactically ill formed" is actally meaning "... while stupid as hell, is not formally an error" 16:38:57 +1 cygri it should be an inconsistency 16:39:00 cygri: Semantics is strange in this regard. It would be simple to say that the presence of an ill typed literal creates an inconsistency 16:39:01 May not know the datatype map. Hence need to deal with it in some sense. Inconsistency is unknown. 16:39:06 pfps: That requires a change to the RDF Semantics 16:39:27 davidwood: I think he did propose that. 16:39:41 pfps: Right now we have two documents that say error where there is no error. 16:40:10 cygri: We need to address this, we should change this from a Concepts into a Semantics issue. 16:40:46 davidwood: is there a pointer to the resolution being talked about in IRC? 16:41:11 s/resolution/proposal/ 16:41:24 http://lists.w3.org/Archives/Public/public-rdf-wg/2012Nov/0268.html 16:41:38 davidwood: PatH says he's fine with that. pfps you disagree? 16:42:02 pfps: If the change is going to be made, it needs to be made correctly. 16:42:27 pfps: That proposal doesn't make sense. 16:43:15 cygri: I don't know how to change that proposal into the semantics. 16:43:40 ... the mecanics would need to be worked out. 16:44:09 pfps: The proposal is kind of weird. In any D entailment... ... ... ... 16:44:50 q+ 16:44:56 ack ivan 16:44:57 zakim, unmute me 16:44:58 Ivan was not muted, ivan 16:45:02 davidwood: hoping to move on... 16:45:13 +PatH 16:45:26 ivan: What pfps described for D entailment, don't we already have that for XMLLiterals? 16:45:55 cygri: The pure presense of an ill-typed literal doesn't cause an inconsistency. Only if there is a range statement. 16:46:28 ... same for all datatypes. You have to have a range statement AND an ill-typed literal to get an inconsistency. 16:47:21 PatH: SOmething could be consistant in RDF, but not with a specific datatype map. 16:47:23 zakim, mute me 16:47:23 Ivan should now be muted 16:47:31 http://www.w3.org/2011/rdf-wg/track/issues/111: Should RDF Concepts define any operations on RDF datasets? 16:47:34 davidwood: lets move on 16:47:36 ISSUE-111 16:47:36 ISSUE-111 -- Should RDF Concepts define any operations on RDF datasets? -- open 16:47:36 http://www.w3.org/2011/rdf-wg/track/issues/111 16:47:56 davidwood: If we find a resolution this will effect ISSUE-105 16:48:03 http://www.w3.org/2011/rdf-wg/wiki/Dataset_Operations 16:48:36 -GavinC 16:48:59 path has joined #rdf-wg 16:49:20 paste that again? 16:49:42 path, http://www.w3.org/2011/rdf-wg/wiki/Dataset_Operations 16:49:54 ta 16:50:17 +GavinC 16:50:38 gavinc_ has joined #rdf-wg 16:50:51 AZ:Tentative definition: 16:50:51 """ 16:50:51 Two RDF datasets (DG1, NG1) and (DG2, NG2) are dataset-isomorphic iff: 16:50:51 - DG1 and DG2 are graph-isomorphic; 16:50:51 - For each (n1,g1) in NG1, there exists (n2,g2) in NG2 such that n1=n2 16:50:51 and g1 and g2 are graph-isomorphic; 16:50:51 - For each (n2,g2) in NG2, there exists (n1,g1) in NG1 such that n1=n2 16:50:52 and g1 and g2 are graph-isomorphic. 16:50:52 """ 16:51:09 sandro: i was assuming we won't define any of this 16:51:17 … given that we don't do semantics for datasets 16:51:18 q+ 16:51:35 … i'm not opposed to this but seems unnecessary 16:51:37 +1 to sandro 16:51:48 q? 16:52:16 ack AZ 16:53:26 sandro: i guess we should do for datasets whatever we do for graphs 16:53:28 I can scribe 16:53:41 -zwu2 16:53:57 AZ: isomorphism is not related to semantics, it's purely about structure 16:54:03 Sorry, have to go to another meeting. 16:54:03 Hmm, things are fine in Sunnyvale. 16:54:06 q? 16:54:12 ...(not to be confused with equivalence) 16:54:50 cygri: we still need some discussion; is there anything that makes sense and would not create too much contention 16:55:24 path: what we could say: if you replace in a dataset a graph by an isomorphic graph, the two datasets are isomorphic 16:55:52 ... That extends simply the notion of graph-isomotphism to datasets. 16:56:05 AZ: this basically is what I proposed. 16:56:58 davidwood: should RDF concepts define only isomorphism on RDF datasets? 16:57:11 cygri: I'm not sure other operations are not useful 16:57:26 ... e.g. union 16:57:31 q+ 16:57:40 it's not uneccessary, but there's not enough experience yet! 16:57:48 ... but may be I can be convinced it is not necessary 16:58:02 q- 16:58:06 path: my problem is that there are 3 different ways to define union, 16:58:15 yeah -- we don't have consensus on which kind of union to use 16:58:16 ... so that would take a lot of time to reach a consensus 16:58:50 i wonder if there's room to define all three of them, and give them different operatiosn name :) 16:59:00 q+ 16:59:11 UNION-MERGE, UNION-REPLACE, etc. 16:59:23 ack sandro 17:00:00 sandro: defining different unions with different names would help people to have a simpler debate in the future 17:00:10 Blog about it. 17:00:13 I don't see the point of going to the effort of defining them all right now 17:00:18 +1 to AndyS 17:00:24 +1 sandro -- name and define different (non-exhaustive!) possibilities, and then leave for future debate 17:00:35 Review/accept Pat's solution to http://www.w3.org/2011/rdf-wg/track/actions/205: Add note to explanation of skolemization 17:00:56 davidwood: Sandro, Yves, etc, go ahead and do that if you want to. 17:01:43 +[GVoice] 17:01:46 Remove the : 17:01:47 http://www.w3.org/2011/rdf-wg/track/actions/205 17:02:01 http://www.w3.org/TR/rdf11-concepts/#section-skolemization 17:02:46 cygri: it has been added, then changed after comments from Peter; I'd like Peter to check the current version (URL above) 17:02:57 s/Peter/Pat/ 17:03:59 close ACTION-205 17:03:59 Closed ACTION-205 Add note to explanation of skolemization. 17:04:19 http://www.w3.org/2011/rdf-wg/track/issues/23: Does going from single-graph to multi-graph require new format and new media types? 17:04:49 davidwood: isn't issue 23 a duplicate? 17:05:24 cygri: I think this was already discusses 17:05:41 davidwood: suggest to close issue 23, the answer being yes 17:06:06 gavin, pedal harder. 17:06:29 markus: does this mean JSON-LD would require different media-types for single-graph / multi-graph? 17:07:05 davidwood: no 17:07:08 it's the shift from "one giant graph" of RDF2004 to "there are multiple graphs" of RDFnow ... 17:07:16 +1 to close 17:07:21 PROPOSAL: Close ISSUE-23; we are indeed defining new formats and new media types for multi-graph. 17:07:23 +1 to close 17:07:23 gkellog: will this not raise problem if RDFa decides to support multiple graphs in the future? 17:07:24 +1 17:07:25 answer is obviously "yes" and we've been doing it 17:07:32 +1 17:07:34 +1 17:07:38 +1 17:07:40 s/gkellog/gkellogg/ 17:07:40 +1 17:07:42 +1 17:07:42 understood that this is about Trig and doesn't affect RDFa or JSON-LD. 17:07:45 +1 17:07:49 +1 17:07:50 +0 17:07:52 +1 17:07:53 +0 17:08:23 davidwood: we can't speculate on what RDFa will do in the future 17:08:35 RESOLVED: Close ISSUE-23; we are indeed defining new formats and new media types for multi-graph. 17:08:37 TOPIC: JSON-LD 17:08:47 http://www.w3.org/2011/rdf-wg/track/issues/16: What is the normative serialization of the JSON grammar? 17:08:51 i have to ring off. 17:09:00 -PatH 17:09:15 err... yeah, that's about What is JSON ;) 17:09:29 JSON, not RDF 17:09:31 markus: i think this is about JSON itself 17:09:56 … JSON-LD uses the JSON RFC as the basis 17:09:58 RFC4627 17:10:09 +1 for RDF4627 17:10:10 markus: JSON-LD uses RFC 4627 17:10:36 davidwood: propose to resolve this by saying that this WG uses JSON-LD to address the charter, which internally uses RFC4627 17:10:54 PROPOSAL: Resolve ISSUE-16 by saying that this WG uses JSON-LD to address the charter, which internally uses RFC4627 17:11:01 +1 17:11:02 +1 17:11:02 +1 17:11:03 +1 17:11:08 +1 17:11:12 +1 17:11:14 +1 17:11:18 +1 17:11:30 +1 17:11:31 +1 17:11:32 +1 17:11:36 RESOLVED: Resolve ISSUE-16 by saying that this WG uses JSON-LD to address the charter, which internally uses RFC4627 17:11:40 http://www.w3.org/2011/rdf-wg/track/issues/92: Mention RDF in the JSON-LD Syntax Introduction. 17:11:57 markus: that's done 17:12:07 +1 17:12:11 +1 17:12:14 PROPOSED: Resolve ISSUE-92 by saysing that it has been done 17:12:19 +1 it's done 17:12:21 +1 17:12:21 +1 17:12:22 +1 17:12:23 +1 17:12:24 +1 17:12:24 +1 again/still 17:12:24 +1 17:12:28 +1 17:12:46 +1 17:12:54 RESOLVED: Resolve ISSUE-92 by saying that it has been done 17:13:01 Working Group status: https://www.w3.org/2011/rdf-wg/track/products 17:13:42 Topic: AOB 17:13:45 q+ 17:13:50 ack markus 17:14:25 markus: what's the group's position on IRI vs URL 17:14:36 zakim, unmute me 17:14:36 Ivan should no longer be muted 17:14:44 q+ 17:14:52 … I propose we close the issue, and re-open it only if someone complains 17:14:53 markus: the JSON-LD group resolved to stick to the technically correct term IRI 17:15:03 davidwood: chair hat off, redefining terms is dangerous 17:15:18 Nice idea but URL-NG is not yet ready. 17:15:21 sandro: communities use different terms 17:15:23 ack ivan 17:15:31 davidwood: IRI is not a semweb-specific term 17:15:32 sandro: this is not only about redefining terms; different communities use different terms 17:15:47 there are lots of protocol RFCs to rewrite if we use "URL" to mean IRI 17:16:14 ivan: someone proposed to use IRI, but put a comment in the document that explains the issue, stating that some people use URL to mean the same thing 17:16:36 ivan: we can add an editorial note stressing the fact that there is some inconsistency, but that this is not the job of this group to solve this inconsistency 17:16:59 sandro: the document could use "identifier" in 99% of the document, 17:17:01 sandro: editorially, you can probably say "identifier", and just define that term somewhere as meaning IRI/URL 17:17:12 zakim, mute me 17:17:12 Ivan should now be muted 17:17:19 ... and add at some point "identifier means IRI, but you can consider is very like URL" 17:17:28 +1 to Gregg 17:17:51 gkellogg: my position is that JSON-LD should comply with the rest of the documents of this WG, using IRI 17:18:06 sandro: stick with IRI, possibly move to URL in the future 17:18:10 +1 to Ivan and Gregg 17:18:16 we should use the correct word/acronym wherever possible, and say something like "others may use or have used URL or URI or other terms for IRI would have been correct; RDF-WG cannot unify/fix all such" 17:18:22 s/sandro: stick/gkellog: stick/ 17:18:45 -Guus 17:18:54 - +1.408.992.aabb 17:18:57 -gkellogg 17:18:59 davidwood: if you want a resolution from this WG, please ask it by mail 17:19:03 -SteveH 17:19:09 -GavinC 17:19:11 -Ivan 17:19:36 -AZ 17:19:41 -markus 17:19:43 -cygri 17:19:49 https://dvcs.w3.org/hg/rdf/file/tip/rdf-turtle/coverage/tests/ 17:19:54 please to post that info to the list, ericP :-) 17:20:16 RRSAgent, make logs public 17:20:35 -LeeF 17:20:48 -Sandro 17:21:47 -AndyS 17:21:59 AndyS has left #rdf-wg 17:23:49 scribe: pchampin 17:23:53 -TallTed 17:23:56 -davidwood 17:23:58 -ericP 17:24:00 -Arnaud 17:24:09 -FabGandon 17:25:21 -pchampin 17:28:53 AndyS has joined #rdf-wg 17:29:14 ericP? 17:29:33 The new test manifest is not valid Turtle !!!!!! 17:30:27 oops 17:30:50 AndyS, which one? 17:31:32 https://dvcs.w3.org/hg/rdf/file/83d32c4aca6e/rdf-turtle/coverage/tests/manifest.ttl 17:31:41 https://dvcs.w3.org/hg/rdf/file/83d32c4aca6e/rdf-turtle/coverage/tests/manifest.ttl 17:32:33 Looks like no quoting of chars in strings. e.g. " """x""" " and teh " \u " but lots of times 17:32:50 I see it 17:35:00 disconnecting the lone participant, yvesr, in SW_RDFWG()11:00AM 17:35:02 SW_RDFWG()11:00AM has ended 17:35:02 Attendees were Guus, davidwood, ericP, SteveH, Arnaud, GavinC, yvesr, Sandro, +1.617.838.aaaa, TallTed, AZ, +1.408.992.aabb, AndyS, cygri, Ivan, markus, zwu2, FabGandon, PatH, 17:35:02 ... LeeF, pchampin, +1.415.686.aaee, gkellogg 17:35:18 was hoping to catch ericP to see if he was OK with fixes. 17:42:31 FabGandon has left #rdf-wg 17:51:20 gkellogg has joined #rdf-wg 18:10:37 davidwood1 has joined #rdf-wg 18:11:08 davidwood2 has joined #rdf-wg 19:25:48 Zakim has left #rdf-wg 20:01:06 TallTed has joined #rdf-wg