20:53:42 RRSAgent has joined #dxwgdcat 20:53:42 logging to https://www.w3.org/2018/02/07-dxwgdcat-irc 20:58:31 chair: SimonCox 20:58:49 regrets: JaroslavPullman 21:01:05 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2018.02.07 21:03:51 Simon has joined #dxwgdcat 21:04:33 StijnGoedertier_AIV has joined #dxwgdcat 21:04:41 present+ 21:06:17 Hi Stijm 21:06:43 Doesn't seem to be anyone else here - not sure what the confusion is, I guess I made a mistake somewhere 21:07:04 s/Stijm/Stijn/ 21:07:11 3 gave their regrets https://www.w3.org/2017/dxwg/wiki/Meetings:DCAT-Telecon2018.02.07 21:07:29 Hi Simon 21:07:35 Regrets: Dave Browning, Makx Dekkers, Peter 21:08:12 I'll wait 3 more minutes then we'll give up - sorry 21:09:21 ok, I see Andrea Perego connecting 21:09:51 AndreaPerego has joined #dxwgdcat 21:12:01 NicholasCar has joined #dxwgdcat 21:14:17 present+ AndreaPerego 21:14:22 present+ 21:14:33 regrets: Jaroslav Pullmann 21:14:50 scribe: AndreaPerego 21:14:55 scribenick: AndreaPerego 21:14:59 chair: SimonCox 21:15:26 RRSAgent, draft minutes v2 21:15:26 I have made the request to generate https://www.w3.org/2018/02/07-dxwgdcat-minutes.html AndreaPerego 21:15:56 Topic: Approve last week minutes 21:16:09 https://www.w3.org/2018/01/31-dxwgdcat-minutes 21:16:15 +1 21:16:17 +1 21:16:29 +1 21:17:11 +1 21:17:25 resolved: Last meeting minutes approved 21:17:49 https://w3c.github.io/dxwg/dcat/ 21:18:02 topic: Actions from last meeting 21:18:18 SimonCox: [explaining work done in GH] 21:18:30 https://github.com/w3c/dxwg/tree/simon-dcat-doc-issues 21:20:01 SimonCox: Relevant PR: https://github.com/w3c/dxwg/pull/102 21:20:36 Use this syntax to link a document issue to GitHub issue

