19:45:23 RRSAgent has joined #dxwg 19:45:23 logging to https://www.w3.org/2018/07/10-dxwg-irc 19:45:40 rrsagent, make logs public 19:45:55 chair: PWinstanley 19:46:29 regrets+ AndreaPerego, Riccardo Albertoni 19:46:40 present+ 19:47:13 Meeting: DXWG Plenary - 2018-07-10 19:47:16 rrsagent, create minutes v2 19:47:16 I have made the request to generate https://www.w3.org/2018/07/10-dxwg-minutes.html PWinstanley 19:54:11 kcoyle has joined #dxwg 19:58:41 phila has joined #dxwg 20:01:47 Jaroslav_Pullmann has joined #dxwg 20:02:04 present+ 20:02:09 roba has joined #dxwg 20:02:14 present+ 20:02:20 antoine has joined #dxwg 20:03:26 annette_g has joined #dxwg 20:03:41 azaroth has joined #dxwg 20:04:18 present+ 20:04:23 present_ 20:04:27 present+ 20:04:31 present+ 20:04:32 SimonCox has joined #dxwg 20:04:32 present+ Rob_Sanderson 20:04:33 present+ 20:05:29 Ixchel has joined #dxwg 20:05:31 present+ 20:05:42 scribe: phila 20:05:46 scribeNick: phila 20:05:50 alejandra has joined #dxwg 20:05:51 Topic: Admin 20:05:58 https://www.w3.org/2018/07/03-dxwg-minutes 20:06:12 -> https://www.w3.org/2018/07/03-dxwg-minutes last week's minutes 20:06:19 Proposed: Accept last week's minutes 20:06:21 +1 20:06:24 +1 20:06:26 +1 20:06:29 +1 20:06:39 +1 20:06:39 +1 20:06:41 +1 20:06:43 present+ 20:06:49 Resolved: Accept last week's minutes 20:07:17 present+ 20:07:19 Topic: General principles 20:07:36 DaveBrowning has joined #dxwg 20:07:43 PWinstanley: Consensus and pluarism - a reminder to everyone that we have to operate in a consensual way 20:07:56 ... meaning being open to ideas from others. There can be more than one way f doing things 20:08:05 present+ 20:08:12 ... We're trying to create an output for a wide and diverse audience 20:08:25 PWinstanley: We can get a bit caught up in our own world a little 20:08:34 ... there can be more than one solution 20:09:08 PWinstanley: In the past we'd use the wiki and the public ML. 20:09:34 ... but now we tend to use GitHub and some of the conversation that would have gone through the issues early enough. 20:09:42 ... Not sure that mailing list bounces have been resolved 20:09:59 +q 20:10:01 kcoyle: The old emails are stored away... antoine noticed it... 20:10:29 SimonCox: I also had anyther experience this week when I was checking whether some mails from colleagues had appeared and no, they had bounce notices 20:10:52 phila: Suggest write to Gerald Oskoboiny 20:11:11 q- 20:11:16 PWinstanley: We'd have noticed it earlier if we weren't using GH so heavily 20:11:19 +q 20:11:29 PWinstanley: We can't be sure that GH will persist 20:11:48 q+ to note that W3C archives GH 20:11:49 ... whereas W3C's persistence policy is much stronger 20:12:07 PWinstanley: We need to make sure that we have some provision for persistence 20:12:09 q? 20:12:26 PWinstanley: We need to think about how we monitor and are open about getting input from GH 20:12:35 ... including people who are not members of the group 20:12:55 ack alejandra 20:12:56 ... Karen was investigating with W3C. It's up to us to decide how to deal with it. 20:13:43 alejandra: I've used in the past an integration between GH and Zenodo which is a persistent repo. CERN uses it. Zenodo assigns a DOI to everything assiged to it 20:13:50 PWinstanley: Do it's a deep copy? 20:14:05 alejandra: It contains a history as long as you include all the GH history 20:14:21 ... We should so regular releases of the GH repo every so often 20:14:28 q+ to rant about DOIs 20:14:41 alejandra: We could use Zenodo as a persistent repo 20:14:52 ack azaroth 20:14:52 azaroth, you wanted to note that W3C archives GH 20:15:19 azaroth: For the annotation WG, and the JSON-LD WG, W3C has an archiving implementation that the team contact can set up 20:15:27 ... It mirrors the entire state of the repo weekly 20:15:37 including the issues and wiki? 20:15:42 PWinstanley: And it keeps it within W3C 20:15:47 azaroth: Yes. 20:15:52 q? 20:16:02 ack phila 20:16:02 phila, you wanted to rant about DOIs 20:16:04 ... Probably a good idea to talk to DSR about that. I dare say Ivan could help 20:17:58 action: dsr to set up regular GitHub dump to w3.org 20:18:00 Created ACTION-145 - Set up regular github dump to w3.org [on Dave Raggett - due 2018-07-17]. 20:18:15 Topic: How to acknowledge and record comments that come via GH 20:19:04 q+ 20:19:09 ack SimonCox 20:19:19 PWinstanley: We need a formal approach to recording and making sure that we acknowledge that we're taking the suggestion into account 20:19:35 SimonCox: That means being sensitive to who is and who isn't a member of the WG 20:19:44 ... two in particular 20:20:08 PWinstanley: Because they're not members of a W3C MO, or an IE, they've not signed away IP 20:20:17 q+ 20:20:17 ... andreas kuchartz and Jakub Klimek 20:20:31 q- 20:21:28 q+ 20:22:11 q+ to suggest addition to readme.md noting IP arrangements 20:22:28 phila: IP is a non-trivial point. No easy answer - but you need to be mindful that the consequences, in extremeley rare circs can be very dangerous 20:22:30 ack SimonCox 20:22:30 SimonCox, you wanted to suggest addition to readme.md noting IP arrangements 20:22:31 ack SimonCox 20:22:53 SimonCox: A modicum of coverage is to add something to the readme.md? 20:23:02 ... Drawing attention to the Ip expectations 20:23:06 phila: +1 20:23:17 +1 20:23:21 SimonCox: It's not secure, but it draws attention to the Ip arrangements 20:23:25 +1 20:24:27 action: dsr to look into adding a disclaimer for IP in the GitHub readme to cover the WG for contributions by non-members as possible solution - or find a better solution 20:24:29 Created ACTION-146 - Look into adding a disclaimer for ip in the github readme to cover the wg for contributions by non-members as possible solution - or find a better solution [on Dave Raggett - due 2018-07-17]. 20:25:02 SimonCox: Was there an immediate action to contact the 2 active contributors? 20:25:20 q+ 20:25:26 ack kcoyle 20:25:51 +q 20:26:01 action: SimonCox to write to Andreas Kuchartz and Jakub Klimek drawing their attention to the IP policies at W3C wrt their contributions 20:26:03 Created ACTION-147 - Write to andreas kuchartz and jakub klimek drawing their attention to the ip policies at w3c wrt their contributions [on Simon Cox - due 2018-07-17]. 20:26:14 ack alejandra 20:26:29 ack alejandra 20:26:47 alejandra: How doe sit work that we invite public comments and then people that suggest something ... may not be part of the WG 20:27:23 s/doe sit/does it/ 20:28:13 phila: It's a conflict... 20:28:21 Topic: Action items 20:28:46 action-110 20:28:47 action-110 -- Karen Coyle to Find better wording for 216 especially "extend" -- due 2018-05-15 -- OPEN 20:28:47 https://www.w3.org/2017/dxwg/track/actions/110 20:28:54 kcoyle: Ongoing 20:28:57 action-129 20:28:57 action-129 -- Alejandra Gonzalez Beltran to Create new use case and requirements for more complex situation -- due 2018-06-19 -- OPEN 20:28:57 https://www.w3.org/2017/dxwg/track/actions/129 20:29:05 alejandra: I need to contact antoine 20:29:15 action-141 20:29:15 action-141 -- Phil Archer to Add his wording to the profiles document -- due 2018-07-10 -- OPEN 20:29:15 https://www.w3.org/2017/dxwg/track/actions/141 20:29:21 close action-141 20:29:21 Closed action-141. 20:30:01 Topic: DCAT sub group reports 20:30:28 SimonCox: Activity has reduced somewhat in the last month. The bulk of the activity on the DXWG has shifted to profiles. 20:30:45 ?+ 20:30:46 ... Most of the discussion has been around new use case for loosely connected files 20:30:54 q? 20:30:59 SimonCox: It was recognised as an important use case 20:31:02 +q 20:31:05 ... Proposed resolutions not yet finalised 20:31:26 ... Mechanism to geneate UCs is worked examples. 20:31:41 SimonCox: FPWD has been released for a few months - almost no comments 20:31:54 ... That's a concern since it suggests that the work is not needed 20:32:13 ... Problem with the comments mailing list came to light when we asked for comments. 20:32:43 ... I asked my colleagues to make comments and express contentment with various things. That drew attention to the comment list problem. 20:32:47 ack kcoyle 20:33:09 kcoyle: Does the WG have any sense of when the next draft might be stabe? 20:33:21 s/stabe?/stable? 20:33:33 SimonCox: We've not been planning towards the next draft, just working through issues 20:33:40 s/geneate/generate/ 20:33:44 ... Settling on a tight audited change process, using GH tracke 20:34:07 SimonCox: Changes to the visible Editor's draft aren't rapid. Maybe changes every 2-3 weeks 20:34:21 ... might come a point where editors will need to do a significant clean up 20:34:25 ... Not at that stage yet 20:34:59 ... changes are incremental. Doc is in good shape, currently better that FPWD, so we could release a be version 20:35:10 ... Hasn't been on our agenda. 20:35:26 PWinstanley: For TPAC, only a few weeks left to get the early bird rate 20:35:49 ... Also October is the start of Q4 and our timetable says we'll be making progress by then. The clock is ticking... 20:36:23 Topic: Profiles Guidance 20:36:23 +q 20:36:56 roba: There hasn't been... the agenda is being driven by Ruben and Lars who weren't available last time 20:37:03 ack kcoyle 20:37:35 kcoyle: I went through, trying to gather what we have discussed that could end up being content for the doc. 20:37:47 ... I could put that on the wiki but it's incomplete 20:37:55 ... There are diagrams, GH issues etc. 20:38:06 ... Might make it clearer what needs to happen next. 20:38:18 PWinstanley: You'd do the wiki cf a Google doc 20:38:25 kcoyle: It's very wikiable 20:38:45 +1 20:38:49 +1 20:38:55 PWinstanley: That would be very kind 20:39:01 kcoyle: OK, I'll get it into shape 20:39:26 ... I can put it on the wiki quickly but it won't quickly be complete 20:39:28 q+ 20:39:46 ack roba 20:39:59 q+ 20:40:06 roba: Thanks Karen. I'm standing ready to help look at some of the content but I don't feel I'm ready to set the scope. 20:40:33 ack antoine 20:40:40 ncar has joined #dxwg 20:41:30 antoine: Organising the calls for this group... maybe Rob can answer this... I understood that the guidance sub group would merge with the profile nego group - but this needs a definite time that works for everyone 20:41:44 roba: We're a bit of a hostage to Ruben and Lars' schedules 20:41:54 .., Maybe we should do alternate weeks 20:42:41 ... I think it would be good if someone could step up and organise this. I'd do it but I'm now in this WG on my own time and not on behalf of OGC. 20:42:47 I can help 20:43:01 antoine: So set it up on the alternate week? OK, I can look at setting that up 20:43:10 yes! 20:43:15 PWinstanley: ncar has offered to help 20:43:41 ncar: I'm at a provenance conference in London 20:43:52 ... I have a proper remit from my agency for this so I can spend time on it 20:44:25 action: Carr to work with Roba and Antoine to establish meeting schedule for profile guidance doc 20:44:26 Error finding 'Carr'. You can review and register nicknames at . 20:44:34 action: ncar to work with Roba and Antoine to establish meeting schedule for profile guidance doc 20:44:35 Error finding 'ncar'. You can review and register nicknames at . 20:44:43 nicholascar (Nicholas Car) 20:44:44 action: nicholas to work with Roba and Antoine to establish meeting schedule for profile guidance doc 20:44:48 Created ACTION-148 - Work with roba and antoine to establish meeting schedule for profile guidance doc [on Nicholas Car - due 2018-07-17]. 20:45:04 Topic: UCR and requirements for conneg and profiles 20:45:10 PWinstanley: There's a link... 20:45:16 RRSAgent: make logs public 20:45:41 PWinstanley: There's a thing from Andrea. There are a couple of PRs that have been around for a long time 20:45:56 Meeting: DXWG weekly 20:45:59 +q 20:46:05 PWinstanley: I think this is something Ale and I should look at 20:46:33 That's correct 20:46:34 SimonCox: I thought those PRs that Andrea was drawing attention to were related to UCs that were accepted but not yet put into the UCR 20:46:59 SimonCox: I believe that's the problem. They're really on the UCR editors to act on 20:47:21 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2018.07.10 20:47:23 .. o.k. thank you for this pointer, we'll care of them 20:47:27 PWinstanley: I guess I should look at that 20:47:37 alejandra: You and Jaro, and Rob. 20:47:51 Jaroslav_Pullmann: Quite a massive clean up needed 20:47:55 s/You and/ 20:48:04 ... No need for an action item, it's our normal responsibility 20:48:33 action: Jaroslav to resolve the outstanding pull requests for the UCR from Andrea 20:48:37 Created ACTION-149 - Resolve the outstanding pull requests for the ucr from andrea [on Jaroslav Pullmann - due 2018-07-17]. 20:49:29 Requirement: "Profiles may add to or specialise clauses from one or more base specifications. Such profiles inherit all the constraints from base specifications.” ID37 [ID39] #238 20:49:50 PWinstanley: is this still under discussion? 20:49:52 kcoyle: Yes 20:50:03 q+ 20:50:12 q+ 20:50:18 ack alejandra 20:50:19 q- 20:50:22 ack phila 20:50:28 ack phila 20:50:45 ack roba 20:50:59 phila: Why is that req contentious? 20:51:12 PWinstanley: It isn't, we just haven't voted on it yet 20:51:28 +q 20:51:36 ack kcoyle 20:51:42 roba: We seem to be being asked for evidence for it. The word inheritance seems to be a problem. 20:52:13 kcoyle: There was a lengthy discussion... some folks were talking about dependency rather than inheritance 20:52:23 q+ 20:52:35 q+ 20:52:35 ack roba 20:52:45 ... people want to have everything available without having to hop up the inheritance tree to get there 20:52:56 +1 to roba 20:52:58 q- 20:53:00 roba: OK, but that's a separate requirement at implementation time 20:53:06 +1 to RobA as well 20:53:22 +1 flattening is an implementation/packaging issue 20:53:30 PWinstanley: Do people want a rewording or just go ahead with what we have? 20:53:41 q? 20:54:00 +1 20:54:01 +1 20:54:03 +1 20:54:08 +1 for voting 20:54:25 Proposed: Accept the Requirement "Profiles may add to or specialise clauses from one or more base specifications. Such profiles inherit all the constraints from base specifications.” ID37 [ID39] #238 20:54:29 +1 20:54:31 +1 20:54:31 +1 20:54:33 +1 20:54:33 +1 20:54:34 +1 20:54:35 +1 20:54:37 +1 20:54:50 Resolved: Accept the Requirement "Profiles may add to or specialise clauses from one or more base specifications. Such profiles inherit all the constraints from base specifications.” ID37 [ID39] #238 20:55:20 12.1 Requirement: a vocabulary or data model can be a profile of several other vocabularies or data models at once 20:55:34 sRequirement: "Profiles/Requirement - "Profiles/ 20:55:41 s/Requirement: "Profiles/Requirement - "Profiles/ 20:55:41 q+ 20:56:11 ack annette_g 20:56:34 annette_g: I think we were concerned that the phrasing was a req about a data model rather than a profile 20:56:36 +1 20:56:38 ... It feels inside out 20:56:49 q+ 20:56:50 q+ 20:56:54 +q 20:56:55 a profile is a sort of data model surely? 20:56:56 ack antoine 20:57:05 q- 20:57:20 q+ 20:57:28 antoine: It was discussed in the context of switching from one req to another 20:57:52 "A profile can be a profile of several vocabularies or data models at the same time" 20:58:05 ... to react to Annette, I woldn't mind losing vocab in the first part. Sometimes I use data model where people use profile 20:58:13 ack SimonCox 20:58:18 ... But if it's easier, I;m happy with Karen's phraseology 20:58:27 SimonCox: I was going to make a similar point 20:58:40 q- 20:58:43 ... I find the distinction between a data model and a profile difficult 20:58:57 ... Every model os a set of constraints on having no model 20:59:08 "A profile can be a profile of several vocabularies or data models at the same time" 20:59:09 How about: A profile can constrain several ... ? 20:59:11 Proposed: Accept "A profile can be a profile of several vocabularies or data models at the same time" 20:59:13 q+ 20:59:19 ack azaroth 20:59:31 q+ 20:59:37 ack SimonCox 20:59:41 azaroth: Say a profile can be a profile is tautology 20:59:47 +1 20:59:47 q+ 20:59:49 q+ 20:59:51 SimonCox: Dependencies is my favoured word 21:00:07 ... Any model or profile potentially builds on other stuff 21:00:07 "A profile can have dependencies on several vocabularies or data models at the same time" 21:00:07 I'm fine with dependency (or anything that isn't a circular reference) 21:00:27 "A profile can be dependent on several vocabularies or data models at the same time" 21:00:30 "a profile can have multiple base specifications" 21:00:33 "A profile can be dependent several vocabularies or data models at the same time" 21:00:43 Q? 21:00:48 ack antoine 21:01:10 Note: the OGC model for specifications essentially is a model for (non-circular!) dependencies 21:01:13 q+ to be -1 on base specifications 21:01:14 antoine: I can live with the formulation... I think I prefer Annette's suggestion of using 'base' 21:01:22 the original UCR used these words: Profiles may inherit clauses from one or more parent profiles 21:01:29 ""A profile can be based on several vocabularies or data models at the same time" 21:01:30 q- 21:01:34 .. is not this the opposite of the original meaning, profile as constraint of a model (not depending on this model?) 21:01:36 PWinstanley: Anything we can agree now? 21:01:41 Base Specification implies it does not itself have dependencies, to me 21:02:06 roba: I think we have the same requirement in a different phrasing in the UCR already 21:02:42 q+ 21:02:44 PWinstanley: A profile can be based on several data models or vocabs at the same time? 21:02:49 ack roba 21:02:52 roba: Inherit clauses from... 21:02:56 I don't like dependency: things can depend on all kinds of things. Derivation is better 21:03:04 +1 to azaroth - base does imply something "pureP 21:03:13 ack antoine 21:03:14 s/P/" 21:03:53 antoine: If we are not yet ... we are looking at reqs in the Europeana context 21:04:03 present- 21:04:08 I like Karen's wording 21:04:12 kcoyle: I think we agree on the principle, but not the wording 21:04:27 +1 @azaroth - thats exactly how modelled in profileDesc - not sure yet if useful :-0 21:04:39 agree with kcoyle 21:04:47 proposal: we accept 12.1 in principle but acknowledge that it may need rewording 21:04:52 +1 21:04:53 +1 21:04:54 +1 21:04:57 +1 21:04:58 +1 21:04:59 +1 21:05:01 +1 21:05:07 resolved: we accept 12.1 in principle but acknowledge that it may need rewording 21:05:07 +1 21:05:09 +1 21:05:18 RRSAgent, draft minutes v2 21:05:18 I have made the request to generate https://www.w3.org/2018/07/10-dxwg-minutes.html phila 21:05:28 PWinstanley: Thanks everyone for being on the call. 21:05:34 ... Same time next week 21:05:36 bye! 21:05:38 bye all! 21:05:41 RRSAgent, draft minutes v2 21:05:41 I have made the request to generate https://www.w3.org/2018/07/10-dxwg-minutes.html phila 21:05:45 present-