11:58:16 RRSAgent has joined #dxwgcneg 11:58:16 logging to https://www.w3.org/2019/08/29-dxwgcneg-irc 11:58:18 RRSAgent, make logs public 11:58:18 Zakim has joined #dxwgcneg 11:58:20 Meeting: Dataset Exchange Working Group Teleconference 11:58:20 Date: 29 August 2019 11:58:37 Meeting: DXWG CNEG Subgroup Telecon 11:58:43 present+ 12:02:36 RRSAgent, please draft minutes v2 12:02:36 I have made the request to generate https://www.w3.org/2019/08/29-dxwgcneg-minutes.html LarsG 12:03:10 RRSAgent, please make logs public 12:03:15 RRSAgent, please draft minutes v2 12:03:15 I have made the request to generate https://www.w3.org/2019/08/29-dxwgcneg-minutes.html LarsG 12:06:28 ncar has joined #dxwgcneg 12:06:36 present+ 12:09:15 scribe: ncar 12:09:19 Chair: LarsG 12:09:24 scribeNick: ncar 12:09:53 TOPIC: conform agenda https://www.w3.org/2017/dxwg/wiki/Meetings:CNEG-Telecon2019.08.29 12:10:17 +1 12:10:21 +1 12:10:52 +1 12:11:34 TOPIC: approve minues of last meeting 12:11:37 https://www.w3.org/2019/08/22-dxwgcneg-minutes 12:12:03 +1 12:12:13 +1 12:12:24 +1 12:12:25 RESOLVED: approve minues of last meeting 12:12:43 TOPIC: open action items 12:12:52 https://www.w3.org/2017/dxwg/track/products/4 12:13:23 action-193? 12:13:23 action-193 -- Rob Atkinson to Move jmeter test suite to within w3c systems -- due 2018-09-05 -- OPEN 12:13:23 https://www.w3.org/2017/dxwg/track/actions/193 12:13:54 roba: this is still open but progress is being made 12:14:05 roba: list profiles support still to go 12:14:08 action-306? 12:14:08 action-306 -- Nicholas Car to Ask annette if #544 can be closed, else she should provide more detail -- due 2019-03-07 -- OPEN 12:14:08 https://www.w3.org/2017/dxwg/track/actions/306 12:15:42 ncar: underlying issue has been long closed 12:15:50 ... so we can close this action 12:15:56 close action-306 12:15:56 Closed action-306. 12:16:02 ACTION-306 is only being closed now since it was in the wrong ACTION list and not seen 12:16:12 action-358? 12:16:12 action-358 -- Rob Atkinson to to convene working session to co-develop common model to match link header data and alternates view requirements. -- due 2019-08-08 -- OPEN 12:16:12 https://www.w3.org/2017/dxwg/track/actions/358 12:17:00 roba: action still open 12:17:16 TOPIC: Discussion of #1017 12:17:20 https://github.com/w3c/dxwg/issues/1017 12:18:00 LarsG: initiated by a question from TomB 12:18:30 Comment from Karen: https://lists.w3.org/Archives/Public/public-dxwg-comments/2019Aug/0002.html 12:18:52 Comments from TomB: https://lists.w3.org/Archives/Public/public-dxwg-comments/2019Aug/0003.html https://lists.w3.org/Archives/Public/public-dxwg-comments/2019Aug/0004.html 12:29:24 As per discussion in the CNEG subgroup meeting 2019-08-29, the subgroup feels that if communities wish to use Conneg by Profile, then they must provide URIs for the things being conformed to (Profiles). Communities may choose not to do so but then they will not be able to use this specification. 12:30:22 (the above is proposed wording for a response in the GitHub Issue) 12:32:13 when using the proposed CNEG mechanisms it is up to each community to determine what a profile identifier means in terms of expected responses. If a URI points to an ambiguous resource with no clear conformance requirements then server may not be usefully predictable. 12:32:18 (the above is proposed wording for a response in the GitHub Issue) 12:32:46 the nature of the server response 12:36:14 The above response is in Issue 1071 (https://github.com/w3c/dxwg/issues/1017#issuecomment-526164813) 12:36:28 TOPIC: Discussion of schedule for moving to REC before end-of-year 12:36:33 https://github.com/w3c/dxwg/wiki/Steps-to-Recommendation-2019 12:47:17 1. this proposal, to cater for tokens, does impact the IETF document - the token definition mechanism will need to be given there 12:47:58 2. servers may choose to implement tokens or not 12:48:42 3. if they do not, they have no further work to do (nothing to implement) 12:49:42 4. the motivation for catering for tokens is that existing profile negotiation systems (pyLDAPI, OAI-PMH, OGC Name Server) all use tokens 12:50:51 5. if we do not provide a token/URI linking mecahnism in the IETF doc, since the W3C doc is dependent on it, then we prevent those systems from being able to adhere to a formal specification 12:50:56 13:11:09 ACTION: LarsG to propose generalising syntax for the IETF doc to bypass hard requriement for token indicator 13:11:10 Created ACTION-362 - Propose generalising syntax for the ietf doc to bypass hard requriement for token indicator [on Lars G. Svensson - due 2019-09-05]. 13:12:03 rrsagent, generate minutes v2 13:12:03 I have made the request to generate https://www.w3.org/2019/08/29-dxwgcneg-minutes.html ncar 13:18:59 present+ roba 13:19:22 RRSAgent, please draft minutes v2 13:19:22 I have made the request to generate https://www.w3.org/2019/08/29-dxwgcneg-minutes.html LarsG