14:08:42 RRSAgent has joined #dwbp 14:08:42 logging to http://www.w3.org/2016/02/26-dwbp-irc 14:08:44 RRSAgent, make logs 351 14:08:44 Zakim has joined #dwbp 14:08:46 Zakim, this will be DWBP 14:08:46 I do not see a conference matching that name scheduled within the next hour, trackbot 14:08:47 Meeting: Data on the Web Best Practices Working Group Teleconference 14:08:47 Date: 26 February 2016 14:08:53 zakim, who is here? 14:08:53 Present: (no one) 14:08:55 On IRC I see RRSAgent, laufer, annette_g, BernadetteLoscio, riccardoAlbertoni, antoine, newton, deirdrelee, Caroline, hadleybeeman, trackbot 14:10:17 present+ newton 14:10:31 present+ annettte_g 14:10:40 present annette_g 14:11:15 present+ annette_g 14:11:21 zakim, who is here? 14:11:21 Present: newton, annettte_g, annette_g 14:11:23 On IRC I see RRSAgent, laufer, annette_g, BernadetteLoscio, riccardoAlbertoni, antoine, newton, deirdrelee, Caroline, hadleybeeman, trackbot 14:11:29 present- annettte_g 14:11:46 present+ antoine 14:11:50 present+ deirdrelee 14:11:53 present+ BernadetteLoscio 14:12:36 https://www.w3.org/2016/02/19-dwbp-minutes 14:12:41 scribenick: antoine 14:12:46 scribe: antoine 14:12:55 PROPOSED: to accept https://www.w3.org/2016/02/19-dwbp-minutes 14:13:03 +1 14:13:05 +1 14:13:06 +1 14:13:09 +1 14:13:11 +1 14:13:11 +1 14:13:11 +1 14:13:12 +1 14:13:18 +1 14:13:21 RESOLVED: accept https://www.w3.org/2016/02/19-dwbp-minutes 14:13:42 http://w3c.github.io/dwbp/bp-status.html 14:13:43 TOPIC: BP-review status update 14:13:52 q+ 14:14:02 ack bern 14:14:10 BernadetteLoscio: annette made some updates 14:14:32 ... and we have aproposal for organizing the sections 14:14:47 s/sections/API section 14:15:09 hadleybeeman: first update on the table? 14:15:18 I did make changes to versioning, too 14:15:21 newton: we haven't updated the table much 14:15:31 ... updated peter and riccardo's BP 14:15:47 http://w3c.github.io/dwbp/bp-status.html 14:16:11 Caroline: this is the link that has not been updated 14:16:42 ... even though some of the BP might have been updated 14:16:49 s/BP/BPs 14:16:59 q+ 14:17:11 ack riccardo 14:17:19 riccardoAlbertoni: I have pushed a revised version of the DQV example 14:17:25 :) 14:17:28 ... and the BP table for my part 14:17:32 thank you riccardoAlbertoni 14:17:36 ... please merge my pull request! 14:17:45 ... (that's about BP7) 14:17:56 thanks a lot! 14:18:17 ... in the DQV section, we're refering to DQV 14:18:35 ... the example BP is complete but depending on DQV issues we may have to update it. 14:18:49 ... I promise I will maintain the two docs in synch. 14:19:37 BP1: providing metadata 14:19:46 but BernadetteLoscio worked a lot in DWBP during her vacation :) 14:19:58 BernadetteLoscio: will work on it asap. Really soon 14:20:09 hadleybeeman: how much work? 14:20:17 BernadetteLoscio: not a lot. 14:20:38 ...especially as I have worked on examples for the following BPs 14:20:40 Just for the record, the revision on bp7 were suggested by antoine, Sorry for not giving the proper credit ;) 14:20:55 hadleybeeman: need help? 14:20:57 thank you antoine :) 14:21:17 action to newton to check if the turtle and RDFa examples are validated 14:21:17 Error finding 'to'. You can review and register nicknames at . 14:21:29 action newton to check if the turtle and RDFa examples are validated 14:21:29 action newton to check if the turtle and RDFa examples are validated 14:21:29 Created ACTION-233 - Check if the turtle and rdfa examples are validated [on Newton Calegari - due 2016-03-04]. 14:21:29 Created ACTION-234 - Check if the turtle and rdfa examples are validated [on Newton Calegari - due 2016-03-04]. 14:21:45 BernadetteLoscio: no need for help for now. I'm going to write example and then ask feedback. 14:21:53 hadleybeeman: before next week? 14:21:56 BernadetteLoscio: yes 14:22:28 hadleybeeman: are we in trouble because this one is late? 14:22:42 s/this one/the things in this table 14:22:48 BernadetteLoscio: beginning of next week we can have a general view about the document 14:23:05 BP 2: Provide descriptive metadata 14:23:28 hadleybeeman: do you need someone to help you review this? 14:24:01 newton: I can work with BernadetteLoscio 14:24:09 ... get it done asap 14:24:21 BP 3: Provide locale parameters metadata 14:24:24 newton: same 14:24:33 BP 4: Provide structural metadata 14:25:07 I'm gonna try to connect again 14:25:12 newton: we're ok with both examples 14:25:17 ... the test will have to be changed 14:25:40 I have connection probelms 14:25:47 BP 5: Provide data license information 14:25:58 newton: same. need to work on test and intented outcome 14:26:05 BP 6: Provide data provenance information 14:26:15 deirdrelee: issue was whether it needs a more detailed example 14:26:31 ... I am considering extending the example early next week 14:26:37 q+ 14:26:41 ... for the text I think what's there should be sufficient 14:26:45 ack newton 14:26:58 newton: if it's necessary to change the intend outcome please let us know! 14:27:09 ... the editors will work on this! 14:27:20 hadleybeeman: on all intended outcomes or only BP6? 14:27:22 q+ 14:27:31 BP 7: Provide data quality information 14:27:39 riccardoAlbertoni: example is finished 14:27:58 ... for the test I didn't change, I wanted to see the other BP 14:28:08 ... for now it seems aligned 14:28:16 ... the question is whether we need to be more specific 14:28:25 ... but that's a question for all BPs no ontoly this one! 14:28:39 ... As soon as other BP's testing section are refined I could check and review 14:28:55 hadleybeeman: that's something to do for evey BP! 14:29:17 riccardoAlbertoni: we have to be careful: test mentions datasets, intended outcome mentions also distribution. 14:29:24 ... I can try to align 14:29:34 BP 8: Provide versioning information 14:29:45 annette_g: there was already a good example 14:29:54 q- 14:29:58 thank you annette_g for imporving the English :) 14:30:01 ... I think the test is ok. 14:30:03 q+ 14:30:11 s/imporving/improving 14:30:13 ... I've reviewed it but I may have written it too ;-) 14:30:22 hadleybeeman: who'd be a good person? 14:30:29 annette_g: I don't know 14:30:48 newton: I've not merged the pull request now 14:30:58 q+ to ask about changes in intended outcome 14:31:24 ack newton 14:31:27 hadleybeeman: let's go BP by BP not step by step 14:31:54 annette_g: I've looked at the content, my PR also makes suggestions for the intro 14:32:05 newton: I will review the test 14:32:20 ACTION: newton to review annette's test for BP8 14:32:20 Created ACTION-235 - Review annette's test for bp8 [on Newton Calegari - due 2016-03-04]. 14:32:28 BP 9: Provide version history 14:32:34 annette_g: I think it's fine 14:32:51 ... maybe need review from a vocabulary person 14:33:25 ACTION: antoine to review the voc aspect of BP9 14:33:25 Created ACTION-236 - Review the voc aspect of bp9 [on Antoine Isaac - due 2016-03-04]. 14:33:31 BP 10: Avoid Breaking Changes to Your API, Communicate Changes to Developers 14:33:49 annette_g: I did a lot of re-write, but let's discuss it later 14:34:01 ... I need opinions on how to test 14:34:13 ... sthg like 'send email to devlopers' would be really helpful? 14:34:23 s/devlopers/developers 14:34:44 ... maybe scribe the actions one should take 14:34:49 q+ 14:34:49 q+ 14:34:50 ... a notice on the API homepage 14:35:21 q- later antoine 14:35:25 q+ antoine 14:35:45 riccardoAlbertoni: is DUV keeping a list of users adopting a dataset or distribution? 14:35:56 ... perhaps the BP example could re-use part of that info in DUV 14:36:21 q+ 14:36:37 hadleybeeman: finding your name in somebody else's metadata is a bit strange 14:36:41 ack bern 14:36:54 BernadetteLoscio: we don't have a proeprty to capture this in DUV 14:37:00 ack riccardoAlbertoni 14:37:07 ... it shouldn't be mandatory 14:37:16 ack newton 14:37:28 newton: annette_g maybe we can talk with SDW 14:37:35 ... they have issues about APIs and examples 14:37:44 ... we meet them next wednesday 14:37:53 q+ 14:38:14 annette_g: the issue here is really how one can write a BP for noticing users 14:38:22 ... is it covered by SDW? 14:38:27 newton: not sure 14:38:38 hadleybeeman: I could imagine situations like this 14:38:57 ... it might as well be solved the same way as everyone else 14:39:05 ... there's nothing special about spatial data. 14:39:23 ... Why don't you send an email to their list and our list? 14:39:37 ack bern 14:40:00 BernadetteLoscio: examples says [cites the BP] 14:40:05 action annette to email SDW (and DWBP) to ask about their API work (with regard to examples for BP 10) 14:40:05 Created ACTION-237 - Email sdw (and dwbp) to ask about their api work (with regard to examples for bp 10) [on Annette Greiner - due 2016-03-04]. 14:40:36 ... maybe we can use an API as example and show waht should be done with that API. 14:40:51 annette_g: like, saying what change would break the API? 14:40:56 BernadetteLoscio: yes 14:41:12 annette_g: it's a great thought 14:41:50 annette_g: I was not sure we should have an example of a maintained example 14:42:22 BernadetteLoscio: we could have a documentation page for the API 14:42:30 annette_g: a fake documentation page? 14:42:37 BernadetteLoscio: yes 14:42:55 annette_g: who would build and maintain it? 14:43:31 BernadetteLoscio: I don't know, but if we have real data, we could have a real or fake API. 14:43:45 hadleybeeman: we need to show that it is practical 14:43:55 ... other groups need implementations in the wild 14:44:08 ... but we don't need to rely on sthg that needs to be maintained 14:44:16 ... we just need enough code to show what we mean 14:44:25 ... so that devlopers can adapt it to their case. 14:44:33 BernadetteLoscio: yes 14:44:45 annette_g: what can we put? An API is a system 14:44:58 hadleybeeman: we're not telling people how to build their APIs, aren't we? 14:45:06 annette_g: no, but we give ideas. 14:45:22 hadleybeeman: so we're pointing to other APIs? 14:45:45 ... examples on how to use this in the context of data on the web? 14:46:17 ... We need to provide examples of the parts we're describing, not what others are describing 14:46:22 annette_g: there is no spec 14:46:32 hadleybeeman: is there any normative references to REST work? 14:46:44 annette_g: ref to functioning APIs or work about how to create them? 14:46:51 hadleybeeman: looking at BP21 14:47:05 ... it's becoming complicated now. 14:47:34 I cannot hear anybody now... 14:47:41 me neither 14:47:42 me neither 14:48:01 restart the call? 14:48:03 sound gone, i'm talking away 14:48:17 Caroline has joined #DWBP 14:49:13 Maybe WebEx has crashed? I can't seem to rejoin the call 14:49:25 me neither 14:49:33 Wait, now I'm back in. 14:49:34 neither me 14:50:46 just finally got audio connected 14:50:53 hadleybeeman: I'm suggesting that Annette has a go at putting down what a developer should have in mind as a bare minimum 14:51:17 ... when they're implementing this 14:52:11 ... instinctively 14:52:26 ... (that's about the BP for making changes) 14:52:40 annette_g: I really like BernadetteLoscio 's suggestion 14:52:51 hadleybeeman: as you wish 14:53:13 again... 14:53:15 no sound again.. 14:53:16 no 14:53:37 it is a ghost... 14:53:46 no audio :( 14:53:52 Right. Well, I was saying — we have 8 mins left. 14:54:00 *holy cow, tempus fugit 14:54:08 @annette_g we're thinking in put all BPs related to APIs into a subsection under Data Access. 14:54:18 I suggest we leave the BP table for now — but it would be great if everyone working on the rest of the BPs make an effort to complete the table by next week 14:54:23 (since we're already a week overdue) 14:54:37 yes, I want to see them all together, with the one about having an API in the first place coming first 14:54:37 newton: can we avoid huge changes in the document at this stage? 14:54:47 @annette_g the APIs BP will be "Data Access API" 14:54:53 I have raised an issue about the BPs I am reviewing 14:54:53 sorry I meant @newton 14:55:21 okay ———— hang on please 14:55:30 Let's finish this meeting here on IRC 14:55:41 a) as above: I suggest we leave the BP table for now — but it would be great if everyone working on the rest of the BPs make an effort to complete the table by next week 14:55:46 (since we're already a week overdue) 14:55:52 Could we have a section called "Data APIs"? I think people will want to search for that. 14:56:10 @antoine we would only replace them into a subsection into Data Access. Won't create new ones. 14:56:17 +1 to annette 14:56:34 Under Data Access section, to have a "Data Section API" as a subsection 14:56:41 yes! that's our idea! 14:57:00 I will not reflect into a huge change, I would be a structural change 14:57:16 s/I will not/ It will not/ 14:57:21 antoine seriously object to structure change and any re-shuffling at the time you're asking text to 10 contributors 14:57:42 Maybe make the change and then send around an email telling us you're done 14:57:50 so we can do a pull 14:58:10 antoine, what are your concerns? 14:58:18 We have the problem of the BPs numbers... 14:58:31 I'm afraid that we lose time figuring out what the impact of the changes are on the individual BPs 14:58:39 I won't have time to figure this out 14:58:45 so I won't work on my BPs 14:58:49 but the Data Access section needed to be reviewed 14:58:59 Aren't we only talking about the API BPs? 14:59:05 its just on the Data Access section 14:59:09 yes! 14:59:11 review doesn't imply changes while everyone else is working on the doc 14:59:23 its just the Data Access section 14:59:30 +1 to antoine, laufer .. 14:59:34 Data vocabularies section wont be affected 14:59:36 antoine, if their changes won't affect the areas you're looking at... Does it matter? 14:59:40 At a minimum *Zero* BP numbers should change 14:59:44 things are going to be changing if multiple people are editing anyway 14:59:47 @antoine, I don't think this would stop you working in your BPs, it would be only putting APIs' together 14:59:59 we're gonna make the merge 15:00:08 on github 15:00:17 I still think APIs deserve their own section 15:00:23 Re BP numbers, I'd suggest putting a temporary header on any merged ones that say, for example, "BP 10 and 21." 15:00:26 we're gonna review the numbers when necessary 15:00:30 we can renumber at the very end 15:00:35 yes 15:00:43 +1 to hadleybeeman suggestion 15:00:47 antoine, does that work for you? 15:00:49 All the static, unwebby stuff in our doc gets so much text and multiple sections; I think we need to give the dynamic stuff fair treatment 15:00:58 I'm ok with renumbering at the very end. Just please don't pull the carpet under our feets while we're working. 15:01:01 I agree that APIs deserve a section but we have to be careful in changing the BPs order now... 15:01:03 Totally fair. 15:01:10 Okay — we're out of time. 15:01:14 We can track every change and show which BP Numbers has changed 15:01:22 You all are champions for continuing this without sound!! 15:01:32 I don't have the time to follow your tracking 15:02:01 we wont change the structure of the document, its just the Data Access section 15:02:04 when moving things around, that is the time to re-order API BPs 15:02:06 mainly API BP 15:02:07 thank you @antoine and @laufer for this concern, we will work on it 15:02:10 Well, in this way we do not need a scribe... it is an advantage... 15:02:11 @newton, I think it might keep everything more sensible now to keep all the numbers as they are, even if they end up in the wrong order or multiple numbers for one BP. 15:02:21 True, laufer :) 15:02:31 bye antoine... 15:02:42 we dont refer to numbers in our document 15:02:50 We will, I promise, make sure it's all lovely and pretty (with numbers in order!) before it goes out to the public. 15:02:54 we always refer to the title of the BP 15:02:58 to the identifier 15:03:00 I find it awkward that the idea of having a API at all comes so late. It seems strange to start telling people how to make an API first and then come back to that fundamental point 15:03:02 True, BernadetteLoscio — but we do in our actions/issues and notes. 15:03:04 We will do it in a different branch or repository, and if the group agrees, we will merge it to the main document 15:03:08 the number is created automatically 15:03:28 that's frustrating. :( 15:03:31 if we also use the title, then it wont be a problem 15:03:41 We haven't always thus far, which is part of the issue. 15:03:53 I think we need to keep them for the moment, if we can -- even if it ends up being an extra bit of text 15:04:10 but just BP abou Data Access and APIs will change 15:04:11 we will do our best to not get in the way of what authors have been working on 15:04:18 others will keep the same 15:04:31 the order of the rest wont change 15:04:32 That sounds great, Caroline. Please do that, for now. 15:04:33 others will be renumbered, though 15:04:52 because BP 10 has to move 15:05:00 ah ok 15:05:17 if we see that this change may get in someone's way, we will wait to do it at the end. Would that be okay @annette? 15:05:32 sure, as long as we do it 15:05:41 great! Thank you! :) 15:06:06 Brilliant. I'm sorry we have to end this meeting! 15:06:11 ok! thanks! 15:06:15 thanks a lot! 15:06:18 Have a wonderful weekend, all. And thank you again for switching to text! 15:06:19 I will send and e-mail abou the issue I raised... 15:06:20 @annette_g I have some other issues to talk to you, may we have a call early next week to talk about it? 15:06:26 Talk next week. 15:06:27 thank you all!! 15:06:28 thanks, laufer. 15:06:33 bye for now :) 15:06:37 @annette_g it's about the Content Negotiation issue 15:06:40 @Newton, sure, want to use Skype? 15:06:45 good weekend !! 15:06:50 @annette_g yes, Skype :-) 15:06:56 s/abou the/about the/ 15:06:56 yay! 15:07:03 :)))) 15:07:51 @newton, let's exchange email to coordinate 15:08:04 @annette_g ok, thanks :) 15:08:23 okay, bye! 15:08:31 trackbot, end meeting 15:08:31 Zakim, list attendees 15:08:31 As of this point the attendees have been newton, annettte_g, annette_g, antoine, deirdrelee, BernadetteLoscio 15:08:39 RRSAgent, please draft minutes 15:08:39 I have made the request to generate http://www.w3.org/2016/02/26-dwbp-minutes.html trackbot 15:08:40 RRSAgent, bye 15:08:56 rrsagent, make logs public 15:08:58 Thank you all for the meeting 15:09:09 thank you, newton! You're doing loads here. :) 15:09:15 bye all 15:58:49 annette_g has joined #dwbp 17:21:24 Zakim has left #dwbp