20:54:28 RRSAgent has joined #dxwg 20:54:28 logging to https://www.w3.org/2018/02/06-dxwg-irc 20:54:30 RRSAgent, make logs public 20:54:30 Zakim has joined #dxwg 20:54:32 Meeting: Dataset Exchange Working Group Teleconference 20:54:32 Date: 06 February 2018 20:55:54 present+ 21:00:10 dsr has joined #dxwg 21:00:18 roba has joined #dxwg 21:00:21 SimonCox has joined #dxwg 21:01:38 annette_g has joined #dxwg 21:02:14 present+ 21:02:19 Jaroslav_Pullmann has joined #dxwg 21:02:20 present+ 21:02:30 present+ 21:02:43 present+ 21:02:59 NicholasCar has joined #dxwg 21:03:14 present+ 21:05:30 scribe: SimonCox 21:05:53 Makx has joined #dxwg 21:06:06 topic: admin 21:06:18 https://www.w3.org/2018/01/30-dxwg-minutes 21:06:29 Ixchel has joined #dxwg 21:06:29 present+ 21:06:42 TopiC: approve minutes of last meeting 21:06:44 present+ Makx 21:06:49 +1 21:06:50 PROPOSED: approve last week's minutes 21:06:56 +1 21:07:03 +1 21:07:11 +1 21:07:12 RESOLVED: approve last week's minutes 21:07:12 +1 21:07:38 Agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2018.02.06 21:07:50 Chair: kcoyle 21:08:12 TOPIC: UCR comments 21:08:25 Need to understand and respond to comments 21:08:51 ... UCR editors are traffic cops for this 21:08:58 q? 21:09:16 roba: sent proposal for how to respond to list 21:09:31 ... no discussion yet 21:09:36 q+ 21:09:39 ... two weeks ago 21:09:59 DaveBrowning has joined #dxwg 21:10:07 Ixchel: was that my email? 21:10:42 q+ 21:10:52 present+ 21:11:06 roba: can't find email now - was it sent? 21:11:46 ... comments from 'Anna' - possible specializations about differnet kinds of profile 21:11:53 ... metadata profile vs. profile 21:12:07 ... unclear at this stage if that is needed 21:12:22 https://lists.w3.org/Archives/Public/public-dxwg-comments/2018Jan/0001.html 21:12:35 ... use-cases from Norway 21:13:04 +1 to simplifying to a single concept 21:13:08 ... no different unless there is functional difference in behaviours 21:13:42 ... looks like main issues are already covered in existing use-cases 21:14:04 q? 21:14:22 ... responsibility of vocabulary providers to package any complex collections 21:15:08 ack Jaroslav_Pullmann 21:15:08 ack Jaroslav_Pullmann 21:15:46 Jaroslav_Pullmann: Norway stated which ucs are important to them and offer to supply user stories 21:16:06 AndreaPerego has joined #dxwg 21:16:13 present+ AndreaPerego 21:16:14 ... Ixchel has elaborated answer to this 21:16:16 q+ 21:16:31 q- 21:17:14 Ixchel: onus is on the contributors to read what we have and comment on missed requirements 21:17:34 ... are there any deadlines on submitting comments on UCR 21:17:36 ? 21:17:56 Jaroslav_Pullmann: no deadline 21:18:17 roba: email failed to send 21:18:38 ... sent now 21:18:42 q? 21:18:56 Jaroslav_Pullmann: should we put a timeframe for responding to UCR comments 21:19:39 q? 21:20:13 roba: no deadline on UCR comments and responses 21:20:38 ACTION: Ixchel to respond to Ostein 21:20:41 Created ACTION-79 - Respond to ostein [on Ixchel Faniel - due 2018-02-13]. 21:20:53 https://lists.w3.org/Archives/Public/public-dxwg-comments/2018Jan/0000.html 21:20:59 Jaroslav_Pullmann: comment from Chris Little 21:21:31 ... requirement for 'update' relation 21:21:49 ... delete and overwrite 21:21:50 q+ 21:21:55 q+ 21:21:59 q- 21:22:18 q+ 21:22:27 Jaroslav_Pullmann: sees problems with replacement relation, inconsistent with datacite 21:22:38 ack SimonCox 21:23:43 ack roba 21:24:05 SimonCox: replacement relations are needed in some scenarios, its not our job to police that 21:24:24 q+ 21:24:35 q+ 21:24:54 roba: dynamically updated data does not 'replace' earlier data, it is a newer 'best guess' 21:25:12 ack AndreaPerego 21:25:14 ... different applciations will have different relationships 21:25:44 AndreaPerego: many different scenarios on this use case, can't apply just one vocabulary of relationships 21:26:13 ... dataset persistence will be a policy issue on the data-provider side 21:26:38 ... various scenarios and possible labeling solutions 21:27:09 ... also link to Data on the Web best practices 21:27:38 ... cannot prescribe solutions for all cases, though can describe good practices 21:27:38 ack DaveBrowning 21:28:45 DaveBrowning: newer 'best guess' scenario should be supported in a profile, and documented in best practices 21:29:09 q+ 21:29:26 ... too much variation for core 21:29:29 q+ 21:30:06 +1 - informal examples - make sure there is at least guidance 21:30:19 Jaroslav_Pullmann: shoudl we document examples of common cases? maybe a new UC for 'replacement? 21:31:05 DaveBrowning: two distinct cases - 1. new version which replaces earlier 2. newer best guess for dataset previously published 21:31:35 Aren't these qualified wasDerivedFroms? 21:31:44 Jaroslav_Pullmann: datacite relation 'new version of' 21:32:20 I don't think so NicholasCar 21:32:28 ack annette_g 21:32:37 dct:versionOf? 21:32:48 annette_g: two versioning issues here - 21:33:01 ... version of dataset recorded in catalogue 21:33:06 ... version of profile 21:34:19 q- 21:34:19 ... dataset case is highly variable, not possible to prescribe versioning patterns generally 21:34:23 +1 21:34:31 s/versionOf/isVersionOf 21:35:15 kcoyle: who will reply to Chris Little? 21:35:38 ... please run this through the dxwg list first! 21:35:41 q? 21:35:56 ack Jaroslav_Pullmann 21:36:16 TOPIC: definition of 'Profile' 21:36:27 q+ 21:36:41 ack roba 21:37:19 roba: had attempt starting from ISO 10000 definition of profile, relaxing need to be based on ISO artefacts 21:37:40 ... still thinks it is good, but lots of push back from the group :-( 21:38:04 kcoyle: where is definition text? 21:38:08 2/4/18 1:07 pm 21:38:23 "A named set of constraints on one or more identified base specifications, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function. This definitions allows for the set of constraints may be empty, and specifications may be profiles themselves, so that all statements about conformance t 21:38:23 o a specification may be made using the single concept of a profile"  21:38:23 21:38:28 https://www.w3.org/2017/dxwg/wiki/ProfileContext 21:38:48 … which I rather like 21:39:09 q+ 21:39:10 q? 21:39:22 ack annette_g 21:39:49 q+ 21:39:50 q? 21:39:55 annette_g: is "this definition ..." part of the text, or commentary. 21:40:21 roba: commentary 21:40:29 "A set of one or more base standards, and, where applicable, the identification of chosen classes, conforming subsets, options and parameters of those base standards necessary to accomplish a particular function." noting that the scope of "base standards" is relaxed to any standard that is identified by a canonical IRI, and thus can be identified by software agents. Profiles may act as "base standards" for more specialised profiles. 21:41:00 q+ 21:41:33 ack AndreaPerego 21:41:53 q+ 21:41:59 AndreaPerego: mixed discussion: 1. profile for conneg 2. profile for metadata 21:42:23 ... which? 21:42:51 roba: UCR says we need common definition of profile, conneg should be consistent with this 21:43:15 ... ruben is concerned about data model describing profile 21:44:08 AndreaPerego: terminological problem - conneg-by-profile allows you to point to information complementary to immediate information 21:44:36 ... metadata records in XML which are either ISO 19139 or DCAT - which schema? 21:44:49 ... conneg-by-profile must complement media-type 21:45:34 ... same term used different for content profile 21:45:36 ack annette_g 21:46:28 type 2, profile for metadata is mostly useful for validation, e.g. expressed as SHACL file 21:47:09 annette_g: 'A named set ...' focuses on the set of constraints, and is better 21:48:38 +1 to Rob 21:48:40 q? 21:48:43 roba: the two applications of 'profile' should be consistent, big problem if they are not 21:48:45 ack roba 21:49:06 +1 to roba 21:49:29 q+ 21:49:37 ack AndreaPerego 21:50:10 AndreaPerego: 'DCAT' itself is a 'profile' in this context - content model that complements serialization 21:50:23 DCAT as profile of DCAT is just the trivial case. 21:51:08 q? 21:51:16 ... profile of metadata is also a profile, similar to data 21:51:27 q+ 21:52:25 PROPOSED: use this as the definition of 'profile' - "A named set of constraints on one or more identified base specifications, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function. " 21:52:30 A named set of constraints on one or more identified base specifications, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function. This definitions allows for the set of constraints may be empty, and specifications may be profiles themselves, so that all statements about conformance t [08:38] o a spec 21:53:04 Maybe we should say: "A named set of constraints, possibly empty, [...]" 21:53:11 o a specification may be made using the single concept of a profile" 21:53:26 +1 at Andreas's c;arification 21:53:34 s/at/to/ 21:53:43 s/c;/cl/ 21:54:14 annette_g: antoine also had comments - 21:54:23 if a 'named set of constraints' is empty, doesn't that mean an empty set, so nothing at all? 21:54:44 q? 21:54:48 ack annette_g 21:54:48 q- 21:55:17 let's vote! 21:55:25 so, is the NULL set a profile? 21:55:42 It is a waste of time, though. 21:55:46 I would delete the 'possibly empty' 21:55:49 PROPOSED: "A named set of constraints, possibly empty, on one or more identified base specifications, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function. " 21:56:05 Then, e.g., DCAT is not a profile. 21:56:16 "A named set of constraints on one or more identified base specifications, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function. " 21:56:23 ... + guidance 21:56:44 q+ 21:57:00 ack annette_g 21:57:04 Last one, without the empty, OK with me 21:57:19 roba: in the wild, some existing specifications could be merely profiles 21:57:21 q+ 21:58:01 ack SimonCox 21:58:19 +1 21:58:19 +1 21:58:28 annette_g: + roba DCAT profiles may be narrower 21:58:28 +1 21:58:30 +1 21:58:31 +1 21:58:40 what are we voting on? 21:58:41 0 21:58:47 (we can always revist) 21:58:55 what was the proposal? 21:58:56 s/revist/revisit/ 21:59:00 +1 21:59:12 q+ 21:59:25 the second one after the PROPOSED? 21:59:30 Proposed: to adopt this definition of 'Profile' - "A named set of constraints on one or more identified base specifications, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function. " 21:59:36 ack roba 21:59:39 +1 21:59:54 Maybe "constraints or restrictions". 22:00:00 Resolved: ns, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function. " 22:00:33 rrsagent, please create minutes 22:00:33 I have made the request to generate https://www.w3.org/2018/02/06-dxwg-minutes.html kcoyle 22:00:34 RESOLUTION: to adopt this definition of 'Profile' - "A named set of constraints on one or more identified base specifications, including the identification of any implementing subclasses of datatypes, semantic interpretations, vocabularies, options and parameters of those base specifications necessary to accomplish a particular function. " 22:00:36 Cheers all 22:00:39 Thanks, bye! 22:00:40 bye 22:00:42 bye! 22:00:42 bye! 22:00:43 rrsagent, please create minutes v2 22:00:43 I have made the request to generate https://www.w3.org/2018/02/06-dxwg-minutes.html kcoyle 22:00:46 bye 22:00:48 present- 22:01:29 RRSAgent, make logs world 22:01:36 RRSAgent, draft minutes v2 22:01:36 I have made the request to generate https://www.w3.org/2018/02/06-dxwg-minutes.html AndreaPerego 22:02:31 regrets+ Lars, Ruben, Peter, Antoine 22:02:33 RRSAgent, draft minutes v2 22:02:33 I have made the request to generate https://www.w3.org/2018/02/06-dxwg-minutes.html AndreaPerego