19:49:14 RRSAgent has joined #dxwg 19:49:14 logging to https://www.w3.org/2019/06/11-dxwg-irc 19:49:22 rrsagent, make logs public 19:49:34 chair: PWinstanley 19:50:07 regrets+ Simon 19:50:18 present+ 19:50:27 rrsagent, create minutes v2 19:50:27 I have made the request to generate https://www.w3.org/2019/06/11-dxwg-minutes.html PWinstanley 19:57:39 roba has joined #dxwg 20:00:22 kcoyle has joined #dxwg 20:00:59 * bo 20:01:11 antoine has joined #dxwg 20:02:03 TomB has joined #dxwg 20:02:07 present+ 20:03:30 present+ 20:04:17 annette_g has joined #dxwg 20:04:25 DaveBrowning has joined #dxwg 20:04:28 present+ 20:04:39 present+ 20:04:43 present+ 20:04:48 present+ 20:04:50 present+ 20:05:28 scribenick: dsr 20:05:50 chair: kcoyle 20:06:12 kcoyle: we we approve the minutes of June 4? 20:07:09 any objecttions? 20:07:13 +0 (was absent) 20:07:16 +0 20:07:21 +1 20:07:26 [no] 20:07:42 resolved: approve minutes of June 4, 2019 20:07:45 s/probelems/problems 20:08:08 https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2019.06.11 20:08:12 Simon 20:08:41 regrets+ SimonCox 20:08:44 Regrets: Simon 20:09:05 rrsagent, draft minutes v2 20:09:05 I have made the request to generate https://www.w3.org/2019/06/11-dxwg-minutes.html DaveBrowning 20:09:18 topic: pull requests 20:09:30 Any pull requests this week, that we need to be alerted to? 20:10:38 Tom present+ 20:10:48 DaveBrowning: some editorial references updated 20:11:24 Anything marked for closing that we should be interested in? 20:12:05 There were some open actions, not sure … 20:12:29 Peter did you do the conneg announcements? 20:12:44 rrsagent, draft minutes v2 20:12:44 I have made the request to generate https://www.w3.org/2019/06/11-dxwg-minutes.html DaveBrowning 20:12:56 PWinstanley: I have drafted a blog post which should be broadcast this week 20:13:30 Rob was due to make a contact … 20:14:02 kcoyle: let’s keep that one open until we have a response 20:14:36 Now we have the question of a six month extension 20:15:10 PWinstanley: PLH says we’re good having made the resolution to request the extension 20:15:30 We should plan on the assumption that we will get the extension 20:16:07 We need to sort out the definition of what we mean by a profile … 20:16:22 kcoyle: we need to work on profile guidance 20:17:04 antoine: we need to homongenise the text 20:17:08 q+ 20:17:27 q? 20:17:31 s/homongenise/homogenise/ 20:18:14 AndreaPerego has joined #dxwg 20:18:31 I am a bit less concerned about the profile document 20:18:36 present+ 20:18:57 ack roba 20:19:44 RRSAgent, draft minutes v2 20:19:44 I have made the request to generate https://www.w3.org/2019/06/11-dxwg-minutes.html AndreaPerego 20:19:55 roba: you’re absolutely correct Karen, my agenda is to ensure that the definition of profile is consistent across our work 20:20:45 q+ 20:20:49 There is a question of how deep our definitions need to go 20:21:05 q+ 20:21:16 ack TomB 20:21:21 ack TomB 20:21:29 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:Telecon2019.06.11 20:21:35 meeting: DXWG Plenary 20:21:36 RRSAgent, draft minutes v2 20:21:36 I have made the request to generate https://www.w3.org/2019/06/11-dxwg-minutes.html AndreaPerego 20:21:46 "conformance" 20:21:55 TomB: ifa profile is defined in terms of constraints then we need a definition of constraints 20:22:21 We don’t need to get hung up on the definition of profile though 20:23:04 for conneg, the issue is the distinction between profile and specification - and if its useful 20:23:21 ack PWinstanley 20:24:09 constraint = requirement that must be met - but a specific type of requirement that references another requirement ? 20:24:22 PWinstanley: I emailed ODRL, Michael Steiner said … 20:24:26 q+ 20:25:08 ack antoine 20:26:08 antoine: I wanted to react to Tom, not about the constraints, … 20:26:49 q+ 20:26:53 at least having an agreement within the group would be good, if we can fully align with ODRL that would be good 20:27:16 q? 20:27:16 a note in an email relating to the wide review of the DCAT v2 thought that the "profile" referenced in the DCAT v2 doc didn't look like the use cases for 'profile' as in the profile vocabulary doc 20:27:24 ack roba 20:27:52 roba: I partly agree with antoine’s perspective, it’s up to the community to define what we mean by profile 20:29:04 in respect to conneg, we found it hard to separate profile from specification 20:29:33 we need to discuss edge cases and avoid pain through a shared understanding 20:30:09 "of course its not a profile" ? 20:30:18 q+ 20:30:21 kcoyle: do we want to broaden the concept of profile to support conneg or … 20:30:28 ack antoine 20:31:08 antoine: I will insist we don’t discuss this right now, the way I would put it is in terms of the definition in Diblin Core 20:31:23 s/Diblin/Dublin/ 20:31:40 q+ thinks a general definition may be good enough for CONNEG 20:31:47 kcoyle: how do you think we should go about resolving this 20:31:54 q+ 20:32:02 antoine: probaly by relating existing definitions 20:32:11 q+ to say that I think we need co-creation around a google doc for the first cut 20:32:32 ack TomB 20:32:33 q+ to suggest that a general definition may be good enough for CONNEG and DCAT 20:32:39 antoine: may be by asking the task groups for their input 20:32:51 ack tomb 20:32:51 TomB, you wanted to suggest that a general definition may be good enough for CONNEG and DCAT 20:33:18 TomB: a general definition is probably sufficient 20:33:35 ack roba 20:33:36 not really convinced any more is needed 20:33:54 roba: the way we’ve done this in the past is through functional requirements 20:34:18 there will be many groups with narrower definitions for their context 20:34:36 … their govenence model … 20:35:02 s/govenence/governence/ 20:35:36 we won’t get too much trouble if we take a functional approach 20:36:08 kcoyle: I seem to remember that we didn’t get much from the use cases 20:36:38 q+ 20:36:44 roba: the requirements comes down to interop requirments 20:37:22 kcoyle: can you either find this in the use case requirement or find us somewhere else for a starting point 20:37:51 https://w3c.github.io/dxwg/ucr/#ProfileNegotiationRequirements 20:38:05 kcoyle: it needs to be something the group agreed on 20:38:07 q? 20:38:54 ack PWinstanley 20:38:54 PWinstanley, you wanted to say that I think we need co-creation around a google doc for the first cut 20:39:05 q- 20:39:06 PWinstanley: (v. distorted) I think we need co-creation around a google doc for the first cut 20:39:36 q+ 20:39:51 ack antoine 20:41:06 kcoyle: it appears that the requirements vary so how do we go about this 20:41:22 no i did _not_ argue conneg is broader than UCR or existing definition 20:41:42 q+ 20:41:51 ack antoine 20:42:34 antoine: I am reacting to roba, … 20:42:55 roba: conneg is broader than UCR or existing definition 20:43:09 I am happy to discuss this further 20:43:54 kcoyle: so we have a definition, you’re saying we just need a better explanation, right? 20:43:59 I'm not sure roba said " conneg is broader than UCR or existing definition" 20:44:14 roba: the process has been adequate so far, if we can improve it great 20:44:33 q+ 20:44:58 ack AndreaPerego 20:45:14 kcoyle: I am having a little difficulty understanding what people are asking for 20:45:41 q+ 20:45:55 AndreaPerego: for conneg we are talking about media types 20:46:20 roba: media types aren’t sufficient 20:47:48 s/roba: conneg is broader/roba: I did not argue that conneg is broader/ 20:48:13 q+ to offer a crazy solution 20:48:44 distinction between profile and media-type was explicitly handled : https://github.com/w3c/dxwg/issues/662 - we have gone to more effort to distinguish in text having agreed there are distinct 20:49:12 AndreaPerego: having something that is sufficient for all needs is impractical and people need to define additional constraints for their own requirements 20:49:31 +1 agree with AndreaPerego point re: different use of "profile" in CONNEG versus other specs and that we should acknowledge this 20:49:32 ack roba 20:49:44 kcoyle: people may read only one spec, so each spec needs to be clear on its own 20:49:57 q+ 20:50:16 roba: conneg relates to media types, but goes further 20:50:21 +1 agree with Karen that specs need to stand on their own for the sake of users 20:50:52 annette_g: may be there is a term that would cover both specs 20:50:56 +1 if we can find it :-) 20:51:14 e.g. schema negotiation, and define profile more narrowly 20:51:20 ack annette_g 20:51:20 annette_g, you wanted to offer a crazy solution 20:51:26 +1 agree with Annette w.r.t. possibly finding a better word 20:51:27 ack antoine 20:52:05 antoine: I am willing to take an action to make sure that our definition is referred to from the profile guidance spec 20:52:35 kcoyle: we could do that as an action 20:52:44 q+ to ask what the desired outcome is for the Guidance doc - WG Note? 20:52:58 ACTION: Antoine to handle definition in 662 re profiles and media types 20:52:58 Created ACTION-338 - Handle definition in 662 re profiles and media types [on Antoine Isaac - due 2019-06-18]. 20:53:22 q- 20:53:33 +1 20:53:42 ack roba 20:53:50 kcoyle: anyone support PWinstanley’s suggestion of a Google doc? 20:54:00 roba: sounds good 20:54:05 q+ 20:54:15 +1 to starting fresh 20:54:24 ack antoine 20:54:36 some discussion if a different document … 20:54:37 s/if/of/ 20:55:04 antoine: the other was about profile guidance 20:55:52 RRSAgent, draft minutes v2 20:55:52 I have made the request to generate https://www.w3.org/2019/06/11-dxwg-minutes.html AndreaPerego 20:55:56 action: roba to start google doc and add whatever he thinks will help 20:55:56 Created ACTION-339 - Start google doc and add whatever he thinks will help [on Rob Atkinson - due 2019-06-18]. 20:56:27 for the record, Tom sees https://docs.google.com/document/d/1Y4jP4SGZMnt63EpjTX11-hW6-3mxlaq1i-Lbiw4tx1M/ and https://docs.google.com/document/d/1HCBt1m6BSTZcS9-Sjw5pGYn_bode-lKsnhinmNnX91s/edit and agrees that another document is needed for this discussion 20:56:28 rrsagent, set logs public 20:57:09 kcoyle: that’s all we have time for today 20:57:36 kcoyle: asks AndreaPerego to clean up the minutes 20:57:41 bye 20:57:43 … end of meeting 20:58:00 RRSAgent, draft minutes v2 20:58:00 I have made the request to generate https://www.w3.org/2019/06/11-dxwg-minutes.html AndreaPerego 21:01:16 RRSAgent, draft minutes v2 21:01:16 I have made the request to generate https://www.w3.org/2019/06/11-dxwg-minutes.html AndreaPerego 21:02:50 RRSAgent, make logs world 21:02:52 RRSAgent, draft minutes v2 21:02:52 I have made the request to generate https://www.w3.org/2019/06/11-dxwg-minutes.html AndreaPerego 21:05:35 RRSAgent, draft minutes v2 21:05:35 I have made the request to generate https://www.w3.org/2019/06/11-dxwg-minutes.html AndreaPerego 21:10:25 RRSAgent, draft minutes v2 21:10:25 I have made the request to generate https://www.w3.org/2019/06/11-dxwg-minutes.html AndreaPerego 21:11:03 s/There is a question of how deep our definitions need to go/... There is a question of how deep our definitions need to go/ 21:11:21 s/I am a bit less concerned about the profile document/... I am a bit less concerned about the profile document/ 21:11:38 s/We need to sort out the definition of what we mean by a profile …/... We need to sort out the definition of what we mean by a profile …/ 21:11:53 s/We should plan on the assumption that we will get the extension/... We should plan on the assumption that we will get the extension/ 21:11:57 RRSAgent, draft minutes v2 21:11:57 I have made the request to generate https://www.w3.org/2019/06/11-dxwg-minutes.html AndreaPerego