14:56:13 RRSAgent has joined #rdf-wg 14:56:13 logging to http://www.w3.org/2013/05/01-rdf-wg-irc 14:56:15 RRSAgent, make logs world 14:56:15 Zakim has joined #rdf-wg 14:56:17 Zakim, this will be 73394 14:56:17 ok, trackbot; I see SW_RDFWG()11:00AM scheduled to start in 4 minutes 14:56:18 Meeting: RDF Working Group Teleconference 14:56:18 Date: 01 May 2013 14:58:14 markus has joined #rdf-wg 14:58:52 gkellogg has joined #rdf-wg 14:59:55 Zakim, this is 73394 14:59:55 ok, TallTed; that matches SW_RDFWG()11:00AM 14:59:59 Zakim, who's here? 14:59:59 On the phone I see Guus_Schreiber, GavinC, Sandro, OpenLink_Software 15:00:00 On IRC I see gkellogg, markus, Zakim, RRSAgent, AndyS, gavinc, Guus, TallTed, SteveH, ivan, manu1, yvesr, manu, ericP, mischat, sandro, trackbot 15:00:08 Zakim, OpenLink_Software is temporarily me 15:00:08 +TallTed; got it 15:00:09 Zakim, mute me 15:00:09 TallTed should now be muted 15:01:14 +Ivan 15:01:18 +pfps 15:01:23 +??P25 15:01:27 +[IPcaller] 15:01:32 zakim, IPCaller is me 15:01:32 +AndyS; got it 15:01:35 Zakim, ??P25 is me 15:01:35 +yvesr; got it 15:01:36 pfps has joined #rdf-wg 15:01:46 cgreer has joined #rdf-wg 15:02:01 zakim, who is here? 15:02:01 On the phone I see Guus_Schreiber, GavinC, Sandro, TallTed (muted), Ivan, pfps, yvesr, AndyS 15:02:03 On IRC I see cgreer, pfps, gkellogg, markus, Zakim, RRSAgent, AndyS, gavinc, Guus, TallTed, SteveH, ivan, manu1, yvesr, manu, ericP, mischat, sandro, trackbot 15:02:14 +??P27 15:02:27 zakim, ??P27 is me 15:02:27 +gkellogg; got it 15:02:30 +??P28 15:02:39 Zakim, ??P28 is me 15:02:40 +SteveH; got it 15:02:42 Souri has joined #rdf-wg 15:02:59 +cgreer 15:03:08 +Souri 15:03:10 +EricP 15:03:17 PatH has joined #rdf-wg 15:03:36 scrbenick cgreer 15:03:46 chair: Guus 15:03:48 scribenick cgreer 15:04:01 scribenick: cgreer 15:04:10 +PatH 15:04:21 thx 15:04:32 tbaker has joined #rdf-wg 15:05:04 topic: admin 15:05:24 propsed: accept minutes of 24 April telecon 15:05:32 s/propsed/proposed 15:05:38 Zakim, unmute me 15:05:38 TallTed should no longer be muted 15:05:54 TallTed: The links in the minutes absorb trailing punctuation 15:06:06 ... the URI poster is somehow messed up 15:06:27 s/TallTed:/pfps:/ 15:06:32 RESOLVED: to accept the minutes of the 24 April telecon 15:06:38 Zakim, mute me 15:06:38 TallTed should now be muted 15:06:45 subtopic: action items 15:07:49 subtopic: Etiquette for responding on public-comments list 15:07:50 +??P34 15:07:56 zakim, ??P34 is me 15:07:56 +markus; got it 15:08:04 Guus: We must be polite and take comments seriously 15:08:13 +1 15:08:25 Zakim, who's here? 15:08:25 On the phone I see Guus_Schreiber, GavinC, Sandro, TallTed (muted), Ivan, pfps, yvesr, AndyS, gkellogg, SteveH, cgreer, Souri, EricP, PatH, markus 15:08:27 On IRC I see tbaker, PatH, Souri, cgreer, pfps, gkellogg, markus, Zakim, RRSAgent, AndyS, gavinc, Guus, TallTed, SteveH, ivan, manu1, yvesr, manu, ericP, mischat, sandro, trackbot 15:08:28 ... we've got a lot of documents going out and keep this in our mind at this time 15:08:49 ... so keep in mind difference between public list and internal one 15:09:00 q+ 15:09:19 ericP: Apropos of comments, I've been tracking them in the wiki, just on turtle. 15:09:22 -> http://www.w3.org/2011/rdf-wg/wiki/Turtle_Candidate_Recommendation_Comments turtle comments 15:09:56 ... I'm looking for people to close issues. The protocol is to put your name under the owner. 15:10:14 ... If you're taking ownership of comments, record owner and resolution please 15:11:21 PatH: I was wondering if there's been any behavior to prompt this comment 15:11:30 zwu2 has joined #rdf-wg 15:11:50 Guus: About RDF/JSON is what I was mainly referring to, but we'll discuss that when Manu is present. 15:11:56 -PatH 15:12:07 +zwu2 15:12:23 topic: Issues related to Concepts and Semantics 15:12:34 +PatH 15:12:44 subtopic: issue 118 Simplifying datatype semantics 15:13:01 http://lists.w3.org/Archives/Public/public-rdf-wg/2013May/0012.html 15:13:52 PatH: The text here basically tries to avoid a semantic-y taint 15:14:02 ... It instead speaks of IRIs and referents 15:14:23 ivan: Perfectly answers my comments 15:14:24 q+ 15:14:36 ack PatH 15:14:36 q- 15:14:40 pfps: I'm trying to look up 'rigid identifier' 15:14:40 ack pfps 15:14:45 ... It's not in semantics yet. 15:14:51 PatH: Right, but it's in the proposed text 15:15:50 pchampin has joined #rdf-wg 15:15:51 pfps: My concern -- if somebody uses an IRI for a datatype, it seems as though that 'fixes it for everyone' 15:16:03 ... The change would be 'implementations that recognize datatype X'... 15:16:31 PatH: I'll adapt, get rid of 'rigid identifier' 15:16:45 ... It's a red flag anyhow 15:16:56 +??P36 15:17:03 zakim, ??P36 is me 15:17:03 +pchampin; got it 15:17:56 PatH: I'll prepare something to vote on now 15:18:19 subtopic: RDF Merge in Semantics 15:19:13 See http://lists.w3.org/Archives/Public/public-rdf-wg/2013Apr/0139.html 15:19:29 -EricP 15:19:34 +[GVoice] 15:19:35 pfps: AZ has a point that other specs use 'merge' so it has to stick around in addition to 'union' 15:20:03 pfps: That's OK. You keep the term around for those circumstances where you need to cope with blank nodes 15:20:50 PROPOSED: add wording to Semantics to again define the merge of two RDF graphs 15:21:49 pat: it was an editorial mistake which I will correct. no need for group decision 15:21:51 guus: fine. 15:22:38 action to PatH: add wording to Semantics to again define the merge of two RDF graphs 15:22:38 Error finding 'to'. You can review and register nicknames at . 15:22:48 ACTION PatH: add wording to Semantics to again define the merge of two RDF graphs 15:22:48 Created ACTION-261 - Add wording to Semantics to again define the merge of two RDF graphs [on Patrick Hayes - due 2013-05-08]. 15:23:26 topic: Turtle 15:24:00 gavinc: one of the possible outcomes of the problem is to remove XML and HTML from concepts. 15:24:09 ... the issue is DOM requirements 15:24:14 Zakim, who is noisy? 15:24:15 zakim, who is noisy? 15:24:25 yvesr, listening for 10 seconds I heard sound from the following: ericP (29%), GavinC (33%), Guus_Schreiber (18%) 15:24:37 ivan, listening for 12 seconds I heard sound from the following: GavinC (83%), PatH (3%), Guus_Schreiber (21%) 15:24:51 gavinc: The HTML fragment parsing as it stands produces an HTML document. 15:25:07 ... There's a spec in progress for a fragment, but it's part of Web Components 15:25:11 ... and it's still a WD 15:25:24 ... for XML, we're referencing DOM4, not DOM3 15:25:41 ... the question of 'can we reference DOM4' is resolved, but what about fragment parsing part of HTML 15:26:00 sure it makes sense 15:26:12 Guus: What do we need to fix? 15:26:31 gavinc: The DOM4 vs. 3 is resolved. The HTML issue is a little more complex 15:26:34 q+ 15:26:42 ... The fragment parsing for HTML just ain't stable 15:26:56 ack ivan 15:27:05 ivan: Why do you say referencing DOM4 is OK? 15:27:09 ... This is also a WD 15:27:22 ... I'm wondering whether we need DOM4. 15:27:34 gavinc: THere are comparison methods in DOM3, but they are not implemented 15:27:39 You could reference the WHATWG version of DOM4. 15:27:57 was just about to propose the same :-) 15:28:02 gavinc: What's specified in DOM4, although it's a WD, there are implementations at least 15:28:05 q? 15:28:07 q+ 15:28:35 ivan: We still don't know whether or not we can reference DOM4. The other issue though... 15:28:39 ack sandro 15:28:46 ... perhaps we can say that HTML datatype is not normative 15:29:00 gavinc: That gets around process problem, but doesn't help implementors 15:29:19 ... I want to just make sure that implementors get HTML datatypes right 15:29:34 sandro: Let's put aside procedural problems. 15:30:01 ... So this comes up if somebody's writing an RDF system and somebody wants to match HTML datatypes, even if representations are different 15:30:09 ... worst case is that they cannot do value comparisons 15:30:22 gavinc: Either that or people expect HTML that you can actually use 15:30:31 ivan: Or equality in SPARQL, but it doesn't happen 15:30:36

