W3C

– DRAFT –
DXWG Plenary

15 June 2021

Attendees

Present
Ana, AndreaPerego, annette_g, DaveBrowning, kcoyle, PWinstanley, riccardoalbertoni
Regrets
Antoine
Chair
PWinstanley
Scribe
annette_g

Meeting minutes

<kcoyle> riccardoalbertoni you should be able to get on without a code

scribe annette_g

<PWinstanley> https://www.w3.org/2021/05/18-dxwg-minutes

proposed: approve minutes from previous meting

<DaveBrowning> 0 (not present)

<AndreaPerego> +1

<PWinstanley> 0

<plh> +1

+1

<Ana> +1

<kcoyle> +1

Resolution: approve minutes from previous meting

<riccardoalbertoni> 0

Subgroup Activities

PWinstanley: riccardoalbertoni , can you give a DCAT update?

riccardoalbertoni: meeting is moving from webex to zoom

request instructions in advance or in IRC

<riccardoalbertoni> https://github.com/w3c/dxwg/issues?q=is%3Aissue+is%3Aclosed++label%3Adcat++closed%3A%3E2021-05-04

riccardoalbertoni: last meeting we discussed some issues related to dcat keywords and other terms like dcterms:subject
… dcat:keywords subproperty of dcterms:subject was considered as a bug, but it is probably not anymore, as dcterms:subject seems to take literals besides URI
… in DCAT 2, we mention using dcat:theme and skos:schema. There was some confusion. The probable solution will be dropping the range of dcat:theme.

in DCAT2, the range was a skos:concept of theme.

Profile Guidance

kcoyle: we talked about moving things into our own github repo.
… I put out a proposal for the first piece. We don't seem to have the cycles for people to actually work on this.
… there was no reply to the proposal.

PWinstanley: as a group, we're a bit on the exhausted side and still have a way to go with DCAT 3. some input is still needed from IETF. It's a bit of a stamina game.
… what do you see as the shortest path forward?

kcoyle: I thought that looking at the issues was the shortest path. The fact is that no one is putting in time and energy.

PWinstanley: numerous people have signed up for membership in the group. The list is really very long. Regular attendees are less than a dozen.

<riccardoalbertoni> s/in DCAT 2, we mention using dcat:theme and skos:schema. There was some confusion. The probably solution will be dropping the range of dcat:theme./in DCAT 2, we mention using other stuff besides skos:ConceptScheme as range of dcat:themeTaxonomy. But we didn't update the range of dcat:theme, which was not incorrect but create some confusion.

PWinstanley: we haven't been able to change that. plh , are we any different from other groups?

plh: not really, especially when things are winding down. It might help to take a break.

PWinstanley: how does that fit with the DCAT working cycle? maybe pretty well. What do people think?

DaveBrowning: people's circumstances vary, and there's a mixture of stubbornness and guilt. I was planning to jump into working on the profiles doc, but then I didn't respond to Karen.

DaveBrowning: I would really love us to be able to do something.

PWinstanley: there's a huge amount of material to come forward and help us along.
… we've had a lot of discussion about this. we've had difficulty finding common ground. I think that stalled some of the activity on profile guidance.
… we were talking at times about a categorization system and picking them off category by category instead of an overarching opinion that would do for everything. what do you think, kcoyle ?

kcoyle: I've been working on application profiles for Dublin Core, so there's a lot we can offer as well, but I'm not willing to take it on alone.

PWinstanley: Issues that are still open in the other streams, we need to get rid of stuff that's irrelevant, determine what can be readily addressed. That's still hanging around.

kcoyle: there's still the prof vocabulary. I was never sure how that was supposed to connect. And we haven't had a report on that for several months.

PWinstanley: it's Australian summer now. Maybe we can try and get something. When do people think it would be appropriate to take a more substantial break?

plh: there's always the option for a summer break.

PWinstanley: how does that work for the timeline for DCAT 3?

