14:25:38 RRSAgent has joined #dawg 14:25:44 yoshio, stay on, please! 14:25:46 have we started, or what? 14:25:49 else Zakim will lose its marbles 14:25:54 we're scheduled to start in 5min 14:26:00 ok - coming back on now. 14:26:00 ok, 5 min 14:26:05 +BryanT 14:26:26 rob_ has joined #dawg 14:26:32 mornin, rob! 14:26:46 what's the number to dial in? 14:27:10 +1.617.761.6200 per http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0212.html 14:27:20 conference 7333 ("RDFD") 14:27:22 * what has happened to Zakim? calling me 5 min. earlier 14:27:30 KevinW has joined #DAWG 14:27:49 + +1.760.476.aaaa 14:27:53 +DanC 14:28:15 -DanC 14:28:19 +DanC 14:28:25 +Kendall_Clark 14:28:26 JeffB has joined #dawg 14:28:53 Zakim, aaaa is rob_ 14:28:54 +NickG 14:28:55 +rob_; got it 14:29:11 Zakim, NickG is temporarily SteveH 14:29:12 +SteveH; got it 14:29:14 +EricP 14:29:18 +??P34 14:29:20 howardk has joined #dawg 14:29:26 zakim, ??P34 is AndyS 14:29:26 +AndyS; got it 14:29:39 +PatH 14:29:57 +Kevin 14:30:04 ericP: i moved the images to not float:right and boxed them; but getting an annoying href artifact that i'm hating. :> 14:30:12 -EricP 14:30:25 +HowardK 14:30:35 +EricP 14:30:36 Zakim, take up agendum 1 14:30:39 agendum 1. "Convene, take roll, review agenda (http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0212.html) and misc actions" taken up [from DanC_] 14:30:45 Zakim, who's on the phone? 14:30:45 On the phone I see HowardK, Yoshio, BryanT, rob_, DanC, Kendall_Clark, SteveH, EricP, AndyS, PatH, Kevin 14:30:58 +Tayeb 14:31:03 kendall, the svg link href? 14:31:18 + +1.781.454.aabb 14:31:22 ericp: yes 14:31:37 Zakim, aabb is Farrukh 14:31:37 +Farrukh; got it 14:32:34 jean francois is Tayeb? 14:32:34 regrets: Dirk, Alberto 14:32:45 Zakim, Tayeb is JeffB 14:32:45 +JeffB; got it 14:33:06 ACTION DanC: inform the TAG of the conflict between sec13.9 of the HTTP 14:33:06 spec and TAG's recommendation on issue 7 14:33:41 http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0212.html 14:34:24 Zakim, next agendum 14:34:24 agendum 2. "record of telcon 15 Apr, Amsterdam ftf meeting" taken up [from DanC_] 14:34:49 seconded by andyS 14:35:08 + +358.925.aacc 14:35:23 Zakim, aacc is JanneS 14:35:23 +JanneS; got it 14:35:42 no objections; adopted 14:35:55 http://www.w3.org/2001/sw/DataAccess/ftf1 14:36:04 Revision 1.51 14:36:15 record of ftf supported by DanC and several others 14:36:19 JanneS has joined #dawg 14:36:25 (am I the only one hearing a new echo) 14:36:26 thompsonbry has joined #dawg 14:36:27 Zakim, next item 14:36:27 agendum 3. "Use cases draft status" taken up [from DanC_] 14:36:38 +JosD 14:36:45 I hear an echo 14:36:52 me too 14:36:54 me too. 14:36:58 me too. 14:37:00 http://www.w3.org/2001/sw/DataAccess/UseCases 1.38 14:37:04 did the echo come with Jos or before? 14:37:07 agenda written against 1.28; now 1.38 14:37:12 with danc I think. 14:37:12 before Jos 14:37:17 JosD has joined #dawg 14:37:24 ACTION RobS: to generate some RDF (in some form) for 5.1.1. 14:37:40 DONE: ACTION EricP: to generate a diagram of a query discussed in the use cases document. 14:37:53 ACTION Kendall: to work with Alberto on 5.1.3. 14:38:03 DONE: ACTION Kendall: to look at Yoshio's use cases. 14:38:17 DONE: ACTION: AndyS, EricP to review kendallC draft by 4 May telcon 14:38:22 http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0223.html 14:38:36 (and now a really nasty hum with Andy) 14:38:49 can not understand andy between buzz and echo 14:39:13 JeffBaget has joined #dawg 14:39:13 eric: nice diagram on use case 2.2! any way of inverting the left-hand property arc? hard to read upside down 14:39:31 (regrets DaveB) 14:40:01 2.2 diagram should be for 2.1 -- it's misplaced in the doc 14:40:24 howard, re diagram, will try. requires some svg fiddling. 14:40:50 andys: easy to get picky over req wording; unavoidable to argue 14:41:04 -JeffB 14:41:10 note that our tech will support use cases, but not necessarily solve them all 14:41:27 as: there is no clear "tell me about" use case 14:41:47 as: partly covered by Motorcycle parts (3.2) 14:42:25 3.2 in latest version at least; previous versions use different numbering 14:42:54 +JeffB 14:43:02 as: we should get community feedback on "tell me about" 14:43:09 are or are not covering what? I am missing the central point. 14:43:28 thompsonbry: the "tell me everything about foo" kind of query 14:43:41 2.8: photos of friend kind of references "tell me about" as well 14:43:51 as: we should add a "tell me about" 14:44:58 rob: steveH was planning to include "browser" use case to demonstrate this req 14:45:23 DaveB has joined #dawg 14:45:49 ok if I mute you, Janne? 14:46:05 Zakim, mute JanneS 14:46:05 JanneS should now be muted 14:46:13 discussin of whether 3.2 really addressed tell me about... 14:46:23 patH: 3.2 is very ambitious 14:46:31 2.2 14:46:38 + +1.441.234.aadd 14:46:38 danC: use cases can be more ambitious than what we'll really do 14:46:48 Zakim, aadd is DaveB 14:46:48 +DaveB; got it 14:48:10 rob: use cases can't cover open-ended things unless they're explicit 14:48:22 andyS was talking about req, not UC 14:48:36 andys: can we use separate mailing list to discuss doc? 14:48:45 danc likes separate list 14:48:53 How about just a UC: prefix? That seems easier. 14:48:57 several for, several against 14:49:46 (i'm ok muted for now) 14:49:47 danc: sometimes useful to separate response to comments from discussion 14:49:57 Zakim, who's talking 14:49:57 I don't understand 'who's talking', rob_ 14:50:03 Zakim, who's talking? 14:50:14 rob_, listening for 10 seconds I heard sound from the following: Kendall_Clark (16%), DaveB (9%), BryanT (37%), rob_ (4%), Yoshio (10%), DanC (34%), AndyS (10%), EricP (25%), 14:50:17 ... Farrukh (9%) 14:50:46 danc: WG list is for group, other is for public 14:51:22 decision to set up separate list for public discussion of doc 14:51:40 ACTION EricP: set up a public comment list; DanC and EricP to choose a name 14:51:48 andys: no puns (no support from anyone else) 14:51:56 dog-groom 14:52:45 dawg-show 14:52:46 will name something like foo-comments 14:53:55 DaveB has joined #dawg 14:54:20 some of the diagrams are in the wrong place... 14:54:32 danc: looking at 1.39 14:54:33 i note that i also provided no completions for [XXX:finish] 14:55:17 diagrams are in the right spot as of 1.39 14:55:23 -DaveB 14:56:09 +DaveB 14:56:17 chosen foaf:name instead of given or anything else 14:56:24 (no objections from anyone) 14:56:29 http://www.w3.org/2004/03/dots/pim1-Aimg.png 14:56:38 (with more arcs) 14:57:10 should we replace question marks with bnodes? 14:57:21 q+ to ask about sec 3 title - candidate requirements? 14:57:49 danc: are diagrams data or queries? 14:58:02 first one is query (email address) 14:58:16 second is query (publishing) 14:58:23 danc: need to make clearer contrast 14:58:40 andyS: write data in N3 14:58:47 maybe just change color 14:59:00 i like the idea of doing n3 for data, diagram for query 14:59:49 eikeon has joined #dawg 15:00:09 rob: I don't think we should put queries into use cases 15:00:35 many voted against query in RDF syntax, so why are we trying to draw RDF diagrams for queries? 15:00:50 data in rdf, that's fine 15:00:55 because we don't have the "real" syntax yet! 15:02:10 eric: no concrete data for media example... 15:02:35 howardK: replace query thing with data in place of variables 15:02:46 many for showing data, not queries 15:02:59 questions about how response should come back 15:03:15 danc: mail your comments 15:03:31 let's talk about schedule 15:03:57 danc says http://lists.w3.org/Archives/Public/public-rdf-dawg/2004AprJun/0215.html 15:04:22 q+ to ask what people here think about issues addressed in the "RDF Query and Rules Framework" 15:04:53 that sched leaves two telecons... 15:05:21 kendal: will stop adding stuff and work reactively 15:05:35 please, my name is kenda*ll* :> 15:05:45 q? 15:05:48 picky picky 15:06:47 supporting a document does not necessarily mean you support it content; i.e. the requirements 15:07:26 danc: this means we don't publish before WWW 15:07:53 end of www'04 is 21 May 15:07:59 ack dave 15:07:59 DaveB, you wanted to ask about sec 3 title - candidate requirements? 15:08:08 -SteveH 15:08:22 DaveB: make clear that these are candidate reqs 15:08:42 danc: change doc to candidate reqs 15:08:47 how about having objectives section? 15:09:51 thompsonbry has joined #dawg 15:10:07 +??P60 15:10:07 1.39 has a start of a "4. Design Objectives" section 15:10:49 howardK what's the diff between req and objective (sec 3 and 4) 15:10:50 Zakim, ??P60 is SteveH 15:10:50 +SteveH; got it 15:11:16 reqs got lots of votes and little opposition 15:11:28 objectives were more mixed in f2f voting 15:11:37 reqs will be critical path; others just desirable 15:11:48 s/voting/polling/ 15:11:52 meant f2f straw polls 15:12:24 yoshio: how are links made between UC and reqs? 15:12:44 sorry, it was not me 15:12:52 sorry; who said that? 15:13:31 I believe that was Farouk (sp?) 15:13:32 kendalll: can link from UC to req via "motivates" relation 15:13:57 that might be solving the problem 15:14:48 we chould publish without links, add them later 15:15:00 kendall: comments ASAP 15:15:20 date and time are out of left field 15:15:42 thompsonbry has joined #dawg 15:15:44 making links would help us check missing requerements, I think though 15:15:52 doc does not mention int or float 15:16:23 andys: two discussions at f2f, one about datatypes and another specifically about date/time 15:16:23 we did not straw poll on int & float, it was skipped 15:16:52 it appeared to be as if int & float were taken for granted without need for poll 15:16:59 i agree with JanneS 15:17:04 yes 15:17:05 datatype related to "exploring neighborhood" 15:17:09 yes 15:17:37 kendall: we took int and float for granted 15:18:02 danc: obviously necessary; add to reqs 15:18:45 what about strings? 15:18:53 rob: equality good, comarisions bad 15:19:03 literals are strings + language 15:19:44 let's skip ahead on the agenda to reqs 15:20:26 +q on extensibility (3.3) 15:20:36 q+ on extensibility (3.3) 15:20:54 ! 15:21:02 eikeon has joined #dawg 15:21:04 rob: let's drop date+time 15:21:17 q+ on 3.1 multi-edged paths 15:21:37 No I am on the queue! 15:21:38 howardK: date+time operations very complex 15:21:41 (can you unmute me? I'll call again if I contribute echo) 15:22:06 q+ defend 3.7 15:22:09 danc: let's stick to what we've got 15:22:30 current doc gives one DT priority arbitrarily 15:22:35 nobody speaks out for reqs 15:22:40 I AM 15:23:00 DanC? 15:23:11 ack jannes 15:23:46 me too. I'll make my "simple" date and times caveat more explicit via email 15:23:48 elaborate 3.7 to include integers and floats 15:25:31 3.3 appears to offer extensibility for datatypes 15:26:27 i'll call again 15:26:31 This may be relevant, soon-to-anounced SWRL spec:http://www.daml.org/2004/04/swrl/builtins 15:26:35 -JanneS 15:26:36 danc: let's not wordsmith; are we happy with what we've got or not? 15:27:09 +??P42 15:27:35 danc: going back to 3.1 and doing them in order 15:31:59 it shouldn't be saying that 15:32:07 ACTION: rewrite 3.1 (AndyS + JF) 15:32:16 (how do I assign actions to particualr people) 15:32:26 say ACTION abc: do something 15:33:18 on to 3.2 15:35:07 (I need to leave in 5 minutes) 15:35:41 no voting 15:35:52 and *candidate* requirements 15:36:04 there was consensus against the general "easy return" thing, but people liked this one 15:36:06 "lack of support" is the wording I'd use. 15:36:08 (rob is still against) 15:37:56 patH: s/queries to return/query results to specify/ 15:38:04 -Farrukh 15:39:02 danc: let's hold of on discussion until Pat writes something 15:39:32 ACTION PatH: summarize query/binding experience from DQL 15:39:49 some support for 3.3 15:40:01 pat objects to 3.3 15:40:12 no definition of extensibility 15:40:13 bryan objects to 3.3 15:40:51 "using extensiblity here means we can't use it anywhere else" 15:41:13 of course there are other requirements; do you support these ones! 15:41:30 abstain on req; object to title 15:41:47 -Yoshio 15:41:51 Zakim, call Yoshio 15:41:51 I am sorry, Yoshio; I do not know a number for Yoshio 15:42:13 it's not part of query langauge to calculate with values 15:42:21 +Yoshio 15:43:36 change title 15:43:37 but to pass the code needed to the server should be part of the query language, I guess 15:43:51 "extensible value processing" 15:44:07 not crazy about it; would abstain at worst 15:45:37 "Extenstible value testing" 15:45:41 +1 15:45:47 +1 15:45:58 consensus...or exhaustion... 15:46:16 objections have faded away 15:46:43 we are voting on this req 15:46:51 bryan objects 15:46:56 rob abstains 15:47:18 janne abstains 15:47:20 ericP abstrains on a formal requirement 15:47:31 JF abstains 15:47:34 Zakim, who's one the phone? 15:47:34 I don't understand your question, DanC_. 15:47:41 Zakim, who's on the phone? 15:47:41 On the phone I see HowardK, JosD, JeffB, DaveB, SteveH, ??P42, Yoshio, BryanT, rob_, DanC, Kendall_Clark, EricP, AndyS, PatH, Kevin 15:47:59 Yoshio wants to see concrete documents before voting 15:48:08 requirement is adopted 15:48:26 bt: it's premature to vote on this. 15:49:00 the first requirement's premature!? 15:49:01 rob notes that he wasn't ready to make a decision 15:49:38 I don't understand the change in 3.3 (in my honest opinion) 15:50:07 (did yoshio vote in favor? did he mean to?) 15:50:33 I want to know the current description of 3.3 15:50:51 You just voted. How did you intend to vote, Yoshio? 15:51:01 "extensible value testing" I think 15:51:05 3.3 Extensible Value Testing -- current state 15:51:07 Yoshio, the change in wording allows two things: addition of more extensibility mechanisms, and constriained arbitrary operations to (simpler) testing operations 15:51:22 plus obvious changes in the following text; mostly s/processing/testing/ 15:51:32 (I need to leave now: I will vote for 3.7 and for adding either a) more text to 3.7 to include int & float or a new requirement for int & float). I would love to hear comments from DAML etc. experience why these types are so hard as someone mentioned earlier during the call. 15:51:45 on to 3.4 15:52:20 (Rob, will you copy&paste my previous comment once you get to 3.7?) 15:52:23 andys: at f2f we tried to go for strong wording 15:52:34 s/MUST/might/? probably not so helpful. 15:52:39 which comment? post it again 15:52:51 I need to leave now: I will vote for 3.7 and for adding either a) more text to 3.7 to include int & float or a new requirement for int & float). I would love to hear comments from DAML etc. experience why these types are so hard as someone mentioned earlier during the call. 15:53:01 your comment is noted, janne 15:53:08 thanks! 15:53:31 JanneS has left #dawg 15:53:35 -??P42 15:55:24 (I'm not likely to put questions to exclude requirements, rob.) 15:55:37 i agree, what is "query" doing in "original query graph"? 15:55:38 [[ * Query results as a sub-graph of the queried RDF graph (straw poll: yes 10, no: 2)]] -ftfreq 15:55:48 perhaps "queried" graph? 15:55:50 so we waste time talking about things that a small minority are interested in, forever? 15:56:23 no, (a) not forever, and (b) I called for support 1st. 15:56:27 small minority? it straw polled strongly, as I recall. 15:56:30 I didn't hear "a small minority" 15:56:33 at least 10 positives 15:56:35 the idea is that you can perform queries and then perform the same query against that result, and get it back 15:57:38 there is more to inferencing than inferred triples 15:58:14 It is for searching the support issue, I guess 15:58:56 comments on "determinism" 15:59:14 danc: let's leave this to email 15:59:19 ACTION EricP, SteveH... 15:59:47 move to 3.5 15:59:49 ACTION: EricP write up implementation experience of 3.4 Subgraph Results 15:59:52 rob supports, a few others 16:00:13 ACTION: SteveH to express objections to 3.4 Subgraph Results 16:00:13 +1 16:00:14 this is about working without a network connection 16:00:39 bryan speaks against: 16:01:36 brian: don't mention "access protocol" 16:01:49 brian suggests s/not depend on the access protocol and should// 16:02:50 brian seconds vote on 3.5 16:02:52 no objections 16:02:55 no abstentions 16:03:01 adopted 16:03:20 RESOLVED: by consensus to adopt local queries as ammended s/not depend on the access protocol and should// 16:03:38 (are we expecting to extend this meeting?) 16:03:57 thompsonbry has joined #dawg 16:04:06

