11:05:34 RRSAgent has joined #dxwg 11:05:38 logging to https://www.w3.org/2023/06/14-dxwg-irc 11:05:38 RRSAgent, make logs Public 11:05:39 please title this meeting ("meeting: ..."), pchampin 11:05:46 rrsagent, please draft minutes v2 11:05:47 I have made the request to generate https://www.w3.org/2023/06/14-dxwg-minutes.html aisaac 11:05:54 meeting: 'Profile' task force' 11:05:57 Chair: roba 11:06:45 scribenick: aisaac 11:07:46 roba: intros 11:08:00 LarsG: I'm back at the German Natl Library 11:08:11 ... my main goal is to get the recommendation back on track 11:08:23 ... especially wrt the IETF process 11:08:45 Yousouf_Taghzouti: my PHD is semantic content negotiation 11:08:55 ... beyond the classicial dimensions 11:09:08 ... for me profiles are the way to go 11:09:24 ... Unfortunately when I joined it was the time when the group stop pushing the effort 11:09:40 ... Antoine suggested that I join the group 11:10:42 scribe+ 11:10:54 aisaac: stilla at Europeana 11:11:09 ... to be honnest, I don't have much time 11:11:36 s/stilla/still/ 11:11:41 ... invoved in Data Spaces (something the EU pushes) 11:11:55 ... in which profiles can have a role 11:12:19 pchampin: several hats. Initially I was interested via RDF* 11:12:30 ... working on RDF1.2 11:12:59 ... and the extension to have edges on edges 11:13:22 ... We want not to break any of the existing systems/data 11:13:29 ... Profiles may be a way to do this. 11:13:55 ... My 2nd hat is that I'm the W3C Staff contact for DXWG 11:14:06 roba: I'm with the open geospatial consortium 11:14:24 ... The needs for providing several views on the same data are quite strong 11:15:04 ... I was working on metadata for data profiles and Phil Archer invited me to DXWG 11:15:27 ... Defining profiles has been very difficult 11:15:42 ... In the meantime we've worked on infrastructure 11:16:06 ... It also touches on the depth of graph traversal (what to include in a response) 11:16:28 ... The Open API spec is prevalent in a lot of OGC work. 11:16:59 ... We use the profile vocabulary for a lot of things. 11:17:14 ... But I wanted to leave that until we progress on Conneg 11:17:52 ... There were a few people on the spec. Hopefully we can reach out to them. 11:18:01 Topic: update on the IETF process 11:18:26 LarsG: it's still stuck. One has to be part of the consortium 11:18:47 ... we've tried the XXX working group and the HTTP API one. Got negative answers. 11:19:07 ... We've tried with a group handling internet drafts 11:19:20 ... I would have to come back to them, asking where this would fit 11:19:27 ... "informative" RFC 11:19:35 roba: how can we support? 11:19:55 LarsG: I don't need support from this WG. Hopefully with Ruben and HErbert 11:20:30 roba: are there other pathways which potentially influence the IETF discussions? Open API? 11:20:30 q+ 11:21:07 pchampin: do you know if there's any application of profile-based conneg in Solid? 11:21:14 LarsG: not that I know of 11:21:24 pchampin: maybe I can ping Ruben about that. 11:21:39 ... Solid is currently developed in a CG but we're working on a WG charter 11:21:48 ... hopefully for the summer 11:22:04 ... If there's interest for profiles in that WG it would be an interesting liaison 11:22:30 q+ 11:22:36 q- 11:22:38 roba: at the moment we've in a vacuum. We're solving a particular problem that may not be understood 11:22:44 ... but there's no competition 11:23:06 LarsG: we're in a better state because there are implementations 11:23:19 q- 11:23:28 q+ 11:23:39 q- 11:24:08 s/XXX/HTTP-bis 11:25:13 q+ to ask about liaison IETF/W3C 11:25:48 For the record we cannot identify other alternative pathways to influence IETF discussions (wrt to the question above) 11:26:12 LarsG: is there a liaison between W3C and IETF? 11:26:17 pchampin: I can check 11:26:23 q- 11:26:27 RRSAgent, please draft minutes v2 11:26:29 I have made the request to generate https://www.w3.org/2023/06/14-dxwg-minutes.html aisaac 11:26:37 Topic: meeting time 11:27:15 roba: there's another person working on JSON-Schema who could be interested, but in the US West coast 11:27:40 ... I will ask him whether there is a connection between Open API and this (he also works on Open API) 11:28:33 aisaac: please don't make an effort for me, wrt setting the time! 11:28:37 Topic: open issues 11:28:44 https://github.com/w3c/dx-connegp/issues 11:29:43 roba: I went through them and have done some triage 11:30:41 present+ LarsG , pchampin , roba , aisaac , Yousouf_Taghzouti 11:30:53 https://github.com/w3c/dx-connegp/issues/31 is typs 11:30:54 regrets+ Nick Car 11:31:07 RRSAgent, please draft minutes v2 11:31:08 I have made the request to generate https://www.w3.org/2023/06/14-dxwg-minutes.html aisaac 11:31:14 https://github.com/w3c/dx-connegp/issues/33 11:31:35 https://github.com/w3c/dx-connegp/issues/34 11:31:54 regrets+ kcoyle 11:32:23 roba: these are simple issues 11:32:33 https://github.com/w3c/dx-connegp/issues/35 11:32:59 roba: I propose to close them 11:33:44 One issue is about a broken link to the editor's draft from the PWD 11:34:01 ... How does one fix such a reference in the PWD? 11:35:31 pchampin: we could modify a broken link on a doc in TR. But in this specific case we could add something at the current link, because it's in control of DXWG 11:35:47 ... Maybe a note saying "this doc has moved, please see [here]" 11:36:02 ... I could make a PR on that repository 11:36:33 roba: this would be great. 11:36:47 https://github.com/w3c/dx-connegp/pull/42 11:37:25 ... Can we move on an close these issues, looking at the PR? 11:37:40 LarsG: Nick and I could review? 11:37:57 Yousouf_Taghzouti: I could give it a try 11:38:00 q+ 11:38:18 q- 11:41:28 aisaac: it would be great to add the link to the PR 11:42:31 PROPOSED: close 31,33,34,35,42 as soon as the corresponding fixes are implented 11:42:39 +1 11:42:41 +1 11:42:42 +1 11:42:44 +1 11:42:44 +1 11:42:56 RESOLVED: close 31,33,34,35,42 as soon as the corresponding fixes are implemented 11:45:04 https://github.com/w3c/dx-connegp/issues/27 11:45:26 will propose an improved version as per suggestion 11:47:00 aisaac: having a subclass of Resource also called Resource doesn't seem ok. 11:47:20 roba: we'll take it offline and develop a proposal 11:47:41 aisaac: removing this class entirely would look better practice 11:48:21 https://github.com/w3c/dx-connegp/issues/6 11:48:30 roba: issue 6 has been labeled 'due-for-closing' 11:48:39 ACTION: Antoine to study issue 6 11:49:33 aisaac: this looks like it's a request to have a document explaining what profiles are. Not trivial ;-) 11:49:45 https://github.com/w3c/dx-connegp/issues/2 11:49:50 ... Maybe we could park it elsewhere, if it still applies 11:49:59 ... (this is about 6 not 2) 11:50:33 roba: for issue 2 we've tweaked the wording. 11:51:34 ... the sentence has been changed from MUST to MAY 11:51:49 ... Maybe we can quickly discuss this. 11:52:27 ... a lot of the issue was a long rambling discussion 11:53:47 LarsG: this sounds like an academic case 11:53:50 +1 11:53:54 -1 11:56:06 aisaac: I think I agree with the remarks but it could be good to advertise it to the group as part of the next call's agenda 11:56:27 ... we've covered a lot of ground today and this could be an opportunity to make noise about the sub-group's resuming 11:56:34 roba: agreed! 11:57:04 ... in the meantime it would be good for everyone to look at the issues and say which ones they'd like to tackle for the next meeting 11:58:02 ... for some I need more time thinking about it 12:00:00 ... Everyone feel free to comment and vote on your priority issues! 12:00:34 Topic: frequency of meetings 12:00:43 roba: every two weeks or every month? 12:00:56 LarsG: every two weeks, for trying to keep the momentum 12:01:07 pchampin: same time? 12:01:21 roba: yes until we have strong hints by other potential contributors 12:01:35 RRSAgent, please draft minutes v2 12:01:36 I have made the request to generate https://www.w3.org/2023/06/14-dxwg-minutes.html aisaac