riccardoalbertoni: I won't be available for August and the end of July, so the summer break I will probably take anyway.
… in terms of the timeline, the group is supposed to end at the beginning of next year. At the moment we have 60 issues open. Andrea made a huge effort in closing issues before the latest draft was issued.
… we close one issue, and one or two pop up.
… we need an exit strategy.
… re feedback on new features, though, I haven't noticed specific comments on them.

PWinstanley: What if we were to take a break for the months of july and august? conference season is in september.

PWinstanley: It might be a good idea to take off July and August.

kcoyle: it's fine with me, but it affects DCAT, not other groups.

PWinstanley: I suspect some people will not be available for August. Antoine likely.

AndreaPerego: I think it's fine. July and August I won't be available. We can do stuff on github still.

riccardoalbertoni: we can have a regular meeting before July. We should plan for more involvement in September.

annette_g: I'm okay with us taking time off. I think it's a good idea.

DaveBrowning: that works for me. I think it's sensible.

proposed: that we take off July and August for vacation

<kcoyle> +1

<Ana> +1

+1

<PWinstanley> +1

<DaveBrowning> +1

<AndreaPerego> +1

<riccardoalbertoni> +1

Resolution: that we take off July and August for vacation

PWinstanley: we can come back with some fairly specific tasks for September
… primer on DCAT, bringing together the various presentations
… the papers are in fairly late stages of writing, right?

riccardoalbertoni: the ones we're writing as the editors, we plan to submit before end of summer.

PWinstanley: September onwards, we should focus on specific deliverables and see if we can marshall enough people around them.

riccardoalbertoni: we will need to collect implementation info for DCAT supporting the new terms.

PWinstanley: I'm hoping we can begin to get something in the way of implementation from people like Ifo.

PWinstanley: anything else people would like to discuss? I think we're needing a kind of revitalization and reframing of our immediate problems so that we have some farily short term horizons that we can meet. Do you think we can usefully meet with Dublin Core?

kcoyle: it depends how we do it. There's a lot of similar work in DC and W3C. I've suggested starting communities in W3C. I think it would be great to combine forces.

PWinstanley: are there practical issues?

kcoyle: I think there are some, also some issues of ownership.
… I think it would be great for the application profile work to have some synergy.

PWinstanley: It would be interesting to take a look at folks developing application profiles.

kcoyle: An actual W3C community group on application profiles would be larger than this group, could bring in more hands.

PWinstanley: what about other conference communities?
… knowledge graph communities, metadata communities

kcoyle: DC is about the core being as useful to as many people as possible, and there can be extensions on that.

PWinstanley: it tends to operate at the lighter end of semantics.

kcoyle: yes, that's the problem and the promise.

PWinstanley: if we need it to be specific, we need stronger, more axiomatized models.

kcoyle: it would be great if those were on a continuum rather than there being a break.

PWinstanley: People have a more external frame than an internal skeleton.

kcoyle: we are looking into SHACL, and thinking the move from metadata to SHeX or SHACL is important.

PWinstanley: There's a awful lot of me-too-ism, with people trying out new things.

kcoyle: you need a certain technology neutrality, but you want what you develop to be useful today.

PWinstanley: anything else? or tea?
… thanks all
… we need to send an email out, I'll do that after this meeting.

<Ana> thanks everybody :)

Summary of resolutions

  1. approve minutes from previous meting
  2. that we take off July and August for vacation
Minutes manually created (not a transcript), formatted by scribe.perl version 136 (Thu May 27 13:50:24 2021 UTC).

Diagnostics

Succeeded: s/probably/probable/

Succeeded: s/what was considered as a bug is not anymore, so that issue was resolved/ dcat:keywords subproperty of dcterms:subject was considered as a bug, but it is probably not anymore, as dcterms:subject seems to take literals besides URI

Failed: s/in DCAT 2, we mention using dcat:theme and skos:schema. There was some confusion. The probably solution will be dropping the range of dcat:theme./in DCAT 2, we mention using other stuff besides skos:ConceptScheme as range of dcat:themeTaxonomy. But we didn't update the range of dcat:theme, which was not incorrect but create some confusion.

Maybe present: plh