foo ==

foo

15:30:48 sandro: Because you're expecting normative ops, attribute order, whitespace, etc. 15:31:08 gavinc: Or all-closed elements vs non-closing ones. 15:31:25 sandro: As a programmer, I'd be happy if it matched, but we're not used to that as of yet 15:31:43 gavinc: every web browser will do the right thing here 15:32:03 ... This does happen a lot 15:32:12 sandro: But are you comparing HTML literals really? 15:32:27 gavinc: But output HTML we expect to look the same, as an effect of parsing 15:32:44 sandro: We can disagree about how important this is, but that people can get by without this 15:32:55 gavinc: Value vs. literal for HTML (and XML) 15:33:11 revized wording for issue 118 is now here, suitable for voting if voting is required: http://lists.w3.org/Archives/Public/public-rdf-wg/2013May/0014.html . Just sayin. 15:33:12 sandro: Is this the only thing wrt HTML? 15:33:22 gavinc: Yes, that's it 15:33:40 sandro: I'd be comfortable with our declaring that the HTML datatype value process is still not fully determined 15:34:01 ... and until that's settled, the datatype is a flag 15:34:09 .. to expect further work in this area 15:34:23 gavinc: And to point to where value processing is being worked out 15:34:46 ... we want people to implement this, but also to point out that it's not final yet 15:35:05 sandro: Is it also a question about non-HTML syntax? 15:35:17 ... like a literal that's '<' but HTML datatyle 15:35:25 gavinc: That's an ill-typed literal 15:35:34 Suggest we avoid test cases if we're outsourcing to DOM4/whatever for final definition as small details may change after we're finished.. 15:35:40 ... you have to be able to parse at least 15:35:41 wondering whether it wouldn't be better to rename rdf:HTML to rdf:HTML5... 15:35:51