21:20:49 RRSAgent, make logs world 21:20:57 RRSAgent, draft minutes v2 21:20:57 I have made the request to generate https://www.w3.org/2018/02/07-dxwgdcat-minutes.html AndreaPerego 21:21:19 SimonCox: This makes GH embed a link into a GH issue. 21:21:56 regrets+ Dave Browning, Makx Dekkers, Peter 21:22:04 topic: Review requirements 21:22:10 https://github.com/w3c/dxwg/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Adcat+label%3Arequirement+ 21:23:08 Encourage people to continue reviewing tags on github issues 21:23:09 SimonCox: A few people went through the GH issues. Labelling improved a bit (good!). We are making some progress. I encourage people to work this out. 21:23:51 SimonCox: I was hoping to discuss some of these issues. Alejandra and I identified some of them. 21:23:58 ... One is #33 21:24:04 https://github.com/w3c/dxwg/issues/53 21:24:16 s/#33/#53/ 21:24:56 SimonCox: There's some discussion on this issue. 21:25:25 q 21:25:25 ... My understanding is that in RDF world this means HTTP URIs. 21:25:36 ack NicholasCar 21:26:11 q+ 21:26:21 ack AndreaPerego 21:26:59 AndreaPerego: main issue is that a number of other identifier systems are used for dat acitation, publishers, etc 21:27:16 ... e.g. DataCite supports quite a few identifier systems 21:27:27 ... DCAT-AP also discussed this at length 21:27:44 ... agencies want to use their internal identifiers, not necessarily URIs 21:28:06 ... may connect datasets using SPARQL queries, etc not just URIs 21:28:30 ... what is needed by different communities is ability to specify different kinds of identifiers, and their *type* 21:28:45 ... need to indicate that a string _is_ and identifier 21:28:51 s/and/an/ 21:29:26 ... whenenver possible make identifiers resolvable by _encoding_ them as URIs, but this does not apply to all identifier systems 21:29:45 ... situation is quite complicated 21:29:46 q+ 21:30:08 there are some other URI systems, but not necessarily resolvable 21:30:19 ... case sensitivity is also an issue 21:30:21 q+ 21:30:41 ... proposal made in UC is to try to address both issue 21:30:50 ... 1. encode as http URIs where possible 21:31:22 ... 2. encode as a string using dct:identifier property, and note the type of the identifier using ^^type indicator 21:31:51 ... Makx also suggests adms:identifier 21:32:37 ... UC is about _providing guidance_ where standard RDF http URI does not apply 21:32:38 q- 21:32:58 ... also for how to use SPARQL queries, for example 21:33:33 ack NicholasCar 21:33:49 NicholasCar: We had the same issue with physical samples. 21:34:08 NicholasCar: similar issues with identifier off-web resources which have local/scoped identifiers 21:34:18 ... The critical ID was the URI, since we have already other IDs as DOIs. 21:34:26 ... recommendation there is to supplement identifier field with identifier-type 21:34:44 ... need a comprehensive schema for alternative identifiers 21:35:08 q+ 21:35:18 ... [missed] 21:35:30 ack sim 21:35:34 ack SimonCox 21:35:51 SimonCox: Makx suggested looking at ADMS. 21:35:54 https://www.w3.org/TR/vocab-adms/#identifier 21:36:07 It would be beneficial to have a comprehensive handling of identifiers, inc. type and other properties, as we need to use them in many situations, not just DCAT 21:36:12 ... There's an adms:Identifier class there. 21:36:51 Yes, ADMS seems to mostly do it! 21:37:03 ... It is based on UN/CEFACT. So, this appear that fullfills the proposal you made, AndreaPerego. 21:37:11 q+ 21:37:17 ack AndreaPerego 21:37:29 Adopt or clone adms:Identifier 21:38:08 AndreaPerego: alternative proposals: PRISM, BIBO, 21:38:27 ... specific fields for well-known identifier schemes, e.g. bibo:DOI 21:39:00 ... these are already used by some important services, e.g. crossRef 21:39:23 ... need to explain how these different approaches map to each other 21:39:56 SimonCox: We should drop some of this discussion in GH. 21:40:04 ACTIO: SimonCox to drop identifeir discussion into GitHub issue 21:40:17 ACTION: SimonCox to drop identifeir discussion into GitHub issue 21:40:17 Sorry, but no Tracker is associated with this channel. 21:40:38 trackbot, associate this channel with #dxwg 21:40:51 q+ on additional guidance on the type of HTTP IRIs for a dcat:Dataset vs dcat:CatalogRecord 21:40:55 ACTION: SimonCox to drop identifeir discussion into GitHub issue 21:40:55 Sorry, but no Tracker is associated with this channel. 21:41:12 s/ACTION: SimonCox to drop identifeir discussion into GitHub issue// 21:41:15 ack StijnGoedertier_AIV 21:41:15 StijnGoedertier_AIV, you wanted to comment on additional guidance on the type of HTTP IRIs for a dcat:Dataset vs dcat:CatalogRecord 21:41:16 s/ACTIO: SimonCox to drop identifeir discussion into GitHub issue// 21:41:39 +q 21:41:49 StijnGoedertier_AIV: use CatalogRecord as proxy for off-web resources 21:42:01 ? 21:42:47 SimonCox: Could you provide a scenario? 21:42:56 ack NicholasCar 21:43:58 NicholasCar: I think the issue StijnGoedertier_AIV mentioned was about what you get from an HTTP URI - the thing, or its description thereof. 21:44:24 StijnGoedertier_AIV: I have this doubt because of the definition of a catalogue record. 21:44:40 q+ 21:44:52 ack AndreaPerego 21:45:25 AndreaPerego: relationship between CatalogRecord and Dataset needs clarification 21:46:18 ... in the CatalogRecord can attach metadata about the metadata - e.g. who created the record, in contrast to metadata about the dataset, e.g. topic, publisher, etc 21:47:18 ... is standard registry model (e.g. ISO 19135, Linked Data Registry, ISO 11179) 21:47:36 ... where registration information is separate from the dataset description 21:47:50 clear to me 21:48:56 yes, I meant that two URIs for Cat. Rec. & Dataset are not used in practice, despite the DCAT option for it 21:49:13 ... not sure any system actually assigns separate URIs for catalogue record and metadata entry 21:49:22 q+ 21:50:12 ack SimonCox 21:50:20 SimonCox: The Linked Data Registry actually can do that. 21:50:30 http://registry.it.csiro.au/ 21:50:52 Topic: dataset type https://github.com/w3c/dxwg/issues/64 21:51:31 SimonCox: There was some discussion on this. 21:51:41 ... A number of vocabularies have been mentioned. 21:53:01 ... Issue #95 notes that dcat:Dataset is made a subclass of dctype:Dataset, and the latter is just one of the DCType classes that could be considered as dcat:Dataset's. 21:53:27 https://github.com/w3c/dxwg/issues/98 21:53:33 ... So, we should probably relax this. Moreover, dctype:Dataset has a quite weak definition. 21:53:51 agreed 21:53:53 ... The proposal is to remove the subclass axioms. 21:53:57 +1 from me. 21:54:05 +1 for me as well 21:54:11 +1 21:54:24 +1 21:54:55 resolved: Drop subclass axiom from dcat:Dataset 21:55:40 SimonCox: Related issue was how to associate dct:type for soft typing. 21:56:27 ... There's a meta-issue on whether we should use more OWL axiomatisation to specify which properties should be used for which classes. 21:56:46 Should we use OWL to bind predicates to classes? https://github.com/w3c/dxwg/issues/105 21:57:18 DCAT 1.0 just says "The following properties are recommended for use on this class" 21:57:18 SimonCox: Makx and Andrea tend to support the idea of not using it. 21:57:50 so just add dct:type to that list 21:58:32 SimonCox: So, this way we have more or less resolved issue #64 21:58:34 with some indications of available type vocabularies 21:58:43 q? 21:58:53 +1 21:59:11 +1 21:59:11 +1 21:59:12 +1 Makes DCAT most broadly usable 21:59:18 (no other comments) 22:00:00 resolved: Include dct:type in the list of properties recommended for dataset 22:00:50 resolved: Include dct:type in the list of properties recommended for dataset, list some of the type vocabularies contributed in the GH issues. This resolves issue #64 22:01:20 I have 5 22:01:31 Topic: - https://github.com/w3c/dxwg/issues/95 22:02:00 AndreaPerego: domain of contactPoint is limited to Dataset 22:02:21 ... so can't be re-used in other context without entailment that they are a Dataset! 22:02:49 q+ 22:03:18 ... contactPoint is one of the most imporant roles encoded in metadata! 22:03:31 ... needs to be available in many places 22:04:22 ... what was it set this way??? 22:04:42 ack SimonCox 22:06:22 +1 22:06:29 +1 to remove the domain restriction 22:06:32 SimonCox: I am not very much in favour of setting domain restrictions on properties, since this reduces reusability. 22:06:33 +1 22:07:17 StijnGoedertier_AIV: I think it is still important to have a range for interoperability purposes. 22:07:39 relsolved: Drop domain restriction from dcat:contactPoint 22:07:41 Agreed - I will generate separate issue. 22:08:07 s/relsolved/resolved/ 22:08:15 RRSAgent, draft minues v2 22:08:15 I'm logging. I don't understand 'draft minues v2', AndreaPerego. Try /msg RRSAgent help 22:08:22 RRSAgent, draft minutes v2 22:08:22 I have made the request to generate https://www.w3.org/2018/02/07-dxwgdcat-minutes.html AndreaPerego 22:09:55 meeting: DXWG DCAT subgroup teleconference 22:09:57 RRSAgent, draft minutes v2 22:09:57 I have made the request to generate https://www.w3.org/2018/02/07-dxwgdcat-minutes.html AndreaPerego 22:10:26 present+ SimonCox 22:10:27 RRSAgent, draft minutes v2 22:10:27 I have made the request to generate https://www.w3.org/2018/02/07-dxwgdcat-minutes.html AndreaPerego 22:12:24 meeting adjourned 22:12:24 RRSAgent, draft minutes v2 22:12:24 I have made the request to generate https://www.w3.org/2018/02/07-dxwgdcat-minutes.html AndreaPerego 22:23:05 BTW, will you be at the RDA Plenary in Berlin? I'm still not sure I can make it. 22:23:40 s/BTW, will you be at the RDA Plenary in Berlin? I'm still not sure I can make it.// 22:24:31 trackbot, bye 22:24:32 trackbot has left #dxwgdcat 22:24:42 zakim, bye 22:24:42 leaving. As of this point the attendees have been StijnGoedertier_AIV, AndreaPerego, NicholasCar, SimonCox 22:24:42 Zakim has left #dxwgdcat 22:24:46 RRSAgent, bye 22:24:46 I see 2 open action items saved in https://www.w3.org/2018/02/07-dxwgdcat-actions.rdf : 22:24:46 ACTION: SimonCox to drop identifeir discussion into GitHub issue [1] 22:24:46 recorded in https://www.w3.org/2018/02/07-dxwgdcat-irc#T21-40-17 22:24:46 ACTION: SimonCox to drop identifeir discussion into GitHub issue [2] 22:24:46 recorded in https://www.w3.org/2018/02/07-dxwgdcat-irc#T21-40-55