– DRAFT –
DXWG CNEG Subgroup Telecon

<LarsG> apologies+ ncar

Approve agenda

<LarsG> +1

Proposed: approve minutes https://‌www.w3.org/‌2018/‌11/‌07-dxwgcneg-minutes.html

+1

<LarsG> +1

Resolved: approve minutes https://‌www.w3.org/‌2018/‌11/‌07-dxwgcneg-minutes.html

<LarsG> action-231?

<trackbot> action-231 -- Robert Sanderson to Submit topic for face to face meeting about test runner/ results repositories -- due 2018-10-17 -- OPEN

<trackbot> https://‌www.w3.org/‌2017/‌dxwg/‌track/‌actions/‌231

<LarsG> RobS not present

<LarsG> action-234?

<trackbot> action-234 -- Nicholas Car to Use definitions to create abstract model diagram and text -- due 2018-10-17 -- OPEN

<trackbot> https://‌www.w3.org/‌2017/‌dxwg/‌track/‌actions/‌234

Open actions

<LarsG> Will be part of 2PWD

<LarsG> action-235?

<trackbot> action-235 -- Rob Atkinson to Create sequence diagram from abstract model and definitions -- due 2018-10-17 -- OPEN

<trackbot> https://‌www.w3.org/‌2017/‌dxwg/‌track/‌actions/‌235

<LarsG> depends on action 234 and will be part of 2pwd

<LarsG> roba: it will be easy enough to pick out terms etc from the definitions

<LarsG> ... and then create the diagram from that

FPWD

<LarsG> roba: have updated short name from plenary meeting, now dx-prof-conneg

roba: plan to do a final copy edit - have short name name of doc to dx-prof-conneg

https://‌www.w3.org/‌TR/‌dx-prof-conneg/

name decided at plenary yesterday

<LarsG> https://‌github.com/‌w3c/‌dxwg/‌issues/‌575

sub issue 15 Examples 2 and 3 are at odds with the conneg recipes derived from Http-range-14. In RDF statements, the 'most interesting' URIs are URIs of non-information resources. These non-information resources are expected to first be de-referenced to the URI of a representation via a 303-redirect. That URI is then served with a 200. There are of course cases where the pattern of examples 2 and 3 will be the right one. But now the text really says that the [CUT]

roba: we can add a redirection process placeholder in the middle of examples..
… this puts the responsibility on the resource to declare profiles - but the redirection mechanism may in fact be the place this is known
… should the resource then list the most specific or all known or all (transitive) it conforms to?

Proposed: add redirect to examples and add issues for profile list and redirect vs final resource knowledge of of profile

e.g. --- (any HTTP 3xx redirection) ---

<LarsG> +1

+1

Resolved: add redirect to examples and add issues for profile list and redirect vs final resource knowledge of of profile

Action: roba to add redirect to examples and add issues for profile list and redirect vs final resource knowledge of of profile

<trackbot> Created ACTION-261 - Add redirect to examples and add issues for profile list and redirect vs final resource knowledge of of profile [on Rob Atkinson - due 2018-11-28].

roba: still an open question in my mind as to whether list_profiles is a MUST - or if catalogs can list these as long as server negotiates
… and concerned text is inconsistent about this "A third request type is given that is expected not to apply to all realizations of this abstract model " and MUST with all three

Action: roba to propose a copy edit (retaining original sense) and add an issue for list_profile responsibility

<trackbot> Created ACTION-262 - Propose a copy edit (retaining original sense) and add an issue for list_profile responsibility [on Rob Atkinson - due 2018-11-28].

LarsG: positive feedback otherwise

Issues due for closing

<LarsG> https://‌github.com/‌w3c/‌dxwg/‌issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Aprofile-negotiation++label%3A%22due+for+closing%22

Action: roba: address 379 in copy edit

<trackbot> Created ACTION-263 - Address 379 in copy edit [on Rob Atkinson - due 2018-11-28].

2PWD

LarsG: hope before christmas - seems hard

roba: publish early - publish often

LarsG: need to check publication moratorium for christmas?

* are you going to join quickly? I will stay for another 15 if you like..

Action: LarsG to check moratorium dates
… if possible aim for 2PWD, even if minimal changes before Christmas

<trackbot> Created ACTION-264 - Check moratorium dates [on Lars G. Svensson - due 2018-11-28].

Articulating possible 303 patterns in an issue at least seems important for 2PWD if we dont get to a decision via feedback

...and discussion on list profiles responsibility across server, redirect and final resource

* thats a wrap...