==

15:35:54

==

? 15:36:09 can we count on trivial equivalence? 15:36:12 yeah, stuff like that ericP 15:36:22 sandro: I'm proposing that we look for an older HTML that is meaningful for this? 15:36:23 q? 15:36:41 gavinc: There's no standard anywhere about HTML fragments 15:36:57 ivan: And we can't refer to an older one. 15:37:14 gavinc: older HTMLs also didn't deal with fragment parsing 15:37:28 sandro: My point is that we don't specify which HTML 15:37:39 good point 15:37:45 +1 15:37:58 q+ 15:38:27 PatH: This does seem as though we're doing something too wishy-washy with THML 15:38:30 s/THML/HTML 15:38:59 gavinc: the idea is to dodge the lexical-value mapping for HTML 15:39:05 PatH: Which violates our spec 15:39:14 ivan: I don't see another choice. 15:39:26 q+ 15:39:31 ... We could wait a couple of years to finalize RDF but that's not an option either 15:39:32 ack PatH 15:39:34 PROPOSAL: we're specifying rdf:HTML deferring the semantics (lexical-to-value mapping) to whatever is latest/greatest HTML standard. This only comes up for people trying to do D-Entailment on rdf:HTML literals --- determining equality of value, and checking for ill-typed. 15:39:54 sandro: This is so complex .. the basic idea has been stable, but little bits keep changing 15:40:06 PatH: But we didn't have HTML before. 15:40:17 ack markus 15:40:20 ivan: Now we have HTML which is not XML. It's much more common now 15:40:31 markus: Why do we need to normalize HTML at all? 15:40:41 Not normalizing! Just parsing 15:40:44 ... we could just use string comparison 15:40:54 ... isn't that viable? 15:41:15 ivan: In practice that would be difficult. 15:41:39 zakim, who is talking? 15:41:40 ... same issue in XML. XML literals rely on XML tools 15:41:50 sandro, listening for 10 seconds I could not identify any sounds 15:41:52 ... and the tools can produce a different literal 15:41:57 zakim, who is talking? 15:42:07 sandro, listening for 10 seconds I heard sound from the following: markus (83%) 15:42:13 zakim, who is talking? 15:42:13 markus: but you can't have interoperability in this case. 15:42:20 eh, 3 or 4 months ;) 15:42:23 sandro, listening for 10 seconds I heard sound from the following: PatH (14%), Ivan (35%), markus (54%) 15:42:27 ivan: out hope is that in two years HTML5 WG will finalize 15:42:28 zakim, who is talking? 15:42:38 sandro, listening for 10 seconds I heard sound from the following: PatH (5%), Guus_Schreiber (9%), markus (60%) 15:42:45 markus: Then HTML6 will come 15:42:56 gavinc: To be clear we're talking about fragment parsing algorithm, not HTML5 15:43:11 ... this is weirder than you think it is 15:43:16 q+ 15:43:18 we are tslking about this: http://www.w3.org/TR/rdf11-concepts/#section-html 15:43:30 sandro: How about two data types. HTML-String and parsed-HTML-string 15:43:35 ack pfps 15:43:37 ... we can't define the latter yet 15:43:53 pfps: I've seen a solution to this in Schema-datatypes 15:44:02 ... to be compliant you can either use XML 1.0 or XML 1.1 15:44:12 q+ 15:44:13 ... which was written when 1.1 was in flux 15:44:32 sandro: It's a bit analogous to our dependency on Unicode 15:44:46 ericP: But the contract with Unicode is that there will be no new punctuation 15:44:55 gavinc: and HTML's main goal is backwards compat 15:45:07 ack gkellogg 15:45:24 ericP: HTML doesnt provide for forward compat 15:45:50 gkellogg: Perhaps we can require that implemenations provide equality based on string comparison, but have an option to change in future 15:46:01 sandro: The question is what if we do use D-entailment 15:46:11 Yeah, we WANT people to do lexical-to-value mapping 15:46:19 ... we want people not to have to remember the string 15:46:26 ... the string is gone if you parse 15:46:39 ... sounds like we need two datatypes, the second one will change 15:46:50 gavinc: The one that doesn't map to a value doesn't have a datatype 15:47:13 PatH: It's its own value space 15:47:20 sandro: The value space is 'string' 15:47:28 gavinc: This reads funny. lexical space and value space are the same 15:47:34 sandro: yep it's string with a flag 15:47:58 gavinc: I'm amused 15:48:12 sandro: I need to know about the flag. 15:48:22 gavinc: Would then HTML entities be equivalient to same string? 15:48:31 ... would seem to be no 15:48:56 ivan: I'd me more comfortable keeping what we have now, plus a little hand waving 15:49:31 STRAWPOLL: (1) two html datatypes, parsed and unparsed; (2) one html datatype, semantics not set yet, (3) something else 15:49:43 1 2 15:50:04 2 15:50:05 tnx ivan 15:50:05 pref 2, can live with 1 15:50:05 I prefer 2 15:50:05 2 (lexical to value mapping to be defined later) 15:50:05 2 15:50:06 2 15:50:06 2 15:50:08 live with 1, prefer 2 15:50:08 2 15:50:10 2 15:50:12 2 15:50:20 prefer 2, OK with 1 15:50:27 1 2 (would prefer to just have unparsed) 15:50:33 3 15:50:34 2 15:50:59 +1 PatH 15:51:03 PatH: 'something else' is that we should be explicit about defining but that it's changeable 15:51:11 ivan: That's what I meant by 2 15:51:31 ... we make it clear that it's a soft target 15:51:34 PROPOSAL: we'll specifying rdf:HTML by deferring the semantics (lexical-to-value mapping) to whatever is latest/greatest HTML standard. This only comes up for people trying to do D-Entailment on rdf:HTML literals --- determining equality of value, and checking for ill-typed. 15:52:37 +1 15:52:40 +1 15:52:44 +1 15:52:46 +1 15:52:48 +0 15:52:48 +1 15:52:48 +1 15:52:49 +1 15:52:53 guus: it's editorial how much of this we say this now. 15:52:56 +1 15:53:31 RESOLVED: close issue-63: we'll specifying rdf:HTML by deferring the semantics (lexical-to-value mapping) to whatever is latest/greatest HTML standard. This only comes up for people trying to do D-Entailment on rdf:HTML literals --- determining equality of value, and checking for ill-typed. 15:53:53 (or it was already closed, but tag this as related to issue-63) 15:54:21 http://lists.w3.org/Archives/Public/public-rdf-wg/2013May/0014.html 15:54:23 subtopic: back to issue 118 15:54:36 q+ 15:55:22 PROPSED: to resolve ISSUE-118 according to Pat's proposal in http://lists.w3.org/Archives/Public/public-rdf-wg/2013May/0014.html 15:55:47 hahah 15:55:47 what's the interpretation of {

