19:55:25 RRSAgent has joined #dxwgcneg 19:55:25 logging to https://www.w3.org/2018/09/12-dxwgcneg-irc 19:55:27 RRSAgent, make logs public 19:55:27 Zakim has joined #dxwgcneg 19:55:29 Meeting: Dataset Exchange Working Group Teleconference 19:55:29 Date: 12 September 2018 19:57:19 Meeting: DXWG CNEG Subgroup Telecon 19:58:45 Chair: LarsG 19:59:03 RRSAgent, please draft minutes v2 19:59:03 I have made the request to generate https://www.w3.org/2018/09/12-dxwgcneg-minutes.html LarsG 19:59:45 present+ 20:00:54 RRSAgent, please draft minutes v2 20:00:54 I have made the request to generate https://www.w3.org/2018/09/12-dxwgcneg-minutes.html LarsG 20:02:07 ncar has joined #dxwgcneg 20:03:30 azaroth has joined #dxwgcneg 20:03:49 trackbot, start telcon 20:03:52 RRSAgent, make logs public 20:03:55 Meeting: Dataset Exchange Working Group Teleconference 20:03:55 Date: 12 September 2018 20:04:02 present+ Rob_Sanderson 20:04:08 present+ 20:04:34 scribeNick: ncar 20:04:45 chair: LarsG 20:04:45 Thanks for scribing ncar :) 20:05:02 +1 to that! 20:05:20 agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:CNEG-Telecon2018.09.12 20:05:54 +1 20:05:58 +1 20:06:01 +1 20:06:16 propose: accept last meeting's minutes 20:06:19 +1 20:06:22 https://www.w3.org/2018/08/29-dxwgcneg-minutes.html 20:06:25 +1 20:06:32 +1 20:06:53 resolution: accept last meeting's minutes 20:07:13 topic: open action items 20:07:16 https://www.w3.org/2017/dxwg/track/actions/open 20:08:01 https://github.com/w3c/json-ld-wg/issues/18 20:08:28 azaroth: has discussed joint sessions with the JSON-LD WG, they are keen 20:09:05 trackbot close action-195 20:09:05 Closed action-195. 20:11:01 trackbot, close action-190 20:11:01 Closed action-190. 20:12:23 topic: discussion of Kam Hay Fung's comment & LarsG's response 20:12:31 Lars' answer https://lists.w3.org/Archives/Public/public-dxwg-wg/2018Aug/0109.html 20:12:46 Kam Hay's comment https://lists.w3.org/Archives/Public/public-dxwg-comments/2018Aug/0002.html 20:17:16 LarsG: muti-line Accept-Profile headers equivalent to comma separated, single line Accept-Profile header 20:17:54 LarsG: the suggestion to name the profile response header Content-Profile with Content- to match other similar headers seems sensible 20:20:09 LarsG: perhaps there's only to be a note in the IETF doc to indicate that there may be ways other than HTTP to indicate profile preference 20:21:02 azaroth: a server dealing with a client that doesn't accept profiles: should return the default profile 20:22:29 azaroth: you should only get an error (rather than default) if client asks for profiles unsupported and no default 20:25:31 LarsG: we should support OPTIONS or HEAD for profile discovery 20:28:14 LarsG: for point about server delivering q values to client - clarification of question is needed 20:30:37 LarsG: if we use URIs for profiles but they change, how will clients know? 20:30:57 +1 20:31:33 ncar: this could be solved by using different URIs for different (changed) profiles 20:33:45 action: ncar to create an issue for profile version representation or not via identifier for W3C conneg doc 20:33:45 Created ACTION-212 - Create an issue for profile version representation or not via identifier for w3c conneg doc [on Nicholas Car - due 2018-09-19]. 20:36:47 LArsG: will draft a reply, based on his previous work and this discussion, and check with this group before sending back to Kam Hay Fung 20:37:19 Action: LarsG to draft reply to KamHay, circulate with the group and then answer on the comments list 20:37:20 Created ACTION-213 - Draft reply to kamhay, circulate with the group and then answer on the comments list [on Lars G. Svensson - due 2018-09-19]. 20:39:12 q? 20:43:05 action: ncar to add an additional section to the W3C conneg doc after Requirements to lay our this subgroup's recommendations for FPWD 20:43:06 Created ACTION-214 - Add an additional section to the w3c conneg doc after requirements to lay our this subgroup's recommendations for fpwd [on Nicholas Car - due 2018-09-19]. 20:44:42 topic: planning for FPWD 20:44:47 discussed above 20:44:58 topic: handing of Reqs in conneg doc 20:45:23 ncar: 19 requirements listed in the document 20:45:35 ... it would be good to have listed, how we want to answer them 20:45:54 ... à la "this is what we suggest" or "do like this" 20:46:04 ... this should be answered in the text 20:46:26 ... e. g Profile Listing: If you want to list your profiles with http, 20:46:54 ... use the way specified in the RFC. Otherwise, use one of those ways. 20:48:09 ... If we put in answers for 3 and 4, people will see how we intend to handle the requirements 20:49:00 action: draft responses to Reqs 3, 4 & 8 to indicate how subgroup will answer all others, styalistically 20:49:00 Error finding 'draft'. You can review and register nicknames at . 20:49:32 Action: ncar to draft responses to Reqs 3, 4 & 8 to indicate how subgroup will answer all others, styalistically 20:49:33 Created ACTION-215 - Draft responses to reqs 3, 4 & 8 to indicate how subgroup will answer all others, styalistically [on Nicholas Car - due 2018-09-19]. 20:50:36 topic: Propose to plenary tidy-up of titles of 'profile-negotiation' Requirement issues in GitHub 20:55:37 no objections to this! 20:57:00 rrsagent, generate minutes 20:57:00 I have made the request to generate https://www.w3.org/2018/09/12-dxwgcneg-minutes.html ncar 20:57:27 RRSAgent, please draft minutes v2 20:57:27 I have made the request to generate https://www.w3.org/2018/09/12-dxwgcneg-minutes.html LarsG 20:57:59 regrets+ Rob Atkinson 20:58:01 RRSAgent, please draft minutes v2 20:58:01 I have made the request to generate https://www.w3.org/2018/09/12-dxwgcneg-minutes.html LarsG