20:39:01 RRSAgent has joined #dxwg 20:39:01 logging to https://www.w3.org/2017/11/28-dxwg-irc 20:45:11 rrsagent, make logs public 20:52:36 roba has joined #dxwg 20:55:43 LarsG has joined #dxwg 20:55:54 LarsG_ has joined #dxwg 20:56:08 LarsG_ has left #dxwg 20:56:47 present+ 20:56:57 PWinstanley has joined #dxwg 20:57:04 present+ 20:58:34 alejandra has joined #dxwg 21:00:18 annette_g has joined #dxwg 21:02:13 present+ 21:02:16 Jaroslav_Pullmann has joined #dxwg 21:02:18 present+ 21:02:29 present+ 21:04:16 present+ 21:04:25 present, but not having luck with webex 21:04:47 PWinstanley_ has joined #dxwg 21:04:54 present+ 21:05:20 riccardoAlbertoni has joined #DXWG 21:05:51 Makx has joined #dxwg 21:05:52 antoine has joined #dxwg 21:06:06 present+ 21:06:27 present+ 21:06:45 scribeNick: alejandra 21:07:18 dsr has joined #dxwg 21:07:30 https://www.w3.org/2017/11/21-dxwg-minutes 21:07:34 Topic: approval of minutes of Nov 21st 21:07:48 present+ 21:08:03 present+ 21:08:11 RESOLVED: approve minutes of Nov 21 21:08:36 Reminder: questionnaire for people to fill in 21:08:37 https://www.w3.org/blog/2017/10/questionnaire-on-practices-tooling-for-web-data-standardisation/ 21:09:20 dsr: this is an opportunity to gather data to help shape the future on how we develop data standards in W3C 21:09:32 dsr: working on a report based on questionnaire results 21:09:35 Caroline has joined #DXWG 21:09:40 ... hoping to have a report by January 21:09:50 ... sponsored by Innovate UK 21:10:03 ... please, fill in the questionnaire as soon as possible 21:10:17 q+ 21:10:29 ack alejandra 21:10:31 Present+ 21:10:49 ... anyone with an interest in data standardisation can fill it in 21:11:53 kcoyle: before we vote on the draft, there is a comment on versioning 21:12:00 ... listed as 6.2.2. 21:12:10 pushed change with status comment for 6.8.2,3 to UCR 21:12:21 "Provide clear guidance on conditions, type and severity of a resource's update that might motivate the creation of a new version in scenarios such as dataset evolution, conversion, translations etc, including how this may assist change management processes for consumers (e.g. semantic versioning techniques)" 21:12:23 ... rewording came from Dave and other comments by Makx and others 21:12:40 present+ Makx 21:12:47 q+ 21:12:55 ack alejandra 21:12:57 I can make change when voted on :-) 21:13:16 "might motivate" 21:13:37 alejandra: does the text include Makx change too? 21:13:40 kcoyle: yes 21:13:40 +1 of course 21:13:53 +1 to the might 21:14:00 +! 21:14:02 +1 21:14:09 +1 21:14:12 PROPOSED: accept changes to 6.2.2 as posted here 21:14:13 +1 21:14:16 +1 21:14:18 +1 21:14:19 +1 21:14:22 +1 21:14:25 s/+!/+1/ 21:14:34 +1 21:14:53 +1 21:14:53 RESOLVED: accept changes to 6.2.2 as posted here 21:15:26 kcoyle: do we issue this version of the UCR as FPWD? 21:15:31 q+ 21:15:43 q+ 21:15:51 q+ 21:15:52 PROPOSED: issue first public working draft of UCR 21:15:57 q? 21:16:20 Jaroslav_Pullmann: the document as it is now, or can it be changed e.g. in terms of the labelling of some requirements 21:16:25 q+ to disccuss if the abstract is too DCATy 21:16:37 ... making IDs referenceable 21:16:47 kcoyle: if it can be done in a day or two 21:16:52 ... then yes 21:16:57 ack Jaroslav_Pullmann 21:17:10 ack alejandra 21:17:39 ack antoine 21:17:44 q+ 21:17:46 alejandra: same question, would like to submit some modifications 21:17:48 http://lists.w3.org/Archives/Public/public-dxwg-wg/2017Nov/0117.html 21:18:02 antoine: I sent my question via email (see link above) 21:18:24 ... I sent a use case for Europeana and I still see it as it used to be, missing a few requirements 21:18:35 yes - as editor i was waiting for a definitive statement re updating it. 21:18:43 ... on the email discussion roba pointed out that there were a missing links to the use cases 21:18:57 kcoyle: what is missing? link to requirements or the use cases? 21:19:09 antoine: we had the discussion on the wording, have you seen them? 21:19:16 kcoyle: the changes don't seem to be in 21:19:46 AndreaPerego has joined #dxwg 21:19:47 roba: the first thing I've done was to reorder the UCs and Requirements so that they match the grouping 21:19:52 present+ AndreaPerego 21:19:54 ... the plan was to wait for the numbers to settle down 21:19:59 ... and then fix all the links 21:20:02 +q to propose a note in the document making explicit the kind of feedback we want from the readers 21:20:18 ... then, that's a piece of work that needs to be done 21:20:20 q+ 21:20:23 ... identification and links processing 21:20:40 ... I won't have time to do it myself, but I've tried to process the content changes 21:21:05 kcoyle: the profile requirements that came out of Europeana were pasted in the spreadsheet after 6.1 21:21:13 ... row 38 21:21:50 kcoyle: there are additional requirements 21:22:04 roba: I can add those as additional requirements 21:22:12 kcoyle: they won't get separate numbers anyway 21:22:50 spreadsheet link: https://docs.google.com/spreadsheets/d/16JmtNCz_aCWtTCSntriDWLvyPY2x-Y9dZFhAHFl55r0/edit#gid=0 21:23:13 kcoyle: put them in the document so that we don't loose them and we'll concentrate on the profile requirements in the next version 21:23:26 roba: there was a note saying that these could be pulled out as requirements if necessary 21:24:07 kcoyle: mark the section as being under revision 21:24:23 ack LarsG 21:24:23 LarsG, you wanted to disccuss if the abstract is too DCATy 21:24:51 ACTION: roba to add requirements for profiles from spreadsheet to UCR 21:24:53 Created ACTION-64 - Add requirements for profiles from spreadsheet to ucr [on Rob Atkinson - due 2017-12-05]. 21:25:06 ack roba 21:25:12 +q to say that some of the suggestions I have are related to referring to the charter in more detail 21:25:48 +1 21:25:55 LarsG: I wanted to talk about the abstract that talks about DCAT vocabulary, application but ignore the other deliverables we have 21:27:15 ACTION: alejandra to provide info for introduction 21:27:16 Created ACTION-65 - Provide info for introduction [on Alejandra Gonzalez Beltran - due 2017-12-05]. 21:27:27 q? 21:27:46 q- 21:27:57 riccardoAlbertoni: I am going to support the publication of the draft as it is 21:28:09 ... I have a comment related to the kind of feedback that we want from the readers 21:28:16 ... what kind of comments we expect? 21:28:25 ... we should add some notes at the end of the document 21:28:57 kcoyle: dsr is there a boilerplate text that we could use? 21:29:09 dsr: there is a boilerplate text about what the document is about 21:29:13 ... and its status 21:30:30 This is what the document says: 21:30:31 q? 21:30:32 "This document was published by the Dataset Exchange Working Group as an Editor's Draft. Comments regarding this document are welcome. Please send them to public-dxwg-comments@w3.org (subscribe, archives)." 21:30:37 ack riccardoAlbertoni 21:30:37 riccardoAlbertoni, you wanted to propose a note in the document making explicit the kind of feedback we want from the readers 21:30:40 q? 21:30:51 BTW, it seems that there is a need to change to FPWD document 21:30:54 @alejandra - you may find merging changes difficult after so much moving around - if so sent me sections to insert/update by email. 21:31:01 Jaroslav_Pullmann: I support making our request for comments more complete 21:31:23 ... and how are the comments going to be processed? 21:31:55 kcoyle: in some cases, the editors of the document are tasked with gathering the comments making sure that all of them are answered 21:32:17 ... and bringing the comments to the group so that we can be sure that there are answered correctly (through votes, etc) 21:32:34 q? 21:32:35 ... we should reply politely to every comment that we received 21:32:38 ack Jaroslav_Pullmann 21:32:44 Pushed change to profiles definition sub-requirements list :-) 21:32:54 great :-) 21:33:20 Jaroslav_Pullmann: there are questions on the search working correctly 21:33:30 ... there are some requirements/use cases that are empty 21:33:39 ... there are some lengthy requirements 21:33:54 ... I would provide a more harmonised text 21:34:09 kcoyle: I rather like to have verbs there 21:34:36 kcoyle: these are editorial questions and it is up to you 21:34:49 Jaroslav_Pullmann: we should discuss the IDs of requirements 21:35:05 ... given the changes in the groups 21:35:33 ... do we give them an alphanumeric identifier pointing to the topic? 21:35:48 kcoyle: is the question for this particular draft or for the later ones 21:35:50 ? 21:36:12 ... if you can hold off on that for this draft, it might be better, or make take too much time 21:36:27 kcoyle: when is the last date to get this version done? 21:36:38 dsr: publication auditorium starts 13th Dec 21:36:48 ... so last date to publish this would be 12th Dec 21:37:09 ... thus we have to have it ready before 21:37:13 ... we need to have it approved 21:37:23 ... so we need to have it ready within a few days from today 21:37:41 ... good news: if it is just the first draft, we can publish an updated draft after that 21:37:51 kcoyle: subsequent updates go through very quickly 21:38:09 ... should we say we need everything ready for Monday? 21:38:24 dsr: I will be at a workshop on 6th and 7th 21:38:29 ... Monday should be ok 21:38:43 ... I will give a heads up that we want to do this 21:39:21 kcoyle: whatever it is available on Monday morning 4th Dec will be in the first draft 21:40:09 kcoyle: we have a drafty draft of DCAT (including DCAT 1.0 stuff) 21:40:48 q+ 21:41:12 ack alejandra 21:43:52 alejandra: for edits, do pull requests with review 21:43:56 +1 to alejandra on the DCAT group GitHub approach 21:44:37 roba: I did most merges for the UCR group but we interacted with Jaroslav_Pullmann 21:44:51 I think new need to have the comments in the mailing list, since it is persistent, and can be used to track whether we have answered or not. GH issues can be modified - they are not persistent. 21:45:00 alejandra: we agreed on the process using branches on the repository and the github review functionality 21:45:16 +1 to AndreaPerego about the use of mailing list 21:45:19 ... happy to merge other peoples PRs and I will assign others in the DCAT group to merge my changes 21:45:34 I'm interested in working on profiles 21:45:35 q? 21:45:41 I agree on the comments on the mailing list 21:45:55 this is what the boilerplate text says 21:46:04 kcoyle: document on profile guidelines 21:46:15 ... and content negotiation on profiles is a third deliverable 21:46:25 I'm happy to help too 21:46:29 q+ 21:46:55 I'm also interested on profiles 21:47:09 Guidance on publishing application profiles of vocabularies. 21:47:23 ack roba 21:47:36 roba: I have two questions: interim set of deliverables was a best guess 21:47:45 ... there are different perspectives 21:48:00 ... guidance on profiles, and other issue is what are profiles 21:48:13 ... DCAT profile should follow, but it does strike me as an additional deliverable 21:48:29 ... general view on profiles, where a DCAT profile guideline would be straightforward to follow 21:48:46 ... I'm interested on the general case 21:49:01 kcoyle: Phil intended to have a general guidance, not just DCAT guidance 21:49:12 ... it should be possible to follow it in creating DCAT profiles 21:49:24 ... I don't think there was a specific document around DCAT profiles 21:49:30 q+ 21:49:36 ack antoine 21:49:38 q+ 21:49:55 antoine: it matches my interest 21:50:01 q+ to say I'm interested 21:50:11 ack alejandra 21:50:41 ack LarsG 21:50:41 LarsG, you wanted to say I'm interested 21:51:00 - can I contribute but not as 'editor'? 21:51:03 alejandra: I'm interested in contributing, and DCAT profiles provide lots of use cases 21:51:08 I'm interest as well, but still have to see whether / how much I can contribute. 21:51:08 roba: also interested 21:51:13 LarsG: also interested 21:51:17 I am also interested to contribute from experience with DCAT profiles in Europe 21:51:37 s/interest as well/interested as well/ 21:51:39 q+ 21:51:45 ack roba 21:51:47 I think it is important to contribute PWinstanley_, don't need to be an editor :) 21:52:10 roba: I'm not going to offer to coordinate the group 21:52:25 ... I've got time guaranteed until June 21:52:35 ... offer to work on reference implementations but not to coordinate the group 21:53:33 Google Hangout? 21:53:44 q+ 21:53:53 ack alejandra 21:53:58 What's the issue with WebEx? 21:54:43 kcoyle: not sure if we can use WebEx but we can use IRC 21:54:52 dsr: I can set up webex calls for you 21:55:04 For IRC, we just need to create a new channel for each subgroup - as we did in SDWWG. 21:55:44 q? 21:55:54 q+ 21:56:38 ack alejandra 21:57:10 alejandra: it could be useful to send a message to the list with the deadline for Monday 21:57:22 kcoyle: I'll do that 21:57:35 @Jaroslav_Pullmann - i will be travelling from Thursday eve your time 21:58:41 yes, Many thanks to Rob - lots of work went into that UCR 21:58:48 +1 21:58:53 many thanks to the UCR group! 21:58:54 +1 21:58:57 +1 21:58:58 +1 21:58:59 thanks all! 21:59:00 rrsagent, please create minutes v2 21:59:00 I have made the request to generate https://www.w3.org/2017/11/28-dxwg-minutes.html kcoyle 21:59:02 bye! 21:59:05 thanks and bye! 21:59:06 bye! 21:59:07 bye! 21:59:07 bye all 21:59:07 Thanks, and bye! 21:59:15 present- 21:59:45 chair: Karen 22:00:02 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2017.11.28 22:00:06 rssagent, draft minutes v2 22:00:20 rrsagent, please create the minutes 22:00:20 I have made the request to generate https://www.w3.org/2017/11/28-dxwg-minutes.html Caroline 22:00:29 rrsagent, make logs public 22:01:27 regrets+ Simon, Ixchel, Linda 22:02:01 meeting: Dataset Exchange Working Group Teleconference 22:02:10 RRSAgent, draft minutes v2 22:02:10 I have made the request to generate https://www.w3.org/2017/11/28-dxwg-minutes.html AndreaPerego 22:03:38 s/rssagent, draft minutes v2// 22:03:43 RRSAgent, draft minutes v2 22:03:43 I have made the request to generate https://www.w3.org/2017/11/28-dxwg-minutes.html AndreaPerego