19:36:15 RRSAgent has joined #dxwg 19:36:15 logging to https://www.w3.org/2020/09/22-dxwg-irc 19:36:25 rrsagent, make logs public 19:36:36 chair: PWinstanley 19:36:57 regrets+: antoine, riccardo 19:37:10 meeting: DXWG Plenary 19:37:21 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2020.09.22 19:37:30 rrsagent, create minutes v2 19:37:30 I have made the request to generate https://www.w3.org/2020/09/22-dxwg-minutes.html PWinstanley 19:37:36 present+ 19:58:00 AndreaPerego has joined #dxwg 19:58:07 present+ 20:02:07 Rachel has joined #dxwg 20:02:31 present+ Rachel 20:02:56 annette_g has joined #dxwg 20:05:48 present+ 20:05:53 scribe: annette_g 20:05:58 Ana has joined #DXWG 20:06:03 present+ 20:06:07 RRSAgent, draft minutes v2 20:06:07 I have made the request to generate https://www.w3.org/2020/09/22-dxwg-minutes.html AndreaPerego 20:06:20 scribenick: annette_g 20:06:34 proposed: accept minutes of last meeting 20:06:39 https://www.w3.org/2020/09/08-dxwg-minutes 20:06:42 +1 20:06:43 +1 20:06:48 +1 20:06:54 +1 20:07:00 +1 20:07:04 resolved: accept minutes of last meeting 20:07:08 RRSAgent, draft minutes v2 20:07:08 I have made the request to generate https://www.w3.org/2020/09/22-dxwg-minutes.html AndreaPerego 20:07:20 https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2020.09.22 20:07:30 topic: approve agenda 20:07:40 topic: TPAC 20:08:14 register and join in anything you want to. Our group will be pretty low key, doing a short breakout session. 20:08:46 PWinstanley: (above and here) anybody else have ideas for things they want to do? 20:08:49 Not from my side. 20:09:29 PWinstanley: the other thing in the admin area was the Process 2020, which we're now one week into. 20:09:32 topic: Process 2020 20:09:35 https://www.w3.org/2017/dxwg/wiki/Process2020Information 20:09:38 RRSAgent, draft minutes v2 20:09:38 I have made the request to generate https://www.w3.org/2020/09/22-dxwg-minutes.html AndreaPerego 20:09:58 PWinstanley: This is where I put a synopsis of the changes. 20:11:33 ... there's a little flexibility for making changes, some may be in the cards for DCAT v2 20:11:59 ... we would be kind of the guinea pigs if we do errata. 20:12:11 q+ 20:12:18 ack AndreaPerego 20:12:26 PWinstanley: please familiarize yourselves with knowing where it is, link off main page of the wiki 20:13:10 AndreaPerego: what has been done recently, the respec template has changed. One of the things we did was try to use it for the specification, but there were some bugs. 20:14:14 ... we can ask what the new version of the respec library does to the content that is automatically filled. There is no detailed description of the changes. 20:14:29 PWinstanley: we can ask PLH 20:14:38 ... I'll write and ask 20:14:56 topic: DCAT work 20:14:56 topic: DCAT 20:16:04 s/topic: DCAT// 20:16:07 RRSAgent, draft minutes v2 20:16:07 I have made the request to generate https://www.w3.org/2020/09/22-dxwg-minutes.html AndreaPerego 20:16:12 We met last week in the whole subgroup to discuss versioning. We took some actions, and we are now trying to draft an extended version of this section of DCAT. Discussion is still going on in GitHub. There will be some dramatic revision. 20:16:24 q+ 20:16:45 ack AndreaPerego 20:17:01 PWinstanley: yes, bikeshedding is one of these complicated issues. If you take the simple route, there's not a lot to say about it, otherwise it takes up a lot of the space of the rec. So we're thinking about how much goes in the rec and how much goes in primers. 20:18:19 AndreaPerego: Today Karen made an important comment. We recognize that versioning is very related to local practices. There is not a common definition of it. It depends on a lot of variables. On the other hand, leaving it out doesn't help. We at least want to have a definition that's helpful. 20:18:53 AndreaPerego: anybody who would like to chime in and comment, that would be more than welcom. 20:18:57 s/welcom/welcome/ 20:19:39 Current discussion on versioning: https://github.com/w3c/dxwg/issues/1251 20:20:08 q+ 20:20:21 PWinstanley: anything anyone else wants to discuss? 20:20:24 crickets 20:20:27 q- 20:20:33 topic: open actions 20:20:38 RRSAgent, draft minutes v2 20:20:38 I have made the request to generate https://www.w3.org/2020/09/22-dxwg-minutes.html AndreaPerego 20:22:47 PWinstanley: some of them should go in the primer. #381 is completely superseded by the new process; even the terminology is different. Are people happy to just close that? 20:23:21 crickets 20:23:31 PWinstanley: 428 has gone, hasn't it? 20:23:54 close action-428 20:23:54 Closed action-428. 20:24:10 close action-381 20:24:10 Closed action-381. 20:24:38 PWinstanley: 425, annette, this is what we're talking about with versioning. 20:25:51 annette_g: I have been in touch with colleagues to see if anyone was interested in contributing to workflows, but in vain 20:26:25 ... It seems to be that workflows are unique and getting standardised terms for the stages is not going to yield useful results 20:26:52 q+ 20:27:14 ... The workflow stages depend on the instruments used, the datasets, the techniques used, etc, and so the merits of establishing a core vocabulary to describe these is questionable 20:27:20 ack AndreaPerego 20:28:22 AndreaPerego: Based on what you said, I wonder whether we should look at versioning just for the final stage, when the data are published, instead of looking at what happens behind and before that. I have several examples of a dataset published on platforms where you can have different versions, you can update it with a new DOI. 20:29:15 ... the rationale is that the dataset may have a relationship to a specific publication. Do you think this would make sense? I understand probably it's more something that is not a concern for researchers. 20:29:52 q+ 20:30:45 yes 20:31:47 AndreaPerego: It may apply to published data. The researcher has to state that. We've had several cases where a dataset has been up for a while but we've changed the methodology, so the old dataset is deprecated and there is a new one. 20:31:51 right 20:31:54 ack PWinstanley 20:32:18 q+ 20:33:04 ack AndreaPerego 20:33:08 PWinstanley: There are connections with prov, where something was done to a dataset, what process, what the raw material was. To have an illustration of the types of vocabulary that could describe status is potentially useful in this space. 20:33:56 AndreaPerego: this is also what we plan to do. We hope to find patterns for these vocabularies and properties because sometimes the definition is not crystal clear. Trying to guide people is difficult. We are trying to study them to understand the relationships between derivation, revision, etc. 20:33:57 UKGOVLD Registry: https://github.com/UKGovLD/registry-core/wiki/Principles-and-concepts#status-and-life-cycle 20:35:09 ... for lifecycle and versionining there is an ISO standard, which is about the item registration--registries. This work has been reused by the UK government working group for their registry. That work is interesting. The documentation they provide is very interesting. An item needs to be approved, etc., the richest example I am aware of. 20:36:26 AndreaPerego: It's about the fact that these taxonomies are used by other organizations. One thing they support is to enable a specific version for a code release, to at least make sure the terms are there. It's very useful to see the workflow for the lifecyle. In my opinion, it can maybe be reduced depending on the use cases. 20:37:28 PWinstanley: That UK gov data working group registry got a couple of implementations in things like the meteorological office, CSIRO, and what have you, but I'm not aware of implementations that have really been pushed. It just seems to be things were people are just trying it out. Are you aware of anyone using it with higher energy? 20:38:04 AndreaPerego: ASPIRE registry is using it, but not the whole workflow. They are still out there but I guess something just didn't happen basically. 20:38:23 PWinstanley: yes, it's still useful archaeology. Some things are a bit ahead of their time. 20:38:27 s/ASPIRE/INSPIRE/ 20:38:31 s/ASPIRE/INSPIRE/ 20:38:33 q+ 20:38:40 ack AndreaPerego 20:39:03 https://inspire.ec.europa.eu/registry 20:39:37 AndreaPerego: I understand not everyone on the call knows what is INSPIRE. It's basically a registry providing access to ISO code lists for geospatial data. It is for environmental policies across Europe. 20:40:01 PWinstanley: Do we think the action can be closed now? 20:40:05 no objection here 20:40:06 +1 20:40:09 +1 20:40:15 close action-425 20:40:16 Closed action-425. 20:40:41 PWinstanley: we need a few more people to do more with open actions. 20:40:54 ... anything else people would like to say? 20:40:55 q+ 20:40:59 ack AndreaPerego 20:41:28 AndreaPerego: wanted to ask Rachel if she has interest in the work on DCAT, if there is something that she sees missing, needing elaboration? 20:42:44 Rachel: I'm still kind of trying to understand exactly what the use cases are, reading through the materials. I gave myself a month or so to get up to speed before jumping in. I do have experience in versioning of catalogs, but don't yet feel in a position to make suggestions or say what is missing. Maybe in a few weeks. 20:42:47 PWinstanley: Ana? 20:42:51 Ana: I'm okay 20:43:15 PWinstanley: let's meet again in a couple of weeks' time. Don't forget about TPAC stuff 20:43:20 Thanks, and bye! 20:43:22 Thank you 20:43:28 RRSAgent, draft minutes v2 20:43:28 I have made the request to generate https://www.w3.org/2020/09/22-dxwg-minutes.html AndreaPerego 20:43:29 rrsagent, create minutes v2 20:43:29 I have made the request to generate https://www.w3.org/2020/09/22-dxwg-minutes.html PWinstanley 20:43:29 thank you! 20:49:53 annette_g has joined #dxwg 22:58:02 Zakim has left #dxwg