<LarsG> Meeting: DXWG CNEG Subgroup

<LarsG> apologies+ antoine

<LarsG> apologies+ RubenVerborgh

<LarsG> RRSAgent please make logs public

<ncar> Hi Lars, I'm unfortunately on the train so I can, for the next 1/2hr, chat and listen but not talk easily

<ncar> I wonder if we will have others join

<ncar> Rob is in the meeting but not here

<ncar> Hi Rob, sorry but I have no audio (on train)

<ncar> Sorry folks, can't get audio working on train at all so I'm now only present in this IRC

<ncar> Since we have so few people, can we live for 20 min or so on chat only or is that too hard?

<roba> PROPOSED: Accept minutes of last meeting: https://www.w3.org/2018/06/06-dxwgcneg-minutes.html

<ncar> +1

<LarsG> +1

<roba> +0

<roba> ACCEPTED:

RESOLUTION: Accept minutes of last meeting: https://www.w3.org/2018/06/06-dxwgcneg-minutes.html

<ncar> (that's both of us who were there)

<LarsG> scribe: roba

<scribe> scribenick: roba:

<ncar> regarrding agenda item 3: topics: Discussion of profile requirements, I have edited the title of the UC as promised at the plenary 12 hours ago

<ncar> "Clients should be able to determine which profiles are supported by a server, and with which content types or other properties, in order to receive the one most appropriate for their use. [ID2]"

<ncar> this includes the motivation "...in order to..."

<roba> * @ncar: we are jkust trying to remember the magic to make the minutes appear in the meetings page..

Discussion of profile requirements and priorisation

<LarsG> https://docs.google.com/document/d/13hV2tJ6Kg2Hfe7e1BowY5QfCIweH9GxSCFQV1aWtOPg/edit#

<LarsG> https://docs.google.com/document/d/1viuNJx_2dhSoEVOkjCG7cuuqzUqqR7fr4LvmP-t7T2A/edit

<roba> roba: will attempt to implement negotiation protocol, but main interest is in descriptive metadata

<ncar> I am unsure how to propagate updates made to these docs

<roba> LarsG: we are "measured" on did we fulfil our requirements - so need to pay attention

<ncar> I have implemented Accept-Profile and Profile HTTP headers and neg in my toolset. Is that what you meant by "will attempt to implement.." roba?

<roba> yes @ncar - on system at OGc

<ncar> ok

<ncar> If you talk, I should hear you now

<ncar> I hear you fine now!

<roba> roba: LarsG what are the key requirements you see for the IETF deliverable?

<ncar> I've also only seen the (now expired) draft of the IETF doc so what's the timeframe there?

<roba> ... shall we take to email to get Reubens input?

<ncar> The second one should be accepted with my change

<roba> LarsG: discussion of "Requirement: There should be a way for a client to look up additional information about a profile. (What kinds of information? Can we clarify this?) "

<roba> ...what is the client in this context? not a priority at run-time, it may be done at configuration or software development time

<roba> PROPOSED: reword as "Requirement: There should be a way to look up additional information about a profile - this may be machine readable for run-time mediation or used to develop or configure a client"

<LarsG> +1

<roba> +1

<ncar> +1

RESOLUTION: reword as "Requirement: There should be a way to look up additional information about a profile - this may be machine readable for run-time mediation or used to develop or configure a client"

<roba> ncar: which documents are we talking about:

<roba> ...have struggled with proliferation of google docs :-(

<roba> LarsG: expectation is that accepting in the plenary meeting will generate action to generation PR against UCR

<roba> ACTION: LarsG report back this expectation to plenary (accepting in the plenary meeting will generate action to generation PR against UCR)

<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.

<roba> ACTION: LarsG report back this expectation to plenary (accepting in the plenary meeting will generate action to generation PR against UCR)

<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.

<ncar_> ncar_ == ncar

<LarsG> https://www.w3.org/2018/06/19-dxwg-minutes.html

<roba> PROPOSED: Requirement: a profile offered by a service must be discoverable through a machine-readable graph of metadata that describes what is offered and how to invoke the offered profiles. is not classified as a conneg requirement

<LarsG> "accept as in scope Profiles must be discoverable through a machine-readable metadata that describes what is offered and how to invoke the offered profiles. ID5"

<LarsG> https://www.w3.org/2018/06/19-dxwg-minutes.html#x08

<roba> PROPOSED: Take requirement 4 to an email discussion to make sure Antoines comments are taken into consideration and potentially split into two requirements.

<ncar_> +1

<LarsG> +1

<roba> +1

RESOLUTION: Take requirement 4 to an email discussion to make sure Antoines comments are taken into consideration and potentially split into two requirements.

<roba_> roba_ = roba

<roba_> PROPOSED: Requirement 5 is covered by requirement 2 and 3 and can be removed as a duplicate

<ncar_> +1

<LarsG> +1

<roba_> +1

RESOLUTION: Requirement 5 is covered by requirement 2 and 3 and can be removed as a duplicate

<roba_> PROPOSED: Accept suggested replacement text for Requirement 6

<roba_> ...with edit This information about the requested profile is not a replacement for content type (e. g. application/xml), language (e. g. zh-Hant) or any other negotiated dimension of the representation

<LarsG> +1

<roba_> +1

<ncar_> +1

RESOLUTION: Accept suggested replacement text for Requirement 6

<roba_> PROPOSED: Reword requirement 6 as "Profiles may be identified by a short token which may be resolved to a canonical URI to support access to further metadata about the profile."

<roba_> PROPOSED: Reword Req 7 as "Requirement: A short token to specify a profile may be used as long as there is a discoverable mapping from it to the profile's identifying URI"

<roba_> +1

<LarsG> +1

<ncar_> +1

RESOLUTION: Reword Requirement 7 as "Requirement: A short token to specify a profile may be used as long as there is a discoverable mapping from it to the profile's identifying URI"

<roba_> ACTION: LarsG to report back progress to plenary.

<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.

<LarsG> trackbot, please close meeting

<trackbot> Sorry, LarsG, I don't understand 'trackbot, please close meeting'. Please refer to <http://www.w3.org/2005/06/tracker/irc> for help.

<LarsG> trackbot, please end meeting

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/"/:/
Succeeded: s/6/7/
Default Present: LarsG, roba, ncar
Present: LarsG roba ncar
Regrets: antoine RubenVerborgh
Found Scribe: roba
Inferring ScribeNick: roba
WARNING: No scribe lines found matching previous ScribeNick pattern: <roba\:> ...
Found ScribeNick: roba:
WARNING: No scribe lines found matching ScribeNick pattern: <roba\:> ...

WARNING: 1 scribe lines found (out of 109 total lines.)
Are you sure you specified a correct ScribeNick?

ScribeNicks: roba:, roba
Found Date: 20 Jun 2018
People with action items: back expectation larsg report this

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)