11:52:53 RRSAgent has joined #dxwgcneg 11:52:53 logging to https://www.w3.org/2019/07/25-dxwgcneg-irc 11:52:55 RRSAgent, make logs public 11:52:55 Zakim has joined #dxwgcneg 11:52:57 Meeting: Dataset Exchange Working Group Teleconference 11:52:57 Date: 25 July 2019 11:53:23 Meeting: DXWG CNEG Telecon 11:53:31 RRSAgent, please make logs public 11:53:43 RRSAgent, please draft minutes v2 11:53:43 I have made the request to generate https://www.w3.org/2019/07/25-dxwgcneg-minutes.html LarsG 11:53:57 present+ 12:00:55 roba has joined #dxwgcneg 12:04:38 ncar has joined #dxwgcneg 12:05:09 present+ 12:05:30 present+ roba 12:06:00 present+ 12:06:30 scribeNick: LarsG 12:06:33 Chair: roba 12:06:36 TOPIC: confirm agenda 12:06:56 +1 12:06:58 +1 12:07:24 roba: We need to discuss profile definition, too 12:07:30 +1 12:07:51 TOPIC: accept minutes https://www.w3.org/2019/07/18-dxwgcneg-minutes 12:08:02 +1 12:08:08 +1 12:08:11 +1 12:08:18 RESOLVED: accept minutes 12:08:19 RESOLVED: Approved minutes from last meeting 12:08:38 TOPIC: open action items https://www.w3.org/2017/dxwg/track/products/4 12:08:42 action-193? 12:08:42 action-193 -- Rob Atkinson to Move jmeter test suite to within w3c systems -- due 2018-09-05 -- OPEN 12:08:42 https://www.w3.org/2017/dxwg/track/actions/193 12:08:53 roba: No progress on 193 12:09:01 action-343? 12:09:01 action-343 -- Nicholas Car to Update qsa documentation with an equivalent to getcapabilities -- due 2019-07-11 -- OPEN 12:09:01 https://www.w3.org/2017/dxwg/track/actions/343 12:09:09 ncar: large update 12:09:30 ... we might be able to circumvent this issue 12:10:32 ... the link header can be the key here 12:10:59 ... we need to give the ua a hint of the alternate views 12:12:16 ... and that can be done through the link header 12:12:44 roba: Is it possible to create examples? 12:24:50 ncar: 12:25:32 roba: this conflates 343 and 347... 12:26:16 ... we'll leave 343 open until ncar makes a PR 12:26:28 action-347? 12:26:28 action-347 -- Rob Atkinson to Create new gh issue explaining the problem of redirects and refer to that issue in the wd -- due 2019-07-18 -- OPEN 12:26:28 https://www.w3.org/2017/dxwg/track/actions/347 12:27:11 roba: we'll handle this one together with 343 12:27:21 action-348? 12:27:21 action-348 -- Nicholas Car to Create pr with real examples to solve #287 -- due 2019-07-18 -- OPEN 12:27:21 https://www.w3.org/2017/dxwg/track/actions/348 12:27:45 ncar: still open 12:28:20 TOPIC: General suitability of URIs for Conneg 12:30:15 roba: Since conformance is a community issue it's for the community to clarify which URIs to use 12:30:33 ncar: is this only about conneg or about profile identification in general? 12:30:51 roba: if there are different profile definitions in one document 12:31:04 ... we need different URIs within the document 12:31:14 ... in order to identify the profiles properly 12:32:13 ncar: is this similar to the functional profiles defined in ยง2.1? 12:32:27 roba: No, it's about the data profiles used for conneg 12:36:34 ... so can we agree that conneg works on data profiles 12:36:54 ... and that there are functional profiles for how conneg works? 12:36:58 LarsG: +1 12:37:10 ... but that doesn't answer ' 12:37:19 ... Tom's question. 12:37:48 roba: It's true that for conneg to work, we need distinct URIs 12:38:06 ... for each profile. If there are no distinct URIs in the specification 12:38:23 ... document, the community needs to invent some 12:39:28 ... so that the URIs unambiguously identify profiles 12:39:44 ... If the whole specification has only one URI, 12:39:52 ... it's not unambiguous 12:40:58 If a specification is unambiguous about the requirements for conformance as a data profile then it only needs a single URI.... 12:41:56 if there are multiple options defined in the specification which can be negotiated against then these must be unambiguously identified with distinct URIs 12:42:36 conneg-by-aP provides no mechanism for describing which part of an arbitratry specification is being conformed to . 12:43:06 s/part of an arbitratry specification/arbitrary part of a specification/ 12:46:10 if there are multiple options or parts of or within a specification which may be considered suitable for being conformed to then these must be unambiguously identified with distinct URIs and thus can be negotiated with for content 12:48:46 LarsG: goes in the right direction but needs some word-smithing 12:49:29 ... discussion will be in GH #1017 12:49:57 ... once that's resolved, we can answer Tom 12:50:09 TOPIC: Discussion of Antoine's conneg doc edits: We still need to address some comments.. 12:53:31 action: LarsG to review Antoine's comments and check if the 3PWD addresses them all 12:53:32 Created ACTION-351 - Review antoine's comments and check if the 3pwd addresses them all [on Lars G. Svensson - due 2019-08-01]. 12:53:37 TOPIC: data profiles definition 12:54:52 ncar: sees a problem since the new definitions are about "data profiles" 12:55:00 ... while conneg talks about "profiles" 12:56:11 ... has made some PRs to reflect this in conneg, prof etc. 12:56:27 roba: not much of an issue to conneg since that's about data profiles 12:56:41 ... prof, however, is also about functional profiles 12:56:53 ... data profiles are narrower than profiles 12:58:02 ncar: we need to ensure that the definition doesn't remove context from the document 12:58:29 roba: PROF will define profile as it always has and then add the definition of data profile 13:00:07 ncar: has split the spec of profile in two parts in the current PR 13:02:40 RRSAgent, please draft minutes v2 13:02:40 I have made the request to generate https://www.w3.org/2019/07/25-dxwgcneg-minutes.html LarsG 14:09:03 Zakim has left #dxwgcneg