""""""rdf:HTMLLiteral . } ? 15:55:50 +1 15:55:51 +1 15:55:52 8.3 15:55:53 +1 15:55:53 +1 15:55:56 s/PROPSED/PROPOSED/ 15:55:57 +1 15:55:58 +1 15:56:00 +1 15:56:00 +1 15:56:04 +1 15:56:05 +1 15:56:09 +1 15:56:22 RESOLVED: to resolve ISSUE-118 according to Pat's proposal in http://lists.w3.org/Archives/Public/public-rdf-wg/2013May/0014.html [17:55] hahah 15:57:05 Guus: We're done with concepts and semantics. 15:57:06 woot 15:57:34 eric, that graph means that s has a p which is the html text "". 15:57:37 Guus: Two minuts for JSON-LD and Turtle 15:57:41 s/minuts/minutes/ 15:57:57 Guus: How about that turtle test suite? 15:58:03 gavinc: blocked by feature at risk 15:58:11 ericP: Also 0 in literals 15:58:20 gavinc: That's fine in test cases 15:58:34 ... we should datatype them something else if they're not strings 15:59:01 gavinc: I started the action for feature at risk. 15:59:03 +1 have some test cases on "\0"^^ 15:59:20 ... lots of 'meh' on prefixes 15:59:26 ... and some who don't like it 15:59:38 Guus: please complete action by next week 15:59:47 sandro: is everything on comments page? 15:59:53 just realized that JSON-LD LC ends next week 15:59:57 gavinc: yes, no positive ones, just two negative ones. 16:00:10 gotta run. bye. 16:00:14 -PatH 16:00:20 ... strongest argument is that we've not changed turtle except this 16:00:28 sandro: but that's not true 16:00:28 i would characterize DBooth's response to those comments as positive 16:00:34 Guus: but we are done for this week. 16:00:47 -Ivan 16:00:49 -gkellogg 16:00:49 -Sandro 16:00:50 -yvesr 16:00:50 -TallTed 16:00:51 -markus 16:00:53 -ericP 16:00:54 -cgreer 16:00:54 -SteveH 16:00:54 -zwu2 16:00:57 -GavinC 16:00:57 -Souri 16:01:00 -AndyS 16:01:07 -pchampin 16:01:09 trackbot, end meeting 16:01:09 Zakim, list attendees 16:01:09 As of this point the attendees have been Guus_Schreiber, GavinC, Sandro, TallTed, Ivan, pfps, AndyS, yvesr, gkellogg, SteveH, cgreer, Souri, EricP, PatH, markus, zwu2, pchampin 16:01:17 RRSAgent, please draft minutes 16:01:17 I have made the request to generate http://www.w3.org/2013/05/01-rdf-wg-minutes.html trackbot 16:01:18 RRSAgent, bye 16:01:18 I see 1 open action item saved in http://www.w3.org/2013/05/01-rdf-wg-actions.rdf : 16:01:18 ACTION: PatH to add wording to Semantics to again define the merge of two RDF graphs [1] 16:01:18 recorded in http://www.w3.org/2013/05/01-rdf-wg-irc#T15-22-48