stijn_goedertier_AIV: has presented the DCAT FPWD to the recent OGC meeting. There was discussion about whether any new DCT would be mapped to the new ISO standard
<AndreaPerego> 0 (was not there)
<stijn_goedertier_AIV> 0 (was not there)
<DaveBrowning> (not there)
DaveBrowning: given that we have few people in the meeting we will start with the discussion of the publicity of the FPWD
… but will defer other discussions to the next meeting
DaveBrowning: we need to have a positioning statement that spells out how our revised DCAT fits into the cataloguing world and what its benefits are
… The way that we are desigining DCAT gives is a position between schema.org and at the other end of the spectrum things like the ISO geospatial standards
… I am not aware of us putting this story together, something that shows the ecosystem. Perhaps we need to explain that DCAT is not a direct competitor with these other extremes
AndreaPerego: I think that we can tell the story. The use of DCAT / DCAT-AP was to provide cross-platform, cross-domain metadata harvesting
AndreaPerego: In the public sector there are catalogues coming from all sectors - there is a need to consistently map the standards for these systems into one for simple harvesting across administrartions
… At the government level there was a driver for having an alternative to INSPIRE etc also
… It was very clear with geoDCAT-AP that it was not replacing existing standards, but was providing an interoperable mapping that was consistent across administrations
… I see the same issue within the research community - we have islands that need connecting
AndreaPerego: JRC works with the public sector and the research community and we see data interchange but no interoperable, compatible approach to metadata and discovery
… I can provide some narrative that describes the approach (RDF and Linked Data) and the benefits. The geospatial community doesn't use global persistent identifiers. In many instances metadata is just free text (e.g. publisher is just the name - but this is provided in different ways, so we cannot easily aggregate from one provider)
… The use of URIs will remove that problem
… It would also enable better sharing across platforms
… There was a community request seeking a solution for cross-platform metadata interoperability. DCAT is a good solution. The problem is an editor and other tooling
DaveBrowning: this is the kind of information we need to give in dialogues with others
stijn_goedertier_AIV: I agree with AndreaPerego . The selling point of DCAT is interoperability between different communities
… DCAT brings the interoperability aspect. My work with the Flemish gov is (issue 223) geospatial and EAD for archives, and also the open data community
… The regional gov also want DCAT to be used as the exchange metadata format. They are building tools for using Geonetwork to edit (in XML) DCAT records
DaveBrowning: This sounds like we need to take AndreaPerego up on the offer of pulling together some narrative. The solution to the 223 - this is why DCAT is perfectly positioned to act as a broad cross-domain interoperability standard.
AndreaPerego: we could put this motivational text in the text discussing DCAT uses - there are examples at the beginning of the text.
DaveBrowning: I am concerned about the structure of the document and it's size. We don't want to end up with a doc that is too long. The end section on alignment with other standards and even quite simple alignments make the doc mushroom in size.
<AndreaPerego> Agree the alignment section is dangerous. I see it as a separate work.
DaveBrowning: we need to perhaps split this off
AndreaPerego: I was thinking that we could publish a separate doc (working draft) for the alignment. We already have docs that were done by others that could be reused
Action: AndreaPerego to draft some text about the drivers for DCAT
<trackbot> Sorry, but no Tracker is associated with this channel.
<DaveBrowning> PWinstanley: At recent meeting, I was talking to certain people about using DCAT to bind together something
<DaveBrowning> PWinstanley: Binding together information assets behind decisions or new directive to act as reification - slightly different to how its been done.
<DaveBrowning> PWinstanley: This might motivate a conversation 'in the margins' about DCAT role in organisation of information assets
<stijn_goedertier_AIV> +1 to the comment of Peter, the expanded scope of DCAT opens the door to better manage information assets throughout the public sector. It mostly need good URIs. Revisiting the Linked Data vision.
<stijn_goedertier_AIV> Thanks everybody
<AndreaPerego> [meeting adjourned]
Succeeded: s/regrest+RiccardoAlbertoni, Nick Car, Simon Cox, Alejandra Gonzalez-Beltran//
Succeeded: s/regrest+ RiccardoAlbertoni, Nick Car, Simon Cox, Alejandra Gonzalez-Beltran//