14:30:50 RRSAgent has joined #dawg 14:30:56 TomAdams, ready to serve as scribe? 14:31:02 Sure. 14:31:04 +DanC 14:31:06 Just about to call in. 14:31:17 +PatH 14:31:22 KevinW has joined #DAWG 14:31:48 patH has joined #dawg 14:31:51 Zakim, who's on the phone? 14:31:51 On the phone I see SteveH, Kevin, ??P18, EricP, DanC, PatH 14:31:55 +[Tucana] 14:31:56 AlbertoR has joined #dawg 14:32:02 zakim, Tucana is TomAdams 14:32:02 +TomAdams; got it 14:32:09 +Farrukh 14:32:14 Zakim, who's on the phone? 14:32:14 On the phone I see SteveH, Kevin, ??P18, EricP, DanC, PatH, TomAdams, Farrukh 14:32:36 +AlbertoR 14:33:01 Regrets: Andy Seaborne, Hiroyuki Sato, Janne, ... 14:33:14 Regrets: Andy Seaborne, Hiroyuki Sato, Janne, Hiroyuki Sato, ... 14:33:15 Regrets from Kendall as well. 14:33:24 Regrets: Andy Seaborne, Hiroyuki Sato, Janne, Kendall Clark, ... 14:33:48 JosD has joined #dawg 14:33:48 partial regrets: alberto 14:34:20 Zakim, who's on the phone? 14:34:20 On the phone I see SteveH, Kevin, SimonR, EricP, DanC, PatH, TomAdams, Farrukh, AlbertoR 14:34:26 I may have to leave a little early this week. 14:35:11 +??P10 14:35:24 Zakim, ??P10 is DaveB 14:35:24 +DaveB; got it 14:35:34 +??P26 14:35:38 Dave seconded minutes 14:35:47 Zakim, ??P26 is JosD 14:35:47 +JosD; got it 14:35:48 RESOLVED to accept minutes of last meeting 14:35:59 Next meeting Tuesday Oct 26 14:36:21 possibly scribe next week 14:36:28 Correction, November 2 for next meeting 14:36:32 good to have backup eventually 14:36:41 Scribe: Alberto 14:37:00 DaveB has joined #dawg 14:38:01 Eric P, discussed next F2f meeting 14:38:06 Continuing action 14:38:17 ericp requested mon/tue 14:38:28 danc has a conflict monday with TAG 14:38:33 Zakim, next agendum 14:38:33 agendum 1. "Convene, take roll, review record and agenda http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0173.html" taken up [from DanC] 14:38:37 i sent the request reciept to the list 14:38:38 Zakim, close agendum 1 14:38:38 agendum 1 closed 14:38:39 I see 4 items remaining on the agenda; the next one is 14:38:40 2. Web Services Constraints and Capabilities [from DanC] 14:38:41 Zakim, next agendum 14:38:41 agendum 1 was just opened, DanC 14:38:47 Zakim, take up agendum 2 14:38:47 agendum 2. "Web Services Constraints and Capabilities" taken up [from DanC] 14:39:09 http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0145.html 14:39:15 . ACTION EricP: draft UC on overlap between RDF query and web service constraints with respect to WS-Policy 14:39:30 Eric wrote something up, cited example, unsure of expressivity 14:39:35 http://www.w3.org/2004/08/20-ws-pol-pos/#query 14:39:50 <-- example query for web services constraints 14:40:09 written by ericp (page is unsigned) 14:41:11 Matrix is familiar to WS policy people. 14:42:48 Expressing what you need to use our web server, must use a security token, X509, etc. Expressed as simple value disjunction for this use case. Not all use cases being kicked around in meeting can be covered by value disjunction. 14:43:21 replace with ... { ?assertion wss:tokentype ?t} AND (t = "wsse:Kerberosv5TGT" or ?t = "wsse:X509v3" ) 14:43:28 ^- value disjunction 14:43:28 simple disjunction as motivated by http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2004Sep/0000.html use case 14:43:33 Other used case: You need X509 or (SSL and basic auth) 14:43:46 q+ to re-ask my question in agenda 14:44:16 ack dave 14:44:16 DaveB, you wanted to re-ask my question in agenda 14:44:38 (which WG, DaveB?) 14:44:38 Quick straw poll conducted on whether to stick this into use cases. 6 came back in the affirmative. 14:44:50 ws-policy ppl 14:45:04 (so you're using "decided" in a liberal sense?) 14:45:25 DaveB asked a question of Eric last week on the decisions of the ws-policy WG. 14:45:34 there is no ws-policy WG 14:45:49 s/WG/ppl 14:45:54 DaveB, If they stopped at disjunction, why did they? 14:46:18 I heard eric say they were about 50/50 for adding/not adding disjunction 14:46:44 Quick straw poll on not bothering, 2 people. 14:46:52 To include in the use cases. 14:47:28 Dave and Steve suggest that we have enough use cases. 14:47:51 ACTION: Eric to ask Kendall to put use case into UC&R 14:48:16 Zakim, next agendum 14:48:16 agendum 3. "Feedback on the SPARQL design" taken up [from DanC] 14:48:24 ACTION 1=Eric to ask Kendall to put use case into UC&R or find a use case that covers it 14:48:57 note: http://www.w3.org/2001/sw/DataAccess/issues#disjunction 14:49:20 agenda + disjunction issues 14:49:38 Steve heard the comment, added to agenda. 14:49:55 ref to steveH's proposal on disjunction http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0604.html 14:50:21 Eric acting as editor on Andy's behalf 14:50:28 http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0160.html 14:51:02 Zakim, who's on the phone? 14:51:02 On the phone I see SteveH, Kevin, SimonR, EricP, DanC, PatH, TomAdams, Farrukh, AlbertoR, DaveB, JosD 14:51:20 SteveH, No pref 14:51:27 KevinW, no pref 14:51:28 ref to my comment on CNF: http://lists.w3.org/Archives/Public/public-rdf-dawg/2004JulSep/0604.html 14:51:56 SimonR, no particular required prefix character, $, ?, :. 14:52:13 DanC, No pref 14:52:15 sorry... http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0047.html 14:52:16 patH, $ 14:52:46 Specifically, I liked the suggestion where there was no required prefix character. And identifier that wasn't a qname (i.e. no colon) would be a variable. 14:52:48 patH, Suggest a design in which the user declares the character, but has a default, which i $ 14:52:51 TomAdams, $ 14:52:57 FarrukhNajmi, $ 14:52:58 And -> Any 14:53:07 AlbertoR, $ 14:53:20 DaveB, $ 14:53:25 JosD, $ 14:53:32 JosD was ? 14:53:38 indeed 14:53:51 JosD, ? (correction) 14:54:11 ericP, Sensed the way the wind is blowing and changed to $ 14:54:19 I agree with Farrukh about having either one or the other, at least. 14:55:09 can live with both - but preference (best practice) is $ 14:55:21 I sort of prefer $ because it's more like XPath/XQuery/XSLT. 14:55:38 . ACTION: PatH review SPARQL def'ns post-publication 14:55:41 DanC, Will leave as input to editor, update as they see fit. 14:56:00 patH, Thought it was on hold, will do it this week. 14:56:25 DanC, Pat to work on editors draft 14:56:34 editor's draft http://www.w3.org/2001/sw/DataAccess/rq23/ 14:56:53 Pat's action cont 14:57:10 Dan sent defns for select, editor didn't read them... 14:57:26 definitions for SELECT, projection http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0151.html 14:57:45 Zakim, next agendum 14:57:45 agendum 4. "PREFIX syntax" taken up [from DanC] 14:58:16 Dave's action complete. 14:59:06 DanC, Thinks we should make the language smaller. 14:59:06 +q 14:59:10 q+ 14:59:28 example http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0161.html 14:59:34 proposal http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0164.html 15:00:20 AlbertoR, Didn't digest grammar, like proposal, is this related to serialisation of results 15:00:21 ? 15:00:38 DaveB, Not aware of relation to result 15:01:13 wondered if the proposal/solution would cover things like select ?prefix:var ?prefix:var1 15:01:27 ericP's position on the three-part proposal: +1 -2 +3 15:02:07 Simon is for just doing prefixing at the beginning 15:04:02 (hmm... why did I make prefix syntax a WG issue and not other syntax details? chairing error.) 15:04:57 Eric P gave his decision, accpt 1 and 3, but not 2 15:05:14 Now that I've read 164, I'd support part 1 and 3, but not 2. 2 is a special case which changes the consistent rule elsewhere that qnames and URIs are interchangeable. 15:05:37 +1 to EricP's position, as I understand it. 15:06:26 Dan to leave this as a he who does the work writes the rule, is suggesting a use case 15:06:27 Zakim, next agendum 15:06:27 agendum 5. "Toward adopting some tests" taken up [from DanC] 15:07:03 If $ is chaging, all the tests are unapprovable 15:07:08 ? is changing 15:07:09 http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0176.html 15:07:34 is about some SOURCE tests details - i.e. my experience while running tests 15:09:16 me too - I have the machinery in place - it does not do OPTIONAL though - results are checked "manually" to - but could use some propose isomorphism utility 15:09:54 DanC walsk through item 5, looking at dawg-triple-pattern-001 15:10:12 daveb has run it. steveh has translated to rdql and run it. josH has done similar ot n3 15:10:56 and Alberto is about to run some simple tests (a part the SOURCE ones) - but OPTIONAL ones 15:11:12 DaveB, Not redundant if you have optional triples 15:12:17 DanC will think about results for optional triples 15:13:56 ?? Not happy with result format, does p come before q? 15:14:15 does SQL / ER models "demand" order on columns? not sure... 15:14:24 "query results are a set of pattern solutions." -- sec 2, SPARQL paragraph 2 15:14:35 SimonR, There is no order specified, so the ordering does not matter in this case. 15:14:56 ?? Sometimes order matters, such as in XSLT 15:15:18 http://www.w3.org/2001/sw/DataAccess/rq23/#MultipleMatches 15:15:19 DanC, Suggests that the protocol does this, not SPARQL 15:15:44 right - but XSLT is already outside the SPARQL protocol stack I expect...good to sort RDF-for-XML syntax for example (we do that actually) 15:16:41 A pattern solution is a set of bindings (no order), the results is a set of query solns 15:16:56 The order of a given row is not order, the order of the rows is not ordered 15:17:04 DanC, points to section 8 15:17:18 http://www.w3.org/2001/sw/DataAccess/rq23/#choosing 15:18:01 Correction: http://www.w3.org/2001/sw/DataAccess/rq23/#select 15:18:12 "Results can be thought of as a table, with one row per query solution. Some cells may be empty because a variable is not bound in that particular solution." 15:18:20 yes - I can read (and implemented) un-order result sets (rows or columns) - just a set of results 15:18:34 SimonR, Have redefined "results" 15:18:47 q+ 15:19:50 Simon is encouraged to look at wording and defn 15:20:14 AlbertoR, References earlier comment. 15:20:45 AlbertoR, Need to spell out clearly that we don't support ordering. 15:21:12 DanC, Expects result format to be in the protocol level, would expect results to be deterministic 15:21:41 DanC makes comments that for protocol format, columns are ordered lexigraphically 15:21:53 DanC, Rows are a separate issue. 15:22:26 q+ to talk about rs:size and graph match 15:22:45 DanC, Asks Steve about taking size out of result format 15:23:20 ACTION SteveH: take rs:size out of expected results from all tests 15:24:12 ACTION EricP: supply definitions for SELECT (vars ordered or not?) ala http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0151.html 15:24:13 SimonR has joined #dawg 15:24:35 ericP, Points on barrier between protocol and query language. 15:25:03 ericP, QL specifies select, gives them back in order specified, rows separate issue. 15:25:34 ericP, In terms of getting information fro QL spec to protocol spec, can the protocol spec peak into the QL? 15:25:54 DanC, See similar issues, wants to see what Eric comes up with 15:26:46 ericP, Talking about removing the number of rows. If you remove the number of rows and do a graph compare between an implementation and that defined in the spec, if you don't have a distinct, won't be able to automatically merge the tuples that have the same binding. 15:27:12 ericP, May be able to do it with a rule, but not tailored to the result set. 15:28:18 DanC, The merged example graphs (texas) are isomrphic 15:28:39 s/isomrphic/isomorphic 15:29:41 ??: Graph are logically equivalent 15:30:17 foo rs:result [ rs:variable "where"; rs:value "Texas"]; 15:30:26 rs:result [ rs:variable "where"; rs:value "Boston"]; 15:30:33 rs:result [ rs:variable "where"; rs:value "Texas"]. 15:30:39 compare to: 15:30:46 foo rs:result [ rs:variable "where"; rs:value "Boston"]; 15:30:49 rs:result [ rs:variable "where"; rs:value "Texas"]. 15:30:50 . 15:32:10 patH says they are not isomorphic, but are logically equivalent 15:32:17 (rdf-entailed I guess) 15:32:27 -AlbertoR 15:32:28 -PatH 15:32:43 ADJOURN. 15:32:48 -DaveB 15:32:48 Meeting adjourned 15:32:55 -Farrukh 15:32:56 -JosD 15:35:47 Bye all! Have fun ;) 15:35:49 -TomAdams 15:36:33 KevinW has left #DAWG 15:37:02 -Kevin 15:37:55 Zakim, make logs world-access 15:37:55 I don't understand 'make logs world-access', DanC 15:38:21 bye 15:38:24 -SteveH 15:39:15 zakim, list attendees 15:39:15 As of this point the attendees have been SteveH, Kevin, EricP, DanC, PatH, [Tucana], TomAdams, Farrukh, SimonR, AlbertoR, DaveB, JosD 15:41:00 -SimonR 15:41:05 RRSAgent, make logs world-access 15:41:10 RRSAgent, bye 15:41:10 I see 3 open action items: 15:41:10 ACTION: Eric to ask Kendall to put use case into UC&R or find a use case that covers it [1] 15:41:10 recorded in http://www.w3.org/2004/10/26-dawg-irc#T14-47-51 15:41:10 ACTION: SteveH to take rs:size out of expected results from all tests [2] 15:41:10 recorded in http://www.w3.org/2004/10/26-dawg-irc#T15-23-20 15:41:10 ACTION: EricP to supply definitions for SELECT (vars ordered or not?) ala http://lists.w3.org/Archives/Public/public-rdf-dawg/2004OctDec/0151.html [3] 15:41:10 recorded in http://www.w3.org/2004/10/26-dawg-irc#T15-24-12