14:22:06 RRSAgent has joined #rdf-wg 14:22:06 logging to http://www.w3.org/2011/05/04-rdf-wg-irc 14:22:08 RRSAgent, make logs world 14:22:08 Zakim has joined #rdf-wg 14:22:10 Zakim, this will be 73394 14:22:10 ok, trackbot; I see SW_RDFWG()11:00AM scheduled to start in 38 minutes 14:22:11 Meeting: RDF Working Group Teleconference 14:22:11 Date: 04 May 2011 14:43:50 OlivierCorby has joined #rdf-wg 14:46:35 AndyS has joined #rdf-wg 14:46:39 Chair: David Wood 14:46:52 Scribe: Thomas Steiner 14:47:30 mischat, yes, the MIT facility does that, but might not fit all the people who want to be local at MIT. 14:48:24 sure 14:49:49 well at least it is an option, i wonder how many people would be at the east coast event if there was a european place to sit as well ... 14:50:24 Yeah, mischat, Guus was going to make a poll to find the answer to that question. 14:53:01 gavinc has joined #rdf-wg 14:53:09 Zakim, code? 14:53:09 the conference code is 73394 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), gavinc 14:53:38 SW_RDFWG()11:00AM has now started 14:53:45 + +1.707.861.aaaa 14:53:53 Zakim, aaaa is me 14:53:53 +gavinc; got it 14:54:19 zakim, dial ivan-voip 14:54:19 ok, ivan; the call is being made 14:54:20 +Ivan 14:54:56 +Tony 14:55:58 zakim, Tony is me 14:55:58 +Scott; got it 14:56:16 + +1.404.978.aabb 14:56:30 zakim, aabb is me 14:56:30 +tomayac; got it 14:57:38 +??P7 14:57:46 zakim, ??P7 is me 14:57:46 +AndyS; got it 14:57:51 + +33.4.92.38.aacc 14:58:14 zwu2 has joined #rdf-wg 14:58:18 zakim, aacc is me 14:58:18 +OlivierCorby; got it 14:59:00 mbrunati has joined #rdf-wg 14:59:00 + +1.540.898.aadd 14:59:09 zakim, aadd is me 14:59:09 +davidwood; got it 15:00:07 +??P10 15:00:08 Zakim, please dial ericP-office 15:00:08 ok, ericP; the call is being made 15:00:08 +EricP 15:00:09 pchampin has joined #rdf-wg 15:00:09 MacTed has joined #rdf-wg 15:00:23 FabGandon has joined #rdf-wg 15:00:53 zakim, ??P10 is me 15:00:53 +mbrunati; got it 15:00:54 +LeeF 15:00:59 AZ has joined #rdf-wg 15:01:01 cmatheus has joined #rdf-wg 15:01:04 +OpenLink_Software 15:01:05 Souri has joined #rdf-wg 15:01:07 ScribeNick: tomayac 15:01:21 Zakim, OpenLink_Software is temporarily me 15:01:21 +MacTed; got it 15:01:21 AlexHall has joined #rdf-wg 15:01:50 +danield 15:01:55 SteveH_ has joined #rdf-wg 15:01:56 +PatH 15:02:00 +??P17 15:02:02 +Souri 15:02:04 + +1.443.212.aaee 15:02:09 +sandro 15:02:15 Zakim, danield is me 15:02:15 +FabGandon; got it 15:02:18 Zakim, mute me 15:02:18 MacTed should now be muted 15:02:23 zakim, +1.443.212.aaee is me 15:02:23 +AlexHall; got it 15:02:33 zakim, ??P17 is Pierre-Antoine 15:02:33 I already had ??P17 as pchampin, ivan 15:02:49 PatH has joined #rdf-wg 15:03:56 q+ to object to pchampin's proposal 15:03:59 q- 15:04:08 ack me 15:04:12 Proposal to accept the minutes 15:04:27 +1 15:04:30 +1 15:04:36 Minutes accepted. 15:04:52 AI 34 overdue 15:05:01 +Russell 15:05:04 http://www.w3.org/2011/rdf-wg/track/actions/34 15:05:08 Done, whole heap of issues raised, see action 15:05:10 zakim, mute me 15:05:10 sorry, AZ, I do not know which phone connection belongs to you 15:05:11 +??P29 15:05:21 Zakim, please mute ??P29 15:05:21 ??P29 should now be muted 15:05:22 zakim, ??P29 is mischat 15:05:22 +mischat; got it 15:05:36 going thru issues today 15:05:41 some easy, some hard 15:05:41 zakim, ??P29 has mischat, SteveH 15:05:41 sorry, mischat, I do not recognize a party named '??P29' 15:05:51 proposed to close ACTION-34 15:05:55 Zakim, ??P29 is [Garlik] 15:05:55 I already had ??P29 as mischat, SteveH 15:06:01 +??P30 15:06:02 closing ACTION-34 15:06:22 zakim, maybe I'm Russel 15:06:22 I don't understand 'maybe I'm Russel', AZ 15:06:32 + +1.408.642.aaff 15:06:39 next topic: ACTION-22 15:06:40 zakim, I may be Russel 15:06:40 +Russel?; got it 15:06:47 but cygri sent regrets 15:06:57 zakim, +1.408.642.aaff is me 15:06:59 +zwu2; got it 15:07:00 zakim, mute me 15:07:00 sorry, AZ, I do not know which phone connection belongs to you 15:07:07 ACTION-21 done? 15:07:15 http://www.w3.org/2011/rdf-wg/track/actions/22 15:07:19 zakim. ??P32 is cmatheus 15:07:21 will be clearified 15:07:45 sandro: ACTION-39 closed 15:08:26 unrecorded action: look at respec text vs. wiki text 15:09:00 gavin: action was unrecorded 15:09:28 gavin, wlliam, pierre-antoine on the unrecorded action 15:09:44 zakim, ??P32 is cmatheus 15:09:45 I already had ??P32 as Nick_van_den_Bleeken, cmatheus 15:09:49 next topic: ACTION-41 15:09:59 action gavin: to compare/contrast respec vs mediawiki for spec authoring 15:09:59 Created ACTION-43 - Compare/contrast respec vs mediawiki for spec authoring [on Gavin Carothers - due 2011-05-11]. 15:10:00 poll for face2face, on antoine 15:10:00 zakim, unmute me 15:10:00 sorry, AZ, I do not know which phone connection belongs to you 15:10:08 action william: to compare/contrast respec vs mediawiki for spec authoring 15:10:08 Created ACTION-44 - Compare/contrast respec vs mediawiki for spec authoring [on William Waites - due 2011-05-11]. 15:10:11 can you hear me? 15:10:11 i found out about the video conferencing facilities at southampton uni fwiw 15:10:27 action piere-antoine: to compare/contrast respec vs mediawiki for spec authoring 15:10:27 Sorry, couldn't find user - piere-antoine 15:10:42 it seems I have a problem with my mic 15:10:46 Zakim, who's here? 15:10:46 On the phone I see gavinc, Russel?, Scott, tomayac, AndyS, OlivierCorby, davidwood, mbrunati, EricP, LeeF, MacTed (muted), FabGandon, PatH, pchampin (muted), Souri, AlexHall, 15:10:49 ... sandro, Russell, mischat (muted), ??P30, zwu2 15:10:55 action Pierre-Antoine: to compare/contrast respec vs mediawiki for spec authoring 15:10:55 Created ACTION-45 - Compare/contrast respec vs mediawiki for spec authoring [on Pierre-Antoine Champin - due 2011-05-11]. 15:11:01 zakim, ??P30 is cmatheus 15:11:01 +cmatheus; got it 15:11:06 http://www.w3.org/2011/rdf-wg/track/actions/42 15:11:08 I have a text to propose 15:11:11 ACTION-42: done? 15:11:11 ACTION-42 Propose text for resolution on archaic xsd:strings notes added 15:11:21 text in email. link anyone? 15:11:22 "PROPOSED: Recommend that data publishers use plain literals instead of xs:string typed literals and tell systems to silently convert xs:string literals to plain literals without language tag." 15:11:26 "PROPOSED: Recommend that data publishers use plain literals instead of xs:string typed literals and tell systems to silently convert xs:string literals to plain literals without language tag." 15:11:28 it's the same as in my email 15:11:35 same as in email 15:11:46 http://lists.w3.org/Archives/Public/public-rdf-wg/2011May/0057.html 15:12:10 ACTION-42 herewith closed 15:12:23 next topic: sparql-turtle alignemnt 15:12:28 +??P34 15:12:36 -mischat 15:12:38 Zakim, ??P34 is [Garlik] 15:12:38 +[Garlik]; got it 15:12:47 Zakim, [Garlik] has SteveH and mischat 15:12:47 +SteveH, mischat; got it 15:12:56 issues, agreements, disagreements 15:13:06 andy discussion lead 15:13:33 http://www.w3.org/2011/rdf-wg/wiki/Diff_SPARQL_Turtle 15:13:35 andy: agreement: on all issues 15:13:38 except for one 15:13:39 -> http://lists.w3.org/Archives/Public/public-rdf-wg/2011May/0000.html Andy's email 15:14:01 eric wishes to add a feature into turtle to allow prefixing of names 15:14:13 http://www.w3.org/2011/rdf-wg/wiki/Diff_SPARQL_Turtle#Possible_extension_to_Turtle 15:14:50 -> http://lists.w3.org/Archives/Public/public-rdf-wg/2011May/0011.html 15:15:09 eric: getting past encoding limitations in pnames 15:15:20 go on ... 15:15:22 _:Eve foaf:name "Eve\u0022 . 15:15:41 _:Eve :says "Éric says \u0022Hi\u0022" . 15:16:43 AndyS 15:17:08 eric: escaping not part of the grammar 15:17:23 q+ 15:17:27 +q 15:17:33 eric: productions of local names to include escape productions 15:17:50 ack ivan 15:17:52 ivan: why this difference? 15:18:09 zakim, Russel is me 15:18:09 +AZ; got it 15:18:42 andy: at the moment as turtle is defined, commas disallowed in prefix names 15:18:58 eric: disagrees 15:19:10 andy: that would be a change to sparql 15:19:57 andy: current form does not allow \u escapings 15:20:16 +[IPcaller] 15:20:21 ack gavinc 15:20:24 zakim, i am IPcaller 15:20:24 ok, webr3, I now associate you with [IPcaller] 15:20:38 gavin: thinks that ntriples has local names 15:20:57 andy: label for a bnode has to be decided on a per-output basis 15:21:15 andy: asks eric: are you happy w/ the outher proosals 15:21:18 eric: ACK 15:21:24 q? 15:21:32 andy: any other issues? 15:21:37 -- silence -- 15:21:42 no other issues 15:21:59 andy: on what basis do we take the decision? 15:22:05 q+ 15:22:28 eric: on the prefix nodes issues: sorry it cant be done 15:22:30 I think it's a "nice feature to have", but I'm (of course) wary of changing SPARQL right now because of the impact on implementors 15:23:03 +1 to LeeF 15:23:23 There is a dragon on the call breathing fire. 15:23:39 eric: no new prefix for each row in the db 15:23:42 zakim, who is making noise ? 15:23:44 zakim, who is speaking? 15:23:45 eric: just use the same prefix 15:23:52 mischat, listening for 10 seconds I heard sound from the following: AndyS (83%), EricP (4%) 15:24:03 davidwood, listening for 10 seconds I heard sound from the following: AndyS (24%), davidwood (5%), AZ (8%), EricP (22%) 15:24:12 sounds like LeeF is right, this is neat feature but not really essential. I suggest not worth changing sparql for. 15:24:14 andy: need a decision mechanism 15:24:22 ack ivan 15:24:30 zakim, mute me 15:24:30 AZ should now be muted 15:24:39 ivan: question is: what is the most, what is the least destructive answer? 15:25:00 ivan seems gone 15:25:08 Zakim, who's here? 15:25:08 On the phone I see gavinc, AZ (muted), Scott, tomayac, AndyS, OlivierCorby, davidwood, mbrunati, EricP, LeeF, MacTed (muted), FabGandon, PatH, pchampin (muted), Souri, AlexHall, 15:25:11 ... sandro, Russell, cmatheus, zwu2, [Garlik], [IPcaller] 15:25:12 [Garlik] has SteveH, mischat 15:25:19 Zakim, unmute az 15:25:19 AZ should no longer be muted 15:25:27 -q 15:25:39 lee: understands the use case 15:25:45 -AZ 15:25:47 lee: probably a good thing to include 15:25:50 (AZ muted, and ivan went quiet ... ivan isn't in the names list ... I'm guessing AZ took ivan's line) 15:25:55 zakim, dial ivan-voip 15:25:56 ok, ivan; the call is being made 15:25:57 +Ivan 15:26:10 ivan is back 15:26:19 s/probably a good thing to include/probably not a good thing to include during SPARQL last call/ 15:26:48 Also mildly disruptive with existing turtle and sparql implementations 15:26:57 ivan: not only last call, but also deployed sparql versions 15:26:59 Both things -- disruptive to SPARQL schedule, and somewhat disruptive to implementations 15:27:14 Maybe should ask, if we DONT do this, how bad would that be? 15:27:29 eric: not convinced that it's true 15:27:57 1.1 (or later) have been known to break (or at least, go beyond) 1.0 ... 15:28:06 q+ 15:28:12 Everyone sees to agree this would be kind of neat, but... So what is the but... for NOT doing it. 15:28:15 BASIC 2.0 commands broke in BASIC 1.0 interpreters... :-) 15:28:27 q? 15:28:52 andy: argument for not doing it: its not currently in turtle and in sparql. how much need is out there? 15:29:03 OK, thanks. 15:29:04 andy: whats the cost. would it cause a new last call? 15:29:12 pat: we have a choice: 15:29:28 pat: if we were to include it in turtle, we'd break the sparql turtle alignment 15:29:45 s/pat/davidwood/ 15:29:46 s/pat/davidwood/ 15:29:48 pat: do we want to break sparql-turtle alignment? 15:29:56 s/pat/davidwood/ 15:30:05 OK, seems to me that sparql/turtle alignment is worth quite a lot of loss of neat-o features. 15:30:06 eric: no 15:30:10 ack ivan 15:30:26 ivan: having a problem w/ sparql turtle alignment would be a mistake 15:30:38 ivan: sandro very diplomatic proposal: 15:30:59 ivan: if sparql goes to last call => sparql can make it a pending feature 15:31:04 if programmatic constructed, then the system writer gets it right anyway 15:31:15 ivan: if feedback on last call very negative => can be taken out 15:31:33 Ivan, you should be in the State Department. 15:31:39 +1 Ivan 15:31:41 ivan: make it clear that its an issue in pimplementations, and see what the feedback is 15:32:18 davidwood: happy with it 15:32:27 lee: implementers are here. opinions? 15:33:05 lee: happy, with the sparql hat on 15:33:25 sparqly pimplementors unite! 15:33:50 |= UCHAR 15:33:50 LeeF: I'm ok with it, because I'm ok with not being 100% conformant, but I wouldn't run off to make this change in my code 15:34:07 ivan: to be fair, other changes for turtle would require turtle parsers to go thru an update circle 15:34:14 I think this is less invasive than the \u escape ordering thing 15:34:21 but I'm not a parser guy 15:34:57 andy: required update is for strings and iris 15:35:05 andy: believed not to affect many people 15:35:14 _:Eve foaf:name "Eve\u0022 . 15:35:25 eric: in the sense of doesnt happen often enough? 15:35:30 andy: yep, in this sense 15:35:50 david: you think we make any progress on this, andy? or should we move on? 15:35:56 andy: think we should move on 15:36:03 as turtle implentor, I'm with Eric. Easy change to make. 15:36:07 ivan: can we agree on other issues to be solved? 15:36:27 andy: yes, i can draft a resolution 15:37:00 eric: one of the poiints in erics mail was: escaping should not be in the grammar, eric says: it should be in the grammar 15:37:14 andy: i took whatever was in the current doc 15:37:21 s/poiints/points/ 15:37:34 PROPOSED: http://lists.w3.org/Archives/Public/public-rdf-wg/2011May/0011.html Point 2-7 are agreed leaving \u processing (point 8) 15:37:48 +1 15:37:55 +1 15:38:00 +1 15:38:04 +1 15:38:05 +1 15:38:07 +1 15:38:08 +1 15:38:11 objections to andy's proposal? 15:38:13 +1 15:38:15 +1 15:38:22 no objections. propsal accepted 15:38:26 +1 15:38:30 abstain 15:38:55 +1 15:38:58 RESOLVED: http://lists.w3.org/Archives/Public/public-rdf-wg/2011May/0011.html Point 2-7 are agreed leaving \u processing 15:39:21 thanks for the productive discussion 15:39:24 next topic: 15:39:35 revisiting of post-poned issues 15:39:52 let's try to resolve whatever is possible via phone 15:39:57 let's skip others 15:40:02 clean up easy ones 15:40:18 ISSUE-42: Revisit "Something should be done about aboutEachPrefix construct" 15:40:18 ISSUE-42 Revisit "Something should be done about aboutEachPrefix construct" notes added 15:40:28 http://www.w3.org/2011/rdf-wg/track/issues/42 15:40:44 looking at issue 42 15:40:45 ISSUE-42? 15:40:45 ISSUE-42 -- Revisit "Something should be done about aboutEachPrefix construct" -- raised 15:40:45 http://www.w3.org/2011/rdf-wg/track/issues/42 15:41:26 davidwood: please check the issue and edit it if need be 15:41:28 +1 15:41:30 +1 15:41:36 +1 15:41:37 +1 15:41:37 +1 15:41:41 +1 15:41:41 +1 15:41:45 davidwood: objections to closing ISSUE-42? 15:41:47 +0 (no idea what the issue was) 15:42:12 davidwood: it's in the charter to clean left-overs 15:42:15 +1 15:42:17 +1 15:42:26 davidwood: closing ISSUE-42 15:42:37 q 15:42:37 ISSUE-43? 15:42:37 ISSUE-43 -- Revisit "Suggestion that Qnames should be allowed as values for attributes such as rdf:about" -- raised 15:42:37 http://www.w3.org/2011/rdf-wg/track/issues/43 15:42:45 next: ISSUE-43 15:43:01 +1 to resolve/close 15:43:04 +1 15:43:04 +1 15:43:06 +1 15:43:08 +1 15:43:10 +1 15:43:12 +1 15:43:12 +1 to close 15:43:15 +0 15:43:20 theere was agreement on email to close this ISSUE-43 15:43:21 +0 15:43:23 +0 15:43:23 +0 15:43:28 -0 15:43:29 davidwood: closing ISSUE-43 15:43:31 ISSUE-44? 15:43:31 ISSUE-44 -- Revisit "The RDF XML syntax cannot represent all possible Property URI's" -- raised 15:43:31 http://www.w3.org/2011/rdf-wg/track/issues/44 15:43:49 next: ISSUE-44 15:43:52 +1 to close, can't see any reason to continue soemthing that won't change 15:43:59 +1 15:44:02 +1 15:44:03 +1 to close 15:44:05 +1 to close 15:44:09 +1 15:44:11 +1 15:44:14 +0 15:44:19 davidwood: seems agreement to close it, as rdf/xml wont never ever change 15:44:23 +1 to close with no change 15:44:31 +1 15:44:32 +0 15:44:41 +1 15:44:41 +1 close 15:44:44 +1 15:44:50 davidwood: correction: minor changes to rdf/xml might happen. sorry 15:45:04 ISSUE-45? 15:45:04 ISSUE-45 -- Revisit "The syntax needs a more convenient way to express the reification of a statement" -- raised 15:45:04 http://www.w3.org/2011/rdf-wg/track/issues/45 15:45:05 +1 close as a duplicate (on issue-25) 15:45:10 davidwood: ISSUE-44 closed 15:45:21 davidwod: next ISSUE-45 15:45:41 +1 15:45:41 +1, close a dup 15:45:43 +1 close as duplicate 15:45:45 +1 15:45:45 +1 15:45:45 +1 15:45:46 davidwood: ISSUE-45 is duplicate of ISSUE-25 => close it 15:45:48 +1 15:45:50 +1 close as duplicate 15:45:53 +1 15:45:56 davidwood: ISSUE-45 closed 15:46:04 ISSUE-46? 15:46:04 ISSUE-46 -- Revisit "Should RDF have a mechanism for declaring two uri's to be equivalent?" -- raised 15:46:04 http://www.w3.org/2011/rdf-wg/track/issues/46 15:46:07 -1 leave open for discussion later 15:46:08 davidwood: ISSUE-46 15:46:14 Sugfgest we keep this one open for now. 15:46:19 -0 leave open 15:46:27 davidwood: leave it open for next workshop 15:46:27 close, we have owl:sameAs 15:46:29 +0 15:46:36 close, we have owl:sameAs 15:46:43 +1 leave open 15:46:46 abstain 15:46:47 davidwood: enough DISagreement to leave this open 15:46:48 -0 15:46:58 0 leave open 15:46:59 ISSUE-47? 15:46:59 ISSUE-47 -- Revisit "RDF embedded in XHTML and other XML documents is hard to validate" -- raised 15:46:59 http://www.w3.org/2011/rdf-wg/track/issues/47 15:47:04 davidwood: ISSUE-47 15:47:08 +1/0 don't care 15:47:13 don't care 15:47:25 +1 to close 15:47:34 out of scope 15:47:35 +1 close 15:47:36 +1 to close 15:47:38 close, but with a better comment. 15:47:38 davidwood: no objections to close it 15:47:41 +1 15:47:41 +1 close 15:47:43 out of scope 15:47:47 does i tmean the RDF is hard to validate or the XML is? 15:47:48 davidwood: ISSUE-47 clsoed 15:47:54 +1 close 15:48:00 +1 close out of scope 15:48:01 davidwood: validation is out of scope of this wg 15:48:04 +1 close with validation out of scope 15:48:09 +1 "Close -- validation is out of scope for this WG" 15:48:18 +1 to close 15:48:23 listen to the worms... 15:48:27 ISSUE-48? 15:48:27 ISSUE-48 -- Revisit "The design of the RDF Model collection classes exhibit various awkward features. Might these be augmented with a 'better' design?" -- raised 15:48:27 http://www.w3.org/2011/rdf-wg/track/issues/48 15:48:34 davidwood: ISSUE-48 15:48:48 +0 15:48:57 davidwood: danbri marked this one as a duplicate 15:49:34 davidwood: proposal to close it as duplicate to ISSUE-24 15:49:39 +0 close as duplicate of Issue-24? 15:49:51 not a dup of 24 15:49:53 +q 15:50:05 andy: not a duplicate of ISSUE-24 15:50:12 andy: its about containers 15:50:22 ISSUE-48 is about collections 15:51:28 patH: couldnt follow, sorry 15:51:37 "The use of special property names (_1, _2, etc.) can really be quite awkward for expressing ordering. It means that it can be very difficult to add new members to a collection after the event" 15:51:42 ack PatH 15:51:49 path: seems to be a suggestion to put linked lists into rdf. done by the prev. wg 15:51:56 path: seems an archaic left-over 15:51:58 SteveH: is speaking now 15:52:07 steveh: not true 15:53:19 davidwood: want to continue this discussion on the list? 15:53:47 steveharris: lists of things done the wrong way twice 15:54:06 Anyone have ideas on making better lists? 15:54:10 path: close it and throw it away 15:54:12 +1 to path 15:54:16 +1 to PatH's dicideratum 15:54:24 +1 15:54:28 +1 15:54:29 +1 15:54:30 +1 15:54:30 davidwood: proposal to close ISSUE-48 as overcome by events. objections? 15:54:31 +1 15:54:31 +1 15:54:32 +1 15:54:33 +1 15:54:33 +1 15:54:33 +! 15:54:37 +1 15:54:42 +1 15:55:05 Add them as a first class data object, not encode in triples. Its the encoding (and possible mis-encoding) that cause some of the pain. 15:55:09 ISSUE-49? 15:55:09 ISSUE-49 -- Revisit "Should the subjects of RDF statements be allowed to be literals" -- raised 15:55:09 http://www.w3.org/2011/rdf-wg/track/issues/49 15:55:10 davidwood: ISSUE-48 closed 15:55:13 +1 to AndyS 15:55:34 would be nice to have it :) 15:55:35 ISSUE-49: literals as subjects cant be closed 15:55:35 ISSUE-49 Revisit "Should the subjects of RDF statements be allowed to be literals" notes added 15:55:35 q: could I create an RDF serialization with literal subjects and defer to the rdf semantics? 15:55:36 Andy: I agree, buit that goes way beyond issue-48. 15:55:55 davidwood: cant be considered closed 15:55:56 q+ 15:55:59 Yes, the semantics is fine iwth lieteral subjects. 15:56:05 with literal 15:56:09 andy: happy to postpone 15:56:10 ack AndyS 15:56:15 so it's in "rdf" but not in the official serializations 15:56:19 andy: rdf api allows literals as subjects 15:56:54 ivan: status of rdf api? first public working draft hopefully next week 15:57:06 There was a chorus of disapproval for literal subjects at the initial workshop, mostly from developers who didnt want to alter lagacy code. 15:57:08 davidwood: for the moment we cant do anything about it 15:57:09 it's now "rdf-interfaces" which contains it - rdf-api is a diff spec 15:57:15 legacy 15:57:18 +1 to continue 15:57:38 +1 to PatH - legacy is now a real issue (and that's good) 15:57:38 tomayac: rdf api is now rdf interfaces 15:57:41 literal as subjects doesn't seem very webbie to me, but anyways ... 15:57:52 ISSUE-50? 15:57:53 ISSUE-50 -- Revisit "Request to allow b-nodes as property labels" -- raised 15:57:53 http://www.w3.org/2011/rdf-wg/track/issues/50 15:58:00 davidwood: ISSUE-50 15:58:09 davidwood: out of charter 15:58:20 Sorry to go back, but I just noticed something about issue-42 that might be slightly important. The POWDER mechanism uses rdf:bag, which me therefor have to be careful not to deprecate. 15:58:37 rdf-interfaces again allows bnode predicates 15:59:06 davidwood: should we leave it open? or postpone? 15:59:17 FWIW< again the semantics is OK with bnode property labels, but some of the entailments might raise eyebrows. 15:59:20 are we goign to discuss further? if nto postpone 15:59:29 davidwood: ISSUE-50 postponed 15:59:34 +1 postpone 15:59:35 postpone please .... 15:59:37 +1 postpone 15:59:37 +1 to postpone 15:59:38 +1 to postpone 15:59:42 +1 15:59:42 COWARDS!! 15:59:43 +1 to postpone 15:59:44 +1 postpone 15:59:45 PatH, ty for confirmation, I don't mind raised eyebrows :) 15:59:45 +1 to postpone 15:59:45 +1 15:59:46 +1 15:59:47 +1 15:59:57 +1 to cowering in fear 16:00:29 RDF Interfaces :\ 16:00:37 as in rdf-interfaces has bnode properties and literal subjects 16:00:54 ivan: this issue is different than the previous one 16:01:11 RDF interface implementations will support it.. rdf semantics do to, serializations don't - doesn't matter, this is behind the "public interface" 16:01:15 ivan: you might have bnodes as predicates 16:01:19 +1 to what ivan is saying 16:01:28 +1 to Ivan 16:01:31 +1 to Ivan 16:01:54 ivan: there was a huge discussion in the rdf applications wg 16:01:57 This is a general issue, BTW, it also bears on literal subjects. 16:02:15 ivan: bnodes as predicates is good, because if not, implementations might have problems 16:02:29 s/is good/is good in APIs/ 16:02:44 the needs for serializing RDF are different to the needs for workign with RDF - we need to accept that generally 16:03:05 Is there a serialization API? 16:03:12 ivan: if it's for me, we can close this issue 16:03:58 It will damage the DL/Full boundary in OWL, for sure. 16:04:01 ivan: dont want to go down that route 16:04:03 AndyS, roughly the RDF API (end user focussed) will be more restricted to the convensional (matching serializations) 16:04:32 david: if we postpone it goes to a later wg 16:04:37 webr3, pointer? 16:04:59 q+ 16:05:03 AndyS, http://www.w3.org/2010/02/rdfa/sources/rdf-api/Overview.html 16:05:03 LOL 16:05:25 davidwood: we're postponing already, leaving leftovers, just like the previous wg did 16:05:31 can we address it properly, to say semantics allows X serializations are advised to allow Y (Reasons) then CLOSE ? 16:05:41 davidwood: if we close, we need to say why 16:06:04 webr3, pointer to serilization? I only see about parser using serialize 16:06:13 davidwood: saying it is out of scope is way different than closing 16:06:23 ivan: every wg may reopen closed issues 16:06:28 AndyS, you've confused me - you're looking for? 16:06:42 q? 16:06:52 Ivan, you read my mind... 16:06:52 ack zwu 16:07:15 Separate the issues! 16:07:17 zwu: how many people would truly object to have literals as subjects and bnodes as predicates 16:07:19 Garlik would object to both / either 16:07:22 A pointer to "roughly the RDF API (end user focussed) will be more restricted to the convensional (matching serializations)" 16:07:22 STRAWPOLL: Who would object to Liuteral Subjects 16:07:24 Quite possibly. 16:07:27 Im happy with literal subjects. 16:07:28 +0.5 16:07:32 zwu: straw poll, please 16:07:33 v happy with +1 16:07:44 I would possibly object to literal subjects - I have before 16:07:47 STRAWPOLL: Allow Literal Subjects 16:07:49 +1 16:07:50 +1 16:07:51 -1 16:07:52 +1 16:07:52 +1 16:07:52 -1 16:07:53 +1 16:07:53 -0.8 16:07:54 +1 16:07:54 -1 16:07:54 +1 16:07:56 +1 16:07:56 -0.5 16:08:00 -0.2 16:08:01 -1 16:08:05 -0 16:08:11 +0 16:08:11 ivan + me == 1 full objection! :-) 16:08:22 -1 16:08:25 Need to think more but quite possibility -1 (because the deployed system impact) 16:08:36 -1 16:08:40 zwu asked also for a straw poll on bnodes as predicates 16:08:59 STRAWPOLL; Allow bnodes as predicates 16:09:01 +1 16:09:01 +0 16:09:02 +1 16:09:02 -1 16:09:03 +1 16:09:03 +1 16:09:03 -1 16:09:04 -1 16:09:04 -1 16:09:06 -1 16:09:06 +1 16:09:06 -1 16:09:08 0 16:09:08 +0 16:09:08 -1 16:09:14 +1 16:09:14 -1 16:09:15 +0 16:09:25 -0.5 16:09:31 This is assuming that we have bnodes at all, of course. 16:09:43 zwu: one for the reasons are: if we are implementing an inference engine, it's way easier to allow, than disallow them 16:09:44 +1 to PatH 16:09:47 bnodes are useful in-process. they are nothing but trouble once you leave process. 16:09:48 We have bnodes, Pat :) 16:09:55 ivan: -1 because it would invalidate many things in owl 16:09:57 It depends what kind of inference engine uyou are tryuing to implement. 16:10:14 OWL-DL would prohibit it rigorously, so it would add a layer of checking to thier engines. 16:10:28 +1 to AndyS 16:10:30 +1 AndyS 16:10:33 +1 to andy 16:10:44 davidwood: back to ISSUE-50 16:10:47 +0.5 to AndyS ... sometimes it leaks 16:11:01 davidwood: open => discuss, close => out of scope, postponed: let others deal with it 16:11:10 if it's not an RDF WG level problem, who would it be a problem for? 16:11:11 gavinc, where??? and I'll stop that!!!!!! 16:11:14 it is not webby to serialise statements suchs as ` "42" _:bnode1 _bnode2 . ` 16:11:29 +1 leave raised 16:11:35 close 16:11:37 davidwood: significant disagreement 16:11:42 +1 postpone it 16:11:44 ivan: either close or postpone 16:11:46 suggest close 16:11:47 +1 leave raised 16:11:52 Its not in our charter, its a huge can of worms, it owuld screw up OWL (and probably RIF) relatkionships. Lets walk away from it. 16:12:00 +1 postpone 16:12:03 out of scope 16:12:17 +1 to postpone it 16:12:26 sorry guys i have to leave 16:12:29 SO, leave it open and ignore it. 16:12:30 davidwood: reads what people say on irc 16:12:34 (I'm saying to leave open/raised until there's good text to close it with or to clarify around the issue) 16:12:39 -mbrunati 16:12:42 I don't think postponing is good. What's the point? If people find this useful and implement it, then we can standardize it in the future. But what's the point in continuing to say "meh"? 16:13:16 just close it, a future group can open a new issue if it becomes desirable 16:13:21 davidwood: enough agreement to postpone 16:13:24 +1 SteveH 16:13:34 davidwood: correction: not enough agreement 16:13:35 +1 SteveH 16:13:37 I'm ok with opening it and then closing it, as well. 16:13:48 -1 to postponing it 16:13:52 -1 16:13:53 -1 16:13:53 STRAWPOLL: postpone issue 50 16:14:12 is an open issue like an open sore? 16:14:37 PatH, very very much so 16:14:57 davidwood: makes a chair decision to leave it raised. talk about it later 16:15:09 http://www.w3.org/2011/rdf-wg/track/issues/42 16:15:14 davidwood: pat raised a question on issue 42 16:15:33 path: rdf bag not much use 16:15:48 path: proposed to deprecate rdf bag 16:16:10 davidwood: thinks we still could deprecate 16:16:51 I thought we already excluded the deprecation of rdf:Bag as it was widely used in RSS 16:17:01 (vague memory of the F2F) 16:17:08 davidwood: out of time for this call 16:17:09 i recall that pchampin too 16:17:13 pchampin, yes 16:17:20 pcahmpin, good point. thnx. 16:17:20 davidwood: remaining issues => later call 16:17:26 davidwood: AOB? 16:17:33 -[IPcaller] 16:17:34 -Souri 16:17:35 davidwood: call adjourned 16:17:36 bye 16:17:36 would be nice to have the next f2f sorted 16:17:36 -sandro 16:17:37 -[Garlik] 16:17:37 ivan, to handle that issue we discussed. 16:17:37 -cmatheus 16:17:39 -AlexHall 16:17:39 doh 16:17:41 bye all 16:17:41 -MacTed 16:17:43 -OlivierCorby 16:17:43 -zwu2 16:17:45 -PatH 16:17:46 -gavinc 16:17:50 -Russell 16:17:51 -Scott 16:17:57 AlexHall has left #rdf-wg 16:18:22 webr3 - I see nothing about serialization 16:19:09 rrsagent, make minutes 16:19:09 I have made the request to generate http://www.w3.org/2011/05/04-rdf-wg-minutes.html pchampin 16:19:15 tomayac: You can edit http://www.w3.org/2011/rdf-wg/meeting/2011-05-04 via the wiki once they are generated 16:19:23 http://www.w3.org/2009/CommonScribe/manual 16:19:55 http://www.w3.org/2009/CommonScribe/panel/ 16:20:03 -AndyS 16:21:35 -FabGandon 16:21:44 FabGandon has left #rdf-wg 16:25:01 -tomayac 16:26:45 -Ivan 16:26:46 -davidwood 16:27:06 zakim, who is here? 16:27:06 On the phone I see EricP, LeeF, pchampin 16:27:07 -LeeF 16:27:28 pchampin has left #rdf-wg 16:27:28 -pchampin 16:28:03 eric, are you having a nice conversation with yourself on zakim? 16:35:01 disconnecting the lone participant, EricP, in SW_RDFWG()11:00AM 16:35:02 SW_RDFWG()11:00AM has ended 16:35:06 Attendees were +1.707.861.aaaa, gavinc, Ivan, Scott, +1.404.978.aabb, tomayac, AndyS, +33.4.92.38.aacc, OlivierCorby, +1.540.898.aadd, davidwood, EricP, mbrunati, LeeF, MacTed, 16:35:09 ... PatH, Souri, sandro, FabGandon, AlexHall, pchampin, Russell, mischat, Russel?, zwu2, cmatheus, SteveH, AZ, [IPcaller] 16:38:31 Please send an email to w3C Chairs of the RDF WG asking for permissions. Either Ivan or Sandro will need to help you. 16:40:24 np 16:42:58 tomayac, can you see w3.org/Member ? 16:43:15 yes 16:43:33 but the irc log wiki is not editable for me, all other wikis so far were 16:43:45 other pages on this wiki are? 16:43:53 yepp 16:44:24 no i can edit 16:44:37 ? 16:44:39 funny. i swear i couldnt a minute ago 16:44:58 well, I'll take full credit for fixing it, then. :-) 16:45:06 (not that I did anything) 16:46:33 Thanks again for scribing, Thomas. 16:49:18 mischat has joined #rdf-wg 18:40:54 Zakim has left #rdf-wg 18:46:54 MacTed, would you be able to leverage the Virtuoso L.O.D. cloud to run a couple of analytics about the prevalence (or lack thereof) of xsd:string literals in LOD? I'm curious whether we (Cam Semantics) are the only people using them with some regularity :) 19:00:21 tomayac has joined #rdf-wg