The query language must be suitable for use in accessing 16:04:06 local RDF data—that is, the same machine or same system 16:04:07 process.

16:04:25 Zakim, pick a scribe 16:04:25 Not knowing who is chairing or who scribed recently, I propose JeffB 16:04:26 volunteers for scribing next week? 16:04:29 Zakim, pick a scribe 16:04:29 Not knowing who is chairing or who scribed recently, I propose JeffB 16:04:30 Zakim, pick a scribe 16:04:31 Not knowing who is chairing or who scribed recently, I propose PatH 16:04:41 Zakim, pick a scribe 16:04:41 Not knowing who is chairing or who scribed recently, I propose rob_ 16:04:43 Zakim, pick a scribe 16:04:43 Not knowing who is chairing or who scribed recently, I propose DaveB 16:05:14 scribe next week: DaveB 16:05:26 RRSAgent, make logs world-access 16:05:48 donm is 11th May 16:05:48 adjourned 16:05:53 -Kendall_Clark 16:06:02 -DaveB 16:06:08 bryan has joined #dawg 16:06:31 -Yoshio 16:06:38 -rob_ 16:06:43 -BryanT 16:07:13 -JosD 16:07:21 http://www.daml.org/2004/04/swrl/builtins 16:07:26 -JeffB 16:07:53 -Kevin 16:08:04 -DanC 16:08:07 -PatH 16:08:08 -SteveH 16:08:09 -HowardK 16:08:11 -AndyS 16:08:28 -EricP 16:08:29 SW_DAWG()10:30AM has ended 16:08:30 Attendees were BryanT, Yoshio, PatH, +1.760.476.aaaa, DanC, Kendall_Clark, rob_, SteveH, EricP, AndyS, Kevin, HowardK, +1.781.454.aabb, Farrukh, JeffB, +358.925.aacc, JanneS, JosD, 16:08:34 ... +1.441.234.aadd, DaveB 16:57:26 Yoshio has left #dawg 18:18:24 Zakim has left #dawg 19:00:59 eikeon has joined #dawg 20:43:38 eikeon has joined #dawg 21:53:40 eikeon_ has joined #dawg