12:01:45 RRSAgent has joined #dxwgcneg 12:01:45 logging to https://www.w3.org/2019/07/18-dxwgcneg-irc 12:01:47 RRSAgent, make logs public 12:01:47 Zakim has joined #dxwgcneg 12:01:49 Meeting: Dataset Exchange Working Group Teleconference 12:01:49 Date: 18 July 2019 12:02:13 Meeting: DXWG CNEG Telecon 12:02:26 present+ 12:02:34 present+ 12:06:54 Chair: LarsG 12:06:57 scribenick: roba 12:07:09 Topic: Confirm Agenda 12:07:52 present+ roba 12:08:12 RRSAgent, please make logs public 12:08:15 RRSAgent, please make logs public 12:08:22 RRSAgent, please draft minutes v2 12:08:22 I have made the request to generate https://www.w3.org/2019/07/18-dxwgcneg-minutes.html LarsG 12:08:26 +1 12:08:31 +1 12:08:36 +1 12:08:46 RESOLVED: confirmed agenda 12:08:54 Topic: Approve minutes from last meeting 12:09:11 https://www.w3.org/2019/07/11-dxwgcneg-minutes 12:09:20 +1 12:09:24 +1 12:09:38 +1 12:09:49 RESOLVED: Approved minutes 12:09:55 Topic: Open action items 12:10:03 https://www.w3.org/2017/dxwg/track/products/4 12:10:17 action-193? 12:10:17 action-193 -- Rob Atkinson to Move jmeter test suite to within w3c systems -- due 2018-09-05 -- OPEN 12:10:17 https://www.w3.org/2017/dxwg/track/actions/193 12:11:08 roba: waiting on implementation to test against 12:11:17 action-341? 12:11:17 action-341 -- Lars G. Svensson to To final review and reply to tom formally -- due 2019-06-27 -- PENDINGREVIEW 12:11:17 https://www.w3.org/2017/dxwg/track/actions/341 12:11:48 larsg: sent out, can be closed 12:12:30 close action-341 12:12:30 Closed action-341. 12:12:39 action-343? 12:12:39 action-343 -- Nicholas Car to Update qsa documentation with an equivalent to getcapabilities -- due 2019-07-11 -- OPEN 12:12:39 https://www.w3.org/2017/dxwg/track/actions/343 12:14:15 we are working on equivalent functionality using conformance to profiles of the Conneg Doc 12:14:35 we will leave this Action open until an equivalent mechanism is delivered 12:15:30 roba: we will "eat our own dog food" and show parts of conneg doc can be conformed to as alternative profiles 12:18:26 ncar: we have deferred the issue of what being conformant to conneg means.. 12:19:25 roba: we need to call it out explicitly in conneg document and provide identifiers different profiles in the document (alternative mechanisms) 12:20:32 action-347? 12:20:32 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:20:32 https://www.w3.org/2017/dxwg/track/actions/347 12:23:40 ncar: reviewed specifications and it appears cannot pass headers via redirects 12:24:18 roba: we can do the same thing as for the getcpabilities idea and recommend a canonical way to embed this info in content - but cannot enforce it. 12:25:21 larsg: we should highlight these in 3PWD and solicit feedback 12:26:29 action-348? 12:26:29 action-348 -- Nicholas Car to Create pr with real examples to solve #287 -- due 2019-07-18 -- OPEN 12:26:29 https://www.w3.org/2017/dxwg/track/actions/348 12:27:57 ncar: examples in email so far - @aisaac has approved - yet to put into document - so leave action open 12:28:26 s/email/github comment/ 12:28:35 action-349? 12:28:35 action-349 -- Lars G. Svensson to Move text from ietf to conneg draft for #500 -- due 2019-07-18 -- PENDINGREVIEW 12:28:35 https://www.w3.org/2017/dxwg/track/actions/349 12:29:06 larsg: PR approved - can close 12:29:08 close action-349 12:29:08 Closed action-349. 12:29:40 Topic: Review of Nick's proposal for conformance to profiles 12:29:49 https://raw.githack.com/w3c/dxwg/conformance-profiles/conneg-by-ap/index.html 12:38:36 There are 4 open questions: 1. do we agree with the general thrust of this proposal? 2. if we agree, do we agree to use PROF to characterise profiles of Conneg by P? 3. If so, do we use PROF namespace for the Conneg by P profile instances? Seperately, 4. How do we link information about the non-informaiton resource (the service conforming to Conneg by P) to the information resources (content served by the services conforming)? 12:41:54 LarsG: can conformance to Conneg by P specifications be described using profiling mechanics? 12:42:15 ncar: I think it can - just write down the spec and conform to it 12:42:26 roba: I think it can - loose interpretation of profiles 12:42:43 LarsG: can we actually specify conformance criteria in Conneg by P? 12:42:58 roba: yes, just look at all the conformance directives: MUST SHALL etc. 12:43:50 ncar: comes back to specifying what conformance means in the context of this community 12:44:57 roba: in a way we are declaring what information is passed and returned - so each specification can be seen as a "data profile" 12:45:28 ncar: no requirement for a machine actionable conformance test. 12:51:19 roba: Q1, ok, Q2, ok, Q3 not necissarily. The profiles' detiail could be declared elsewhere with this doc only containing URIs for identification 12:52:26 roba: correction (from tying error): Q2: no, we don't need to characterise anything beyond the corrent Conneg by P doc's language. Q3 I haven't addresses 12:52:36 s/addresses/addressed/ 12:55:03 LarsG: Q1, yes, Q2, we may use PROF or we should. 12:55:56 s/we may use PROF or we should/we MAY use PROF, not we SHOULD use PROF/ 13:00:01 roba: change qsa-strict to qsa and qsa-loose to qsa-alt 13:04:53 LarsG: does the idea of having the profile URIs in the main document 13:05:05 ... and the PROF definitions of the profiles in an annex mean 13:05:31 ... that the profile URIs are normative and the PROF definitions are not? 13:05:38 roba: thats the intent 13:05:38 ncar: yes 13:05:57 * cheers 13:06:15 RRSAgent: please draft minutes v2 13:06:15 I have made the request to generate https://www.w3.org/2019/07/18-dxwgcneg-minutes.html LarsG 14:29:59 Zakim has left #dxwgcneg