W3C

– DRAFT –
Dataset Exchange Working Group Teleconference

30 May 2019

Attendees

Present
roba
Regrets
ncar
Chair
roba
Scribe
LarsG

Meeting minutes

Confirm Agenda

+1

Last meeting's minutes

roba: Nick was there but is missing from the minutes
… apart from that they're OK

<roba> +1

LarsG: I'll notify Philipp

+1

List of open action items

https://‌www.w3.org/‌2017/‌dxwg/‌track/‌products/‌4

roba: No action on 193 since last week,
… working on headers
… 327 is underway
… 328, here we can copy the text from the google doc into a github issue
… and use that one to generate more specific issues
… (no will put it into another action and use that to generate issues)
… and point TomB to that
… action

action-329?

<trackbot> action-329: Peter Winstanley to Check if an announcement has been made to public comments list -- due 2019-05-28 -- OPEN

roba: haven't heard anything about this. In the plenary plh said there is no
… formal automatism, so Peter will write a blog post

action-330

<trackbot> action-330: Peter Winstanley to Formally notify these cgs with plh_ -style request -- due 2019-05-28 -- OPEN

roba: this is about Peter's process to action action-327

action-336?

<trackbot> action-336: Lars G. Svensson to Poll pwin regarding action-327 -- due 2019-05-30 -- OPEN

LarsG: Has addressed Peter and he's on the task and the blog post will appear shortly
… 336 can be closed

close action-336

<trackbot> Closed action-336.

Topics/actions arising from plenary (if any)?

roba: nothing particular. Roba reported that we're working
… on substantial issues in order to get a 3PWD out asap
… It was mentioned that the cneg-profile document needs to have
… a good definition of profile in order to be able to stand alone
… without any other document (e. g. profile advice)
… we need a definition that is more founded in computer science
… that can be seen as a foundry definition

<roba> https://‌github.com/‌ProfileNegotiation/‌I-D-Profile-Negotiation/‌issues/‌17#issuecomment-497023698

AOB

<roba> the definition of the profile relation: This specification defines the 'profile' link relation type that allows resource representations to indicate that they are following one or more profiles. A profile is defined not to alter the semantics of the resource representation itself, but to allow clients to learn about additional semantics (constraints, conventions, extensions) that are associated with the resource representation, in addition [CUT]

Subtopic: use of profile relation vs profile attribute

roba: the use of "anchor" seems reasonable, Herbert's suggestion
… seems to work
… The problem is when we have one URI that supports profile negotiation
… then we don't have one unique anchor
… this issue and #932 and #603 are probably the last show stoppers
… maybe we can ask someone from the W3C team to give advice on
… web architecture issues from #603

Action: roba to contact plh about web architecture issues arising from #603

<trackbot> Created ACTION-337 - Contact plh about web architecture issues arising from #603 [on Rob Atkinson - due 2019-06-06].

Summary of action items

  1. roba to contact plh about web architecture issues arising from #603
Minutes manually created (not a transcript), formatted by Bert Bos's scribe.perl version Mon Apr 15 13:11:59 2019 UTC, a reimplementation of David Booth's scribe.perl. See history.

Diagnostics

Maybe present: LarsG, Subtopic