Meeting minutes
<riccardoAlbertoni> PROPOSED: approve last meeting minutes https://
approve last meeting minutes
<riccardoAlbertoni> +1
AndreaPerego: 0 (I was not there)
<DaveBrowning> +1
<nobu_ogura> +1
RESOLUTION: approve last meeting minutes https://
<riccardoAlbertoni> https://
approve agenda
(silently approved)
<riccardoAlbertoni> https://
pending PRs
<riccardoAlbertoni> :https://
riccardoAlbertoni: There was feedback on possible misunderstanding in the use of dcat:haVersion and dcterms:hasVersion.
proposed: approve https://
AndreaPerego: +1
<DaveBrowning> +1
<riccardoAlbertoni> +1
<nobu_ogura> +1
RESOLUTION: approve https://
riccardoAlbertoni: Next PR
<riccardoAlbertoni> https://
riccardoAlbertoni: There are some open questions - used of multiple instances of dcterms:modified and URI for W3C.
… In DCAT we recommend using dcterms:modified only once. Shoudl we follow this approach here?
AndreaPerego: The question is whether it is useful to have all the modification dates or just the latest.
riccardoAlbertoni: There may be use cases for that, and I don't see much harm in keeping more than one - but maybe not all.
… For instance, we can just keep only the modification date since we started working on DCAT3.
… What do you think?
proposed: we keep only the modification dates starting from the first draft of DCAT3
<riccardoAlbertoni> +1
<nobu_ogura> +1
<DaveBrowning> +1
AndreaPerego: +1
RESOLUTION: we keep only the modification dates starting from the first draft of DCAT3
riccardoAlbertoni: The other issue about the URI for W3C.
… We can just use the home page of W3C.
proposed: as the URI we use the URL of the W3C homepage
<riccardoAlbertoni> +1
<DaveBrowning> +1
<nobu_ogura> +1
AndreaPerego: +1
RESOLUTION: as the URI we use the URL of the W3C homepage
<riccardoAlbertoni> https://
riccardoAlbertoni: I'll take care of updating the PR accordingly.
riccardoAlbertoni: Next PR
<riccardoAlbertoni> https://
riccardoAlbertoni: This PR is about changing the datatype for spatial resolution.
AndreaPerego: I see some discussion happening in the issue that triggered this PR: https://
… I have the impression that this is just an implementation-related issue, and I am not sure it should be addressed in DCAT - maybe we can add a note on that.
… Eventually, the datatypes we specify are meant to indicate as exactly as possible which are the expected values. Implementation-wise, they can be changed depending on the requirements.
riccardoAlbertoni: Let's try to keep as it is and change the usage note to explain that compatible datatypes can be used.
AndreaPerego: Fine with me.
riccardoAlbertoni: Any objections.
DaveBrowning: No objections.
nobu_ogura: No objections.
AOB
riccardoAlbertoni: About the next meeting, let's skip it, and move it to January.
… Let's say, Jan, 10th.
<riccardoAlbertoni> proposed: next DCAT submeeting on Jan, 10th.
<DaveBrowning> +1
<nobu_ogura> +1
AndreaPerego: +1
<riccardoAlbertoni> +1
RESOLUTION: next DCAT submeeting on Jan, 10th.
<riccardoAlbertoni> https://
riccardoAlbertoni: The file above ^^ summarises the open issues.
… If you can choose the issues with no assignee you can deal with, that would be great.
AndreaPerego: About the implementation report, do we have an idea when we have to deliver it?
riccardoAlbertoni: This will be next year.
[meeting adjourned]