– DRAFT –
Dataset Exchange WG

<FranckC> This is DXWG weekly call, 20 August 2026

<FranckC> regrets?

first agendum

Approval of minutes of last meeting (https://www.w3.org/2026/08/13-dxwg-minutes)

frankc - chairing today

FranckC - approval of minutes

<Jakub> +1

<annette_g> +1

<LarsG> +1

<Arofan> +1

<Dan> +1

<antoine> s/munites/minutes

<pchampin> +0 (absent)

<FranckC> +1

<antoine> +1

<YoucTagh> +1

RESOLUTION: Approval of last weeks's minutes

Github repositories

<pchampin> w3c/dx-dcat w3c/dx-vvd w3c/dx-qb

FranckC: create repositories for separate subgroups?

pchampin: , created 3 repositories
… every participant has write

<antoine> w3c/dxwg#1641

<gb> Issue 1641 Create separate repository for each DXWG deliverable (by dr-shorthair) [packaging]

pchampin: sometimes rights are distributed
… more permissive model

<antoine> s/distrivbuted/distributed/

FranckC: each task force can use github repositories

FranckC: what should be done with old repositories

pchampin: chairs have admin rights

jakub: up to facilitators to move old issues?

pchampin: permissions are unknown right now
… define labels
… everyone should have triage rights
… labels indicate what should be done

FranckC: labels are names of target repositories

Organization of task forces (facilitators, calendars, etc.)

FranckC: need facilitators for each TF
… need nominations

FranckC: will check with people about facilitating

<Arofan> Dan - it's true. I remember!

Dan: volunteered to facilitate vvd
… co-facilitator with FranckM

YoucTagh: discussed having first meetings of TFs

<pchampin> FYI labels are now created on repo dxwg: 'move-to-*'

FranckC: meetings will be discussed next
… roles for facilitators

<pchampin> https://github.com/w3c/dxwg/labels?q=move

FranckC: Franck doesn't know if facilitators can create agendas

YoucTagh: can go to calendar, but can't create events

YoucTagh: sharing page with form for creating events

FranckC: each TF needs to find their own meeting times

YoucTagh: do we have mailing lists for eachTF>\?

<roba> +1

FranckC: no automatice means for creating mailing lists

<pchampin> I believe that I can create task-force specific mailing list; they are just not created automatically

<antoine> roba: we could create github issues in the specific task repo to organise and discuss meetings

Roba: use github notifications where members apply
… topic could be scheduling

antoine: open discussions so far, each TF can use general mailing lists

<roba> again most exchanges should by by issues or discussion pages - tracking threads through > 100 emails per day across various activities (not just dxwg) is not feasible.

FranckC: every substantive mail exchange should go to general list

<roba> +1

antoine: Idid not mean it is better to move the github issues to the general list!

FranckC: best to use GitHub for specific discussions

YoucTagh: should we start TFs now, Sept, when?

Switch to new meeting organization (alternate between plenary and task forces meetings)

FranckC: every other week for plenary, alternate with TFs?
… when do we start?
… now
… reactions?

roba: all TFGs in one meeting?

FranckC: each TF has its own meeting

roba: TF meeting times need to be staggered

FranckC: no need for meeting next week (as Jakub and Riccardo can't do one for DCAT)
… not required

Github Wiki

FranckC: different types of wikis

<antoine> https://github.com/w3c/dxwg/wiki

antoine: no time to look at issue
… start with looking at wiki on Github
… put link in chat
… able to start with table based on deliverables
… each TF can decide if this is useful

FranckC: postpone substantive discussion. will discuss next time

AOB

FranckC: anyother business? No?
… went over the items discussed in this meeting

<antoine> s/roba TF meeting times/roba: TF meeting times/