<LarsG> Meeting: DXWG CNEG Subgroup telecon
scribenick ncar
<LarsG> Scribe: ncar
<roba> * still looking for link to webex - not in meeting notes still
LarsG: Link to previous meeting is incorrect
<LarsG> https://www.w3.org/2018/08/15-dxwgcneg-minutes.html
<LarsG> PROPOSED: Accept minutes from last meeting
<roba> +1
<LarsG> +1
agenda for this meeting updated with correct minutes link
+1
RESOLUTION: Accept minutes from last meeting
<LarsG> action-166?
<trackbot> action-166 -- Lars G. Svensson to Invite herbert & ruben to generate an ietf fpwd before tpac -- due 2018-08-08 -- OPEN
<trackbot> https://www.w3.org/2017/dxwg/track/actions/166
LarsG: Reuben can spend time on
thsi in Spet, Herbert, no response
... leave this action open for Herbert response
<LarsG> action-167?
<trackbot> action-167 -- Nicholas Car to Create a draft of the conneg guidance doc for next conneg meeting -- due 2018-08-08 -- OPEN
<trackbot> https://www.w3.org/2017/dxwg/track/actions/167
<LarsG> close action-167
<trackbot> Closed action-167.
<LarsG> action-180?
<trackbot> action-180 -- Robert Sanderson to Review the requirements and suggest edits -- due 2018-08-22 -- OPEN
<trackbot> https://www.w3.org/2017/dxwg/track/actions/180
<LarsG> close action-180
<trackbot> Closed action-180.
<LarsG> action-181?
<trackbot> action-181 -- Lars G. Svensson to Look at detail of second comment and report to group -- due 2018-08-22 -- OPEN
<trackbot> https://www.w3.org/2017/dxwg/track/actions/181
<LarsG> https://lists.w3.org/Archives/Public/public-dxwg-wg/2018Aug/0109.html
<LarsG> close action-181
<trackbot> Closed action-181.
<scribe> ACTION:LarsG to add discussion of Kam Hay Fung's email to next conneg meeting agenda
<scribe> ACTION: LarsG to add discussion of Kam Hay Fung's email to next conneg meeting agenda
<trackbot> Created ACTION-190 - Add discussion of kam hay fung's email to next conneg meeting agenda [on Lars G. Svensson - due 2018-09-05].
roba: there is sense to have both
labels and they are not quite applied correctly - he is fixing
this now
... this is in opposition to ncar's assertion added to the
minutes that they are artefacts of a cleanup
Should we add all approved requirements to the guidance document?
scribe: as has been done with the Profile Guidance doc
roba: yes, this was discussed in plenary for DCAT and we should follow precident
LarsG: we don't have a profile-negotiation list of approved requirements
<roba> * welcome azaroth
ncar: I will add requirements to
the cneg document as they become approved by plenary
... we should propose requirements approved by this group, to
plenary, for their approval and thus inclusion in the
deliverable doc
roba: we should include all
requirements in doc first with a status/'health warning' before
approval so we don't look in two places
... use cneg document as the point-of-truth for all requirments
- complete and unresolved requirements too
LarsG: I see Rob's point
roba: we have a process for tidying up docs anyway
ncar: I'm happy with this method noting it is different to Profile Negotiation group
<LarsG> ACTION: ncar to add all requirements tagged with *-negotiation to the CNEG guidance document
<trackbot> Created ACTION-191 - Add all requirements tagged with *-negotiation to the cneg guidance document [on Nicholas Car - due 2018-09-05].
agenda item - What timeline can we commit to?
LarsG: adding items to the doc in this way is quicker than plenary approval first however what time dis this suggest for a FPWD?
ncar: yes, we can be ready by TPAC
roba: method suggested is similar to DCAT FPWD
<azaroth> +1
LarsG: I can spend most time on the IETF doc and can spend some time on this
azaroth: I may be able to spend some time in Oct on this
LarsG: I will be at TPAC
roba: I won't be
azaroth: I will be there but at the JSON-LD meeting colliding with DXWG
ncar: I am not certain to be there yet- depends on projects and their funding interests
roba: would like to see profiling work in the JSON-LD group discussed
azaroth: we could have a JSON-LD/DXWG joint session
<azaroth> ACTION: azaroth to propose join DX/JSON-LD WG session at TPAC to JSON-LD group
<trackbot> Created ACTION-192 - Propose join dx/json-ld wg session at tpac to json-ld group [on Robert Sanderson - due 2018-09-05].
roba: we (in this group) should be more informed about the JSON-LD mechanics for negotiation to learn from it
<azaroth> +1
<LarsG> +1
roba: linking between groups will improve W3C perceptions of this group
Q: Do the two documents cover off on the conceptual scopes we've discussed previously?
<LarsG> ncar: The profile guidance document so far has intro text by phila and some
<LarsG> ... other text about defs etc.
<LarsG> ... needs text about requirements and will eventually have things
<LarsG> ... leading to profile negotiation (but won't get into the mechanics of that)
<LarsG> ... Nothing controversial about that, but needs to be aligned with the other
<LarsG> ... work by the CNEG group.
<LarsG> ... Has added intro information about different ways of providing instructions
<LarsG> ... on how profile negotiation can be done (http conneg, URI queries etc.)
<LarsG> ... Also added the original motivation
roba: comfortable with scope
azaroth: is this cneg doc a rec?
ncar: I think so
roba: a rec
azaroth: we need a test suit + 2
working examples
... this might be a high bar for a small WG
... do we have linkely implementation in the WG timeframe (due
to capacity)?
ncar: we are producing an implementation (at CSIRO) and could generate a test suite
<LarsG> ncar: can easily get an implementation done within the time-frame of the WG
<LarsG> ... what are the requirements on the test suite?
roba: has an independent implementation
<LarsG> roba: would a Jmeter test suite good enough?
roba: is a JMeter test suite enough?
azaroth: could be
... describes test suites in other WGs
<LarsG> ncar: this sounds good, since we can use roba's test suite to test our work
<scribe> ACTION: roba to move JMeter test suite to within W3C systems
<trackbot> Created ACTION-193 - Move jmeter test suite to within w3c systems [on Rob Atkinson - due 2018-09-05].
<azaroth> We intend to implement at least the http conneg version, and will definitely consider the other options. I can't promise the timeline though
<scribe> ACTION: ncar to add headings for (4) implementations and a test suite to the doc
<trackbot> Created ACTION-194 - Add headings for (4) implementations and a test suite to the doc [on Nicholas Car - due 2018-09-05].
<LarsG> we intend to implement http conneg, too, but cannot promise the time line
azaroth: we could ask JSON-LD people for implementations to be tested
<scribe> ACTION: azaroth to ask JSON-LD group to consider profileneg by HTTP implementations for JSON-LD
<trackbot> Created ACTION-195 - Ask json-ld group to consider profileneg by http implementations for json-ld [on Robert Sanderson - due 2018-09-05].
<azaroth> Thanks everyone, and apologies again for being delayed in attending
<azaroth> +1 to email
roba: resolve UC Web browser navigation of profile information by email
<scribe> ACTION: ncar to request retification of UC Web browser navigation of profile information by email
<trackbot> Created ACTION-196 - Request retification of uc web browser navigation of profile information by email [on Nicholas Car - due 2018-09-05].
<azaroth> :)
:)
exit
<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/sepnd/spend/ Default Present: LarsG, ncar, Rob_Sanderson Present: LarsG ncar Rob_Sanderson Found Scribe: ncar Inferring ScribeNick: ncar Agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:CNEG-Telecon2018.08.29 Found Date: 29 Aug 2018 People with action items: azaroth larsg ncar roba 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.)[End of scribe.perl diagnostic output]