20:49:17 RRSAgent has joined #dxwg 20:49:17 logging to https://www.w3.org/2019/03/05-dxwg-irc 20:49:24 rrsagent, make logs public 20:49:29 dsr has joined #dxwg 20:50:08 dsr has left #dxwg 20:50:36 dsr has joined #dxwg 20:54:49 meeting: dxwg plenary March 5 2019 20:54:55 chair: Karen Coyle 20:55:07 regrets+ Antoine , SimonCox 20:55:13 present+ 20:55:37 PWinstanley has joined #dxwg 20:57:17 present+ 20:57:44 Makx has joined #dxwg 20:58:08 ncar has joined #dxwg 20:58:31 present+ 21:00:07 roba has joined #dxwg 21:03:01 presenr+ 21:03:14 present+ 21:03:37 annette_g has joined #dxwg 21:05:01 scribenick: PWinstanley 21:05:08 present+ 21:05:16 https://www.w3.org/2019/02/26-dxwg-minutes 21:05:18 alejandra has joined #dxwg 21:05:25 meeting: DXWG Plenary 21:05:42 topic: Admin 21:05:42 present+ 21:05:53 proposed: accept minues of Feb 26 21:06:08 +1 21:06:11 +1 21:06:38 +1 21:06:47 +1 21:07:17 resolved: accept minutes of Feb 26 21:07:45 kcoyle: Open Actions 21:07:50 +1 21:08:06 AndreaPerego has joined #dxwg 21:08:12 present+ 21:08:21 sorry, I'm going to have to miss today's meeting. 21:08:30 ... there are actions from the conneg work that are open 21:08:32 RRSAgent, make logs world 21:08:54 q+ 21:08:59 ... we still have the gap analysis for the guidance doc, but we need to wait until that doc is further forward 21:09:02 ack ncar 21:09:26 RRSAgent, draft minutes v2 21:09:26 I have made the request to generate https://www.w3.org/2019/03/05-dxwg-minutes.html AndreaPerego 21:09:30 ncar: that gap analysis is long-standing, but will only be done when there is more of a doc 21:09:30 RRSAgent, make logs world 21:09:40 ...I have completed #305 21:09:56 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2019.03.05 21:09:58 RRSAgent, draft minutes v2 21:09:58 I have made the request to generate https://www.w3.org/2019/03/05-dxwg-minutes.html AndreaPerego 21:10:06 ... we ran a sprint and pulled together text that is now in the draft 21:10:28 ... following agreement from roba and LarsG 21:11:14 regrets+ annette_g 21:11:40 https://docs.google.com/spreadsheets/d/1Jo8pMcYbJBl8jNezeHTml7HfeqO8fnTnc3swVXEiS3I/edit#gid=0 21:12:11 kcoyle: For keeping track of all the feedback, PWinstanley began a google sheet that is far from complete. Do people think this is useful? 21:13:03 q+ 21:13:10 ack ncar 21:13:20 ... the complication is the discussion in github, which is being labelled as feedback, but is often part of a complicated thread where the comment might come in somewhere deepeer in thread 21:13:38 +q 21:13:47 Just to note that PROF and ODRL profiles were discussed in today's ODRL CG call: https://lists.w3.org/Archives/Public/public-odrl/2019Mar/0002.html 21:14:20 ncar: we are getting good contributions that we can respond to that are entirely related to conneg 21:14:36 kcoyle: what is the w3c position for github comments? 21:15:27 dsr: are they coming in as issues? using the labels would help,but I'm not aware of any W3C formal approach. we are still evaluating github and this can feed into that 21:15:51 Jaroslav_Pullmann has joined #dxwg 21:15:57 present+ 21:16:15 kcoyle: github has been very fruitful, but is harder for discussion and also tracking that the response is to the satisfaction of the commenter 21:16:47 ncar: we ask the other people who comment on the mailing list to look at the issue when we transfer it to github 21:17:15 I've emailed Annette re ACTION-306 so please can that ACTION be closed here? 21:17:43 dsr: the disposition of comments will mention the comment and its resolution in a document 21:18:18 kcoyle: this could be incorporated into the spreadsheet if we add columns for resolution and the agreement that it is satisfactory 21:18:57 Topic: subgroup reports 21:19:10 kcoyle: how close are we with DCAT to another draft? 21:19:13 RRSAgent, draft minutes v2 21:19:13 I have made the request to generate https://www.w3.org/2019/03/05-dxwg-minutes.html AndreaPerego 21:19:34 alejandra: re: issues and comments, we encourage people to put things in issues 21:20:03 alejandra: re: DCAT, we are trying to define a date and will then guillotine 21:20:36 ... dsr can perhaps guide on the implementation report. Does it need to be complete when going to CR? 21:21:05 ... according to the calculator that PWinstanley guided us to , we need to stop in mid March. 21:22:02 ... there are many things we still need to complete. Given this is an update of an existing implementation, do we only need to provide evidence on the gaps that we have filled? 21:22:18 dsr: I'll ask Phillipe 21:22:48 kcoyle: can alejandra say something about the importance of things that might not be included? anything vital? 21:23:26 alejandra: we haven't included versioning. There is a PR from riccardo, and Jaro is preparing some material. I think it is an important area 21:23:47 ... other things are more detailed 21:24:18 q+ 21:24:24 kcoyle: if we feel there are essential things we don't have time for we can ask for an extension, but we need to know what we are wanting to do 21:24:34 roba: 21:24:36 ack alejandra 21:25:04 ack roba 21:25:33 roba: the profiles ont - questions on attaching metadata props. we have an alignment to DCAT and we might make it a subClass of dcat:Resource 21:25:43 ...is this helpful as an implementation? 21:26:03 +q 21:26:20 ack alejandra 21:27:06 alejandra: I don't have the answer, but it would be helpful since we think of dcat:Resource as an abstract class , an extension point 21:27:27 dsr: I will try to formulate the question and ask 21:27:52 kcoyle: we need a drop-dead date for DCAT and then a gap analysis to determine if we need an extension 21:28:13 ... we are well organised re: DCAT 21:28:28 topic: Profile Vocabulary 21:28:30 RRSAgent, draft minutes v2 21:28:30 I have made the request to generate https://www.w3.org/2019/03/05-dxwg-minutes.html AndreaPerego 21:28:30 ...profiles vocab has some significant issues still. 21:29:02 ... the addition of roles, which we voted on, and fixing definitions (makx referred to some time back) 21:29:31 ... we can use this issue to discuss it 21:29:51 https://github.com/w3c/dxwg/issues/755 21:30:22 ... these are 2 things we would like to get into the next draft as they will be explanatory. How do we do it? 21:30:27 q+ 21:30:36 ack ncar 21:31:03 q+ 21:31:17 ncar: we are poised to add the roles to the doc, we just need to determine which ones we put in the doc. we are still determining the names for roles 21:31:44 istribution, not resource 21:32:03 ... we need to work through the implications of making a profile a subClass of dcat:Resource 21:32:19 ... we are trying to work out if we can reuse more than we did in the past 21:32:49 kcoyle: the question is how we do this - it needs plenty of discussion with the largest group possible. Github? 21:33:15 ncar: that is a good idea. The other option is a discussion within a drafting sprint 21:33:16 ack roba 21:33:44 * I've put a Doodle Poll up for a sprint 21:34:22 roba: I asked ncar if we can have a sprint, and we can include this discussion in that. We can use the googledoc mode, but if people can't join that then the github issues are there and people can contribute to that if they cannot manage to be in the sprint 21:35:02 kcoyle: we need a clean github issue without other stuff, ideally 21:35:29 roba: we have decided to do that 21:35:48 q+ 21:35:51 About the spreadsheet for comments (https://docs.google.com/spreadsheets/d/1Jo8pMcYbJBl8jNezeHTml7HfeqO8fnTnc3swVXEiS3I/edit#gid=0), I think it should include a column with the document they refer to (DCAT, PROF Voc, ProfGui, Conneg) 21:35:59 kcoyle: we only decided that we include the roles, but we haven't discussed the specifics of which roles to include 21:36:02 ack ncar 21:36:23 ncar: that is exactly what we need to discuss. 21:36:30 ok make a clean issue for the roles definitions 21:36:42 kcoyle: these are roles that ncar and roba have discussed, but have others? 21:36:57 ncar: simon cox has contributed, 21:37:00 roles have been exposed in examples in FPWD 21:37:11 will make the issue now 21:37:52 actiion: roba to open new issue seeded with list of roles and definitions and ask for comment 21:38:00 action: roba to open new issue seeded with list of roles and definitions and ask for comment 21:38:01 Created ACTION-307 - Open new issue seeded with list of roles and definitions and ask for comment [on Rob Atkinson - due 2019-03-12]. 21:38:25 ncar: other roles can be added later 21:38:42 kcoyle: we can mention OWA in the doc in context of roles 21:38:58 ... we don't need to define the extension mechanism 21:40:20 ncar: this is the issue I have been against, why I've thought we needed an explicit roles definition so that people look elsewhere for them. I've been trying to encourage people to use their own roles rather than just relying on what is included 21:40:47 kcoyle: we want the roles in the next draft to elicit comments, not to include them in the vocab. 21:41:03 ... they can be just a bullet list in the HTML doc 21:41:26 ... We have done that in other docs. e.g. DCAT with examples of mappings 21:41:52 q+ 21:41:59 ... we give a taster in the doc, purely to stimulate the reader to go and look at the full piece (which is elsewhere) 21:43:20 ... there are other substantial comments about the profiles vocab, including that it might be formally aligned with DCAT. So there is a lot to do. At what point do we have sufficient issues resolved and how do we show that we have addressed the issues, even if we haven't resolved them all? 21:43:37 ack ncar 21:44:01 ncar: we have tagged 34 open issues with 2ndPWD. we are unlikely to get through those soon 21:44:43 ... makx issue #755 serves as a listing of all the definitions made elsewhere. If we do that and the roles issue, then that is a good 2ndPWD candidate 21:44:47 PROF 2PWD Issue list: https://github.com/w3c/dxwg/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22PROF+2PWD%22 21:45:16 dsr: why are these things not concluded? 21:45:30 kcoyle: there is plenty of discussion but we didn't act on them 21:45:32 i think the vast majority of issues are easy to resolve. 21:45:35 q+ 21:45:55 ... we haven't determined how substantial they are, though some look like they are 21:46:27 roba: we made 1 change to the model, but the rest is about explanation, packaging, naming of properties, etc. 21:46:51 ... many issues come down to style, editorial clean-up etc. 21:47:11 ... formalising the alignment to DCAT might resolve issues 21:48:03 kcoyle: I disagree in that i see many substantive issues. if they are simple they should be resolved asap 21:48:22 roba: I think many are editorial and a sprint will help 21:48:50 kcoyle: many comments are on the content of the diags. e.g. ShEx community comments 21:49:25 q+ 21:49:30 ... PWinstanley and kcoyle sent a list of issues that need attention 21:49:38 https://github.com/w3c/dxwg/issues/572 21:49:48 roba: ncar generated a list of issues 21:50:08 kcoyle: if they are easy then please get them sorted quickly 21:51:42 ncar: we have agreed in this meeting an approach for roles, and in an email last night I provided an approach to the comments in that email from PWinstanley and kcoyle 21:52:23 kcoyle: they are small issues, so complete them . we can't move forward with 82 issues being open 21:53:06 ... List the 'substantial' issues to ensure that we get these covered 21:54:09 ... we need a list to ensure that we can track the issues individually 21:54:37 q+ 21:55:21 roba: there is the ontology, the formalism. 21:55:51 kcoyle: which of the 82 github issues are 'substantial', not just a small editorial effort? 21:56:48 ok will add issue numbers to sprint agenda 21:57:26 dsr: this is where having everything on a spreadsheet makes life easier to manage 21:57:53 kcoyle: we will need to add to the spreadsheet issues brought up by WG members 21:58:20 feel free to give us a list of issue numbers 21:58:32 ... they are not all externally generated. The external ones have a specific requirement to be answered formally 21:58:43 +q 21:58:58 q- 21:59:01 ack roba 21:59:01 q- 21:59:36 ack ncar 22:00:49 ncar: one source of confusion was that in the orginal email from Tom Baker have many points that were converted into github issues. They are all there, afaik. Please can others double check 22:01:02 kcoyle: that is detailed in the email from PWinstanley and kcoyle 22:01:41 ... I will check this against the issues and let you know if there are any gaps. 22:02:23 i responded to your email of 4 march agreeing - and those issues are the focus of the sprint - its hard to see wjat else we can do.. 22:02:24 kcoyle: there are lots of meetings - it is difficult for people, but if you can manage to join in the profiles vocab then please do 22:02:35 rrsagent, please create minutes v2 22:02:35 I have made the request to generate https://www.w3.org/2019/03/05-dxwg-minutes.html kcoyle 22:02:47 bye 22:02:48 bye! 22:02:51 present- 22:02:52 Bye 22:02:54 RRSAgent, draft minutes v2 22:02:54 I have made the request to generate https://www.w3.org/2019/03/05-dxwg-minutes.html AndreaPerego