14:23:08 RRSAgent has joined #dawg 14:23:08 logging to http://www.w3.org/2007/05/01-dawg-irc 14:23:13 zakim, this will be DAWG 14:23:13 ok, LeeF; I see SW_DAWG()10:30AM scheduled to start in 7 minutes 14:23:23 Meeting: RDF Data Access Weekly 14:23:27 Agenda: http://lists.w3.org/Archives/Public/public-rdf-dawg/2007AprJun/0033.html 14:23:33 Ref: http://rfc.net/rfc3987.html#s3. 14:23:39 LeeF has changed the topic to: RDF Data Access Working Group - Agenda: http://lists.w3.org/Archives/Public/public-rdf-dawg/2007AprJun/0033.html 14:23:45 Chair: LeeF 14:23:49 Scribe: jeen 14:23:51 Regrets: 14:23:58 agenda + convene 14:24:00 agenda + action items 14:24:10 agenda + leading digits in prefixed names 14:24:22 agenda + non-URI characters in IRIs 14:24:26 better: http://rfc.net/rfc3987.html#s3.1. just before 3.2 14:24:41 agenda + Last Call comments status / CR status 14:24:50 agenda + ordered, distinct, and reduced attributes in SPARQL XML Results Format 14:29:00 SimonR has joined #dawg 14:29:56 SW_DAWG()10:30AM has now started 14:30:03 +??P17 14:30:06 +??P18 14:30:09 zakim, ??P17 is me 14:30:09 +AndyS; got it 14:30:11 Zakim, ??P17 is me 14:30:11 I already had ??P17 as AndyS, SimonR 14:30:37 zakim, ??P18 is me 14:30:37 +AndyS; got it 14:30:52 zakim, mute SimonR 14:30:52 sorry, AndyS, I do not know which phone connection belongs to SimonR 14:30:54 Zakim, ??P17 is me 14:30:54 I already had ??P17 as AndyS, SimonR 14:31:05 chimezie has joined #dawg 14:31:13 +??P19 14:31:16 Zakim, ??P19 is me 14:31:16 +jeen; got it 14:31:21 +[IBMCambridge] 14:31:25 zakim, IBMCambridge is me 14:31:25 +LeeF; got it 14:31:26 +Chimezie_Ogbuji 14:31:42 zakim, who's here? 14:31:42 On the phone I see AndyS, AndyS.a, jeen, LeeF, Chimezie_Ogbuji 14:31:44 On IRC I see chimezie, SimonR, RRSAgent, Zakim, AndyS, jeen, LeeF, PvK, afs, SteveH, iv_an_ru, ericP 14:32:23 PvK has left #dawg 14:32:38 zakim, AndyS.a is SimonR 14:32:38 +SimonR; got it 14:32:53 ericP, you coming along? 14:33:21 agenda? 14:34:45 zakim, take up next agendum 14:34:45 agendum 1. "convene" taken up [from LeeF] 14:34:49 Zakim, please dial ericP-office 14:34:49 ok, ericP; the call is being made 14:34:51 +EricP 14:35:05 minutes from 24 Apr -> http://www.w3.org/2007/04/24-dawg-minutes.html 14:35:30 minutes approved, seconded by jeen 14:35:58 Off topic: Jooset launch: RDF in action! http://news.bbc.co.uk/1/hi/business/6612199.stm 14:36:10 s/Jooset/Joost/ 14:36:34 next meeting, 8 May, scribe @@ 14:36:51 zakim, close this agendum 14:36:51 agendum 1 closed 14:36:52 I see 5 items remaining on the agenda; the next one is 14:36:53 2. action items [from LeeF] 14:36:54 zakim, take up next agendum 14:36:54 agendum 2. "action items" taken up [from LeeF] 14:37:03 ACTION: ericP to respond to Jeremy Carroll's comments re: langMatches [DONE] 14:37:09 ACTION: ericP to respond http://www.w3.org/mid/4617D68D.4010608@hp.com [DONE] 14:37:19 ACTION: EricP to run the yacker tool over and annotate the existing tests [CONTINUES] 14:37:25 + +1.603.897.aaaa 14:37:30 ACTION: ericP to get in touch with SteveH re: setting up an environment to generate an Overview page for tests in data-r2 a la http://www.w3.org/2001/sw/DataAccess/tests/ [CONTINUES] 14:37:48 ACTION: ericP, jeen, or LeeF to update http://www.w3.org/2001/sw/DataAccess/tests/README with info on possible results format and on changes to manifest and test vocabularies [CONTINUES] 14:38:00 ACTION: ericP to write a test showing that langMatches doens't do extended matching [CONTINUES] 14:38:09 ACTION: LeeF or EliasT to reply to Bjoern regarding (not) POSTing application/sparql-query documents [CONTINUES] 14:38:23 ACTION: LeeF or EliasT to reply to Bjoern regarding (not) POSTing application/sparql-query documents [CONTINUES[ 14:38:32 ACTION: LeeF to mark the 4 regex tests approved [CONTINUES] 14:39:09 zakim, close this agendum 14:39:09 agendum 2 closed 14:39:11 I see 4 items remaining on the agenda; the next one is 14:39:12 mzakim, take up next agendudm 14:39:14 3. leading digits in prefixed names [from LeeF] 14:39:16 zakim, take up next agendudm 14:39:16 I don't understand 'take up next agendudm', LeeF 14:39:16 zakim, aaaa is Souri 14:39:17 +Souri; got it 14:39:21 zakim, take up next agendum 14:39:21 agendum 3. "leading digits in prefixed names" taken up [from LeeF] 14:39:47 LeeF: discussed this last week, consensus seems no technical objections against allowing 14:39:49 I do have a technical reason against it. 14:40:11 Souri has joined #dawg 14:40:29 ... I was going to check whether this would be substantive enough to need a new LC 14:41:19 SimonR: I did have a technical objection, you can put it in a construct and thus produce something which is not a legal XML QName in your output graph 14:41:35 i don't see how expanding 'qname' lexical form will be problematic for serializing RDF/XML 14:41:46 via CONSTRUCT 14:42:16 EricP: if the data is there in the first place, it can already occur in the output of a query, so we are not introducing a _new_ problem. 14:42:19 Example: x:0123 becomes as a property which is not qname-able in RDF/XML. 14:42:59 ahh, thx 14:43:06 SimonR: I'd be inclined not to change the spec and be conservative. but the world won't fall if we do allow this. 14:43:30 Can do it in other ways - this makes it a bit easier to do. 14:43:55 LeeF: EricP talked to Ralf (and Tim). according to him it is a substantive change. 14:44:35 s/Ralf/Ralph 14:44:38 ... but we could mark it as 'at risk', reserving the right to remove in PR if we want. 14:45:15 zakim, who's on the phone? 14:45:15 On the phone I see AndyS, SimonR, jeen, LeeF, Chimezie_Ogbuji, EricP, Souri 14:45:25 AndyS: neutral 14:45:31 SimonR: do nothing 14:46:07 jeen: neutral 14:46:23 chimezie: add it at-risk 14:46:28 ericP: add it at-risk 14:46:52 Souri: add it at-risk 14:49:31 SimonR: can we explain in the spec why it is at risk? 14:49:49 LeeF: we have no obligation to do that, at least. 14:50:18 PROPOSED: To accept leading digits in the local part of a prefixed name and mark this as a feature at-risk in the sepcification 14:50:48 seconded by AndyS 14:50:52 so resolved. 14:50:59 RESOLVED, no abstentions 14:51:30 I'm willing to write some text explaining the issues around leading digis. 14:51:40 ACTION: SimonR to write text explaining the leading digits at-risk feature 14:52:07 ACTION: AndyS to update the grammar for leading digits 14:52:26 ACTION: chimezie to write up a test case showing leading digits in local part of prefixed names 14:53:55 zakim, close this agendum 14:53:55 agendum 3 closed 14:53:56 I see 3 items remaining on the agenda; the next one is 14:53:58 4. non-URI characters in IRIs [from LeeF] 14:53:58 zakim, take up next agendum 14:53:58 agendum 4. "non-URI characters in IRIs" taken up [from LeeF] 14:54:38 issue inspired by comments in http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2007Apr/0007.html 14:54:39 Do we have a way in the test suite to express an "at risk" feature? I'm presuming at the moment our tests are supposed to either succeed or fail. Do we have any marked to only work in the case of a optional feature? (Exntailment regimes, user-defined functions, etc?) 14:55:03 -> http://rfc.net/rfc3987.html#s3.1. 14:55:34 i *think* the current test suite uses 'vanilla' RDF test vocabulary, so I don't think so (currently) 14:55:47 simon, i don't we do 14:56:28 Okay, so there might be some test suite framework extension required, as well as writing the tests themselves. 14:57:36 IRI specification includes certain characters which would cause conflicts in our grammar (< for instance) 14:58:27 AndyS: in favor of maximizing interoperability by keeping out that excluded-char list 14:58:30 (correct? 14:58:31 ) 14:58:55 Example: seems to be a legal IRI but not a URI. 15:00:31 Is RDF core officially using IRIs yet? (Probably a silly question, but I might as well ask.) 15:00:58 -AndyS 15:01:14 LeeF: my inclinination would be to stick to as close as what we have right now, and keep the exclusion list 15:01:38 SimonR, we seem to have lost you (under the guise of AndyS) 15:01:38 RDF core is not using IRIs because it predates RFC 3987 15:01:45 zakim, SimonR is AndyS 15:01:45 +AndyS; got it 15:02:27 Souri: also in favor of sticking with as-is 15:03:38 if there is no technical pushback is seems prudent to go in teh IRI direction 15:03:50 as this seems to be the general consensus direction 15:03:56 zakim, who's on the phone? 15:03:56 On the phone I see AndyS, jeen, LeeF, Chimezie_Ogbuji, EricP, Souri 15:04:02 s/is/it 15:05:12 +??P37 15:05:18 Zakim, ??P37 is me 15:05:18 +SimonR; got it 15:05:33 jeen: not sure about changing this without taking a good look at consequences for current parsers first. 15:05:54 Chimezie - just an observation - the arg could be to go for the most conservative as well. This is tricky. 15:06:39 yes, the uncertainty for me is mainly what hiccups (if any) it introduces 15:07:40 You know, if we delimited our prefixed named with <> and left IRIs delimited by whitespace, we might dodge this. Probably to confusing to consider, but <> would be no issue for pseudo-XML characters. 15:07:49 to/too 15:08:30 Jeen - SeRQL uses {} for delims doesn't it? 15:09:29 Andy - delims around subject and object (i.e. graph nodes as opposed to edges) . uris are delimited with <> same as in SPARQL 15:09:55 Jeen - thanks 15:10:02 What are the characters? <,>,{,}, space, ... 15:10:33 I see 2 items remaining on the agenda; the next one is 15:10:34 5. Last Call comments status / CR status [from LeeF] 15:10:35 zakim, take up next agendum 15:10:35 agendum 5. "Last Call comments status / CR status" taken up [from LeeF] 15:10:42 agenda? 15:11:01 -> http://www.w3.org/2001/sw/DataAccess/lc-status-report.html somewhat accurate comment report 15:11:02 Souri: "<", ">", '"', space, "{", "}", "|", "\", "^", and "`" 15:11:24 Thanks Andy. 15:11:25 (from RFC 3987 near end sec 3.1) 15:14:55 -> http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2007Apr/0027.html #2 has been fixed, #3 is a question, #1 is mainly a question 15:15:49 -SimonR 15:16:23 LeeF: we have pretty much addressed all the LC comments (only have to send one more reply) 15:16:44 LeeF: still hoping to move to CR next week 15:18:36 (we have some heavy winds on the line it seems) 15:19:08 LeeF: I will go through old objections and summarize their status 15:19:09 zakim, close this agendum 15:19:09 agendum 5 closed 15:19:10 I see 1 item remaining on the agenda: 15:19:11 6. ordered, distinct, and reduced attributes in SPARQL XML Results Format [from LeeF] 15:19:14 zakim, next agendum please 15:19:14 agendum 6. "ordered, distinct, and reduced attributes in SPARQL XML Results Format" taken up [from LeeF] 15:19:40 -> http://lists.w3.org/Archives/Public/public-rdf-dawg/2007AprJun/0031.html attributes in results format 15:20:40 LeeF: question on whether we need additional reduced attribute in XML format triggered discussion on under-specification on meaning of distinct attribute 15:21:14 ... so the broader question is whether we need a reduced keyword and whether we need to keep the distinct and ordered keywords in the result format? 15:21:18 my vote: wipe them all out 15:22:00 Is anyone in favor of keeping the distinct= and ordered= attributes? 15:22:11 I too favor removing them 15:22:14 zakim, who's on the phone? 15:22:14 On the phone I see AndyS, jeen, LeeF, Chimezie_Ogbuji, EricP, Souri 15:22:47 Chimezie: I'm in favor of removing as well 15:23:05 LeeF: we seem to have consensus on this 15:24:43 PROPOSED: To remove the ordered= and distinct= attributes from the SPARQL Query Results XML Format 15:24:55 second by jeen and andy 15:25:08 RESOLVED, no abstentions or objections 15:25:20 ACTION: jeen to remove ordered and distinct attributes from the query results xml format editors' draft 15:25:44 ADJOURNED 15:25:51 -Chimezie_Ogbuji 15:25:56 -LeeF 15:25:57 -EricP 15:26:01 -Souri 15:26:04 Zakim, bye 15:26:04 leaving. As of this point the attendees were AndyS, jeen, LeeF, Chimezie_Ogbuji, EricP, +1.603.897.aaaa, Souri, SimonR 15:26:04 Zakim has left #dawg 15:26:14 RRSAgent, draft minutes 15:26:14 I have made the request to generate http://www.w3.org/2007/05/01-dawg-minutes.html jeen 15:26:37 RRSAgent, bye 15:28:45 rrsagent, make minutes world-readable 15:28:45 I'm logging. I don't understand 'make minutes world-readable', AndyS. Try /msg RRSAgent help 15:28:48 RRSAgent, make logs world-access 15:29:31 rrsagent, please leave 15:29:31 I see 13 open action items saved in http://www.w3.org/2007/05/01-dawg-actions.rdf : 15:29:31 ACTION: ericP to respond to Jeremy Carroll's comments re: langMatches [DONE] [1] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T14-37-03 15:29:31 ACTION: ericP to respond http://www.w3.org/mid/4617D68D.4010608@hp.com [DONE] [2] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T14-37-09 15:29:31 ACTION: EricP to run the yacker tool over and annotate the existing tests [CONTINUES] [3] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T14-37-19 15:29:31 ACTION: ericP to get in touch with SteveH re: setting up an environment to generate an Overview page for tests in data-r2 a la http://www.w3.org/2001/sw/DataAccess/tests/ [CONTINUES] [4] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T14-37-30 15:29:31 ACTION: ericP, jeen, or LeeF to update http://www.w3.org/2001/sw/DataAccess/tests/README with info on possible results format and on changes to manifest and test vocabularies [CONTINUES] [5] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T14-37-48 15:29:31 ACTION: ericP to write a test showing that langMatches doens't do extended matching [CONTINUES] [6] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T14-38-00 15:29:31 ACTION: LeeF or EliasT to reply to Bjoern regarding (not) POSTing application/sparql-query documents [CONTINUES] [7] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T14-38-09 15:29:31 ACTION: LeeF or EliasT to reply to Bjoern regarding (not) POSTing application/sparql-query documents [CONTINUES[ [8] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T14-38-23 15:29:31 ACTION: LeeF to mark the 4 regex tests approved [CONTINUES] [9] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T14-38-32 15:29:31 ACTION: SimonR to write text explaining the leading digits at-risk feature [10] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T14-51-40 15:29:31 ACTION: AndyS to update the grammar for leading digits [11] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T14-52-07 15:29:31 ACTION: chimezie to write up a test case showing leading digits in local part of prefixed names [12] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T14-52-26 15:29:31 ACTION: jeen to remove ordered and distinct attributes from the query results xml format editors' draft [13] 15:29:31 recorded in http://www.w3.org/2007/05/01-dawg-irc#T15-25-20 15:29:38 zakim, leave