Revision of DCAT-AP Working Group Meeting 1 13/03/2015 PwC EU Services

Content 1. Revision process 2. Scope criteria 3. Received input 4. Proposed issues

Revision Process - phases 5. Release publication 4. Release endorsement 3. Release preparation 2. Request resolution 1. Request handling

Revision Process - request resolution Establish Working Group Governance Committee Elaborate drafts and discuss in scheduled meetings and calls Working Group Finalise draft for public review Working Group Publish draft for public review Governance Committee Resolve public comments Working Group

Scope criteria Change requests need to meet the following scope criteria in order to be considered for the revised version of DCAT-AP: Improve the discovery of datasets Ensure compliance with DCAT Ensure simplicity: keep a narrow scope Ensure application domain neutrality

Scope criteria Improve the discovery of datasets... meaning that we will give priority to those aspects that can be used in searching and navigating and that we will not handle requests that have to do with dataset management and operational issues. Implementation advice of a general nature can be included in the descriptions in chapters 6, 7 and 8, but we will not add further deployment advice for specific operational environments.

Scope criteria Ensure compliance with DCAT... meaning that we will not try to re-model DCAT or replace properties that already exist in DCAT by others that do more or less the same thing. If adding elements, we will only add those that can be re-used from existing namespaces, i.e. we’re not going to create new terms for which we need to create and maintain a namespace.

Scope criteria Ensure simplicity: keep a narrow scope... meaning that we only add things for which there is evidence that they are needed and that the information is commonly available in existing systems; if there are several ways to meet a requirement, we choose the simplest one that requires the least effort to provide and process the information.

Scope criteria Ensure application domain neutrality... meaning that we will not consider request that are only relevant for certain types of datasets. In particular, we refer requirements that are related to geographic characteristics and to handling of statistical data to the GeoDCAT and StatDCAT work.

Received input 14 Respondents 97 Requests 67 Issues Data.ac.uk Flemish Open Data Portal Fedict - Open Data Portals Catalan Open Data Portal National application profile Publications Office Joint Research Centre Pan-European Open Data Portal Open Data Support Datos.gob.es iMinds Aragón Open Data initiative Swedish Open Data Portal UK BE ES NO NL EU ES BE ES SE

Proposed issues CodeIssue category# PRProperties26 IMImplementing guidelines9 MOModel11 VOVocabularies7 COConsistency issues5 OBObligations and cardinalities4 MAMapping guidelines2 OPOperational issues2 EDEditorial1 Total67

Next steps Proposed dateTopic March 30, 2015Share the draft version of the revised DCAT-AP with the Working Group April 6, 2015Working Group to provide feedback on the draft Week of April 13, 2015 Working Group meeting to discuss the draft April 27, 2015Share the updated draft with the Working Group Week of May 4, 2015 Working Group to provide feedback on the updated draft Week of May 11, 2015 Working Group meeting to discuss the updated draft May 19 – June 19, 2015 Public review period Week of June 22, 2015 Working Group meeting to discuss the outcome of the public review period.

Join the SEMIC group on LinkedIn on Twitter Join the SEMIC community on Joinup Project Get involved Visit our initiatives