20:58:01 RRSAgent has joined #dxwg 20:58:01 logging to https://www.w3.org/2018/01/09-dxwg-irc 20:58:10 rrsagent, make logs public 20:58:18 present+ 21:01:40 DaveBrowning has joined #dxwg 21:01:42 antoine has joined #dxwg 21:01:48 present+ antoine 21:01:56 alejandra has joined #dxwg 21:02:21 SimonCox has joined #dxwg 21:03:16 LarsG has joined #dxwg 21:03:22 LarsG_ has joined #dxwg 21:03:28 LarsG_ has left #dxwg 21:03:38 present+ 21:03:54 present+ 21:04:03 nicholascar has joined #dxwg 21:04:06 present+ 21:04:08 great! 21:04:10 annette_g has joined #dxwg 21:04:17 present + 21:04:24 present+ 21:04:26 Makx has joined #dxwg 21:05:26 scribe nick:PWinstanley 21:05:35 scribenick:PWinstanley 21:06:06 https://www.w3.org/2017/12/12-dxwg-minutes 21:06:06 https://www.w3.org/2017/12/12-dxwg-minutes 21:06:22 could we update the table at https://www.w3.org/2017/dxwg/wiki/Meetings with all the scribes, please? 21:06:25 Approval of last meeting's minutes 21:06:35 present+ SimonCox 21:06:47 kcoyle: I will try to update the scribes list 21:06:55 Ixchel has joined #dxwg 21:07:27 present+ 21:07:49 RESOLVED: approve minutes of previous meeting (Dec 12, 2017) 21:08:14 TOPIC: promote UCR 21:08:17 q+ 21:08:32 ack roba 21:09:26 roba: I note that we have a new member on the list - Nick Car 21:09:49 https://docs.google.com/spreadsheets/d/1_f5CAZv7rgUjJH5YXkmD6w5xS6GX5X2AmEp_LMptAfQ/edit#gid=0 21:09:57 kcoyle: we need to think about doing a second round of emails to promote/stimulate responses to the UCR publication 21:10:25 q+ 21:10:41 DaveBrowning: what is the green colour? 21:11:12 kcoyle: Caroline did that , but not sure what it means. The column 'sent' should be the key 21:11:36 ... if your name is on the spreadsheet then send it 21:12:13 q+ 21:12:17 q+ 21:12:29 q- 21:12:32 nicholascar: should we add new contacts? 21:12:34 ack DaveBrowning 21:12:38 ack nicholascar 21:12:38 kcoyle: yes please 21:12:53 ack alejandra 21:13:21 alejandra: people are supposed to reply by 20 Jan, we reply to comments. What's next? 21:13:24 AndreaPerego has joined #dxwg 21:13:32 kcoyle: comments feed into the next version of the draft 21:13:37 present+ AndreaPerego 21:13:52 ...we don't have a set date for the next draft 21:14:03 alejandra: but if there are no comments? 21:14:20 kcoyle: we ourselves might want to update the draft too ... 21:14:38 q? 21:14:54 TOPIC: open action items 21:15:01 https://www.w3.org/2017/dxwg/track/actions/open 21:15:40 kcoyle: jaroslav is still intending to cover action #50 21:15:57 ... andrea - Action 59? 21:16:24 AndreaPerego: I am still on the case, hope to get completion in the next couple of weeks 21:16:55 roba: Mine can be marked as done 21:17:38 kcoyle: Rob, please can you say what is going on in OGC (open geospatial consortium) that's relevant 21:19:02 roba: OGC specialises in spatio-temporal matters. I have a role as OGC staff member supporting knowledge management, and we are interested in describing relationships between our specifications, their versions and their profiles. I'm building a linked data environment to describe this 21:19:34 ...Because it is early days I have freedom in choices and have decided to link it to DXWG activity stream 21:19:57 kcoyle: on our home page we have related docs/vocabs. If there is anything related please link it there 21:20:21 roba: I plan to share a model for describing profiles. 21:20:30 q+ 21:20:34 kcoyle: I am doing a similar thing for Dubllin Core 21:20:52 s/Dubllin/Dublin/ 21:20:57 ack Makx 21:21:00 Just to note that OGC has also a group working on DCAT for geo metadata - already included in the list of stakeholders that have been contacted for the UCR doc. 21:21:25 Makx: Do you want to look at the EC ADMS schema - a DCAT-based schema for profiles and schemas. 21:21:28 q+ 21:21:45 kcoyle: please add to the home page 21:21:47 @Makx - what is the scope of ADMS? 21:21:53 ^^ https://www.w3.org/TR/vocab-adms/ 21:22:11 https://www.w3.org/2017/dxwg/wiki/Main_Page#Background_About_Profiles 21:22:15 (I have looked at it but not fully clear what set of problems it targets) 21:22:44 q? 21:22:49 ack roba 21:23:37 roba: while I've been working on requirements I'm happy to slot in with wider activity - the namespace must relate to a body that OGC has liaison with already, but it can be brought through this group to do that 21:23:58 ...Gathering prior art would be a good starting point 21:24:07 kcoyle: does this become a use case? 21:24:32 roba: I think it might be covered by existing generic UC, but we might need a more specific one. 21:25:05 kcoyle: add it as a github issue to allow discussion before we firm up the action on this 21:25:10 TOPIC: co-chair 21:25:43 kcoyle: Peter has volunteered to take over from Caroline when she steps out 21:25:58 ... we will work Peter into the schedule 21:26:25 PWinstanley++ 21:26:32 +1! 21:26:46 +100 21:26:47 TOPIC: meetings for DCAT & Profiles 21:26:49 hurray! 21:27:05 +q 21:27:25 kcoyle: we determined that DCAT meetings will be on Wednesdays, 20:00 UTC 21:27:30 ack alejandra 21:28:26 alejandra: After we made this decision Andrea updated his availability and it doesn't include this time. We will start with the decided time and review depending on attendance 21:29:09 AndreaPerego: I changed the timeslot when the poll was extended. The Wednesday 20:00 will be difficult for me 21:29:32 ...If I'm the only one affected then just go ahead without me 21:30:59 kcoyle: we need to know who is going to call the meeting. Use of webex is through Dave Raggett - but if you are using other things then that's fine. Use the IRC and Zakim to facilitate getting a record of the meeting 21:31:09 ...There needs to be a public record 21:31:33 SimonCox: Do you want me to do it? 21:31:37 kcoyle: Yes please 21:31:42 I will manage DCAT meetings then 21:32:05 +1 to SimonCox 21:32:13 +1 21:32:14 kcoyle: Please post on email the schedule and connection 21:32:19 What about the IRC channel to be used? #dxwg-dcat? 21:32:54 so, use the same channel as now 21:32:57 kcoyle: we can use #dxwg 21:33:06 ... the same channel as now 21:33:06 s/#dxwg-dcat/#dxwgdcat/ 21:33:37 q+ 21:33:40 ... using RRSAgent we will have to experiment with naming of minutes 21:33:59 SimonCox: I will contact Dave Raggett and sort arrangements 21:34:34 q+ to ask whether Profiles group includes content negotiation 21:34:37 kcoyle: we can also ask about naming conventions and options for automated management of minutes 21:34:46 ...Next is the profiles group 21:34:47 +q 21:34:49 q? 21:35:26 AndreaPerego: I propose a separate IRC channel - just in case there are parallel sessions 21:35:38 ... Dave R can advise 21:35:46 ack AndreaPerego 21:35:54 ack RubenVerborgh 21:35:54 RubenVerborgh, you wanted to ask whether Profiles group includes content negotiation 21:36:23 RubenVerborgh: the last email was about splitting profiles into guidance and content negotiation - what does the group cover 21:36:39 q+ 21:36:50 kcoyle: separate groups for each deliverable - so how do we want to split 21:36:54 q+ 21:37:45 ...Did you see the note after antoine posted to suggest that the content negotiation could be independent and be covered before the profiles 21:38:22 q+ 21:38:30 q? 21:38:38 ... RubenVerborgh and LarsG can proceed without waiting for others 21:38:55 ..The profiles should be renamed to profile guidance 21:39:14 RubenVerborgh: There should be an invitation email 21:39:36 kcoyle: most of those interested in profiles were interested in guidance. 21:39:48 I intend to implement profile negotiation.. so will join that group. 21:40:01 RubenVerborgh: I will send an email around 21:40:04 ack alejandra 21:40:27 alejandra: I want to return to the DCAT group - are we planning to start this week? 21:40:47 ack antoi 21:41:43 antoine: Organisation of profile discussion - it can meet in the same space as the content negotiation so as to cross-fertilise 21:41:54 ack annette_g 21:42:12 +1 to antoine 21:42:19 annette_g: We might want to start out together and split into subgroups later 21:42:51 kcoyle: that is what we were trying to do on the content page. It was clear that there were different parallel paths that were not meeting 21:43:41 annette_g: the first joint meeting should discuss the broad definition and then determine the commonality that allows the content negotiation people to push ahead 21:43:48 q? 21:44:02 +1 21:44:06 +1 21:44:08 q+ 21:44:12 kcoyle: What do people think? Does the initial joint meeting followed by splitting up later suit? 21:44:19 ack roba 21:44:27 roba: I support this. 21:45:10 ... Also at least 3 of us are modelling profiles, so this needs to be done in plenary so that we have an agreed formalism as a starting point 21:45:11 ack antoine 21:45:38 antoine: I was suggesting for cross-fertilisation, as I don't think we can get an agreement in just one meeting 21:45:53 +1 to antoine 21:46:08 kcoyle: Rob mentioned a plenary. Would it make sense to have this discussed in a general meeting? 21:46:19 regular agenda item :-) 21:46:36 q+ 21:46:37 :D 21:46:50 ack roba 21:46:51 kcoyle: I am willing for us to do that if that is what the group wants 21:47:07 roba: I think we should ask the question 21:47:26 ... are we in a position to parallelise activities, or not? 21:47:58 kcoyle: I fear we will have to come up with more than one term - one for ConNeg, and another for guidance 21:47:59 q+ 21:48:06 ack antoine 21:48:08 -1 for different term - +1 to formalise model so we can see if it is the same 21:48:14 q+ 21:48:26 antoine: does the charter allow us to split definitions in the final specs? 21:48:33 q+ 21:49:13 q? 21:49:16 kcoyle: the charter uses 'application profile' for both, but we could decide on a macro-level and a more specialised version. I've talked to Phil Archer who said we can refine the terms as we need 21:49:53 AndreaPerego: looking at the profiles use cases, we are using the word two ways - 21:50:32 ... We need to align with the terminology we use in the UCR otherwise it will be challenging for readers 21:50:40 q? 21:50:40 q+ process clarification - how will we track and tag requirements? 21:50:41 kcoyle: we need a way of distinguishing them 21:50:47 ack AndreaPerego 21:51:02 q+ to clarify how will we track and tag requirements? 21:51:08 ack roba 21:52:00 roba: at this stage we cannot make a call if they are different or not. If there are strong reasons for general and special views then that's OK, but we should not prejudge and we should do the work. Life would be simpler if they were the same thing (though different aspects) 21:52:20 ack SimonCox 21:52:20 SimonCox, you wanted to clarify how will we track and tag requirements? 21:52:22 s/using the word two ways/using the word more than two ways/ 21:52:23 ... The ISO definition seems to be broad enough to handle all 21:52:52 SimonCox: I am concerned that we are getting into material that should be covered in subgroup. 21:52:58 +1 with roba : in general I'm rather optimistic that we can get an agreement. I just think it will be super hard to do it quickly, and without first draft specs under our eyes. 21:54:20 ...I am concerned too about process - I started work on DCAT but had problems finding all documentation. In the last meeting we agreed to focus on github, yet we still have UCR in an HTML doc. We need to sort requirements to deliverables and this is challenging with the HTML doc esp as we agree to use github 21:55:09 ...The subgroups will benefit from a clarification of process. I have started by suggesting to group leads that we convert the UCR into github 21:55:25 q+ 21:55:45 kcoyle: we agreed that we work on the documents in github, but not all our work will take place this way (e.g. google spreadsheet) 21:56:09 ack roba 21:56:21 SimonCox: we are creating work by using too many tools and not using github as it can be used 21:57:13 +q 21:57:40 roba: I dont disagree with Simon, but it would be good to chat to Jaroslav to see if the conversion can be automated. Doing it by hand would be too lengthy. We need to explore potential for scripting the parsing 21:57:57 ... I will go with whatever we decide 21:58:11 kcoyle: roba will you check with Jaroslav? 21:58:19 It is easy to generate a list of github issues tagged as 'requirement' for a single deliverable - e.g. https://github.com/w3c/dxwg/issues?q=label%3Arequirement+label%3Adcat 21:58:30 roba: if we decide to go with github then yes 21:58:50 q- 21:58:57 (currently empty) 21:58:59 kcoyle: we don't have much time - so a straw poll now? 21:59:02 strawpoll: use github for discussing/deciding on requirements 21:59:08 +1 21:59:10 + 21:59:10 +1 21:59:11 +1 21:59:12 +1 21:59:13 +1 21:59:16 +1 21:59:16 +1 21:59:17 +1 21:59:18 +1 21:59:18 +1 21:59:49 ACTION: roba contact Jaroslav re: scripting github issues from UCR 21:59:51 Created ACTION-72 - Contact jaroslav re: scripting github issues from ucr [on Rob Atkinson - due 2018-01-16]. 22:00:14 We use GitHub Issues in other WGs like RDA's 22:00:44 kcoyle: I will put the discussion on how we are defining profiles into the next meeting agenda 22:01:06 thanks, bye 22:01:06 thanks folks! 22:01:07 thanks and bye! 22:01:08 ...If you can formulate the question that the group has to decide on then please let everyone know 22:01:09 Thanks, and bye! 22:01:10 bye! 22:01:11 RubenVerborgh has left #dxwg 22:01:14 rrsagent, please generate minutes v2 22:01:14 I have made the request to generate https://www.w3.org/2018/01/09-dxwg-minutes.html kcoyle 22:01:14 bye 22:03:34 meeting: Dataset Exchange Working Group Teleconference 22:03:38 chair: Karen 22:03:58 regrets+ Jaroslav, Riccardo 22:04:14 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2018.01.09 22:04:26 RRSAgent, draft minutes v2 22:04:26 I have made the request to generate https://www.w3.org/2018/01/09-dxwg-minutes.html AndreaPerego