CINXE.COM

<!DOCTYPE html><html lang="en" dir="ltr"><head> <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"> <meta content="text/html; charset=utf-8" http-equiv="content-type"> <meta name="generator" content="ReSpec 35.1.1"> <style> span.example-title{text-transform:none} :is(aside,div).example,div.illegal-example{padding:.5em;margin:1em 0;position:relative;clear:both} div.illegal-example{color:red} div.illegal-example p{color:#000} aside.example div.example{border-left-width:.1em;border-color:#999;background:#fff} </style> <style> .issue-label{text-transform:initial} .warning>p:first-child{margin-top:0} .warning{padding:.5em;border-left-width:.5em;border-left-style:solid} span.warning{padding:.1em .5em .15em} .issue.closed span.issue-number{text-decoration:line-through} .issue.closed span.issue-number::after{content:" (Closed)";font-size:smaller} .warning{border-color:#f11;border-color:var(--warning-border,#f11);border-width:.2em;border-style:solid;background:#fbe9e9;background:var(--warning-bg,#fbe9e9);color:#000;color:var(--text,#000)} .warning-title:before{content:"⚠";font-size:1.3em;float:left;padding-right:.3em;margin-top:-.3em} li.task-list-item{list-style:none} input.task-list-item-checkbox{margin:0 .35em .25em -1.6em;vertical-align:middle} .issue a.respec-gh-label{padding:5px;margin:0 2px 0 2px;font-size:10px;text-transform:none;text-decoration:none;font-weight:700;border-radius:4px;position:relative;bottom:2px;border:none;display:inline-block} </style> <style> dfn{cursor:pointer} .dfn-panel{position:absolute;z-index:35;min-width:300px;max-width:500px;padding:.5em .75em;margin-top:.6em;font-family:"Helvetica Neue",sans-serif;font-size:small;background:#fff;background:var(--indextable-hover-bg,#fff);color:#000;color:var(--text,#000);box-shadow:0 1em 3em -.4em rgba(0,0,0,.3),0 0 1px 1px rgba(0,0,0,.05);box-shadow:0 1em 3em -.4em var(--tocsidebar-shadow,rgba(0,0,0,.3)),0 0 1px 1px var(--tocsidebar-shadow,rgba(0,0,0,.05));border-radius:2px} .dfn-panel:not(.docked)>.caret{position:absolute;top:-9px} .dfn-panel:not(.docked)>.caret::after,.dfn-panel:not(.docked)>.caret::before{content:"";position:absolute;border:10px solid transparent;border-top:0;border-bottom:10px solid #fff;border-bottom-color:var(--indextable-hover-bg,#fff);top:0} .dfn-panel:not(.docked)>.caret::before{border-bottom:9px solid #a2a9b1;border-bottom-color:var(--indextable-hover-bg,#a2a9b1)} .dfn-panel *{margin:0} .dfn-panel b{display:block;color:#000;color:var(--text,#000);margin-top:.25em} .dfn-panel ul a[href]{color:#333;color:var(--text,#333)} .dfn-panel>div{display:flex} .dfn-panel a.self-link{font-weight:700;margin-right:auto} .dfn-panel .marker{padding:.1em;margin-left:.5em;border-radius:.2em;text-align:center;white-space:nowrap;font-size:90%;color:#040b1c} .dfn-panel .marker.dfn-exported{background:#d1edfd;box-shadow:0 0 0 .125em #1ca5f940} .dfn-panel .marker.idl-block{background:#8ccbf2;box-shadow:0 0 0 .125em #0670b161} .dfn-panel a:not(:hover){text-decoration:none!important;border-bottom:none!important} .dfn-panel a[href]:hover{border-bottom-width:1px} .dfn-panel ul{padding:0} .dfn-panel li{margin-left:1em} .dfn-panel.docked{position:fixed;left:.5em;top:unset;bottom:2em;margin:0 auto;max-width:calc(100vw - .75em * 2 - .5em - .2em * 2);max-height:30vh;overflow:auto} </style> <title>Data Catalog Vocabulary (DCAT) - Version 3</title> <style> table.simple {width:100%;} #table-sdo-mapping th:first-child , #table-sdo-mapping td:first-child {text-align:right;} .prop-list {columns:4;} </style> <style id="respec-mainstyle"> @keyframes pop{ 0%{transform:scale(1,1)} 25%{transform:scale(1.25,1.25);opacity:.75} 100%{transform:scale(1,1)} } a.internalDFN{color:inherit;border-bottom:1px solid #99c;text-decoration:none} a.externalDFN{color:inherit;border-bottom:1px dotted #ccc;text-decoration:none} a.bibref{text-decoration:none} .respec-offending-element:target{animation:pop .25s ease-in-out 0s 1} .respec-offending-element,a[href].respec-offending-element{text-decoration:red wavy underline} @supports not (text-decoration:red wavy underline){ .respec-offending-element:not(pre){display:inline-block} .respec-offending-element{background:url(data:image/gif;base64,R0lGODdhBAADAPEAANv///8AAP///wAAACwAAAAABAADAEACBZQjmIAFADs=) bottom repeat-x} } #references :target{background:#eaf3ff;animation:pop .4s ease-in-out 0s 1} cite .bibref{font-style:normal} a[href].orcid{padding-left:4px;padding-right:4px} a[href].orcid>svg{margin-bottom:-2px} ol.tof,ul.tof{list-style:none outside none} .caption{margin-top:.5em;font-style:italic} #issue-summary>ul{column-count:2} #issue-summary li{list-style:none;display:inline-block} details.respec-tests-details{margin-left:1em;display:inline-block;vertical-align:top} details.respec-tests-details>*{padding-right:2em} details.respec-tests-details[open]{z-index:999999;position:absolute;border:thin solid #cad3e2;border-radius:.3em;background-color:#fff;padding-bottom:.5em} details.respec-tests-details[open]>summary{border-bottom:thin solid #cad3e2;padding-left:1em;margin-bottom:1em;line-height:2em} details.respec-tests-details>ul{width:100%;margin-top:-.3em} details.respec-tests-details>li{padding-left:1em} .self-link:hover{opacity:1;text-decoration:none;background-color:transparent} aside.example .marker>a.self-link{color:inherit} .header-wrapper{display:flex;align-items:baseline} :is(h2,h3,h4,h5,h6):not(#toc>h2,#abstract>h2,#sotd>h2,.head>h2){position:relative;left:-.5em} :is(h2,h3,h4,h5,h6):not(#toch2)+a.self-link{color:inherit;order:-1;position:relative;left:-1.1em;font-size:1rem;opacity:.5} :is(h2,h3,h4,h5,h6)+a.self-link::before{content:"§";text-decoration:none;color:var(--heading-text)} :is(h2,h3)+a.self-link{top:-.2em} :is(h4,h5,h6)+a.self-link::before{color:#000} @media (max-width:767px){ dd{margin-left:0} } @media print{ .removeOnSave{display:none} } </style> <meta name="color-scheme" content="light"> <meta name="description" content="DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. This document defines the schema and provides examples for its use."> <link rel="canonical" href="https://www.w3.org/TR/vocab-dcat-3/"> <script type="application/ld+json">{ "@context": [ "http://schema.org", { "@vocab": "http://schema.org/", "@language": "en", "w3p": "http://www.w3.org/2001/02pd/rec54#", "foaf": "http://xmlns.com/foaf/0.1/", "datePublished": { "@type": "http://www.w3.org/2001/XMLSchema#date" }, "inLanguage": { "@language": null }, "isBasedOn": { "@type": "@id" }, "license": { "@type": "@id" } } ], "id": "https://www.w3.org/TR/vocab-dcat-3/", "type": [ "TechArticle", "w3p:REC" ], "name": "Data Catalog Vocabulary (DCAT) - Version 3", "inLanguage": "en", "license": "https://www.w3.org/copyright/software-license-2023/", "datePublished": "2024-08-22", "copyrightHolder": { "name": "World Wide Web Consortium", "url": "https://www.w3.org/" }, "discussionUrl": "https://github.com/w3c/dxwg/issues/", "alternativeHeadline": "", "isBasedOn": "https://www.w3.org/TR/2020/REC-vocab-dcat-3-20200204/", "description": "DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web.\n This document defines the schema and provides examples for its use.", "editor": [ { "type": "Person", "name": "Riccardo Albertoni", "url": "https://imati.cnr.it/mypage.php?idk=PG-62", "worksFor": { "name": "Invited Expert / CNR - Consiglio Nazionale delle Ricerche, Italy", "url": "https://www.cnr.it/" } }, { "type": "Person", "name": "David Browning", "worksFor": { "name": "Invited Expert" } }, { "type": "Person", "name": "Simon J D Cox", "url": "https://orcid.org/0000-0002-3884-3420", "worksFor": { "name": "Invited Expert" } }, { "type": "Person", "name": "Alejandra Gonzalez Beltran", "url": "https://www.scd.stfc.ac.uk/Pages/Alejandra-Gonzalez-Beltran.aspx", "worksFor": { "name": "Invited Expert / Scientific Computing Department, Science and Technology Facilities Council, UK", "url": "https://stfc.ukri.org/" } }, { "type": "Person", "name": "Andrea Perego", "worksFor": { "name": "Invited Expert" } }, { "type": "Person", "name": "Peter Winstanley", "worksFor": { "name": "Invited Expert" } } ], "contributor": [], "citation": [ { "id": "https://www.dublincore.org/specifications/dublin-core/dcmi-terms/", "type": "TechArticle", "name": "DCMI Metadata Terms", "url": "https://www.dublincore.org/specifications/dublin-core/dcmi-terms/", "creator": [ { "name": "DCMI Usage Board" } ], "publisher": { "name": "DCMI" } }, { "id": "https://www.w3.org/TR/vocab-dcat/", "type": "TechArticle", "name": "Data Catalog Vocabulary (DCAT)", "url": "https://www.w3.org/TR/vocab-dcat/", "creator": [ { "name": "Fadi Maali" }, { "name": "John Erickson" } ], "publisher": { "name": "W3C" } }, { "id": "http://xmlns.com/foaf/spec", "type": "TechArticle", "name": "FOAF Vocabulary Specification 0.99 (Paddington Edition)", "url": "http://xmlns.com/foaf/spec", "creator": [ { "name": "Dan Brickley" }, { "name": "Libby Miller" } ], "publisher": { "name": "FOAF project" } }, { "id": "http://www.w3.org/ns/locn", "type": "TechArticle", "name": "ISA Programme Location Core Vocabulary", "url": "http://www.w3.org/ns/locn", "creator": [ { "name": "Andrea Perego" }, { "name": "Michael Lutz" } ], "publisher": { "name": "European Commission" } }, { "id": "https://www.w3.org/TR/odrl-vocab/", "type": "TechArticle", "name": "ODRL Vocabulary & Expression 2.2", "url": "https://www.w3.org/TR/odrl-vocab/", "creator": [ { "name": "Renato Iannella" }, { "name": "Michael Steidl" }, { "name": "Stuart Myles" }, { "name": "Víctor Rodríguez-Doncel" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/owl2-syntax/", "type": "TechArticle", "name": "OWL 2 Web Ontology Language Structural Specification and Functional-Style Syntax (Second Edition)", "url": "https://www.w3.org/TR/owl2-syntax/", "creator": [ { "name": "Boris Motik" }, { "name": "Peter Patel-Schneider" }, { "name": "Bijan Parsia" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/prov-o/", "type": "TechArticle", "name": "PROV-O: The PROV Ontology", "url": "https://www.w3.org/TR/prov-o/", "creator": [ { "name": "Timothy Lebo" }, { "name": "Satya Sahoo" }, { "name": "Deborah McGuinness" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/rdf-syntax-grammar/", "type": "TechArticle", "name": "RDF 1.1 XML Syntax", "url": "https://www.w3.org/TR/rdf-syntax-grammar/", "creator": [ { "name": "Fabien Gandon" }, { "name": "Guus Schreiber" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/rdf-schema/", "type": "TechArticle", "name": "RDF Schema 1.1", "url": "https://www.w3.org/TR/rdf-schema/", "creator": [ { "name": "Dan Brickley" }, { "name": "Ramanathan Guha" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/skos-reference/", "type": "TechArticle", "name": "SKOS Simple Knowledge Organization System Reference", "url": "https://www.w3.org/TR/skos-reference/", "creator": [ { "name": "Alistair Miles" }, { "name": "Sean Bechhofer" } ], "publisher": { "name": "W3C" } }, { "id": "https://spdx.org/rdf/spdx-terms-v2.2/", "type": "TechArticle", "name": "SPDX 2.2", "url": "https://spdx.org/rdf/spdx-terms-v2.2/", "publisher": { "name": "SPDX" } }, { "id": "https://www.w3.org/TR/owl-time/", "type": "TechArticle", "name": "Time Ontology in OWL", "url": "https://www.w3.org/TR/owl-time/", "creator": [ { "name": "Simon Cox" }, { "name": "Chris Little" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/vcard-rdf/", "type": "TechArticle", "name": "vCard Ontology - for describing People and Organizations", "url": "https://www.w3.org/TR/vcard-rdf/", "creator": [ { "name": "Renato Iannella" }, { "name": "James McKinney" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/xmlschema11-2/", "type": "TechArticle", "name": "W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes", "url": "https://www.w3.org/TR/xmlschema11-2/", "creator": [ { "name": "David Peterson" }, { "name": "Sandy Gao" }, { "name": "Ashok Malhotra" }, { "name": "Michael Sperberg-McQueen" }, { "name": "Henry Thompson" }, { "name": "Paul V. Biron" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/owl2-overview/", "type": "TechArticle", "name": "OWL 2 Web Ontology Language Document Overview (Second Edition)", "url": "https://www.w3.org/TR/owl2-overview/", "creator": [ { "name": "W3C OWL Working Group" } ], "publisher": { "name": "W3C" } }, { "id": "http://dublincore.org/documents/dces/", "type": "TechArticle", "name": "Dublin Core Metadata Element Set, Version 1.1", "url": "http://dublincore.org/documents/dces/", "publisher": { "name": "DCMI" } }, { "id": "https://www.w3.org/TR/odrl-model/", "type": "TechArticle", "name": "ODRL Information Model 2.2", "url": "https://www.w3.org/TR/odrl-model/", "creator": [ { "name": "Renato Iannella" }, { "name": "Serena Villata" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/dwbp/", "type": "TechArticle", "name": "Data on the Web Best Practices", "url": "https://www.w3.org/TR/dwbp/", "creator": [ { "name": "Bernadette Farias Loscio" }, { "name": "Caroline Burle" }, { "name": "Newton Calegari" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.iana.org/assignments/media-types/", "type": "TechArticle", "name": "Media Types", "url": "https://www.iana.org/assignments/media-types/", "publisher": { "name": "IANA" } }, { "id": "https://docs.ogc.org/is/22-047r1/22-047r1.html", "type": "TechArticle", "name": "OGC GeoSPARQL - A Geographic Query Language for RDF Data", "url": "https://docs.ogc.org/is/22-047r1/22-047r1.html", "creator": [ { "name": "Nicholas J. Car" }, { "name": "Timo Homburg" }, { "name": "Matthew Perry" }, { "name": "Frans Knibbe" }, { "name": "Simon J.D. Cox" }, { "name": "Joseph Abhayaratna" }, { "name": "Mathias Bonduel" }, { "name": "Paul J. Cripps" }, { "name": "Krzysztof Janowicz" } ], "publisher": { "name": "OGC" } }, { "id": "https://www.w3.org/TR/UNDERSTANDING-WCAG20/", "type": "TechArticle", "name": "Understanding WCAG 2.0", "url": "https://www.w3.org/TR/UNDERSTANDING-WCAG20/", "creator": [ { "name": "Michael Cooper" }, { "name": "Andrew Kirkpatrick" }, { "name": "Joshue O'Connor" } ], "publisher": { "name": "W3C" } }, { "id": "https://pav-ontology.github.io/pav/", "type": "TechArticle", "name": "PAV - Provenance, Authoring and Versioning. Version 2.3.1", "url": "https://pav-ontology.github.io/pav/", "creator": [ { "name": "Paolo Ciccarese" }, { "name": "Stian Soiland-Reyes" } ], "publisher": { "name": "Mind Informatics" } }, { "id": "https://www.rfc-editor.org/rfc/rfc2119", "type": "TechArticle", "name": "Key words for use in RFCs to Indicate Requirement Levels", "url": "https://www.rfc-editor.org/rfc/rfc2119", "creator": [ { "name": "S. Bradner" } ], "publisher": { "name": "IETF" } }, { "id": "https://www.rfc-editor.org/rfc/rfc8174", "type": "TechArticle", "name": "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", "url": "https://www.rfc-editor.org/rfc/rfc8174", "creator": [ { "name": "B. Leiba" } ], "publisher": { "name": "IETF" } }, { "id": "https://www.w3.org/TR/vocab-adms/", "type": "TechArticle", "name": "Asset Description Metadata Schema (ADMS)", "url": "https://www.w3.org/TR/vocab-adms/", "creator": [ { "name": "Phil Archer" }, { "name": "Gofran Shukair" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/vocab-dcat-2/", "type": "TechArticle", "name": "Data Catalog Vocabulary (DCAT) - Version 2", "url": "https://www.w3.org/TR/vocab-dcat-2/", "creator": [ { "name": "Riccardo Albertoni" }, { "name": "David Browning" }, { "name": "Simon Cox" }, { "name": "Alejandra Gonzalez Beltran" }, { "name": "Andrea Perego" }, { "name": "Peter Winstanley" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/vocab-dcat-1/", "type": "TechArticle", "name": "Data Catalog Vocabulary (DCAT)", "url": "https://www.w3.org/TR/vocab-dcat-1/", "creator": [ { "name": "Fadi Maali" }, { "name": "John Erickson" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/dcat-ucr/", "type": "TechArticle", "name": "Dataset Exchange Use Cases and Requirements", "url": "https://www.w3.org/TR/dcat-ucr/", "creator": [ { "name": "Jaroslav Pullmann" }, { "name": "Rob Atkinson" }, { "name": "Antoine Isaac" }, { "name": "Ixchel Faniel" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/void/", "type": "TechArticle", "name": "Describing Linked Datasets with the VoID Vocabulary", "url": "https://www.w3.org/TR/void/", "creator": [ { "name": "Keith Alexander" }, { "name": "Richard Cyganiak" }, { "name": "Michael Hausenblas" }, { "name": "Jun Zhao" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/html-rdfa/", "type": "TechArticle", "name": "HTML+RDFa 1.1 - Second Edition", "url": "https://www.w3.org/TR/html-rdfa/", "creator": [ { "name": "Manu Sporny" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/", "type": "TechArticle", "name": "Notation3 (N3): A readable RDF syntax", "url": "https://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/", "creator": [ { "name": "Tim Berners-Lee" }, { "name": "Dan Connolly" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/turtle/", "type": "TechArticle", "name": "RDF 1.1 Turtle", "url": "https://www.w3.org/TR/turtle/", "creator": [ { "name": "Eric Prud'hommeaux" }, { "name": "Gavin Carothers" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/json-ld/", "type": "TechArticle", "name": "JSON-LD 1.0", "url": "https://www.w3.org/TR/json-ld/", "creator": [ { "name": "Manu Sporny" }, { "name": "Gregg Kellogg" }, { "name": "Markus Lanthaler" } ], "publisher": { "name": "W3C" } }, { "id": "https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe", "type": "TechArticle", "name": "DCAT Application Profile for data portals in Europe. Version 2.0.1", "url": "https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe", "publisher": { "name": "European Commission" } }, { "id": "https://www.w3.org/TR/hcls-dataset/", "type": "TechArticle", "name": "Dataset Descriptions: HCLS Community Profile", "url": "https://www.w3.org/TR/hcls-dataset/", "creator": [ { "name": "Alasdair Gray" }, { "name": "M. Scott Marshall" }, { "name": "Michel Dumontier" } ], "publisher": { "name": "W3C" } }, { "id": "https://datatagsuite.github.io/docs/html/", "type": "TechArticle", "name": "Data Tag Suite", "url": "https://datatagsuite.github.io/docs/html/", "creator": [ { "name": "Alejandra Gonzalez-Beltran" }, { "name": "Philippe Rocca-Serra" } ], "publisher": { "name": "NIH Big Data 2 Knowledge bioCADDIE and NIH Data Commons projects" } }, { "id": "https://www.w3.org/TR/vocab-dqv/", "type": "TechArticle", "name": "Data on the Web Best Practices: Data Quality Vocabulary", "url": "https://www.w3.org/TR/vocab-dqv/", "creator": [ { "name": "Riccardo Albertoni" }, { "name": "Antoine Isaac" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/EARL10-Schema/", "type": "TechArticle", "name": "Evaluation and Report Language (EARL) 1.0 Schema", "url": "https://www.w3.org/TR/EARL10-Schema/", "creator": [ { "name": "Shadi Abou-Zahra" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/annotation-vocab/", "type": "TechArticle", "name": "Web Annotation Vocabulary", "url": "https://www.w3.org/TR/annotation-vocab/", "creator": [ { "name": "Robert Sanderson" }, { "name": "Paolo Ciccarese" }, { "name": "Benjamin Young" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/vocab-data-cube/", "type": "TechArticle", "name": "The RDF Data Cube Vocabulary", "url": "https://www.w3.org/TR/vocab-data-cube/", "creator": [ { "name": "Richard Cyganiak" }, { "name": "Dave Reynolds" } ], "publisher": { "name": "W3C" } }, { "id": "https://schema.org/", "type": "TechArticle", "name": "Schema.org", "url": "https://schema.org/" }, { "id": "https://www.w3.org/1999/xhtml/vocab", "type": "TechArticle", "name": "XHTML Vocabulary", "url": "https://www.w3.org/1999/xhtml/vocab", "creator": [ { "name": "XHTML 2 Working Group" } ], "publisher": { "name": "W3C" } }, { "id": "http://dublincore.org/documents/profile-guidelines/", "type": "TechArticle", "name": "Guidelines for Dublin Core Application Profiles", "url": "http://dublincore.org/documents/profile-guidelines/", "creator": [ { "name": "Karen Coyle" }, { "name": "Thomas Baker" } ], "publisher": { "name": "DCMI" } }, { "id": "https://www.rfc-editor.org/rfc/rfc3987", "type": "TechArticle", "name": "Internationalized Resource Identifiers (IRIs)", "url": "https://www.rfc-editor.org/rfc/rfc3987", "creator": [ { "name": "M. Duerst" }, { "name": "M. Suignard" } ], "publisher": { "name": "IETF" } }, { "id": "https://www.w3.org/TR/rdf11-primer/", "type": "TechArticle", "name": "RDF 1.1 Primer", "url": "https://www.w3.org/TR/rdf11-primer/", "creator": [ { "name": "Guus Schreiber" }, { "name": "Yves Raimond" } ], "publisher": { "name": "W3C" } }, { "id": "http://patterns.dataincubator.org/book/", "type": "TechArticle", "name": "Linked Data Patterns: A pattern catalogue for modelling, publishing, and consuming Linked Data", "url": "http://patterns.dataincubator.org/book/", "creator": [ { "name": "Leigh Dodds" }, { "name": "Ian Davis" } ] }, { "id": "https://www.iso.org/standard/53798.html", "type": "TechArticle", "name": "Geographic information -- Metadata -- Part 1: Fundamentals", "url": "https://www.iso.org/standard/53798.html", "creator": [ { "name": "ISO/TC 211" } ], "publisher": { "name": "ISO" } }, { "id": "https://schema.datacite.org/", "type": "TechArticle", "name": "DataCite Metadata Schema", "url": "https://schema.datacite.org/", "creator": [ { "name": "DataCite Metadata Working Group" } ], "publisher": { "name": "DataCite e.V." } }, { "id": "https://doi.org/10.2312/re3.008", "type": "TechArticle", "name": "Metadata Schema for the Description of Research Data Repositories: version 3", "url": "https://doi.org/10.2312/re3.008", "creator": [ { "name": "Jessika Rücknagel" } ], "publisher": { "name": "GFZ Potsdam" } }, { "id": "https://www.w3.org/TR/vocab-org/", "type": "TechArticle", "name": "The Organization Ontology", "url": "https://www.w3.org/TR/vocab-org/", "creator": [ { "name": "Dave Reynolds" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/NOTE-datetime", "type": "TechArticle", "name": "Date and Time Formats", "url": "https://www.w3.org/TR/NOTE-datetime", "publisher": { "name": "W3C" } }, { "id": "https://www.rfc-editor.org/rfc/rfc5646", "type": "TechArticle", "name": "Tags for Identifying Languages", "url": "https://www.rfc-editor.org/rfc/rfc5646", "creator": [ { "name": "A. Phillips, Ed." }, { "name": "M. Davis, Ed." } ], "publisher": { "name": "IETF" } }, { "id": "https://www.w3.org/TR/sparql11-query/", "type": "TechArticle", "name": "SPARQL 1.1 Query Language", "url": "https://www.w3.org/TR/sparql11-query/", "creator": [ { "name": "Steven Harris" }, { "name": "Andy Seaborne" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/shacl/", "type": "TechArticle", "name": "Shapes Constraint Language (SHACL)", "url": "https://www.w3.org/TR/shacl/", "creator": [ { "name": "Holger Knublauch" }, { "name": "Dimitris Kontokostas" } ], "publisher": { "name": "W3C" } }, { "id": "http://shex.io/shex-semantics/", "type": "TechArticle", "name": "Shape Expressions Language 2.1", "url": "http://shex.io/shex-semantics/", "publisher": { "name": "Shape Expressions W3C Community Group" } }, { "id": "https://github.com/vivo-isf/vivo-isf", "type": "TechArticle", "name": "VIVO-ISF Data Standard", "url": "https://github.com/vivo-isf/vivo-isf" }, { "id": "https://github.com/ewilderj/doap/wiki", "type": "TechArticle", "name": "Description of a Project", "url": "https://github.com/ewilderj/doap/wiki", "creator": [ { "name": "Edd Wilder-James" } ] }, { "id": "http://dbpedia.org/ontology/", "type": "TechArticle", "name": "DBPedia ontology", "url": "http://dbpedia.org/ontology/" }, { "id": "https://semiceu.github.io/GeoDCAT-AP/releases/", "type": "TechArticle", "name": "GeoDCAT-AP: A geospatial extension for the DCAT application profile for data portals in Europe", "url": "https://semiceu.github.io/GeoDCAT-AP/releases/", "publisher": { "name": "European Commission" } }, { "id": "https://docs.italia.it/italia/daf/linee-guida-cataloghi-dati-dcat-ap-it/it/stabile/dcat-ap_it.html", "type": "TechArticle", "name": "Profilo metadatazione DCAT-AP_IT", "url": "https://docs.italia.it/italia/daf/linee-guida-cataloghi-dati-dcat-ap-it/it/stabile/dcat-ap_it.html", "publisher": { "name": "AgID & Team Digitale" } }, { "id": "https://web.archive.org/web/20200506120557/https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/news/geodcat-apit", "type": "TechArticle", "name": "GeoDCAT-AP in Italy, the national guidelines published", "url": "https://web.archive.org/web/20200506120557/https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/news/geodcat-apit" }, { "id": "https://www.unidata.ucar.edu/software/netcdf/", "type": "TechArticle", "name": "Network Common Data Form (NetCDF)", "url": "https://www.unidata.ucar.edu/software/netcdf/", "publisher": { "name": "UNIDATA" } }, { "id": "http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/", "type": "TechArticle", "name": "INSPIRE Registry: Spatial data service types", "url": "http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/", "publisher": { "name": "European Commission" } }, { "id": "https://www.openapis.org/", "type": "TechArticle", "name": "OpenAPI Specification", "url": "https://www.openapis.org/", "creator": [ { "name": "Darrell Miller" }, { "name": "Jason Harmon" }, { "name": "Jeremy Whitlock" }, { "name": "Marsh Gardiner" }, { "name": "Mike Ralphson" }, { "name": "Ron Ratovsky" }, { "name": "Tony Tam" }, { "name": "Uri Sarid" } ], "publisher": { "name": "OpenAPI Initiative" } }, { "id": "http://www.opengeospatial.org/standards/wfs", "type": "TechArticle", "name": "Web Feature Service 2.0 Interface Standard", "url": "http://www.opengeospatial.org/standards/wfs", "creator": [ { "name": "Panagiotis (Peter) A. Vretanos" } ], "publisher": { "name": "OGC" } }, { "id": "https://www.iso.org/standard/42136.html", "type": "TechArticle", "name": "Geographic information -- Web Feature Service", "url": "https://www.iso.org/standard/42136.html", "creator": [ { "name": "ISO/TC 211" } ], "publisher": { "name": "ISO" } }, { "id": "http://www.opengeospatial.org/standards/wms", "type": "TechArticle", "name": "Web Map Service Implementation Specification", "url": "http://www.opengeospatial.org/standards/wms", "creator": [ { "name": "Jeff de la Beaujardiere" } ], "publisher": { "name": "OGC" } }, { "id": "https://www.iso.org/standard/32546.html", "type": "TechArticle", "name": "Geographic information -- Web map server interface", "url": "https://www.iso.org/standard/32546.html", "creator": [ { "name": "ISO/TC 211" } ], "publisher": { "name": "ISO" } }, { "id": "https://www.w3.org/TR/sparql11-service-description/", "type": "TechArticle", "name": "SPARQL 1.1 Service Description", "url": "https://www.w3.org/TR/sparql11-service-description/", "creator": [ { "name": "Gregory Williams" } ], "publisher": { "name": "W3C" } }, { "id": "https://github.com/dewitt/opensearch/blob/master/opensearch-1-1-draft-6.md", "type": "TechArticle", "name": "OpenSearch 1.1 Draft 6", "url": "https://github.com/dewitt/opensearch/blob/master/opensearch-1-1-draft-6.md", "creator": [ { "name": "DeWitt Clinton" } ], "publisher": { "name": "OpenSearch" } }, { "id": "https://www.w3.org/TR/wsdl20/", "type": "TechArticle", "name": "Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language", "url": "https://www.w3.org/TR/wsdl20/", "creator": [ { "name": "Roberto Chinnici" }, { "name": "Jean-Jacques Moreau" }, { "name": "Arthur Ryman" }, { "name": "Sanjiva Weerawarana" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.hydra-cg.com/spec/latest/core/", "type": "TechArticle", "name": "Hydra Core Vocabulary", "url": "https://www.hydra-cg.com/spec/latest/core/", "creator": [ { "name": "Markus Lanthaler" } ], "publisher": { "name": "Hydra W3C Community Group" } }, { "id": "https://www.iso.org/standard/26020.html", "type": "TechArticle", "name": "Geographic information -- Metadata", "url": "https://www.iso.org/standard/26020.html", "creator": [ { "name": "ISO/TC 211" } ], "publisher": { "name": "ISO" } }, { "id": "https://www.iana.org/assignments/link-relations/", "type": "TechArticle", "name": "Link Relations", "url": "https://www.iana.org/assignments/link-relations/", "publisher": { "name": "IANA" } }, { "id": "https://www.w3.org/TR/sdw-bp/", "type": "TechArticle", "name": "Spatial Data on the Web Best Practices", "url": "https://www.w3.org/TR/sdw-bp/", "creator": [ { "name": "Payam Barnaghi" }, { "name": "Jeremy Tandy" }, { "name": "Linda van den Brink" }, { "name": "Timo Homburg" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.iso.org/standard/43506.html", "type": "TechArticle", "name": "Information and documentation -- Digital object identifier system", "url": "https://www.iso.org/standard/43506.html", "creator": [ { "name": "ISO/TC 46/SC 9" } ], "publisher": { "name": "ISO" } }, { "id": "https://www.w3.org/TR/rdf11-concepts/", "type": "TechArticle", "name": "RDF 1.1 Concepts and Abstract Syntax", "url": "https://www.w3.org/TR/rdf11-concepts/", "creator": [ { "name": "Richard Cyganiak" }, { "name": "David Wood" }, { "name": "Markus Lanthaler" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.rfc-editor.org/rfc/rfc3986", "type": "TechArticle", "name": "Uniform Resource Identifier (URI): Generic Syntax", "url": "https://www.rfc-editor.org/rfc/rfc3986", "creator": [ { "name": "T. Berners-Lee" }, { "name": "R. Fielding" }, { "name": "L. Masinter" } ], "publisher": { "name": "IETF" } }, { "id": "https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml", "type": "TechArticle", "name": "Uniform Resource Identifier (URI) Schemes", "url": "https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml", "publisher": { "name": "IANA" } }, { "id": "https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/access-right", "type": "TechArticle", "name": "Named Authority List: Access rights", "url": "https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/access-right", "publisher": { "name": "Publications Office of the European Union" } }, { "id": "http://schema.theodi.org/odrs", "type": "TechArticle", "name": "Open Data Rights Statement Vocabulary", "url": "http://schema.theodi.org/odrs", "creator": [ { "name": "Leigh Dodds" } ], "publisher": { "name": "ODI" } }, { "id": "https://www.iso.org/standard/32553.html", "type": "TechArticle", "name": "Geographic information -- Procedures for item registration", "url": "https://www.iso.org/standard/32553.html", "creator": [ { "name": "ISO/TC 211" } ], "publisher": { "name": "ISO" } }, { "id": "https://web.archive.org/web/20210521035614/https://joinup.ec.europa.eu/svn/adms/ADMS_v1.00/ADMS_SKOS_v1.00.html", "type": "TechArticle", "name": "Joinup. ADMS Controlled Vocabularies", "url": "https://web.archive.org/web/20210521035614/https://joinup.ec.europa.eu/svn/adms/ADMS_v1.00/ADMS_SKOS_v1.00.html", "publisher": { "name": "European Commission" } }, { "id": "https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/dataset-status", "type": "TechArticle", "name": "Named Authority List: Dataset statuses", "url": "https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/dataset-status", "publisher": { "name": "Publications Office of the European Union" } }, { "id": "https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/concept-status", "type": "TechArticle", "name": "Named Authority List: Concept statuses", "url": "https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/concept-status", "publisher": { "name": "Publications Office of the European Union" } }, { "id": "https://github.com/UKGovLD/registry-core/wiki/Principles-and-concepts", "type": "TechArticle", "name": "Linked Data Registry - Principles and Concepts", "url": "https://github.com/UKGovLD/registry-core/wiki/Principles-and-concepts", "publisher": { "name": "UK Government Linked Data Working Group" } }, { "id": "http://iso25000.com/index.php/en/iso-25000-standards/iso-25012", "type": "TechArticle", "name": "ISO/IEC 25012 - Data Quality model", "url": "http://iso25000.com/index.php/en/iso-25000-standards/iso-25012" }, { "id": "https://doi.org/10.3233/SW-150175", "type": "TechArticle", "name": "Quality assessment for Linked Data: A Survey", "url": "https://doi.org/10.3233/SW-150175", "creator": [ { "name": "Amrapali Zaveri" } ], "publisher": { "name": "IOS Press" } }, { "id": "https://www.w3.org/TR/sparql11-protocol/", "type": "TechArticle", "name": "SPARQL 1.1 Protocol", "url": "https://www.w3.org/TR/sparql11-protocol/", "creator": [ { "name": "Lee Feigenbaum" }, { "name": "Gregory Williams" }, { "name": "Kendall Clark" }, { "name": "Elias Torres" } ], "publisher": { "name": "W3C" } }, { "id": "http://www.opengeospatial.org/standards/cat", "type": "TechArticle", "name": "Catalogue Services 3.0 - General Model", "url": "http://www.opengeospatial.org/standards/cat", "creator": [ { "name": "Douglas Nebert" }, { "name": "Uwe Voges" }, { "name": "Lorenzo Bigagli" } ], "publisher": { "name": "OGC" } }, { "id": "http://inspire.ec.europa.eu/metadata-codelist/DegreeOfConformity/", "type": "TechArticle", "name": "INSPIRE Registry: Degrees of conformity", "url": "http://inspire.ec.europa.eu/metadata-codelist/DegreeOfConformity/", "publisher": { "name": "European Commission" } }, { "id": "https://doi.org/10.1038/sdata.2016.18", "type": "TechArticle", "name": "The FAIR Guiding Principles for scientific data management and stewardship", "url": "https://doi.org/10.1038/sdata.2016.18", "creator": [ { "name": "Mark D. Wilkinson" } ], "publisher": { "name": "Nature" } }, { "id": "https://www.w3.org/TR/vocab-ssn/", "type": "TechArticle", "name": "Semantic Sensor Network Ontology", "url": "https://www.w3.org/TR/vocab-ssn/", "creator": [ { "name": "Armin Haller" }, { "name": "Krzysztof Janowicz" }, { "name": "Simon Cox" }, { "name": "Danh Le Phuoc" }, { "name": "Kerry Taylor" }, { "name": "Maxime Lefrançois" } ], "publisher": { "name": "W3C" } }, { "id": "https://joinup.ec.europa.eu/solution/statdcat-application-profile-data-portals-europe", "type": "TechArticle", "name": "StatDCAT-AP – DCAT Application Profile for description of statistical datasets. Version 1.0.1", "url": "https://joinup.ec.europa.eu/solution/statdcat-application-profile-data-portals-europe", "publisher": { "name": "European Commission" } }, { "id": "https://data.norge.no/specification/dcat-ap-no/", "type": "TechArticle", "name": "Standard for beskrivelse av datasett, datatjenester og datakataloger (DCAT-AP-NO)", "url": "https://data.norge.no/specification/dcat-ap-no/" }, { "id": "https://dcat-ap.de/def/", "type": "TechArticle", "name": "Vokabulare und Dokumente für DCAT-AP.de", "url": "https://dcat-ap.de/def/" }, { "id": "http://dcat.be/", "type": "TechArticle", "name": "Linking data portals across Belgium.", "url": "http://dcat.be/" }, { "id": "https://docs.dataportal.se/dcat/en/", "type": "TechArticle", "name": "DCAT-AP-SE: Clarifications, translations and explanations of DCAT-AP for Sweden", "url": "https://docs.dataportal.se/dcat/en/", "creator": [ { "name": "Matthias Palmér" } ] }, { "id": "https://www.w3.org/TR/2024/CR-vocab-dcat-3-20240118/", "type": "TechArticle", "name": "Data Catalog Vocabulary (DCAT) - Version 3", "url": "https://www.w3.org/TR/2024/CR-vocab-dcat-3-20240118/", "creator": [ { "name": "Simon Cox" }, { "name": "Andrea Perego" }, { "name": "Alejandra Gonzalez Beltran" }, { "name": "Peter Winstanley" }, { "name": "Riccardo Albertoni" }, { "name": "David Browning" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/2022/WD-vocab-dcat-3-20220510/", "type": "TechArticle", "name": "Data Catalog Vocabulary (DCAT) - Version 3", "url": "https://www.w3.org/TR/2022/WD-vocab-dcat-3-20220510/", "creator": [ { "name": "Riccardo Albertoni" }, { "name": "David Browning" }, { "name": "Simon Cox" }, { "name": "Alejandra Gonzalez Beltran" }, { "name": "Andrea Perego" }, { "name": "Peter Winstanley" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/2022/WD-vocab-dcat-3-20220111/", "type": "TechArticle", "name": "Data Catalog Vocabulary (DCAT) - Version 3", "url": "https://www.w3.org/TR/2022/WD-vocab-dcat-3-20220111/", "creator": [ { "name": "Riccardo Albertoni" }, { "name": "David Browning" }, { "name": "Simon Cox" }, { "name": "Alejandra Gonzalez Beltran" }, { "name": "Andrea Perego" }, { "name": "Peter Winstanley" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/2021/WD-vocab-dcat-3-20210504/", "type": "TechArticle", "name": "Data Catalog Vocabulary (DCAT) - Version 3", "url": "https://www.w3.org/TR/2021/WD-vocab-dcat-3-20210504/", "creator": [ { "name": "Riccardo Albertoni" }, { "name": "David Browning" }, { "name": "Simon Cox" }, { "name": "Alejandra Gonzalez Beltran" }, { "name": "Andrea Perego" }, { "name": "Peter Winstanley" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/TR/2020/WD-vocab-dcat-3-20201217/", "type": "TechArticle", "name": "Data Catalog Vocabulary (DCAT) - Version 3", "url": "https://www.w3.org/TR/2020/WD-vocab-dcat-3-20201217/", "creator": [ { "name": "Riccardo Albertoni" }, { "name": "David Browning" }, { "name": "Simon Cox" }, { "name": "Alejandra Gonzalez Beltran" }, { "name": "Andrea Perego" }, { "name": "Peter Winstanley" } ], "publisher": { "name": "W3C" } }, { "id": "https://www.w3.org/2003/01/geo/", "type": "TechArticle", "name": "Basic Geo (WGS84 lat/long) Vocabulary", "url": "https://www.w3.org/2003/01/geo/", "creator": [ { "name": "Dan Brickley" } ], "publisher": { "name": "W3C Semantic Web Interest Group" } }, { "id": "https://www.w3.org/TR/2020/REC-vocab-dcat-2-20200204/", "type": "TechArticle", "name": "Data Catalog Vocabulary (DCAT) - Version 2", "url": "https://www.w3.org/TR/2020/REC-vocab-dcat-2-20200204/", "creator": [ { "name": "Riccardo Albertoni" }, { "name": "David Browning" }, { "name": "Simon Cox" }, { "name": "Alejandra Gonzalez Beltran" }, { "name": "Andrea Perego" }, { "name": "Peter Winstanley" } ], "publisher": { "name": "W3C" } } ] }</script> <style> .hljs{--base:#fafafa;--mono-1:#383a42;--mono-2:#686b77;--mono-3:#717277;--hue-1:#0b76c5;--hue-2:#336ae3;--hue-3:#a626a4;--hue-4:#42803c;--hue-5:#ca4706;--hue-5-2:#c91243;--hue-6:#986801;--hue-6-2:#9a6a01} @media (prefers-color-scheme:dark){ .hljs{--base:#282c34;--mono-1:#abb2bf;--mono-2:#818896;--mono-3:#5c6370;--hue-1:#56b6c2;--hue-2:#61aeee;--hue-3:#c678dd;--hue-4:#98c379;--hue-5:#e06c75;--hue-5-2:#be5046;--hue-6:#d19a66;--hue-6-2:#e6c07b} } .hljs{display:block;overflow-x:auto;padding:.5em;color:#383a42;color:var(--mono-1,#383a42);background:#fafafa;background:var(--base,#fafafa)} .hljs-comment,.hljs-quote{color:#717277;color:var(--mono-3,#717277);font-style:italic} .hljs-doctag,.hljs-formula,.hljs-keyword{color:#a626a4;color:var(--hue-3,#a626a4)} .hljs-deletion,.hljs-name,.hljs-section,.hljs-selector-tag,.hljs-subst{color:#ca4706;color:var(--hue-5,#ca4706);font-weight:700} .hljs-literal{color:#0b76c5;color:var(--hue-1,#0b76c5)} .hljs-addition,.hljs-attribute,.hljs-meta-string,.hljs-regexp,.hljs-string{color:#42803c;color:var(--hue-4,#42803c)} .hljs-built_in,.hljs-class .hljs-title{color:#9a6a01;color:var(--hue-6-2,#9a6a01)} .hljs-attr,.hljs-number,.hljs-selector-attr,.hljs-selector-class,.hljs-selector-pseudo,.hljs-template-variable,.hljs-type,.hljs-variable{color:#986801;color:var(--hue-6,#986801)} .hljs-bullet,.hljs-link,.hljs-meta,.hljs-selector-id,.hljs-symbol,.hljs-title{color:#336ae3;color:var(--hue-2,#336ae3)} .hljs-emphasis{font-style:italic} .hljs-strong{font-weight:700} .hljs-link{text-decoration:underline} </style> <style> var{position:relative;cursor:pointer} var[data-type]::after,var[data-type]::before{position:absolute;left:50%;top:-6px;opacity:0;transition:opacity .4s;pointer-events:none} var[data-type]::before{content:"";transform:translateX(-50%);border-width:4px 6px 0 6px;border-style:solid;border-color:transparent;border-top-color:#222} var[data-type]::after{content:attr(data-type);transform:translateX(-50%) translateY(-100%);background:#222;text-align:center;font-family:"Dank Mono","Fira Code",monospace;font-style:normal;padding:6px;border-radius:3px;color:#daca88;text-indent:0;font-weight:400} var[data-type]:hover::after,var[data-type]:hover::before{opacity:1} </style> <script id="initialUserConfig" type="application/json">{ "doJsonLd": true, "specStatus": "REC", "errata": "https://w3c.github.io/dxwg/errata/", "crEnd": "2024-02-15", "implementationReportURI": "https://w3c.github.io/dxwg/dcat3-implementation-report/", "shortName": "vocab-dcat-3", "prevRecShortname": "vocab-dcat-2", "canonicalURI": "TR", "prevRecURI": "https://www.w3.org/TR/2020/REC-vocab-dcat-2-20200204/", "previousPublishDate": "2020-02-04", "previousMaturity": "REC", "edDraftURI": "https://w3c.github.io/dxwg/dcat/", "alternateFormats": [ { "label": "Turtle", "uri": "https://www.w3.org/ns/dcat.ttl" }, { "label": "RDF/XML", "uri": "https://www.w3.org/ns/dcat.rdf" }, { "label": "JSON-LD", "uri": "https://www.w3.org/ns/dcat.jsonld" } ], "editors": [ { "name": "Riccardo Albertoni", "orcid": "https://orcid.org/0000-0001-5648-2713", "company": "Invited Expert / CNR - Consiglio Nazionale delle Ricerche, Italy", "url": "https://imati.cnr.it/mypage.php?idk=PG-62", "companyURL": "https://www.cnr.it/", "w3cid": 72458 }, { "name": "David Browning", "company": "Invited Expert", "note": "Previously at Refinitiv.com", "w3cid": 98704 }, { "name": "Simon J D Cox", "orcid": "https://orcid.org/0000-0002-3884-3420", "company": "Invited Expert", "url": "https://orcid.org/0000-0002-3884-3420", "note": "Previously at CSIRO", "w3cid": 1796 }, { "name": "Alejandra Gonzalez Beltran", "orcid": "https://orcid.org/0000-0003-3499-8262", "company": "Invited Expert / Scientific Computing Department, Science and Technology Facilities Council, UK", "url": "https://www.scd.stfc.ac.uk/Pages/Alejandra-Gonzalez-Beltran.aspx", "companyURL": "https://stfc.ukri.org/", "note": "Previously at the University of Oxford", "w3cid": 61587 }, { "name": "Andrea Perego", "orcid": "https://orcid.org/0000-0001-9300-2694", "company": "Invited Expert", "w3cid": 40317 }, { "name": "Peter Winstanley", "company": "Invited Expert", "w3cid": 64374 } ], "formerEditors": [ { "name": "Fadi Maali", "company": "DERI", "companyURL": "https://en.wikipedia.org/wiki/Digital_Enterprise_Research_Institute" }, { "name": "John Erickson", "company": "Tetherless World Constellation (RPI)", "companyURL": "http://tw.rpi.edu/" } ], "otherLinks": [ { "key": "Contributors", "data": [ { "value": "Makx Dekkers", "href": "https://github.com/makxdekkers" } ] } ], "group": "dx", "wgPublicList": "public-dxwg-comments", "inlineCSS": "true", "lint": "false", "github": "https://github.com/w3c/dxwg/", "localBiblio": { "ADMS-SKOS": { "href": "https://web.archive.org/web/20210521035614/https://joinup.ec.europa.eu/svn/adms/ADMS_v1.00/ADMS_SKOS_v1.00.html", "title": "Joinup. ADMS Controlled Vocabularies", "publisher": "European Commission", "id": "adms-skos" }, "DATS": { "href": "https://datatagsuite.github.io/docs/html/", "title": "Data Tag Suite", "authors": [ "Alejandra Gonzalez-Beltran", "Philippe Rocca-Serra" ], "publisher": "NIH Big Data 2 Knowledge bioCADDIE and NIH Data Commons projects", "date": "2016", "id": "dats" }, "DBPEDIA-ONT": { "href": "http://dbpedia.org/ontology/", "title": "DBPedia ontology", "id": "dbpedia-ont" }, "DCAT-AP-SE": { "title": "DCAT-AP-SE: Clarifications, translations and explanations of DCAT-AP for Sweden", "href": "https://docs.dataportal.se/dcat/en/", "authors": [ "Matthias Palmér" ], "etAl": false, "id": "dcat-ap-se" }, "DCAT-BE": { "title": "Linking data portals across Belgium.", "href": "http://dcat.be/", "id": "dcat-be" }, "DCAT-AP-IT": { "title": "Profilo metadatazione DCAT-AP_IT", "href": "https://docs.italia.it/italia/daf/linee-guida-cataloghi-dati-dcat-ap-it/it/stabile/dcat-ap_it.html", "publisher": "AgID & Team Digitale", "id": "dcat-ap-it" }, "DCAT-AP-NO": { "title": "Standard for beskrivelse av datasett, datatjenester og datakataloger (DCAT-AP-NO)", "href": "https://data.norge.no/specification/dcat-ap-no/", "id": "dcat-ap-no" }, "DCAT-AP.de": { "title": "Vokabulare und Dokumente für DCAT-AP.de", "href": "https://dcat-ap.de/def/", "id": "dcat-ap.de" }, "DDI": { "href": "https://www.ddialliance.org/explore-documentation", "title": "Data Documentation Initiative", "publisher": "DDI Alliance" }, "DOAP": { "href": "https://github.com/ewilderj/doap/wiki", "title": "Description of a Project", "authors": [ "Edd Wilder-James" ], "id": "doap" }, "FAIR": { "title": "The FAIR Guiding Principles for scientific data management and stewardship", "authors": [ "Mark D. Wilkinson" ], "etAl": true, "status": "Scientific Data, vol. 3, Article nr. 160018", "publisher": "Nature", "href": "https://doi.org/10.1038/sdata.2016.18", "id": "fair" }, "FRAPO": { "href": "http://www.sparontologies.net/ontologies/frapo", "title": "FRAPO, the Funding, Research Administration and Projects Ontology", "authors": [ "David Shotton" ], "date": "04 September 2017" }, "GeoDCAT-AP-IT": { "title": "GeoDCAT-AP in Italy, the national guidelines published", "href": "https://web.archive.org/web/20200506120557/https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/news/geodcat-apit", "id": "geodcat-ap-it" }, "HYDRA": { "authors": [ "Markus Lanthaler" ], "href": "https://www.hydra-cg.com/spec/latest/core/", "title": "Hydra Core Vocabulary", "date": "15 March 2018", "publisher": "Hydra W3C Community Group", "status": "Unofficial Draft", "id": "hydra" }, "INSPIRE-DoC": { "href": "http://inspire.ec.europa.eu/metadata-codelist/DegreeOfConformity/", "title": "INSPIRE Registry: Degrees of conformity", "publisher": "European Commission", "id": "inspire-doc" }, "INSPIRE-SDST": { "href": "http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/", "title": "INSPIRE Registry: Spatial data service types", "publisher": "European Commission", "id": "inspire-sdst" }, "ISO-IEC-25012": { "title": "ISO/IEC 25012 - Data Quality model", "href": "http://iso25000.com/index.php/en/iso-25000-standards/iso-25012", "id": "iso-iec-25012" }, "ISO-26324": { "authors": [ "ISO/TC 46/SC 9" ], "href": "https://www.iso.org/standard/43506.html", "title": "Information and documentation -- Digital object identifier system", "publisher": "ISO", "status": "International Standard", "date": "2012", "id": "iso-26324" }, "LinkedDataPatterns": { "title": "Linked Data Patterns: A pattern catalogue for modelling, publishing, and consuming Linked Data", "authors": [ "Leigh Dodds", "Ian Davis" ], "date": "31 May 2012", "href": "http://patterns.dataincubator.org/book/", "id": "linkeddatapatterns" }, "EUV-AR": { "href": "https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/access-right", "title": "Named Authority List: Access rights", "publisher": "Publications Office of the European Union", "id": "euv-ar" }, "EUV-CS": { "href": "https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/concept-status", "title": "Named Authority List: Concept statuses", "publisher": "Publications Office of the European Union", "id": "euv-cs" }, "EUV-DS": { "href": "https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/dataset-status", "title": "Named Authority List: Dataset statuses", "publisher": "Publications Office of the European Union", "id": "euv-ds" }, "netCDF": { "href": "https://www.unidata.ucar.edu/software/netcdf/", "title": "Network Common Data Form (NetCDF)", "publisher": "UNIDATA", "id": "netcdf" }, "OBO": { "href": "http://www.obofoundry.org/", "title": "The OBO Foundry" }, "ODRS": { "authors": [ "Leigh Dodds" ], "href": "http://schema.theodi.org/odrs", "title": "Open Data Rights Statement Vocabulary", "date": "29 July 2013", "publisher": "ODI", "id": "odrs" }, "OpenSearch": { "authors": [ "DeWitt Clinton" ], "href": "https://github.com/dewitt/opensearch/blob/master/opensearch-1-1-draft-6.md", "title": "OpenSearch 1.1 Draft 6", "date": "17 April 2018", "publisher": "OpenSearch", "id": "opensearch" }, "PDO": { "href": "https://web.archive.org/web/20100727172837/http://vocab.deri.ie/pdo", "title": "Project Documents Ontology", "authors": [ "Pradeep Varma" ], "date": "09 July 2010" }, "PROF-GUIDE": { "href": "https://w3c.github.io/dxwg/profiles/", "title": "Profile Guidance", "date": "03 October 2018", "status": "W3C Editor's Draft" }, "PROF-IETF": { "authors": [ "L. Svensson", "R. Verborgh" ], "href": "https://profilenegotiation.github.io/I-D-Accept--Schema/I-D-accept-schema", "title": "Negotiating Profiles in HTTP", "date": "24 October 2017", "status": "IETF Internet Draft" }, "SCHEMA-ORG": { "href": "https://schema.org/", "title": "Schema.org", "id": "schema-org" }, "ShEx": { "href": "http://shex.io/shex-semantics/", "title": "Shape Expressions Language 2.1", "date": "17 November 2018", "status": "Draft Community Group Report", "publisher": "Shape Expressions W3C Community Group", "id": "shex" }, "UKGOVLD-REG": { "href": "https://github.com/UKGovLD/registry-core/wiki/Principles-and-concepts", "title": "Linked Data Registry - Principles and Concepts", "publisher": "UK Government Linked Data Working Group", "id": "ukgovld-reg" }, "VIVO-ISF": { "href": "https://github.com/vivo-isf/vivo-isf", "title": "VIVO-ISF Data Standard", "id": "vivo-isf" }, "ZaveriEtAl": { "title": "Quality assessment for Linked Data: A Survey", "authors": [ "Amrapali Zaveri" ], "etAl": true, "status": "Semantic Web, vol. 7, no. 1, pp. 63-93", "publisher": "IOS Press", "href": "https://doi.org/10.3233/SW-150175", "date": "2015", "id": "zaverietal" }, "PAV": { "href": "https://pav-ontology.github.io/pav/", "title": "PAV - Provenance, Authoring and Versioning. Version 2.3.1", "authors": [ "Paolo Ciccarese", "Stian Soiland-Reyes" ], "publisher": "Mind Informatics", "date": "16 March 2015", "id": "pav" }, "SPDX": { "href": "https://spdx.org/rdf/spdx-terms-v2.2/", "title": "SPDX 2.2", "publisher": "SPDX", "id": "spdx" } }, "publishDate": "2024-08-22", "publishISODate": "2024-08-22T00:00:00.000Z", "generatedSubtitle": "W3C Recommendation 22 August 2024" }</script> <link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2021/W3C-REC"></head> <body class="h-entry"><div class="head"> <p class="logos"><a class="logo" href="https://www.w3.org/"><img crossorigin="" alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72"> </a></p> <h1 id="title" class="title">Data Catalog Vocabulary (DCAT) - Version 3</h1> <p id="w3c-state"><a href="https://www.w3.org/standards/types#REC">W3C Recommendation</a> <time class="dt-published" datetime="2024-08-22">22 August 2024</time></p> <details open=""> <summary>More details about this document</summary> <dl> <dt>This version:</dt><dd> <a class="u-url" href="https://www.w3.org/TR/2024/REC-vocab-dcat-3-20240822/">https://www.w3.org/TR/2024/REC-vocab-dcat-3-20240822/</a> </dd> <dt>Latest published version:</dt><dd> <a href="https://www.w3.org/TR/vocab-dcat-3/">https://www.w3.org/TR/vocab-dcat-3/</a> </dd> <dt>Latest editor's draft:</dt><dd><a href="https://w3c.github.io/dxwg/dcat/">https://w3c.github.io/dxwg/dcat/</a></dd> <dt>History:</dt><dd> <a href="https://www.w3.org/standards/history/vocab-dcat-3/">https://www.w3.org/standards/history/vocab-dcat-3/</a> </dd><dd> <a href="https://github.com/w3c/dxwg/commits/">Commit history</a> </dd> <dt>Implementation report:</dt><dd> <a href="https://w3c.github.io/dxwg/dcat3-implementation-report/">https://w3c.github.io/dxwg/dcat3-implementation-report/</a> </dd> <dt>Previous Recommendation:</dt><dd><a href="https://www.w3.org/TR/2020/REC-vocab-dcat-2-20200204/">https://www.w3.org/TR/2020/REC-vocab-dcat-2-20200204/</a></dd> <dt>Editors:</dt><dd class="editor p-author h-card vcard" data-editor-id="72458"> <a class="u-url url p-name fn" href="https://imati.cnr.it/mypage.php?idk=PG-62">Riccardo Albertoni</a><a class="p-name orcid" href="https://orcid.org/0000-0001-5648-2713"><svg width="16" height="16" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 256 256"> <style> .st1 { fill: #fff; } </style> <path d="M256 128c0 70.7-57.3 128-128 128S0 198.7 0 128 57.3 0 128 0s128 57.3 128 128z" fill="#a6ce39"></path> <path class="st1" d="M86.3 186.2H70.9V79.1h15.4v107.1zM108.9 79.1h41.6c39.6 0 57 28.3 57 53.6 0 27.5-21.5 53.6-56.8 53.6h-41.8V79.1zm15.4 93.3h24.5c34.9 0 42.9-26.5 42.9-39.7C191.7 111.2 178 93 148 93h-23.7v79.4zM88.7 56.8c0 5.5-4.5 10.1-10.1 10.1s-10.1-4.6-10.1-10.1c0-5.6 4.5-10.1 10.1-10.1s10.1 4.6 10.1 10.1z"></path> </svg></a> (<a class="p-org org h-org" href="https://www.cnr.it/">Invited Expert / CNR - Consiglio Nazionale delle Ricerche, Italy</a>) </dd><dd class="editor p-author h-card vcard" data-editor-id="98704"> <span class="p-name fn">David Browning</span> (<span class="p-org org h-org">Invited Expert</span>) (Previously at Refinitiv.com) </dd><dd class="editor p-author h-card vcard" data-editor-id="1796"> <a class="u-url url p-name fn" href="https://orcid.org/0000-0002-3884-3420">Simon J D Cox</a><a class="p-name orcid" href="https://orcid.org/0000-0002-3884-3420"><svg width="16" height="16" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 256 256"> <style> .st1 { fill: #fff; } </style> <path d="M256 128c0 70.7-57.3 128-128 128S0 198.7 0 128 57.3 0 128 0s128 57.3 128 128z" fill="#a6ce39"></path> <path class="st1" d="M86.3 186.2H70.9V79.1h15.4v107.1zM108.9 79.1h41.6c39.6 0 57 28.3 57 53.6 0 27.5-21.5 53.6-56.8 53.6h-41.8V79.1zm15.4 93.3h24.5c34.9 0 42.9-26.5 42.9-39.7C191.7 111.2 178 93 148 93h-23.7v79.4zM88.7 56.8c0 5.5-4.5 10.1-10.1 10.1s-10.1-4.6-10.1-10.1c0-5.6 4.5-10.1 10.1-10.1s10.1 4.6 10.1 10.1z"></path> </svg></a> (<span class="p-org org h-org">Invited Expert</span>) (Previously at CSIRO) </dd><dd class="editor p-author h-card vcard" data-editor-id="61587"> <a class="u-url url p-name fn" href="https://www.scd.stfc.ac.uk/Pages/Alejandra-Gonzalez-Beltran.aspx">Alejandra Gonzalez Beltran</a><a class="p-name orcid" href="https://orcid.org/0000-0003-3499-8262"><svg width="16" height="16" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 256 256"> <style> .st1 { fill: #fff; } </style> <path d="M256 128c0 70.7-57.3 128-128 128S0 198.7 0 128 57.3 0 128 0s128 57.3 128 128z" fill="#a6ce39"></path> <path class="st1" d="M86.3 186.2H70.9V79.1h15.4v107.1zM108.9 79.1h41.6c39.6 0 57 28.3 57 53.6 0 27.5-21.5 53.6-56.8 53.6h-41.8V79.1zm15.4 93.3h24.5c34.9 0 42.9-26.5 42.9-39.7C191.7 111.2 178 93 148 93h-23.7v79.4zM88.7 56.8c0 5.5-4.5 10.1-10.1 10.1s-10.1-4.6-10.1-10.1c0-5.6 4.5-10.1 10.1-10.1s10.1 4.6 10.1 10.1z"></path> </svg></a> (<a class="p-org org h-org" href="https://stfc.ukri.org/">Invited Expert / Scientific Computing Department, Science and Technology Facilities Council, UK</a>) (Previously at the University of Oxford) </dd><dd class="editor p-author h-card vcard" data-editor-id="40317"> <span class="p-name fn">Andrea Perego</span><a class="p-name orcid" href="https://orcid.org/0000-0001-9300-2694"><svg width="16" height="16" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 256 256"> <style> .st1 { fill: #fff; } </style> <path d="M256 128c0 70.7-57.3 128-128 128S0 198.7 0 128 57.3 0 128 0s128 57.3 128 128z" fill="#a6ce39"></path> <path class="st1" d="M86.3 186.2H70.9V79.1h15.4v107.1zM108.9 79.1h41.6c39.6 0 57 28.3 57 53.6 0 27.5-21.5 53.6-56.8 53.6h-41.8V79.1zm15.4 93.3h24.5c34.9 0 42.9-26.5 42.9-39.7C191.7 111.2 178 93 148 93h-23.7v79.4zM88.7 56.8c0 5.5-4.5 10.1-10.1 10.1s-10.1-4.6-10.1-10.1c0-5.6 4.5-10.1 10.1-10.1s10.1 4.6 10.1 10.1z"></path> </svg></a> (<span class="p-org org h-org">Invited Expert</span>) </dd><dd class="editor p-author h-card vcard" data-editor-id="64374"> <span class="p-name fn">Peter Winstanley</span> (<span class="p-org org h-org">Invited Expert</span>) </dd> <dt> Former editors: </dt><dd class="editor p-author h-card vcard"> <span class="p-name fn">Fadi Maali</span> (<a class="p-org org h-org" href="https://en.wikipedia.org/wiki/Digital_Enterprise_Research_Institute">DERI</a>) </dd><dd class="editor p-author h-card vcard"> <span class="p-name fn">John Erickson</span> (<a class="p-org org h-org" href="http://tw.rpi.edu/">Tetherless World Constellation (RPI)</a>) </dd> <dt>Feedback:</dt><dd> <a href="https://github.com/w3c/dxwg/">GitHub w3c/dxwg</a> (<a href="https://github.com/w3c/dxwg/pulls/">pull requests</a>, <a href="https://github.com/w3c/dxwg/issues/new/choose">new issue</a>, <a href="https://github.com/w3c/dxwg/issues/">open issues</a>) </dd><dd><a href="mailto:public-dxwg-comments@w3.org?subject=%5Bvocab-dcat-3%5D%20YOUR%20TOPIC%20HERE">public-dxwg-comments@w3.org</a> with subject line <kbd>[vocab-dcat-3] <em>… message topic …</em></kbd> (<a rel="discussion" href="https://lists.w3.org/Archives/Public/public-dxwg-comments">archives</a>)</dd> <dt>Errata:</dt><dd><a href="https://w3c.github.io/dxwg/errata/">Errata exists</a>.</dd> <dt>Contributors</dt><dd> <a href="https://github.com/makxdekkers">Makx Dekkers</a> </dd> </dl> </details> <p> See also <a href="https://www.w3.org/Translations/?technology=vocab-dcat-3"> <strong>translations</strong></a>. </p> <p> This document is also available in these non-normative formats: <a rel="alternate" href="https://www.w3.org/ns/dcat.ttl">Turtle</a>, <a rel="alternate" href="https://www.w3.org/ns/dcat.rdf">RDF/XML</a>, and <a rel="alternate" href="https://www.w3.org/ns/dcat.jsonld">JSON-LD</a> </p> <p class="copyright"> <a href="https://www.w3.org/policies/#copyright">Copyright</a> © 2024 <a href="https://www.w3.org/">World Wide Web Consortium</a>. <abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup> <a href="https://www.w3.org/policies/#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/policies/#W3C_Trademarks">trademark</a> and <a rel="license" href="https://www.w3.org/copyright/software-license-2023/" title="W3C Software and Document Notice and License">permissive document license</a> rules apply. </p> <hr title="Separator for header"> </div> <div class="note" role="note" id="issue-container-generatedID"><div role="heading" class="note-title marker" id="h-note" aria-level="2"><span>Note</span></div><aside class=""> <p>DCAT 3 supersedes DCAT 2 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-2" title="Data Catalog Vocabulary (DCAT) - Version 2">VOCAB-DCAT-2</a></cite>], but it does not make it obsolete. DCAT 3 maintains the DCAT namespace as its terms preserve backward compatibility with DCAT 2. DCAT 3 relaxes constraints and adds new classes and properties, but these changes do not break the definition of previous terms.</p> <p>Any new implementation is expected to adopt DCAT 3, while the existing implementations do not need to upgrade to it, unless they want to use the new features. In particular, current DCAT 2 deployments that do not overlap with the DCAT 3 new features (e.g., versioning, dataset series and inverse properties) don't need to change anything to remain in conformance with DCAT 3. </p> </aside></div> <section class="notoc introductory" id="abstract"><h2>Abstract</h2> <p>DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. This document defines the schema and provides examples for its use.</p> <p>DCAT enables a publisher to describe datasets and data services in a catalog using a standard model and vocabulary that facilitates the consumption and aggregation of metadata from multiple catalogs. This can increase the discoverability of datasets and data services. It also makes it possible to have a decentralized approach to publishing data catalogs and makes federated search for datasets across catalogs in multiple sites possible using the same query mechanism and structure. Aggregated DCAT metadata can serve as a manifest file as part of the digital preservation process.</p> <p style="text-indent: 100px;">The namespace for DCAT terms is <code>http://www.w3.org/ns/dcat#</code></p> <p style="text-indent: 100px;">The suggested prefix for the DCAT namespace is <code>dcat</code></p> </section> <section class="notoc introductory" id="sotd"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. A list of current <abbr title="World Wide Web Consortium">W3C</abbr> publications and the latest revision of this technical report can be found in the <a href="https://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> technical reports index</a> at https://www.w3.org/TR/.</em></p> <p> This document defines a major revision of the DCAT 2 vocabulary ([<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-2" title="Data Catalog Vocabulary (DCAT) - Version 2">VOCAB-DCAT-2</a></cite>]) in response to use cases, requirements and community experience which could not be considered during the previous vocabulary development. This revision extends the DCAT standard in line with community practice while supporting diverse approaches to data description and dataset exchange. The main changes to the DCAT vocabulary have been: </p> <ul> <li>addition of <a href="#Property:distribution_checksum"><code>spdx:checksum</code></a> property and <a href="#Class:Checksum"><code>spdx:Checksum</code></a> class to provide digest for DCAT distributions</li> <li>addition of properties for supporting versioning, e.g., <a href="#Property:resource_version"><code>dcat:version</code></a>, <a href="#Property:resource_previous_version"><code>dcat:previousVersion</code></a>, <a href="#Property:resource_has_current_version"><code>dcat:hasCurrentVersion</code></a>, see <a href="#dataset-versions" class="sec-ref"><bdi class="secno">11. </bdi>Versioning</a></li> <li>addition of a <a href="#Class:Dataset_Series"><code>dcat:DatasetSeries</code></a> class and properties for representing Dataset Series, see <a href="#dataset-series" class="sec-ref"><bdi class="secno">12. </bdi>Dataset series</a></li> </ul> <p> This new version of the vocabulary updates and expands the original but preserves backward compatibility. A full list of the significant changes (with links to the relevant GitHub issues) is described in <a href="#changes" class="sec-ref"><bdi class="secno">D. </bdi>Change history</a>. </p> <p> <a href="https://github.com/w3c/dxwg/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Adcat+">Issues, requirements, and features</a> that have been considered and discussed by the Data eXchange Working Group but have not been addressed due to lack of maturity or consensus are collected in GitHub. Those believed to be a priority for a future release are in the milestone <a href="https://github.com/w3c/dxwg/milestone/31">DCAT Future Priority Work</a>. </p> <section><div class="header-wrapper"><h3 id="dcat_history">DCAT history</h3><a class="self-link" href="#dcat_history" aria-label="Permalink for this Section"></a></div> <p>The original DCAT vocabulary was developed and hosted at the <a href="https://web.archive.org/web/20141224031914/http://www.deri.ie/">Digital Enterprise Research Institute (DERI)</a>, then refined by the <a href="https://www.w3.org/egov/">eGov Interest Group</a>, and finally standardized in 2014 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>] by the <a href="https://www.w3.org/2011/gld/">Government Linked Data (GLD)</a> Working Group.</p> <p>A second recommended revision of DCAT, DCAT 2 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-2" title="Data Catalog Vocabulary (DCAT) - Version 2">VOCAB-DCAT-2</a></cite>], was developed by the <a href="https://www.w3.org/2017/dxwg/">Dataset Exchange Working Group</a> in response to a new set of Use Cases and Requirements [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ucr" title="Dataset Exchange Use Cases and Requirements">DCAT-UCR</a></cite>] gathered from peoples' experience with the DCAT vocabulary from the time of the original version, and new applications that were not considered in the first version. </p> <p>This version of DCAT, DCAT 3, was developed by the <a href="https://www.w3.org/2017/dxwg/">Dataset Exchange Working Group</a>, considering some of the more pressing use cases and requests among those left unaddressed in the previous standardization round. A summary of the changes from [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-2" title="Data Catalog Vocabulary (DCAT) - Version 2">VOCAB-DCAT-2</a></cite>] is provided in <a href="#changes" class="sec-ref"><bdi class="secno">D. </bdi>Change history</a>. </p> </section><section><div class="header-wrapper"><h3 id="external_terms">External terms</h3><a class="self-link" href="#external_terms" aria-label="Permalink for this Section"></a></div> <p>DCAT incorporates terms from pre-existing vocabularies where stable terms with appropriate meanings could be found, such as <a href="http://xmlns.com/foaf/0.1/homepage"><code>foaf:homepage</code></a> and <a href="http://purl.org/dc/terms/title"><code>dcterms:title</code></a>. Informal summary definitions of the externally-defined terms are included in the DCAT vocabulary for convenience, while authoritative definitions are available in the normative references. Changes to definitions in the references, if any, supersede the summaries given in this specification. Note that conformance to DCAT (<a href="#conformance" class="sec-ref"><bdi class="secno">4. </bdi>Conformance</a>) concerns usage of only the terms in the DCAT vocabulary specification, so possible changes to other external definitions will not affect the conformance of DCAT implementations.</p> </section><section><div class="header-wrapper"><h3 id="please_send_comments">Please send comments</h3><a class="self-link" href="#please_send_comments" aria-label="Permalink for this Section"></a></div> The Working Group invited publishers to describe their catalogs and datasets with the revised version of DCAT described in this document and to report their implementations following <a href="https://github.com/w3c/dxwg/wiki/DCAT-implementation-evidence">the instruction to reporting DCAT revised implementations</a>. This information and subsequent analysis is published in the <a href="https://w3c.github.io/dxwg/dcat3-implementation-report/">implementation report.</a> <p> This document was published by the <a href="https://www.w3.org/groups/wg/dx">Dataset Exchange Working Group</a> as a Recommendation using the <a href="https://www.w3.org/policies/process/20231103/#recs-and-notes">Recommendation track</a>. </p><p> <abbr title="World Wide Web Consortium">W3C</abbr> recommends the wide deployment of this specification as a standard for the Web. </p><p> A <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation is a specification that, after extensive consensus-building, is endorsed by <abbr title="World Wide Web Consortium">W3C</abbr> and its Members, and has commitments from Working Group members to <a href="https://www.w3.org/policies/patent-policy/#sec-Requirements">royalty-free licensing</a> for implementations. </p><p> This document was produced by a group operating under the <a href="https://www.w3.org/policies/patent-policy/"><abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>. <abbr title="World Wide Web Consortium">W3C</abbr> maintains a <a rel="disclosure" href="https://www.w3.org/groups/wg/dx/ipr">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="https://www.w3.org/policies/patent-policy/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="https://www.w3.org/policies/patent-policy/#sec-Disclosure">section 6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>. </p><p> This document is governed by the <a id="w3c_process_revision" href="https://www.w3.org/policies/process/20231103/">03 November 2023 <abbr title="World Wide Web Consortium">W3C</abbr> Process Document</a>. </p></section></section><nav id="toc"><h2 class="introductory" id="table-of-contents">Table of Contents</h2><ol class="toc"><li class="tocline"><a class="tocxref" href="#introduction"><bdi class="secno">1. </bdi>Introduction</a></li><li class="tocline"><a class="tocxref" href="#motivation"><bdi class="secno">2. </bdi>Motivation for change</a></li><li class="tocline"><a class="tocxref" href="#namespaces"><bdi class="secno">3. </bdi>Namespaces</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#normative-namespaces"><bdi class="secno">3.1 </bdi>Normative namespaces</a></li><li class="tocline"><a class="tocxref" href="#non-normative-namespaces"><bdi class="secno">3.2 </bdi>Non-normative namespaces</a></li></ol></li><li class="tocline"><a class="tocxref" href="#conformance"><bdi class="secno">4. </bdi>Conformance</a></li><li class="tocline"><a class="tocxref" href="#vocabulary-overview"><bdi class="secno">5. </bdi>Vocabulary overview</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#dcat-scope"><bdi class="secno">5.1 </bdi>DCAT scope</a></li><li class="tocline"><a class="tocxref" href="#dcat-rdf"><bdi class="secno">5.2 </bdi>RDF considerations</a></li><li class="tocline"><a class="tocxref" href="#basic-example"><bdi class="secno">5.3 </bdi>Basic example</a></li><li class="tocline"><a class="tocxref" href="#classifying-datasets"><bdi class="secno">5.4 </bdi>Classifying datasets thematically</a></li><li class="tocline"><a class="tocxref" href="#classifying-dataset-types"><bdi class="secno">5.5 </bdi>Classifying dataset types</a></li><li class="tocline"><a class="tocxref" href="#describing-catalog-records-metadata"><bdi class="secno">5.6 </bdi>Describing catalog records metadata</a></li><li class="tocline"><a class="tocxref" href="#example-landing-page"><bdi class="secno">5.7 </bdi>Dataset available only behind some Web page</a></li><li class="tocline"><a class="tocxref" href="#a-dataset-available-as-download-and-behind-some-web-page"><bdi class="secno">5.8 </bdi>A dataset available as a download and behind some Web page</a></li><li class="tocline"><a class="tocxref" href="#a-dataset-available-from-a-service"><bdi class="secno">5.9 </bdi>A dataset available through a service</a></li></ol></li><li class="tocline"><a class="tocxref" href="#vocabulary-specification"><bdi class="secno">6. </bdi>Vocabulary specification</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#RDF-representation"><bdi class="secno">6.1 </bdi>RDF representation</a></li><li class="tocline"><a class="tocxref" href="#external-vocab"><bdi class="secno">6.2 </bdi>Elements from other vocabularies</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#complements"><bdi class="secno">6.2.1 </bdi>Complementary vocabularies</a></li><li class="tocline"><a class="tocxref" href="#dependencies"><bdi class="secno">6.2.2 </bdi>Element definitions</a></li></ol></li><li class="tocline"><a class="tocxref" href="#Class:Catalog"><bdi class="secno">6.3 </bdi>Class: Catalog</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#Property:catalog_homepage"><bdi class="secno">6.3.1 </bdi>Property: homepage</a></li><li class="tocline"><a class="tocxref" href="#Property:catalog_themes"><bdi class="secno">6.3.2 </bdi>Property: themes</a></li><li class="tocline"><a class="tocxref" href="#Property:catalog_resource"><bdi class="secno">6.3.3 </bdi>Property: resource</a></li><li class="tocline"><a class="tocxref" href="#Property:catalog_dataset"><bdi class="secno">6.3.4 </bdi>Property: dataset</a></li><li class="tocline"><a class="tocxref" href="#Property:catalog_service"><bdi class="secno">6.3.5 </bdi>Property: service</a></li><li class="tocline"><a class="tocxref" href="#Property:catalog_catalog"><bdi class="secno">6.3.6 </bdi>Property: catalog</a></li><li class="tocline"><a class="tocxref" href="#Property:catalog_catalog_record"><bdi class="secno">6.3.7 </bdi>Property: catalog record</a></li></ol></li><li class="tocline"><a class="tocxref" href="#Class:Resource"><bdi class="secno">6.4 </bdi>Class: Cataloged Resource</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#Property:resource_access_rights"><bdi class="secno">6.4.1 </bdi>Property: access rights</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_conforms_to"><bdi class="secno">6.4.2 </bdi>Property: conforms to</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_contact_point"><bdi class="secno">6.4.3 </bdi>Property: contact point</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_creator"><bdi class="secno">6.4.4 </bdi>Property: creator</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_description"><bdi class="secno">6.4.5 </bdi>Property: description</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_title"><bdi class="secno">6.4.6 </bdi>Property: title</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_release_date"><bdi class="secno">6.4.7 </bdi>Property: release date</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_update_date"><bdi class="secno">6.4.8 </bdi>Property: update/modification date</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_language"><bdi class="secno">6.4.9 </bdi>Property: language</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_publisher"><bdi class="secno">6.4.10 </bdi>Property: publisher</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_identifier"><bdi class="secno">6.4.11 </bdi>Property: identifier</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_theme"><bdi class="secno">6.4.12 </bdi>Property: theme/category</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_type"><bdi class="secno">6.4.13 </bdi>Property: type/genre</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_relation"><bdi class="secno">6.4.14 </bdi>Property: relation</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_qualified_relation"><bdi class="secno">6.4.15 </bdi>Property: qualified relation</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_keyword"><bdi class="secno">6.4.16 </bdi>Property: keyword/tag</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_landing_page"><bdi class="secno">6.4.17 </bdi>Property: landing page</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_qualified_attribution"><bdi class="secno">6.4.18 </bdi>Property: qualified attribution</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_license"><bdi class="secno">6.4.19 </bdi>Property: license</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_rights"><bdi class="secno">6.4.20 </bdi>Property: rights</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_has_part"><bdi class="secno">6.4.21 </bdi>Property: has part</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_has_policy"><bdi class="secno">6.4.22 </bdi>Property: has policy</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_is_referenced_by"><bdi class="secno">6.4.23 </bdi>Property: is referenced by</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_previous_version"><bdi class="secno">6.4.24 </bdi>Property: previous version</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_has_version"><bdi class="secno">6.4.25 </bdi>Property: has version</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_has_current_version"><bdi class="secno">6.4.26 </bdi>Property: current version</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_replaces"><bdi class="secno">6.4.27 </bdi>Property: replaces</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_version"><bdi class="secno">6.4.28 </bdi>Property: version</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_version_notes"><bdi class="secno">6.4.29 </bdi>Property: version notes</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_status"><bdi class="secno">6.4.30 </bdi>Property: status</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_first"><bdi class="secno">6.4.31 </bdi>Property: first</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_last"><bdi class="secno">6.4.32 </bdi>Property: last</a></li><li class="tocline"><a class="tocxref" href="#Property:resource_previous"><bdi class="secno">6.4.33 </bdi>Property: previous</a></li></ol></li><li class="tocline"><a class="tocxref" href="#Class:Catalog_Record"><bdi class="secno">6.5 </bdi>Class: Catalog Record</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#Property:record_title"><bdi class="secno">6.5.1 </bdi>Property: title</a></li><li class="tocline"><a class="tocxref" href="#Property:record_description"><bdi class="secno">6.5.2 </bdi>Property: description</a></li><li class="tocline"><a class="tocxref" href="#Property:record_listing_date"><bdi class="secno">6.5.3 </bdi>Property: listing date</a></li><li class="tocline"><a class="tocxref" href="#Property:record_update_date"><bdi class="secno">6.5.4 </bdi>Property: update/modification date</a></li><li class="tocline"><a class="tocxref" href="#Property:record_primary_topic"><bdi class="secno">6.5.5 </bdi>Property: primary topic</a></li><li class="tocline"><a class="tocxref" href="#Property:record_conforms_to"><bdi class="secno">6.5.6 </bdi>Property: conforms to</a></li></ol></li><li class="tocline"><a class="tocxref" href="#Class:Dataset"><bdi class="secno">6.6 </bdi>Class: Dataset</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#Property:dataset_distribution"><bdi class="secno">6.6.1 </bdi>Property: distribution</a></li><li class="tocline"><a class="tocxref" href="#Property:dataset_frequency"><bdi class="secno">6.6.2 </bdi>Property: frequency</a></li><li class="tocline"><a class="tocxref" href="#Property:dataset_in_series"><bdi class="secno">6.6.3 </bdi>Property: in series</a></li><li class="tocline"><a class="tocxref" href="#Property:dataset_spatial"><bdi class="secno">6.6.4 </bdi>Property: spatial/geographical coverage</a></li><li class="tocline"><a class="tocxref" href="#Property:dataset_spatial_resolution"><bdi class="secno">6.6.5 </bdi>Property: spatial resolution</a></li><li class="tocline"><a class="tocxref" href="#Property:dataset_temporal"><bdi class="secno">6.6.6 </bdi>Property: temporal coverage</a></li><li class="tocline"><a class="tocxref" href="#Property:dataset_temporal_resolution"><bdi class="secno">6.6.7 </bdi>Property: temporal resolution</a></li><li class="tocline"><a class="tocxref" href="#Property:dataset_was_generated_by"><bdi class="secno">6.6.8 </bdi>Property: was generated by</a></li></ol></li><li class="tocline"><a class="tocxref" href="#Class:Dataset_Series"><bdi class="secno">6.7 </bdi>Class: Dataset Series</a></li><li class="tocline"><a class="tocxref" href="#Class:Distribution"><bdi class="secno">6.8 </bdi>Class: Distribution</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#Property:distribution_title"><bdi class="secno">6.8.1 </bdi>Property: title</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_description"><bdi class="secno">6.8.2 </bdi>Property: description</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_release_date"><bdi class="secno">6.8.3 </bdi>Property: release date</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_update_date"><bdi class="secno">6.8.4 </bdi>Property: update/modification date</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_license"><bdi class="secno">6.8.5 </bdi>Property: license</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_access_rights"><bdi class="secno">6.8.6 </bdi>Property: access rights</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_rights"><bdi class="secno">6.8.7 </bdi>Property: rights</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_has_policy"><bdi class="secno">6.8.8 </bdi>Property: has policy</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_access_url"><bdi class="secno">6.8.9 </bdi>Property: access URL</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_access_service"><bdi class="secno">6.8.10 </bdi>Property: access service</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_download_url"><bdi class="secno">6.8.11 </bdi>Property: download URL</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_size"><bdi class="secno">6.8.12 </bdi>Property: byte size</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_spatial_resolution"><bdi class="secno">6.8.13 </bdi>Property: spatial resolution</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_temporal_resolution"><bdi class="secno">6.8.14 </bdi>Property: temporal resolution</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_conforms_to"><bdi class="secno">6.8.15 </bdi>Property: conforms to</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_media_type"><bdi class="secno">6.8.16 </bdi>Property: media type</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_format"><bdi class="secno">6.8.17 </bdi>Property: format</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_compression_format"><bdi class="secno">6.8.18 </bdi>Property: compression format</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_packaging_format"><bdi class="secno">6.8.19 </bdi>Property: packaging format</a></li><li class="tocline"><a class="tocxref" href="#Property:distribution_checksum"><bdi class="secno">6.8.20 </bdi>Property: checksum</a></li></ol></li><li class="tocline"><a class="tocxref" href="#Class:Data_Service"><bdi class="secno">6.9 </bdi>Class: Data Service</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#Property:data_service_endpoint_url"><bdi class="secno">6.9.1 </bdi>Property: endpoint URL</a></li><li class="tocline"><a class="tocxref" href="#Property:data_service_endpoint_description"><bdi class="secno">6.9.2 </bdi>Property: endpoint description</a></li><li class="tocline"><a class="tocxref" href="#Property:data_service_serves_dataset"><bdi class="secno">6.9.3 </bdi>Property: serves dataset</a></li></ol></li><li class="tocline"><a class="tocxref" href="#Class:Concept_Scheme"><bdi class="secno">6.10 </bdi>Class: Concept Scheme</a></li><li class="tocline"><a class="tocxref" href="#Class:Concept"><bdi class="secno">6.11 </bdi>Class: Concept</a></li><li class="tocline"><a class="tocxref" href="#Class:Organization_Person"><bdi class="secno">6.12 </bdi>Class: Organization/Person</a></li><li class="tocline"><a class="tocxref" href="#Class:Relationship"><bdi class="secno">6.13 </bdi>Class: Relationship</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#Property:relationship_relation"><bdi class="secno">6.13.1 </bdi>Property: relation</a></li><li class="tocline"><a class="tocxref" href="#Property:relationship_hadRole"><bdi class="secno">6.13.2 </bdi>Property: had role</a></li></ol></li><li class="tocline"><a class="tocxref" href="#Class:Role"><bdi class="secno">6.14 </bdi>Class: Role</a></li><li class="tocline"><a class="tocxref" href="#Class:Period_of_Time"><bdi class="secno">6.15 </bdi>Class: Period of Time</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#Property:period_start_date"><bdi class="secno">6.15.1 </bdi>Property: start date</a></li><li class="tocline"><a class="tocxref" href="#Property:period_end_date"><bdi class="secno">6.15.2 </bdi>Property: end date</a></li><li class="tocline"><a class="tocxref" href="#Property:period_has_beginning"><bdi class="secno">6.15.3 </bdi>Property: beginning</a></li><li class="tocline"><a class="tocxref" href="#Property:period_has_end"><bdi class="secno">6.15.4 </bdi>Property: end</a></li></ol></li><li class="tocline"><a class="tocxref" href="#Class:Location"><bdi class="secno">6.16 </bdi>Class: Location</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#Property:location_geometry"><bdi class="secno">6.16.1 </bdi>Property: geometry</a></li><li class="tocline"><a class="tocxref" href="#Property:location_bbox"><bdi class="secno">6.16.2 </bdi>Property: bounding box</a></li><li class="tocline"><a class="tocxref" href="#Property:location_centroid"><bdi class="secno">6.16.3 </bdi>Property: centroid</a></li></ol></li><li class="tocline"><a class="tocxref" href="#Class:Checksum"><bdi class="secno">6.17 </bdi>Class: Checksum</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#Property:checksum_algorithm"><bdi class="secno">6.17.1 </bdi>Property: algorithm</a></li><li class="tocline"><a class="tocxref" href="#Property:checksum_checksum_value"><bdi class="secno">6.17.2 </bdi>Property: checksum value</a></li></ol></li></ol></li><li class="tocline"><a class="tocxref" href="#inverse-properties"><bdi class="secno">7. </bdi>Use of inverse properties</a></li><li class="tocline"><a class="tocxref" href="#dereferenceable-identifiers"><bdi class="secno">8. </bdi>Dereferenceable identifiers</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#identifiers-type"><bdi class="secno">8.1 </bdi>Indicating common identifier types</a></li></ol></li><li class="tocline"><a class="tocxref" href="#license-rights"><bdi class="secno">9. </bdi>License and rights statements</a></li><li class="tocline"><a class="tocxref" href="#time-and-space"><bdi class="secno">10. </bdi>Time and space</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#temporal-properties"><bdi class="secno">10.1 </bdi>Temporal properties</a></li><li class="tocline"><a class="tocxref" href="#spatial-properties"><bdi class="secno">10.2 </bdi>Spatial properties</a></li></ol></li><li class="tocline"><a class="tocxref" href="#dataset-versions"><bdi class="secno">11. </bdi>Versioning</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#version-relationships"><bdi class="secno">11.1 </bdi>Relationships between versions</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#version-history"><bdi class="secno">11.1.1 </bdi>Version chains and hierarchies</a></li><li class="tocline"><a class="tocxref" href="#version-replace"><bdi class="secno">11.1.2 </bdi>Versions replaced by other ones</a></li></ol></li><li class="tocline"><a class="tocxref" href="#version-info"><bdi class="secno">11.2 </bdi>Version information</a></li><li class="tocline"><a class="tocxref" href="#life-cycle"><bdi class="secno">11.3 </bdi>Resource life-cycle</a></li><li class="tocline"><a class="tocxref" href="#versioning-complementary-approaches"><bdi class="secno">11.4 </bdi>Complementary approaches to versioning</a></li></ol></li><li class="tocline"><a class="tocxref" href="#dataset-series"><bdi class="secno">12. </bdi>Dataset series</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#dataset-series-specification"><bdi class="secno">12.1 </bdi>How to specify dataset series</a></li><li class="tocline"><a class="tocxref" href="#dataset-series-properties"><bdi class="secno">12.2 </bdi>Dataset series metadata</a></li><li class="tocline"><a class="tocxref" href="#dataset-series-before-dcat3"><bdi class="secno">12.3 </bdi>Dataset series in existing DCAT implementations</a></li></ol></li><li class="tocline"><a class="tocxref" href="#data-citation"><bdi class="secno">13. </bdi>Data citation</a></li><li class="tocline"><a class="tocxref" href="#quality-information"><bdi class="secno">14. </bdi>Quality information</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#quality-example1"><bdi class="secno">14.1 </bdi>Providing quality information</a></li><li class="tocline"><a class="tocxref" href="#quality-conformance"><bdi class="secno">14.2 </bdi>Documenting conformance to standards</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#quality-conformance-statement"><bdi class="secno">14.2.1 </bdi>Conformance to a standard</a></li><li class="tocline"><a class="tocxref" href="#quality-conformance-degree"><bdi class="secno">14.2.2 </bdi>Degree of conformance</a></li><li class="tocline"><a class="tocxref" href="#quality-conformance-test-results"><bdi class="secno">14.2.3 </bdi>Conformance test results</a></li></ol></li></ol></li><li class="tocline"><a class="tocxref" href="#qualified-forms"><bdi class="secno">15. </bdi>Qualified relations</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#qualified-attribution"><bdi class="secno">15.1 </bdi>Relationships between datasets and agents</a></li><li class="tocline"><a class="tocxref" href="#qualified-relationship"><bdi class="secno">15.2 </bdi>Relationships between datasets and other resources</a></li></ol></li><li class="tocline"><a class="tocxref" href="#profiles"><bdi class="secno">16. </bdi>DCAT Profiles</a></li><li class="tocline"><a class="tocxref" href="#security_and_privacy"><bdi class="secno">17. </bdi>Security and Privacy Considerations</a></li><li class="tocline"><a class="tocxref" href="#accessibility"><bdi class="secno">18. </bdi>Accessibility Considerations</a></li><li class="tocline"><a class="tocxref" href="#acknowledgments"><bdi class="secno">A. </bdi>Acknowledgments</a></li><li class="tocline"><a class="tocxref" href="#dcat-sdo"><bdi class="secno">B. </bdi>Alignment with Schema.org</a></li><li class="tocline"><a class="tocxref" href="#collection-of-examples"><bdi class="secno">C. </bdi>Examples</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#examples-bag-of-files"><bdi class="secno">C.1 </bdi>Loosely structured catalog</a></li><li class="tocline"><a class="tocxref" href="#examples-dataset-provenance"><bdi class="secno">C.2 </bdi>Dataset provenance</a></li><li class="tocline"><a class="tocxref" href="#examples-dataset-publication"><bdi class="secno">C.3 </bdi>Link datasets and publications</a></li><li class="tocline"><a class="tocxref" href="#examples-data-service"><bdi class="secno">C.4 </bdi>Data services</a></li><li class="tocline"><a class="tocxref" href="#examples-compressed-and-packaged-distributions"><bdi class="secno">C.5 </bdi>Compressed and packaged distributions</a></li></ol></li><li class="tocline"><a class="tocxref" href="#changes"><bdi class="secno">D. </bdi>Change history</a></li><li class="tocline"><a class="tocxref" href="#changes-since-20240118"><bdi class="secno">E. </bdi>Changes since the Candidate Recommendation Snapshot 18 January 2024</a></li><li class="tocline"><a class="tocxref" href="#changes-since-20220510"><bdi class="secno">F. </bdi>Changes since the fourth public working draft of 10 May 2022</a></li><li class="tocline"><a class="tocxref" href="#changes-since-20220111"><bdi class="secno">G. </bdi>Changes since the third public working draft of 11 January 2022</a></li><li class="tocline"><a class="tocxref" href="#changes-since-20210504"><bdi class="secno">H. </bdi>Changes since the second public working draft of 4 May 2021</a></li><li class="tocline"><a class="tocxref" href="#changes-since-20201217"><bdi class="secno">I. </bdi>Changes since the first public working draft of 17 December 2020</a></li><li class="tocline"><a class="tocxref" href="#changes-since-20200204"><bdi class="secno">J. </bdi>Changes since the <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation of 4 February 2020</a></li><li class="tocline"><a class="tocxref" href="#references"><bdi class="secno">K. </bdi>References</a><ol class="toc"><li class="tocline"><a class="tocxref" href="#normative-references"><bdi class="secno">K.1 </bdi>Normative references</a></li><li class="tocline"><a class="tocxref" href="#informative-references"><bdi class="secno">K.2 </bdi>Informative references</a></li></ol></li></ol></nav> <section id="introduction" class="informative"><div class="header-wrapper"><h2 id="x1-introduction"><bdi class="secno">1. </bdi>Introduction</h2><a class="self-link" href="#introduction" aria-label="Permalink for Section 1."></a></div><p><em>This section is non-normative.</em></p> <p>Sharing data resources among different organizations, researchers, governments and citizens requires the provision of metadata. This is irrespective of the data being open or not. DCAT is a vocabulary for publishing data catalogs on the Web, which was originally developed in the context of government data catalogs such as <a href="https://www.data.gov/">data.gov</a> and <a href="https://data.gov.uk">data.gov.uk</a>, but it is also applicable and has been used in other contexts. </p><p> </p><p> DCAT 3 has extended the previous version to support further use cases and requirements [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ucr" title="Dataset Exchange Use Cases and Requirements">DCAT-UCR</a></cite>]. These include the possibility of cataloging other resources in addition to datasets, such as dataset series. The revision also supports describing versioning of resources. Guidance on how to use inverse properties is provided. </p> <p> DCAT provides RDF classes and properties to allow datasets and data services to be described and included in a catalog. The use of a standard model and vocabulary facilitates the consumption and aggregation of metadata from multiple catalogs, which can:</p> <ol> <li> increase the discoverability of datasets and data services </li> <li> allow federated search for datasets across catalogs in multiple sites </li> </ol> <p> Data described in a catalog can come in many formats, ranging from spreadsheets, through XML and RDF to various specialized formats. DCAT does not make any assumptions about these serialization formats of the datasets but it does distinguish between the abstract dataset and its different manifestations or distributions. </p> <p> Data is often provided through a service which supports selection of an extract, sub-set, or combination of existing data, or of new data generated by some data processing function. DCAT allows the description of a data access service to be included in a catalog. </p> <p> Complementary vocabularies can be used together with DCAT to provide more detailed format-specific information. For example, properties from the VoID vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-void" title="Describing Linked Datasets with the VoID Vocabulary">VOID</a></cite>] can be used within DCAT to express various statistics about a dataset if that dataset is in RDF format. </p> <p> This document does not prescribe any particular method of deploying data catalogs expressed in DCAT. DCAT information can be presented in many forms including RDF accessible via SPARQL endpoints, embedded in HTML pages as [<cite><a class="bibref" data-link-type="biblio" href="#bib-html-rdfa" title="HTML+RDFa 1.1 - Second Edition">HTML-RDFa</a></cite>], or serialized as RDF/XML [<cite><a class="bibref" data-link-type="biblio" href="#bib-rdf-syntax-grammar" title="RDF 1.1 XML Syntax">RDF-SYNTAX-GRAMMAR</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-n3" title="Notation3 (N3): A readable RDF syntax">N3</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-turtle" title="RDF 1.1 Turtle">Turtle</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-json-ld" title="JSON-LD 1.0">JSON-LD</a></cite>] or other formats. Within this document the examples use [<cite><a class="bibref" data-link-type="biblio" href="#bib-turtle" title="RDF 1.1 Turtle">Turtle</a></cite>] because of its readability. </p> </section> <section id="motivation" class="informative"><div class="header-wrapper"><h2 id="x2-motivation-for-change"><bdi class="secno">2. </bdi>Motivation for change</h2><a class="self-link" href="#motivation" aria-label="Permalink for Section 2."></a></div><p><em>This section is non-normative.</em></p> <p>The original Recommendation [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>] published in January 2014 provided the basic framework for describing datasets. It made an important distinction between a <i>dataset</i> as an abstract idea and a <i>distribution</i> as a manifestation of the dataset. Although DCAT has been widely adopted, it has become clear that the original specification lacked a number of essential features that were added either through the mechanism of a profile, such as the European Commission's DCAT-AP [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap" title="DCAT Application Profile for data portals in Europe. Version 2.0.1">DCAT-AP</a></cite>], or the development of larger vocabularies that to a greater or lesser extent built upon the base standard, such as the Healthcare and Life Sciences Community Profile [<cite><a class="bibref" data-link-type="biblio" href="#bib-hcls-dataset" title="Dataset Descriptions: HCLS Community Profile">HCLS-Dataset</a></cite>], the Data Tag Suite [<cite><a class="bibref" data-link-type="biblio" href="#bib-dats" title="Data Tag Suite">DATS</a></cite>] and more. DCAT 2 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-2" title="Data Catalog Vocabulary (DCAT) - Version 2">VOCAB-DCAT-2</a></cite>] was developed to address the specific shortcomings that have come to light through the experiences of different communities, the aim being to improve interoperability between the outputs of these larger vocabularies. For example, DCAT 2 provided classes, properties and guidance to address <a href="#dereferenceable-identifiers">identifiers</a>, <a href="#quality-information">dataset quality information</a>, and <a href="#data-citation">data citation</a> issues.</p> <p>This revision, DCAT 3, updates the specification throughout. Significant changes from the 2014 Recommendation and DCAT 2 are marked within the text using "Note" sections, as well as being described in <a href="#changes" class="sec-ref"><bdi class="secno">D. </bdi>Change history</a>.</p> </section> <section id="namespaces"><div class="header-wrapper"><h2 id="x3-namespaces"><bdi class="secno">3. </bdi>Namespaces</h2><a class="self-link" href="#namespaces" aria-label="Permalink for Section 3."></a></div> <p>The namespace for DCAT is <code>http://www.w3.org/ns/dcat#</code>. DCAT also makes extensive use of terms from other vocabularies, in particular Dublin Core [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>]. DCAT defines a minimal set of classes and properties of its own.</p> <section id="normative-namespaces"><div class="header-wrapper"><h3 id="x3-1-normative-namespaces"><bdi class="secno">3.1 </bdi>Normative namespaces</h3><a class="self-link" href="#normative-namespaces" aria-label="Permalink for Section 3.1"></a></div> <p>Namespaces and prefixes used in normative parts of this recommendation are shown in the following table.</p> <table id="table-namespaces" class="simple"> <thead><tr><th>Prefix</th><th>Namespace <abbr title="Internationalized Resource Identifier">IRI</abbr></th><th>Source</th></tr></thead> <tbody> <tr><td><code>adms</code></td><td><code>http://www.w3.org/ns/adms#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-adms" title="Asset Description Metadata Schema (ADMS)">VOCAB-ADMS</a></cite>]</td></tr> <tr><td><code>dc</code></td><td><code>http://purl.org/dc/elements/1.1/</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>]</td></tr> <tr><td><code>dcat</code></td><td><code>http://www.w3.org/ns/dcat#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT</a></cite>]</td></tr> <tr><td><code>dcterms</code></td><td><code>http://purl.org/dc/terms/</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>]</td></tr> <tr><td><code>dctype</code></td><td><code>http://purl.org/dc/dcmitype/</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>]</td></tr> <tr><td><code>foaf</code></td><td><code>http://xmlns.com/foaf/0.1/</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-foaf" title="FOAF Vocabulary Specification 0.99 (Paddington Edition)">FOAF</a></cite>]</td></tr> <tr><td><code>locn</code></td><td><code>http://www.w3.org/ns/locn#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-locn" title="ISA Programme Location Core Vocabulary">LOCN</a></cite>]</td></tr> <tr><td><code>odrl</code></td><td><code>http://www.w3.org/ns/odrl/2/</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-odrl-vocab" title="ODRL Vocabulary & Expression 2.2">ODRL-VOCAB</a></cite>]</td></tr> <tr><td><code>owl</code></td><td><code>http://www.w3.org/2002/07/owl#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-owl2-syntax" title="OWL 2 Web Ontology Language Structural Specification and Functional-Style Syntax (Second Edition)">OWL2-SYNTAX</a></cite>]</td></tr> <tr><td><code>prov</code></td><td><code>http://www.w3.org/ns/prov#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>]</td></tr> <tr><td><code>rdf</code></td><td><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-rdf-syntax-grammar" title="RDF 1.1 XML Syntax">RDF-SYNTAX-GRAMMAR</a></cite>]</td></tr> <tr><td><code>rdfs</code></td><td><code>http://www.w3.org/2000/01/rdf-schema#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-rdf-schema" title="RDF Schema 1.1">RDF-SCHEMA</a></cite>]</td></tr> <tr><td><code>skos</code></td><td><code>http://www.w3.org/2004/02/skos/core#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-skos-reference" title="SKOS Simple Knowledge Organization System Reference">SKOS-REFERENCE</a></cite>]</td></tr> <tr><td><code>spdx</code></td><td><code>http://spdx.org/rdf/terms#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-spdx" title="SPDX 2.2">SPDX</a></cite>]</td></tr> <tr><td><code>time</code></td><td><code>http://www.w3.org/2006/time#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-owl-time" title="Time Ontology in OWL">OWL-TIME</a></cite>]</td></tr> <tr><td><code>vcard</code></td><td><code>http://www.w3.org/2006/vcard/ns#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-vcard-rdf" title="vCard Ontology - for describing People and Organizations">VCARD-RDF</a></cite>]</td></tr> <tr><td><code>xsd</code></td><td><code>http://www.w3.org/2001/XMLSchema#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-xmlschema11-2" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">XMLSCHEMA11-2</a></cite>]</td></tr> </tbody> </table> </section> <section class="informative" id="non-normative-namespaces"><div class="header-wrapper"><h3 id="x3-2-non-normative-namespaces"><bdi class="secno">3.2 </bdi>Non-normative namespaces</h3><a class="self-link" href="#non-normative-namespaces" aria-label="Permalink for Section 3.2"></a></div><p><em>This section is non-normative.</em></p> <p>Namespaces and prefixes used in examples and guidelines in the document and not from normative parts of the recommendation are shown in the following table.</p> <table id="table-namespaces-examples" class="simple"> <thead><tr><th>Prefix</th><th>Namespace <abbr title="Internationalized Resource Identifier">IRI</abbr></th><th>Source</th></tr></thead> <tbody> <tr><td><code>dqv</code></td><td><code>http://www.w3.org/ns/dqv#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>]</td></tr> <tr><td><code>earl</code></td><td><code>http://www.w3.org/ns/earl#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-earl10-schema" title="Evaluation and Report Language (EARL) 1.0 Schema">EARL10-Schema</a></cite>]</td></tr> <tr><td><code>geosparql</code></td><td><code>http://www.opengis.net/ont/geosparql#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-geosparql" title="OGC GeoSPARQL - A Geographic Query Language for RDF Data">GeoSPARQL</a></cite>]</td></tr> <tr><td><code>oa</code></td><td><code>http://www.w3.org/ns/oa#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-annotation-vocab" title="Web Annotation Vocabulary">ANNOTATION-VOCAB</a></cite>]</td></tr> <tr><td><code>pav</code></td><td><code>http://purl.org/pav/</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-pav" title="PAV - Provenance, Authoring and Versioning. Version 2.3.1">PAV</a></cite>]</td></tr> <tr><td><code>sdmx-attribute</code></td><td><code>http://purl.org/linked-data/sdmx/2009/attribute#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-data-cube" title="The RDF Data Cube Vocabulary">VOCAB-DATA-CUBE</a></cite>]</td></tr> <tr><td><code>sdo</code></td><td><code>https://schema.org/</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-schema-org" title="Schema.org">SCHEMA-ORG</a></cite>]</td></tr> <tr><td><code>xhv</code></td><td><code>http://www.w3.org/1999/xhtml/vocab#</code></td><td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-xhtml-vocab" title="XHTML Vocabulary">XHTML-VOCAB</a></cite>]</td></tr> </tbody> </table> </section> </section> <section id="conformance"><div class="header-wrapper"><h2 id="x4-conformance"><bdi class="secno">4. </bdi>Conformance</h2><a class="self-link" href="#conformance" aria-label="Permalink for Section 4."></a></div><p>As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.</p><p> The key words <em class="rfc2119">MAY</em>, <em class="rfc2119">MUST</em>, <em class="rfc2119">MUST NOT</em>, and <em class="rfc2119">SHOULD</em> in this document are to be interpreted as described in <a href="https://datatracker.ietf.org/doc/html/bcp14">BCP 14</a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-rfc2119" title="Key words for use in RFCs to Indicate Requirement Levels">RFC2119</a></cite>] [<cite><a class="bibref" data-link-type="biblio" href="#bib-rfc8174" title="Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words">RFC8174</a></cite>] when, and only when, they appear in all capitals, as shown here. </p> <p>A data catalog conforms to DCAT if:</p> <ul> <li> Access to data is organized into datasets, distributions, data services and dataset series. </li> <li> An RDF description of the catalog itself, the corresponding cataloged resources, and distributions is available (but the choice of RDF syntax, access protocol, and access policy are not mandated by this specification).</li> <li> The contents of all metadata fields that are held in the catalog and that contain data about the catalog itself, the corresponding cataloged resources, and distributions are included in this RDF description and are expressed using the appropriate classes and properties from DCAT, except where no such class or property exists.</li> <li> All classes and properties defined in DCAT are used in a way consistent with the semantics declared in this specification.</li> </ul> DCAT-compliant catalogs <em class="rfc2119">MAY</em> include additional non-DCAT metadata fields and additional RDF data in the catalog's RDF description. <p> A <strong>DCAT profile</strong> is a specification for a data catalog that adds additional constraints to DCAT. A data catalog that conforms to the profile also conforms to DCAT. Additional constraints in a profile <em class="rfc2119">MAY</em> include: </p> <ul> <li> Cardinality constraints, including a minimum set of required metadata fields </li> <li> Sub-classes and sub-properties of the standard DCAT classes and properties</li> <li> Classes and properties for additional metadata fields not covered in DCAT vocabulary specification</li> <li> Controlled vocabularies or <abbr title="Internationalized Resource Identifier">IRI</abbr> sets as acceptable values for properties</li> <li> Requirements for specific access mechanisms (RDF syntaxes, protocols) to the catalog's RDF description</li> </ul> <div class="note" role="note" id="issue-container-generatedID-0"><div role="heading" class="note-title marker" id="h-note-0" aria-level="3"><span>Note</span></div><aside class=""> <p>The notion of <em>profile</em> used in this document denotes metadata specifications that the Dublin Core community would call <em>application profiles</em> [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcap" title="Guidelines for Dublin Core Application Profiles">DCAP</a></cite>].</p> </aside></div> </section> <section id="vocabulary-overview" class="informative"><div class="header-wrapper"><h2 id="x5-vocabulary-overview"><bdi class="secno">5. </bdi>Vocabulary overview</h2><a class="self-link" href="#vocabulary-overview" aria-label="Permalink for Section 5."></a></div><p><em>This section is non-normative.</em></p> <section id="dcat-scope"><div class="header-wrapper"><h3 id="x5-1-dcat-scope"><bdi class="secno">5.1 </bdi>DCAT scope</h3><a class="self-link" href="#dcat-scope" aria-label="Permalink for Section 5.1"></a></div> <p>DCAT is an RDF vocabulary for representing data catalogs. DCAT is based around seven main classes (<a href="#fig-dcat-all-attributes" class="fig-ref" title="Overview of DCAT model, showing the classes of resources that can be members of a Catalog, and the relationships between them. Except where specifically indicated, DCAT does not provide cardinality constraints.">Figure <bdi class="">1</bdi></a>):</p> <ul> <li> <a href="#Class:Catalog"><code>dcat:Catalog</code></a> represents a catalog, which is a dataset in which each individual item is a metadata record describing some resource; the scope of <code>dcat:Catalog</code> is collections of metadata about <b>datasets</b>, <b>data services</b>, or other resource types. </li> <li> <a href="#Class:Resource"><code>dcat:Resource</code></a> represents a dataset, a data service or any other resource that may be described by a metadata record in a catalog. This class is not intended to be used directly, but is the parent class of <a href="#Class:Dataset"><code>dcat:Dataset</code></a>, <a href="#Class:Data_Service"><code>dcat:DataService</code></a> and <a href="#Class:Catalog"><code>dcat:Catalog</code></a>. Resources in a catalog should be instances of one of these classes, or of a sub-class of these, or of a sub-class of <a href="#Class:Resource"><code>dcat:Resource</code></a> defined in a DCAT profile or other DCAT application. <a href="#Class:Resource"><code>dcat:Resource</code></a> is actually an extension point for defining a catalog of any kind of resources. <a href="#Class:Dataset"><code>dcat:Dataset</code></a> and <a href="#Class:Data_Service"><code>dcat:DataService</code></a> can be used for datasets and services which are not documented in any catalog. </li> <li> <a href="#Class:Dataset"><code>dcat:Dataset</code></a> represents a collection of data, published or curated by a single agent or identifiable community. The notion of dataset in DCAT is broad and inclusive, with the intention of accommodating resource types arising from all communities. Data comes in many forms including numbers, text, pixels, imagery, sound and other multi-media, and potentially other types, any of which might be collected into a dataset. </li> <li> <a href="#Class:Distribution"><code>dcat:Distribution</code></a> represents an accessible form of a dataset such as a downloadable file. </li> <li> <a href="#Class:Data_Service"><code>dcat:DataService</code></a> represents a collection of operations accessible through an interface (<abbr title="Application Programming Interface">API</abbr>) that provide access to one or more datasets or data processing functions. </li> <li> <a href="#Class:Dataset_Series"><code>dcat:DatasetSeries</code></a> is a dataset that represents a collection of datasets that are published separately, but share some characteristics that group them. </li> <li> <a href="#Class:Catalog_Record"><code>dcat:CatalogRecord</code></a> represents a metadata record in the catalog, primarily concerning the registration information, such as who added the record and when. </li> </ul> <figure id="fig-dcat-all-attributes"> <img alt="UML model of DCAT classes and properties" src="./images/dcat-all-attributes.svg"> <figcaption><a class="self-link" href="#fig-dcat-all-attributes">Figure <bdi class="figno">1</bdi></a> <span class="fig-title"> Overview of DCAT model, showing the classes of resources that can be members of a Catalog, and the relationships between them. Except where specifically indicated, DCAT does not provide cardinality constraints. </span></figcaption> </figure> <div class="note" role="note" id="issue-container-generatedID-1"><div role="heading" class="note-title marker" id="h-note-1" aria-level="4"><span>Note</span></div><aside class=""> <p> Along with the rest of <a href="#vocabulary-overview" class="sec-ref"><bdi class="secno">5. </bdi>Vocabulary overview</a>, this diagram is <b>non-normative</b>. Furthermore, while the diagram uses UML-style class notation it should be interpreted following the usual RDF open-world assumptions around the presence/absence of properties, relationships, and their cardinality. The properties shown in each class reflect those specified in the descriptions of classes in <a href="#vocabulary-specification" class="sec-ref"><bdi class="secno">6. </bdi>Vocabulary specification</a>. Open arrow-heads indicate RDFS <i>sub-class-of</i> relationships (not object-oriented generalization). To assist in understanding the full scope of each class, available properties are copied down from each '::super-class'. </p> </aside></div> <p> A <b>dataset</b> in DCAT is defined as a "collection of data, published or curated by a single agent, and available for access or download in one or more serializations or formats". A dataset is a conceptual entity, and can be represented by one or more <b>distributions</b> that serialize the dataset for transfer. Distributions of a dataset can be provided via <b>data services</b>. </p> <p> A data service typically provides selection, extraction, combination, processing or transformation operations over datasets that might be hosted locally or remote to the service. The result of any request to a data service is a representation of a part or all of a dataset or catalog. A data service might be tied to specific datasets, or its source data might be configured at request- or run-time. A data distribution service allows selection and download of a distribution of a dataset or subset. A data discovery service allows a client to find a suitable dataset. Other kinds of data service include data transformation services, such as coordinate transformation services, re-sampling and interpolation services, and various data processing services, including simulation and modeling services. Note that a data service in DCAT is a collection of operations or <b><abbr title="Application Programming Interface">API</abbr></b> which provides access to data. An interactive user-interface is often available to provide convenient access to <abbr title="Application Programming Interface">API</abbr> operations, but its description is outside the scope of DCAT. The details of a particular data service endpoint will often be specified through a description conforming to a standard service type, which complement the scope of the DCAT vocabulary itself. </p> <p> Descriptions of datasets and data services can be included in a <b>catalog</b>. A catalog is a kind of dataset whose member items are descriptions of datasets and data services. Other types of resources might also be cataloged, but the scope of DCAT is currently limited to datasets and data services. To extend the scope of a catalog beyond datasets and data services it is recommended to define additional sub-classes of <a href="#Class:Resource"><code>dcat:Resource</code></a> in a DCAT profile or other DCAT application. To extend the scope of service descriptions beyond data distribution services it is recommended to define additional sub-classes of <a href="#Class:Data_Service"><code>dcat:DataService</code></a> in a DCAT profile or other DCAT application. </p> <div class="note" role="note" id="issue-container-generatedID-2"><div role="heading" class="note-title marker" id="h-note-2" aria-level="4"><span>Note</span></div><aside class=""> <p> The scope of DCAT 1 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>] was limited to catalogs of datasets. A number of use cases for the revision [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ucr" title="Dataset Exchange Use Cases and Requirements">DCAT-UCR</a></cite>] involve <b>data services</b> as members of a catalog - see <a href="https://www.w3.org/TR/dcat-ucr/#ID6">§ <span class="secno">5.16 </span>DCAT Distribution to describe Web services</a> and <a href="https://www.w3.org/TR/dcat-ucr/#ID18">§ <span class="secno">5.18 </span>Modeling service-based data access</a>. Since DCAT 2 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-2" title="Data Catalog Vocabulary (DCAT) - Version 2">VOCAB-DCAT-2</a></cite>], DCAT includes both datasets and data services to enable these to be part of a DCAT conformant catalog. Provision for catalogs to be composed of other catalogs is also made. See Issue <a href="https://github.com/w3c/dxwg/issues/172">#172</a>. </p> <p> Catalogs of other kinds of things might be designed following the DCAT pattern, e.g., dealing with facilities, instruments, samples and specimens, other physical artifacts, events or activities. These are currently out of scope for DCAT, but might be defined through further sub-classes of <a href="#Class:Resource"><code>dcat:Resource</code></a>, which could be specified in a DCAT profile or other DCAT application. </p> </aside></div> <p>A <b>catalog record</b> describes an entry in the catalog. Notice that while <a href="#Class:Resource"><code>dcat:Resource</code></a> represents the dataset or service itself, <a href="#Class:Catalog_Record"><code>dcat:CatalogRecord</code></a> is the record that describes the registration of a resource in the catalog. The use of <a href="#Class:Catalog_Record"><code>dcat:CatalogRecord</code></a> is considered optional. It is used to capture provenance information about entries in a catalog explicitly. If this is not necessary then <a href="#Class:Catalog_Record"><code>dcat:CatalogRecord</code></a> can be safely ignored.</p> </section> <section id="dcat-rdf"><div class="header-wrapper"><h3 id="x5-2-rdf-considerations"><bdi class="secno">5.2 </bdi>RDF considerations</h3><a class="self-link" href="#dcat-rdf" aria-label="Permalink for Section 5.2"></a></div> <p id="owl2"> The DCAT vocabulary is an OWL2 ontology [<cite><a class="bibref" data-link-type="biblio" href="#bib-owl2-overview" title="OWL 2 Web Ontology Language Document Overview (Second Edition)">OWL2-OVERVIEW</a></cite>] formalized using [<cite><a class="bibref" data-link-type="biblio" href="#bib-rdf-schema" title="RDF Schema 1.1">RDF-SCHEMA</a></cite>]. Each class and property in DCAT is denoted by an <abbr title="Internationalized Resource Identifier">IRI</abbr> [<cite><a class="bibref" data-link-type="biblio" href="#bib-rfc3987" title="Internationalized Resource Identifiers (IRIs)">RFC3987</a></cite>]. Locally defined elements are in the namespace <a href="https://www.w3.org/ns/dcat#"><code>http://www.w3.org/ns/dcat#</code></a>. Elements are also adopted from several external vocabularies, in particular [<cite><a class="bibref" data-link-type="biblio" href="#bib-foaf" title="FOAF Vocabulary Specification 0.99 (Paddington Edition)">FOAF</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] and [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] </p> <p id="blankNodes"> RDF allows resources to have global identifiers (<abbr title="Internationalized Resource Identifiers">IRIs</abbr>) or to be blank nodes. Blank nodes can be used to denote resources without explicitly naming them with an <abbr title="Internationalized Resource Identifier">IRI</abbr>. They can appear in the subject and object position of a triple [<cite><a class="bibref" data-link-type="biblio" href="#bib-rdf11-primer" title="RDF 1.1 Primer">RDF11-PRIMER</a></cite>]. For example, in many actual DCAT catalogs, distributions are represented as blank nodes nested inside the related dataset description. While blank nodes can offer flexibility for some use cases, in a Linked Data context, blank nodes limit our ability to collaboratively annotate data. A blank node resource cannot be the target of a link and it can't be annotated with new information from new sources. As one of the biggest benefits of the Linked Data approach is that "anyone can say anything anywhere", use of blank nodes undermines some of the advantages we can gain from wide adoption of the RDF model. Even within the closed world of a single application dataset, use of blank nodes can quickly become limiting when integrating new data [<cite><a class="bibref" data-link-type="biblio" href="#bib-linkeddatapatterns" title="Linked Data Patterns: A pattern catalogue for modelling, publishing, and consuming Linked Data">LinkedDataPatterns</a></cite>]. For these reasons, it is recommended that instances of the DCAT main classes have a global identifier, and use of blank nodes is generally discouraged when encoding DCAT in RDF. </p> <p id="rdf-syntax"> All RDF examples in this document are written in Turtle syntax [<cite><a class="bibref" data-link-type="biblio" href="#bib-turtle" title="RDF 1.1 Turtle">Turtle</a></cite>] and many are available from the <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/examples">DXWG code repository</a>. </p> <div class="note" role="note" id="issue-container-generatedID-3"><div role="heading" class="note-title marker" id="h-note-3" aria-level="4"><span>Note</span></div><aside class=""> <p> Each RDF example in this document is intended to demonstrate specific capabilities of DCAT, and therefore only shows a subset of all the potential properties and links which might appear in a complete DCAT resource. </p> </aside></div> </section> <section id="basic-example"><div class="header-wrapper"><h3 id="x5-3-basic-example"><bdi class="secno">5.3 </bdi>Basic example</h3><a class="self-link" href="#basic-example" aria-label="Permalink for Section 5.3"></a></div> <p>This example provides a quick overview of how DCAT might be used to represent a government catalog and its datasets. Titles, labels and keywords are provided both in English and Spanish to demonstrate the use of language tags.</p> <p>First, the catalog description: </p> <aside id="ex-catalog" class="example"><div class="marker"> <a class="self-link" href="#ex-catalog">Example<bdi> 1</bdi></a> </div> <pre class="nohighlight turtle">ex:catalog a dcat:Catalog ; dcterms:title "Imaginary Catalog"@en ; dcterms:title "Catálogo imaginario"@es ; rdfs:label "Imaginary Catalog"@en ; rdfs:label "Catálogo imaginario"@es ; foaf:homepage <http://dcat.example.org/catalog> ; dcterms:publisher ex:transparency-office ; dcterms:language <http://id.loc.gov/vocabulary/iso639-1/en>  ; dcat:dataset ex:dataset-001 , ex:dataset-002 , ex:dataset-003 ; .</pre> </aside> <p>The publisher of the catalog has the relative <abbr title="Internationalized Resource Identifier">IRI</abbr> <code>ex:transparency-office</code>. Further description of the publisher can be provided as in <a href="#ex-publisher" class="box-ref">Example<bdi> 2</bdi></a>: </p> <aside id="ex-publisher" class="example"><div class="marker"> <a class="self-link" href="#ex-publisher">Example<bdi> 2</bdi></a> </div> <pre class="nohighlight turtle">ex:transparency-office a foaf:Organization ; rdfs:label "Transparency Office"@en ; rdfs:label "Oficina de Transparencia"@es ; .</pre> </aside> <p>The catalog lists each of its datasets via the <code>dcat:dataset</code> property. In <a href="#ex-catalog" class="box-ref">Example<bdi> 1</bdi></a>, an example dataset was mentioned with the relative <abbr title="Internationalized Resource Identifier">IRI</abbr> <code>ex:dataset-001</code>. A possible description of it using DCAT is shown below: </p> <aside id="ex-dataset" class="example"><div class="marker"> <a class="self-link" href="#ex-dataset">Example<bdi> 3</bdi></a> </div> <pre class="nohighlight turtle">ex:dataset-001 a dcat:Dataset ; dcterms:title "Imaginary dataset"@en ; dcterms:title "Conjunto de datos imaginario"@es ; dcat:keyword "accountability"@en, "transparency"@en, "payments"@en ; dcat:keyword "responsabilidad"@es, "transparencia"@es, "pagos"@es ; dcterms:creator ex:finance-employee-001 ; dcterms:issued "2011-12-05"^^xsd:date ; dcterms:modified "2011-12-15"^^xsd:date ; dcat:contactPoint <http://dcat.example.org/transparency-office/contact> ; dcterms:temporal [ a dcterms:PeriodOfTime ; dcat:startDate "2011-07-01"^^xsd:date ; dcat:endDate "2011-09-30"^^xsd:date ; ]; dcat:temporalResolution "P1D"^^xsd:duration ; dcterms:spatial <http://sws.geonames.org/6695072/> ; dcat:spatialResolutionInMeters "30.0"^^xsd:decimal ; dcterms:publisher ex:finance-ministry ; dcterms:language <http://id.loc.gov/vocabulary/iso639-1/en> ; dcterms:accrualPeriodicity <http://purl.org/linked-data/sdmx/2009/code#freq-W>  ; dcat:distribution ex:dataset-001-csv ; .</pre> </aside> <p> Five distinct temporal descriptors are shown for this dataset. The dataset publication and revision dates are shown in <a href="#Property:resource_release_date"><code>dcterms:issued</code></a> and <a href="#Property:resource_update_date"><code>dcterms:modified</code></a>. For the frequency of update of the dataset in <a href="#Property:dataset_frequency"><code>dcterms:accrualPeriodicity</code></a>, we use an instance from the <a href="https://www.w3.org/TR/vocab-data-cube/#dsd-cog">content-oriented guidelines</a> developed as part of the <abbr title="World Wide Web Consortium">W3C</abbr> Data Cube Vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-data-cube" title="The RDF Data Cube Vocabulary">VOCAB-DATA-CUBE</a></cite>] efforts. The temporal coverage or extent is given in <a href="#Property:dataset_temporal"><code>dcterms:temporal</code></a> defining a <a href="#Class:Period_of_Time"><code>dcterms:PeriodOfTime</code></a> as a closed interval indicated by <a href="#Property:period_start_date"><code>dcat:startDate</code></a> and <a href="#Property:period_end_date"><code>dcat:endDate</code></a>. The temporal resolution, which describes the minimum spacing of items within the dataset, is given in <a href="#Property:dataset_temporal_resolution"><code>dcat:temporalResolution</code></a> using the standard datatype <code>xsd:duration</code>. </p> <p> Additionally, the spatial coverage or extent is given <a href="#Property:dataset_spatial"><code>dcterms:spatial</code></a> using an <abbr title="Internationalized Resource Identifier">IRI</abbr> from <a href="http://www.geonames.org/">Geonames</a>. The spatial resolution, which describes the minimum spatial separation of items within the dataset, is given in <a href="#Property:dataset_spatial_resolution"><code>dcat:spatialResolutionInMeters</code></a> using the standard datatype <code>xsd:decimal</code>. </p> <p> A contact point is provided where comments and feedback about the dataset can be sent. Further details about the contact point, such as email address or telephone number, can be provided using vCard [<cite><a class="bibref" data-link-type="biblio" href="#bib-vcard-rdf" title="vCard Ontology - for describing People and Organizations">VCARD-RDF</a></cite>]. </p> <p>One representation of the dataset <code>ex:dataset-001-csv</code> can be downloaded as a 5kB CSV file. This is represented as an RDF resource of type <code>dcat:Distribution</code>. </p> <aside id="ex-distribution" class="example"><div class="marker"> <a class="self-link" href="#ex-distribution">Example<bdi> 4</bdi></a> </div> <pre class="nohighlight turtle">ex:dataset-001-csv a dcat:Distribution ; dcat:downloadURL <http://dcat.example.org/files/001.csv> ; dcterms:title "CSV distribution of imaginary dataset 001"@en ; dcterms:title "distribución en CSV del conjunto de datos imaginario 001"@es ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/csv> ; dcat:byteSize "5120"^^xsd:nonNegativeInteger ; .</pre> </aside> </section> <section id="classifying-datasets"><div class="header-wrapper"><h3 id="x5-4-classifying-datasets-thematically"><bdi class="secno">5.4 </bdi>Classifying datasets thematically</h3><a class="self-link" href="#classifying-datasets" aria-label="Permalink for Section 5.4"></a></div> <p>The catalog classifies its datasets according to a set of domains represented by the relative <abbr title="Internationalized Resource Identifier">IRI</abbr> <code>ex:themes</code>. SKOS [<cite><a class="bibref" data-link-type="biblio" href="#bib-skos-reference" title="SKOS Simple Knowledge Organization System Reference">SKOS-REFERENCE</a></cite>] can be used to describe the domains used: </p> <aside id="ex-thematic-classification" class="example"><div class="marker"> <a class="self-link" href="#ex-thematic-classification">Example<bdi> 5</bdi></a> </div> <pre class="nohighlight turtle">ex:catalog dcat:themeTaxonomy ex:themes . ex:themes a skos:ConceptScheme ; skos:prefLabel "A set of domains to classify documents"@en ; . ex:dataset-001 dcat:theme ex:accountability .</pre> </aside> <p>Notice that this dataset is classified under the domain represented by the relative <abbr title="Internationalized Resource Identifier">IRI</abbr> <code>ex:accountability</code>. It is recommended to define the concept as part of the concept scheme identified by the <abbr title="Internationalized Resource Identifier">IRI</abbr> <code>ex:themes</code> that was used to describe the catalog domains. An example SKOS description: </p> <aside id="ex-theme-accountability" class="example"><div class="marker"> <a class="self-link" href="#ex-theme-accountability">Example<bdi> 6</bdi></a> </div> <pre class="nohighlight turtle">ex:accountability a skos:Concept ; skos:inScheme ex:themes ; skos:prefLabel "Accountability"@en ; .</pre> </aside> </section> <section id="classifying-dataset-types"><div class="header-wrapper"><h3 id="x5-5-classifying-dataset-types"><bdi class="secno">5.5 </bdi>Classifying dataset types</h3><a class="self-link" href="#classifying-dataset-types" aria-label="Permalink for Section 5.5"></a></div> <p> The type or genre of a dataset can be indicated using the <a href="http://purl.org/dc/terms/type"><code>dcterms:type</code></a> property. It is recommended that the value of the property is taken from a well governed and broadly recognised set of resource types, such as the <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#section-7">DCMI Type Vocabulary</a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>], the <a href="https://id.loc.gov/vocabulary/marcgt.html">MARC Genre/Terms Scheme</a>, the [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115-1" title="Geographic information -- Metadata -- Part 1: Fundamentals">ISO-19115-1</a></cite>] <a href="https://standards.iso.org/iso/19115/resources/Codelists/gml/MD_ScopeCode.xml"><code>MD_Scope codes</code></a>, the <a href="https://schema.datacite.org/meta/kernel-4.4/include/datacite-resourceType-v4.xsd">DataCite resource types</a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-datacite" title="DataCite Metadata Schema">DataCite</a></cite>], or the PARSE.Insight content-types from Re3data [<cite><a class="bibref" data-link-type="biblio" href="#bib-re3data-schema" title="Metadata Schema for the Description of Research Data Repositories: version 3">RE3DATA-SCHEMA</a></cite>]. </p> <p> In the following examples, a (notional) dataset is classified separately using values from different vocabularies. </p> <aside id="ex-dataset-type" class="example"><div class="marker"> <a class="self-link" href="#ex-dataset-type">Example<bdi> 7</bdi></a> </div> <pre class="nohighlight turtle">ex:dataset-001 rdf:type dcat:Dataset ; dcterms:type <http://purl.org/dc/dcmitype/Dataset> ; . ex:dataset-001 rdf:type dcat:Dataset ; dcterms:type <http://id.loc.gov/vocabulary/marcgt/dtb> ; .</pre> </aside> <p> It is also possible for multiple classifications to be present in a single description. </p> <aside id="ex-dataset-multiple-types" class="example"><div class="marker"> <a class="self-link" href="#ex-dataset-multiple-types">Example<bdi> 8</bdi></a> </div> <pre class="nohighlight turtle">ex:dataset-001 rdf:type dcat:Dataset ; dcterms:type <http://purl.org/dc/dcmitype/Dataset> ; dcterms:type <http://id.loc.gov/vocabulary/marcgt/dtb> ; dcterms:type <urn:example:datacite/resourceType/Dataset> ; dcterms:type <urn:example:re3data/contentType/database> ; . <urn:example:datacite/resourceType/Dataset> rdfs:label "Dataset"@en ; dcterms:source [ rdfs:label "DataCite resource types"@en ] ; . <urn:example:re3data/contentType/database> rdfs:label "Database"@en ; dcterms:source [ rdfs:label "Re3data content types"@en ] ; .</pre> </aside> </section> <section id="describing-catalog-records-metadata"><div class="header-wrapper"><h3 id="x5-6-describing-catalog-records-metadata"><bdi class="secno">5.6 </bdi>Describing catalog records metadata</h3><a class="self-link" href="#describing-catalog-records-metadata" aria-label="Permalink for Section 5.6"></a></div> <p>If the catalog publisher decides to keep metadata describing its records (i.e., the records containing metadata describing the datasets), <code>dcat:CatalogRecord</code> can be used. For example, while <code>ex:dataset-001</code> was issued on 2011-12-05, its description on Imaginary Catalog was added on 2011-12-11. This can be represented by DCAT as in <a href="#ex-catalog-record" class="box-ref">Example<bdi> 9</bdi></a>: </p> <aside id="ex-catalog-record" class="example"><div class="marker"> <a class="self-link" href="#ex-catalog-record">Example<bdi> 9</bdi></a> </div> <pre class="nohighlight turtle">ex:catalog dcat:record ex:record-001 . ex:record-001 a dcat:CatalogRecord ; foaf:primaryTopic ex:dataset-001 ; dcterms:issued "2011-12-11"^^xsd:date ; .</pre> </aside> </section> <section id="example-landing-page"><div class="header-wrapper"><h3 id="x5-7-dataset-available-only-behind-some-web-page"><bdi class="secno">5.7 </bdi>Dataset available only behind some Web page</h3><a class="self-link" href="#example-landing-page" aria-label="Permalink for Section 5.7"></a></div> <p><code>ex:dataset-002</code> is available as a CSV file. However <code>ex:dataset-002</code> can only be obtained through some Web page where the user needs to follow some links, provide some information and check some boxes before accessing the data.</p> <aside id="ex-landing-page" class="example"><div class="marker"> <a class="self-link" href="#ex-landing-page">Example<bdi> 10</bdi></a> </div> <pre class="nohighlight turtle">ex:dataset-002 a dcat:Dataset ; dcat:landingPage <http://dcat.example.org/dataset-002.html> ; dcat:distribution ex:dataset-002-csv ; . ex:dataset-002-csv a dcat:Distribution ; dcat:accessURL <http://dcat.example.org/dataset-002.html> ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/csv> ; .</pre> </aside> <p>Notice the use of a <code>dcat:landingPage</code> and the definition of the <code>dcat:Distribution</code> instance.</p> </section> <section id="a-dataset-available-as-download-and-behind-some-web-page"><div class="header-wrapper"><h3 id="x5-8-a-dataset-available-as-a-download-and-behind-some-web-page"><bdi class="secno">5.8 </bdi>A dataset available as a download and behind some Web page</h3><a class="self-link" href="#a-dataset-available-as-download-and-behind-some-web-page" aria-label="Permalink for Section 5.8"></a></div> <p>On the other hand, <code>ex:dataset-003</code> can be obtained through some landing page but also can be downloaded from a known URL. </p> <aside id="ex-access-and-download-url" class="example"><div class="marker"> <a class="self-link" href="#ex-access-and-download-url">Example<bdi> 11</bdi></a> </div> <pre class="nohighlight turtle">ex:dataset-003 a dcat:Dataset ; dcat:landingPage <http://dcat.example.org/dataset-003.html> ; dcat:distribution ex:dataset-003-csv ; . ex:dataset-003-csv a dcat:Distribution ; dcat:downloadURL <http://dcat.example.org/dataset-003.csv> ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/csv> ; .</pre> </aside> <p>Notice that we used <code>dcat:downloadURL</code> with the downloadable distribution and that the other distribution accessible through the landing page does not have to be defined as a separate <code>dcat:Distribution</code> instance.</p> </section> <section id="a-dataset-available-from-a-service"><div class="header-wrapper"><h3 id="x5-9-a-dataset-available-through-a-service"><bdi class="secno">5.9 </bdi>A dataset available through a service</h3><a class="self-link" href="#a-dataset-available-from-a-service" aria-label="Permalink for Section 5.9"></a></div> <p><code>ex:dataset-004</code> is distributed in different representations from different services. The <code>dcat:accessURL</code> for each <code>dcat:Distribution</code> corresponds with the <code>dcat:endpointURL</code> of the service. Each service is characterized by its general type using <code>dcterms:type</code> (here using values from the INSPIRE spatial data service type vocabulary), its specific <abbr title="Application Programming Interface">API</abbr> definition using <code>dcterms:conformsTo</code>, with the detailed description of the individual endpoint parameters and options linked using <code>dcat:endpointDescription</code>. </p> <aside id="ex-access-service" class="example"><div class="marker"> <a class="self-link" href="#ex-access-service">Example<bdi> 12</bdi></a> </div> <pre class="nohighlight turtle">ex:dataset-004 rdf:type dcat:Dataset ; dcat:distribution ex:dataset-004-csv ; dcat:distribution ex:dataset-004-png ; . ex:dataset-004-csv rdf:type dcat:Distribution ; dcat:accessService ex:table-service-005 ; dcat:accessURL <http://dcat.example.org/api/table-005> ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/csv> ; . ex:dataset-004-png rdf:type dcat:Distribution ; dcat:accessService ex:figure-service-006 ; dcat:accessURL <http://dcat.example.org/api/figure-006> ; dcat:mediaType <http://www.iana.org/assignments/media-types/image/png> ; . ex:figure-service-006 rdf:type dcat:DataService ; dcterms:conformsTo <http://dcat.example.org/apidef/figure/v1.0> ; dcterms:type <https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/view> ; dcat:endpointDescription <http://dcat.example.org/api/figure-006/params> ; dcat:endpointURL <http://dcat.example.org/api/figure-006> ; dcat:servesDataset ex:dataset-004 ; . ex:table-service-005 rdf:type dcat:DataService ; dcterms:conformsTo <http://dcat.example.org/apidef/table/v2.2> ; dcterms:type <https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/download> ; dcat:endpointDescription <http://dcat.example.org/api/table-005/capability> ; dcat:endpointURL <http://dcat.example.org/api/table-005> ; dcat:servesDataset ex:dataset-003, ex:dataset-004 ; .</pre> </aside> </section> </section> <section id="vocabulary-specification"><div class="header-wrapper"><h2 id="x6-vocabulary-specification"><bdi class="secno">6. </bdi>Vocabulary specification</h2><a class="self-link" href="#vocabulary-specification" aria-label="Permalink for Section 6."></a></div> <section id="RDF-representation"><div class="header-wrapper"><h3 id="x6-1-rdf-representation"><bdi class="secno">6.1 </bdi>RDF representation</h3><a class="self-link" href="#RDF-representation" aria-label="Permalink for Section 6.1"></a></div> <div class="note" id="issue-container-generatedID-4"><div role="heading" class="ednote-title marker" id="h-ednote" aria-level="4"><span>Editor's note</span></div><aside class=""> <p>New RDF serializations will be made available for DCAT 3 in the official URIs as soon as DCAT 3 becomes REC. In the meanwhile, the DCAT 3 RDFs are available in the <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/rdf">DXWG GitHub repository</a>: <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/rdf/dcat3.ttl">dcat3.ttl</a>, <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/rdf/dcat3.rdf">dcat3.rdf</a>, and <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/rdf/dcat3.jsonld">dcat3.jsonld</a></p> </aside></div> <p>The (revised) DCAT vocabulary is <a href="https://www.w3.org/ns/dcat#">available in RDF</a>. The primary artifact <a href="https://www.w3.org/ns/dcat.ttl"><code>dcat.ttl</code></a> is a serialization of the core DCAT vocabulary. Alongside it are a set of other RDF files that provide additional information, including:</p> <ol> <li> <p>The files <a href="https://www.w3.org/ns/dcat-external.ttl">dcat-external.ttl</a>, <a href="https://www.w3.org/ns/dcat-external.rdf">dcat-external.rdf</a>, and <a href="https://www.w3.org/ns/dcat-external.jsonld">dcat-external.jsonld</a> includes externally defined terms where DCAT has provided additional documentation or usage notes.</p> </li> <li> <p>The files <a href="https://www.w3.org/ns/dcat2.ttl">dcat2.ttl</a>, <a href="https://www.w3.org/ns/dcat2.rdf">dcat2.rdf</a>, and <a href="https://www.w3.org/ns/dcat2.jsonld">dcat2.jsonld</a> that correspond to version 2 of DCAT [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-2" title="Data Catalog Vocabulary (DCAT) - Version 2">VOCAB-DCAT-2</a></cite>].</p> </li> <li> The files <a href="https://www.w3.org/ns/dcat2014.ttl">dcat2014.ttl</a> and <a href="https://www.w3.org/ns/dcat2014.rdf">dcat2014.rdf</a> that correspond to the 2014 version of DCAT [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>]. </li> </ol> <div class="note" role="note" id="issue-container-generatedID-5"><div role="heading" class="note-title marker" id="h-note-4" aria-level="4"><span>Note</span></div><aside class=""> <p>Where possible, properties defined by DCAT do not have specified domains in order to leave the property open for use with any kind of resources. The intention is that such properties can be reused in any suitable circumstance where they make sense. </p> </aside></div> </section> <section id="external-vocab"><div class="header-wrapper"><h3 id="x6-2-elements-from-other-vocabularies"><bdi class="secno">6.2 </bdi>Elements from other vocabularies</h3><a class="self-link" href="#external-vocab" aria-label="Permalink for Section 6.2"></a></div> <p> DCAT requires use of elements from a number of other vocabularies. Furthermore, DCAT may be augmented by additional elements from external vocabularies, following the usual RDFS [<cite><a class="bibref" data-link-type="biblio" href="#bib-rdf-schema" title="RDF Schema 1.1">RDF-SCHEMA</a></cite>] and OWL2 [<cite><a class="bibref" data-link-type="biblio" href="#bib-owl2-overview" title="OWL 2 Web Ontology Language Document Overview (Second Edition)">OWL2-OVERVIEW</a></cite>] rules and patterns. </p> <section id="complements"><div class="header-wrapper"><h4 id="x6-2-1-complementary-vocabularies"><bdi class="secno">6.2.1 </bdi>Complementary vocabularies</h4><a class="self-link" href="#complements" aria-label="Permalink for Section 6.2.1"></a></div> <p> Elements from a number of complementary vocabularies <em class="rfc2119">MAY</em> be used together with DCAT to provide more detailed information. For example: properties from the VoID vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-void" title="Describing Linked Datasets with the VoID Vocabulary">VOID</a></cite>] allow the description of various statistics about a DCAT-described dataset if that dataset is in RDF format; properties from the Provenance ontology [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] can be used to provide more information about the workflow that generated a dataset or service and related activities and agents; classes and properties from the Organization Ontology [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-org" title="The Organization Ontology">VOCAB-ORG</a></cite>] can be used to explain additional details of responsible agents. </p> </section> <section id="dependencies"><div class="header-wrapper"><h4 id="x6-2-2-element-definitions"><bdi class="secno">6.2.2 </bdi>Element definitions</h4><a class="self-link" href="#dependencies" aria-label="Permalink for Section 6.2.2"></a></div> <p> The definitions (including domain and range) of terms outside the DCAT namespace are provided here only for convenience and <em class="rfc2119">MUST NOT</em> be considered normative. The authoritative definitions of these terms are in the corresponding specifications, i.e., [<cite><a class="bibref" data-link-type="biblio" href="#bib-dc11" title="Dublin Core Metadata Element Set, Version 1.1">DC11</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-foaf" title="FOAF Vocabulary Specification 0.99 (Paddington Edition)">FOAF</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-rdf-schema" title="RDF Schema 1.1">RDF-SCHEMA</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-skos-reference" title="SKOS Simple Knowledge Organization System Reference">SKOS-REFERENCE</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-xmlschema11-2" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">XMLSCHEMA11-2</a></cite>] and [<cite><a class="bibref" data-link-type="biblio" href="#bib-vcard-rdf" title="vCard Ontology - for describing People and Organizations">VCARD-RDF</a></cite>]. </p> </section> </section> <section id="Class:Catalog"><div class="header-wrapper"><h3 id="x6-3-class-catalog"><bdi class="secno">6.3 </bdi>Class: Catalog</h3><a class="self-link" href="#Class:Catalog" aria-label="Permalink for Section 6.3"></a></div> <div class="note" role="note" id="issue-container-generatedID-6"><div role="heading" class="note-title marker" id="h-note-5" aria-level="4"><span>Note</span></div><aside class=""> <p>The scope of <code>dcat:Catalog</code> in DCAT 1 was catalogs of datasets [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>]. Since DCAT 2 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-2" title="Data Catalog Vocabulary (DCAT) - Version 2">VOCAB-DCAT-2</a></cite>], this was generalized, and properties common to all cataloged resources were associated with a super-class <a href="#Class:Resource"><code>dcat:Resource</code></a>.</p> <p>Moreover, an explicit class for <a href="#Class:Data_Service">data services</a> was added in DCAT, to enable these to be part of a catalog.</p> <p>Finally, <code>dcat:Catalog</code> was made a sub-class of <code>dcat:Dataset</code>, and provision for catalogs to be composed of other catalogs is also enabled.</p> <p>See Issue <a href="https://github.com/w3c/dxwg/issues/116">#116</a> and Issue <a href="https://github.com/w3c/dxwg/issues/172">#172</a>.</p> </aside></div> <p>The following properties are specific to this class:</p><p> </p><ul class="prop-list"> <li><a href="#Property:catalog_catalog_record">catalog record</a></li> <li><a href="#Property:catalog_resource">resource</a></li> <li><a href="#Property:catalog_dataset">dataset</a></li> <li><a href="#Property:catalog_service">service</a></li> <li><a href="#Property:catalog_catalog">catalog</a></li> <li><a href="#Property:catalog_homepage">homepage</a></li> <li><a href="#Property:catalog_themes">themes</a></li> </ul> <p>The following properties of the super-class <a href="#Class:Dataset"><code>dcat:Dataset</code></a> are also available for use:</p> <ul class="prop-list"> <li><a href="#Property:dataset_distribution">distribution</a></li> <li><a href="#Property:dataset_frequency">frequency</a></li> <li><a href="#Property:dataset_spatial">spatial/geographic coverage</a></li> <li><a href="#Property:dataset_spatial_resolution">spatial resolution</a></li> <li><a href="#Property:dataset_temporal">temporal coverage</a></li> <li><a href="#Property:dataset_temporal_resolution">temporal resolution</a></li> <li><a href="#Property:dataset_was_generated_by">was generated by</a></li> </ul> <p>The following properties of the super-class <a href="#Class:Resource"><code>dcat:Resource</code></a> are also available for use:</p> <ul class="prop-list"> <li><a href="#Property:resource_access_rights">access rights</a></li> <li><a href="#Property:resource_conforms_to">conforms to</a></li> <li><a href="#Property:resource_contact_point">contact point</a></li> <li><a href="#Property:resource_creator">creator</a></li> <li><a href="#Property:resource_description">description</a></li> <li><a href="#Property:resource_has_policy">has policy</a></li> <li><a href="#Property:resource_identifier">identifier</a></li> <li><a href="#Property:resource_is_referenced_by">is referenced by</a></li> <li><a href="#Property:resource_keyword">keyword/tag</a></li> <li><a href="#Property:resource_landing_page">landing page</a></li> <li><a href="#Property:resource_license">license</a></li> <li><a href="#Property:resource_language">language</a></li> <li><a href="#Property:resource_relation">relation</a></li> <li><a href="#Property:resource_rights">rights</a></li> <li><a href="#Property:resource_qualified_relation">qualified relation</a></li> <li><a href="#Property:resource_publisher">publisher</a></li> <li><a href="#Property:resource_release_date">release date</a></li> <li><a href="#Property:resource_theme">theme/category</a></li> <li><a href="#Property:resource_title">title</a></li> <li><a href="#Property:resource_type">type/genre</a></li> <li><a href="#Property:resource_update_date">update/modification date</a></li> <li><a href="#Property:resource_qualified_attribution">qualified attribution</a></li> <li><a href="#Property:resource_has_current_version">has current version</a></li> <li><a href="#Property:resource_has_version">has version</a></li> <li><a href="#Property:resource_previous_version">previous version</a></li> <li><a href="#Property:resource_replaces">replaces</a></li> <li><a href="#Property:resource_status">status</a></li> <li><a href="#Property:resource_version">version</a></li> <li><a href="#Property:resource_version_notes">version notes</a></li> <li><a href="#Property:resource_first">first</a></li> <li><a href="#Property:resource_last">last</a></li> <li><a href="#Property:resource_previous">previous</a></li> </ul> <table class="def"> <tbody><tr><th>RDF Class:</th><td><a href="https://www.w3.org/ns/dcat#Catalog"><code>dcat:Catalog</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A curated collection of metadata about resources.</td></tr> <tr><th class="prop">Sub-class of:</th><td><a href="#Class:Dataset"><code>dcat:Dataset</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>A Web-based data catalog is typically represented as a single instance of this class.</td></tr> <tr><th class="prop">Usage note:</th><td>Datasets and data services are examples of resources in the context of a data catalog.</td></tr> <tr><th class="prop">See also:</th><td> <a href="#Class:Catalog_Record" class="sec-ref"><bdi class="secno">6.5 </bdi>Class: Catalog Record</a>, <a href="#Class:Dataset" class="sec-ref"><bdi class="secno">6.6 </bdi>Class: Dataset</a></td></tr> </tbody></table> <section id="Property:catalog_homepage"><div class="header-wrapper"><h4 id="x6-3-1-property-homepage"><bdi class="secno">6.3.1 </bdi>Property: homepage</h4><a class="self-link" href="#Property:catalog_homepage" aria-label="Permalink for Section 6.3.1"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://xmlns.com/foaf/0.1/homepage"><code>foaf:homepage</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A homepage of the catalog (a public Web document usually available in HTML).</td></tr> <tr><th class="prop">Range:</th><td><a href="http://xmlns.com/foaf/0.1/Document"><code>foaf:Document</code></a></td></tr> <tr><th class="prop">Usage note:</th><td><a href="http://xmlns.com/foaf/0.1/homepage"><code>foaf:homepage</code></a> is an inverse functional property (IFP) which means that it <em class="rfc2119">MUST</em> be unique and precisely identify the Web-page for the resource. This property indicates the canonical Web-page, which might be helpful in cases where there is more than one Web-page about the resource.</td></tr> </tbody></table> </section> <section id="Property:catalog_themes"><div class="header-wrapper"><h4 id="x6-3-2-property-themes"><bdi class="secno">6.3.2 </bdi>Property: themes</h4><a class="self-link" href="#Property:catalog_themes" aria-label="Permalink for Section 6.3.2"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#themeTaxonomy"><code>dcat:themeTaxonomy</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A knowledge organization system (KOS) used to classify the resources documented in the catalog (e.g., datasets and services).</td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Catalog"><code>dcat:Catalog</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Resource"><code>rdfs:Resource</code></a></td></tr> <tr> <th class="prop"> Usage note: </th> <td> It is recommended that the taxonomy is organized in a <a href="https://www.w3.org/2004/02/skos/core#ConceptScheme"><code>skos:ConceptScheme</code></a>, <a href="https://www.w3.org/2004/02/skos/core#Collection"><code>skos:Collection</code></a>, <a href="https://www.w3.org/2002/07/owl#Ontology"><code>owl:Ontology</code></a> or similar, which allows each member to be denoted by an <abbr title="Internationalized Resource Identifier">IRI</abbr> and published as Linked Data. </td> </tr> </tbody></table> </section> <section id="Property:catalog_resource"><div class="header-wrapper"><h4 id="x6-3-3-property-resource"><bdi class="secno">6.3.3 </bdi>Property: resource</h4><a class="self-link" href="#Property:catalog_resource" aria-label="Permalink for Section 6.3.3"></a></div> <div class="note" role="note" id="issue-container-generatedID-7"><div role="heading" class="note-title marker" id="h-note-6" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in this context in DCAT 3. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#resource"><code>dcat:resource</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A resource that is listed in the catalog.</td></tr> <tr><th class="prop">Sub-property of:</th><td><a href="http://purl.org/dc/terms/hasPart"><code>dcterms:hasPart</code></a></td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Catalog"><code>dcat:Catalog</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="#Class:Resource"><code>dcat:Resource</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>This is the most general predicate for membership of a catalog. Use of a more specific sub-property is recommended when available. </td></tr> <tr><th class="prop">See also:</th><td>Sub-properties of <code>dcat:resource</code> in particular <a href="#Property:catalog_dataset"><code>dcat:dataset</code></a>, <a href="#Property:catalog_catalog"><code>dcat:catalog</code></a>, <a href="#Property:catalog_service"><code>dcat:service</code></a>. </td></tr> </tbody></table> </section> <section id="Property:catalog_dataset"><div class="header-wrapper"><h4 id="x6-3-4-property-dataset"><bdi class="secno">6.3.4 </bdi>Property: dataset</h4><a class="self-link" href="#Property:catalog_dataset" aria-label="Permalink for Section 6.3.4"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#dataset"><code>dcat:dataset</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A dataset that is listed in the catalog.</td></tr> <tr><th class="prop">Sub-property of:</th><td><a href="#Property:catalog_resource"><code>dcat:resource</code></a></td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Catalog"><code>dcat:Catalog</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="#Class:Dataset"><code>dcat:Dataset</code></a></td></tr> </tbody></table> </section> <section id="Property:catalog_service"><div class="header-wrapper"><h4 id="x6-3-5-property-service"><bdi class="secno">6.3.5 </bdi>Property: service</h4><a class="self-link" href="#Property:catalog_service" aria-label="Permalink for Section 6.3.5"></a></div> <div class="note" role="note" id="issue-container-generatedID-8"><div role="heading" class="note-title marker" id="h-note-7" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#service"><code>dcat:service</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A service that is listed in the catalog.</td></tr> <tr><th class="prop">Sub-property of:</th><td><a href="#Property:catalog_resource"><code>dcat:resource</code></a></td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Catalog"><code>dcat:Catalog</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="#Class:Data_Service"><code>dcat:DataService</code></a></td></tr> </tbody></table> </section> <section id="Property:catalog_catalog"><div class="header-wrapper"><h4 id="x6-3-6-property-catalog"><bdi class="secno">6.3.6 </bdi>Property: catalog</h4><a class="self-link" href="#Property:catalog_catalog" aria-label="Permalink for Section 6.3.6"></a></div> <div class="note" role="note" id="issue-container-generatedID-9"><div role="heading" class="note-title marker" id="h-note-8" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#catalog"><code>dcat:catalog</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A catalog that is listed in the catalog.</td></tr> <tr><th class="prop">Sub-property of:</th><td><a href="#Property:catalog_resource"><code>dcat:resource</code></a></td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Catalog"><code>dcat:Catalog</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="#Class:Catalog"><code>dcat:Catalog</code></a></td></tr> </tbody></table> </section> <section id="Property:catalog_catalog_record"><div class="header-wrapper"><h4 id="x6-3-7-property-catalog-record"><bdi class="secno">6.3.7 </bdi>Property: catalog record</h4><a class="self-link" href="#Property:catalog_catalog_record" aria-label="Permalink for Section 6.3.7"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#record"><code>dcat:record</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A record describing the registration of a single resource (e.g., a dataset, a data service) that is part of the catalog.</td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Catalog"><code>dcat:Catalog</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="#Class:Catalog_Record"><code>dcat:CatalogRecord</code></a></td></tr> </tbody></table> </section> </section> <section id="Class:Resource"><div class="header-wrapper"><h3 id="x6-4-class-cataloged-resource"><bdi class="secno">6.4 </bdi>Class: Cataloged Resource</h3><a class="self-link" href="#Class:Resource" aria-label="Permalink for Section 6.4"></a></div> <div class="note" role="note" id="issue-container-generatedID-10"><div role="heading" class="note-title marker" id="h-note-9" aria-level="4"><span>Note</span></div><aside class=""> <p> Class added in DCAT 2. </p> </aside></div> <p>The following properties are specific to this class:</p> <ul class="prop-list"> <li><a href="#Property:resource_access_rights">access rights</a></li> <li><a href="#Property:resource_conforms_to">conforms to</a></li> <li><a href="#Property:resource_contact_point">contact point</a></li> <li><a href="#Property:resource_creator">creator</a></li> <li><a href="#Property:resource_description">description</a></li> <li><a href="#Property:resource_has_part">has part</a></li> <li><a href="#Property:resource_has_policy">has policy</a></li> <li><a href="#Property:resource_identifier">identifier</a></li> <li><a href="#Property:resource_is_referenced_by">is referenced by</a></li> <li><a href="#Property:resource_keyword">keyword/tag</a></li> <li><a href="#Property:resource_landing_page">landing page</a></li> <li><a href="#Property:resource_license">license</a></li> <li><a href="#Property:resource_language">language</a></li> <li><a href="#Property:resource_relation">relation</a></li> <li><a href="#Property:resource_rights">rights</a></li> <li><a href="#Property:resource_qualified_relation">qualified relation</a></li> <li><a href="#Property:resource_publisher">publisher</a></li> <li><a href="#Property:resource_release_date">release date</a></li> <li><a href="#Property:resource_theme">theme/category</a></li> <li><a href="#Property:resource_title">title</a></li> <li><a href="#Property:resource_type">type/genre</a></li> <li><a href="#Property:resource_update_date">update/modification date</a></li> <li><a href="#Property:resource_qualified_attribution">qualified attribution</a></li> <li><a href="#Property:resource_has_current_version">has current version</a></li> <li><a href="#Property:resource_has_version">has version</a></li> <li><a href="#Property:resource_previous_version">previous version</a></li> <li><a href="#Property:resource_replaces">replaces</a></li> <li><a href="#Property:resource_status">status</a></li> <li><a href="#Property:resource_version">version</a></li> <li><a href="#Property:resource_version_notes">version notes</a></li> <li><a href="#Property:resource_first">first</a></li> <li><a href="#Property:resource_last">last</a></li> <li><a href="#Property:resource_previous">previous</a></li> </ul> <table class="def"> <tbody><tr> <th>RDF Class:</th> <td><a href="https://www.w3.org/ns/dcat#Resource"><code>dcat:Resource</code></a></td> </tr> <tr> <th class="prop">Definition:</th> <td>Resource published or curated by a single agent.</td> </tr> <tr> <th class="prop">Usage note:</th> <td> <p>The class of all cataloged resources, the super-class of <a href="#Class:Dataset"><code>dcat:Dataset</code></a>, <a href="#Class:Data_Service"><code>dcat:DataService</code></a>, <a href="#Class:Catalog"><code>dcat:Catalog</code></a> and any other member of a <a href="#Class:Catalog"><code>dcat:Catalog</code></a>.</p> <p>This class carries properties common to all cataloged resources, including datasets and data services.</p> <p>The instances of this class <em class="rfc2119">SHOULD</em> be included in a catalog.</p> <p>When describing a resource which is not a <a href="#Class:Dataset"><code>dcat:Dataset</code></a> or <a href="#Class:Data_Service"><code>dcat:DataService</code></a>, it is recommended to create a suitable sub-class of <a href="#Class:Resource"><code>dcat:Resource</code></a>, or use <a href="#Class:Resource"><code>dcat:Resource</code></a> with the <a href="#Property:resource_type"><code>dcterms:type</code></a> property to indicate the specific type.</p> </td> </tr> <tr> <th class="prop">Usage note:</th> <td><a href="#Class:Resource"><code>dcat:Resource</code></a> is an extension point that enables the definition of any kind of catalog. Additional sub-classes may be defined in a DCAT profile or other DCAT application for catalogs of other kinds of resources.</td> </tr> <tr> <th class="prop">See also:</th> <td><a href="#Class:Catalog_Record" class="sec-ref"><bdi class="secno">6.5 </bdi>Class: Catalog Record</a></td> </tr> </tbody></table> <section id="Property:resource_access_rights"><div class="header-wrapper"><h4 id="x6-4-1-property-access-rights"><bdi class="secno">6.4.1 </bdi>Property: access rights</h4><a class="self-link" href="#Property:resource_access_rights" aria-label="Permalink for Section 6.4.1"></a></div> <div class="note" role="note" id="issue-container-generatedID-11"><div role="heading" class="note-title marker" id="h-note-10" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/accessRights"><code>dcterms:accessRights</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Information about who can access the resource or an indication of its security status.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/RightsStatement"><code>dcterms:RightsStatement</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>Information about licenses and rights <em class="rfc2119">MAY</em> be provided for the Resource. See also guidance at <a href="#license-rights" class="sec-ref"><bdi class="secno">9. </bdi>License and rights statements</a>.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:resource_rights" class="sec-ref"><bdi class="secno">6.4.20 </bdi>Property: rights</a></td></tr> </tbody></table> </section> <section id="Property:resource_conforms_to"><div class="header-wrapper"><h4 id="x6-4-2-property-conforms-to"><bdi class="secno">6.4.2 </bdi>Property: conforms to</h4><a class="self-link" href="#Property:resource_conforms_to" aria-label="Permalink for Section 6.4.2"></a></div> <div class="note" role="note" id="issue-container-generatedID-12"><div role="heading" class="note-title marker" id="h-note-11" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/conformsTo"><code>dcterms:conformsTo</code></a></td></tr> <tr><th class="prop">Definition:</th><td>An established standard to which the described resource conforms.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/Standard"><code>dcterms:Standard</code></a> ("A basis for comparison; a reference point against which other things can be evaluated." [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>])</td></tr> <tr><th class="prop">Usage note:</th><td>This property <em class="rfc2119">SHOULD</em> be used to indicate the model, schema, ontology, view or profile that the cataloged resource content conforms to. </td></tr> </tbody></table> </section> <p>For guidance on the use of this property, see <a href="#quality-conformance-statement" class="sec-ref"><bdi class="secno">14.2.1 </bdi>Conformance to a standard</a>.</p> <div class="note" role="note" id="issue-container-generatedID-13"><div role="heading" class="note-title marker" id="h-note-12" aria-level="4"><span>Note</span></div><aside class=""> <p> <a href="http://purl.org/dc/terms/Standard"><code>dcterms:Standard</code></a> is defined in [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] as "A basis for comparison; a reference point against which other things can be evaluated." The target resource is not restricted to formal standards issued by bodies like <abbr title="International Organization for Standardization">ISO</abbr> and <abbr title="World Wide Web Consortium">W3C</abbr>. In this context, it is any resource that specifies one or more aspects of the cataloged resource content, for example schema, semantics, syntax, usage guidelines, file format, or specific serialization. The meaning of conformance is determined by provisions in the target standard. </p> </aside></div> <section id="Property:resource_contact_point"><div class="header-wrapper"><h4 id="x6-4-3-property-contact-point"><bdi class="secno">6.4.3 </bdi>Property: contact point</h4><a class="self-link" href="#Property:resource_contact_point" aria-label="Permalink for Section 6.4.3"></a></div> <div class="note" role="note" id="issue-container-generatedID-14"><div role="heading" class="note-title marker" id="h-note-13" aria-level="5"><span>Note</span></div><aside class=""> <p> In DCAT 1 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>] the domain of <code>dcat:contactPoint</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain was relaxed in DCAT 2. See Issue <a href="https://github.com/w3c/dxwg/issues/95">#95</a>. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#contactPoint"><code>dcat:contactPoint</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Relevant contact information for the cataloged resource. Use of vCard is recommended [<cite><a class="bibref" data-link-type="biblio" href="#bib-vcard-rdf" title="vCard Ontology - for describing People and Organizations">VCARD-RDF</a></cite>]. </td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/TR/vcard-rdf/#d4e1819"><code>vcard:Kind</code></a></td></tr> </tbody></table> </section> <section id="Property:resource_creator"><div class="header-wrapper"><h4 id="x6-4-4-property-creator"><bdi class="secno">6.4.4 </bdi>Property: creator</h4><a class="self-link" href="#Property:resource_creator" aria-label="Permalink for Section 6.4.4"></a></div> <div class="note" role="note" id="issue-container-generatedID-15"><div role="heading" class="note-title marker" id="h-note-14" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2, specifically to address data citation requirements. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/creator"><code>dcterms:creator</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The entity responsible for producing the resource.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://xmlns.com/foaf/0.1/Agent"><code>foaf:Agent</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>Resources of type <a href="http://xmlns.com/foaf/0.1/Agent"><code>foaf:Agent</code></a> are recommended as values for this property.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Class:Organization_Person" class="sec-ref"><bdi class="secno">6.12 </bdi>Class: Organization/Person</a></td></tr> </tbody></table> <div class="note" role="note" id="issue-container-generatedID-16"><div role="heading" class="note-title marker" id="h-note-15" aria-level="5"><span>Note</span></div><aside class=""> <p> This property is added to the <a href="#Class:Resource"><code>dcat:Resource</code></a> class, as the <code>dcat:Dataset</code> super-class. For more details, see <a href="#data-citation" class="sec-ref"><bdi class="secno">13. </bdi>Data citation</a>. </p> <p> The use of the [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] qualified-attribution pattern is described in <a href="#qualified-attribution" class="sec-ref"><bdi class="secno">15.1 </bdi>Relationships between datasets and agents</a>. <code>dcterms:creator</code> corresponds with a general attribution with the role 'creator'. </p> </aside></div> </section> <section id="Property:resource_description"><div class="header-wrapper"><h4 id="x6-4-5-property-description"><bdi class="secno">6.4.5 </bdi>Property: description</h4><a class="self-link" href="#Property:resource_description" aria-label="Permalink for Section 6.4.5"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/description"><code>dcterms:description</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A free-text account of the resource.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a></td></tr> </tbody></table> </section> <section id="Property:resource_title"><div class="header-wrapper"><h4 id="x6-4-6-property-title"><bdi class="secno">6.4.6 </bdi>Property: title</h4><a class="self-link" href="#Property:resource_title" aria-label="Permalink for Section 6.4.6"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/title"><code>dcterms:title</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A name given to the resource.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a></td></tr> </tbody></table> </section> <section id="Property:resource_release_date"><div class="header-wrapper"><h4 id="x6-4-7-property-release-date"><bdi class="secno">6.4.7 </bdi>Property: release date</h4><a class="self-link" href="#Property:resource_release_date" aria-label="Permalink for Section 6.4.7"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/issued"><code>dcterms:issued</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Date of formal issuance (e.g., publication) of the resource.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a> encoded using the relevant <abbr title="International Organization for Standardization">ISO</abbr> 8601 Date and Time compliant string [<cite><a class="bibref" data-link-type="biblio" href="#bib-datetime" title="Date and Time Formats">DATETIME</a></cite>] and typed using the appropriate XML Schema datatype [<cite><a class="bibref" data-link-type="biblio" href="#bib-xmlschema11-2" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">XMLSCHEMA11-2</a></cite>] (<a href="https://www.w3.org/TR/xmlschema11-2/#gYear"><code>xsd:gYear</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#gYearMonth"><code>xsd:gYearMonth</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#date"><code>xsd:date</code></a>, or <a href="https://www.w3.org/TR/xmlschema11-2/#dateTime"><code>xsd:dateTime</code></a>). </td></tr> <tr><th class="prop">Usage note:</th><td>This property <em class="rfc2119">SHOULD</em> be set using the first known date of issuance.</td></tr> <tr><th class="prop">See also:</th><td> <a href="#Property:record_listing_date" class="sec-ref"><bdi class="secno">6.5.3 </bdi>Property: listing date</a> and <a href="#Property:distribution_release_date" class="sec-ref"><bdi class="secno">6.8.3 </bdi>Property: release date</a></td></tr> </tbody></table> </section> <section id="Property:resource_update_date"><div class="header-wrapper"><h4 id="x6-4-8-property-update-modification-date"><bdi class="secno">6.4.8 </bdi>Property: update/modification date</h4><a class="self-link" href="#Property:resource_update_date" aria-label="Permalink for Section 6.4.8"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/modified"><code>dcterms:modified</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Most recent date on which the resource was changed, updated or modified.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a> encoded using the relevant <abbr title="International Organization for Standardization">ISO</abbr> 8601 Date and Time compliant string [<cite><a class="bibref" data-link-type="biblio" href="#bib-datetime" title="Date and Time Formats">DATETIME</a></cite>] and typed using the appropriate XML Schema datatype [<cite><a class="bibref" data-link-type="biblio" href="#bib-xmlschema11-2" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">XMLSCHEMA11-2</a></cite>] (<a href="https://www.w3.org/TR/xmlschema11-2/#gYear"><code>xsd:gYear</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#gYearMonth"><code>xsd:gYearMonth</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#date"><code>xsd:date</code></a>, or <a href="https://www.w3.org/TR/xmlschema11-2/#dateTime"><code>xsd:dateTime</code></a>). </td></tr> <tr><th class="prop">Usage note:</th><td>The value of this property indicates a change to the actual resource, not a change to the catalog record. An absent value <em class="rfc2119">MAY</em> indicate that the resource has never changed after its initial publication, or that the date of last modification is not known, or that the resource is continuously updated.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:dataset_frequency" class="sec-ref"><bdi class="secno">6.6.2 </bdi>Property: frequency</a>, <a href="#Property:record_update_date" class="sec-ref"><bdi class="secno">6.5.4 </bdi>Property: update/modification date</a> and <a href="#Property:distribution_update_date" class="sec-ref"><bdi class="secno">6.8.4 </bdi>Property: update/modification date</a></td></tr> </tbody></table> </section> <section id="Property:resource_language"><div class="header-wrapper"><h4 id="x6-4-9-property-language"><bdi class="secno">6.4.9 </bdi>Property: language</h4><a class="self-link" href="#Property:resource_language" aria-label="Permalink for Section 6.4.9"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/language"><code>dcterms:language</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A language of the resource. This refers to the natural language used for textual metadata (i.e., titles, descriptions, etc.) of a cataloged resource (i.e., dataset or service) or the textual values of a dataset distribution</td></tr> <tr><th class="prop">Range:</th><td> <p><a href="http://purl.org/dc/terms/LinguisticSystem"><code>dcterms:LinguisticSystem</code></a></p> <p>Resources defined by the Library of Congress (<a href="http://id.loc.gov/vocabulary/iso639-1.html"><abbr title="International Organization for Standardization">ISO</abbr> 639-1</a>, <a href="http://id.loc.gov/vocabulary/iso639-2.html"><abbr title="International Organization for Standardization">ISO</abbr> 639-2</a>) <em class="rfc2119">SHOULD</em> be used.</p> <p>If a <abbr title="International Organization for Standardization">ISO</abbr> 639-1 (two-letter) code is defined for language, then its corresponding <abbr title="Internationalized Resource Identifier">IRI</abbr> <em class="rfc2119">SHOULD</em> be used; if no <abbr title="International Organization for Standardization">ISO</abbr> 639-1 code is defined, then <abbr title="Internationalized Resource Identifier">IRI</abbr> corresponding to the <abbr title="International Organization for Standardization">ISO</abbr> 639-2 (three-letter) code <em class="rfc2119">SHOULD</em> be used.</p> </td></tr> <tr><th class="prop">Usage note:</th><td>Repeat this property if the resource is available in multiple languages.</td></tr> <tr><th class="prop">Usage note:</th><td>The value(s) provided for members of a catalog (i.e., dataset or service) override the value(s) provided for the catalog if they conflict.</td></tr> <tr><th class="prop">Usage note:</th><td>If representations of a dataset are available for each language separately, define an instance of <code>dcat:Distribution</code> for each language and describe the specific language of each distribution using <code>dcterms:language</code> (i.e., the dataset will have multiple <code>dcterms:language</code> values and each distribution will have just one as the value of its <code>dcterms:language</code> property). In case of multilingual distributions, the distributions will have multiple <code>dcterms:language</code> values.</td></tr> </tbody></table> <div class="note" role="note" id="issue-container-generatedID-17"><div role="heading" class="note-title marker" id="h-note-16" aria-level="5"><span>Note</span></div><aside class=""> Requirements for identification of natural language in linked data specifications are evolving. Many applications use [<cite><a class="bibref" data-link-type="biblio" href="#bib-bcp47" title="Tags for Identifying Languages">BCP47</a></cite>] language tags for this purpose. <abbr title="International Organization for Standardization">ISO</abbr> 639 also provides additional codes in <abbr title="International Organization for Standardization">ISO</abbr> 639-3 which might be required for some uses. </aside></div> </section> <section id="Property:resource_publisher"><div class="header-wrapper"><h4 id="x6-4-10-property-publisher"><bdi class="secno">6.4.10 </bdi>Property: publisher</h4><a class="self-link" href="#Property:resource_publisher" aria-label="Permalink for Section 6.4.10"></a></div> <div class="note" role="note" id="issue-container-generatedID-18"><div role="heading" class="note-title marker" id="h-note-17" aria-level="5"><span>Note</span></div><aside class=""> <p> The use of the [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] qualified-attribution pattern is described in <a href="#qualified-attribution" class="sec-ref"><bdi class="secno">15.1 </bdi>Relationships between datasets and agents</a>. <code>dcterms:publisher</code> corresponds with a general attribution with the role 'publisher'. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/publisher"><code>dcterms:publisher</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The entity responsible for making the resource available.</td></tr> <tr><th class="prop">Usage note:</th><td>Resources of type <a href="http://xmlns.com/foaf/0.1/Agent"><code>foaf:Agent</code></a> are recommended as values for this property.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Class:Organization_Person" class="sec-ref"><bdi class="secno">6.12 </bdi>Class: Organization/Person</a></td></tr> </tbody></table> </section> <section id="Property:resource_identifier"><div class="header-wrapper"><h4 id="x6-4-11-property-identifier"><bdi class="secno">6.4.11 </bdi>Property: identifier</h4><a class="self-link" href="#Property:resource_identifier" aria-label="Permalink for Section 6.4.11"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/identifier"><code>dcterms:identifier</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A unique identifier of the resource being described or cataloged.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>The identifier might be used as part of the <abbr title="Internationalized Resource Identifier">IRI</abbr> of the resource, but still having it represented explicitly is useful.</td></tr> <tr><th class="prop">Usage note:</th><td>The identifier is a text string which is assigned to the resource to provide an unambiguous reference within a particular context.</td></tr> </tbody></table> </section> <section id="Property:resource_theme"><div class="header-wrapper"><h4 id="x6-4-12-property-theme-category"><bdi class="secno">6.4.12 </bdi>Property: theme/category</h4><a class="self-link" href="#Property:resource_theme" aria-label="Permalink for Section 6.4.12"></a></div> <div class="note" role="note" id="issue-container-generatedID-19"><div role="heading" class="note-title marker" id="h-note-18" aria-level="5"><span>Note</span></div><aside class=""> <p> In DCAT 1 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>] the domain of <code>dcat:theme</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain was relaxed in DCAT 2. See Issue <a href="https://github.com/w3c/dxwg/issues/123">#123</a>. </p> <p> DCAT 3 maintains the same expectation as DCAT 2 for the use of the property <code>dcat:theme</code>. DCAT 3 defines <code>dcat:theme</code> as an OWL object property and drops its range to make the formalization of the property more consistent with the expected use. In particular, the change intends to prevent that each entity used as object of <code>dcat:theme</code> is automatically inferred as <code>skos:Concept</code>. See issue <a href="https://github.com/w3c/dxwg/issues/1364">#1364</a>. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#theme"><code>dcat:theme</code></a></td></tr> <tr><th>Type:</th><td><a href="https://www.w3.org/2002/07/owl#ObjectProperty"><code title="http://www.w3.org/2002/07/owl#ObjectProperty">owl:ObjectProperty</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A main category of the resource. A resource can have multiple themes.</td></tr> <tr><th class="prop">Sub-property of:</th><td><a href="http://purl.org/dc/terms/subject"><code>dcterms:subject</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>The set of themes used to categorize the resources are organized in a <a href="https://www.w3.org/2004/02/skos/core#ConceptScheme"><code>skos:ConceptScheme</code></a>, <a href="https://www.w3.org/2009/08/skos-reference/skos.html#Collection"><code>skos:Collection</code></a>, <a href="https://www.w3.org/2002/07/owl#Ontology"><code>owl:Ontology</code></a> or similar, describing all the categories and their relations in the catalog.</td></tr> <tr><th>See also:</th><td><a href="#Property:catalog_themes" class="sec-ref"><bdi class="secno">6.3.2 </bdi>Property: themes</a></td></tr> </tbody></table> </section> <section id="Property:resource_type"><div class="header-wrapper"><h4 id="x6-4-13-property-type-genre"><bdi class="secno">6.4.13 </bdi>Property: type/genre</h4><a class="self-link" href="#Property:resource_type" aria-label="Permalink for Section 6.4.13"></a></div> <div class="note" role="note" id="issue-container-generatedID-20"><div role="heading" class="note-title marker" id="h-note-19" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. See Issue <a href="https://github.com/w3c/dxwg/issues/64">#64</a>. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/type"><code>dcterms:type</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The nature or genre of the resource.</td></tr> <tr><th class="prop">Sub-property of:</th><td><a href="http://purl.org/dc/elements/1.1/type"><code>dc:type</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Class"><code>rdfs:Class</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>The value <em class="rfc2119">SHOULD</em> be taken from a well governed and broadly recognised controlled vocabulary, such as: <ol> <li><a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#section-7">DCMI Type vocabulary</a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>]</li> <li>[<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115-1" title="Geographic information -- Metadata -- Part 1: Fundamentals">ISO-19115-1</a></cite>] <a href="https://standards.iso.org/iso/19115/resources/Codelists/gml/MD_ScopeCode.xml">scope codes</a></li> <li><a href="https://schema.datacite.org/meta/kernel-4.1/include/datacite-resourceType-v4.1.xsd">Datacite resource types</a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-datacite" title="DataCite Metadata Schema">DataCite</a></cite>]</li> <li>PARSE.Insight content-types used by <a href="https://www.re3data.org/">re3data.org</a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-re3data-schema" title="Metadata Schema for the Description of Research Data Repositories: version 3">RE3DATA-SCHEMA</a></cite>] (see item 15 contentType)</li> <li><a href="http://id.loc.gov/vocabulary/marcgt.html">MARC intellectual resource types</a></li> </ol> Some members of these controlled vocabularies are not strictly suitable for datasets or data services (e.g., DCMI Type <i>Event</i>, <i>PhysicalObject</i>; [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115-1" title="Geographic information -- Metadata -- Part 1: Fundamentals">ISO-19115-1</a></cite>] <i>CollectionHardware</i>, <i>CollectionSession</i>, <i>Initiative</i>, <i>Sample</i>, <i>Repository</i>), but might be used in the context of other kinds of catalogs defined in DCAT profiles or applications. </td></tr> <tr><th class="prop">Usage note:</th><td>To describe the file format, physical medium, or dimensions of the resource, use the <a href="http://purl.org/dc/terms/format"><code>dcterms:format</code></a> element.</td></tr> </tbody></table> </section> <section id="Property:resource_relation"><div class="header-wrapper"><h4 id="x6-4-14-property-relation"><bdi class="secno">6.4.14 </bdi>Property: relation</h4><a class="self-link" href="#Property:resource_relation" aria-label="Permalink for Section 6.4.14"></a></div> <div class="note" role="note" id="issue-container-generatedID-21"><div role="heading" class="note-title marker" id="h-note-20" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/relation"><code>dcterms:relation</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A resource with an unspecified relationship to the cataloged resource.</td></tr> <tr><th class="prop">Usage note:</th><td><a href="http://purl.org/dc/terms/relation"><code>dcterms:relation</code></a> <em class="rfc2119">SHOULD</em> be used where the nature of the relationship between a cataloged resource and related resources is not known. A more specific sub-property <em class="rfc2119">SHOULD</em> be used if the nature of the relationship of the link is known. The property <a href="#Property:dataset_distribution"><code>dcat:distribution</code></a> <em class="rfc2119">SHOULD</em> be used to link from a <a href="#Class:Dataset"><code>dcat:Dataset</code></a> to a representation of the dataset, described as a <a href="#Class:Distribution"><code>dcat:Distribution</code></a></td></tr> <tr><th class="prop">See also:</th><td>Sub-properties of <code>dcterms:relation</code> in particular <a href="#Property:dataset_distribution"><code>dcat:distribution</code></a>, <a href="http://purl.org/dc/terms/hasPart"><code>dcterms:hasPart</code></a>, (and its sub-properties <a href="#Property:catalog_resource"><code>dcat:resource</code></a>, <a href="#Property:catalog_catalog"><code>dcat:catalog</code></a>, <a href="#Property:catalog_dataset"><code>dcat:dataset</code></a>, <a href="#Property:catalog_service"><code>dcat:service</code></a> ), <a href="http://purl.org/dc/terms/isPartOf"><code>dcterms:isPartOf</code></a>, <a href="http://purl.org/dc/terms/conformsTo"><code>dcterms:conformsTo</code></a>, <a href="http://purl.org/dc/terms/isFormatOf"><code>dcterms:isFormatOf</code></a>, <a href="http://purl.org/dc/terms/hasFormat"><code>dcterms:hasFormat</code></a>, <a href="http://purl.org/dc/terms/isVersionOf"><code>dcterms:isVersionOf</code></a>, <a href="http://purl.org/dc/terms/hasVersion"><code>dcterms:hasVersion</code></a> (and its sub-property <a href="#Property:resource_has_version"><code>dcat:hasVersion</code></a> ), <a href="http://purl.org/dc/terms/replaces"><code>dcterms:replaces</code></a>, <a href="http://purl.org/dc/terms/isReplacedBy"><code>dcterms:isReplacedBy</code></a>, <a href="http://purl.org/dc/terms/references"><code>dcterms:references</code></a>, <a href="http://purl.org/dc/terms/isReferencedBy"><code>dcterms:isReferencedBy</code></a>, <a href="http://purl.org/dc/terms/requires"><code>dcterms:requires</code></a>, <a href="http://purl.org/dc/terms/isRequiredBy"><code>dcterms:isRequiredBy</code></a></td> </tr> </tbody></table> <p> Many existing and legacy catalogs do not distinguish between dataset components, representations, documentation, schemata and other resources that are lumped together as part of a dataset. <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/relation"><code title="http://purl.org/dc/terms/relation">dcterms:relation</code></a> is a super-property of a number of more specific properties which express more precise relationships, so use of <code>dcterms:relation</code> is not inconsistent with a subsequent reclassification with more specific semantics, though the more specialized sub-properties <em class="rfc2119">SHOULD</em> be used to link a dataset to component and supplementary resources if possible. </p> </section> <section id="Property:resource_qualified_relation"><div class="header-wrapper"><h4 id="x6-4-15-property-qualified-relation"><bdi class="secno">6.4.15 </bdi>Property: qualified relation</h4><a class="self-link" href="#Property:resource_qualified_relation" aria-label="Permalink for Section 6.4.15"></a></div> <div class="note" role="note" id="issue-container-generatedID-22"><div role="heading" class="note-title marker" id="h-note-21" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#qualifiedRelation"><code>dcat:qualifiedRelation</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Link to a description of a relationship with another resource</td></tr> <tr><th class="prop">Sub-property of:</th><td><a href="https://www.w3.org/TR/prov-o/#qualifiedInfluence"><code>prov:qualifiedInfluence</code></a></td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Resource"><code>dcat:Resource</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="#Class:Relationship"><code>dcat:Relationship</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>Used to link to another resource where the nature of the relationship is known but does not match one of the standard [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] properties (<a href="http://purl.org/dc/terms/hasPart"><code>dcterms:hasPart</code></a>, <a href="http://purl.org/dc/terms/isPartOf"><code>dcterms:isPartOf</code></a>, <a href="http://purl.org/dc/terms/conformsTo"><code>dcterms:conformsTo</code></a>, <a href="http://purl.org/dc/terms/isFormatOf"><code>dcterms:isFormatOf</code></a>, <a href="http://purl.org/dc/terms/hasFormat"><code>dcterms:hasFormat</code></a>, <a href="http://purl.org/dc/terms/isVersionOf"><code>dcterms:isVersionOf</code></a>, <a href="http://purl.org/dc/terms/hasVersion"><code>dcterms:hasVersion</code></a>, <a href="http://purl.org/dc/terms/replaces"><code>dcterms:replaces</code></a>, <a href="http://purl.org/dc/terms/isReplacedBy"><code>dcterms:isReplacedBy</code></a>, <a href="http://purl.org/dc/terms/references"><code>dcterms:references</code></a>, <a href="http://purl.org/dc/terms/isReferencedBy"><code>dcterms:isReferencedBy</code></a>, <a href="http://purl.org/dc/terms/requires"><code>dcterms:requires</code></a>, <a href="http://purl.org/dc/terms/isRequiredBy"><code>dcterms:isRequiredBy</code></a>) or [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] properties (<a href="https://www.w3.org/TR/prov-o/#wasDerivedFrom"><code>prov:wasDerivedFrom</code></a>, <a href="https://www.w3.org/TR/prov-o/#wasInfluencedBy"><code>prov:wasInfluencedBy</code></a>, <a href="https://www.w3.org/TR/prov-o/#wasQuotedFrom"><code>prov:wasQuotedFrom</code></a>, <a href="https://www.w3.org/TR/prov-o/#wasRevisionOf"><code>prov:wasRevisionOf</code></a>, <a href="https://www.w3.org/TR/prov-o/#hadPrimarySource"><code>prov:hadPrimarySource</code></a>, <a href="https://www.w3.org/TR/prov-o/#alternateOf"><code>prov:alternateOf</code></a>, <a href="https://www.w3.org/TR/prov-o/#specializationOf"><code>prov:specializationOf</code></a>). </td> </tr> </tbody></table> <p> This DCAT property follows the common qualified relation pattern described in <a href="#qualified-forms" class="sec-ref"><bdi class="secno">15. </bdi>Qualified relations</a> . </p> <div class="note" role="note" id="issue-container-generatedID-23"><div role="heading" class="note-title marker" id="h-note-22" aria-level="5"><span>Note</span></div><aside class=""> <p> Since this property is a sub-property of <a href="https://www.w3.org/TR/prov-o/#qualifiedInfluence"><code>prov:qualifiedInfluence</code></a>, use of this property on an individual entails that the context resource is a member of the class <a href="https://www.w3.org/TR/prov-o/#Entity"><code>prov:Entity</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] . </p> </aside></div> </section> <section id="Property:resource_keyword"><div class="header-wrapper"><h4 id="x6-4-16-property-keyword-tag"><bdi class="secno">6.4.16 </bdi>Property: keyword/tag</h4><a class="self-link" href="#Property:resource_keyword" aria-label="Permalink for Section 6.4.16"></a></div> <div class="note" role="note" id="issue-container-generatedID-24"><div role="heading" class="note-title marker" id="h-note-23" aria-level="5"><span>Note</span></div><aside class=""> <p> In DCAT 1 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>] the domain of <code>dcat:keyword</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain was relaxed in DCAT 2 - see Issue <a href="https://github.com/w3c/dxwg/issues/121">#121</a>. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#keyword"><code>dcat:keyword</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A keyword or tag describing the resource.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a></td></tr> </tbody></table> </section> <section id="Property:resource_landing_page"><div class="header-wrapper"><h4 id="x6-4-17-property-landing-page"><bdi class="secno">6.4.17 </bdi>Property: landing page</h4><a class="self-link" href="#Property:resource_landing_page" aria-label="Permalink for Section 6.4.17"></a></div> <div class="note" role="note" id="issue-container-generatedID-25"><div role="heading" class="note-title marker" id="h-note-24" aria-level="5"><span>Note</span></div><aside class=""> <p> In DCAT 1 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>] the domain of <code>dcat:landingPage</code> was <code>dcat:Dataset</code>, which limited use of this property in other contexts. The domain was relaxed in DCAT 2 - see Issue <a href="https://github.com/w3c/dxwg/issues/122">#122</a>. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#landingPage"><code>dcat:landingPage</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A Web page that can be navigated to in a Web browser to gain access to the catalog, a dataset, its distributions and/or additional information.</td></tr> <tr><th class="prop">Sub-property of:</th><td><a href="http://xmlns.com/foaf/0.1/page"><code>foaf:page</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="http://xmlns.com/foaf/0.1/Document"><code>foaf:Document</code></a></td></tr> <tr><th class="prop">Usage note:</th><td> If the distribution(s) are accessible only through a landing page (i.e., direct download URLs are not known), then the landing page link <em class="rfc2119">SHOULD</em> be duplicated as <code>dcat:accessURL</code> on a distribution. (see <a href="#example-landing-page" class="sec-ref"><bdi class="secno">5.7 </bdi>Dataset available only behind some Web page</a>) </td></tr> </tbody></table> </section> <section id="Property:resource_qualified_attribution"><div class="header-wrapper"><h4 id="x6-4-18-property-qualified-attribution"><bdi class="secno">6.4.18 </bdi>Property: qualified attribution</h4><a class="self-link" href="#Property:resource_qualified_attribution" aria-label="Permalink for Section 6.4.18"></a></div> <div class="note" role="note" id="issue-container-generatedID-26"><div role="heading" class="note-title marker" id="h-note-25" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in this context in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/TR/prov-o/#qualifiedAttribution"><code>prov:qualifiedAttribution</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Link to an Agent having some form of responsibility for the resource</td></tr> <tr><th class="prop">Sub-property of:</th><td><a href="https://www.w3.org/TR/prov-o/#qualifiedInfluence"><code>prov:qualifiedInfluence</code></a></td></tr> <tr><th class="prop">Domain:</th><td><a href="https://www.w3.org/TR/prov-o/#Entity"><code>prov:Entity</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/TR/prov-o/#Attribution"><code>prov:Attribution</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>Used to link to an Agent where the nature of the relationship is known but does not match one of the standard [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] properties (<a href="http://purl.org/dc/terms/creator"><code>dcterms:creator</code></a>, <a href="http://purl.org/dc/terms/creator"><code>dcterms:publisher</code></a>). Use <code>dcat:hadRole</code> on the <a href="https://www.w3.org/TR/prov-o/#Attribution"><code>prov:Attribution</code></a> to capture the responsibility of the Agent with respect to the Resource. See <a href="#qualified-attribution" class="sec-ref"><bdi class="secno">15.1 </bdi>Relationships between datasets and agents</a> for usage examples.</td></tr> </tbody></table> <p> This DCAT property follows the common qualified relation pattern described in <a href="#qualified-forms" class="sec-ref"><bdi class="secno">15. </bdi>Qualified relations</a> . </p> <div class="note" role="note" id="issue-container-generatedID-27"><div role="heading" class="note-title marker" id="h-note-26" aria-level="5"><span>Note</span></div><aside class=""> <p> Use of this property on an individual entails that the context resource is a member of the class <a href="https://www.w3.org/TR/prov-o/#Entity"><code>prov:Entity</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>]. </p> </aside></div> </section> <section id="Property:resource_license"><div class="header-wrapper"><h4 id="x6-4-19-property-license"><bdi class="secno">6.4.19 </bdi>Property: license</h4><a class="self-link" href="#Property:resource_license" aria-label="Permalink for Section 6.4.19"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/license"><code>dcterms:license</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A legal document under which the resource is made available.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/LicenseDocument"><code>dcterms:LicenseDocument</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>Information about licenses and rights <em class="rfc2119">MAY</em> be provided for the Resource. See also guidance at <a href="#license-rights" class="sec-ref"><bdi class="secno">9. </bdi>License and rights statements</a>.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:resource_rights" class="sec-ref"><bdi class="secno">6.4.20 </bdi>Property: rights</a>, <a href="#Property:distribution_license" class="sec-ref"><bdi class="secno">6.8.5 </bdi>Property: license</a></td></tr> </tbody></table> </section> <section id="Property:resource_rights"><div class="header-wrapper"><h4 id="x6-4-20-property-rights"><bdi class="secno">6.4.20 </bdi>Property: rights</h4><a class="self-link" href="#Property:resource_rights" aria-label="Permalink for Section 6.4.20"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/rights"><code>dcterms:rights</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A statement that concerns all rights not addressed with <a href="#Property:resource_license"><code>dcterms:license</code></a> or <a href="#Property:resource_access_rights"><code>dcterms:accessRights</code></a>, such as copyright statements.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/RightsStatement"><code>dcterms:RightsStatement</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>Information about licenses and rights <em class="rfc2119">MAY</em> be provided for the Resource. See also guidance at <a href="#license-rights" class="sec-ref"><bdi class="secno">9. </bdi>License and rights statements</a>.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:resource_license" class="sec-ref"><bdi class="secno">6.4.19 </bdi>Property: license</a>, <a href="#Property:distribution_rights" class="sec-ref"><bdi class="secno">6.8.7 </bdi>Property: rights</a>, <a href="#Property:resource_access_rights" class="sec-ref"><bdi class="secno">6.4.1 </bdi>Property: access rights</a></td></tr> </tbody></table> </section> <section id="Property:resource_has_part"><div class="header-wrapper"><h4 id="x6-4-21-property-has-part"><bdi class="secno">6.4.21 </bdi>Property: has part</h4><a class="self-link" href="#Property:resource_has_part" aria-label="Permalink for Section 6.4.21"></a></div> <div class="note" role="note" id="issue-container-generatedID-28"><div role="heading" class="note-title marker" id="h-note-27" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in this context in DCAT 3. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/hasPart"><code>dcterms:hasPart</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A related resource that is included either physically or logically in the described resource.</td></tr> </tbody></table> </section> <section id="Property:resource_has_policy"><div class="header-wrapper"><h4 id="x6-4-22-property-has-policy"><bdi class="secno">6.4.22 </bdi>Property: has policy</h4><a class="self-link" href="#Property:resource_has_policy" aria-label="Permalink for Section 6.4.22"></a></div> <div class="note" role="note" id="issue-container-generatedID-29"><div role="heading" class="note-title marker" id="h-note-28" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/TR/odrl-vocab/#term-hasPolicy"><code>odrl:hasPolicy</code></a></td></tr> <tr><th class="prop">Definition:</th><td>An <abbr title="Open Digital Rights Language">ODRL</abbr> conformant policy expressing the rights associated with the resource.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/TR/odrl-vocab/#term-Policy"><code>odrl:Policy</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>Information about rights expressed as an <abbr title="Open Digital Rights Language">ODRL</abbr> policy [<cite><a class="bibref" data-link-type="biblio" href="#bib-odrl-model" title="ODRL Information Model 2.2">ODRL-MODEL</a></cite>] using the <abbr title="Open Digital Rights Language">ODRL</abbr> vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-odrl-vocab" title="ODRL Vocabulary & Expression 2.2">ODRL-VOCAB</a></cite>] <em class="rfc2119">MAY</em> be provided for the resource. See also guidance at <a href="#license-rights" class="sec-ref"><bdi class="secno">9. </bdi>License and rights statements</a>.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:resource_license" class="sec-ref"><bdi class="secno">6.4.19 </bdi>Property: license</a>, <a href="#Property:resource_access_rights" class="sec-ref"><bdi class="secno">6.4.1 </bdi>Property: access rights</a>, <a href="#Property:resource_rights" class="sec-ref"><bdi class="secno">6.4.20 </bdi>Property: rights</a></td></tr> </tbody></table> </section> <section id="Property:resource_is_referenced_by"><div class="header-wrapper"><h4 id="x6-4-23-property-is-referenced-by"><bdi class="secno">6.4.23 </bdi>Property: is referenced by</h4><a class="self-link" href="#Property:resource_is_referenced_by" aria-label="Permalink for Section 6.4.23"></a></div> <div class="note" role="note" id="issue-container-generatedID-30"><div role="heading" class="note-title marker" id="h-note-29" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/isReferencedBy"><code>dcterms:isReferencedBy</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A related resource, such as a publication, that references, cites, or otherwise points to the cataloged resource.</td></tr> <tr><th class="prop">Usage note:</th><td>In relation to the use case of data citation, when the cataloged resource is a dataset, the <code>dcterms:isReferencedBy</code> property allows to relate the dataset to the resources (such as scholarly publications) that cite or point to the dataset. Multiple <code>dcterms:isReferencedBy</code> properties can be used to indicate the dataset has been referenced by multiple publications, or other resources.</td> </tr> <tr><th class="prop">Usage note:</th><td>This property is used to associate a resource with the resource (of type <code>dcat:Resource</code>) in question. For other relations to resources not covered with this property, the more generic property <a href="#Property:resource_qualified_relation"><code>dcat:qualifiedRelation</code></a> can be used. See also <a href="#qualified-forms" class="sec-ref"><bdi class="secno">15. </bdi>Qualified relations</a>.</td></tr> </tbody></table> <p>For examples on the use of this property, see <a href="#examples-dataset-publication" class="sec-ref"><bdi class="secno">C.3 </bdi>Link datasets and publications</a>.</p> </section> <section id="Property:resource_previous_version"><div class="header-wrapper"><h4 id="x6-4-24-property-previous-version"><bdi class="secno">6.4.24 </bdi>Property: previous version</h4><a class="self-link" href="#Property:resource_previous_version" aria-label="Permalink for Section 6.4.24"></a></div> <div class="note" role="note" id="issue-container-generatedID-31"><div role="heading" class="note-title marker" id="h-note-30" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#previousVersion"><code>dcat:previousVersion</code></a></td></tr> <tr> <th class="prop">Definition:</th> <td>The previous version of a resource in a lineage [<cite><a class="bibref" data-link-type="biblio" href="#bib-pav" title="PAV - Provenance, Authoring and Versioning. Version 2.3.1">PAV</a></cite>].</td> </tr> <tr> <th class="prop">Equivalent property:</th> <td><a href="https://pav-ontology.github.io/pav/#d4e459"><code title="http://purl.org/pav/previousVersion">pav:previousVersion</code></a></td> </tr> <tr> <th class="prop">Sub-property of:</th> <td><a href="https://www.w3.org/TR/prov-o/#wasRevisionOf"><code title="http://www.w3.org/ns/prov#wasRevisionOf">prov:wasRevisionOf</code></a></td> </tr> <tr> <th class="prop">Usage note:</th> <td> <p>This property is meant to be used to specify a version chain, consisting of snapshots of a resource.</p> <p>The notion of version used by this property is limited to versions resulting from revisions occurring to a resource as part of its life-cycle. One of the typical cases here is representing the history of the versions of a dataset that have been released over time.</p> </td> </tr> <tr> <th class="prop">See also:</th> <td> <a href="#Property:resource_has_current_version" class="sec-ref"><bdi class="secno">6.4.26 </bdi>Property: current version</a>, <a href="#Property:resource_has_version" class="sec-ref"><bdi class="secno">6.4.25 </bdi>Property: has version</a>, <a href="#Property:resource_release_date" class="sec-ref"><bdi class="secno">6.4.7 </bdi>Property: release date</a>, <a href="#Property:resource_replaces" class="sec-ref"><bdi class="secno">6.4.27 </bdi>Property: replaces</a>, <a href="#Property:resource_status" class="sec-ref"><bdi class="secno">6.4.30 </bdi>Property: status</a>, <a href="#Property:resource_version" class="sec-ref"><bdi class="secno">6.4.28 </bdi>Property: version</a>, <a href="#Property:resource_version_notes" class="sec-ref"><bdi class="secno">6.4.29 </bdi>Property: version notes</a>. </td> </tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#version-history" class="sec-ref"><bdi class="secno">11.1.1 </bdi>Version chains and hierarchies</a>.</p> </section> <section id="Property:resource_has_version"><div class="header-wrapper"><h4 id="x6-4-25-property-has-version"><bdi class="secno">6.4.25 </bdi>Property: has version</h4><a class="self-link" href="#Property:resource_has_version" aria-label="Permalink for Section 6.4.25"></a></div> <div class="note" role="note" id="issue-container-generatedID-32"><div role="heading" class="note-title marker" id="h-note-31" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#hasVersion"><code>dcat:hasVersion</code></a></td></tr> <tr> <th class="prop">Definition:</th> <td>This resource has a more specific, versioned resource [<cite><a class="bibref" data-link-type="biblio" href="#bib-pav" title="PAV - Provenance, Authoring and Versioning. Version 2.3.1">PAV</a></cite>].</td> </tr> <tr> <th class="prop">Equivalent property:</th> <td><a href="https://pav-ontology.github.io/pav/#d4e395"><code title="http://purl.org/pav/hasVersion">pav:hasVersion</code></a></td> </tr> <tr> <th class="prop">Sub-property of:</th> <td><a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/hasVersion"><code title="http://purl.org/dc/terms/hasVersion">dcterms:hasVersion</code></a></td> </tr> <tr> <th class="prop">Sub-property of:</th> <td><a href="https://www.w3.org/TR/prov-o/#inverse-names-table"><code title="http://www.w3.org/ns/prov#generalizationOf">prov:generalizationOf</code></a></td> </tr> <tr> <th class="prop">Usage note:</th> <td> <p>This property is intended for relating a non-versioned or abstract resource to several versioned resources, e.g., snapshots [<cite><a class="bibref" data-link-type="biblio" href="#bib-pav" title="PAV - Provenance, Authoring and Versioning. Version 2.3.1">PAV</a></cite>].</p> <p>The notion of version used by this property is limited to versions resulting from revisions occurring to a resource as part of its life-cycle. Therefore, its semantics is more specific than its super-property <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/hasVersion"><code title="http://purl.org/dc/terms/hasVersion">dcterms:hasVersion</code></a>, which makes use of a broader notion of version, including editions and adaptations.</p> </td> </tr> <tr> <th class="prop">See also:</th> <td> <a href="#Property:resource_has_current_version" class="sec-ref"><bdi class="secno">6.4.26 </bdi>Property: current version</a>, <a href="#Property:resource_previous_version" class="sec-ref"><bdi class="secno">6.4.24 </bdi>Property: previous version</a>, <a href="#Property:resource_release_date" class="sec-ref"><bdi class="secno">6.4.7 </bdi>Property: release date</a>, <a href="#Property:resource_replaces" class="sec-ref"><bdi class="secno">6.4.27 </bdi>Property: replaces</a>, <a href="#Property:resource_status" class="sec-ref"><bdi class="secno">6.4.30 </bdi>Property: status</a>, <a href="#Property:resource_version" class="sec-ref"><bdi class="secno">6.4.28 </bdi>Property: version</a>, <a href="#Property:resource_version_notes" class="sec-ref"><bdi class="secno">6.4.29 </bdi>Property: version notes</a>. </td> </tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#version-history" class="sec-ref"><bdi class="secno">11.1.1 </bdi>Version chains and hierarchies</a>.</p> </section> <section id="Property:resource_has_current_version"><div class="header-wrapper"><h4 id="x6-4-26-property-current-version"><bdi class="secno">6.4.26 </bdi>Property: current version</h4><a class="self-link" href="#Property:resource_has_current_version" aria-label="Permalink for Section 6.4.26"></a></div> <div class="note" role="note" id="issue-container-generatedID-33"><div role="heading" class="note-title marker" id="h-note-32" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#hasCurrentVersion"><code>dcat:hasCurrentVersion</code></a></td></tr> <tr> <th class="prop">Definition:</th> <td>This resource has a more specific, versioned resource with equivalent content [<cite><a class="bibref" data-link-type="biblio" href="#bib-pav" title="PAV - Provenance, Authoring and Versioning. Version 2.3.1">PAV</a></cite>].</td> </tr> <tr> <th class="prop">Equivalent property:</th> <td><a href="https://pav-ontology.github.io/pav/#d4e359"><code title="http://purl.org/pav/hasCurrentVersion">pav:hasCurrentVersion</code></a></td> </tr> <tr> <th class="prop">Sub-property of:</th> <td><a href="https://pav-ontology.github.io/pav/#d4e395"><code title="http://purl.org/pav/hasVersion">pav:hasVersion</code></a></td> </tr> <tr> <th class="prop">Usage note:</th> <td> <p>This property is intended for relating a non-versioned or abstract resource to a single snapshot that can be used as a permalink to indicate the current version of the content [<cite><a class="bibref" data-link-type="biblio" href="#bib-pav" title="PAV - Provenance, Authoring and Versioning. Version 2.3.1">PAV</a></cite>].</p> <p>The notion of version used by this property is limited to versions resulting from revisions occurring to a resource as part of its life-cycle.</p> </td> </tr> <tr> <th class="prop">See also:</th> <td> <a href="#Property:resource_has_version" class="sec-ref"><bdi class="secno">6.4.25 </bdi>Property: has version</a>, <a href="#Property:resource_previous_version" class="sec-ref"><bdi class="secno">6.4.24 </bdi>Property: previous version</a>, <a href="#Property:resource_release_date" class="sec-ref"><bdi class="secno">6.4.7 </bdi>Property: release date</a>, <a href="#Property:resource_replaces" class="sec-ref"><bdi class="secno">6.4.27 </bdi>Property: replaces</a>, <a href="#Property:resource_status" class="sec-ref"><bdi class="secno">6.4.30 </bdi>Property: status</a>, <a href="#Property:resource_version" class="sec-ref"><bdi class="secno">6.4.28 </bdi>Property: version</a>, <a href="#Property:resource_version_notes" class="sec-ref"><bdi class="secno">6.4.29 </bdi>Property: version notes</a>. </td> </tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#version-history" class="sec-ref"><bdi class="secno">11.1.1 </bdi>Version chains and hierarchies</a>.</p> </section> <section id="Property:resource_replaces"><div class="header-wrapper"><h4 id="x6-4-27-property-replaces"><bdi class="secno">6.4.27 </bdi>Property: replaces</h4><a class="self-link" href="#Property:resource_replaces" aria-label="Permalink for Section 6.4.27"></a></div> <div class="note" role="note" id="issue-container-generatedID-34"><div role="heading" class="note-title marker" id="h-note-33" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/replaces"><code>dcterms:replaces</code></a></td></tr> <tr> <th class="prop">Definition:</th> <td>A related resource that is supplanted, displaced, or superseded by the described resource [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>].</td> </tr> <tr> <th class="prop">Sub-property of:</th> <td><a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/relation"><code title="http://purl.org/dc/terms/relation">dcterms:relation</code></a></td> </tr> <tr> <th class="prop">See also:</th> <td> <a href="#Property:resource_has_current_version" class="sec-ref"><bdi class="secno">6.4.26 </bdi>Property: current version</a>, <a href="#Property:resource_has_version" class="sec-ref"><bdi class="secno">6.4.25 </bdi>Property: has version</a>, <a href="#inverse-properties" class="sec-ref"><bdi class="secno">7. </bdi>Use of inverse properties</a>, <a href="#Property:resource_previous_version" class="sec-ref"><bdi class="secno">6.4.24 </bdi>Property: previous version</a>, <a href="#Property:resource_release_date" class="sec-ref"><bdi class="secno">6.4.7 </bdi>Property: release date</a>, <a href="#Property:resource_status" class="sec-ref"><bdi class="secno">6.4.30 </bdi>Property: status</a>, <a href="#Property:resource_version" class="sec-ref"><bdi class="secno">6.4.28 </bdi>Property: version</a>, <a href="#Property:resource_version_notes" class="sec-ref"><bdi class="secno">6.4.29 </bdi>Property: version notes</a>. </td> </tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#version-replace" class="sec-ref"><bdi class="secno">11.1.2 </bdi>Versions replaced by other ones</a>.</p> </section> <section id="Property:resource_version"><div class="header-wrapper"><h4 id="x6-4-28-property-version"><bdi class="secno">6.4.28 </bdi>Property: version</h4><a class="self-link" href="#Property:resource_version" aria-label="Permalink for Section 6.4.28"></a></div> <div class="note" role="note" id="issue-container-generatedID-35"><div role="heading" class="note-title marker" id="h-note-34" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#version"><code>dcat:version</code></a></td></tr> <tr> <th class="prop">Definition:</th> <td>The version indicator (name or identifier) of a resource.</td> </tr> <tr> <th class="prop">Equivalent property:</th> <td><a href="https://pav-ontology.github.io/pav/#d4e869"><code title="http://purl.org/pav/version">pav:version</code></a></td> </tr> <tr> <th class="prop">Range:</th> <td><a href="https://www.w3.org/TR/rdf-schema/#ch_literal"><code title="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</code></a></td> </tr> <tr> <th class="prop">Usage note:</th> <td> <p>DCAT does not prescribe how a version name / identifier should be specified, and refers for guidance to [<cite><a class="bibref" data-link-type="biblio" href="#bib-dwbp" title="Data on the Web Best Practices">DWBP</a></cite>]'s <a href="https://www.w3.org/TR/dwbp/#VersioningInfo">Best Practice 7: Provide a version indicator</a>.</p> </td> </tr> <tr> <th class="prop">See also:</th> <td> <a href="#Property:resource_has_current_version" class="sec-ref"><bdi class="secno">6.4.26 </bdi>Property: current version</a>, <a href="#Property:resource_has_version" class="sec-ref"><bdi class="secno">6.4.25 </bdi>Property: has version</a>, <a href="#Property:resource_previous_version" class="sec-ref"><bdi class="secno">6.4.24 </bdi>Property: previous version</a>, <a href="#Property:resource_release_date" class="sec-ref"><bdi class="secno">6.4.7 </bdi>Property: release date</a>, <a href="#Property:resource_replaces" class="sec-ref"><bdi class="secno">6.4.27 </bdi>Property: replaces</a>, <a href="#Property:resource_status" class="sec-ref"><bdi class="secno">6.4.30 </bdi>Property: status</a>, <a href="#Property:resource_version_notes" class="sec-ref"><bdi class="secno">6.4.29 </bdi>Property: version notes</a>. </td> </tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#version-info" class="sec-ref"><bdi class="secno">11.2 </bdi>Version information</a>.</p> </section> <section id="Property:resource_version_notes"><div class="header-wrapper"><h4 id="x6-4-29-property-version-notes"><bdi class="secno">6.4.29 </bdi>Property: version notes</h4><a class="self-link" href="#Property:resource_version_notes" aria-label="Permalink for Section 6.4.29"></a></div> <div class="note" role="note" id="issue-container-generatedID-36"><div role="heading" class="note-title marker" id="h-note-35" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/TR/vocab-adms/#adms-versionnotes"><code>adms:versionNotes</code></a></td></tr> <tr> <th class="prop">Definition:</th> <td>A description of changes between this version and the previous version of the resource [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-adms" title="Asset Description Metadata Schema (ADMS)">VOCAB-ADMS</a></cite>].</td> </tr> <tr> <th class="prop">Range:</th> <td><a href="https://www.w3.org/TR/rdf-schema/#ch_literal"><code title="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</code></a></td> </tr> <tr> <th class="prop">Usage note:</th> <td> <p>In case of backward compatibility issues with the previous version of the resource, a textual description of them <em class="rfc2119">SHOULD</em> be specified by using this property.</p> </td> </tr> <tr> <th class="prop">See also:</th> <td> <a href="#Property:resource_has_current_version" class="sec-ref"><bdi class="secno">6.4.26 </bdi>Property: current version</a>, <a href="#Property:resource_has_version" class="sec-ref"><bdi class="secno">6.4.25 </bdi>Property: has version</a>, <a href="#Property:resource_previous_version" class="sec-ref"><bdi class="secno">6.4.24 </bdi>Property: previous version</a>, <a href="#Property:resource_release_date" class="sec-ref"><bdi class="secno">6.4.7 </bdi>Property: release date</a>, <a href="#Property:resource_replaces" class="sec-ref"><bdi class="secno">6.4.27 </bdi>Property: replaces</a>, <a href="#Property:resource_status" class="sec-ref"><bdi class="secno">6.4.30 </bdi>Property: status</a>, <a href="#Property:resource_version" class="sec-ref"><bdi class="secno">6.4.28 </bdi>Property: version</a>. </td> </tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#version-info" class="sec-ref"><bdi class="secno">11.2 </bdi>Version information</a>.</p> </section> <section id="Property:resource_status"><div class="header-wrapper"><h4 id="x6-4-30-property-status"><bdi class="secno">6.4.30 </bdi>Property: status</h4><a class="self-link" href="#Property:resource_status" aria-label="Permalink for Section 6.4.30"></a></div> <div class="note" role="note" id="issue-container-generatedID-37"><div role="heading" class="note-title marker" id="h-note-36" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/TR/vocab-adms/#adms-status"><code>adms:status</code></a></td></tr> <tr> <th class="prop">Definition:</th> <td>The status of the resource in the context of a particular workflow process [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-adms" title="Asset Description Metadata Schema (ADMS)">VOCAB-ADMS</a></cite>].</td> </tr> <tr> <th class="prop">Range:</th> <td><a href="https://www.w3.org/TR/skos-reference/#concepts"><code title="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</code></a></td> </tr> <tr> <th class="prop">Usage note:</th> <td> <p>DCAT does not prescribe the use of any specific set of life-cycle statuses, but refers to existing standards and community practices fit for the relevant application scenario.</p> </td> </tr> <tr> <th class="prop">See also:</th> <td> <a href="#Property:resource_has_current_version" class="sec-ref"><bdi class="secno">6.4.26 </bdi>Property: current version</a>, <a href="#Property:resource_has_version" class="sec-ref"><bdi class="secno">6.4.25 </bdi>Property: has version</a>, <a href="#Property:resource_previous_version" class="sec-ref"><bdi class="secno">6.4.24 </bdi>Property: previous version</a>, <a href="#Property:resource_release_date" class="sec-ref"><bdi class="secno">6.4.7 </bdi>Property: release date</a>, <a href="#Property:resource_replaces" class="sec-ref"><bdi class="secno">6.4.27 </bdi>Property: replaces</a>, <a href="#Property:resource_version" class="sec-ref"><bdi class="secno">6.4.28 </bdi>Property: version</a>, <a href="#Property:resource_version_notes" class="sec-ref"><bdi class="secno">6.4.29 </bdi>Property: version notes</a>. </td> </tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#life-cycle" class="sec-ref"><bdi class="secno">11.3 </bdi>Resource life-cycle</a>.</p> </section> <section id="Property:resource_first"><div class="header-wrapper"><h4 id="x6-4-31-property-first"><bdi class="secno">6.4.31 </bdi>Property: first</h4><a class="self-link" href="#Property:resource_first" aria-label="Permalink for Section 6.4.31"></a></div> <div class="note" role="note" id="issue-container-generatedID-38"><div role="heading" class="note-title marker" id="h-note-37" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#first"><code>dcat:first</code></a></td></tr> <tr> <th class="prop">Definition:</th> <td>The first resource in an ordered collection or series of resources, to which the current resource belongs.</td> </tr> <tr> <th class="prop">Sub-property of:</th> <td><a href="https://www.w3.org/1999/xhtml/vocab#first"><code title="http://www.w3.org/1999/xhtml/vocab#first">xhv:first</code></a></td> </tr> <tr> <th class="prop">Usage note:</th> <td> <p>In DCAT this property is used for resources belonging to a <a href="#Class:Dataset_Series"><code>dcat:DatasetSeries</code></a>.</p> </td> </tr> <tr> <th class="prop">See also:</th> <td> <a href="#Property:resource_last" class="sec-ref"><bdi class="secno">6.4.32 </bdi>Property: last</a>, <a href="#inverse-properties" class="sec-ref"><bdi class="secno">7. </bdi>Use of inverse properties</a>, <a href="#Property:resource_previous" class="sec-ref"><bdi class="secno">6.4.33 </bdi>Property: previous</a>. </td> </tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#dataset-series" class="sec-ref"><bdi class="secno">12. </bdi>Dataset series</a>.</p> </section> <section id="Property:resource_last"><div class="header-wrapper"><h4 id="x6-4-32-property-last"><bdi class="secno">6.4.32 </bdi>Property: last</h4><a class="self-link" href="#Property:resource_last" aria-label="Permalink for Section 6.4.32"></a></div> <div class="note" role="note" id="issue-container-generatedID-39"><div role="heading" class="note-title marker" id="h-note-38" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#last"><code>dcat:last</code></a></td></tr> <tr> <th class="prop">Definition:</th> <td>The last resource in an ordered collection or series of resources, to which the current resource belongs.</td> </tr> <tr> <th class="prop">Sub-property of:</th> <td><a href="https://www.w3.org/1999/xhtml/vocab#last"><code title="http://www.w3.org/1999/xhtml/vocab#last">xhv:last</code></a></td> </tr> <tr> <th class="prop">Usage note:</th> <td> <p>In DCAT this property is used for resources belonging to a <a href="#Class:Dataset_Series"><code>dcat:DatasetSeries</code></a>.</p> </td> </tr> <tr> <th class="prop">See also:</th> <td> <a href="#Property:resource_first" class="sec-ref"><bdi class="secno">6.4.31 </bdi>Property: first</a>, <a href="#inverse-properties" class="sec-ref"><bdi class="secno">7. </bdi>Use of inverse properties</a>, <a href="#Property:resource_previous" class="sec-ref"><bdi class="secno">6.4.33 </bdi>Property: previous</a>. </td> </tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#dataset-series" class="sec-ref"><bdi class="secno">12. </bdi>Dataset series</a>.</p> </section> <section id="Property:resource_previous"><div class="header-wrapper"><h4 id="x6-4-33-property-previous"><bdi class="secno">6.4.33 </bdi>Property: previous</h4><a class="self-link" href="#Property:resource_previous" aria-label="Permalink for Section 6.4.33"></a></div> <div class="note" role="note" id="issue-container-generatedID-40"><div role="heading" class="note-title marker" id="h-note-39" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#prev"><code>dcat:prev</code></a></td></tr> <tr> <th class="prop">Definition:</th> <td>The previous resource (before the current one) in an ordered collection or series of resources.</td> </tr> <tr> <th class="prop">Sub-property of:</th> <td><a href="https://www.w3.org/1999/xhtml/vocab#prev"><code title="http://www.w3.org/1999/xhtml/vocab#prev">xhv:prev</code></a></td> </tr> <tr> <th class="prop">Usage note:</th> <td> <p>In DCAT this property is used for resources belonging to a <a href="#Class:Dataset_Series"><code>dcat:DatasetSeries</code></a>.</p> <p>It is important to note that this property is different from <a href="#Property:resource_previous_version"><code>dcat:previousVersion</code></a>, as it does not denote a previous version of the same resource, but a distinct resource immediately preceding the current one in an ordered collection of resources.</p> </td> </tr> <tr> <th class="prop">See also:</th> <td> <a href="#Property:resource_first" class="sec-ref"><bdi class="secno">6.4.31 </bdi>Property: first</a>, <a href="#Property:resource_last" class="sec-ref"><bdi class="secno">6.4.32 </bdi>Property: last</a>, <a href="#inverse-properties" class="sec-ref"><bdi class="secno">7. </bdi>Use of inverse properties</a>. </td> </tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#dataset-series" class="sec-ref"><bdi class="secno">12. </bdi>Dataset series</a>.</p> </section> </section> <section id="Class:Catalog_Record"><div class="header-wrapper"><h3 id="x6-5-class-catalog-record"><bdi class="secno">6.5 </bdi>Class: Catalog Record</h3><a class="self-link" href="#Class:Catalog_Record" aria-label="Permalink for Section 6.5"></a></div> <p>The following properties are specific to this class (<code>dcat:CatalogRecord</code>):</p> <ul class="prop-list"> <li><a href="#Property:record_conforms_to">conforms to</a></li> <li><a href="#Property:record_description">description</a></li> <li><a href="#Property:record_listing_date">listing date</a></li> <li><a href="#Property:record_primary_topic">primary topic</a></li> <li><a href="#Property:record_title">title</a></li> <li><a href="#Property:record_update_date">update/modification date</a></li> </ul> <table class="def"> <tbody><tr><th>RDF Class:</th><td><a href="https://www.w3.org/ns/dcat#CatalogRecord"><code>dcat:CatalogRecord</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A record in a catalog, describing the registration of a single <a href="#Class:Resource"><code>dcat:Resource</code></a>.</td></tr> <tr><th class="prop">Usage note</th><td>This class is optional and not all catalogs will use it. It exists for catalogs where a distinction is made between metadata about a <em>dataset or service</em> and metadata about the <em>entry in the catalog about the dataset or service</em>. For example, the <i>publication date</i> property of the <i>dataset</i> reflects the date when the information was originally made available by the publishing agency, while the publication date of the <i>catalog record</i> is the date when the dataset was added to the catalog. In cases where both dates differ, or where only the latter is known, the <em>publication date</em> <em class="rfc2119">SHOULD</em> only be specified for the catalog record. Notice that the <abbr title="World Wide Web Consortium">W3C</abbr> PROV Ontology [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] allows describing further provenance information such as the details of the process and the agent involved in a particular change to a dataset or its registration. </td></tr> <tr><th class="prop">See also</th><td><a href="#Class:Dataset" class="sec-ref"><bdi class="secno">6.6 </bdi>Class: Dataset</a></td></tr> </tbody></table> <p>If a catalog is represented as an RDF Dataset with named graphs (as defined in [<cite><a class="bibref" data-link-type="biblio" href="#bib-sparql11-query" title="SPARQL 1.1 Query Language">SPARQL11-QUERY</a></cite>]), then it is appropriate to place the description of each dataset (consisting of all RDF triples that mention the <code>dcat:Dataset</code>, <code>dcat:CatalogRecord</code>, and any of its <code>dcat:Distribution</code>s) into a separate named graph. The name of that graph <em class="rfc2119">SHOULD</em> be the <abbr title="Internationalized Resource Identifier">IRI</abbr> of the catalog record. </p> <section id="Property:record_title"><div class="header-wrapper"><h4 id="x6-5-1-property-title"><bdi class="secno">6.5.1 </bdi>Property: title</h4><a class="self-link" href="#Property:record_title" aria-label="Permalink for Section 6.5.1"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/title"><code>dcterms:title</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A name given to the record.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a></td></tr> </tbody></table> </section> <section id="Property:record_description"><div class="header-wrapper"><h4 id="x6-5-2-property-description"><bdi class="secno">6.5.2 </bdi>Property: description</h4><a class="self-link" href="#Property:record_description" aria-label="Permalink for Section 6.5.2"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/description"><code>dcterms:description</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A free-text account of the record.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a></td></tr> </tbody></table> </section> <section id="Property:record_listing_date"><div class="header-wrapper"><h4 id="x6-5-3-property-listing-date"><bdi class="secno">6.5.3 </bdi>Property: listing date</h4><a class="self-link" href="#Property:record_listing_date" aria-label="Permalink for Section 6.5.3"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/issued"><code>dcterms:issued</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The date of listing (i.e., formal recording) of the corresponding dataset or service in the catalog.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a> encoded using the relevant <abbr title="International Organization for Standardization">ISO</abbr> 8601 Date and Time compliant string [<cite><a class="bibref" data-link-type="biblio" href="#bib-datetime" title="Date and Time Formats">DATETIME</a></cite>] and typed using the appropriate XML Schema datatype [<cite><a class="bibref" data-link-type="biblio" href="#bib-xmlschema11-2" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">XMLSCHEMA11-2</a></cite>] (<a href="https://www.w3.org/TR/xmlschema11-2/#gYear"><code>xsd:gYear</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#gYearMonth"><code>xsd:gYearMonth</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#date"><code>xsd:date</code></a>, or <a href="https://www.w3.org/TR/xmlschema11-2/#dateTime"><code>xsd:dateTime</code></a>). </td></tr> <tr><th class="prop">Usage note:</th><td>This indicates the date of listing the dataset in the catalog and not the publication date of the dataset itself.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:resource_release_date" class="sec-ref"><bdi class="secno">6.4.7 </bdi>Property: release date</a></td></tr> </tbody></table> </section> <section id="Property:record_update_date"><div class="header-wrapper"><h4 id="x6-5-4-property-update-modification-date"><bdi class="secno">6.5.4 </bdi>Property: update/modification date</h4><a class="self-link" href="#Property:record_update_date" aria-label="Permalink for Section 6.5.4"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/modified"><code>dcterms:modified</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Most recent date on which the catalog entry was changed, updated or modified.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a> encoded using the relevant <abbr title="International Organization for Standardization">ISO</abbr> 8601 Date and Time compliant string [<cite><a class="bibref" data-link-type="biblio" href="#bib-datetime" title="Date and Time Formats">DATETIME</a></cite>] and typed using the appropriate XML Schema datatype [<cite><a class="bibref" data-link-type="biblio" href="#bib-xmlschema11-2" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">XMLSCHEMA11-2</a></cite>] (<a href="https://www.w3.org/TR/xmlschema11-2/#gYear"><code>xsd:gYear</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#gYearMonth"><code>xsd:gYearMonth</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#date"><code>xsd:date</code></a>, or <a href="https://www.w3.org/TR/xmlschema11-2/#dateTime"><code>xsd:dateTime</code></a>). </td></tr> <tr><th class="prop">Usage note:</th><td>This indicates the date of last change of a catalog entry, i.e., the catalog metadata description of the dataset, and not the date of the dataset itself.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:resource_update_date" class="sec-ref"><bdi class="secno">6.4.8 </bdi>Property: update/modification date</a></td></tr> </tbody></table> </section> <section id="Property:record_primary_topic"><div class="header-wrapper"><h4 id="x6-5-5-property-primary-topic"><bdi class="secno">6.5.5 </bdi>Property: primary topic</h4><a class="self-link" href="#Property:record_primary_topic" aria-label="Permalink for Section 6.5.5"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://xmlns.com/foaf/0.1/primaryTopic"><code>foaf:primaryTopic</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The <a href="#Class:Resource"><code>dcat:Resource</code></a> (dataset or service) described in the record.</td></tr> <tr><th class="prop">Usage note:</th><td><a href="http://xmlns.com/foaf/0.1/primaryTopic"><code>foaf:primaryTopic</code></a> property is functional: each catalog record can have at most one primary topic, i.e., describes one cataloged resource.</td></tr> </tbody></table> </section> <section id="Property:record_conforms_to"><div class="header-wrapper"><h4 id="x6-5-6-property-conforms-to"><bdi class="secno">6.5.6 </bdi>Property: conforms to</h4><a class="self-link" href="#Property:record_conforms_to" aria-label="Permalink for Section 6.5.6"></a></div> <div class="note" role="note" id="issue-container-generatedID-41"><div role="heading" class="note-title marker" id="h-note-40" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in this context in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/conformsTo"><code>dcterms:conformsTo</code></a></td></tr> <tr><th class="prop">Definition:</th><td>An established standard to which the described resource conforms.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/Standard"><code>dcterms:Standard</code></a> (A basis for comparison; a reference point against which other things can be evaluated.)</td></tr> <tr><th class="prop">Usage note:</th><td>This property <em class="rfc2119">SHOULD</em> be used to indicate the model, schema, ontology, view or profile that the catalog record metadata conforms to. </td></tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#quality-conformance-statement" class="sec-ref"><bdi class="secno">14.2.1 </bdi>Conformance to a standard</a>.</p> <div class="note" role="note" id="issue-container-generatedID-42"><div role="heading" class="note-title marker" id="h-note-41" aria-level="5"><span>Note</span></div><aside class=""> <p> <a href="http://purl.org/dc/terms/Standard"><code>dcterms:Standard</code></a> is defined in [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] as "A basis for comparison; a reference point against which other things can be evaluated." The target resource is not restricted to formal standards issued by bodies like <abbr title="International Organization for Standardization">ISO</abbr> and <abbr title="World Wide Web Consortium">W3C</abbr>. In this context, it is any resource that specifies one or more aspects of the catalog record content, for example schema, semantics, syntax, usage guidelines, file format, or specific serialization. The meaning of conformance is determined by provisions in the target standard. </p> </aside></div> </section> </section> <section id="Class:Dataset"><div class="header-wrapper"><h3 id="x6-6-class-dataset"><bdi class="secno">6.6 </bdi>Class: Dataset</h3><a class="self-link" href="#Class:Dataset" aria-label="Permalink for Section 6.6"></a></div> <div class="note" role="note" id="issue-container-generatedID-43"><div role="heading" class="note-title marker" id="h-note-42" aria-level="4"><span>Note</span></div><aside class=""> <p> In DCAT 1 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>] <a href="#Class:Dataset"><code>dcat:Dataset</code></a> was a sub-class of <a href="http://purl.org/dc/dcmitype/Dataset"><code>dctype:Dataset</code></a>, which is a member of the <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#section-7">DCMI Types vocabulary</a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>]. The scope of <a href="#Class:Dataset"><code>dcat:Dataset</code></a> also includes other members of the <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#section-7">DCMI Types vocabulary</a>, such as various multimedia (imagery, sound, video) and text, so the sub-class relationship defined in DCAT 1 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>] was removed in the DCAT 2 vocabulary - see Issue <a href="https://github.com/w3c/dxwg/issues/98">#98</a>. </p> <p> Note that members of the <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#section-7">DCMI Types vocabulary</a> may appear as the value of the <a href="#Property:resource_type"><code>dcterms:type</code></a> property, as shown in <a href="#classifying-dataset-types" class="sec-ref"><bdi class="secno">5.5 </bdi>Classifying dataset types</a>. </p> </aside></div> <p>The following properties are specific to this class:</p> <ul class="prop-list"> <li><a href="#Property:dataset_distribution">distribution</a></li> <li><a href="#Property:dataset_frequency">frequency</a></li> <li><a href="#Property:dataset_in_series">in series</a></li> <li><a href="#Property:dataset_spatial">spatial/geographic coverage</a></li> <li><a href="#Property:dataset_spatial_resolution">spatial resolution</a></li> <li><a href="#Property:dataset_temporal">temporal coverage</a></li> <li><a href="#Property:dataset_temporal_resolution">temporal resolution</a></li> <li><a href="#Property:dataset_was_generated_by">was generated by</a></li> </ul> <p>The following properties of the super-class <a href="#Class:Resource"><code>dcat:Resource</code></a> are also available for use:</p> <ul class="prop-list"> <li><a href="#Property:resource_access_rights">access rights</a></li> <li><a href="#Property:resource_conforms_to">conforms to</a></li> <li><a href="#Property:resource_contact_point">contact point</a></li> <li><a href="#Property:resource_creator">creator</a></li> <li><a href="#Property:resource_description">description</a></li> <li><a href="#Property:resource_has_policy">has policy</a></li> <li><a href="#Property:resource_identifier">identifier</a></li> <li><a href="#Property:resource_is_referenced_by">is referenced by</a></li> <li><a href="#Property:resource_keyword">keyword/tag</a></li> <li><a href="#Property:resource_landing_page">landing page</a></li> <li><a href="#Property:resource_license">license</a></li> <li><a href="#Property:resource_language">language</a></li> <li><a href="#Property:resource_relation">relation</a></li> <li><a href="#Property:resource_rights">rights</a></li> <li><a href="#Property:resource_qualified_relation">qualified relation</a></li> <li><a href="#Property:resource_publisher">publisher</a></li> <li><a href="#Property:resource_release_date">release date</a></li> <li><a href="#Property:resource_theme">theme/category</a></li> <li><a href="#Property:resource_title">title</a></li> <li><a href="#Property:resource_type">type/genre</a></li> <li><a href="#Property:resource_update_date">update/modification date</a></li> <li><a href="#Property:resource_qualified_attribution">qualified attribution</a></li> <li><a href="#Property:resource_has_current_version">has current version</a></li> <li><a href="#Property:resource_has_version">has version</a></li> <li><a href="#Property:resource_previous_version">previous version</a></li> <li><a href="#Property:resource_replaces">replaces</a></li> <li><a href="#Property:resource_status">status</a></li> <li><a href="#Property:resource_version">version</a></li> <li><a href="#Property:resource_version_notes">version notes</a></li> <li><a href="#Property:resource_first">first</a></li> <li><a href="#Property:resource_last">last</a></li> <li><a href="#Property:resource_previous">previous</a></li> </ul> <p> Information about licenses and rights <em class="rfc2119">SHOULD</em> be provided on the level of Distribution. Information about licenses and rights <em class="rfc2119">MAY</em> be provided for a Dataset in addition to but not instead of the information provided for the Distributions of that Dataset. Providing license or rights information for a Dataset that is different from information provided for a Distribution of that Dataset <em class="rfc2119">SHOULD</em> be avoided as this can create legal conflicts. </p> <table class="def"> <tbody><tr><th>RDF Class:</th><td><a href="https://www.w3.org/ns/dcat#Dataset"><code>dcat:Dataset</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A collection of data, published or curated by a single agent, and available for access or download in one or more representations.</td></tr> <tr><th class="prop">Sub-class of:</th><td><a href="#Class:Resource"><code>dcat:Resource</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>This class describes the conceptual dataset. One or more representations might be available, with differing schematic layouts and formats or serializations.</td></tr> <tr><th class="prop">Usage note:</th><td>This class describes the actual dataset as published by the dataset provider. In cases where a distinction between the actual dataset and its entry in the catalog is necessary (because metadata such as modification date might differ), the <a href="#Class:Catalog_Record"><code>dcat:CatalogRecord</code></a> class can be used for the latter.</td></tr> <tr><th class="prop">Usage note:</th><td>The notion of dataset in DCAT is broad and inclusive, with the intention of accommodating resource types arising from all communities. Data comes in many forms including numbers, text, pixels, imagery, sound and other multi-media, and potentially other types, any of which might be collected into a dataset.</td></tr> </tbody></table> <section id="Property:dataset_distribution"><div class="header-wrapper"><h4 id="x6-6-1-property-distribution"><bdi class="secno">6.6.1 </bdi>Property: distribution</h4><a class="self-link" href="#Property:dataset_distribution" aria-label="Permalink for Section 6.6.1"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#distribution"><code>dcat:distribution</code></a></td></tr> <tr><th class="prop">Definition:</th><td>An available distribution of the dataset.</td></tr> <tr><th class="prop">Sub-property of:</th><td><a href="http://purl.org/dc/terms/relation"><code>dcterms:relation</code></a></td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Dataset"><code>dcat:Dataset</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="#Class:Distribution"><code>dcat:Distribution</code></a></td></tr> </tbody></table> </section> <section id="Property:dataset_frequency"><div class="header-wrapper"><h4 id="x6-6-2-property-frequency"><bdi class="secno">6.6.2 </bdi>Property: frequency</h4><a class="self-link" href="#Property:dataset_frequency" aria-label="Permalink for Section 6.6.2"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/accrualPeriodicity"><code>dcterms:accrualPeriodicity</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The frequency at which a dataset is published.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/Frequency"><code>dcterms:Frequency</code></a> (A rate at which something recurs)</td></tr> <tr><th class="prop">Usage note:</th><td> The value of <code>dcterms:accrualPeriodicity</code> gives the rate at which the dataset-as-a-whole is updated. This may be complemented by <a href="#Property:dataset_temporal_resolution"><code>dcat:temporalResolution</code></a> to give the time between collected data points in a time series. </td></tr> </tbody></table> <p> Examples showing how <code>dcterms:accrualPeriodicity</code> and <a href="#Property:dataset_temporal_resolution"><code>dcat:temporalResolution</code></a> may be combined are given in <a href="#temporal-properties" class="sec-ref"><bdi class="secno">10.1 </bdi>Temporal properties</a>. </p> </section> <section id="Property:dataset_in_series"><div class="header-wrapper"><h4 id="x6-6-3-property-in-series"><bdi class="secno">6.6.3 </bdi>Property: in series</h4><a class="self-link" href="#Property:dataset_in_series" aria-label="Permalink for Section 6.6.3"></a></div> <div class="note" role="note" id="issue-container-generatedID-44"><div role="heading" class="note-title marker" id="h-note-43" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#inSeries"><code>dcat:inSeries</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A dataset series of which the dataset is part.</td></tr> <tr><th class="prop">Range:</th><td><a href="#Class:Dataset_Series"><code>dcat:DatasetSeries</code></a></td></tr> <tr><th class="prop">Sub-property of:</th> <td><a href="http://purl.org/dc/terms/isPartOf"><code>dcterms:isPartOf</code></a></td> </tr> <tr><th class="prop">See also:</th><td><a href="#inverse-properties" class="sec-ref"><bdi class="secno">7. </bdi>Use of inverse properties</a></td></tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#dataset-series" class="sec-ref"><bdi class="secno">12. </bdi>Dataset series</a>.</p> </section> <section id="Property:dataset_spatial"><div class="header-wrapper"><h4 id="x6-6-4-property-spatial-geographical-coverage"><bdi class="secno">6.6.4 </bdi>Property: spatial/geographical coverage</h4><a class="self-link" href="#Property:dataset_spatial" aria-label="Permalink for Section 6.6.4"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/spatial"><code>dcterms:spatial</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The geographical area covered by the dataset.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/Location"><code>dcterms:Location</code></a> (A spatial region or named place)</td></tr> <tr><th class="prop">Usage note:</th><td>The spatial coverage of a dataset may be encoded as an instance of <a href="http://purl.org/dc/terms/Location"><code>dcterms:Location</code></a>, or may be indicated using an <abbr title="Internationalized Resource Identifier">IRI</abbr> reference (link) to a resource describing a location. It is recommended that links are to entries in a well maintained gazetteer such as <a href="http://www.geonames.org/">Geonames</a>.</td></tr> </tbody></table> <p> Options for expressing the details of a <code>dcterms:Location</code> are provided in <a href="#Class:Location" class="sec-ref"><bdi class="secno">6.16 </bdi>Class: Location</a>. </p> </section> <section id="Property:dataset_spatial_resolution"><div class="header-wrapper"><h4 id="x6-6-5-property-spatial-resolution"><bdi class="secno">6.6.5 </bdi>Property: spatial resolution</h4><a class="self-link" href="#Property:dataset_spatial_resolution" aria-label="Permalink for Section 6.6.5"></a></div> <div class="note" role="note" id="issue-container-generatedID-45"><div role="heading" class="note-title marker" id="h-note-44" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#spatialResolutionInMeters"><code>dcat:spatialResolutionInMeters</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Minimum spatial separation resolvable in a dataset, measured in meters.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a> typed as <a href="https://www.w3.org/TR/xmlschema11-2/#decimal"><code>xsd:decimal</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>If the dataset is an image or grid this should correspond to the spacing of items. For other kinds of spatial datasets, this property will usually indicate the smallest distance between items in the dataset.</td></tr> </tbody></table> <p>The range of this property is a number representing a length in meters. This is intended to provide a summary indication of the spatial resolution of the data as a single number. More complex descriptions of various aspects of spatial precision, accuracy, resolution and other statistics can be provided using the Data Quality Vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>]. </p> <div class="note" role="note" id="issue-container-generatedID-46"><div role="heading" class="note-title marker" id="h-note-45" aria-level="5"><span>Note</span></div><div class=""> <p>As for the use of datatype, note that [<cite><a class="bibref" data-link-type="biblio" href="#bib-json-ld" title="JSON-LD 1.0">JSON-LD</a></cite>] converts numbers to <a href="https://www.w3.org/TR/xmlschema11-2/#double"><code>xsd:double</code></a> or <a href="https://www.w3.org/TR/xmlschema11-2/#integer"><code>xsd:integer</code></a>, and properly generating <a href="https://www.w3.org/TR/xmlschema11-2/#decimal"><code>xsd:decimal</code></a> requires the use of strings with an explicit or coerced datatype. In [<cite><a class="bibref" data-link-type="biblio" href="#bib-turtle" title="RDF 1.1 Turtle">Turtle</a></cite>], seemingly minor modifications can change the datatype of a value: <code>100.0</code> is an <a href="https://www.w3.org/TR/xmlschema11-2/#decimal"><code>xsd:decimal</code></a>, while <code>1e2</code> is an <a href="https://www.w3.org/TR/xmlschema11-2/#double"><code>xsd:double</code></a>.</p> <p>Note also that number constants without a decimal part (e.g. <code>42</code>) will, in [<cite><a class="bibref" data-link-type="biblio" href="#bib-turtle" title="RDF 1.1 Turtle">Turtle</a></cite>] or [<cite><a class="bibref" data-link-type="biblio" href="#bib-json-ld" title="JSON-LD 1.0">JSON-LD</a></cite>], produce a literal with datatype <a href="https://www.w3.org/TR/xmlschema11-2/#integer"><code>xsd:integer</code></a>. Since [<cite><a class="bibref" data-link-type="biblio" href="#bib-xmlschema11-2" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">XMLSCHEMA11-2</a></cite>] defines <a href="https://www.w3.org/TR/xmlschema11-2/#integer"><code>xsd:integer</code></a> as a derived type of <a href="https://www.w3.org/TR/xmlschema11-2/#decimal"><code>xsd:decimal</code></a>, such literals are semantically valid as values of <a href="https://www.w3.org/ns/dcat#spatialResolutionInMeters"><code>dcat:spatialResolutionInMeters</code></a>. However, syntactic validation tools such as [<cite><a class="bibref" data-link-type="biblio" href="#bib-shacl" title="Shapes Constraint Language (SHACL)">SHACL</a></cite>] or [<cite><a class="bibref" data-link-type="biblio" href="#bib-shex" title="Shape Expressions Language 2.1">ShEx</a></cite>] consider them as distinct datatypes. Authors of validation schemas in these languages should therefore consider adding <a href="https://www.w3.org/TR/xmlschema11-2/#integer"><code>xsd:integer</code></a> to the accepted datatypes for <a href="https://www.w3.org/ns/dcat#spatialResolutionInMeters"><code>dcat:spatialResolutionInMeters</code></a>.</p> </div></div> </section> <section id="Property:dataset_temporal"><div class="header-wrapper"><h4 id="x6-6-6-property-temporal-coverage"><bdi class="secno">6.6.6 </bdi>Property: temporal coverage</h4><a class="self-link" href="#Property:dataset_temporal" aria-label="Permalink for Section 6.6.6"></a></div> <table class="def"> <tbody><tr> <th>RDF Property:</th> <td><a href="http://purl.org/dc/terms/temporal"><code>dcterms:temporal</code></a></td> </tr> <tr> <th class="prop">Definition:</th> <td>The temporal period that the dataset covers.</td> </tr> <tr><th class="prop">Range:</th> <td><a href="http://purl.org/dc/terms/PeriodOfTime"><code>dcterms:PeriodOfTime</code></a> (An interval of time that is named or defined by its start and end dates)</td> </tr> <tr> <th class="prop">Usage note:</th> <td>The temporal coverage of a dataset may be encoded as an instance of <a href="http://purl.org/dc/terms/PeriodOfTime"><code>dcterms:PeriodOfTime</code></a>, or may be indicated using an <abbr title="Internationalized Resource Identifier">IRI</abbr> reference (link) to a resource describing a time period or interval.</td> </tr> </tbody></table> <p> Options for expressing the details of a <code>dcterms:PeriodOfTime</code> are provided in <a href="#Class:Period_of_Time" class="sec-ref"><bdi class="secno">6.15 </bdi>Class: Period of Time</a>. </p> </section> <section id="Property:dataset_temporal_resolution"><div class="header-wrapper"><h4 id="x6-6-7-property-temporal-resolution"><bdi class="secno">6.6.7 </bdi>Property: temporal resolution</h4><a class="self-link" href="#Property:dataset_temporal_resolution" aria-label="Permalink for Section 6.6.7"></a></div> <div class="note" role="note" id="issue-container-generatedID-47"><div role="heading" class="note-title marker" id="h-note-46" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#temporalResolution"><code>dcat:temporalResolution</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Minimum time period resolvable in the dataset.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a> typed as <a href="https://www.w3.org/TR/xmlschema11-2/#duration"><code>xsd:duration</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>If the dataset is a time-series this should correspond to the spacing of items in the series. For other kinds of dataset, this property will usually indicate the smallest time difference between items in the dataset. </td></tr> </tbody></table> <p>This is intended to provide a summary indication of the temporal resolution of the data distribution as a single value. More complex descriptions of various aspects of temporal precision, accuracy, resolution and other statistics can be provided using the Data Quality Vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>].</p> <p> The distinction between <code>dcat:temporalResolution</code> and <a href="#Property:dataset_frequency"><code>dcterms:accrualPeriodicity</code></a> is illustrated by examples in <a href="#temporal-properties" class="sec-ref"><bdi class="secno">10.1 </bdi>Temporal properties</a>. </p> </section> <section id="Property:dataset_was_generated_by"><div class="header-wrapper"><h4 id="x6-6-8-property-was-generated-by"><bdi class="secno">6.6.8 </bdi>Property: was generated by</h4><a class="self-link" href="#Property:dataset_was_generated_by" aria-label="Permalink for Section 6.6.8"></a></div> <div class="note" role="note" id="issue-container-generatedID-48"><div role="heading" class="note-title marker" id="h-note-47" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in this context in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/TR/prov-o/#wasGeneratedBy"><code>prov:wasGeneratedBy</code></a></td></tr> <tr><th class="prop">Definition:</th><td>An activity that generated, or provides the business context for, the creation of the dataset.</td></tr> <tr><th class="prop">Domain:</th><td><a href="https://www.w3.org/TR/prov-o/#Entity"><code>prov:Entity</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/TR/prov-o/#Activity"><code>prov:Activity</code></a> An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities.</td></tr> <tr><th class="prop">Usage note:</th><td>The activity associated with generation of a dataset will typically be an initiative, project, mission, survey, on-going activity ("business as usual") etc. Multiple <code>prov:wasGeneratedBy</code> properties can be used to indicate the dataset production context at various levels of granularity. </td></tr> <tr><th class="prop">Usage note:</th><td>Use <a href="https://www.w3.org/TR/prov-o/#qualifiedGeneration"><code>prov:qualifiedGeneration</code></a> to attach additional details about the relationship between the dataset and the activity, e.g., the exact time that the dataset was produced during the lifetime of a project</td></tr> </tbody></table> <div class="note" role="note" id="issue-container-generatedID-49"><div role="heading" class="note-title marker" id="h-note-48" aria-level="5"><span>Note</span></div><aside class=""> <p> Use of this property on an individual entails that the context resource is a member of the class <a href="https://www.w3.org/TR/prov-o/#Entity"><code>prov:Entity</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] . </p> </aside></div> <p> Details about how to describe the activity that generated a dataset, such as a project, initiative, on-going activity, mission or survey, are out of scope for this document. <a href="https://www.w3.org/TR/prov-o/#Activity"><code>prov:Activity</code></a> provides for some basic properties such as begin and end time, associated agents etc. Further details may be provided through classes defined in applications. A number of ontologies for describing projects are available, for example VIVO for academic research projects [<cite><a class="bibref" data-link-type="biblio" href="#bib-vivo-isf" title="VIVO-ISF Data Standard">VIVO-ISF</a></cite>], DOAP (Description of a Project) for software projects [<cite><a class="bibref" data-link-type="biblio" href="#bib-doap" title="Description of a Project">DOAP</a></cite>], and DBPedia for general projects [<cite><a class="bibref" data-link-type="biblio" href="#bib-dbpedia-ont" title="DBPedia ontology">DBPEDIA-ONT</a></cite>] which are expected to be suitable for different applications. </p> </section> </section> <section id="Class:Dataset_Series"><div class="header-wrapper"><h3 id="x6-7-class-dataset-series"><bdi class="secno">6.7 </bdi>Class: Dataset Series</h3><a class="self-link" href="#Class:Dataset_Series" aria-label="Permalink for Section 6.7"></a></div> <div class="note" role="note" id="issue-container-generatedID-50"><div role="heading" class="note-title marker" id="h-note-49" aria-level="4"><span>Note</span></div><aside class=""> <p> Class added in DCAT 3, see Issue <a href="https://github.com/w3c/dxwg/issues/1272">#1272</a>. </p> </aside></div> <p>The following properties of the super-classes <a href="#Class:Resource"><code>dcat:Resource</code></a> and <a href="#Class:Dataset"><code>dcat:Dataset</code></a> are also available for use:</p> <ul class="prop-list"> <li><a href="#Property:resource_access_rights">access rights</a></li> <li><a href="#Property:resource_conforms_to">conforms to</a></li> <li><a href="#Property:resource_contact_point">contact point</a></li> <li><a href="#Property:resource_creator">creator</a></li> <li><a href="#Property:dataset_distribution">distribution</a></li> <li><a href="#Property:resource_description">description</a></li> <li><a href="#Property:resource_has_part">has part</a></li> <li><a href="#Property:resource_has_policy">has policy</a></li> <li><a href="#Property:resource_identifier">identifier</a></li> <li><a href="#Property:dataset_in_series">in series</a></li> <li><a href="#Property:resource_is_referenced_by">is referenced by</a></li> <li><a href="#Property:resource_keyword">keyword/tag</a></li> <li><a href="#Property:resource_landing_page">landing page</a></li> <li><a href="#Property:resource_license">license</a></li> <li><a href="#Property:resource_language">language</a></li> <li><a href="#Property:resource_relation">relation</a></li> <li><a href="#Property:resource_rights">rights</a></li> <li><a href="#Property:resource_qualified_relation">qualified relation</a></li> <li><a href="#Property:resource_publisher">publisher</a></li> <li><a href="#Property:resource_release_date">release date</a></li> <li><a href="#Property:resource_theme">theme/category</a></li> <li><a href="#Property:resource_title">title</a></li> <li><a href="#Property:resource_type">type/genre</a></li> <li><a href="#Property:resource_update_date">update/modification date</a></li> <li><a href="#Property:resource_qualified_attribution">qualified attribution</a></li> <li><a href="#Property:dataset_frequency">frequency</a></li> <li><a href="#Property:dataset_spatial">spatial/geographic coverage</a></li> <li><a href="#Property:dataset_spatial_resolution">spatial resolution</a></li> <li><a href="#Property:dataset_temporal">temporal coverage</a></li> <li><a href="#Property:dataset_temporal_resolution">temporal resolution</a></li> <li><a href="#Property:dataset_was_generated_by">was generated by</a></li> <li><a href="#Property:resource_has_current_version">has current version</a></li> <li><a href="#Property:resource_has_version">has version</a></li> <li><a href="#Property:resource_previous_version">previous version</a></li> <li><a href="#Property:resource_replaces">replaces</a></li> <li><a href="#Property:resource_status">status</a></li> <li><a href="#Property:resource_version">version</a></li> <li><a href="#Property:resource_version_notes">version notes</a></li> <li><a href="#Property:resource_first">first</a></li> <li><a href="#Property:resource_last">last</a></li> <li><a href="#Property:resource_previous">previous</a></li> </ul> <div class="note" role="note" id="issue-container-generatedID-51"><div role="heading" class="note-title marker" id="h-note-50" aria-level="4"><span>Note</span></div><aside class=""> <p>Some of the inherited properties may have a particular semantics when used with <code>dcat:DatasetSeries</code>. For more details, see <a href="#dataset-series" class="sec-ref"><bdi class="secno">12. </bdi>Dataset series</a>.</p> </aside></div> <table class="def"> <tbody><tr><th>RDF Class:</th><td><a href="https://www.w3.org/ns/dcat#DatasetSeries"><code>dcat:DatasetSeries</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A collection of datasets that are published separately, but share some characteristics that group them. </td></tr> <tr><th class="prop">Sub-class of:</th><td><a href="#Class:Dataset"><code>dcat:Dataset</code></a></td></tr> <tr><th class="prop">Usage note:</th><td> Dataset series can be also soft-typed via property <code>dcterms:type</code> as in the approach used in [<cite><a class="bibref" data-link-type="biblio" href="#bib-geodcat-ap" title="GeoDCAT-AP: A geospatial extension for the DCAT application profile for data portals in Europe">GeoDCAT-AP</a></cite>], and adopted in [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap-it" title="Profilo metadatazione DCAT-AP_IT">DCAT-AP-IT</a></cite>] and [<cite><a class="bibref" data-link-type="biblio" href="#bib-geodcat-ap-it" title="GeoDCAT-AP in Italy, the national guidelines published">GeoDCAT-AP-IT</a></cite>]).</td></tr> <tr><th class="prop">Usage note:</th><td>Common scenarios for dataset series include: time series composed of periodically released subsets; map-series composed of items of the same type or theme but with differing spatial footprints.</td></tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#dataset-series" class="sec-ref"><bdi class="secno">12. </bdi>Dataset series</a>.</p> </section> <section id="Class:Distribution"><div class="header-wrapper"><h3 id="x6-8-class-distribution"><bdi class="secno">6.8 </bdi>Class: Distribution</h3><a class="self-link" href="#Class:Distribution" aria-label="Permalink for Section 6.8"></a></div> <p>The following properties are specific to this class:</p> <ul class="prop-list"> <li><a href="#Property:distribution_access_rights">access rights</a></li> <li><a href="#Property:distribution_access_url">access URL</a></li> <li><a href="#Property:distribution_access_service">access service</a></li> <li><a href="#Property:distribution_size">byte size</a></li> <li><a href="#Property:distribution_compression_format">compression format</a></li> <li><a href="#Property:distribution_conforms_to">conforms to</a></li> <li><a href="#Property:distribution_description">description</a></li> <li><a href="#Property:distribution_download_url">download URL</a></li> <li><a href="#Property:distribution_format">format</a></li> <li><a href="#Property:distribution_has_policy">has policy</a></li> <li><a href="#Property:distribution_license">license</a></li> <li><a href="#Property:distribution_media_type">media type</a></li> <li><a href="#Property:distribution_packaging_format">packaging format</a></li> <li><a href="#Property:distribution_release_date">release date</a></li> <li><a href="#Property:distribution_rights">rights</a></li> <li><a href="#Property:distribution_spatial_resolution">spatial resolution</a></li> <li><a href="#Property:distribution_temporal_resolution">temporal resolution</a></li> <li><a href="#Property:distribution_title">title</a></li> <li><a href="#Property:distribution_update_date">update/modification date</a></li> </ul> <table class="def"> <tbody><tr><th>RDF Class:</th><td><a href="https://www.w3.org/ns/dcat#Distribution"><code>dcat:Distribution</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A specific representation of a dataset. A dataset might be available in multiple serializations that may differ in various ways, including natural language, media-type or format, schematic organization, temporal and spatial resolution, level of detail or profiles (which might specify any or all of the above). </td></tr> <tr><th class="prop">Usage note:</th><td>This represents a general availability of a dataset. It implies no information about the actual access method of the data, i.e., whether by direct download, <abbr title="Application Programming Interface">API</abbr>, or through a Web page. The use of <a href="#Property:distribution_download_url"><code>dcat:downloadURL</code></a> property indicates directly downloadable distributions.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Class:Data_Service" class="sec-ref"><bdi class="secno">6.9 </bdi>Class: Data Service</a></td></tr> </tbody></table> <div class="note" role="note" id="issue-container-generatedID-52"><div role="heading" class="note-title marker" id="h-note-51" aria-level="4"><span>Note</span></div><aside class=""> <p> Examples of distributions include a CSV file, a [<cite><a class="bibref" data-link-type="biblio" href="#bib-netcdf" title="Network Common Data Form (NetCDF)">netCDF</a></cite>] file, a JSON document, or a data-cube, files made accessible according to different profiles, such as XML or JSON schemas or [<cite><a class="bibref" data-link-type="biblio" href="#bib-shex" title="Shape Expressions Language 2.1">ShEx</a></cite>] or [<cite><a class="bibref" data-link-type="biblio" href="#bib-shacl" title="Shapes Constraint Language (SHACL)">SHACL</a></cite>] expressions.</p> <p>In some cases all distributions of a dataset will be fully informationally equivalent, in the sense that lossless transformations between the representations are possible. An example would be different serializations of an RDF graph using RDF/XML [<cite><a class="bibref" data-link-type="biblio" href="#bib-rdf-syntax-grammar" title="RDF 1.1 XML Syntax">RDF-SYNTAX-GRAMMAR</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-turtle" title="RDF 1.1 Turtle">Turtle</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-n3" title="Notation3 (N3): A readable RDF syntax">N3</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-json-ld" title="JSON-LD 1.0">JSON-LD</a></cite>]. However, in other cases the distributions might have different levels of fidelity to the underlying data. For example, a graphical representation about the data on a CSV file may not contain the same total information recorded in the CSV file, but they could be considered as two distributions for the same dataset as they are about the same data. </p> <p> As a counter-example, budget data for different years would usually be modeled as different datasets, each with their own distributions, since all distributions of one dataset should broadly contain the same data. </p> <p> Nevertheless, the question of whether different representations can be understood to be distributions of the same dataset, or distributions of different datasets, is application specific. Judgment about how to describe them is the responsibility of the provider, taking into account their understanding of the expectations of users, and practices in the relevant community. </p> </aside></div> <p> Links between a <code>dcat:Distribution</code> and services or Web addresses where it can be accessed are expressed using <a href="#Property:distribution_access_url"><code>dcat:accessURL</code></a>, <a href="#Property:distribution_access_service"><code>dcat:accessService</code></a>, <a href="#Property:distribution_download_url"><code>dcat:downloadURL</code></a>, as shown in <a href="#fig-dcat-all-attributes" class="fig-ref" title="Overview of DCAT model, showing the classes of resources that can be members of a Catalog, and the relationships between them. Except where specifically indicated, DCAT does not provide cardinality constraints.">Figure <bdi class="">1</bdi></a> and described in the definitions below. </p> <section id="Property:distribution_title"><div class="header-wrapper"><h4 id="x6-8-1-property-title"><bdi class="secno">6.8.1 </bdi>Property: title</h4><a class="self-link" href="#Property:distribution_title" aria-label="Permalink for Section 6.8.1"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/title"><code>dcterms:title</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A name given to the distribution.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a></td></tr> </tbody></table> </section> <section id="Property:distribution_description"><div class="header-wrapper"><h4 id="x6-8-2-property-description"><bdi class="secno">6.8.2 </bdi>Property: description</h4><a class="self-link" href="#Property:distribution_description" aria-label="Permalink for Section 6.8.2"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/description"><code>dcterms:description</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A free-text account of the distribution.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a></td></tr> </tbody></table> </section> <section id="Property:distribution_release_date"><div class="header-wrapper"><h4 id="x6-8-3-property-release-date"><bdi class="secno">6.8.3 </bdi>Property: release date</h4><a class="self-link" href="#Property:distribution_release_date" aria-label="Permalink for Section 6.8.3"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/issued"><code>dcterms:issued</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Date of formal issuance (e.g., publication) of the distribution.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a> encoded using the relevant <abbr title="International Organization for Standardization">ISO</abbr> 8601 Date and Time compliant string [<cite><a class="bibref" data-link-type="biblio" href="#bib-datetime" title="Date and Time Formats">DATETIME</a></cite>] and typed using the appropriate XML Schema datatype [<cite><a class="bibref" data-link-type="biblio" href="#bib-xmlschema11-2" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">XMLSCHEMA11-2</a></cite>] (<a href="https://www.w3.org/TR/xmlschema11-2/#gYear"><code>xsd:gYear</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#gYearMonth"><code>xsd:gYearMonth</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#date"><code>xsd:date</code></a>, or <a href="https://www.w3.org/TR/xmlschema11-2/#dateTime"><code>xsd:dateTime</code></a>). </td></tr> <tr><th class="prop">Usage note:</th><td>This property <em class="rfc2119">SHOULD</em> be set using the first known date of issuance.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:resource_release_date" class="sec-ref"><bdi class="secno">6.4.7 </bdi>Property: release date</a></td></tr> </tbody></table> </section> <section id="Property:distribution_update_date"><div class="header-wrapper"><h4 id="x6-8-4-property-update-modification-date"><bdi class="secno">6.8.4 </bdi>Property: update/modification date</h4><a class="self-link" href="#Property:distribution_update_date" aria-label="Permalink for Section 6.8.4"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/modified"><code>dcterms:modified</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Most recent date on which the distribution was changed, updated or modified.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a> encoded using the relevant <abbr title="International Organization for Standardization">ISO</abbr> 8601 Date and Time compliant string [<cite><a class="bibref" data-link-type="biblio" href="#bib-datetime" title="Date and Time Formats">DATETIME</a></cite>] and typed using the appropriate XML Schema datatype [<cite><a class="bibref" data-link-type="biblio" href="#bib-xmlschema11-2" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">XMLSCHEMA11-2</a></cite>] (<a href="https://www.w3.org/TR/xmlschema11-2/#gYear"><code>xsd:gYear</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#gYearMonth"><code>xsd:gYearMonth</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#date"><code>xsd:date</code></a>, or <a href="https://www.w3.org/TR/xmlschema11-2/#dateTime"><code>xsd:dateTime</code></a>).</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:resource_update_date" class="sec-ref"><bdi class="secno">6.4.8 </bdi>Property: update/modification date</a></td></tr> </tbody></table> </section> <section id="Property:distribution_license"><div class="header-wrapper"><h4 id="x6-8-5-property-license"><bdi class="secno">6.8.5 </bdi>Property: license</h4><a class="self-link" href="#Property:distribution_license" aria-label="Permalink for Section 6.8.5"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/license"><code>dcterms:license</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A legal document under which the distribution is made available.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/LicenseDocument"><code>dcterms:LicenseDocument</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>Information about licenses and rights <em class="rfc2119">SHOULD</em> be provided on the level of Distribution. Information about licenses and rights <em class="rfc2119">MAY</em> be provided for a Dataset in addition to but not instead of the information provided for the Distributions of that Dataset. Providing license or rights information for a Dataset that is different from information provided for a Distribution of that Dataset <em class="rfc2119">SHOULD</em> be avoided as this can create legal conflicts. See also guidance at <a href="#license-rights" class="sec-ref"><bdi class="secno">9. </bdi>License and rights statements</a>.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:distribution_rights" class="sec-ref"><bdi class="secno">6.8.7 </bdi>Property: rights</a> <a href="#Property:resource_license" class="sec-ref"><bdi class="secno">6.4.19 </bdi>Property: license</a></td></tr> </tbody></table> </section> <section id="Property:distribution_access_rights"><div class="header-wrapper"><h4 id="x6-8-6-property-access-rights"><bdi class="secno">6.8.6 </bdi>Property: access rights</h4><a class="self-link" href="#Property:distribution_access_rights" aria-label="Permalink for Section 6.8.6"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/accessRights"><code>dcterms:accessRights</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A rights statement that concerns how the distribution is accessed.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/RightsStatement"><code>dcterms:RightsStatement</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>Information about licenses and rights <em class="rfc2119">MAY</em> be provided for the Distribution. See also guidance at <a href="#license-rights" class="sec-ref"><bdi class="secno">9. </bdi>License and rights statements</a>.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:distribution_license" class="sec-ref"><bdi class="secno">6.8.5 </bdi>Property: license</a>, <a href="#Property:distribution_rights" class="sec-ref"><bdi class="secno">6.8.7 </bdi>Property: rights</a>, <a href="#Property:resource_access_rights" class="sec-ref"><bdi class="secno">6.4.1 </bdi>Property: access rights</a></td></tr> </tbody></table> </section> <section id="Property:distribution_rights"><div class="header-wrapper"><h4 id="x6-8-7-property-rights"><bdi class="secno">6.8.7 </bdi>Property: rights</h4><a class="self-link" href="#Property:distribution_rights" aria-label="Permalink for Section 6.8.7"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/rights"><code>dcterms:rights</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Information about rights held in and over the distribution.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/RightsStatement"><code>dcterms:RightsStatement</code></a></td></tr> <tr><th class="prop">Usage note:</th><td> <p><code>dcterms:license</code>, which is a sub-property of <code>dcterms:rights</code>, can be used to link a distribution to a license document. However, <code>dcterms:rights</code> allows linking to a rights statement that can include licensing information as well as other information that supplements the license such as attribution.</p> <p>Information about licenses and rights <em class="rfc2119">SHOULD</em> be provided on the level of Distribution. Information about licenses and rights <em class="rfc2119">MAY</em> be provided for a Dataset in addition to but not instead of the information provided for the Distributions of that Dataset. Providing license or rights information for a Dataset that is different from information provided for a Distribution of that Dataset <em class="rfc2119">SHOULD</em> be avoided as this can create legal conflicts. See also guidance at <a href="#license-rights" class="sec-ref"><bdi class="secno">9. </bdi>License and rights statements</a>.</p> </td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:distribution_license" class="sec-ref"><bdi class="secno">6.8.5 </bdi>Property: license</a>, <a href="#Property:resource_rights" class="sec-ref"><bdi class="secno">6.4.20 </bdi>Property: rights</a></td></tr> </tbody></table> </section> <section id="Property:distribution_has_policy"><div class="header-wrapper"><h4 id="x6-8-8-property-has-policy"><bdi class="secno">6.8.8 </bdi>Property: has policy</h4><a class="self-link" href="#Property:distribution_has_policy" aria-label="Permalink for Section 6.8.8"></a></div> <div class="note" role="note" id="issue-container-generatedID-53"><div role="heading" class="note-title marker" id="h-note-52" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in this context in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/TR/odrl-vocab/#term-hasPolicy"><code>odrl:hasPolicy</code></a></td></tr> <tr><th class="prop">Definition:</th><td>An <abbr title="Open Digital Rights Language">ODRL</abbr> conformant policy expressing the rights associated with the distribution.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/TR/odrl-vocab/#term-Policy"><code>odrl:Policy</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>Information about rights expressed as an <abbr title="Open Digital Rights Language">ODRL</abbr> policy [<cite><a class="bibref" data-link-type="biblio" href="#bib-odrl-model" title="ODRL Information Model 2.2">ODRL-MODEL</a></cite>] using the <abbr title="Open Digital Rights Language">ODRL</abbr> vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-odrl-vocab" title="ODRL Vocabulary & Expression 2.2">ODRL-VOCAB</a></cite>] <em class="rfc2119">MAY</em> be provided for the distribution. See also guidance at <a href="#license-rights" class="sec-ref"><bdi class="secno">9. </bdi>License and rights statements</a>.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:resource_license" class="sec-ref"><bdi class="secno">6.4.19 </bdi>Property: license</a>, <a href="#Property:distribution_access_rights" class="sec-ref"><bdi class="secno">6.8.6 </bdi>Property: access rights</a>, <a href="#Property:distribution_rights" class="sec-ref"><bdi class="secno">6.8.7 </bdi>Property: rights</a></td></tr> </tbody></table> </section> <section id="Property:distribution_access_url"><div class="header-wrapper"><h4 id="x6-8-9-property-access-url"><bdi class="secno">6.8.9 </bdi>Property: access URL</h4><a class="self-link" href="#Property:distribution_access_url" aria-label="Permalink for Section 6.8.9"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#accessURL"><code>dcat:accessURL</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A URL of the resource that gives access to a distribution of the dataset. E.g., landing page, feed, SPARQL endpoint.</td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Distribution"><code>dcat:Distribution</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Resource"><code>rdfs:Resource</code></a></td></tr> <tr><th class="prop">Usage note:</th><td> <p><a href="#Property:distribution_access_url"><code>dcat:accessURL</code></a> <em class="rfc2119">SHOULD</em> be used for the URL of a service or location that can provide access to this distribution, typically through a Web form, query or <abbr title="Application Programming Interface">API</abbr> call.</p> <p><a href="#Property:distribution_download_url"><code>dcat:downloadURL</code></a> is preferred for direct links to downloadable resources.</p> <p>If the distribution(s) are accessible only through a landing page (i.e., direct download URLs are not known), then the landing page URL associated with the <code>dcat:Dataset</code> <em class="rfc2119">SHOULD</em> be duplicated as access URL on a distribution (see <a href="#example-landing-page" class="sec-ref"><bdi class="secno">5.7 </bdi>Dataset available only behind some Web page</a>).</p> </td></tr> <tr><th class="prop">See also</th><td><a href="#Property:distribution_download_url" class="sec-ref"><bdi class="secno">6.8.11 </bdi>Property: download URL</a>, <a href="#Property:distribution_access_service" class="sec-ref"><bdi class="secno">6.8.10 </bdi>Property: access service</a></td></tr> </tbody></table> <p> <code>dcat:accessURL</code> matches the property-chain <code>dcat:accessService</code>/<code>dcat:endpointURL</code>. In the RDF representation of DCAT this is axiomatized as an OWL property-chain axiom. </p> </section> <section id="Property:distribution_access_service"><div class="header-wrapper"><h4 id="x6-8-10-property-access-service"><bdi class="secno">6.8.10 </bdi>Property: access service</h4><a class="self-link" href="#Property:distribution_access_service" aria-label="Permalink for Section 6.8.10"></a></div> <div class="note" role="note" id="issue-container-generatedID-54"><div role="heading" class="note-title marker" id="h-note-53" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#accessService"><code>dcat:accessService</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A data service that gives access to the distribution of the dataset</td></tr> <tr><th class="prop">Range:</th><td><a href="#Class:Data_Service"><code>dcat:DataService</code></a></td></tr> <tr><th class="prop">Usage note:</th><td><a href="#Property:distribution_access_service"><code>dcat:accessService</code></a> <em class="rfc2119">SHOULD</em> be used to link to a description of a <a href="#Class:Data_Service"><code>dcat:DataService</code></a> that can provide access to this distribution.</td></tr> <tr><th class="prop">See also</th><td><a href="#Property:distribution_download_url" class="sec-ref"><bdi class="secno">6.8.11 </bdi>Property: download URL</a>, <a href="#Property:distribution_access_url" class="sec-ref"><bdi class="secno">6.8.9 </bdi>Property: access URL</a></td></tr> </tbody></table> </section> <section id="Property:distribution_download_url"><div class="header-wrapper"><h4 id="x6-8-11-property-download-url"><bdi class="secno">6.8.11 </bdi>Property: download URL</h4><a class="self-link" href="#Property:distribution_download_url" aria-label="Permalink for Section 6.8.11"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#downloadURL"><code>dcat:downloadURL</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The URL of the downloadable file in a given format. E.g., CSV file or RDF file. The format is indicated by the distribution's <code>dcterms:format</code> and/or <code>dcat:mediaType</code></td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Distribution"><code>dcat:Distribution</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Resource"><code>rdfs:Resource</code></a></td></tr> <tr><th class="prop">Usage note:</th><td><a href="#Property:distribution_download_url"><code>dcat:downloadURL</code></a> <em class="rfc2119">SHOULD</em> be used for the URL at which this distribution is available directly, typically through a HTTP Get request. </td></tr> <tr><th class="prop">See also</th><td><a href="#Property:distribution_access_url" class="sec-ref"><bdi class="secno">6.8.9 </bdi>Property: access URL</a>, <a href="#Property:distribution_access_service" class="sec-ref"><bdi class="secno">6.8.10 </bdi>Property: access service</a></td></tr> </tbody></table> </section> <section id="Property:distribution_size"><div class="header-wrapper"><h4 id="x6-8-12-property-byte-size"><bdi class="secno">6.8.12 </bdi>Property: byte size</h4><a class="self-link" href="#Property:distribution_size" aria-label="Permalink for Section 6.8.12"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#byteSize"><code>dcat:byteSize</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The size of a distribution in bytes.</td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Distribution"><code>dcat:Distribution</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Literal"><code>rdfs:Literal</code></a> typically typed as <a href="https://www.w3.org/TR/xmlschema11-2/#nonNegativeInteger"><code>xsd:nonNegativeInteger</code></a>.</td></tr> <tr><th class="prop">Usage note:</th><td>The size in bytes can be approximated (as a non-negative integer) when the precise size is not known.</td></tr> <tr><th class="prop">Usage note:</th><td>While it is recommended that the size be given as an integer, alternative literals such as '1.5 MB' are sometimes used.</td></tr> </tbody></table> </section> <section id="Property:distribution_spatial_resolution"><div class="header-wrapper"><h4 id="x6-8-13-property-spatial-resolution"><bdi class="secno">6.8.13 </bdi>Property: spatial resolution</h4><a class="self-link" href="#Property:distribution_spatial_resolution" aria-label="Permalink for Section 6.8.13"></a></div> <div class="note" role="note" id="issue-container-generatedID-55"><div role="heading" class="note-title marker" id="h-note-54" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#spatialResolutionInMeters"><code>dcat:spatialResolutionInMeters</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The minimum spatial separation resolvable in a dataset distribution, measured in meters.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/TR/xmlschema11-2/#decimal"><code>xsd:decimal</code></a> or <a href="https://www.w3.org/TR/xmlschema11-2/#double"><code>xsd:double</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>If the dataset is an image or grid this should correspond to the spacing of items. For other kinds of spatial datasets, this property will usually indicate the smallest distance between items in the dataset.</td></tr> <tr><th class="prop">Usage note:</th><td>Alternative spatial resolutions might be provided as different dataset distributions</td></tr> </tbody></table> <p>The range of this property is a number representing a length in meters. This is intended to provide a summary indication of the spatial resolution of the data distribution as a single number. More complex descriptions of various aspects of spatial precision, accuracy, resolution and other statistics can be provided using the Data Quality Vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>]. </p> </section> <section id="Property:distribution_temporal_resolution"><div class="header-wrapper"><h4 id="x6-8-14-property-temporal-resolution"><bdi class="secno">6.8.14 </bdi>Property: temporal resolution</h4><a class="self-link" href="#Property:distribution_temporal_resolution" aria-label="Permalink for Section 6.8.14"></a></div> <div class="note" role="note" id="issue-container-generatedID-56"><div role="heading" class="note-title marker" id="h-note-55" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#temporalResolution"><code>dcat:temporalResolution</code></a></td></tr> <tr><th class="prop">Definition:</th><td>Minimum time period resolvable in the dataset distribution.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/TR/xmlschema11-2/#duration"><code>xsd:duration</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>If the dataset is a time-series this should correspond to the spacing of items in the series. For other kinds of dataset, this property will usually indicate the smallest time difference between items in the dataset. </td></tr> <tr><th class="prop">Usage note:</th><td>Alternative temporal resolutions might be provided in different dataset distributions</td></tr> </tbody></table> <p>This is intended to provide a summary indication of the temporal resolution of the data distribution as a single value. More complex descriptions of various aspects of temporal precision, accuracy, resolution and other statistics can be provided using the Data Quality Vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>]. </p> </section> <section id="Property:distribution_conforms_to"><div class="header-wrapper"><h4 id="x6-8-15-property-conforms-to"><bdi class="secno">6.8.15 </bdi>Property: conforms to</h4><a class="self-link" href="#Property:distribution_conforms_to" aria-label="Permalink for Section 6.8.15"></a></div> <div class="note" role="note" id="issue-container-generatedID-57"><div role="heading" class="note-title marker" id="h-note-56" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in this context in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/conformsTo"><code>dcterms:conformsTo</code></a></td></tr> <tr><th class="prop">Definition:</th><td>An established standard to which the distribution conforms.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/Standard"><code>dcterms:Standard</code></a> (A basis for comparison; a reference point against which other things can be evaluated.)</td></tr> <tr><th class="prop">Usage note:</th><td>This property <em class="rfc2119">SHOULD</em> be used to indicate the model, schema, ontology, view or profile that this representation of a dataset conforms to. This is (generally) a complementary concern to the media-type or format. </td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:distribution_format" class="sec-ref"><bdi class="secno">6.8.17 </bdi>Property: format</a>, <a href="#Property:distribution_media_type" class="sec-ref"><bdi class="secno">6.8.16 </bdi>Property: media type</a></td></tr> </tbody></table> <p>For guidance on the use of this property, see <a href="#quality-conformance-statement" class="sec-ref"><bdi class="secno">14.2.1 </bdi>Conformance to a standard</a>.</p> <div class="note" role="note" id="issue-container-generatedID-58"><div role="heading" class="note-title marker" id="h-note-57" aria-level="5"><span>Note</span></div><aside class=""> <p> <a href="http://purl.org/dc/terms/Standard"><code>dcterms:Standard</code></a> is defined in [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] as "A basis for comparison; a reference point against which other things can be evaluated." It is not restricted to formal standards issued by bodies like <abbr title="International Organization for Standardization">ISO</abbr> and <abbr title="World Wide Web Consortium">W3C</abbr>. In this context it will usually be used for a schema, ontology, data model or profile which specifies the structure of a dataset distribution. This is not necessarily tied to a single encoding or serialization. </p> </aside></div> </section> <section id="Property:distribution_media_type"><div class="header-wrapper"><h4 id="x6-8-16-property-media-type"><bdi class="secno">6.8.16 </bdi>Property: media type</h4><a class="self-link" href="#Property:distribution_media_type" aria-label="Permalink for Section 6.8.16"></a></div> <div class="note" role="note" id="issue-container-generatedID-59"><div role="heading" class="note-title marker" id="h-note-58" aria-level="5"><span>Note</span></div><aside class=""> <p> The range of <code>dcat:mediaType</code> was tightened from <code>dcterms:MediaTypeOrExtent</code> to <code>dcterms:MediaType</code> as part of the DCAT 2 vocabulary. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#mediaType"><code>dcat:mediaType</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The media type of the distribution as defined by IANA [<cite><a class="bibref" data-link-type="biblio" href="#bib-iana-media-types" title="Media Types">IANA-MEDIA-TYPES</a></cite>].</td></tr> <tr><th class="prop">Sub-property of:</th><td><a href="http://purl.org/dc/terms/format"><code>dcterms:format</code></a></td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Distribution"><code>dcat:Distribution</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/MediaType"><code>dcterms:MediaType</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>This property <em class="rfc2119">SHOULD</em> be used when the media type of the distribution is defined in IANA [<cite><a class="bibref" data-link-type="biblio" href="#bib-iana-media-types" title="Media Types">IANA-MEDIA-TYPES</a></cite>], otherwise <code>dcterms:format</code> <em class="rfc2119">MAY</em> be used with different values.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:distribution_format" class="sec-ref"><bdi class="secno">6.8.17 </bdi>Property: format</a>, <a href="#Property:distribution_conforms_to" class="sec-ref"><bdi class="secno">6.8.15 </bdi>Property: conforms to</a></td></tr> </tbody></table> </section> <section id="Property:distribution_format"><div class="header-wrapper"><h4 id="x6-8-17-property-format"><bdi class="secno">6.8.17 </bdi>Property: format</h4><a class="self-link" href="#Property:distribution_format" aria-label="Permalink for Section 6.8.17"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/format"><code>dcterms:format</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The file format of the distribution.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/MediaTypeOrExtent"><code>dcterms:MediaTypeOrExtent</code></a></td></tr> <tr><th class="prop">Usage note:</th><td> <a href="#Property:distribution_media_type"><code>dcat:mediaType</code></a> <em class="rfc2119">SHOULD</em> be used if the type of the distribution is defined by IANA [<cite><a class="bibref" data-link-type="biblio" href="#bib-iana-media-types" title="Media Types">IANA-MEDIA-TYPES</a></cite>].</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:distribution_media_type" class="sec-ref"><bdi class="secno">6.8.16 </bdi>Property: media type</a>, <a href="#Property:distribution_conforms_to" class="sec-ref"><bdi class="secno">6.8.15 </bdi>Property: conforms to</a></td></tr> </tbody></table> </section> <section id="Property:distribution_compression_format"><div class="header-wrapper"><h4 id="x6-8-18-property-compression-format"><bdi class="secno">6.8.18 </bdi>Property: compression format</h4><a class="self-link" href="#Property:distribution_compression_format" aria-label="Permalink for Section 6.8.18"></a></div> <div class="note" role="note" id="issue-container-generatedID-60"><div role="heading" class="note-title marker" id="h-note-59" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#compressFormat"><code>dcat:compressFormat</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The compression format of the distribution in which the data is contained in a compressed form, e.g., to reduce the size of the downloadable file.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/MediaType"><code>dcterms:MediaType</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>This property to be used when the files in the distribution are compressed, e.g., in a ZIP file. The format <em class="rfc2119">SHOULD</em> be expressed using a media type as defined by IANA [<cite><a class="bibref" data-link-type="biblio" href="#bib-iana-media-types" title="Media Types">IANA-MEDIA-TYPES</a></cite>], if available.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:distribution_packaging_format" class="sec-ref"><bdi class="secno">6.8.19 </bdi>Property: packaging format</a>.</td></tr> </tbody></table> <p>For examples on the use of this property, see <a href="#examples-compressed-and-packaged-distributions" class="sec-ref"><bdi class="secno">C.5 </bdi>Compressed and packaged distributions</a>.</p> </section> <section id="Property:distribution_packaging_format"><div class="header-wrapper"><h4 id="x6-8-19-property-packaging-format"><bdi class="secno">6.8.19 </bdi>Property: packaging format</h4><a class="self-link" href="#Property:distribution_packaging_format" aria-label="Permalink for Section 6.8.19"></a></div> <div class="note" role="note" id="issue-container-generatedID-61"><div role="heading" class="note-title marker" id="h-note-60" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#packageFormat"><code>dcat:packageFormat</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The package format of the distribution in which one or more data files are grouped together, e.g., to enable a set of related files to be downloaded together.</td></tr> <tr><th class="prop">Range:</th><td><a href="http://purl.org/dc/terms/MediaType"><code>dcterms:MediaType</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>This property to be used when the files in the distribution are packaged, e.g., in a <a href="https://en.wikipedia.org/wiki/Tar_(computing)">TAR file</a>, a <a href="https://en.wikipedia.org/wiki/ZIP_(file_format)">ZIP file</a>, a <a href="https://specs.frictionlessdata.io/data-package/">Frictionless Data Package</a> or a <a href="https://datatracker.ietf.org/doc/html/draft-kunze-bagit-14">Bagit</a> file. The format <em class="rfc2119">SHOULD</em> be expressed using a media type as defined by IANA [<cite><a class="bibref" data-link-type="biblio" href="#bib-iana-media-types" title="Media Types">IANA-MEDIA-TYPES</a></cite>], if available.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:distribution_compression_format" class="sec-ref"><bdi class="secno">6.8.18 </bdi>Property: compression format</a>.</td></tr> </tbody></table> <p>For examples on the use of this property, see <a href="#examples-compressed-and-packaged-distributions" class="sec-ref"><bdi class="secno">C.5 </bdi>Compressed and packaged distributions</a>.</p> </section> <section id="Property:distribution_checksum"><div class="header-wrapper"><h4 id="x6-8-20-property-checksum"><bdi class="secno">6.8.20 </bdi>Property: checksum</h4><a class="self-link" href="#Property:distribution_checksum" aria-label="Permalink for Section 6.8.20"></a></div> <div class="note" role="note" id="issue-container-generatedID-62"><div role="heading" class="note-title marker" id="h-note-61" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr> <th>RDF Property:</th> <td><a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e1930"><code title="http://spdx.org/rdf/terms#checksum">spdx:checksum</code></a></td> </tr> <tr> <th class="prop">Definition:</th> <td>The checksum property provides a mechanism that can be used to verify that the contents of a file or package have not changed [<cite><a class="bibref" data-link-type="biblio" href="#bib-spdx" title="SPDX 2.2">SPDX</a></cite>].</td> </tr> <tr> <th class="prop">Range:</th> <td><a href="#Class:Checksum"><code title="http://spdx.org/rdf/terms#Checksum">spdx:Checksum</code></a></td> </tr> <tr> <th class="prop">Usage note:</th> <td> <p>The checksum is related to the download URL.</p> </td> </tr> </tbody></table> </section> </section> <section id="Class:Data_Service"><div class="header-wrapper"><h3 id="x6-9-class-data-service"><bdi class="secno">6.9 </bdi>Class: Data Service</h3><a class="self-link" href="#Class:Data_Service" aria-label="Permalink for Section 6.9"></a></div> <div class="note" role="note" id="issue-container-generatedID-63"><div role="heading" class="note-title marker" id="h-note-62" aria-level="4"><span>Note</span></div><aside class=""> <p> Class added in DCAT 2. </p> </aside></div> <p>The following properties are specific to this class: <a href="#Property:data_service_endpoint_description">endpoint description</a>, <a href="#Property:data_service_endpoint_url">endpoint URL</a>, <a href="#Property:data_service_serves_dataset">serves dataset</a>. </p> <p>The following properties of the super-class <a href="#Class:Resource"><code>dcat:Resource</code></a> are also available for use:</p> <ul class="prop-list"> <li><a href="#Property:resource_access_rights">access rights</a></li> <li><a href="#Property:resource_conforms_to">conforms to</a></li> <li><a href="#Property:resource_contact_point">contact point</a></li> <li><a href="#Property:resource_creator">creator</a></li> <li><a href="#Property:resource_description">description</a></li> <li><a href="#Property:resource_has_policy">has policy</a></li> <li><a href="#Property:resource_identifier">identifier</a></li> <li><a href="#Property:resource_is_referenced_by">is referenced by</a></li> <li><a href="#Property:resource_keyword">keyword/tag</a></li> <li><a href="#Property:resource_landing_page">landing page</a></li> <li><a href="#Property:resource_license">license</a></li> <li><a href="#Property:resource_language">language</a></li> <li><a href="#Property:resource_relation">relation</a></li> <li><a href="#Property:resource_rights">rights</a></li> <li><a href="#Property:resource_qualified_relation">qualified relation</a></li> <li><a href="#Property:resource_publisher">publisher</a></li> <li><a href="#Property:resource_release_date">release date</a></li> <li><a href="#Property:resource_theme">theme/category</a></li> <li><a href="#Property:resource_title">title</a></li> <li><a href="#Property:resource_type">type/genre</a></li> <li><a href="#Property:resource_update_date">update/modification date</a></li> <li><a href="#Property:resource_qualified_attribution">qualified attribution</a></li> <li><a href="#Property:resource_has_current_version">has current version</a></li> <li><a href="#Property:resource_has_version">has version</a></li> <li><a href="#Property:resource_previous_version">previous version</a></li> <li><a href="#Property:resource_replaces">replaces</a></li> <li><a href="#Property:resource_status">status</a></li> <li><a href="#Property:resource_version">version</a></li> <li><a href="#Property:resource_version_notes">version notes</a></li> <li><a href="#Property:resource_first">first</a></li> <li><a href="#Property:resource_last">last</a></li> <li><a href="#Property:resource_previous">previous</a></li> </ul> <table class="def"> <tbody><tr><th>RDF Class:</th><td><a href="https://www.w3.org/ns/dcat#DataService"><code>dcat:DataService</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A collection of operations that provides access to one or more datasets or data processing functions.</td></tr> <tr><th class="prop">Sub-class of:</th><td><a href="#Class:Resource"><code>dcat:Resource</code></a></td></tr> <tr><th class="prop">Sub-class of:</th><td><a href="http://purl.org/dc/dcmitype/Service"><code>dctype:Service</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>If a <a href="#Class:Data_Service"><code>dcat:DataService</code></a> is bound to one or more specified Datasets, they are indicated by the <a href="#Property:data_service_serves_dataset"><code>dcat:servesDataset</code></a> property.</td></tr> <tr><th class="prop">Usage note:</th><td>The kind of service can be indicated using the <a href="http://purl.org/dc/terms/type"><code>dcterms:type</code></a> property. Its value may be taken from a controlled vocabulary such as the INSPIRE spatial data service type code list [<cite><a class="bibref" data-link-type="biblio" href="#bib-inspire-sdst" title="INSPIRE Registry: Spatial data service types">INSPIRE-SDST</a></cite>].</td></tr> </tbody></table> <p>For examples on the use of this class and related properties, see <a href="#examples-data-service" class="sec-ref"><bdi class="secno">C.4 </bdi>Data services</a>.</p> <section id="Property:data_service_endpoint_url"><div class="header-wrapper"><h4 id="x6-9-1-property-endpoint-url"><bdi class="secno">6.9.1 </bdi>Property: endpoint URL</h4><a class="self-link" href="#Property:data_service_endpoint_url" aria-label="Permalink for Section 6.9.1"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#endpointURL"><code>dcat:endpointURL</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The root location or primary endpoint of the service (a Web-resolvable <abbr title="Internationalized Resource Identifier">IRI</abbr>).</td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Data_Service"><code>dcat:DataService</code></a> </td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Resource"><code>rdfs:Resource</code></a> </td></tr> </tbody></table> </section> <section id="Property:data_service_endpoint_description"><div class="header-wrapper"><h4 id="x6-9-2-property-endpoint-description"><bdi class="secno">6.9.2 </bdi>Property: endpoint description</h4><a class="self-link" href="#Property:data_service_endpoint_description" aria-label="Permalink for Section 6.9.2"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#endpointDescription"><code>dcat:endpointDescription</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A description of the services available via the end-points, including their operations, parameters etc.</td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Data_Service"><code>dcat:DataService</code></a> </td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/2000/01/rdf-schema#Resource"><code>rdfs:Resource</code></a> </td></tr> <tr><th class="prop">Usage note:</th><td>The endpoint description gives specific details of the actual endpoint instances, while <a href="#Property:resource_conforms_to"><code>dcterms:conformsTo</code></a> is used to indicate the general standard or specification that the endpoints implement.</td></tr> <tr><th class="prop">Usage note:</th><td>An endpoint description may be expressed in a machine-readable form, such as an OpenAPI (Swagger) description [<cite><a class="bibref" data-link-type="biblio" href="#bib-openapi" title="OpenAPI Specification">OpenAPI</a></cite>], an OGC <code>GetCapabilities</code> response [<cite><a class="bibref" data-link-type="biblio" href="#bib-wfs" title="Web Feature Service 2.0 Interface Standard">WFS</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19142" title="Geographic information -- Web Feature Service">ISO-19142</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-wms" title="Web Map Service Implementation Specification">WMS</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19128" title="Geographic information -- Web map server interface">ISO-19128</a></cite>], a SPARQL Service Description [<cite><a class="bibref" data-link-type="biblio" href="#bib-sparql11-service-description" title="SPARQL 1.1 Service Description">SPARQL11-SERVICE-DESCRIPTION</a></cite>], an [<cite><a class="bibref" data-link-type="biblio" href="#bib-opensearch" title="OpenSearch 1.1 Draft 6">OpenSearch</a></cite>] or [<cite><a class="bibref" data-link-type="biblio" href="#bib-wsdl20" title="Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language">WSDL20</a></cite>] document, a Hydra <abbr title="Application Programming Interface">API</abbr> description [<cite><a class="bibref" data-link-type="biblio" href="#bib-hydra" title="Hydra Core Vocabulary">HYDRA</a></cite>], else in text or some other informal mode if a formal representation is not possible.</td></tr> </tbody></table> </section> <section id="Property:data_service_serves_dataset"><div class="header-wrapper"><h4 id="x6-9-3-property-serves-dataset"><bdi class="secno">6.9.3 </bdi>Property: serves dataset</h4><a class="self-link" href="#Property:data_service_serves_dataset" aria-label="Permalink for Section 6.9.3"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#servesDataset"><code>dcat:servesDataset</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A collection of data that this data service can distribute.</td></tr> <tr><th class="prop">Range:</th><td><a href="#Class:Dataset"><code>dcat:Dataset</code></a></td></tr> </tbody></table> </section> </section> <section id="Class:Concept_Scheme"><div class="header-wrapper"><h3 id="x6-10-class-concept-scheme"><bdi class="secno">6.10 </bdi>Class: Concept Scheme</h3><a class="self-link" href="#Class:Concept_Scheme" aria-label="Permalink for Section 6.10"></a></div> <table class="def"> <tbody><tr><th>RDF Class:</th><td><a href="https://www.w3.org/2004/02/skos/core#ConceptScheme"><code>skos:ConceptScheme</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A knowledge organization system (KOS) used to represent themes/categories of datasets in the catalog.</td></tr> <tr><th class="prop">See also:</th><td><a href="#Property:catalog_themes" class="sec-ref"><bdi class="secno">6.3.2 </bdi>Property: themes</a>, <a href="#Property:resource_theme" class="sec-ref"><bdi class="secno">6.4.12 </bdi>Property: theme/category</a></td></tr> </tbody></table> </section> <section id="Class:Concept"><div class="header-wrapper"><h3 id="x6-11-class-concept"><bdi class="secno">6.11 </bdi>Class: Concept</h3><a class="self-link" href="#Class:Concept" aria-label="Permalink for Section 6.11"></a></div> <table class="def"> <tbody><tr> <th>RDF Class:</th> <td><a href="https://www.w3.org/2004/02/skos/core#Concept"><code>skos:Concept</code></a></td></tr> <tr> <th class="prop">Definition:</th> <td>A category or a theme used to describe datasets in the catalog.</td> </tr> <tr> <th class="prop">Usage note:</th> <td>It is recommended to use either <code>skos:inScheme</code> or <code>skos:topConceptOf</code> on every <code>skos:Concept</code> used to classify datasets to link it to the concept scheme it belongs to. This concept scheme is typically associated with the catalog using <code>dcat:themeTaxonomy</code>.</td> </tr> <tr> <th class="prop">See also:</th> <td><a href="#Property:catalog_themes" class="sec-ref"><bdi class="secno">6.3.2 </bdi>Property: themes</a>, <a href="#Property:resource_theme" class="sec-ref"><bdi class="secno">6.4.12 </bdi>Property: theme/category</a></td> </tr> </tbody></table> </section> <section id="Class:Organization_Person"><div class="header-wrapper"><h3 id="x6-12-class-organization-person"><bdi class="secno">6.12 </bdi>Class: Organization/Person</h3><a class="self-link" href="#Class:Organization_Person" aria-label="Permalink for Section 6.12"></a></div> <table class="def"> <tbody><tr> <th>RDF Classes:</th> <td> <p><a href="http://xmlns.com/foaf/0.1/Person"><code>foaf:Person</code></a> (for people)</p> <p><a href="http://xmlns.com/foaf/0.1/Organization"><code>foaf:Organization</code></a> (for government agencies or other entities)</p> </td> </tr> <tr><th class="prop">Sub-class of:</th><td><a href="http://xmlns.com/foaf/0.1/Agent"><code>foaf:Agent</code></a></td></tr> <tr> <th class="prop">Usage note:</th> <td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-foaf" title="FOAF Vocabulary Specification 0.99 (Paddington Edition)">FOAF</a></cite>] provides several properties to describe these entities.</td> </tr> </tbody></table> </section> <section id="Class:Relationship"><div class="header-wrapper"><h3 id="x6-13-class-relationship"><bdi class="secno">6.13 </bdi>Class: Relationship</h3><a class="self-link" href="#Class:Relationship" aria-label="Permalink for Section 6.13"></a></div> <div class="note" role="note" id="issue-container-generatedID-64"><div role="heading" class="note-title marker" id="h-note-63" aria-level="4"><span>Note</span></div><aside class=""> <p> Class added in DCAT 2. </p> </aside></div> <p>The following properties are specific to this class: <a href="#Property:relationship_relation">relation</a>, <a href="#Property:relationship_hadRole">had role</a>. </p> <p>Examples illustrating use of this class and its properties are given in <a href="#qualified-forms" class="sec-ref"><bdi class="secno">15. </bdi>Qualified relations</a>.</p> <table class="def"> <tbody><tr><th>RDF Class:</th><td><a href="https://www.w3.org/ns/dcat#Relationship"><code>dcat:Relationship</code></a></td></tr> <tr><th class="prop">Definition:</th><td>An association class for attaching additional information to a relationship between DCAT Resources</td></tr> <tr><th class="prop">Sub-class of:</th><td><a href="https://www.w3.org/TR/prov-o/#EntityInfluence"><code>prov:EntityInfluence</code></a></td></tr> <tr><th class="prop">Usage note:</th><td> Use to characterize a relationship between datasets, and potentially other resources, where the nature of the relationship is known but is not adequately characterized by the standard [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] properties (<a href="http://purl.org/dc/terms/hasPart"><code>dcterms:hasPart</code></a>, <a href="http://purl.org/dc/terms/isPartOf"><code>dcterms:isPartOf</code></a>, <a href="http://purl.org/dc/terms/conformsTo"><code>dcterms:conformsTo</code></a>, <a href="http://purl.org/dc/terms/isFormatOf"><code>dcterms:isFormatOf</code></a>, <a href="http://purl.org/dc/terms/hasFormat"><code>dcterms:hasFormat</code></a>, <a href="http://purl.org/dc/terms/isVersionOf"><code>dcterms:isVersionOf</code></a>, <a href="http://purl.org/dc/terms/hasVersion"><code>dcterms:hasVersion</code></a>, <a href="http://purl.org/dc/terms/replaces"><code>dcterms:replaces</code></a>, <a href="http://purl.org/dc/terms/isReplacedBy"><code>dcterms:isReplacedBy</code></a>, <a href="http://purl.org/dc/terms/references"><code>dcterms:references</code></a>, <a href="http://purl.org/dc/terms/isReferencedBy"><code>dcterms:isReferencedBy</code></a>, <a href="http://purl.org/dc/terms/requires"><code>dcterms:requires</code></a>, <a href="http://purl.org/dc/terms/isRequiredBy"><code>dcterms:isRequiredBy</code></a>) or [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] properties (<a href="https://www.w3.org/TR/prov-o/#wasDerivedFrom"><code>prov:wasDerivedFrom</code></a>, <a href="https://www.w3.org/TR/prov-o/#wasInfluencedBy"><code>prov:wasInfluencedBy</code></a>, <a href="https://www.w3.org/TR/prov-o/#wasQuotedFrom"><code>prov:wasQuotedFrom</code></a>, <a href="https://www.w3.org/TR/prov-o/#wasRevisionOf"><code>prov:wasRevisionOf</code></a>, <a href="https://www.w3.org/TR/prov-o/#hadPrimarySource"><code>prov:hadPrimarySource</code></a>, <a href="https://www.w3.org/TR/prov-o/#alternateOf"><code>prov:alternateOf</code></a>, <a href="https://www.w3.org/TR/prov-o/#specializationOf"><code>prov:specializationOf</code></a>) </td> </tr> </tbody></table> <section id="Property:relationship_relation"><div class="header-wrapper"><h4 id="x6-13-1-property-relation"><bdi class="secno">6.13.1 </bdi>Property: relation</h4><a class="self-link" href="#Property:relationship_relation" aria-label="Permalink for Section 6.13.1"></a></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="http://purl.org/dc/terms/relation"><code>dcterms:relation</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The resource related to the source resource.</td></tr> <tr><th class="prop">Usage note:</th><td>In the context of a <code>dcat:Relationship</code> this is expected to point to another <code>dcat:Dataset</code> or other cataloged resource.</td></tr> </tbody></table> </section> <section id="Property:relationship_hadRole"><div class="header-wrapper"><h4 id="x6-13-2-property-had-role"><bdi class="secno">6.13.2 </bdi>Property: had role</h4><a class="self-link" href="#Property:relationship_hadRole" aria-label="Permalink for Section 6.13.2"></a></div> <div class="note" role="note" id="issue-container-generatedID-65"><div role="heading" class="note-title marker" id="h-note-64" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th><td><a href="https://www.w3.org/ns/dcat#hadRole"><code>dcat:hadRole</code></a></td></tr> <tr><th class="prop">Definition:</th><td>The function of an entity or agent with respect to another entity or resource.</td></tr> <tr><th class="prop">Domain:</th><td><a href="https://www.w3.org/TR/prov-o/#Attribution"><code>prov:Attribution</code></a> or <a href="#Class:Relationship"><code>dcat:Relationship</code></a></td></tr> <tr><th class="prop">Range:</th><td><a href="#Class:Role"><code>dcat:Role</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>May be used in a qualified-attribution to specify the role of an Agent with respect to an Entity. It is recommended that the value be taken from a controlled vocabulary of agent roles, such as [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115" title="Geographic information -- Metadata">ISO-19115</a></cite>] <a href="https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml"><code>CI_RoleCode</code></a>.</td></tr> <tr><th class="prop">Usage note:</th><td>May be used in a qualified-relation to specify the role of an Entity with respect to another Entity. It is recommended that the value be taken from a controlled vocabulary of entity roles.</td></tr> </tbody></table> <p> This DCAT property complements <a href="https://www.w3.org/TR/prov-o/#hadRole"><code>prov:hadRole</code></a> which provides the function of an entity or agent with respect to an activity. </p> </section> </section> <section id="Class:Role"><div class="header-wrapper"><h3 id="x6-14-class-role"><bdi class="secno">6.14 </bdi>Class: Role</h3><a class="self-link" href="#Class:Role" aria-label="Permalink for Section 6.14"></a></div> <div class="note" role="note" id="issue-container-generatedID-66"><div role="heading" class="note-title marker" id="h-note-65" aria-level="4"><span>Note</span></div><aside class=""> <p> Class added in DCAT 2. </p> </aside></div> <p>Examples illustrating use of this class are given in <a href="#qualified-forms" class="sec-ref"><bdi class="secno">15. </bdi>Qualified relations</a>.</p> <table class="def"> <tbody><tr><th>RDF Class:</th><td><a href="https://www.w3.org/ns/dcat#Role"><code>dcat:Role</code></a></td></tr> <tr><th class="prop">Definition:</th><td>A role is the function of a resource or agent with respect to another resource, in the context of resource attribution or resource relationships.</td></tr> <tr><th class="prop">Sub-class of:</th><td><a href="https://www.w3.org/2004/02/skos/core#Concept"><code>skos:Concept</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>Used in a qualified-attribution to specify the role of an Agent with respect to an Entity. It is recommended that the values be managed as a controlled vocabulary of agent roles, such as [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115-1" title="Geographic information -- Metadata -- Part 1: Fundamentals">ISO-19115-1</a></cite>] <a href="https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml"><code>CI_RoleCode</code></a>.</td></tr> <tr><th class="prop">Usage note:</th><td> <p>Used in a qualified-relation to specify the role of an Entity with respect to another Entity. It is recommended that the values be managed as a controlled vocabulary of entity roles such as</p> <ul> <li>[<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115-1" title="Geographic information -- Metadata -- Part 1: Fundamentals">ISO-19115-1</a></cite>] <a href="https://standards.iso.org/iso/19115/resources/Codelists/gml/DS_AssociationTypeCode.xml"><code>DS_AssociationTypeCode</code></a></li> <li>IANA Registry of Link Relations [<cite><a class="bibref" data-link-type="biblio" href="#bib-iana-relations" title="Link Relations">IANA-RELATIONS</a></cite>]</li> <li>DataCite metadata schema [<cite><a class="bibref" data-link-type="biblio" href="#bib-datacite" title="DataCite Metadata Schema">DataCite</a></cite>]</li> <li><a href="https://id.loc.gov/vocabulary/relators">MARC relators</a></li> </ul> </td></tr> </tbody></table> <p> This DCAT class complements <a href="https://www.w3.org/TR/prov-o/#Role"><code>prov:Role</code></a> which provides the function of an entity or agent with respect to an activity. </p> </section> <section id="Class:Period_of_Time"><div class="header-wrapper"><h3 id="x6-15-class-period-of-time"><bdi class="secno">6.15 </bdi>Class: Period of Time</h3><a class="self-link" href="#Class:Period_of_Time" aria-label="Permalink for Section 6.15"></a></div> <div class="note" role="note" id="issue-container-generatedID-67"><div role="heading" class="note-title marker" id="h-note-66" aria-level="4"><span>Note</span></div><aside class=""> <p> Class added in this context in DCAT 2. </p> </aside></div> <p>The following properties are specific to this class: <a href="#Property:period_start_date">start date</a>, <a href="#Property:period_end_date">end date</a>. <a href="#Property:period_has_beginning">beginning</a>, <a href="#Property:period_has_end">end</a>. </p> <p> Examples illustrating use of these options for the temporal coverage of a dataset are given in <a href="#temporal-properties" class="sec-ref"><bdi class="secno">10.1 </bdi>Temporal properties</a>. </p> <table class="def"> <tbody><tr> <th>RDF Class:</th> <td><a href="http://purl.org/dc/terms/PeriodOfTime"><code title="http://purl.org/dc/terms/PeriodOfTime">dcterms:PeriodOfTime</code></a></td> </tr> <tr> <th class="prop">Definition:</th> <td>An interval of time that is named or defined by its start and end.</td> </tr> <tr> <th class="prop">Usage note:</th> <td>The start and end of the interval <em class="rfc2119">SHOULD</em> be given by using properties <a href="#Property:period_start_date"><code title="http://www.w3.org/ns/dcat#startDate">dcat:startDate</code></a> or <a href="#Property:period_has_beginning"><code title="http://www.w3.org/2006/time#hasBeginning">time:hasBeginning</code></a>, and <a href="#Property:period_end_date"><code title="http://www.w3.org/ns/dcat#endDate">dcat:endDate</code></a> or <a href="#Property:period_has_end"><code title="http://www.w3.org/2006/time#hasEnd">time:hasEnd</code></a>, respectively. The interval can also be open - i.e., it can have just a start or just an end.</td> </tr> </tbody></table> <section id="Property:period_start_date"><div class="header-wrapper"><h4 id="x6-15-1-property-start-date"><bdi class="secno">6.15.1 </bdi>Property: start date</h4><a class="self-link" href="#Property:period_start_date" aria-label="Permalink for Section 6.15.1"></a></div> <div class="note" role="note" id="issue-container-generatedID-68"><div role="heading" class="note-title marker" id="h-note-67" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr> <th>RDF Property:</th> <td><a href="https://www.w3.org/ns/dcat#startDate"><code title="http://www.w3.org/ns/dcat#startDate">dcat:startDate</code></a></td> </tr> <tr> <th class="prop">Definition:</th> <td>The start of the period.</td> </tr> <tr> <th class="prop">Domain:</th> <td><a href="#Class:Period_of_Time"><code title="http://purl.org/dc/terms/PeriodOfTime">dcterms:PeriodOfTime</code></a></td> </tr> <tr><th class="prop">Range:</th><td><a title="http://www.w3.org/2000/01/rdf-schema#Literal" href="https://www.w3.org/TR/rdf-schema/#ch_literal"><code>rdfs:Literal</code></a> encoded using the relevant <abbr title="International Organization for Standardization">ISO</abbr> 8601 Date and Time compliant string [<cite><a class="bibref" data-link-type="biblio" href="#bib-datetime" title="Date and Time Formats">DATETIME</a></cite>] and typed using the appropriate XML Schema datatype [<cite><a class="bibref" data-link-type="biblio" href="#bib-xmlschema11-2" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">XMLSCHEMA11-2</a></cite>] (<a href="https://www.w3.org/TR/xmlschema11-2/#gYear"><code>xsd:gYear</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#gYearMonth"><code>xsd:gYearMonth</code></a>, <a href="https://www.w3.org/TR/xmlschema11-2/#date"><code>xsd:date</code></a>, or <a href="https://www.w3.org/TR/xmlschema11-2/#dateTime"><code>xsd:dateTime</code></a>).</td></tr> </tbody></table> </section> <section id="Property:period_end_date"><div class="header-wrapper"><h4 id="x6-15-2-property-end-date"><bdi class="secno">6.15.2 </bdi>Property: end date</h4><a class="self-link" href="#Property:period_end_date" aria-label="Permalink for Section 6.15.2"></a></div> <div class="note" role="note" id="issue-container-generatedID-69"><div role="heading" class="note-title marker" id="h-note-68" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr> <th>RDF Property:</th> <td><a href="https://www.w3.org/ns/dcat#endDate"><code title="http://www.w3.org/ns/dcat#endDate">dcat:endDate</code></a></td> </tr> <tr><th class="prop">Definition:</th><td>The end of the period.</td></tr> <tr><th class="prop">Domain:</th><td><a href="#Class:Period_of_Time"><code title="http://purl.org/dc/terms/PeriodOfTime">dcterms:PeriodOfTime</code></a></td></tr> <tr><th class="prop">Range:</th><td><a title="http://www.w3.org/2000/01/rdf-schema#Literal" href="https://www.w3.org/TR/rdf-schema/#ch_literal"><code>rdfs:Literal</code></a> encoded using the relevant <abbr title="International Organization for Standardization">ISO</abbr> 8601 Date and Time compliant string [<cite><a class="bibref" data-link-type="biblio" href="#bib-datetime" title="Date and Time Formats">DATETIME</a></cite>] and typed using the appropriate XML Schema datatype [<cite><a class="bibref" data-link-type="biblio" href="#bib-xmlschema11-2" title="W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes">XMLSCHEMA11-2</a></cite>]</td></tr> </tbody></table> </section> <section id="Property:period_has_beginning"><div class="header-wrapper"><h4 id="x6-15-3-property-beginning"><bdi class="secno">6.15.3 </bdi>Property: beginning</h4><a class="self-link" href="#Property:period_has_beginning" aria-label="Permalink for Section 6.15.3"></a></div> <div class="note" role="note" id="issue-container-generatedID-70"><div role="heading" class="note-title marker" id="h-note-69" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in this context in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr> <th>RDF Property:</th> <td><a href="https://www.w3.org/TR/owl-time/#time:hasBeginning"><code title="http://www.w3.org/2006/time#hasBeginning">time:hasBeginning</code></a></td> </tr> <tr><th class="prop">Definition:</th><td>Beginning of a period or interval.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/TR/owl-time/#time:Instant"><code title="http://www.w3.org/2006/time#Instant">time:Instant</code></a></td></tr> <tr> <th class="prop">Usage note:</th> <td>Use of the property <code>time:hasBeginning</code> entails that value of the <code>dcterms:temporal</code> property is a member of the <code>time:TemporalEntity</code> class from [<cite><a class="bibref" data-link-type="biblio" href="#bib-owl-time" title="Time Ontology in OWL">OWL-TIME</a></cite>]. In this context this could be taken to imply that <code>dcterms:PeriodOfTime</code> is equivalent to the sub-class <a href="https://www.w3.org/TR/owl-time/#time:ProperInterval"><code title="http://www.w3.org/2006/time#ProperInterval">time:ProperInterval</code></a></td> </tr> </tbody></table> <div class="note" role="note" id="issue-container-generatedID-71"><div role="heading" class="note-title marker" id="h-note-70" aria-level="5"><span>Note</span></div><aside class=""> <p> The value of <a href="https://www.w3.org/TR/owl-time/#time:hasBeginning"><code title="http://www.w3.org/2006/time#hasBeginning">time:hasEnd</code></a> is a <a title="http://www.w3.org/2006/time#Instant" href="https://www.w3.org/TR/owl-time/#time:Instant"><code>time:Instant</code></a> for whose position several options are available. In particular times that do not use the conventional Gregorian calendar can be expressed, such as geological and archeological periods, and times given as numeric positions on a time-line. </p> </aside></div> </section> <section id="Property:period_has_end"><div class="header-wrapper"><h4 id="x6-15-4-property-end"><bdi class="secno">6.15.4 </bdi>Property: end</h4><a class="self-link" href="#Property:period_has_end" aria-label="Permalink for Section 6.15.4"></a></div> <div class="note" role="note" id="issue-container-generatedID-72"><div role="heading" class="note-title marker" id="h-note-71" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in this context in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr> <th>RDF Property:</th> <td><a href="https://www.w3.org/TR/owl-time/#time:hasEnd"><code title="http://www.w3.org/2006/time#hasEnd">time:hasEnd</code></a></td> </tr> <tr><th class="prop">Definition:</th><td>End of a period or interval.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/TR/owl-time/#time:Instant"><code title="http://www.w3.org/2006/time#Instant">time:Instant</code></a></td></tr> <tr> <th class="prop">Usage note:</th> <td>Use of the property <code>time:hasEnd</code> entails that value of the <code>dcterms:temporal</code> property is a member of the <code>time:TemporalEntity</code> class from [<cite><a class="bibref" data-link-type="biblio" href="#bib-owl-time" title="Time Ontology in OWL">OWL-TIME</a></cite>]. In this context this could be taken to imply that <code>dcterms:PeriodOfTime</code> is equivalent to the sub-class <a href="https://www.w3.org/TR/owl-time/#time:ProperInterval"><code title="http://www.w3.org/2006/time#ProperInterval">time:ProperInterval</code></a></td> </tr> </tbody></table> <div class="note" role="note" id="issue-container-generatedID-73"><div role="heading" class="note-title marker" id="h-note-72" aria-level="5"><span>Note</span></div><aside class=""> <p> The value of <a href="https://www.w3.org/TR/owl-time/#time:hasEnd"><code title="http://www.w3.org/2006/time#hasEnd">time:hasEnd</code></a> is a <a title="http://www.w3.org/2006/time#Instant" href="https://www.w3.org/TR/owl-time/#time:Instant"><code>time:Instant</code></a> for whose position several options are available. In particular times that do not use the conventional Gregorian calendar can be expressed, such as geological and archeological periods, and times given as numeric positions on a time-line. </p> </aside></div> </section> </section> <section id="Class:Location"><div class="header-wrapper"><h3 id="x6-16-class-location"><bdi class="secno">6.16 </bdi>Class: Location</h3><a class="self-link" href="#Class:Location" aria-label="Permalink for Section 6.16"></a></div> <div class="note" role="note" id="issue-container-generatedID-74"><div role="heading" class="note-title marker" id="h-note-73" aria-level="4"><span>Note</span></div><aside class=""> <p> Class added in this context in DCAT 2. </p> </aside></div> <p>The following properties are specific to this class: <a href="#Property:location_geometry">geometry</a>, <a href="#Property:location_bbox">bounding box</a>, <a href="#Property:location_centroid">centroid</a>. </p> <p> Examples illustrating use of these options for the spatial coverage of a dataset are given in <a href="#spatial-properties" class="sec-ref"><bdi class="secno">10.2 </bdi>Spatial properties</a>. </p> <table class="def"> <tbody><tr> <th>RDF Class:</th> <td><a href="http://purl.org/dc/terms/Location"><code title="http://purl.org/dc/terms/Location">dcterms:Location</code></a></td> </tr> <tr> <th class="prop">Definition:</th> <td>A spatial region or named place.</td> </tr> <tr> <th class="prop">Usage note:</th> <td> <ul> <li>For an extensive geometry (i.e., a set of coordinates denoting the vertices of the relevant geographic area), the property <a href="#Property:location_geometry"><code title="http://www.w3.org/ns/locn#geometry">locn:geometry</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-locn" title="ISA Programme Location Core Vocabulary">LOCN</a></cite>] <em class="rfc2119">SHOULD</em> be used.</li> <li>For a geographic bounding box delimiting a spatial area the property <a href="#Property:location_bbox"><code title="http://www.w3.org/ns/dcat#bbox">dcat:bbox</code></a> <em class="rfc2119">SHOULD</em> be used.</li> <li>For the geographic center of a spatial area, or another characteristic point, the property <a href="#Property:location_centroid"><code title="http://www.w3.org/ns/dcat#centroid">dcat:centroid</code></a> <em class="rfc2119">SHOULD</em> be used.</li> </ul> </td> </tr> </tbody></table> <section id="Property:location_geometry"><div class="header-wrapper"><h4 id="x6-16-1-property-geometry"><bdi class="secno">6.16.1 </bdi>Property: geometry</h4><a class="self-link" href="#Property:location_geometry" aria-label="Permalink for Section 6.16.1"></a></div> <div class="note" role="note" id="issue-container-generatedID-75"><div role="heading" class="note-title marker" id="h-note-74" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in this context in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr> <th>RDF Property:</th> <td><a href="https://www.w3.org/ns/locn#locn:geometry"><code title="http://www.w3.org/ns/locn#geometry">locn:geometry</code></a></td> </tr> <tr><th class="prop">Definition:</th><td>Associates a spatial thing [<cite><a class="bibref" data-link-type="biblio" href="#bib-sdw-bp" title="Spatial Data on the Web Best Practices">SDW-BP</a></cite>] with a corresponding geometry.</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/ns/locn#locn:Geometry"><code title="https://www.w3.org/ns/locn#Geometry">locn:Geometry</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>The range of this property (<code title="https://www.w3.org/ns/locn#Geometry">locn:Geometry</code>) allows for any type of geometry specification. E.g., the geometry could be encoded by a literal, as <abbr title="Well-known Text">WKT</abbr> (<a href="http://www.opengis.net/ont/geosparql#wktLiteral"><code title="http://www.opengis.net/ont/geosparql#wktLiteral">geosparql:wktLiteral</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-geosparql" title="OGC GeoSPARQL - A Geographic Query Language for RDF Data">GeoSPARQL</a></cite>]), or represented by a class, as <a href="http://www.opengis.net/ont/geosparql#Geometry"><code title="http://www.opengis.net/ont/geosparql#Geometry">geosparql:Geometry</code></a> (or any of its subclasses) [<cite><a class="bibref" data-link-type="biblio" href="#bib-geosparql" title="OGC GeoSPARQL - A Geographic Query Language for RDF Data">GeoSPARQL</a></cite>].</td></tr> </tbody></table> </section> <section id="Property:location_bbox"><div class="header-wrapper"><h4 id="x6-16-2-property-bounding-box"><bdi class="secno">6.16.2 </bdi>Property: bounding box</h4><a class="self-link" href="#Property:location_bbox" aria-label="Permalink for Section 6.16.2"></a></div> <div class="note" role="note" id="issue-container-generatedID-76"><div role="heading" class="note-title marker" id="h-note-75" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr><th>RDF Property:</th> <td><a href="https://www.w3.org/ns/dcat#bbox"><code title="http://www.w3.org/ns/dcat#centroid">dcat:bbox</code></a></td> </tr> <tr><th class="prop">Definition:</th><td>The geographic bounding box of a spatial thing [<cite><a class="bibref" data-link-type="biblio" href="#bib-sdw-bp" title="Spatial Data on the Web Best Practices">SDW-BP</a></cite>].</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/TR/rdf-schema/#ch_literal"><code title="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>The range of this property (<code>rdfs:Literal</code>) is intentionally generic, with the purpose of allowing different geometry literal encodings. E.g., the geometry could be encoded as a <abbr title="Well-known Text">WKT</abbr> literal (<a href="http://www.opengis.net/ont/geosparql#wktLiteral"><code title="http://www.opengis.net/ont/geosparql#wktLiteral">geosparql:wktLiteral</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-geosparql" title="OGC GeoSPARQL - A Geographic Query Language for RDF Data">GeoSPARQL</a></cite>]).</td></tr> </tbody></table> <div class="note" role="note" id="issue-container-generatedID-77"><div role="heading" class="note-title marker" id="h-note-76" aria-level="5"><span>Note</span></div><aside class=""> <p> The <abbr title="Well-known Text">WKT</abbr> encoding supports geospatial positions expressed in coordinate reference systems other than <a href="https://en.wikipedia.org/wiki/World_Geodetic_System#WGS84">WGS84</a>. </p> </aside></div> </section> <section id="Property:location_centroid"><div class="header-wrapper"><h4 id="x6-16-3-property-centroid"><bdi class="secno">6.16.3 </bdi>Property: centroid</h4><a class="self-link" href="#Property:location_centroid" aria-label="Permalink for Section 6.16.3"></a></div> <div class="note" role="note" id="issue-container-generatedID-78"><div role="heading" class="note-title marker" id="h-note-77" aria-level="5"><span>Note</span></div><aside class=""> <p> Property added in DCAT 2. </p> </aside></div> <table class="def"> <tbody><tr> <th>RDF Property:</th> <td><a href="https://www.w3.org/ns/dcat#centroid"><code title="http://www.w3.org/ns/dcat#centroid">dcat:centroid</code></a></td> </tr> <tr><th class="prop">Definition:</th><td>The geographic center (centroid) of a spatial thing [<cite><a class="bibref" data-link-type="biblio" href="#bib-sdw-bp" title="Spatial Data on the Web Best Practices">SDW-BP</a></cite>].</td></tr> <tr><th class="prop">Range:</th><td><a href="https://www.w3.org/TR/rdf-schema/#ch_literal"><code title="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</code></a></td></tr> <tr><th class="prop">Usage note:</th><td>The range of this property (<code>rdfs:Literal</code>) is intentionally generic, with the purpose of allowing different geometry literal encodings. E.g., the geometry could be encoded as a <abbr title="Well-known Text">WKT</abbr> literal (<a href="http://www.opengis.net/ont/geosparql#wktLiteral"><code title="http://www.opengis.net/ont/geosparql#wktLiteral">geosparql:wktLiteral</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-geosparql" title="OGC GeoSPARQL - A Geographic Query Language for RDF Data">GeoSPARQL</a></cite>]).</td></tr> </tbody></table> <div class="note" role="note" id="issue-container-generatedID-79"><div role="heading" class="note-title marker" id="h-note-78" aria-level="5"><span>Note</span></div><aside class=""> <p> The <abbr title="Well-known Text">WKT</abbr> encoding supports geospatial positions expressed in coordinate reference systems other than <a href="https://en.wikipedia.org/wiki/World_Geodetic_System#WGS84">WGS84</a>. </p> </aside></div> </section> </section> <section id="Class:Checksum"><div class="header-wrapper"><h3 id="x6-17-class-checksum"><bdi class="secno">6.17 </bdi>Class: Checksum</h3><a class="self-link" href="#Class:Checksum" aria-label="Permalink for Section 6.17"></a></div> <div class="note" role="note" id="issue-container-generatedID-80"><div role="heading" class="note-title marker" id="h-note-79" aria-level="4"><span>Note</span></div><aside class=""> <p>Class added in DCAT 3.</p> </aside></div> <p>The following properties are specific to this class: <a href="#Property:checksum_algorithm">algorithm</a>, <a href="#Property:checksum_checksum_value">checksum value</a>. </p> <table class="def"> <tbody><tr> <th>RDF Class:</th> <td><a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e1930"><code title="http://spdx.org/rdf/terms#Checksum">spdx:Checksum</code></a></td> </tr> <tr> <th class="prop">Definition:</th> <td>A Checksum is a value that allows to check the integrity of the contents of a file. Even small changes to the content of the file will change its checksum. This class allows the results of a variety of checksum and cryptographic message digest algorithms to be represented [<cite><a class="bibref" data-link-type="biblio" href="#bib-spdx" title="SPDX 2.2">SPDX</a></cite>].</td> </tr> <tr> <th class="prop">Usage note:</th> <td>The Checksum includes the algorithm (<a href="#Property:checksum_algorithm"><code>spdx:algorithm</code></a>) and value (<a href="#Property:checksum_checksum_value"><code>spdx:checksumValue</code></a>) that allows the integrity of a file to be verified to ensure no errors occurred in transmission or storage.</td> </tr> </tbody></table> <section id="Property:checksum_algorithm"><div class="header-wrapper"><h4 id="x6-17-1-property-algorithm"><bdi class="secno">6.17.1 </bdi>Property: algorithm</h4><a class="self-link" href="#Property:checksum_algorithm" aria-label="Permalink for Section 6.17.1"></a></div> <div class="note" role="note" id="issue-container-generatedID-81"><div role="heading" class="note-title marker" id="h-note-80" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr> <th>RDF Property:</th> <td><a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e52"><code title="http://spdx.org/rdf/terms#algorithm">spdx:algorithm</code></a></td> </tr> <tr> <th class="prop">Definition:</th> <td>Identifies the algorithm used to produce the subject Checksum [<cite><a class="bibref" data-link-type="biblio" href="#bib-spdx" title="SPDX 2.2">SPDX</a></cite>].</td> </tr> <tr> <th class="prop">Domain:</th> <td><a href="#Class:Checksum"><code title="http://spdx.org/rdf/terms#Checksum">spdx:Checksum</code></a></td> </tr> <tr> <th class="prop">Range:</th> <td> <p>The set of individuals of class <a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e1968"><code title="http://spdx.org/rdf/terms#ChecksumAlgorithm">spdx:ChecksumAlgorithm</code></a>.</p> </td> </tr> <tr> <th class="prop">Usage note:</th> <td>Version 2.2 of [<cite><a class="bibref" data-link-type="biblio" href="#bib-spdx" title="SPDX 2.2">SPDX</a></cite>] defines individuals for the following algorithms: <a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e3691">MD2</a>, <a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e3704">MD4</a>, <a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e3717">MD5</a>, <a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e3731">MD6</a>, <a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e3744">SHA-1</a>, <a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e3757">SHA-224</a>, <a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e3771">SHA-256</a>, <a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e3784">SHA-384</a>, <a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e3797">SHA-512</a>. </td> </tr> </tbody></table> </section> <section id="Property:checksum_checksum_value"><div class="header-wrapper"><h4 id="x6-17-2-property-checksum-value"><bdi class="secno">6.17.2 </bdi>Property: checksum value</h4><a class="self-link" href="#Property:checksum_checksum_value" aria-label="Permalink for Section 6.17.2"></a></div> <div class="note" role="note" id="issue-container-generatedID-82"><div role="heading" class="note-title marker" id="h-note-81" aria-level="5"><span>Note</span></div><aside class=""> <p>Property added in DCAT 3.</p> </aside></div> <table class="def"> <tbody><tr> <th>RDF Property:</th> <td><a href="https://spdx.org/rdf/spdx-terms-v2.2/#d4e1111"><code title="http://spdx.org/rdf/terms#checksumValue">spdx:checksumValue</code></a></td> </tr> <tr> <th class="prop">Definition:</th> <td>The checksumValue property provides a lowercase hexadecimal encoded digest value produced using a specific algorithm [<cite><a class="bibref" data-link-type="biblio" href="#bib-spdx" title="SPDX 2.2">SPDX</a></cite>].</td> </tr> <tr> <th class="prop">Domain:</th> <td><a href="#Class:Checksum"><code title="http://spdx.org/rdf/terms#Checksum">spdx:Checksum</code></a></td> </tr> <tr> <th class="prop">Range:</th> <td><a href="https://www.w3.org/TR/xmlschema11-2/#hexBinary"><code title="http://www.w3.org/2001/XMLSchema#hexBinary">xsd:hexBinary</code></a></td> </tr> </tbody></table> </section> </section> </section> <section id="inverse-properties"><div class="header-wrapper"><h2 id="x7-use-of-inverse-properties"><bdi class="secno">7. </bdi>Use of inverse properties</h2><a class="self-link" href="#inverse-properties" aria-label="Permalink for Section 7."></a></div> <p>The properties described in <a href="#vocabulary-specification" class="sec-ref"><bdi class="secno">6. </bdi>Vocabulary specification</a> do not include inverses intentionally, with the purpose of ensuring interoperability also in systems not making use of OWL reasoning.</p> <p>However, recognizing that inverses are needed for some use cases, DCAT supports them, but with the requirement that they <em class="rfc2119">MAY</em> be used only <em>in addition to</em> those described in <a href="#vocabulary-specification" class="sec-ref"><bdi class="secno">6. </bdi>Vocabulary specification</a>, and that they <em class="rfc2119">MUST NOT</em> be used to replace them.</p> <p>The following table lists the inverse properties supported in DCAT.</p> <table class="simple"> <thead> <tr> <th>Property</th> <th>Inverse</th> </tr> </thead> <tbody> <tr> <td><a href="#Property:resource_previous"><code>dcat:prev</code></a></td> <td id="inverse_of_resource_previous"><code>dcat:next</code></td> </tr> <tr> <td><a href="#Property:resource_previous_version"><code>dcat:previousVersion</code></a></td> <td id="inverse_of_resource_previous_version"><code>dcat:nextVersion</code></td> </tr> <tr> <td><a href="#Property:dataset_distribution"><code>dcat:distribution</code></a></td> <td id="inverse_of_dataset_distribution"><code>dcat:isDistributionOf</code></td> </tr> <tr> <td><a href="#Property:resource_has_part"><code>dcterms:hasPart</code></a></td> <td id="inverse_of_resource_has_part"><a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/isPartOf"><code>dcterms:isPartOf</code></a></td> </tr> <tr> <td><a href="#Property:catalog_resource"><code>dcat:resource</code></a></td> <td id="inverse_of_catalog_resource"><code>dcat:inCatalog</code></td> </tr> <tr> <td><a href="#Property:resource_replaces"><code>dcterms:replaces</code></a></td> <td id="inverse_of_resource_replaces"><a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/isReplacedBy"><code>dcterms:isReplacedBy</code></a></td> </tr> <tr> <td><a href="#Property:resource_is_referenced_by"><code>dcterms:isReferencedBy</code></a></td> <td id="inverse_of_resource_is_referenced_by"><a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/references"><code>dcterms:references</code></a></td> </tr> <tr> <td><a href="#Property:resource_has_version"><code>dcat:hasVersion</code></a></td> <td id="Property:resource_is_version_of"><code>dcat:isVersionOf</code></td> </tr> <tr> <td><a href="#Property:dataset_in_series"><code>dcat:inSeries</code></a></td> <td id="inverse_of_dataset_in_series"><code>dcat:seriesMember</code></td> </tr> <tr> <td><a href="#Property:record_primary_topic"><code>foaf:primaryTopic</code></a></td> <td id="inverse_of_record_primary_topic"><a href="http://xmlns.com/foaf/spec#term_isPrimaryTopicOf"><code>foaf:isPrimaryTopicOf</code></a></td> </tr> <tr> <td><a href="#Property:dataset_was_generated_by"><code>prov:wasGeneratedBy</code></a></td> <td id="inverse_of_dataset_was_generated_by"><a href="https://www.w3.org/TR/prov-o/#generated"><code>prov:generated</code></a></td> </tr> </tbody> </table> </section> <section id="dereferenceable-identifiers" class="informative"><div class="header-wrapper"><h2 id="x8-dereferenceable-identifiers"><bdi class="secno">8. </bdi>Dereferenceable identifiers</h2><a class="self-link" href="#dereferenceable-identifiers" aria-label="Permalink for Section 8."></a></div><p><em>This section is non-normative.</em></p> <p>The scientific and data provider communities use a number of different identifiers for publications, authors and data. DCAT primarily relies on persistent HTTP <abbr title="Internationalized Resource Identifiers">IRIs</abbr> as an effective way of making identifiers actionable. Notably, quite a few identifier schemes can be encoded as dereferenceable HTTP <abbr title="Internationalized Resource Identifiers">IRIs</abbr>, and some of them are also returning machine-readable metadata (e.g., <abbr title="Digital Object Identifier">DOIs</abbr> [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-26324" title="Information and documentation -- Digital object identifier system">ISO-26324</a></cite>] and <a href="https://orcid.org/"><abbr title="Open Researcher and Contributor ID">ORCIDs</abbr></a>). Regardless, data providers still might need to refer to legacy identifiers, non-HTTP dereferenceable identifiers, locally minted or third-party-provided identifiers. In these cases, [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] and [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-adms" title="Asset Description Metadata Schema (ADMS)">VOCAB-ADMS</a></cite>] can be of use.</p> <p>The property <a href="#Property:resource_identifier"><code>dcterms:identifier</code></a> explicitly indicates HTTP <abbr title="Internationalized Resource Identifiers">IRIs</abbr> as well as legacy identifiers. In the following examples, <a href="#Property:resource_identifier"><code>dcterms:identifier</code></a> identifies a dataset, but it can similarly be used with any kind of resources.</p> <aside id="ex-identifier" class="example"><div class="marker"> <a class="self-link" href="#ex-identifier">Example<bdi> 13</bdi></a> </div> <pre class="nohighlight turtle"><https://dcat.example.org/id> a dcat:Dataset; dcterms:identifier "https://dcat.example.org/id"^^xsd:anyURI ; .</pre> </aside> <p> Proxy dereferenceable <abbr title="Internationalized Resource Identifiers">IRIs</abbr> can be used when resources do not have HTTP dereferenceable IDs. For example, in <a href="#ex-proxy-id" class="box-ref">Example<bdi> 14</bdi></a>, <code>dcat.example.org/proxyid</code> is a proxy for <code>id</code>.</p> <aside id="ex-proxy-id" class="example"><div class="marker"> <a class="self-link" href="#ex-proxy-id">Example<bdi> 14</bdi></a> </div> <pre class="nohighlight turtle"><https://dcat.example.org/proxyid> a dcat:Dataset; dcterms:identifier "id"^^xsd:string ; .</pre> </aside> <p>The property <a href="https://www.w3.org/TR/vocab-adms/#adms-identifier"><code>adms:identifier</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-adms" title="Asset Description Metadata Schema (ADMS)">VOCAB-ADMS</a></cite>] can express other locally minted identifiers or external identifiers, like DOI, <a href="https://eur-lex.europa.eu/eli-register/about.html"><abbr title="European Legislation Identifier">ELI</abbr></a>, <a href="https://arxiv.org/">arΧiv</a> for creative works and <a href="https://orcid.org/">ORCID</a>, <a href="https://viaf.org/"><abbr title="Virtual International Authority File">VIAF</abbr></a>, <a href="http://www.isni.org/"><abbr title="International Standard Name Identifier">ISNI</abbr></a> for actors such as authors and publishers, as long as the identifiers are globally unique and stable.</p> <p><a href="#ex-adms-identifier" class="box-ref">Example<bdi> 15</bdi></a> uses <a href="https://www.w3.org/TR/vocab-adms/#adms-schemaagency"><code>adms:schemaAgency</code></a> and <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/creator"><code>dcterms:creator</code></a> to represent the authority that defines the identifier scheme (e.g., the <a href="https://www.doi.org/">DOI foundation</a> in the example), <code>adms:schemaAgency</code> is used when the authority has no <abbr title="Internationalized Resource Identifier">IRI</abbr> associated. The <a href="https://www.crossref.org/display-guidelines/">CrossRef</a> and <a href="https://support.datacite.org/docs/datacite-doi-display-guidelines">DataCite</a> display guidelines recommend displaying <abbr title="Digital Object Identifier">DOIs</abbr> as full URL link in the form <code>https://doi.org/10.xxxx/xxxxx/</code>. </p> <aside id="ex-adms-identifier" class="example"><div class="marker"> <a class="self-link" href="#ex-adms-identifier">Example<bdi> 15</bdi></a> </div> <pre class="nohighlight turtle"><https://dcat.example.org/id> a dcat:Dataset; adms:identifier <https://dcat.example.org/iddoi> ; dcterms:publisher <https://dcat.example.org/PoelenJorritH> ; . <https://dcat.example.org/iddoi> a adms:Identifier ; # reading https://www.w3.org/TR/skos-reference/#notations more than one skos:notation can be set skos:notation "https://doi.org/10.5281/zenodo.1486279"^^xsd:anyURI; # the authority/agency defining the identifier scheme, used if the agency has no IRI adms:schemaAgency "International DOI Foundation" ; # the authority/agency defining the identifier scheme, used if the agency has IRI dcterms:creator ex:InternationalDOIFundation ; . ex:InternationalDOIFundation a foaf:Organization ; rdfs:label "International DOI Foundation" ; foaf:homepage <https://www.doi.org/> ; . <https://dcat.example.org/PoelenJorritH> a foaf:Person; foaf:name "Jorrit H. Poelen" ; adms:identifier <https://dcat.example.org/PoelenJorritHID> ; . <https://dcat.example.org/PoelenJorritHID> a adms:Identifier; skos:notation "https://orcid.org/0000-0003-3138-4118"^^xsd:anyURI ; # the authority/agency defining the identifier scheme, used if the agency has no IRI adms:schemaAgency "ORCID" ; .</pre> </aside> <p><a href="#ex-adms-identifier" class="box-ref">Example<bdi> 15</bdi></a> does not represent the authority responsible for assigning and maintaining identifiers using that scheme (e.g., <a href="https://zenodo.org/">Zenodo</a>) as naming the registrant goes against the philosophy of DOI, where the sub-spaces are abstracted from the organization that registers them, with the advantage that <abbr title="Digital Object Identifier">DOIs</abbr> do not change when the organization changes or the responsibility for that sub-space is handed over to someone else. <a href="#ex-adms-identifier" class="box-ref">Example<bdi> 15</bdi></a> shows a locally minted identifier for the creator of the dataset (e.g., <code>https://dcat.example.org/PoelenJorritHID</code>) and its correspondent ORCID identifier (e.g., <code>https://orcid.org/0000-0003-3138-4118</code>). </p> <p>When the HTTP dereferenceable ID returns an RDF/OWL description for the dataset, the use of <code>owl:sameAs</code> might be considered. For example,</p> <aside id="ex-owl-sameas" class="example"><div class="marker"> <a class="self-link" href="#ex-owl-sameas">Example<bdi> 16</bdi></a> </div> <pre class="nohighlight turtle"><https://dcat.example.org/id3> a dcat:Dataset; ... owl:sameAs <https://doi.org/10.5281/zenodo.1486279> ; .</pre> </aside> <p>when dereferenced with media type <code>text/turtle</code>, <code>https://doi.org/10.5281/zenodo.1486279</code> returns a [<cite><a class="bibref" data-link-type="biblio" href="#bib-schema-org" title="Schema.org">SCHEMA-ORG</a></cite>] description for the dataset, which might dynamically enrich the description provided by <code>https://dcat.example.org/id</code>. </p> <div class="note" role="note" id="issue-container-generatedID-83"><div role="heading" class="note-title marker" id="h-note-82" aria-level="3"><span>Note</span></div><aside class=""> <p>Identifiers for datasets should follow the best practices in <a href="https://www.w3.org/TR/dwbp/#DataIdentifiers">§ <span class="secno">8.7 </span>Data Identifiers</a> of [<cite><a class="bibref" data-link-type="biblio" href="#bib-dwbp" title="Data on the Web Best Practices">DWBP</a></cite>].</p> </aside></div> <p>The need to distinguish between primary and alternative (or legacy) identifiers for a dataset within DCAT has been posed as a requirement. However, it is very much application-specific and would be better addressed in DCAT profiles rather than mandating a general approach.</p> <p>Depending on the application context, specific guidelines such as <a href="https://joinup.ec.europa.eu/release/dcat-ap-how-manage-duplicates">"DCAT-AP: How to manage duplicates?"</a> can be adopted for distinguishing authoritative datasets from dataset harvested by third parties catalogs.</p> <section id="identifiers-type"><div class="header-wrapper"><h3 id="x8-1-indicating-common-identifier-types"><bdi class="secno">8.1 </bdi>Indicating common identifier types</h3><a class="self-link" href="#identifiers-type" aria-label="Permalink for Section 8.1"></a></div> <p> If identifiers are not HTTP dereferenceable, common identifier types can be served as <a href="https://www.w3.org/TR/rdf11-concepts/#dfn-recognized-datatype-iris">RDF datatypes</a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-rdf11-concepts" title="RDF 1.1 Concepts and Abstract Syntax">RDF11-CONCEPTS</a></cite>] or custom <a href="https://www.w3.org/TR/owl2-syntax/#Datatype_Definitions">OWL datatypes</a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-owl2-syntax" title="OWL 2 Web Ontology Language Structural Specification and Functional-Style Syntax (Second Edition)">OWL2-SYNTAX</a></cite>] for the sake of interoperability, see <code>ex:type</code> in <a href="#ex-identifier-type" class="box-ref">Example<bdi> 17</bdi></a>.</p> <aside id="ex-identifier-type" class="example"><div class="marker"> <a class="self-link" href="#ex-identifier-type">Example<bdi> 17</bdi></a> </div> <pre class="nohighlight turtle"><https://dcat.example.org/id4> a dcat:Dataset; ... adms:identifier <https://dcat.example.org/sid> . <https://dcat.example.org/sid5> rdf:type adms:Identifier ; # the actual id skos:notation "PA 1-060-815"^^ex:type ; # Human readable schema agency adms:schemaAgency "US Copyright Office" ; dcterms:issued "2001-09-12"^^xsd:date ; .</pre> </aside> <p>If a registered <abbr title="Internationalized Resource Identifier">IRI</abbr> type is used (following [<cite><a class="bibref" data-link-type="biblio" href="#bib-rfc3986" title="Uniform Resource Identifier (URI): Generic Syntax">RFC3986</a></cite>], <a href="https://www.rfc-editor.org/rfc/rfc3986#section-3.1">§ <span class="secno">3.1 </span>Scheme</a>), the identifier scheme is part of the <abbr title="Internationalized Resource Identifier">IRI</abbr>; thus indicating a separate identifier scheme in 'type' is redundant. For example, DOI is registered as a namespace in the <code>info</code> <abbr title="Internationalized Resource Identifier">IRI</abbr> scheme [<cite><a class="bibref" data-link-type="biblio" href="#bib-iana-uri-schemes" title="Uniform Resource Identifier (URI) Schemes">IANA-URI-SCHEMES</a></cite>] (see <a href="https://www.doi.org/faq.html">DOI FAQ #11</a>), so according to [<cite><a class="bibref" data-link-type="biblio" href="#bib-rfc3986" title="Uniform Resource Identifier (URI): Generic Syntax">RFC3986</a></cite>], it should be encoded as in <a href="#ex-identifier-type-in-uri" class="box-ref">Example<bdi> 18</bdi></a>.</p> <aside id="ex-identifier-type-in-uri" class="example"><div class="marker"> <a class="self-link" href="#ex-identifier-type-in-uri">Example<bdi> 18</bdi></a> </div> <pre class="nohighlight turtle"><https://dcat.example.org/sid6> rdf:type adms:Identifier ; # the actual id skos:notation "info:doi/10.1109/5.771073"^^xsd:anyURI .</pre> </aside> <p>Otherwise, examples of common types for identifier scheme (<a href="https://arxiv.org/help/arxiv_identifier.html">arXiv</a>, etc.) are defined in <a href="https://schema.datacite.org/meta/kernel-4.4/include/datacite-relatedIdentifierType-v4.xsd">DataCite schema</a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-datacite" title="DataCite Metadata Schema">DataCite</a></cite>] and <a href="https://fairsharing.org/standards/?q=&selected_facets=type_exact:identifier%20schema">FAIRsharing Registry</a>.</p> </section> </section> <section id="license-rights" class="informative"><div class="header-wrapper"><h2 id="x9-license-and-rights-statements"><bdi class="secno">9. </bdi>License and rights statements</h2><a class="self-link" href="#license-rights" aria-label="Permalink for Section 9."></a></div><p><em>This section is non-normative.</em></p> <p> Selecting the right way to express conditions for access to and re-use of resources can be complex. Implementers should always seek legal advice before deciding which conditions apply to the resource being described. </p> <p> This specification distinguishes three main situations: one where a statement is associated with a resource that is explicitly declared as a 'license'; a second, where the statement is associated with a resource denoting only access rights; a third, covering all the other cases - i.e., statements not concerning licensing conditions and/or access rights (e.g., copyright statements). </p> <div class="note" role="note" id="issue-container-generatedID-84"><div role="heading" class="note-title marker" id="h-note-83" aria-level="3"><span>Note</span></div><aside class=""> <p> The provision of licensing conditions and access rights complies with the Best Practices 4 ("<a href="https://www.w3.org/TR/dwbp/#licenses">Provide data license information</a>") and 22 ("<a href="https://www.w3.org/TR/dwbp/#DataUnavailabilityReference">Provide an explanation for data that is not available</a>"), respectively, from [<cite><a class="bibref" data-link-type="biblio" href="#bib-dwbp" title="Data on the Web Best Practices">DWBP</a></cite>]. </p> </aside></div> <p> To address these scenarios, it is recommended to use the property <code>dcterms:rights</code>, and its sub-properties <code>dcterms:license</code> and <code>dcterms:accessRights</code>. More precisely: </p> <ol> <li> <p>use <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/license"><code>dcterms:license</code></a> to refer to licenses;</p> <div class="note" role="note" id="issue-container-generatedID-85"><div role="heading" class="note-title marker" id="h-note-84" aria-level="3"><span>Note</span></div><aside class=""> <p> For interoperability, it is recommended to use canonical <abbr title="Internationalized Resource Identifiers">IRIs</abbr> of well-known licenses such as <a href="https://creativecommons.org/share-your-work/licensing-types-examples/">those defined by Creative Commons</a>. </p> </aside></div> </li> <li> <p>use <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/accessRights"><code>dcterms:accessRights</code></a> to express statements concerning only access rights (e.g., whether data can be accessed by anyone or just by authorized parties);</p> <div class="note" role="note" id="issue-container-generatedID-86"><div role="heading" class="note-title marker" id="h-note-85" aria-level="3"><span>Note</span></div><aside class=""> <p> Access rights can also be expressed as code lists / taxonomies. Examples include the access rights code list [<cite><a class="bibref" data-link-type="biblio" href="#bib-euv-ar" title="Named Authority List: Access rights">EUV-AR</a></cite>] used in [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap" title="DCAT Application Profile for data portals in Europe. Version 2.0.1">DCAT-AP</a></cite>] and the <a href="http://purl.org/eprint/accessRights/">Eprints Access Rights Vocabulary Encoding Scheme</a>. </p> </aside></div> </li> <li> <p>use <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/rights"><code>dcterms:rights</code></a> for all the other types of rights statements - those which are not covered by <code>dcterms:license</code> and <code>dcterms:accessRights</code>, such as copyright statements.</p> <div class="note" role="note" id="issue-container-generatedID-87"><div role="heading" class="note-title marker" id="h-note-86" aria-level="3"><span>Note</span></div><aside class=""> <p> A more sophisticated approach to express rights, based on and extending [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>], is provided by the Open Data Rights Statement Vocabulary (ODRS) [<cite><a class="bibref" data-link-type="biblio" href="#bib-odrs" title="Open Data Rights Statement Vocabulary">ODRS</a></cite>], which defines properties for specifying, among others, copyright statements and copyright notices. </p> </aside></div> </li> </ol> <aside class="example" id="ex-license-and-access-rights"><div class="marker"> <a class="self-link" href="#ex-license-and-access-rights">Example<bdi> 19</bdi></a><span class="example-title">: License, access rights, and copyright statement</span> </div> <p>The following example is about a dataset publicly available (with no access restriction) and whose distribution is released by using a standard license - namely, the Creative Commons Attribution (CC-BY) 4.0 license. Access rights are specified by using the [<cite><a class="bibref" data-link-type="biblio" href="#bib-euv-ar" title="Named Authority List: Access rights">EUV-AR</a></cite>] code list. Property <code>dcterms:rights</code> is used for the copyright statement, which is specified with a textual description, by using property <code>rdfs:label</code> (following the <a href="https://www.dublincore.org/resources/userguide/publishing_metadata/">Dublin Core™ User Guide</a>).</p> <pre aria-busy="false"><code class="hljs">ex:ds7890 a dcat:Dataset ; # other dataset properties... dcterms:accessRights <http://publications.europa.eu/resource/authority/access-right/PUBLIC> ; dcterms:rights [ a dcterms:RightsStatement ; rdfs:label "© 2021 ACME Inc."@en ] ; dcat:distribution [ a dcat:Distribution ; # other distribution properties... dcterms:license <https://creativecommons.org/licenses/by/4.0/> ] ; .</code></pre> </aside> <p>Finally, in the particular case when rights are expressed via <a href="https://www.w3.org/TR/odrl-vocab/#term-Policy"><abbr title="Open Digital Rights Language">ODRL</abbr> policies</a>, it is recommended to use the <a href="https://www.w3.org/TR/odrl-vocab/#term-hasPolicy"><code>odrl:hasPolicy</code></a> property as the link from the description of the cataloged resource or distribution to the <abbr title="Open Digital Rights Language">ODRL</abbr> policy.</p> <div class="note" role="note" id="issue-container-generatedID-88"><div role="heading" class="note-title marker" id="h-note-87" aria-level="3"><span>Note</span></div><aside class=""> <p>The Open Digital Rights Language (<abbr title="Open Digital Rights Language">ODRL</abbr>) is a policy expression language that provides a flexible and interoperable information model [<cite><a class="bibref" data-link-type="biblio" href="#bib-odrl-model" title="ODRL Information Model 2.2">ODRL-MODEL</a></cite>], vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-odrl-vocab" title="ODRL Vocabulary & Expression 2.2">ODRL-VOCAB</a></cite>], and encoding mechanisms for representing statements about usage (i.e., permissions, prohibitions, and obligations) of content and services.</p> </aside></div> <aside class="example" id="ex-odrl-policy"><div class="marker"> <a class="self-link" href="#ex-odrl-policy">Example<bdi> 20</bdi></a><span class="example-title">: ODRL policy</span> </div> <p>This example shows how to use [<cite><a class="bibref" data-link-type="biblio" href="#bib-odrl-vocab" title="ODRL Vocabulary & Expression 2.2">ODRL-VOCAB</a></cite>] for a dataset with very specific usage rules. In this case, the data can be read and derivatives can be created, but no commercial use of the dataset is allowed. In addition, it is a requirement to register before the permissions are granted.</p> <pre aria-busy="false"><code class="hljs">ex:ds4242 a dcat:Dataset ; # other dataset properties... dcat:distribution [ a dcat:Distribution ; # other distribution properties... odrl:hasPolicy [ a odrl:Policy ; odrl:permission [ a odrl:Permission ; odrl:action ( <http://www.w3.org/ns/odrl/2/read> <http://www.w3.org/ns/odrl/2/derive> ) ]; odrl:prohibition [ a odrl:Prohibition ; odrl:action <http://creativecommons.org/ns#CommercialUse> ] ; odrl:obligation [ a odrl:Duty ; odrl:action <https://schema.org/RegisterAction> ]; ] ; ] ; .</code></pre> <p>The above example does not explicitly define the <abbr title="Open Digital Rights Language">ODRL</abbr> Asset, so assumes the enclosing identified entity is the subject of the policy as per <a href="https://www.w3.org/TR/odrl-model/#policy-has">§ <span class="secno">2.2.3 </span>Target Policy Property</a> in [<cite><a class="bibref" data-link-type="biblio" href="#bib-odrl-model" title="ODRL Information Model 2.2">ODRL-MODEL</a></cite>]. In addition, the example above follows the <abbr title="Open Digital Rights Language">ODRL</abbr> <em>compact policy</em> rules as per <a href="https://www.w3.org/TR/odrl-model/#composition-compact">§ <span class="secno">2.7.1 </span>Compact Policy</a> in [<cite><a class="bibref" data-link-type="biblio" href="#bib-odrl-model" title="ODRL Information Model 2.2">ODRL-MODEL</a></cite>].</p> </aside> </section> <section id="time-and-space" class="informative"><div class="header-wrapper"><h2 id="x10-time-and-space"><bdi class="secno">10. </bdi>Time and space</h2><a class="self-link" href="#time-and-space" aria-label="Permalink for Section 10."></a></div><p><em>This section is non-normative.</em></p> <section id="temporal-properties"><div class="header-wrapper"><h3 id="x10-1-temporal-properties"><bdi class="secno">10.1 </bdi>Temporal properties</h3><a class="self-link" href="#temporal-properties" aria-label="Permalink for Section 10.1"></a></div> <p> Five temporal properties of resources may be described using DCAT. </p> <ol> <li> The release time of a resource is given using <a href="#Property:resource_release_date"><code title="http://purl.org/dc/terms/issued">dcterms:issued</code></a>. The value is usually encoded as a <a href="https://www.w3.org/TR/xmlschema11-2/#date"><code>xsd:date</code></a>. </li> <li> The revision or update time of a resource is given using <a href="#Property:resource_update_date"><code title="http://purl.org/dc/terms/modified">dcterms:modified</code></a>. The value is usually encoded as a <a href="https://www.w3.org/TR/xmlschema11-2/#date"><code>xsd:date</code></a>. </li> <li> The update schedule for a resource is indicated using <a href="#Property:dataset_frequency"><code title="http://purl.org/dc/terms/accrualPeriodicity">dcterms:accrualPeriodicity</code></a>. The value should be taken from a controlled vocabulary such as <a href="http://www.dublincore.org/specifications/dublin-core/collection-description/frequency/">Dublin Core Collection Description Frequency Vocabulary</a>. </li> <li> The minimum temporal separation of items in a dataset is given using <a href="#Property:dataset_temporal_resolution"><code title="http://www.w3.org/ns/dcat#temporalResolution">dcat:temporalResolution</code></a>. The value is encoded as a <a href="https://www.w3.org/TR/xmlschema11-2/#duration"><code>xsd:duration</code></a>. The update schedule and the temporal resolution can be combined to support the description of different kinds of time-series data as shown below. </li> <li> The temporal extent of a dataset is given using <a href="#Property:dataset_temporal"><code title="http://purl.org/dc/terms/temporal">dcterms:temporal</code></a>. The value is a <a href="http://purl.org/dc/terms/PeriodOfTime"><code>dcterms:PeriodOfTime</code></a>. A number of options for expressing the details of a <code>dcterms:PeriodOfTime</code> are recommended in <a href="#Class:Period_of_Time" class="sec-ref"><bdi class="secno">6.15 </bdi>Class: Period of Time</a>. Examples of these follow. </li> </ol> <aside class="example" id="ex-time-series-1"><div class="marker"> <a class="self-link" href="#ex-time-series-1">Example<bdi> 21</bdi></a><span class="example-title">: 15-minute time-series published daily</span> </div> <pre class="nohighlight turtle">ex:ds913 a dcat:Dataset ; dcterms:accrualPeriodicity <http://purl.org/cld/freq/daily> ; dcat:temporalResolution "PT15M"^^xsd:duration ; .</pre> </aside> <aside class="example" id="ex-time-series-2"><div class="marker"> <a class="self-link" href="#ex-time-series-2">Example<bdi> 22</bdi></a><span class="example-title">: Hourly data published immediately</span> </div> <pre class="nohighlight turtle">ex:ds782 a dcat:Dataset ; dcterms:accrualPeriodicity <http://purl.org/cld/freq/continuous> ; dcat:temporalResolution "PT1H"^^xsd:duration ; .</pre> </aside> <aside class="example" id="ex-temporal-coverage-closed-interval"><div class="marker"> <a class="self-link" href="#ex-temporal-coverage-closed-interval">Example<bdi> 23</bdi></a><span class="example-title">: Temporal coverage as closed interval</span> </div> <pre class="nohighlight turtle">ex:ds257 a dcat:Dataset ; dcterms:temporal [ a dcterms:PeriodOfTime ; dcat:startDate "2016-03-04"^^xsd:date ; dcat:endDate "2018-08-05"^^xsd:date ; ] .</pre> </aside> <aside class="example" id="ex-temporal-coverage-closed-proper-interval"><div class="marker"> <a class="self-link" href="#ex-temporal-coverage-closed-proper-interval">Example<bdi> 24</bdi></a><span class="example-title">: Temporal coverage as closed interval, using time:ProperInterval</span> </div> <p>The following dataset specification is equivalent to the one in <a href="#ex-temporal-coverage-closed-interval" class="box-ref">Example<bdi> 23</bdi></a>, but it uses [<cite><a class="bibref" data-link-type="biblio" href="#bib-owl-time" title="Time Ontology in OWL">OWL-TIME</a></cite>]:</p> <pre class="nohighlight turtle">ex:ds348 a dcat:Dataset ; dcterms:temporal [ a dcterms:PeriodOfTime , time:ProperInterval ; time:hasBeginning [ a time:Instant ; time:inXSDDate "2016-03-04"^^xsd:date ; ] ; time:hasEnd [ a time:Instant ; time:inXSDDate "2018-08-05"^^xsd:date ; ] ; ] .</pre> </aside> <aside class="example" id="ex-temporal-coverage-closed-proper-interval-gyear"><div class="marker"> <a class="self-link" href="#ex-temporal-coverage-closed-proper-interval-gyear">Example<bdi> 25</bdi></a><span class="example-title">: Temporal coverage as proper interval using gYear</span> </div> <pre class="nohighlight turtle">ex:ds429 a dcat:Dataset ; dcterms:temporal [ a dcterms:PeriodOfTime , time:ProperInterval ; time:hasBeginning [ a time:Instant ; time:inXSDgYear "1914"^^xsd:gYear ; ] ; time:hasEnd [ a time:Instant ; time:inXSDgYear "1939"^^xsd:gYear ; ] ; ] .</pre> </aside> <aside class="example" id="ex-temporal-coverage-geologic"><div class="marker"> <a class="self-link" href="#ex-temporal-coverage-geologic">Example<bdi> 26</bdi></a><span class="example-title">: Temporal coverage for a geologic dataset</span> </div> <pre class="nohighlight turtle">ex:ds850 a dcat:Dataset ; dcterms:temporal [ a dcterms:PeriodOfTime , time:ProperInterval ; time:hasBeginning [ a time:Instant ; time:inTimePosition [ a time:TimePosition ; time:hasTRS <http://resource.geosciml.org/classifier/cgi/geologicage/ma> ; time:numericPosition "541.0"^^xsd:decimal ; ] ; ] ; time:hasEnd [ a time:Instant ; time:inTimePosition [ a time:TimePosition ; time:hasTRS <http://resource.geosciml.org/classifier/cgi/geologicage/ma> ; time:numericPosition "251.902"^^xsd:decimal ; ] ; ] ; ] .</pre> </aside> <aside class="example" id="ex-temporal-coverage-open-end-interval"><div class="marker"> <a class="self-link" href="#ex-temporal-coverage-open-end-interval">Example<bdi> 27</bdi></a><span class="example-title">: Temporal coverage as open interval (no end date)</span> </div> <pre class="nohighlight turtle">ex:ds127 a dcat:Dataset ; dcterms:temporal [ a dcterms:PeriodOfTime ; dcat:startDate "2016-03-04"^^xsd:date ; ] .</pre> </aside> <aside class="example" id="ex-temporal-coverage-open-begin-interval"><div class="marker"> <a class="self-link" href="#ex-temporal-coverage-open-begin-interval">Example<bdi> 28</bdi></a><span class="example-title">: Temporal coverage as open interval (no beginning)</span> </div> <pre class="nohighlight turtle">ex:ds586 a dcat:Dataset ; dcterms:temporal [ a dcterms:PeriodOfTime , time:ProperInterval ; time:hasEnd [ time:inXSDDate "2018-08-05"^^xsd:date ] ; ] .</pre> </aside> </section> <section id="spatial-properties"><div class="header-wrapper"><h3 id="x10-2-spatial-properties"><bdi class="secno">10.2 </bdi>Spatial properties</h3><a class="self-link" href="#spatial-properties" aria-label="Permalink for Section 10.2"></a></div> <p> Two spatial properties of datasets may be described using DCAT. </p> <ol> <li> <p>The minimum spatial separation of items in a dataset is given using <a href="#Property:dataset_spatial_resolution"><code title="http://www.w3.org/ns/dcat#spatialResolutionInMeters">dcat:spatialResolutionInMeters</code></a>. The value is a decimal number.</p> <p>An example of the use of <a href="#Property:dataset_spatial_resolution"><code title="http://www.w3.org/ns/dcat#spatialResolutionInMeters">dcat:spatialResolutionInMeters</code></a> is given in <a href="#ex-dataset" class="box-ref">Example<bdi> 3</bdi></a>.</p> </li> <li> <p>The spatial extent of a dataset is given using <a href="#Property:dataset_spatial"><code title="http://purl.org/dc/terms/spatial">dcterms:spatial</code></a>. The value is a <a href="http://purl.org/dc/terms/Location"><code>dcterms:Location</code></a>. A number of options for expressing the details of a <code>dcterms:Location</code> are recommended in <a href="#Class:Location" class="sec-ref"><bdi class="secno">6.16 </bdi>Class: Location</a>.</p> <p>Examples of these follow.</p> </li> </ol> <div class="note" role="note" id="issue-container-generatedID-89"><div role="heading" class="note-title marker" id="h-note-88" aria-level="4"><span>Note</span></div><aside class=""> <p>The following examples are built on the relevant ones included in [<cite><a class="bibref" data-link-type="biblio" href="#bib-sdw-bp" title="Spatial Data on the Web Best Practices">SDW-BP</a></cite>] (in particular, <a href="https://www.w3.org/TR/sdw-bp/#geometry-and-crs">§ <span class="secno">12.2.2 </span>Geometries and coordinate reference systems</a>).</p> <p>In the examples, for properties <code>locn:geometry</code>, <code>dcat:bbox</code>, and <code>dcat:centroid</code>, the geometry is always specified with <abbr title="Well-known Text">WKT</abbr>. As per [<cite><a class="bibref" data-link-type="biblio" href="#bib-geosparql" title="OGC GeoSPARQL - A Geographic Query Language for RDF Data">GeoSPARQL</a></cite>], when the <abbr title="Coordinate Reference System">CRS</abbr> specification is omitted this implies that the default <abbr title="Coordinate Reference System">CRS</abbr> is used - namely CRS84 (corresponding to WGS84, but with axis order longitude/latitude).</p> <p>For more details on coordinate reference systems and geometry encoding, we refer the reader to [<cite><a class="bibref" data-link-type="biblio" href="#bib-sdw-bp" title="Spatial Data on the Web Best Practices">SDW-BP</a></cite>], and, in particular, to the following sections:</p> <ul> <li><a href="https://www.w3.org/TR/sdw-bp/#CRS-background">§ <span class="secno">9 </span>Coordinate Reference Systems (<abbr title="Coordinate Reference System">CRS</abbr>)</a></li> <li><a href="https://www.w3.org/TR/sdw-bp/#geometry-and-crs">§ <span class="secno">12.2.2 </span>Geometries and coordinate reference systems</a></li> </ul> </aside></div> <aside class="example" id="ex-spatial-coverage-geometry"><div class="marker"> <a class="self-link" href="#ex-spatial-coverage-geometry">Example<bdi> 29</bdi></a><span class="example-title">: Spatial coverage as a polygon</span> </div> <p>A dataset whose spatial coverage corresponds to Anne Frank's house in Amsterdam, specified as a polygon (the coordinate reference system is CRS84).</p> <pre class="nohighlight turtle"><AnneFrank_0> a dcat:Dataset ; dcterms:spatial [ a dcterms:Location ; locn:geometry """POLYGON (( 4.8842353 52.375108 , 4.884276 52.375153 , 4.8842567 52.375159 , 4.883981 52.375254 , 4.8838502 52.375109 , 4.883819 52.375075 , 4.8841037 52.374979 , 4.884143 52.374965 , 4.8842069 52.375035 , 4.884263 52.375016 , 4.8843200 52.374996 , 4.884255 52.374926 , 4.8843289 52.374901 , 4.884451 52.375034 , 4.8842353 52.375108 ))"""^^geosparql:wktLiteral ; ] .</pre> <figure id="fig-spatial-coverage-geometry"> <img src="./images/ex-spatial-coverage-geometry-anne-frank-house.png"> <figcaption><a class="self-link" href="#fig-spatial-coverage-geometry">Figure <bdi class="figno">2</bdi></a> <span class="fig-title">Map preview of a spatial coverage specified with a geometry</span></figcaption> </figure> </aside> <aside class="example" id="ex-spatial-coverage-geometry-with-crs"><div class="marker"> <a class="self-link" href="#ex-spatial-coverage-geometry-with-crs">Example<bdi> 30</bdi></a><span class="example-title">: Spatial coverage as a polygon, using a specific CRS</span> </div> <p>The same dataset in <a href="#ex-spatial-coverage-geometry" class="box-ref">Example<bdi> 29</bdi></a>, but where the coordinates of the polygon are specified by using the national Dutch <abbr title="Coordinate Reference System">CRS</abbr> - <a href="https://epsg.io/28992">EPSG:28992</a> ("Amersfoort / RD New").</p> <pre class="nohighlight turtle"><AnneFrank_1> a dcat:Dataset ; dcterms:spatial [ a dcterms:Location ; locn:geometry """<http://www.opengis.net/def/crs/EPSG/0/28992> POLYGON (( 120749.725 487589.422 , 120752.55 487594.375 , 120751.227 487595.129 , 120732.539 487605.788 , 120723.505 487589.745 , 120721.387 487585.939 , 120740.668 487575.07 , 120743.316 487573.589 , 120747.735 487581.337 , 120751.564 487579.154 , 120755.411 487576.96 , 120750.935 487569.172 , 120755.941 487566.288 , 120764.369 487581.066 , 120749.725 487589.422 ))"""^^geosparql:wktLiteral ; ] .</pre> </aside> <aside class="example" id="ex-spatial-coverage-centroid"><div class="marker"> <a class="self-link" href="#ex-spatial-coverage-centroid">Example<bdi> 31</bdi></a><span class="example-title">: Spatial coverage as centroid</span> </div> <p>The same dataset of <a href="#ex-spatial-coverage-geometry" class="box-ref">Example<bdi> 29</bdi></a>, but where spatial coverage is specified by using the centroid / representative point of Anne Frank's house.</p> <pre class="nohighlight turtle"><AnneFrank_2> a dcat:Dataset ; dcterms:spatial [ a dcterms:Location ; dcat:centroid "POINT(4.88412 52.37509)"^^geosparql:wktLiteral ; ] .</pre> <figure id="fig-spatial-coverage-centroid"> <img src="./images/ex-spatial-coverage-centroid-anne-frank-house.png"> <figcaption><a class="self-link" href="#fig-spatial-coverage-centroid">Figure <bdi class="figno">3</bdi></a> <span class="fig-title">Map preview of a spatial coverage specified with a centroid</span></figcaption> </figure> </aside> <aside class="example" id="ex-spatial-coverage-bbox"><div class="marker"> <a class="self-link" href="#ex-spatial-coverage-bbox">Example<bdi> 32</bdi></a><span class="example-title">: Spatial coverage as bounding box</span> </div> <p>The Dutch dataset of postal addresses, with its spatial coverage (Netherlands) specified as a bounding box.</p> <pre class="nohighlight turtle">ex:Dutch-postal a dcat:Dataset ; dcterms:title "Adressen"@nl ; dcterms:title "Addresses"@en ; dcterms:description """INSPIRE Adressen afkomstig uit de basisregistratie Adressen, beschikbaar voor heel Nederland"""@nl ; dcterms:description """INSPIRE addresses derived from the Addresses base registry, available for the Netherlands"""@en ; dcat:theme <http://inspire.ec.europa.eu/theme/ad> ; dcterms:spatial [ a dcterms:Location ; dcat:bbox """POLYGON(( 3.053 47.975 , 7.24 47.975 , 7.24 53.504 , 3.053 53.504 , 3.053 47.975 ))"""^^geosparql:wktLiteral ; ] .</pre> <figure id="fig-spatial-coverage-bbox"> <img src="./images/ex-spatial-coverage-bbox-netherlands.png"> <figcaption><a class="self-link" href="#fig-spatial-coverage-bbox">Figure <bdi class="figno">4</bdi></a> <span class="fig-title">Map preview of a spatial coverage specified with a bounding box</span></figcaption> </figure> </aside> </section> </section> <section id="dataset-versions" class="informative"><div class="header-wrapper"><h2 id="x11-versioning"><bdi class="secno">11. </bdi>Versioning</h2><a class="self-link" href="#dataset-versions" aria-label="Permalink for Section 11."></a></div><p><em>This section is non-normative.</em></p> <p>The notion of <em>version</em> is often used as a generic term to denote some kind of relationship between a resource and a derived one. Examples, among others, include revisions, editions, adaptations, and translations.</p> <p>This section focuses specifically on how to use DCAT to describe versions resulting from a revision - i.e., from changes occurring to a resource as part of its life-cycle.</p> <p>For this purpose, DCAT builds upon existing vocabularies, in particular the versioning component of the [<cite><a class="bibref" data-link-type="biblio" href="#bib-pav" title="PAV - Provenance, Authoring and Versioning. Version 2.3.1">PAV</a></cite>] ontology, and the relevant terms from [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>], [<cite><a class="bibref" data-link-type="biblio" href="#bib-owl2-overview" title="OWL 2 Web Ontology Language Document Overview (Second Edition)">OWL2-OVERVIEW</a></cite>], and [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-adms" title="Asset Description Metadata Schema (ADMS)">VOCAB-ADMS</a></cite>].</p> <p>It is important to note that versioning can be applied to any of the first class citizens DCAT resources, including Catalogs, Catalog Records, Datasets, Distributions.</p> <p>Note also that the DCAT approach described in the following sections is meant to be complementary with those already used in specific types of resources (e.g., [<cite><a class="bibref" data-link-type="biblio" href="#bib-owl2-overview" title="OWL 2 Web Ontology Language Document Overview (Second Edition)">OWL2-OVERVIEW</a></cite>] provides a set of versioning properties for ontologies), as well as in given domains and communities. For a comparison between the DCAT versioning approach and those of other vocabularies, see <a href="#versioning-complementary-approaches" class="sec-ref"><bdi class="secno">11.4 </bdi>Complementary approaches to versioning</a>.</p> <div class="note" role="note" id="issue-container-generatedID-90"><div role="heading" class="note-title marker" id="h-note-89" aria-level="3"><span>Note</span></div><aside class=""> <p>The notion of version is very much related to the community practices, the data management policy and the workflows in place. It is up to data providers to decide when and why a new version should be released. For this reason, DCAT refrains from providing definitions or rules about when changes in a resource should turn into a new release of it, and refers for guidance to [<cite><a class="bibref" data-link-type="biblio" href="#bib-dwbp" title="Data on the Web Best Practices">DWBP</a></cite>] (<a href="https://www.w3.org/TR/dwbp/#dataVersioning">§ <span class="secno">8.6 </span>Data Versioning</a> and <a href="https://www.w3.org/TR/dwbp/#DataIdentifiers">§ <span class="secno">8.7 </span>Data Identifiers</a>).</p> </aside></div> <section id="version-relationships"><div class="header-wrapper"><h3 id="x11-1-relationships-between-versions"><bdi class="secno">11.1 </bdi>Relationships between versions</h3><a class="self-link" href="#version-relationships" aria-label="Permalink for Section 11.1"></a></div> <p>DCAT supports the following kinds of relationships between versions:</p> <ol> <li>Those indicating the version chain and hierarchy (the version history).</li> <li>Those indicating whether a version is replaced/superseded by another one.</li> </ol> <section id="version-history"><div class="header-wrapper"><h4 id="x11-1-1-version-chains-and-hierarchies"><bdi class="secno">11.1.1 </bdi>Version chains and hierarchies</h4><a class="self-link" href="#version-history" aria-label="Permalink for Section 11.1.1"></a></div> <p>DCAT defines specific properties for describing version history, aligned with the corresponding [<cite><a class="bibref" data-link-type="biblio" href="#bib-pav" title="PAV - Provenance, Authoring and Versioning. Version 2.3.1">PAV</a></cite>] ones:</p> <ul> <li><a href="#Property:resource_previous_version"><code>dcat:previousVersion</code></a> (equivalent to <a href="https://pav-ontology.github.io/pav/#d4e459"><code>pav:previousVersion</code></a>)</li> <li><p><a href="#Property:resource_has_version"><code>dcat:hasVersion</code></a> (equivalent to <a href="https://pav-ontology.github.io/pav/#d4e395"><code>pav:hasVersion</code></a>);</p></li> <li><a href="#Property:resource_has_current_version"><code>dcat:hasCurrentVersion</code></a> (equivalent to <a href="https://pav-ontology.github.io/pav/#d4e359"><code>pav:hasCurrentVersion</code></a>, and subproperty of <code>dcat:hasVersion</code>).</li> </ul> <p>Property <code>dcat:previousVersion</code> is used to build a version chain that can be navigated backward from a given version to the first one. This reflects the most typical use case - i.e., linking different versions published as distinct resources in a catalog.</p> <p>In addition to this, property <code>dcat:hasVersion</code> can be used to specify a version hierarchy, by linking an abstract resource to its versions.</p> <p>If needed, the version hierarchy can be further described by specific properties. More precisely, property <code>dcat:hasCurrentVersion</code> link an abstract resource to snapshot corresponding to the current version of the content, whereas property <code>dcat:isVersionOf</code> (inverse of <code>dcat:hasVersion</code>) gives the possibility of specifying a back link from a version to the abstract resource (for the use of this property, see <a href="#inverse-properties" class="sec-ref"><bdi class="secno">7. </bdi>Use of inverse properties</a>).</p> <div class="note" role="note" id="issue-container-generatedID-91"><div role="heading" class="note-title marker" id="h-note-90" aria-level="5"><span>Note</span></div><aside class=""> <p>On how to use DCAT to specify a resource's status, see <a href="#life-cycle" class="sec-ref"><bdi class="secno">11.3 </bdi>Resource life-cycle</a>.</p> </aside></div> <p>Note that the only properties necessary to specify a version chain and hierarchy are, respectively, <code>dcat:previousVersion</code> and <code>dcat:hasVersion</code>. Whether to use or not the other ones depends on the requirements of the relevant use case.</p> <p>The following example reuses those in <a href="https://www.w3.org/TR/dwbp/#dataVersioning">§ <span class="secno">8.6 </span>Data Versioning</a> of [<cite><a class="bibref" data-link-type="biblio" href="#bib-dwbp" title="Data on the Web Best Practices">DWBP</a></cite>] and revises them to show how to specify a version chain and hierarchy on a bus stops dataset, by using the properties described in this section.</p> <aside class="example" id="ex-version-chain-and-hierarchy"><div class="marker"> <a class="self-link" href="#ex-version-chain-and-hierarchy">Example<bdi> 33</bdi></a><span class="example-title">: Version history of the MyCity bus stops dataset</span> </div> <p>The MyCity bus stops dataset is updated whenever the list of bus stops changes. The different versions are preserved in order to keep an historical record of the bus stops available at given points in time. An abstract dataset is used to point to the version with the most up to date list of bus stops.</p> <p>In <a href="#fig-version-chain-and-hierarchy" class="fig-ref" title="Version chain and hierarchy of the MyCity bus stops dataset">Figure <bdi class="">5</bdi></a>, the resource with <abbr title="Internationalized Resource Identifier">IRI</abbr> <code>mycity-bus:stops</code> is the abstract resource, corresponding always to the latest version of the MyCity bus stops dataset, whereas the other ones correspond to specific versions of it. The current version is the one with <abbr title="Internationalized Resource Identifier">IRI</abbr> <code>mycity-bus:stops-2015-12-07</code>.</p> <figure id="fig-version-chain-and-hierarchy"> <img src="./images/version-chain-and-hierarchy.svg"> <figcaption><a class="self-link" href="#fig-version-chain-and-hierarchy">Figure <bdi class="figno">5</bdi></a> <span class="fig-title">Version chain and hierarchy of the MyCity bus stops dataset</span></figcaption> </figure> <p>The corresponding [<cite><a class="bibref" data-link-type="biblio" href="#bib-turtle" title="RDF 1.1 Turtle">Turtle</a></cite>] representation:</p> <pre aria-busy="false"><code class="hljs css">mycity-bus:stops a dcat:Dataset ; ... dcat<span class="hljs-selector-pseudo">:has</span>Version mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span> , mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">05</span>-<span class="hljs-number">05</span> , mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">12</span>-<span class="hljs-number">07</span> ; dcat<span class="hljs-selector-pseudo">:has</span>CurrentVersion mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">12</span>-<span class="hljs-number">07</span> ; . mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span> a dcat:Dataset ; ... dcat<span class="hljs-selector-pseudo">:is</span>VersionOf mycity-bus:stops ; . mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">05</span>-<span class="hljs-number">05</span> a dcat:Dataset ; ... dcat:previousVersion mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span> ; dcat<span class="hljs-selector-pseudo">:is</span>VersionOf mycity-bus:stops ; . mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">12</span>-<span class="hljs-number">07</span> a dcat:Dataset ; ... dcat:previousVersion mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">05</span>-<span class="hljs-number">05</span> ; dcat<span class="hljs-selector-pseudo">:is</span>VersionOf mycity-bus:stops ; .</code></pre> </aside> </section> <section id="version-replace"><div class="header-wrapper"><h4 id="x11-1-2-versions-replaced-by-other-ones"><bdi class="secno">11.1.2 </bdi>Versions replaced by other ones</h4><a class="self-link" href="#version-replace" aria-label="Permalink for Section 11.1.2"></a></div> <p>Another type of relationship concerns whether a given version replaces/supersedes another one. For this purpose, DCAT reuses the relevant [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] property, namely, <a href="#Property:resource_replaces"><code title="http://purl.org/dc/terms/replaces">dcterms:replaces</code></a>, plus its inverse <code title="http://purl.org/dc/terms/isReplacedBy">dcterms:isReplacedBy</code>, in case a back link needs to be provided.</p> <p>It is worth noting that these properties are not denoting by themselves a version chain - i.e., a version is not necessarily replacing its immediate predecessor.</p> <p>The following example reuses the description of the MyCity bus stop dataset in <a href="#ex-version-chain-and-hierarchy" class="box-ref">Example<bdi> 33</bdi></a> to show how replaced versions can be specified in DCAT.</p> <aside class="example" id="ex-version-replace"><div class="marker"> <a class="self-link" href="#ex-version-replace">Example<bdi> 34</bdi></a><span class="example-title">: Replaced versions of the MyCity bus stops dataset</span> </div> <pre aria-busy="false"><code class="hljs css">mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span> a dcat:Dataset ; ... dcat<span class="hljs-selector-pseudo">:is</span>VersionOf mycity-bus:stops ; . mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">05</span>-<span class="hljs-number">05</span> a dcat:Dataset ; ... dcat:previousVersion mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span> ; dcat<span class="hljs-selector-pseudo">:is</span>VersionOf mycity-bus:stops ; dcterms:replaces mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span> ; . mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">12</span>-<span class="hljs-number">07</span> a dcat:Dataset ; ... dcat:previousVersion mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">05</span>-<span class="hljs-number">05</span> ; dcat<span class="hljs-selector-pseudo">:is</span>VersionOf mycity-bus:stops ; dcterms:replaces mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">05</span>-<span class="hljs-number">05</span> ; .</code></pre> </aside> </section> </section> <section id="version-info"><div class="header-wrapper"><h3 id="x11-2-version-information"><bdi class="secno">11.2 </bdi>Version information</h3><a class="self-link" href="#version-info" aria-label="Permalink for Section 11.2"></a></div> <p>Besides the relationships illustrated in the previous section, versioned resources may be associated with additional information, describing, e.g., their differences with the original resource (the version "delta"), the version identifier, and release date.</p> <p>For these purposes, DCAT makes use of the following properties:</p> <ul> <li><a href="#Property:resource_version"><code>dcat:version</code></a> (equivalent to <a href="https://pav-ontology.github.io/pav/#d4e395"><code>pav:version</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-pav" title="PAV - Provenance, Authoring and Versioning. Version 2.3.1">PAV</a></cite>]), for the version name / identifier;</li> <li><a href="#Property:resource_release_date"><code>dcterms:issued</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>], for the version release date;</li> <li><p><a href="#Property:resource_version_notes"><code>adms:versionNotes</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-adms" title="Asset Description Metadata Schema (ADMS)">VOCAB-ADMS</a></cite>], for a textual description of the changes, including backward compatibility issues with the previous version of the resource.</p> </li> </ul> <div class="note" role="note" id="issue-container-generatedID-92"><div role="heading" class="note-title marker" id="h-note-91" aria-level="4"><span>Note</span></div><aside class=""> <p>DCAT does not prescribe how a version name / identifier should be specified, and refers for guidance to [<cite><a class="bibref" data-link-type="biblio" href="#bib-dwbp" title="Data on the Web Best Practices">DWBP</a></cite>]'s <a href="https://www.w3.org/TR/dwbp/#VersioningInfo">Best Practice 7: Provide a version indicator</a>.</p> </aside></div> <p>The following example reuses the one in [<cite><a class="bibref" data-link-type="biblio" href="#bib-dwbp" title="Data on the Web Best Practices">DWBP</a></cite>]'s <a href="https://www.w3.org/TR/dwbp/#VersioningInfo">Best Practice 7: Provide a version indicator</a> to show how version information can be specified in DCAT.</p> <aside class="example" id="ex-version-info"><div class="marker"> <a class="self-link" href="#ex-version-info">Example<bdi> 35</bdi></a><span class="example-title">: First version of the MyCity bus stops dataset</span> </div> <pre aria-busy="false"><code class="hljs css">mycity-bus:stops-<span class="hljs-number">2015</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span> a dcat:Dataset ; dcterms:title <span class="hljs-string">"Bus stops of MyCity"</span> ; ... dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2015</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span>"^^xsd:date ; ... dcat:version <span class="hljs-string">"1.0"</span> ; adms:versionNotes <span class="hljs-string">"First version of the bus stop dataset."</span>@en ; .</code></pre> </aside> </section> <section id="life-cycle"><div class="header-wrapper"><h3 id="x11-3-resource-life-cycle"><bdi class="secno">11.3 </bdi>Resource life-cycle</h3><a class="self-link" href="#life-cycle" aria-label="Permalink for Section 11.3"></a></div> <p>The life-cycle of a resource is an aspect orthogonal to versioning, and sometimes strictly related. The evolution of a resource along its life-cycle (from its conception, to its creation and publication) may result in new versions, although this is not always the case (e.g., in case an approval workflow is in place, the resource may not undergo any change if no revision is needed). Similarly, the creation of a new version may not necessarily lead to a change in status (e.g., when changes are not substantial, and/or are implemented on resources still in development). Moreover, when a resource is replaced because of a revision (correcting errors, adding new content, etc.), it may be moved to a different life-cycle status (e.g., deprecation or withdrawal).</p> <p>It is worth noting that the status of a resource with respect to its life-cycle is often an important piece of information by itself, from both the data provider's and data consumers' perspectives. For a data consumer, it is important to know if a resource is still in development or not, as well as if it is deprecated or withdrawn (and, in such cases, if there is a new version to be used). On the other hand, for a data provider, flagging a resource with its status in the life-cycle is fundamental for the correct administration of the data management workflow. E.g., a resource before being published may need to be stable, and possibly flagged as approved and/or registered. Finally, besides the actual status of a resource, another useful piece of information is <em>when</em> the resource moved to a different status (e.g., when it was created, reviewed, accepted, published).</p> <p>As for versioning, the resource life-cycle depends on community practices, data management policies, and the workflows in place. Moreover, different resource types (e.g., datasets vs catalog records) may have different life-cycle statuses.</p> <p>For the specification of life-cycle statuses, DCAT makes use of property <a href="#Property:resource_status"><code>adms:status</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-adms" title="Asset Description Metadata Schema (ADMS)">VOCAB-ADMS</a></cite>], along with the appropriate [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] time-related properties (<code>dcterms:created</code>, <code>dcterms:dateSubmitted</code>, <code>dcterms:dateAccepted</code>, <code>dcterms:dateCopyrighted</code>, <a href="#Property:resource_release_date"><code>dcterms:issued</code></a>, <a href="#Property:resource_update_date"><code>dcterms:modified</code></a>, <code>dcterms:valid</code>). However, DCAT does not prescribe the use of any specific set of life-cycle statuses, but refers to existing standards and community practices fit for the relevant application scenario.</p> <div class="note" role="note" id="issue-container-generatedID-93"><div role="heading" class="note-title marker" id="h-note-92" aria-level="4"><span>Note</span></div><aside class=""> <p>Examples of life-cycle statuses include:</p> <ul> <li>Those defined in the <abbr title="International Organization for Standardization">ISO</abbr> standard for item registration [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19135" title="Geographic information -- Procedures for item registration">ISO-19135</a></cite>] (accepted / not accepted, deprecated, experimental, reserved, retired, stable, submitted, superseded, valid / invalid).</li> <li>The progress codes defined in [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115" title="Geographic information -- Metadata">ISO-19115</a></cite>] (accepted, completed, deprecated, final, historical archive, not accepted, obsolete, ongoing, pending, planned, proposed, required, retired, superseded, tentative, under development, valid, withdrawn).</li> <li>The ADMS Status vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-adms-skos" title="Joinup. ADMS Controlled Vocabularies">ADMS-SKOS</a></cite>], used in [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap" title="DCAT Application Profile for data portals in Europe. Version 2.0.1">DCAT-AP</a></cite>], which includes four statuses: completed, deprecated, under development, and withdrawn.</li> <li>The dataset statuses [<cite><a class="bibref" data-link-type="biblio" href="#bib-euv-ds" title="Named Authority List: Dataset statuses">EUV-DS</a></cite>] and concept statuses [<cite><a class="bibref" data-link-type="biblio" href="#bib-euv-cs" title="Named Authority List: Concept statuses">EUV-CS</a></cite>] vocabularies from the EU Vocabularies registry.</li> </ul> <p>The UK Government Linked Data Registry project [<cite><a class="bibref" data-link-type="biblio" href="#bib-ukgovld-reg" title="Linked Data Registry - Principles and Concepts">UKGOVLD-REG</a></cite>] provides an example of how the life-cycle statuses defined in [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19135" title="Geographic information -- Procedures for item registration">ISO-19135</a></cite>] can be used in a registry, along with the criteria for status transition.</p> </aside></div> </section> <section id="versioning-complementary-approaches"><div class="header-wrapper"><h3 id="x11-4-complementary-approaches-to-versioning"><bdi class="secno">11.4 </bdi>Complementary approaches to versioning</h3><a class="self-link" href="#versioning-complementary-approaches" aria-label="Permalink for Section 11.4"></a></div> <p>The DCAT versioning approach can coexist with existing versioning practices - as those used in specific communities, domains, and resource types.</p> <p>As an example, the following table shows the correspondences between the DCAT versioning properties and the vocabularies most frequently used to specify similar concepts, namely, OWL, for ontologies, [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>], and [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>].</p> <table class="simple" id="table-versioning-complementary-approaches"> <caption>Similar (but not equivalent) versioning properties in DCAT, OWL, [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>], and [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>]</caption> <thead> <tr> <th>DCAT</th> <th>OWL</th> <th>[<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>]</th> <th>[<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>]</th> </tr> </thead> <tbody> <tr> <td><a href="#Property:resource_has_version"><code>dcat:hasVersion</code></a></td> <td></td> <td><a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/hasVersion"><code>dcterms:hasVersion</code></a></td> <td><a href="https://www.w3.org/TR/prov-o/#inverse-names-table"><code title="http://www.w3.org/ns/prov#generalizationOf">prov:generalizationOf</code></a></td> </tr> <tr> <td><a href="#Property:resource_is_version_of"><code>dcat:isVersionOf</code></a></td> <td></td> <td><a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/isVersionOf"><code>dcterms:isVersionOf</code></a></td> <td><a href="https://www.w3.org/TR/prov-o/#specializationOf"><code title="http://www.w3.org/ns/prov#specializationOf">prov:specializationOf</code></a></td> </tr> <tr> <td><a href="#Property:resource_has_current_version"><code>dcat:hasCurrentVersion</code></a></td> <td><code>owl:versionIRI</code></td> <td></td> <td></td> </tr> <tr> <td><a href="#Property:resource_previous_version"><code>dcat:previousVersion</code></a></td> <td><code>owl:priorVersion</code></td> <td></td> <td><a href="https://www.w3.org/TR/prov-o/#wasRevisionOf"><code>prov:wasRevisionOf</code></a></td> </tr> <tr> <td><a href="#Property:resource_version"><code>dcat:version</code></a></td> <td><code>owl:versionInfo</code></td> <td></td> <td></td> </tr> </tbody> </table> <p>Note that correspondence does not imply equivalence. These properties have different scopes and semantics, and therefore they can complement but not replace each other. In particular, OWL properties are meant to be used on resources that can be typed as <code>owl:Ontology</code>'s, whereas the [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] ones use a very broad notion of <em>version</em> (including editions and adaptations). On the other hand, DCAT versioning properties are meant to be used on any resource in a catalog, and they use a very specific notion of <em>version</em>, as explained in the introduction to <a href="#dataset-versions" class="sec-ref"><bdi class="secno">11. </bdi>Versioning</a>. Finally, the [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] property <code>prov:wasRevisionOf</code>, although semantically similar to <code>dcat:previousVersion</code>, is not explicitly meant to be used to build a version chain, whereas <code>prov:generalizationOf</code> and <code>prov:specializationOf</code> are semantically broader than their sub-properties <code>dcat:hasVersion</code> and <code>dcat:isVersionOf</code>, respectively.</p> <p>The following example shows how DCAT and OWL can be used complementarily to versioning [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-2" title="Data Catalog Vocabulary (DCAT) - Version 2">VOCAB-DCAT-2</a></cite>].</p> <aside class="example" id="ex-versioning-with-dcat-and-owl"><div class="marker"> <a class="self-link" href="#ex-versioning-with-dcat-and-owl">Example<bdi> 36</bdi></a><span class="example-title">: Use of DCAT and OWL for versioning DCAT 3</span> </div> <pre aria-busy="false"><code class="hljs css"><http://www.w3.org/ns/dcat> a owl:Ontology , dcat:Dataset ; owl:versionInfo <span class="hljs-string">"3"</span> ; dcat:version <span class="hljs-string">"3"</span> ; owl:versionIRI <http://www.w3.org/ns/dcat3> ; dcat<span class="hljs-selector-pseudo">:has</span>CurrentVersion <http://www.w3.org/ns/dcat3> ; owl:priorVersion <http://www.w3.org/ns/dcat2> ; dcat:previousVersion <http://www.w3.org/ns/dcat2> ; dcat<span class="hljs-selector-pseudo">:has</span>Version <http://www.w3.org/ns/dcat2014> , <http://www.w3.org/ns/dcat2> , <http://www.w3.org/ns/dcat3> ; .</code></pre> </aside> </section> </section> <section class="informative" id="dataset-series"><div class="header-wrapper"><h2 id="x12-dataset-series"><bdi class="secno">12. </bdi>Dataset series</h2><a class="self-link" href="#dataset-series" aria-label="Permalink for Section 12."></a></div><p><em>This section is non-normative.</em></p> <p>With "dataset series" we refer to data, somehow interrelated, that are published separately. An example is budget data split by year and/or country, instead of being made available in a single dataset.</p> <p>Dataset series are defined in [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115" title="Geographic information -- Metadata">ISO-19115</a></cite>] as a <q>collection of datasets […] sharing common characteristics</q>. However, their use is not limited to geospatial data, although in other domains they can be named differently (e.g., time series, data slices) and defined more or less strictly (see, e.g., the notion of "dataset slice" in [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-data-cube" title="The RDF Data Cube Vocabulary">VOCAB-DATA-CUBE</a></cite>]).</p> <p>The reasons and criteria for grouping datasets into series are manyfold, and they may be related to, e.g., data characteristics, publishing process, and how they are typically used. For instance, data huge in size (as geospatial ones) are more easily handled (by data providers as well as data consumers) by splitting them into smaller ones. Another example is data released on a yearly basis, which are typically published as separate datasets, instead of appending the new data to the first in the series.</p> <p>As there are no common rules and criteria across domains to decide when dataset series should be created and how they should be organized, DCAT does not prescribe any specific approach, and refer for guidance and domain- and community practices. The purpose of this section is limited to providing guidance on how dataset series can be specified in DCAT.</p> <section id="dataset-series-specification"><div class="header-wrapper"><h3 id="x12-1-how-to-specify-dataset-series"><bdi class="secno">12.1 </bdi>How to specify dataset series</h3><a class="self-link" href="#dataset-series-specification" aria-label="Permalink for Section 12.1"></a></div> <div class="note" role="note" id="issue-container-generatedID-94"><div role="heading" class="note-title marker" id="h-note-93" aria-level="4"><span>Note</span></div><aside class=""> Discussion about using distributions or datasets as members of a dataset series has taken place in issues <a href="https://github.com/w3c/dxwg/issues/868">issue 868</a> and <a href="https://github.com/w3c/dxwg/issues/1429">issue 1429</a>. </aside></div> <p>DCAT makes dataset series first class citizens of data catalogs by minting a new class <a href="#Class:Dataset_Series"><code>dcat:DatasetSeries</code></a>, defined as a subclass of <a href="#Class:Dataset"><code>dcat:Dataset</code></a>. The datasets are linked to the dataset series by using the property <a href="#Property:dataset_in_series"><code>dcat:inSeries</code></a>. Note that a dataset series can also be hierarchical, and a dataset series can be a member of another dataset series.</p> <aside class="example" id="ex-dataset-series-containment"><div class="marker"> <a class="self-link" href="#ex-dataset-series-containment">Example<bdi> 37</bdi></a><span class="example-title">: Yearly budget datasets grouped into a series</span> </div> <p>In the following example, yearly budget data are grouped into a series. The series is typed as <code>dcat:DatasetSeries</code>, the child datasets are typed as <code>dcat:Dataset</code>. The datasets are linked to the series by using <code>dcat:inSeries</code>.</p> <pre aria-busy="false"><code class="hljs css">ex:EUCatalogue a dcat:Catalog ; dcterms:title <span class="hljs-string">"European Data Catalogue"</span>@en ; dcat:dataset ex:budget , ex:employment , ex:finance ; . ex:budget a dcat:DatasetSeries ; dcterms:title <span class="hljs-string">"Budget data"</span>@en ; . ex:budget-<span class="hljs-number">2018</span> a dcat:Dataset ; dcterms:title <span class="hljs-string">"Budget data for year 2018"</span>@en ; dcat:inSeries ex:budget ; . ex:budget-<span class="hljs-number">2019</span> a dcat:Dataset ; dcterms:title <span class="hljs-string">"Budget data for year 2019"</span>@en ; dcat:inSeries ex:budget ; . ex:budget-<span class="hljs-number">2020</span> a dcat:Dataset ; dcterms:title <span class="hljs-string">"Budget data for year 2020"</span>@en ; dcat:inSeries ex:budget ; .</code></pre> </aside> <p>Dataset series may evolve over time, by acquiring new datasets. E.g., a dataset series about yearly budget data will acquire a new child dataset every year. In such cases, it might be important to link the yearly releases with relationships specifying the first, previous, next, and latest ones. In such a scenario, DCAT makes use of properties <a href="#Property:resource_first"><code>dcat:first</code></a>, <a href="#Property:resource_previous"><code>dcat:prev</code></a>, and <a href="#Property:resource_last"><code>dcat:last</code></a>, respectively. See <a href="#inverse-properties" class="sec-ref"> <bdi class="secno">7. </bdi>Use of inverse properties</a> for <code>dcat:next</code>. </p> <aside class="example" id="ex-dataset-series-releases"><div class="marker"> <a class="self-link" href="#ex-dataset-series-releases">Example<bdi> 38</bdi></a><span class="example-title">: Linking datasets in a series</span> </div> <p>The following example extends <a href="#ex-dataset-series-containment" class="box-ref">Example<bdi> 37</bdi></a> by specifying the publication date (<code>dcterms:issued</code>) of each child dataset, and the previous (<code>dcat:prev</code>) and next (<code>dcat:next</code>) dataset in the series. Moreover, the dataset series is linked to its first (<code>dcat:first</code>) and last (<code>dcat:last</code>) child datasets.</p> <pre aria-busy="false"><code class="hljs css">ex:budget a dcat:DatasetSeries ; dcterms:title <span class="hljs-string">"Budget data"</span>@en ; dcat<span class="hljs-selector-pseudo">:first</span> ex:budget-<span class="hljs-number">2018</span> ; dcat:last ex:budget-<span class="hljs-number">2020</span> ; . ex:budget-<span class="hljs-number">2018</span> a dcat:Dataset ; dcterms:title <span class="hljs-string">"Budget data for year 2018"</span>@en ; dcat:inSeries ex:budget ; dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2019</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span>"^^xsd:date ; dcat:next ex:budget-<span class="hljs-number">2019</span> ; . ex:budget-<span class="hljs-number">2019</span> a dcat:Dataset ; dcterms:title <span class="hljs-string">"Budget data for year 2019"</span>@en ; dcat:inSeries ex:budget ; dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2020</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span>"^^xsd:date ; dcat:prev ex:budget-<span class="hljs-number">2018</span> ; dcat:next ex:budget-<span class="hljs-number">2020</span> ; . ex:budget-<span class="hljs-number">2020</span> a dcat:Dataset ; dcterms:title <span class="hljs-string">"Budget data for year 2020"</span>@en ; dcat:inSeries ex:budget ; dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2021</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span>"^^xsd:date ; dcat:prev ex:budget-<span class="hljs-number">2019</span> ; .</code></pre> </aside> <p>Datasets in a series can, of course, be versioned. In such a case, the dataset can be linked to its versions by using the approach illustrated in <a href="#version-history" class="sec-ref"><bdi class="secno">11.1.1 </bdi>Version chains and hierarchies</a>, as shown in <a href="#ex-dataset-series-and-versions" class="box-ref">Example<bdi> 39</bdi></a>.</p> <div class="note" role="note" id="issue-container-generatedID-95"><div role="heading" class="note-title marker" id="h-note-94" aria-level="4"><span>Note</span></div><aside class=""> <p>This use case was contributed in Issue <a href="https://github.com/w3c/dxwg/issues/1409">#1409</a>.</p> </aside></div> <aside class="example" id="ex-dataset-series-and-versions"><div class="marker"> <a class="self-link" href="#ex-dataset-series-and-versions">Example<bdi> 39</bdi></a><span class="example-title">: Combining dataset series and versions</span> </div> <p>The following example extends <a href="#ex-dataset-series-releases" class="box-ref">Example<bdi> 38</bdi></a> by supposing that dataset <code>ex:budget-2019</code> has two different versions, namely, <code>ex:budget-2019-rev0</code> and <code>ex:budget-2019-rev1</code>. Dataset <code>ex:budget-2019</code> is linked to its versions by using property <a href="#Property:resource_has_version"><code>dcat:hasVersion</code></a>, and to its current version (<code>ex:budget-2019-rev1</code>) by using property <a href="#Property:resource_has_current_version"><code>dcat:hasCurrentVersion</code></a>.</p> <pre aria-busy="false"><code class="hljs css">ex:budget a dcat:DatasetSeries ; dcterms:title <span class="hljs-string">"Budget data"</span>@en ; dcat<span class="hljs-selector-pseudo">:first</span> ex:budget-<span class="hljs-number">2018</span> ; dcat:last ex:budget-<span class="hljs-number">2020</span> ; . ex:budget-<span class="hljs-number">2018</span> a dcat:Dataset ; dcterms:title <span class="hljs-string">"Budget data for year 2018"</span>@en ; dcat:inSeries ex:budget ; dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2019</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span>"^^xsd:date ; dcat:next ex:budget-<span class="hljs-number">2019</span> ; . ex:budget-<span class="hljs-number">2019</span> a dcat:Dataset ; dcterms:title <span class="hljs-string">"Budget data for year 2019"</span>@en ; dcat:inSeries ex:budget ; dcat<span class="hljs-selector-pseudo">:has</span>Version ex:budget-<span class="hljs-number">2019</span>-rev0 , ex:budget-<span class="hljs-number">2019</span>-rev1 ; dcat<span class="hljs-selector-pseudo">:has</span>CurrentVersion ex:budget-<span class="hljs-number">2019</span>-rev1 ; dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2020</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span>"^^xsd:date ; dcat:prev ex:budget-<span class="hljs-number">2018</span> ; dcat:next ex:budget-<span class="hljs-number">2020</span> ; . ex:budget-<span class="hljs-number">2019</span>-rev0 a dcat:Dataset ; dcterms:title <span class="hljs-string">"Budget data for year 2019"</span>@en ; dcat:version <span class="hljs-string">"rev0"</span> ; dcat<span class="hljs-selector-pseudo">:is</span>VersionOf ex:budget-<span class="hljs-number">2019</span> ; dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2020</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span>"^^xsd:date ; . ex:budget-<span class="hljs-number">2019</span>-rev1 a dcat:Dataset ; dcterms:title <span class="hljs-string">"Budget data for year 2019"</span>@en ; dcat:version <span class="hljs-string">"rev1"</span> ; dcat<span class="hljs-selector-pseudo">:is</span>VersionOf ex:budget-<span class="hljs-number">2019</span> ; dcat:previousVersion ex:budget-<span class="hljs-number">2019</span>-rev0 ; dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2020</span>-<span class="hljs-number">05</span>-<span class="hljs-number">10</span>"^^xsd:date ; . ex:budget-<span class="hljs-number">2020</span> a dcat:Dataset ; dcterms:title <span class="hljs-string">"Budget data for year 2020"</span>@en ; dcat:inSeries ex:budget ; dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2021</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span>"^^xsd:date ; dcat:prev ex:budget-<span class="hljs-number">2019</span> ; .</code></pre> </aside> </section> <section id="dataset-series-properties"><div class="header-wrapper"><h3 id="x12-2-dataset-series-metadata"><bdi class="secno">12.2 </bdi>Dataset series metadata</h3><a class="self-link" href="#dataset-series-properties" aria-label="Permalink for Section 12.2"></a></div> <p>Properties about dataset series can be classified into two groups.</p> <p>The first group is about properties describing the dataset series itself. For instance, this is the case of property <a href="#Property:dataset_frequency"><code>dcterms:accrualPeriodicity</code></a>, whose value should correspond to the frequency upon which a new child dataset is added.</p> <p>The second group is about properties reflecting the dimensions described in child dataset metadata, via upstream inheritance - i.e., property values of child datasets are inherited by their parent (the dataset series).</p> <p>Typically, this means that, for each of the relevant properties, the dataset series takes as value the union of those specified in child datasets. For instance:</p> <ul> <li>If the temporal coverage of child datasets is a different year, e.g., 2018, 2019, 2020, the temporal coverage of the series will be the time period between years 2018 and 2020.</li> <li>If child datasets have a different geographic bounding box as spatial coverage, the spatial coverage of the series will be the union of these bounding boxes (i.e., a bounding box including the ones of the child datasets).</li> <li>If each child dataset uses a different spatial reference system, the dataset series will have multiple spatial reference systems.</li> </ul> <p>Finally, some annotation properties of child datasets may need to be taken into account as well at the level of dataset series. In particular, properties concerning the creation / publication / update dates of child datasets may affect the corresponding ones in the series. For these properties, DCAT recommends the following approach:</p> <ul> <li>The creation date (<code>dcterms:created</code>) of the dataset series should correspond to the earliest creation date of the child datasets.</li> <li>The publication date (<a href="#Property:resource_release_date"><code>dcterms:issued</code></a>) of the dataset series should correspond to the earliest publication date of the child datasets.</li> <li>The update date (<a href="#Property:resource_update_date"><code>dcterms:modified</code></a>) of the dataset series should correspond to the latest publication or update date of the child datasets.</li> </ul> <div class="note" role="note" id="issue-container-generatedID-96"><div role="heading" class="note-title marker" id="h-note-95" aria-level="4"><span>Note</span></div><aside class=""> <p>To ensure dataset series metadata be correct and updated, mechanisms can be put in place to implement upstream inheritance automatically. However, DCAT does not recommend any specific strategy to be adopted.</p> </aside></div> <aside class="example" id="ex-dataset-series-properties"><div class="marker"> <a class="self-link" href="#ex-dataset-series-properties">Example<bdi> 40</bdi></a><span class="example-title">: Dataset series metadata</span> </div> <p>The following example is a variant of <a href="#ex-dataset-series-releases" class="box-ref">Example<bdi> 38</bdi></a>, with child datasets corresponding to yearly budget data for specific countries. The temporal resolution (<code>dcat:temporalResolution</code>), temporal coverage (<code>dcat:temporal</code>), and spatial coverage (<code>dcat:spatial</code>) of the dataset series correspond to the union of those of the child datasets. Moreover, the dataset series specifies as publication date the one of the first published child dataset, whereas the date of publication of the last child dataset is specified as update date (<code>dcterms:modified</code>). Finally, the update frequency (<code>dcterms:accrualPeriodicity</code>) of the dataset series is annual, as the child datasets are published on a yearly basis.</p> <pre aria-busy="false"><code class="hljs css">ex:budget a dcat:DatasetSeries ; dcterms:title <span class="hljs-string">"Budget data"</span>@en ; dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2019</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span>"^^xsd:date , dcterms:modified <span class="hljs-string">"2021-01-01"</span>^^xsd:date ; dcterms:accrualPeriodicity <http://purl.org/cld/freq/annual> ; dcat:temporalResolution <span class="hljs-string">"P1Y"</span>^^xsd:duration ; dcterms:temporal [ a dcterms:PeriodOfTime ; dcat:startDate <span class="hljs-string">"2018-01-01"</span>^^xsd:date ; dcat:endDate <span class="hljs-string">"2020-12-31"</span>^^xsd:date ; ] ; dcterms:spatial <http://publications.europa.eu/resource/dataset/country/BEL> , <http://publications.europa.eu/resource/dataset/country/FRA> , <http://publications.europa.eu/resource/dataset/country/ITA> , ... ; . ex:budget-<span class="hljs-number">2018</span>-be a dcat:Dataset ; dcterms:title <span class="hljs-string">"Belgium budget data for year 2018"</span>@en ; dcat:inSeries ex:budget ; dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2019</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span>"^^xsd:date ; dcat:next ex:budget-<span class="hljs-number">2019</span>-be ; dcterms:accrualPeriodicity <http://purl.org/cld/freq/annual> ; dcat:temporalResolution <span class="hljs-string">"P1Y"</span>^^xsd:duration ; dcterms:temporal [ a dcterms:PeriodOfTime ; dcat:startDate <span class="hljs-string">"2018-01-01"</span>^^xsd:date ; dcat:endDate <span class="hljs-string">"2018-12-31"</span>^^xsd:date ; ] ; dcterms:spatial <http://publications.europa.eu/resource/dataset/country/BEL> ; . ... ex:budget-<span class="hljs-number">2018</span>-fr a dcat:Dataset ; dcterms:title <span class="hljs-string">"France budget data for year 2018"</span>@en ; dcat:inSeries ex:budget ; dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2019</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span>"^^xsd:date ; dcat:next ex:budget-<span class="hljs-number">2019</span>-fr ; dcterms:accrualPeriodicity <http://purl.org/cld/freq/annual> ; dcat:temporalResolution <span class="hljs-string">"P1Y"</span>^^xsd:duration ; dcterms:temporal [ a dcterms:PeriodOfTime ; dcat:startDate <span class="hljs-string">"2018-01-01"</span>^^xsd:date ; dcat:endDate <span class="hljs-string">"2018-12-31"</span>^^xsd:date ; ] ; dcterms:spatial <http://publications.europa.eu/resource/dataset/country/FRA> ; . ... ex:budget-<span class="hljs-number">2018</span>-it a dcat:Dataset ; dcterms:title <span class="hljs-string">"Italy budget data for year 2018"</span>@en ; dcat:inSeries ex:budget ; dcterms<span class="hljs-selector-pseudo">:is</span>sued "<span class="hljs-number">2019</span>-<span class="hljs-number">01</span>-<span class="hljs-number">01</span>"^^xsd:date ; dcat:next ex:budget-<span class="hljs-number">2019</span>-it ; dcterms:accrualPeriodicity <http://purl.org/cld/freq/annual> ; dcat:temporalResolution <span class="hljs-string">"P1Y"</span>^^xsd:duration ; dcterms:temporal [ a dcterms:PeriodOfTime ; dcat:startDate <span class="hljs-string">"2018-01-01"</span>^^xsd:date ; dcat:endDate <span class="hljs-string">"2018-12-31"</span>^^xsd:date ; ] ; dcterms:spatial <http://publications.europa.eu/resource/dataset/country/ITA> ; . ...</code></pre> </aside> </section> <section id="dataset-series-before-dcat3"><div class="header-wrapper"><h3 id="x12-3-dataset-series-in-existing-dcat-implementations"><bdi class="secno">12.3 </bdi>Dataset series in existing DCAT implementations</h3><a class="self-link" href="#dataset-series-before-dcat3" aria-label="Permalink for Section 12.3"></a></div> <p>Existing DCAT implementations adopt two main alternative approaches to specifying dataset series:</p> <ol> <li>The dataset series is typed as a <code>dcat:Dataset</code>, whereas its child datasets are typed as <code>dcat:Distribution</code>'s.</li> <li>Both the dataset series and its child datasets are typed as a <code>dcat:Dataset</code>'s, and the two are usually linked by using the [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] properties <code>dcterms:hasPart</code> / <code>dcterms:isPartOf</code>.</li> </ol> <p>In both cases, the dataset series is sometimes soft-typed by using the [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] property <code>dcterms:type</code> (e.g., this is the approach used in [<cite><a class="bibref" data-link-type="biblio" href="#bib-geodcat-ap" title="GeoDCAT-AP: A geospatial extension for the DCAT application profile for data portals in Europe">GeoDCAT-AP</a></cite>], and adopted in [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap-it" title="Profilo metadatazione DCAT-AP_IT">DCAT-AP-IT</a></cite>] and [<cite><a class="bibref" data-link-type="biblio" href="#bib-geodcat-ap-it" title="GeoDCAT-AP in Italy, the national guidelines published">GeoDCAT-AP-IT</a></cite>]).</p> <p>These options are not formally incompatible with DCAT, so they can coexist with <code>dcat:DatasetSeries</code> during the upgrade to DCAT 3.</p> </section> </section> <section id="data-citation" class="informative"><div class="header-wrapper"><h2 id="x13-data-citation"><bdi class="secno">13. </bdi>Data citation</h2><a class="self-link" href="#data-citation" aria-label="Permalink for Section 13."></a></div><p><em>This section is non-normative.</em></p> <p> <a href="https://www.w3.org/TR/dcat-ucr/#RDSC">Dataset citation</a> is one of the requirements identified. Data citation is the practice of referencing data in a similar way as when providing bibliographic references, acknowledging data as a first class output in any investigative process. Data citation offers multiple benefits, such as supporting proper attribution and credit to those producing the data, facilitating data discovery, supporting tracking the impact and reuse of data, allowing for collaboration and re-use of data, and enabling the reproducibility of results based on the data. </p> <p> To support data citation, the dataset description should include at a minimum: the dataset identifier, the dataset creator(s), the dataset title, the dataset publisher and the dataset publication or release date. These elements are those required by the DataCite metadata schema [<cite><a class="bibref" data-link-type="biblio" href="#bib-datacite" title="DataCite Metadata Schema">DataCite</a></cite>], which is the metadata associated by the persistent identifiers (Digital Object Identifiers or <abbr title="Digital Object Identifier">DOIs</abbr>) assigned by [<cite><a class="bibref" data-link-type="biblio" href="#bib-datacite" title="DataCite Metadata Schema">DataCite</a></cite>] to research data. </p> <p> In order to support data citation, DCAT 2 added the consideration of <a href="#dereferenceable-identifiers">dereferenceable identifiers</a> and support for indicating <a href="#Property:resource_creator">the creators of the cataloged resources</a>. The remaining properties necessary for data citation were already available in DCAT 1 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>]. </p> <p> The constraints on the availability of properties required for data citation in the dataset description can be represented as a DCAT data citation profile. </p> </section> <section id="quality-information" class="informative"><div class="header-wrapper"><h2 id="x14-quality-information"><bdi class="secno">14. </bdi>Quality information</h2><a class="self-link" href="#quality-information" aria-label="Permalink for Section 14."></a></div><p><em>This section is non-normative.</em></p> <div class="note" role="note" id="issue-container-generatedID-97"><div role="heading" class="note-title marker" id="h-note-96" aria-level="3"><span>Note</span></div><aside class=""> <p>This section is non-normative as it provides guidance on how to document the quality of DCAT first class entities (e.g., datasets, distributions) and it does not define new DCAT terms. The guidance relies on the Data Quality Vocabulary (DQV) [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>], which is a <abbr title="World Wide Web Consortium">W3C</abbr> Group Note.</p> </aside></div> <p>The Data Quality Vocabulary (DQV) [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>] offers common modeling patterns for different aspects of Data Quality. It can relate DCAT datasets and distributions with different types of quality information including:</p> <ul> <li><a href="https://www.w3.org/TR/vocab-dqv/#dqv:QualityAnnotation"><code>dqv:QualityAnnotation</code></a>, which represents feedback and quality certificates given about the dataset or its distribution.</li> <li><a href="https://www.w3.org/TR/vocab-dqv/#dqv:QualityPolicy"><code>dqv:QualityPolicy</code></a>, which represents a policy or agreement that is chiefly governed by data quality concerns.</li> <li><a href="https://www.w3.org/TR/vocab-dqv/#dqv:QualityMeasurement"><code>dqv:QualityMeasurement</code></a>, which represents a metric value providing quantitative or qualitative information about the dataset or distribution.</li> </ul> <p>Each type of quality information can pertain to one or more quality dimensions, namely, quality characteristics relevant to the consumer. The practice to see the quality as a multi-dimensional space is consolidated in the field of quality management to split the quality management into addressable chunks. DQV does not define a normative list of quality dimensions. It offers the quality dimensions proposed in <abbr title="International Organization for Standardization">ISO</abbr>/IEC 25012 [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-iec-25012" title="ISO/IEC 25012 - Data Quality model">ISO-IEC-25012</a></cite>] and [<cite><a class="bibref" data-link-type="biblio" href="#bib-zaverietal" title="Quality assessment for Linked Data: A Survey">ZaveriEtAl</a></cite>] as two possible starting points. It also provides an <a href="https://www.w3.org/2016/05/ldqd">RDF representation</a> for the quality dimensions and categories defined in the latter. Ultimately, implementers will need to choose themselves the collection of quality dimensions that best fits their needs. The following section shows how DCAT and DQV can be coupled to describe the quality of datasets and distributions. For a comprehensive introduction and further examples of use, please refer to [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>].</p> <div class="note" role="note" id="issue-container-generatedID-98"><div role="heading" class="note-title marker" id="h-note-97" aria-level="3"><span>Note</span></div><aside class=""> <p>The following examples make no comments on where the quality information would reside and how it is managed. That is out of scope for the DCAT vocabulary. The assumption made is that the quality individuals are available using the <abbr title="Internationalized Resource Identifiers">IRIs</abbr> indicated. Besides, the examples and more in general the [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>] is neutral to the data portal design choices on how to collect quality information. For example, data portals can collect [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>] instances by implementing specific UI to annotate data or by taking inputs from 3rd-party services. </p> </aside></div> <section id="quality-example1"><div class="header-wrapper"><h3 id="x14-1-providing-quality-information"><bdi class="secno">14.1 </bdi>Providing quality information</h3><a class="self-link" href="#quality-example1" aria-label="Permalink for Section 14.1"></a></div> <p> A data consumer (<code>ex:consumer1</code>) describes the quality of the dataset <code>ex:genoaBusStopsDataset</code> that includes a georeferenced list of bus stops in Genoa. He/she annotates the dataset with a DQV quality note (<code>ex:genoaBusStopsDatasetCompletenessNote</code>) about data completeness (<code>ldqd:completeness</code>) to warn that the dataset includes only 20500 out of the 30000 stops. </p> <aside class="example" id="ex-genoa-bus-stops-dataset-completeness-note"><div class="marker"> <a class="self-link" href="#ex-genoa-bus-stops-dataset-completeness-note">Example<bdi> 41</bdi></a> </div> <pre class="nohighlight turtle">ex:genoaBusStopsDataset a dcat:Dataset ; dqv:hasQualityAnnotation ex:genoaBusStopsDatasetCompletenessNote . ex:genoaBusStopsDatasetCompletenessNote a dqv:UserQualityFeedback ; oa:hasTarget ex:genoaBusStopsDataset ; oa:hasBody ex:textBody ; oa:motivatedBy dqv:qualityAssessment ; prov:wasAttributedTo ex:consumer1 ; prov:generatedAtTime "2018-05-27T02:52:02Z"^^xsd:dateTime ; dqv:inDimension ldqd:completeness . ex:textBody a oa:TextualBody ; rdf:value "Incomplete dataset: it contains only 20500 out of 30000 existing bus stops" ; dc:language "en" ; dc:format "text/plain" .</pre> </aside> <p> The activity <code>ex:myQualityChecking</code> employs the service <code>ex:myQualityChecker</code> to check the quality of the <code>ex:genoaBusStopsDataset</code> dataset. The metric <code>ex:completenessWRTExpectedNumberOfEntities</code> is applied to measure the dataset completeness (<code>ldqd:completeness</code>) and it results in the quality measurement <code>ex:genoaBusStopsDatasetCompletenessMeasurement</code>. </p> <aside class="example" id="ex-genoa-bus-stops-dataset-completeness-measure"><div class="marker"> <a class="self-link" href="#ex-genoa-bus-stops-dataset-completeness-measure">Example<bdi> 42</bdi></a> </div> <pre class="nohighlight turtle">ex:genoaBusStopsDataset dqv:hasQualityMeasurement ex:genoaBusStopsDatasetCompletenessMeasurement . ex:genoaBusStopsDatasetCompletenessMeasurement a dqv:QualityMeasurement ; dqv:computedOn ex:genoaBusStopsDataset ; dqv:isMeasurementOf ex:completenessWRTExpectedNumberOfEntities ; dqv:value "0.6833333"^^xsd:decimal ; prov:wasAttributedTo ex:myQualityChecker ; prov:generatedAtTime "2018-05-27T02:52:02Z"^^xsd:dateTime ; prov:wasGeneratedBy ex:myQualityChecking . ex:completenessWRTExpectedNumberOfEntities a dqv:Metric ; skos:definition "The degree of completeness as ratio between the actual number of entities included in the dataset and the declared expected number of entities."@en ; dqv:expectedDataType xsd:decimal ; dqv:inDimension ldqd:completeness . # ex:myQualityChecker is a service computing some quality metrics ex:myQualityChecker a prov:SoftwareAgent ; rdfs:label "A quality assessment service"@en . # Further details about quality service/software can be provided, for example, # deploying vocabularies such as Dataset Usage Vocabulary (DUV), Dublin Core or ADMS.SW # ex:myQualityChecking is the activity that has generated # ex:genoaBusStopsDatasetCompletenessMeasurement from ex:genoaBusStopsDataset ex:myQualityChecking a prov:Activity ; rdfs:label "The checking of genoaBusStopsDataset's quality"@en ; prov:wasAssociatedWith ex:myQualityChecker ; prov:used ex:genoaBusStopsDataset ; prov:generated ex:genoaBusStopsDatasetCompletenessMeasurement ; prov:endedAtTime "2018-05-27T02:52:02Z"^^xsd:dateTime ; prov:startedAtTime "2018-05-27T00:52:02Z"^^xsd:dateTime .</pre> </aside> <p> Other examples of quality documentation are available in [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>], including examples about <a href="https://www.w3.org/TR/vocab-dqv/#ExpressDatasetAccuracyPrecision">how to express dataset accuracy and precision</a>. </p></section> <section id="quality-conformance"><div class="header-wrapper"><h3 id="x14-2-documenting-conformance-to-standards"><bdi class="secno">14.2 </bdi>Documenting conformance to standards</h3><a class="self-link" href="#quality-conformance" aria-label="Permalink for Section 14.2"></a></div> <p> This section shows different modeling patterns combining [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>] with [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] and EARL [<cite><a class="bibref" data-link-type="biblio" href="#bib-earl10-schema" title="Evaluation and Report Language (EARL) 1.0 Schema">EARL10-Schema</a></cite>] to represent the conformance degree to a stated quality standard and the details about the conformance tests. </p> <section id="quality-conformance-statement"><div class="header-wrapper"><h4 id="x14-2-1-conformance-to-a-standard"><bdi class="secno">14.2.1 </bdi>Conformance to a standard</h4><a class="self-link" href="#quality-conformance-statement" aria-label="Permalink for Section 14.2.1"></a></div> <p>The use of <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/conformsTo"><code>dcterms:conformsTo</code></a> and <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/Standard"><code>dcterms:Standard</code></a> is a well-known pattern to represent the conformance to a standard. <a href="#ex-inspire-conformant-dataset" class="box-ref">Example<bdi> 43</bdi></a>, directly borrowed from [<cite><a class="bibref" data-link-type="biblio" href="#bib-sdw-bp" title="Spatial Data on the Web Best Practices">SDW-BP</a></cite>] (<a href="https://www.w3.org/TR/sdw-bp/#ex-geodcat-ap-dataset-conformance-with-specification">Example 51</a>), declares a fictitious <code>dcat:Dataset</code> conformant to the EU INSPIRE Regulation on interoperability of spatial data sets and services (<a href="http://data.europa.eu/eli/reg/2014/1312/oj">"Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services"</a>).</p> <aside class="example" id="ex-inspire-conformant-dataset"><div class="marker"> <a class="self-link" href="#ex-inspire-conformant-dataset">Example<bdi> 43</bdi></a> </div> <pre class="nohighlight turtle">ex:Dataset-1 a dcat:Dataset; dcterms:conformsTo <http://data.europa.eu/eli/reg/2014/1312/oj> . # Reference standard / specification <http://data.europa.eu/eli/reg/2014/1312/oj> a dcterms:Standard ; dcterms:title "Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services"@en ; dcterms:issued "2010-11-23"^^xsd:date .</pre> </aside> <p>Another example concerns the specification of the coordinate reference system (<abbr title="Coordinate Reference System">CRS</abbr>) used in a dataset - an information which is typically included in geospatial metadata. <a href="#ex-dataset-crs" class="box-ref">Example<bdi> 44</bdi></a> shows how the <abbr title="Coordinate Reference System">CRS</abbr> of a dataset can be specified in DCAT:</p> <aside class="example" id="ex-dataset-crs"><div class="marker"> <a class="self-link" href="#ex-dataset-crs">Example<bdi> 44</bdi></a> </div> <pre class="nohighlight turtle">ex:Dataset-2 a dcat:Dataset; dcterms:conformsTo <http://www.opengis.net/def/crs/EPSG/0/28992> .</pre> </aside> <p>In <a href="#ex-dataset-crs" class="box-ref">Example<bdi> 44</bdi></a>, <code>http://www.opengis.net/def/crs/EPSG/0/28992</code> is an <abbr title="Internationalized Resource Identifier">IRI</abbr> from the OGC <abbr title="Coordinate Reference System">CRS</abbr> Registry, corresponding to <a href="https://epsg.io/28992">EPSG:28992</a> ("Amersfoort / RD New") (see also <a href="#ex-spatial-coverage-geometry-with-crs" class="box-ref">Example<bdi> 30</bdi></a>).</p> <div class="note" role="note" id="issue-container-generatedID-99"><div role="heading" class="note-title marker" id="h-note-98" aria-level="5"><span>Note</span></div><aside class=""> <p>The provision of a resource <abbr title="Coordinate Reference System">CRS</abbr> complies with Best Practice 8 (<a href="https://www.w3.org/TR/sdw-bp/#bp-crs">State how coordinate values are encoded</a>) from [<cite><a class="bibref" data-link-type="biblio" href="#bib-sdw-bp" title="Spatial Data on the Web Best Practices">SDW-BP</a></cite>].</p> </aside></div> <p>In order to ensure interoperability, it is important to consistently use the <abbr title="Internationalized Resource Identifiers">IRIs</abbr> identifying the reference standards / specifications. In particular, DCAT recommends the following general rules:</p> <ul> <li>Use <abbr title="Internationalized Resource Identifiers">IRIs</abbr> from reference registries, when available. Examples include the <a href="https://www.w3.org/TR/"><abbr title="World Wide Web Consortium">W3C</abbr> TR registry</a>, the <a href="https://www.ogc.org/def-server">OGC Definitions Server</a>, the <a href="https://www.iso.org/obp/ui"><abbr title="International Organization for Standardization">ISO</abbr> OBP</a>.</li> <li>Use the <abbr title="Internationalized Resource Identifier">IRI</abbr> of the standard / specification, and not the namespace <abbr title="Internationalized Resource Identifier">IRI</abbr>. E.g., to express conformance of a <code>dcat:CatalogRecord</code> with DCAT, the <abbr title="Internationalized Resource Identifier">IRI</abbr> to be used is <code>https://www.w3.org/TR/vocab-dcat/</code>, and not <code>http://www.w3.org/ns/dcat#</code>.</li> <li>Use the canonical, persistent <abbr title="Internationalized Resource Identifier">IRI</abbr>. This is usually specified in the document itself. If you are in doubt, use the one included in the bibliographic citations for that standard / specification.</li> <li>Use the non-versioned <abbr title="Internationalized Resource Identifier">IRI</abbr>. If you need to express conformance with a specific version of the standard / specification, use both the un-versioned and the versioned <abbr title="Internationalized Resource Identifier">IRI</abbr>. E.g., in case you need to explicitly state conformance of a <code>dcat:CatalogRecord</code> with DCAT 2, use both <code>https://www.w3.org/TR/vocab-dcat/</code> and <code>https://www.w3.org/TR/vocab-dcat-2/</code>.</li> </ul> <p><a href="#ex-catalog-record-schema" class="box-ref">Example<bdi> 45</bdi></a> extends <a href="#ex-catalog-record" class="box-ref">Example<bdi> 9</bdi></a> to show how to specify that a given catalog record is conformant with DCAT, by following the above rules.</p> <aside class="example" id="ex-catalog-record-schema"><div class="marker"> <a class="self-link" href="#ex-catalog-record-schema">Example<bdi> 45</bdi></a> </div> <pre class="nohighlight turtle">ex:catalog dcat:record ex:record-001 . ex:record-001 a dcat:CatalogRecord ; foaf:primaryTopic ex:dataset-001 ; dcterms:issued "2011-12-11"^^xsd:date ; dcterms:conformsTo <https://www.w3.org/TR/vocab-dcat/> ; .</pre> </aside> <aside class="example" id="ex-standards-uris"><div class="marker"> <a class="self-link" href="#ex-standards-uris">Example<bdi> 46</bdi></a><span class="example-title">: IRIs for standards</span> </div> <p>The following table shows the <abbr title="Internationalized Resource Identifiers">IRIs</abbr> of some of the standards used in the examples included in this document.</p> <table class="simple" id="table-uris-for-standards"> <thead> <tr> <th><abbr title="Internationalized Resource Identifier">IRI</abbr></th> <th>Specification</th> </tr> </thead> <tbody> <tr> <td><code>https://www.w3.org/TR/owl2-overview/</code></td> <td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-owl2-overview" title="OWL 2 Web Ontology Language Document Overview (Second Edition)">OWL2-OVERVIEW</a></cite>]</td> </tr> <tr> <td><code>https://www.w3.org/TR/rdf-schema/</code></td> <td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-rdf-schema" title="RDF Schema 1.1">RDF-SCHEMA</a></cite>]</td> </tr> <tr> <td><code>https://www.w3.org/TR/sparql11-protocol/</code></td> <td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-sparql11-protocol" title="SPARQL 1.1 Protocol">SPARQL11-PROTOCOL</a></cite>]</td> </tr> <tr> <td><code>http://www.opengis.net/def/serviceType/ogc/csw/</code></td> <td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-csw" title="Catalogue Services 3.0 - General Model">CSW</a></cite>]</td> </tr> <tr> <td><code>http://www.opengis.net/def/serviceType/ogc/wfs/</code></td> <td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-wfs" title="Web Feature Service 2.0 Interface Standard">WFS</a></cite>]</td> </tr> <tr> <td><code>http://www.opengis.net/def/serviceType/ogc/wms/</code></td> <td>[<cite><a class="bibref" data-link-type="biblio" href="#bib-wms" title="Web Map Service Implementation Specification">WMS</a></cite>]</td> </tr> </tbody> </table> </aside> </section> <section id="quality-conformance-degree"><div class="header-wrapper"><h4 id="x14-2-2-degree-of-conformance"><bdi class="secno">14.2.2 </bdi>Degree of conformance</h4><a class="self-link" href="#quality-conformance-degree" aria-label="Permalink for Section 14.2.2"></a></div> <p>Some legal context requires to specify the degree of conformance. For example, INSPIRE metadata adopts a specific controlled vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-inspire-doc" title="INSPIRE Registry: Degrees of conformity">INSPIRE-DoC</a></cite>] to express non-conformance and non-evaluation beside the full compliance. Similar controlled vocabularies can be defined in other contexts.</p> <p><a href="#ex-conformance-degree" class="box-ref">Example<bdi> 47</bdi></a> specifies some newly minted concepts representing the degree of conformance (i.e., conformant, not conformant) and declares the <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/type"><code>dcterms:type</code></a> for indicating the result of conformance test. Following a pattern used in [<cite><a class="bibref" data-link-type="biblio" href="#bib-geodcat-ap" title="GeoDCAT-AP: A geospatial extension for the DCAT application profile for data portals in Europe">GeoDCAT-AP</a></cite>], the example uses a <code>prov:Entity</code> to model the conformance test (e.g., <code>ex:testResult</code>), a <code>prov:Activity</code> to model the testing activity (e.g., <code>ex:testingActivity</code>), a <code>prov:Plan</code> derived from the Data on the Web Best Practices [<cite><a class="bibref" data-link-type="biblio" href="#bib-dwbp" title="Data on the Web Best Practices">DWBP</a></cite>] (e.g., <code>ex:conformanceTest</code>) to check for the whole set of best practices. A qualified PROV association binds the testing activity to the conformance test.</p> <div class="note" role="note" id="issue-container-generatedID-100"><div role="heading" class="note-title marker" id="h-note-99" aria-level="5"><span>Note</span></div><aside class=""> <p>Depending on the kind of dataset, other best practices and standards, such as the FAIR Principles [<cite><a class="bibref" data-link-type="biblio" href="#bib-fair" title="The FAIR Guiding Principles for scientific data management and stewardship">FAIR</a></cite>] or the Spatial Data on the Web Best Practices [<cite><a class="bibref" data-link-type="biblio" href="#bib-sdw-bp" title="Spatial Data on the Web Best Practices">SDW-BP</a></cite>], can be considered as a replacement or used in combination with [<cite><a class="bibref" data-link-type="biblio" href="#bib-dwbp" title="Data on the Web Best Practices">DWBP</a></cite>].</p> </aside></div> <aside class="example" id="ex-conformance-degree"><div class="marker"> <a class="self-link" href="#ex-conformance-degree">Example<bdi> 47</bdi></a> </div> <pre class="nohighlight turtle">ex:Dataset-3 a dcat:Dataset ; prov:wasUsedBy ex:testingActivity . ex:testingActivity a prov:Activity ; prov:generated ex:testResult ; prov:qualifiedAssociation [ a prov:Association ; # http://validator.example.org/ is the agent who ran the test. prov:agent <http://validator.example.org/> # following the plan ex:conformanceTest prov:hadPlan ex:conformanceTest ] . # Conformance test result ex:testResult a prov:Entity ; prov:wasGeneratedBy ex:testingActivity; # ex:notConformant belongs to a SKOS concept scheme about conformance dcterms:type ex:notConformant . ex:conformanceTest a prov:Plan ; # Here one can specify additional information on the test, which in the example is derived by the W3C Data on the Web Best Practices prov:wasDerivedFrom <https://www.w3.org/TR/dwbp/> .</pre> </aside> <p>Also, [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>] can be deployed to measure the compliance to a specific standard. In <a href="#ex-conformance-degree-percentage" class="box-ref">Example<bdi> 48</bdi></a>, the <code>ex:levelOfComplianceToDWBP</code> is a quality metrics which measures the compliance of a dataset to [<cite><a class="bibref" data-link-type="biblio" href="#bib-dwbp" title="Data on the Web Best Practices">DWBP</a></cite>] in terms of the percentage of passed compliance tests. <a href="#ex-conformance-degree-percentage" class="box-ref">Example<bdi> 48</bdi></a> assumes <code>iso</code> as a namespace prefix representing the quality dimensions and categories defined in the <abbr title="International Organization for Standardization">ISO</abbr>/IEC 25012 [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-iec-25012" title="ISO/IEC 25012 - Data Quality model">ISO-IEC-25012</a></cite>].</p> <aside class="example" id="ex-conformance-degree-percentage"><div class="marker"> <a class="self-link" href="#ex-conformance-degree-percentage">Example<bdi> 48</bdi></a> </div> <pre class="nohighlight turtle">ex:levelOfComplianceToDWBP a dqv:Metric ; skos:definition "The degree of compliance to DWBP defined as the percentage of passed compliance tests."@en ; dqv:expectedDataType xsd:double ; dqv:inDimension iso:compliance . iso:compliance a dqv:Dimension ; skos:prefLabel "Compliance"@en ; skos:definition "The degree to which data has attributes that adhere to standards, conventions or regulations in force and similar rules relating to data quality in a specific context of use."@en ; dqv:inCategory iso:inherentAndSystemDependentDataQuality . iso:inherentAndSystemDependentDataQuality a dqv:Category ; skos:prefLabel "Inherent and System-Dependent Data Quality"@en .</pre> </aside> <p>The quality measurement <code>ex:measurement_complianceToDWBP</code> represents the level of compliance for dataset <code>ex:Dataset</code>, namely, measurement of the metric <code>ex:levelOfComplianceToDWBP</code>. If only a part of the compliance tests succeeds (e.g., half of the compliance tests), the measurement would look like in <a href="#ex-conformance-test-partial-success" class="box-ref">Example<bdi> 49</bdi></a>.</p> <aside class="example" id="ex-conformance-test-partial-success"><div class="marker"> <a class="self-link" href="#ex-conformance-test-partial-success">Example<bdi> 49</bdi></a> </div> <pre class="nohighlight turtle">ex:measurement_complianceToDWBP a dqv:QualityMeasurement ; dqv:computedOn ex:Dataset ; dqv:value "50"^^xsd:double ; sdmx-attribute:unitMeasure <http://www.wurvoc.org/vocabularies/om-1.8/Percentage> ; dcterms:date "2018-01-10"^^xsd:date ; dqv:isMeasurementOf ex:levelOfComplianceToDWBP .</pre> </aside> </section> <section id="quality-conformance-test-results"><div class="header-wrapper"><h4 id="x14-2-3-conformance-test-results"><bdi class="secno">14.2.3 </bdi>Conformance test results</h4><a class="self-link" href="#quality-conformance-test-results" aria-label="Permalink for Section 14.2.3"></a></div> <p> Further information about the tests can be provided using EARL [<cite><a class="bibref" data-link-type="biblio" href="#bib-earl10-schema" title="Evaluation and Report Language (EARL) 1.0 Schema">EARL10-Schema</a></cite>]. EARL provides specific classes to describe the testing activity, which can be adopted in conjunction with [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>]. <a href="#ex-conformance-test-results-earl" class="box-ref">Example<bdi> 50</bdi></a> describes the Testing activity <code>ex:testingActivity</code> as an <code>earl:Assertion</code> instead of a qualified association on the <code>prov:Activity</code>. The <code>earl:Assertion</code> states that dataset <code>ex:Dataset</code> has been tested with the conformance test <code>ex:conformanceTest</code>, and it has passed the test as described in <code>ex:testResult</code>. </p> <aside class="example" id="ex-conformance-test-results-earl"><div class="marker"> <a class="self-link" href="#ex-conformance-test-results-earl">Example<bdi> 50</bdi></a> </div> <pre class="nohighlight turtle">ex:assertion a earl:Assertion ; earl:subject ex:Dataset ; earl:test ex:conformanceTest ; earl:result ex:testResult ; # let's indicate if the test was manual, automatic, or what .. earl:mode earl:automatic ; earl:assertedBy <http://validator.example.org/> ; prov:wasAttributedTo <http://validator.example.org/> . ex:conformanceTest a earl:TestRequirement, prov:Plan ; dcterms:title "Set of conformance test derived from the W3C Data on the Web Best Practices"@en ; # it includes different subtests dcterms:hasPart ex:testBP1, ex:testBP2, ..., ex:testBP35 ; #It is derived by the reference standard prov:wasDerivedFrom <https://www.w3.org/TR/dwbp/> . ex:testResult a earl:TestResult ; # results in conformancy . dcterms:type ex:conformant ; prov:wasGeneratedBy ex:testingActivity; #the overall set of tests have been passed earl:outcome earl:passed . # the description of the validator <http://validator.example.org/> a earl:Assertor, prov:Agent ; dcterms:description "A test execution service that runs conformance test suites."@en ; dcterms:title "Validator"@en . #the testing activity ex:testingActivity a prov:Activity ; prov:generated ex:assertion, ex:testResult ; prov:use ex:Dataset ; prov:wasAssociatedWith <http://validator.example.org/> .</pre> </aside> <p><a href="#ex-conformance-test-earl-fail" class="box-ref">Example<bdi> 51</bdi></a> shows how the description would have looked like if the subtest <code>ex:testq1</code> had failed. In particular, <code>dcterms:description</code> and <code>earl:info</code> provide additional warnings or error messages in a human-readable form.</p> <aside class="example" id="ex-conformance-test-earl-fail"><div class="marker"> <a class="self-link" href="#ex-conformance-test-earl-fail">Example<bdi> 51</bdi></a> </div> <pre class="nohighlight turtle">ex:assertion1 a earl:Assertion ; earl:subject ex:Dataset ; earl:test ex:testq1 ; earl:result [ a earl:TestResult ; # results in no conformancy dcterms:type ex:nonConformant ; #the overall set of tests have not been passed (!?) dcterms:date "2015-09-29T11:50:00+00:00"^^xsd:dateTime ; # Some XML encoding of the error dcterms:description """ <ul xmlns="http://www.w3.org/1999/xhtml"> <li> test 1 has failed. Some description of the errors found</li> </ul>"""^^rdf:HTML ; earl:info """ <test-method duration-ms="47" finished-at="2015-09-29T11:50:00Z" name="validate" signature="validate()" started-at="2015-09-29T11:50:00Z" status="FAIL"> <exception class="java.lang.AssertionError"> <message> Total validation errors found: 2 </message> </exception> </test-method>"""^^rdf:XMLLiteral ; earl:outcome earl:fail . ]; # we do not know if the test was manual, automatic, or what .. earl:mode earl:automatic.</pre> </aside> <p>Depending on the details required about tests, [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dqv" title="Data on the Web Best Practices: Data Quality Vocabulary">VOCAB-DQV</a></cite>] can express the testing activity and errors as well. In <a href="#ex-conformance-test-error" class="box-ref">Example<bdi> 52</bdi></a>, <code>ex:error</code> is a quality annotation that represents the previous error, and <code>ex:testResult</code> is defined as a <code>dqv:QualityMetadata</code> to collect the above annotations and the compliance measurements providing provenance information. </p><aside class="example" id="ex-conformance-test-error"><div class="marker"> <a class="self-link" href="#ex-conformance-test-error">Example<bdi> 52</bdi></a> </div> <pre class="nohighlight turtle">ex:errors a dqv:QualityAnnotation ; #this annotation is derived by the measurement prov:wasGeneratedBy ex:testingActivity; oa:hasTarget ex:Dataset ; oa:hasBody [ #errors/failed test description a oa:TextualBody ; rdf:value """ <test-method duration-ms="47" finished-at="2015-09-29T11:50:00Z" name="validate" signature="validate()" started-at="2015-09-29T11:50:00Z" status="FAIL"> <exception class="java.lang.AssertionError"> <message> Total validation errors found: 2 </message> </exception> </test-method>"""^^rdf:XMLLiteral ; #it can be in any format supported by dc dc:format "application/xml" ; ] ; oa:motivatedBy dqv:qualityAssessment , oa:assessing ; dqv:inDimension iso:compliance ; . ex:testResult a dqv:QualityMetadata ; # change the the dcterms:type according to the resulted compliance dcterms:type <http://inspire.ec.europa.eu/metadata-codelist/DegreeOfConformity/conformant> ; prov:wasAttributedTo <http://validator.example.org/> ; prov:generatedAtTime "2018-05-27T02:52:02Z"^^xsd:dateTime ; prov:wasGeneratedBy ex:testingActivity . # The graph contains the rest of the statements presented in the previous examples. # The graph is expressed according to TRIG syntax not TTL (see https://www.w3.org/TR/trig/) ex:testResult { a dcat:Dataset ; dqv:hasQualityMeasurement ex:measurement_complianceToDWBP ; dqv:hasQualityAnnotation ex:errors . } #the testing activity ex:testingActivity a prov:Activity ; prov:generated ex:testResult ; prov:use ex:Dataset ; prov:wasAssociatedWith <http://validator.example.org/> ; .</pre> </aside> <p>Of course, the above modeling patterns can represent any quality tests, not only conformance to standards.</p> </section> </section> </section> <section id="qualified-forms" class="informative"><div class="header-wrapper"><h2 id="x15-qualified-relations"><bdi class="secno">15. </bdi>Qualified relations</h2><a class="self-link" href="#qualified-forms" aria-label="Permalink for Section 15."></a></div><p><em>This section is non-normative.</em></p> <p> DCAT includes elements to support description of many aspects of datasets and data services. Nevertheless, additional information is required in order to fully express the semantics of some relationships. An example is that, while [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] provides the standard roles <b>creator</b>, <b>contributor</b> and <b>publisher</b> for attribution of a resource to a responsible party or agent, there are many other potential roles, see for example the <a href="https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml"><code>CI_RoleCode</code></a> values from [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115-1" title="Geographic information -- Metadata -- Part 1: Fundamentals">ISO-19115-1</a></cite>]. Similarly, while [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] and [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] provide some properties to capture relationships between resources, including <b>was derived from</b>, <b>was quoted from</b>, <b>is version of</b>, <b>references</b> and several others, many additional concerns are seen in the list of [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115-1" title="Geographic information -- Metadata -- Part 1: Fundamentals">ISO-19115-1</a></cite>] <a href="https://standards.iso.org/iso/19115/resources/Codelists/gml/DS_AssociationTypeCode.xml"><code>DS_AssociationTypeCodes</code></a>, the IANA Registry of Link Relations [<cite><a class="bibref" data-link-type="biblio" href="#bib-iana-relations" title="Link Relations">IANA-RELATIONS</a></cite>], the DataCite metadata schema [<cite><a class="bibref" data-link-type="biblio" href="#bib-datacite" title="DataCite Metadata Schema">DataCite</a></cite>] and the <a href="https://id.loc.gov/vocabulary/relators">MARC relators</a>. While these relations could be captured with additional sub-properties of <code>dcterms:relation</code>, <code>dcterms:contributor</code>, etc., this would lead to an explosion in the number of properties, and anyway the full set of potential roles and relationships is unknown. </p> <p> A common approach for meeting these kinds of requirements is to introduce an additional resource to carry parameters that qualify the relationship. Precedents are the <a href="https://www.w3.org/TR/prov-o/#description-qualified-terms">qualified terms</a> in [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] and the <a href="https://www.w3.org/TR/vocab-ssn/#Sample_Relations">sample relations</a> in the Semantic Sensor Network ontology [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-ssn" title="Semantic Sensor Network Ontology">VOCAB-SSN</a></cite>]. The general <a href="http://patterns.dataincubator.org/book/qualified-relation.html">Qualified Relation pattern</a> is described in [<cite><a class="bibref" data-link-type="biblio" href="#bib-linkeddatapatterns" title="Linked Data Patterns: A pattern catalogue for modelling, publishing, and consuming Linked Data">LinkedDataPatterns</a></cite>]. </p> <p> Many of the qualified terms from [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] are relevant to the description of resources in catalogs but these are incomplete due to the activity-centric viewpoint taken by PROV-O. Addressing some of the gaps, additional forms are included in the DCAT vocabulary to satisfy requirements that do not involve explicit activities. These are summarized in <a href="#fig-dcat-relationships" class="fig-ref" title="Qualified relationships support an extensible set of roles relating resources to agents or to other resources">Figure <bdi class="">6</bdi></a>: </p> <figure id="fig-dcat-relationships"><img alt="UML model of DCAT qualified relationships" src="images/dcat-relationships.svg"> <figcaption><a class="self-link" href="#fig-dcat-relationships">Figure <bdi class="figno">6</bdi></a> <span class="fig-title"> Qualified relationships support an extensible set of roles relating resources to agents or to other resources </span></figcaption> </figure> <p> Note that, while the focus of these qualified forms is to allow for additional <i>roles</i> on a relationship, other aspect of the relationships, such as the applicable time interval, are easily attached when a specific node is used to describe the relationship like this (e.g., see the <a href="https://www.w3.org/TR/prov-o/#qualified-terms-figure">chart of Influence relations</a> in [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] for some examples). </p> <div class="note" role="note" id="issue-container-generatedID-101"><div role="heading" class="note-title marker" id="h-note-100" aria-level="3"><span>Note</span></div><aside class=""> <p> Because of the global domain constraints on <a href="https://www.w3.org/TR/prov-o/#qualifiedAttribution"><code>prov:qualifiedAttribution</code></a> and the super-property of <a href="#Property:resource_qualified_relation"><code>dcat:qualifiedRelation</code></a>, use of the qualified forms entail that the context resource is a member of the class <a href="https://www.w3.org/TR/prov-o/#Entity"><code>prov:Entity</code></a> [<cite><a class="bibref" data-link-type="biblio" href="#bib-rdf-schema" title="RDF Schema 1.1">RDF-SCHEMA</a></cite>]. </p> </aside></div> <section id="qualified-attribution"><div class="header-wrapper"><h3 id="x15-1-relationships-between-datasets-and-agents"><bdi class="secno">15.1 </bdi>Relationships between datasets and agents</h3><a class="self-link" href="#qualified-attribution" aria-label="Permalink for Section 15.1"></a></div> <p> The standard [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] properties <a href="http://purl.org/dc/terms/contributor"><code>dcterms:contributor</code></a>, <a href="http://purl.org/dc/terms/creator"><code>dcterms:creator</code></a> and <a href="http://purl.org/dc/terms/publisher"><code>dcterms:publisher</code></a>, and the generic <a href="https://www.w3.org/TR/prov-o/#wasAttributedTo"><code>prov:wasAttributedTo</code></a> from [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>], support basic associations of responsible agents with a cataloged resource. However, there are many other roles of importance in relation to datasets and services - e.g., funder, distributor, custodian, editor. Some of these roles are enumerated in the <a href="https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml"><code>CI_RoleCode</code></a> values from [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115-1" title="Geographic information -- Metadata -- Part 1: Fundamentals">ISO-19115-1</a></cite>], in the [<cite><a class="bibref" data-link-type="biblio" href="#bib-datacite" title="DataCite Metadata Schema">DataCite</a></cite>] metadata schema, and included within the <a href="https://id.loc.gov/vocabulary/relators">MARC relators</a>. </p> <p> A general method for assigning an agent to a resource with a specified role is provided by using the qualified form <a href="https://www.w3.org/TR/prov-o/#qualifiedAttribution"><code>prov:qualifiedAttribution</code></a> from [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>]. <a href="#ex-qualified-attribution" class="box-ref">Example<bdi> 53</bdi></a> provides an illustration: </p> <aside id="ex-qualified-attribution" class="example"><div class="marker"> <a class="self-link" href="#ex-qualified-attribution">Example<bdi> 53</bdi></a> </div> <pre class="nohighlight turtle">ex:DS987 a dcat:Dataset ; prov:qualifiedAttribution [ a prov:Attribution ; prov:agent <https://www.ala.org.au/> ; dcat:hadRole <urn:example:isotc211/CI_RoleCode/distributor> ] ; prov:qualifiedAttribution [ a prov:Attribution ; prov:agent <https://www.education.gov.au/> ; dcat:hadRole <urn:example:isotc211/CI_RoleCode/funder> ] ; .</pre> </aside> <p> In <a href="#ex-qualified-attribution" class="box-ref">Example<bdi> 53</bdi></a> the roles are denoted by <abbr title="Internationalized Resource Identifiers">IRIs</abbr> from a non-normative, non-dereferenceable representation of the <a href="https://standards.iso.org/iso/19115/resources/Codelists/gml/CI_RoleCode.xml"><code>CI_RoleCode</code></a> codelist from [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115-1" title="Geographic information -- Metadata -- Part 1: Fundamentals">ISO-19115-1</a></cite>] (e.g., URN like <code>urn:example:isotc211/CI_RoleCode</code>). Linked data dereferenceable and normative representations should be preferred when available. </p> <div class="note" role="note" id="issue-container-generatedID-102"><div role="heading" class="note-title marker" id="h-note-101" aria-level="4"><span>Note</span></div><aside class=""> <p>The domain of <a href="https://www.w3.org/TR/prov-o/#hadRole"><code>prov:hadRole</code></a> property is <a href="https://www.w3.org/TR/prov-o/#Association"><code>prov:Association</code></a>, i.e., [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] roles relate to activities, not entities [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>]. Therefore, a new property <a href="#Property:relationship_hadRole"><code>dcat:hadRole</code></a> is used to attach a specific role to the association-class <a href="https://www.w3.org/TR/prov-o/#Attribution"><code>prov:Attribution</code></a>.</p> </aside></div> </section> <section id="qualified-relationship"><div class="header-wrapper"><h3 id="x15-2-relationships-between-datasets-and-other-resources"><bdi class="secno">15.2 </bdi>Relationships between datasets and other resources</h3><a class="self-link" href="#qualified-relationship" aria-label="Permalink for Section 15.2"></a></div> <p> The standard [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] properties <a href="http://purl.org/dc/terms/relation"><code>dcterms:relation</code></a> and sub-properties such as <a href="http://purl.org/dc/terms/hasPart"><code>dcterms:hasPart</code></a> / <a href="http://purl.org/dc/terms/isPartOf"><code>dcterms:isPartOf</code></a>, <a href="http://purl.org/dc/terms/hasVersion"><code>dcterms:hasVersion</code></a> / <a href="http://purl.org/dc/terms/isVersionOf"><code>dcterms:isVersionOf</code></a>, <a href="http://purl.org/dc/terms/replaces"><code>dcterms:replaces</code></a> / <a href="http://purl.org/dc/terms/isReplacedBy"><code>dcterms:isReplacedBy</code></a>, <a href="http://purl.org/dc/terms/requires"><code>dcterms:requires</code></a> / <a href="http://purl.org/dc/terms/isRequiredBy"><code>dcterms:isRequiredBy</code></a>, <a href="https://www.w3.org/TR/prov-o/#wasDerivedFrom"><code>prov:wasDerivedFrom</code></a>, <a href="https://www.w3.org/TR/prov-o/#wasQuotedFrom"><code>prov:wasQuotedFrom</code></a>, support the description of relationships between datasets and other cataloged resources. However, there are many other relationships of importance - e.g., alternate, canonical, original, preview, stereo-mate, working-copy-of. Some of these roles are enumerated in the <a href="https://standards.iso.org/iso/19115/resources/Codelists/gml/DS_AssociationTypeCode.xml"><code>DS_AssociationTypeCodes</code></a> values from [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115-1" title="Geographic information -- Metadata -- Part 1: Fundamentals">ISO-19115-1</a></cite>], the IANA Registry of Link Relations [<cite><a class="bibref" data-link-type="biblio" href="#bib-iana-relations" title="Link Relations">IANA-RELATIONS</a></cite>], in the [<cite><a class="bibref" data-link-type="biblio" href="#bib-datacite" title="DataCite Metadata Schema">DataCite</a></cite>] metadata schema, and included within the <a href="https://id.loc.gov/vocabulary/relators">MARC relators</a>. </p><p> </p><p> A general method for relating a resource to another resource with a specified role is provided by using the qualified form <a href="#Property:resource_qualified_relation"><code>dcat:qualifiedRelation</code></a>. <a href="#ex-dataset-resource" class="box-ref">Example<bdi> 54</bdi></a> provides illustrations: </p> <aside id="ex-dataset-resource" class="example"><div class="marker"> <a class="self-link" href="#ex-dataset-resource">Example<bdi> 54</bdi></a> </div> <pre class="nohighlight turtle">ex:Test987 a dcat:Dataset ; dcat:qualifiedRelation [ a dcat:Relationship ; dcterms:relation <http://dcat.example.org/Original987> ; dcat:hadRole <http://www.iana.org/assignments/relation/original> ] ; . ex:Test543L a dcat:Dataset ; dcat:qualifiedRelation [ a dcat:Relationship ; dcterms:relation <http://dcat.example.org/Test543R> ; dcat:hadRole <urn:example:isotc211/DS_AssociationTypeCode/stereoMate> ] ; .</pre> </aside> <p> In <a href="#ex-dataset-resource" class="box-ref">Example<bdi> 54</bdi></a> the roles are denoted by <abbr title="Internationalized Resource Identifiers">IRIs</abbr> from [<cite><a class="bibref" data-link-type="biblio" href="#bib-iana-relations" title="Link Relations">IANA-RELATIONS</a></cite>] and from a (non-normative) <a href="https://web.archive.org/web/20211206184420/http://registry.it.csiro.au/def/isotc211/DS_AssociationTypeCode">linked data representation</a> of the <a href="https://standards.iso.org/iso/19115/resources/Codelists/gml/DS_AssociationTypeCode.xml"><code>DS_AssociationTypeCode</code></a> codelist from [<cite><a class="bibref" data-link-type="biblio" href="#bib-iso-19115-1" title="Geographic information -- Metadata -- Part 1: Fundamentals">ISO-19115-1</a></cite>]. </p> <div class="note" role="note" id="issue-container-generatedID-103"><div role="heading" class="note-title marker" id="h-note-102" aria-level="4"><span>Note</span></div><aside class=""> <p>The property <a href="#Property:resource_qualified_relation"><code>dcat:qualifiedRelation</code></a> and association-class <a href="#Class:Relationship"><code>dcat:Relationship</code></a> follow the pattern established in <abbr title="World Wide Web Consortium">W3C</abbr> [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] and described in <a href="https://www.w3.org/TR/prov-o/#description-qualified-terms">§ <span class="secno">3.3 </span>Qualified Terms</a>. However, [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>] is activity-centric, and does not support Entity-Entity relations except for the single case of 'was derived from', thus necessitating the new elements shown here to support the general case.</p> </aside></div> </section> </section> <section id="profiles" class="informative"><div class="header-wrapper"><h2 id="x16-dcat-profiles"><bdi class="secno">16. </bdi>DCAT Profiles</h2><a class="self-link" href="#profiles" aria-label="Permalink for Section 16."></a></div><p><em>This section is non-normative.</em></p> <p> The DCAT-2014 vocabulary [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>] and DCAT 2 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-2" title="Data Catalog Vocabulary (DCAT) - Version 2">VOCAB-DCAT-2</a></cite>] have been extended for application in data catalogs in different domains. Each of these new specifications constitutes a DCAT profile, i.e., a named set of constraints based on DCAT (see <a href="#conformance" class="sec-ref"><bdi class="secno">4. </bdi>Conformance</a>). In some cases, a profile extends one of the DCAT profiles themselves, by adding classes and properties for metadata fields not covered in the reference DCAT profile. </p> <p>Some of the DCAT profiles are:</p> <ul> <li>DCAT-AP [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap" title="DCAT Application Profile for data portals in Europe. Version 2.0.1">DCAT-AP</a></cite>]: The <cite>DCAT application profile for data portals in Europe</cite></li> <li>GeoDCAT-AP [<cite><a class="bibref" data-link-type="biblio" href="#bib-geodcat-ap" title="GeoDCAT-AP: A geospatial extension for the DCAT application profile for data portals in Europe">GeoDCAT-AP</a></cite>]: Geospatial profile of [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap" title="DCAT Application Profile for data portals in Europe. Version 2.0.1">DCAT-AP</a></cite>]</li> <li>StatDCAT-AP [<cite><a class="bibref" data-link-type="biblio" href="#bib-statdcat-ap" title="StatDCAT-AP – DCAT Application Profile for description of statistical datasets. Version 1.0.1">StatDCAT-AP</a></cite>]: Statistical profile of [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap" title="DCAT Application Profile for data portals in Europe. Version 2.0.1">DCAT-AP</a></cite>]</li> <li>DCAT-AP_IT [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap-it" title="Profilo metadatazione DCAT-AP_IT">DCAT-AP-IT</a></cite>]: Italian profile of [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap" title="DCAT Application Profile for data portals in Europe. Version 2.0.1">DCAT-AP</a></cite>]</li> <li>GeoDCAT-AP_IT [<cite><a class="bibref" data-link-type="biblio" href="#bib-geodcat-ap-it" title="GeoDCAT-AP in Italy, the national guidelines published">GeoDCAT-AP-IT</a></cite>]: Italian profile of [<cite><a class="bibref" data-link-type="biblio" href="#bib-geodcat-ap" title="GeoDCAT-AP: A geospatial extension for the DCAT application profile for data portals in Europe">GeoDCAT-AP</a></cite>]</li> <li>DCAT-AP-NO [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap-no" title="Standard for beskrivelse av datasett, datatjenester og datakataloger (DCAT-AP-NO)">DCAT-AP-NO</a></cite>]: Norwegian profile of [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap" title="DCAT Application Profile for data portals in Europe. Version 2.0.1">DCAT-AP</a></cite>]</li> <li>DCAT-AP.de [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap.de" title="Vokabulare und Dokumente für DCAT-AP.de">DCAT-AP.de</a></cite>]: German profile of [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap" title="DCAT Application Profile for data portals in Europe. Version 2.0.1">DCAT-AP</a></cite>]</li> <li>DCAT-BE [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-be" title="Linking data portals across Belgium.">DCAT-BE</a></cite>]: Belgian profile of [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap" title="DCAT Application Profile for data portals in Europe. Version 2.0.1">DCAT-AP</a></cite>]</li> <li>DCAT-AP-SE [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap-se" title="DCAT-AP-SE: Clarifications, translations and explanations of DCAT-AP for Sweden">DCAT-AP-SE</a></cite>]: Swedish profile of [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcat-ap" title="DCAT Application Profile for data portals in Europe. Version 2.0.1">DCAT-AP</a></cite>]</li> </ul> </section> <section id="security_and_privacy"><div class="header-wrapper"><h2 id="x17-security-and-privacy-considerations"><bdi class="secno">17. </bdi>Security and Privacy Considerations</h2><a class="self-link" href="#security_and_privacy" aria-label="Permalink for Section 17."></a></div> <p> The DCAT vocabulary supports datasets that may contain personal or private information. In addition, the metadata expressed with DCAT may itself contain personal or private information, such as resource <a href="#Property:resource_creator">creators</a>, <a href="#Property:resource_publisher">publishers</a>, and other parties or agents described via <a href="#qualified-forms">qualified relations</a>. Implementers who produce, maintain, publish or consume such vocabulary terms must take steps to ensure security and privacy considerations are addressed. Sensitive data and metadata must be stored securely and made available only to authorized parties, in accordance with the legal and functional requirements of the type of data involved. Detailing how to secure web content and authenticate users is beyond the scope of DCAT. </p> <p>Some datasets require assurances of integrity and authenticity (for example, data about software vulnerabilities). For these, checksums can serve as a type of verification. DCAT borrows the <a href="#Class:Checksum"><code>spdx:Checksum</code></a> class from [<cite><a class="bibref" data-link-type="biblio" href="#bib-spdx" title="SPDX 2.2">SPDX</a></cite>] to ensure the integrity and authenticity of DCAT distributions. Publishers may provide a checksum value (a hash) and the algorithm used to generate the hash for each resource in the distribution. A checksum must, however, be provided via a route that is separate from the data it sums. It may be included in metadata that is provided with the data (e.g., a tarfile that includes a file for the distribution and a file for the metadata that includes a checksum for the distribution file), but if so the checksum, or a checksum for the metadata, must also be provided separately to foil an attacker who would manipulate the checksum along with the data. A checksum provided in DCAT metadata will not provide the expected assurances if the integrity and authenticity of the metadata are not also guaranteed. </p> <p>Integrity and authenticity of DCAT data ultimately depend on the trustworthiness of the source. DCAT providers should address integrity and authenticity at the application level and transport level. For example, they should ensure the integrity and authenticity of their <abbr title="Application Programming Interface">API</abbr> and download endpoints, make DCAT data and metadata files downloadable from authoritative HTTPS origins, and provide any checksums via a separate channel from the data they represent. </p> </section> <section id="accessibility"><div class="header-wrapper"><h2 id="x18-accessibility-considerations"><bdi class="secno">18. </bdi>Accessibility Considerations</h2><a class="self-link" href="#accessibility" aria-label="Permalink for Section 18."></a></div> <p> The DCAT vocabulary provides a model for describing data catalogs. The nature of data in the catalogs depends on the specific domains of application and might include non-text data. When possible, it is important to enforce alternative text for non-text data resources through the DCAT profile mechanisms or systems supporting the creation and editing of such data to improve the accessibility to data. The practice to provide text alternatives for any non-text content, which can be changed into other forms people need, such as large print, braille, speech, symbols, or simpler language complies with accessibility guidelines included in [<cite><a class="bibref" data-link-type="biblio" href="#bib-understanding-wcag20" title="Understanding WCAG 2.0">UNDERSTANDING-WCAG20</a></cite>]. </p> </section> <section id="acknowledgments" class="appendix"><div class="header-wrapper"><h2 id="a-acknowledgments"><bdi class="secno">A. </bdi>Acknowledgments</h2><a class="self-link" href="#acknowledgments" aria-label="Permalink for Appendix A."></a></div> <p>The editors gratefully acknowledge the contributions made to this document by <a href="https://www.w3.org/groups/wg/dx/participants">all members of the working group</a>, especially Annette Greiner, Antoine Isaac, Dan Brickley, Karen Coyle, Lars G. Svensson, Makx Dekkers, Nicholas Car, Rob Atkinson, Tom Baker. </p> <p>The editors would also like to thank the following for comments received: Addison Phillips, Alex Nelson, Andreas Geißner, Andreas Kuckartz, Anna Odgaard Ingram, Aymen Charef, Bart Hanssens, Becky Gibson, Bert van Nuffelen, Bob Coret, Brian Donohue, Chavdar Ivanov, Claus Stadler, Cristiano Longo, Christophe Dzikowski, Dimitris Zeginis, Dominik Schneider, Emidio Stani, Ivo Velitchkov, Jakob Voß, Jakub Klímek, Jan Voskuil, Jim J. Yang, Joep Meindertsma, Joep van Genuchten, Katherine Anderson Aur, Ludger A. Rinsche, Marielle Adam, Martial Honsberger, Mathias Bonduel, Mathias Richter, Matthias Palmér, Nancy Jean, Nuno Freire, Øystein Åsnes, Paul van Genuchten, Pieter J. C. van Everdingen, Renato Iannella, Rajaram Kaliyaperumal, Robin Gower, Sabine Maennel, Sebastian Hellman, Simson L. Garfinkel, Siri Jodha S. Khalsa, Stefan Ollinger, Stephen Richard, Stian Soiland-Reyes, Stig B. Dørmænen, Susheel Varma, Sidney Cox, Thomas Francart, Vittorio Meloni, Wouter Beek, Yves Coene. </p> <p>The editors also gratefully acknowledge the chairs of this Working Group: Caroline Burle and Peter Winstanley — and staff contacts Philippe Le Hégaret and Pierre-Antoine Champin.</p> </section> <section id="dcat-sdo" class="appendix informative"><div class="header-wrapper"><h2 id="b-alignment-with-schema-org"><bdi class="secno">B. </bdi>Alignment with Schema.org</h2><a class="self-link" href="#dcat-sdo" aria-label="Permalink for Appendix B."></a></div><p><em>This section is non-normative.</em></p> <div class="note" role="note" id="issue-container-generatedID-104"><div role="heading" class="note-title marker" id="h-note-103" aria-level="3"><span>Note</span></div><aside class=""> <p> See the issues on <a href="https://github.com/w3c/dxwg/labels/alignment">Alignments and Crosswalks</a> for more discussion. </p> </aside></div> <p> Schema.org [<cite><a class="bibref" data-link-type="biblio" href="#bib-schema-org" title="Schema.org">SCHEMA-ORG</a></cite>] includes a number of types and properties based on the original DCAT work (see <a href="https://schema.org/Dataset">sdo:Dataset</a> as a starting point), and the index for Google's <a href="https://g.co/datasetsearch">Dataset Search service</a> relies on structured description in Web pages about datasets using both <a href="https://developers.google.com/search/docs/data-types/dataset">schema.org and DCAT</a>. A comparison of the DCAT backbone, shown in <a href="#fig-dcat-all-attributes" class="fig-ref" title="Overview of DCAT model, showing the classes of resources that can be members of a Catalog, and the relationships between them. Except where specifically indicated, DCAT does not provide cardinality constraints.">Figure <bdi class="">1</bdi></a> above with the related classes from [<cite><a class="bibref" data-link-type="biblio" href="#bib-schema-org" title="Schema.org">SCHEMA-ORG</a></cite>] in <a href="#UML_SchemaOrg_Data_Cat" class="fig-ref" title="schema.org support for dataset catalogs, showing a selection of schema.org properties related to the classes shown">Figure <bdi class="">7</bdi></a> shows the similarity, in particular: . </p> <ul> <li> the distinction between (abstract) Dataset and (concrete) DataDownload matches dcat:Dataset / dcat:Distribution </li> <li> the relationship of Datasets to DataCatalogs </li> </ul> <figure id="UML_SchemaOrg_Data_Cat"><img alt="UML model of schema.org classes and properties related to dataset catalogs" src="images/schema.org-dataset.svg"> <figcaption><a class="self-link" href="#UML_SchemaOrg_Data_Cat">Figure <bdi class="figno">7</bdi></a> <span class="fig-title"> schema.org support for dataset catalogs, showing a selection of schema.org properties related to the classes shown </span></figcaption> </figure> <p> General purpose Web search services that use metadata at all rely primarily on [<cite><a class="bibref" data-link-type="biblio" href="#bib-schema-org" title="Schema.org">SCHEMA-ORG</a></cite>], so the relationship of DCAT to [<cite><a class="bibref" data-link-type="biblio" href="#bib-schema-org" title="Schema.org">SCHEMA-ORG</a></cite>] is of interest for data providers and catalog publishers who wish their datasets and services to be exposed through those indexes. </p> <p> A <a href="https://www.w3.org/wiki/WebSchemas/Datasets">mapping between DCAT 1 and schema.org</a> was discussed on the original proposal to extend [<cite><a class="bibref" data-link-type="biblio" href="#bib-schema-org" title="Schema.org">SCHEMA-ORG</a></cite>] for describing datasets and data catalogs. Partial mappings between DCAT 1 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-1" title="Data Catalog Vocabulary (DCAT)">VOCAB-DCAT-1</a></cite>] and [<cite><a class="bibref" data-link-type="biblio" href="#bib-schema-org" title="Schema.org">SCHEMA-ORG</a></cite>] were provided earlier by the <a href="https://www.w3.org/2015/spatial/wiki/ISO_19115_-_DCAT_-_Schema">Spatial Data on the Web Working Group</a>, building upon previous work. </p> <p> A recommended mapping from the revised DCAT (this document) to [<cite><a class="bibref" data-link-type="biblio" href="#bib-schema-org" title="Schema.org">SCHEMA-ORG</a></cite>] version 3.4 is <a href="https://w3c.github.io/dxwg/dcat/rdf/dcat-schema.ttl">available in an RDF file</a>. This mapping is axiomatized using the predicates <code>rdfs:subClassOf</code>, <code>rdfs:subPropertyOf</code>, <code>owl:equivalentClass</code>, <code>owl:equivalentProperty</code>, <code>skos:closeMatch</code>, and also using the annotation properties <code>sdo:domainIncludes</code> and <code>sdo:rangeIncludes</code> to match [<cite><a class="bibref" data-link-type="biblio" href="#bib-schema-org" title="Schema.org">SCHEMA-ORG</a></cite>] semantics. The alignment is summarized in the table below, considering the prefix <code>sdo</code> as <code>http://schema.org/</code>. </p> <table class="simple" id="table-sdo-mapping"> <thead> <tr> <th>DCAT element</th> <th>Target element from schema.org</th> </tr> </thead> <tbody> <tr> <td><b>dcat:Resource</b></td> <td><b>sdo:Thing</b></td> </tr> <tr> <td>dcterms:title</td> <td>sdo:name</td> </tr> <tr> <td>dcterms:description</td> <td>sdo:description</td> </tr> <tr> <td>dcat:keyword <br> <em>dcat:keyword is singular, sdo:keywords is plural</em></td> <td>sdo:keywords</td> </tr> <tr> <td>dcat:theme</td> <td>sdo:about</td> </tr> <tr> <td>dcterms:identifier</td> <td>sdo:identifier</td> </tr> <tr> <td>dcterms:type</td> <td>sdo:additionalType</td> </tr> <tr> <td>dcterms:issued</td> <td>sdo:datePublished</td> </tr> <tr> <td>dcterms:modified</td> <td>sdo:dateModified</td> </tr> <tr> <td>dcterms:language</td> <td>sdo:inLanguage</td> </tr> <tr> <td>dcterms:relation</td> <td>sdo:isRelatedTo</td> </tr> <tr> <td>dcat:landingPage</td> <td>sdo:url</td> </tr> <tr> <td>dcterms:publisher</td> <td>sdo:publisher</td> </tr> <tr> <td>dcat:contactPoint</td> <td>sdo:contactPoint</td> </tr> <tr> <td>dcat:version</td> <td>sdo:version</td> </tr> <tr> <td><b>dcat:Catalog</b></td> <td><b>sdo:DataCatalog</b></td> </tr> <tr> <td>dcterms:hasPart</td> <td>sdo:hasPart</td> </tr> <tr> <td>dcat:dataset</td> <td>sdo:dataset</td> </tr> <tr> <td>dcat:distribution</td> <td>sdo:distribution</td> </tr> <tr> <td><b>dcat:Dataset</b></td> <td><b>sdo:Dataset</b></td> </tr> <tr> <td><b>dcat:Dataset</b> <br> <i>dcterms:accrualPeriodicity fixed to <br> <http://purl.org/cld/freq/continuous></i></td> <td><b>sdo:DataFeed</b></td> </tr> <tr> <td>dcterms:spatial</td> <td>sdo:spatialCoverage</td> </tr> <tr> <td>dcterms:temporal</td> <td>sdo:temporalCoverage</td> </tr> <tr> <td>dcterms:accrualPeriodicity</td> <td>sdo:repeatFrequency</td> </tr> <tr> <td>prov:wasGeneratedBy</td> <td>[ owl:inverseOf sdo:result ]</td> </tr> <tr> <td>dcat:inSeries</td> <td>sdo:isPartOf</td> </tr> <tr> <td><b>dcat:DatasetSeries</b></td> <td><b>sdo:CreativeWorkSeries</b></td> </tr> <tr> <td><b>dcat:Distribution</b></td> <td><b>sdo:DataDownload</b></td> </tr> <tr> <td>dcterms:format</td> <td>sdo:encodingFormat</td> </tr> <tr> <td>dcat:mediaType</td> <td>sdo:encodingFormat</td> </tr> <tr> <td>dcat:byteSize</td> <td>sdo:contentSize</td> </tr> <tr> <td>dcat:accessURL</td> <td>sdo:contentUrl</td> </tr> <tr> <td>dcat:downloadURL</td> <td>sdo:contentUrl</td> </tr> <tr> <td>dcterms:license</td> <td>sdo:license</td> </tr> <tr> <td><b>dcat:DataService</b></td> <td><b>sdo:WebAPI</b></td> </tr> <tr> <td>dcat:endpointURL</td> <td>sdo:url</td> </tr> <tr> <td>dcat:endpointDescription</td> <td>sdo:documentation, sdo:hasOfferCatalog</td> </tr> <tr> <td>dcterms:type <br> <i>in context of a dcat:DataService</i></td> <td>sdo:serviceType</td> </tr> <tr> <td>dcat:servesDataset</td> <td>sdo:serviceOutput</td> </tr> <tr> <td><b>dcat:Relationship</b></td> <td><b>sdo:Role</b></td> </tr> </tbody> </table> </section> <section id="collection-of-examples" class="appendix informative"><div class="header-wrapper"><h2 id="c-examples"><bdi class="secno">C. </bdi>Examples</h2><a class="self-link" href="#collection-of-examples" aria-label="Permalink for Appendix C."></a></div><p><em>This section is non-normative.</em></p> <section id="examples-bag-of-files"><div class="header-wrapper"><h3 id="c-1-loosely-structured-catalog"><bdi class="secno">C.1 </bdi>Loosely structured catalog</h3><a class="self-link" href="#examples-bag-of-files" aria-label="Permalink for Appendix C.1"></a></div> <div class="note" role="note" id="issue-container-generatedID-105"><div role="heading" class="note-title marker" id="h-note-104" aria-level="4"><span>Note</span></div><aside class=""> <p> The background to this example is discussed in Issue <a href="https://github.com/w3c/dxwg/issues/253">#253</a> ("Best practice for a loosely-structured catalog"). </p> </aside></div> <p> In many legacy catalogs and repositories (e.g., CKAN), ‘datasets’ are ‘just a bag of files’. There is no distinction made between distribution (representation), and other kinds of relationship (e.g., documentation, schema, supporting documents) from the dataset to each of the files. </p> <p> If the nature of the relationships between a dataset and component resources in a catalog, repository, or elsewhere are not known, <code>dcterms:relation</code> or its sub-property <code>dcterms:hasPart</code> can be used: </p> <aside id="ex-dataset-as-bag-of-files" class="example"><div class="marker"> <a class="self-link" href="#ex-dataset-as-bag-of-files">Example<bdi> 55</bdi></a> </div> <pre class="nohighlight turtle">ex:d33937 dcterms:description "A set of RDF graphs representing the International [Chrono]stratigraphic Chart, ..."@en ; dcterms:identifier "https://doi.org/10.25919/5b4d2b83cbf2d"^^xsd:anyURI ; dcterms:creator <https://orcid.org/0000-0002-3884-3420> ; dcterms:relation ex:ChronostratChart2017-02.pdf ; dcterms:relation ex:ChronostratChart2017-02.jpg ; dcterms:hasPart ex:timescale.zip ; dcterms:hasPart ex:d33937-jsonld ; dcterms:hasPart ex:d33937-nt ; dcterms:hasPart ex:d33937-rdf ; dcterms:hasPart ex:d33937-ttl ; .</pre> </aside> <p> If the nature of the relationship is known, then other <a href="#Property:resource_relation">sub-properties of <code>dcterms:relation</code> should be used</a> to convey this. In particular, if it is clear that any of these related resources is a proper <i>representation</i> of the dataset, then <code>dcat:distribution</code> should be used. </p> <aside id="ex-when-using-distribution" class="example"><div class="marker"> <a class="self-link" href="#ex-when-using-distribution">Example<bdi> 56</bdi></a> </div> <pre class="nohighlight turtle">ex:d33937 rdf:type dcat:Dataset ; dcterms:description "A set of RDF graphs representing the International [Chrono]stratigraphic Chart, ..."@en ; dcterms:identifier "https://doi.org/10.25919/5b4d2b83cbf2d"^^xsd:anyURI ; dcterms:hasFormat ex:ChronostratChart2017-02.pdf ; dcterms:hasFormat ex:ChronostratChart2017-02.jpg ; dcat:distribution ex:timescale.zip ; dcat:distribution ex:d33937-jsonld ; dcat:distribution ex:d33937-nt ; dcat:distribution ex:d33937-rdf ; dcat:distribution ex:d33937-ttl ; . ex:d33937-jsonld rdf:type dcat:Distribution ; dcat:downloadURL ex:isc2017.jsonld ; dcat:byteSize "698039"^^xsd:nonNegativeInteger ; dcat:mediaType <http://www.iana.org/assignments/media-types/application/ld+json> ; . ex:d33937-nt rdf:type dcat:Distribution ; dcat:downloadURL ex:isc2017.nt ; dcat:byteSize "2047874"^^xsd:nonNegativeInteger ; dcat:mediaType <http://www.iana.org/assignments/media-types/application/n-triples> ; . ex:d33937-rdf rdf:type dcat:Distribution ; dcat:downloadURL ex:isc2017.rdf ; dcat:byteSize "1600569"^^xsd:nonNegativeInteger ; dcat:mediaType <http://www.iana.org/assignments/media-types/application/rdf+xml> ; . ex:d33937-ttl rdf:type dcat:Distribution ; dcat:downloadURL ex:isc2017.ttl ; dcat:byteSize "531703"^^xsd:nonNegativeInteger ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/turtle> ; .</pre> </aside> <p> This example is available from the <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/examples/vocab-dcat-3">DXWG DCAT 3 code repository</a> at <a href="https://w3c.github.io/dxwg/dcat/examples/vocab-dcat-3/csiro-dap-examples.ttl"><code>csiro-dap-examples.ttl</code></a> and <a href="https://w3c.github.io/dxwg/dcat/examples/vocab-dcat-3/csiro-stratchart_dcat3.ttl"><code>csiro-stratchart_dcat3.ttl</code></a>. </p> <p> Additional detail about the nature of the related resources can be given using suitable elements from other RDF vocabularies, along with dataset descriptors from DCAT. For example, the example above might be more fully expressed as follows (embedded comments explain the different resources in the graph): </p> <aside id="ex-elaborated-bag" class="example"><div class="marker"> <a class="self-link" href="#ex-elaborated-bag">Example<bdi> 57</bdi></a> </div> <pre class="nohighlight turtle">dap:d33937 rdf:type dcat:Dataset ; dcterms:title "The data"@en ; dcterms:conformsTo <http://resource.geosciml.org/ontology/timescale/gts> ; dcterms:description "A set of RDF graphs representing the International [Chrono]stratigraphic Chart [...]"@en ; dcterms:identifier "https://doi.org/10.25919/5b4d2b83cbf2d" ; dcterms:issued "2018-07-07"^^xsd:date ; dcterms:license <https://creativecommons.org/licenses/by/4.0/> ; dcterms:publisher <http://www.csiro.au> ; dcterms:hasPart <http://stratigraphy.org/ICSchart/ChronostratChart2017-02.jpg> ; dcterms:hasPart <http://stratigraphy.org/ICSchart/ChronostratChart2017-02.pdf> ; dcterms:hasPart [ rdf:type dcat:Dataset ; dcterms:conformsTo <https://www.w3.org/TR/owl2-overview/> ; dcterms:title "The ontology used for the data"@en ; dcterms:description "This is an RDF/OWL representation of the GeoSciML Geologic Timescale model ..."@en ; dcterms:issued "2011-01-01"^^xsd:date ; dcterms:modified "2017-04-28"^^xsd:date ; dcterms:title "Geologic Timescale model" ; dcterms:type <http://purl.org/adms/assettype/DomainModel> ; dcat:distribution [ rdf:type dcat:Distribution ; dcterms:title "RDF/XML representation of the ontology used for the data"@en ; dcat:downloadURL <http://resource.geosciml.org/ontology/timescale/gts.rdf> ; dcat:mediaType <http://www.iana.org/assignments/media-types/application/rdf+xml> ; ] ; dcat:distribution [ rdf:type dcat:Distribution ; dcterms:title "TTL representation of the ontology used for the data"@en ; dcat:downloadURL <http://resource.geosciml.org/ontology/timescale/gts.ttl> ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/turtle> ; ] ; dcat:distribution [ rdf:type dcat:Distribution ; dcterms:title "Webpage describing the ontology used for the data"@en ; dcat:downloadURL <http://resource.geosciml.org/ontology/timescale/gts.html> ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/html> ; ] ; dcat:landingPage <http://resource.geosciml.org/ontology/timescale/gts> ; ] ; dcat:distribution [ rdf:type dcat:Distribution ; dcterms:conformsTo <https://www.w3.org/TR/rdf-schema/> ; dcterms:title "RDF representation of the data"@en ; dcat:accessService [ rdf:type dcat:DataService ; dcterms:conformsTo <https://www.w3.org/TR/sparql11-protocol/> ; dcterms:title "International Chronostratigraphic Chart hosted at Research Vocabularies Australia"@en ; dcterms:description "Service that supports queries to obtain RDF representations of subsets of the data"@en ; dcat:endpointURL <http://vocabs.ands.org.au/repository/api/sparql/csiro_international-chronostratigraphic-chart_2017> ; dcat:landingPage <https://vocabs.ands.org.au/viewById/196> ; ] ; ] ; dcat:distribution [ rdf:type dcat:Distribution ; dcterms:identifier "isc2017.jsonld" ; dcterms:title "JSON-LD serialization of the RDF representation of the entire dataset"@en ; dcat:mediaType <http://www.iana.org/assignments/media-types/application/ld+json> ; ] ; dcat:distribution [ rdf:type dcat:Distribution ; dcterms:identifier "isc2017.nt" ; dcterms:title "N-Triples serialization of the RDF representation of the entire dataset"@en ; dcat:mediaType <http://www.iana.org/assignments/media-types/application/n-triples> ; ] ; dcat:distribution [ rdf:type dcat:Distribution ; dcterms:identifier "isc2017.rdf" ; dcterms:title "RDF/XML serialization of the RDF representation of the entire dataset"@en ; dcat:mediaType <http://www.iana.org/assignments/media-types/application/rdf+xml> ; ] ; dcat:distribution [ rdf:type dcat:Distribution ; dcterms:identifier "isc2017.ttl" ; dcterms:title "TTL serialization of the RDF representation of the entire dataset"@en ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/turtle> ; ] ; dcat:landingPage <https://data.csiro.au/dap/landingpage?pid=csiro:33937> ; . <http://stratigraphy.org/ICSchart/ChronostratChart2017-02.jpg> rdf:type foaf:Document ; dcterms:type <http://purl.org/dc/dcmitype/Image> ; dcterms:format <http://www.iana.org/assignments/media-types/img/jpeg> ; dcterms:description "Coloured image representation of the International Chronostratigraphic Chart"@en ; dcterms:issued "2017-02-01"^^xsd:date ; dcterms:title "International Chronostratigraphic Chart"@en ; . <http://stratigraphy.org/ICSchart/ChronostratChart2017-02.pdf> rdf:type foaf:Document ; dcterms:type <http://purl.org/dc/dcmitype/Image> ; dcterms:format <http://www.iana.org/assignments/media-types/application/pdf> ; dcterms:description "Coloured image representation of the International Chronostratigraphic Chart"@en ; dcterms:issued "2017-02-01"^^xsd:date ; dcterms:title "International Chronostratigraphic Chart"@en ; .</pre> </aside> <p> This example is available from the <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/examples/vocab-dcat-3">DXWG DCAT 3 code repository</a> at <a href="https://w3c.github.io/dxwg/dcat/examples/vocab-dcat-3/csiro-stratchart.ttl"><code>csiro-stratchart.ttl</code></a>. </p> </section> <section id="examples-dataset-provenance"><div class="header-wrapper"><h3 id="c-2-dataset-provenance"><bdi class="secno">C.2 </bdi>Dataset provenance</h3><a class="self-link" href="#examples-dataset-provenance" aria-label="Permalink for Appendix C.2"></a></div> <p> The provenance or business context of a dataset can be described using elements from the <abbr title="World Wide Web Consortium">W3C</abbr> Provenance Ontology [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>]. </p> <p> For example, a simple link from a dataset description to the project that generated the dataset can be formalized as follows (other details elided for clarity): </p> <aside id="ex-dataset-project" class="example"><div class="marker"> <a class="self-link" href="#ex-dataset-project">Example<bdi> 58</bdi></a> </div> <pre class="nohighlight turtle">dap:atnf-P366-2003SEPT rdf:type dcat:Dataset ; dcterms:bibliographicCitation "Burgay, M; McLaughlin, M; Kramer, M; Lyne, A; Joshi, B; Pearce, G; D'Amico, N; Possenti, A; Manchester, R; Camilo, F (2017): Parkes observations for project P366 semester 2003SEPT. v1. CSIRO. Data Collection. https://doi.org/10.4225/08/598dc08d07bb7" ; dcterms:title "Parkes observations for project P366 semester 2003SEPT"@en ; dcat:landingPage <https://data.csiro.au/dap/landingpage?pid=csiro:P366-2003SEPT> ; prov:wasGeneratedBy dap:P366 ; . dap:P366 rdf:type prov:Activity ; dcterms:type <http://dbpedia.org/resource/Observation> ; prov:startedAtTime "2000-11-01"^^xsd:date ; prov:used dap:Parkes-radio-telescope ; prov:wasInformedBy dap:ATNF ; rdfs:label "P366 - Parkes multibeam high-latitude pulsar survey"@en ; rdfs:seeAlso <https://doi.org/10.1111/j.1365-2966.2006.10100.x> ; .</pre> </aside> <p> This example is available from the <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/examples/vocab-dcat-3">DXWG DCAT 3 code repository</a> at <a href="https://w3c.github.io/dxwg/dcat/examples/vocab-dcat-3/csiro-dap-examples.ttl"><code>csiro-dap-examples.ttl</code></a>. </p> <p> Several properties capture provenance information, including within the citation and title, but the primary link to a formal description of the project is through <a href="#Property:dataset_was_generated_by"><code>prov:wasGeneratedBy</code></a>. A terse description of the project is shown as a <a href="https://www.w3.org/TR/prov-o/#Activity"><code>prov:Activity</code></a>, though this would not necessarily be part of the same catalog. Note that as the project is ongoing, the activity has no end date. </p> <p> Further provenance information might be provided using the other <i>starting point properties</i> from PROV, in particular <a href="https://www.w3.org/TR/prov-o/#wasAttributedTo"><code>prov:wasAttributedTo</code></a> (to link to an agent associated with the dataset production) and <a href="https://www.w3.org/TR/prov-o/#wasDerivedFrom"><code>prov:wasDerivedFrom</code></a> (to link to a predecessor dataset). Both of these complement Dublin Core properties already used in DCAT, as follows: </p> <ul> <li> <code>prov:wasAttributedTo</code> provides a general link to all kinds of associated agents, such as project sponsors, managers, dataset owners, etc., which are not correctly characterized using <code>dcterms:creator</code>, <code>dcterms:contributor</code> or <code>dcterms:publisher</code>. </li> <li> <code>prov:wasDerivedFrom</code> supports a more specific relationship to an input or predecessor dataset compared with <code>dcterms:source</code>, which is not necessarily a previous dataset. </li> </ul> <p> Further patterns for the use of <i>qualified properties</i> for resource attribution and interrelationships are described in <a href="#qualified-forms" class="sec-ref"><bdi class="secno">15. </bdi>Qualified relations</a>. </p> </section> <section id="examples-dataset-publication"><div class="header-wrapper"><h3 id="c-3-link-datasets-and-publications"><bdi class="secno">C.3 </bdi>Link datasets and publications</h3><a class="self-link" href="#examples-dataset-publication" aria-label="Permalink for Appendix C.3"></a></div> <p>Datasets are often associated with publications (scholarly articles, reports, etc.) and DCAT relies on the property <a href="#Property:resource_is_referenced_by"><code>dcterms:isReferencedBy</code></a> to provide a way to link publications about a dataset to the dataset</p> <p>The following example shows how a dataset published in the <a href="https://datadryad.org">Dryad repository</a> is linked to a publication available in the <a href="https://doi.org/10.1038/sdata.2018.22">Nature Scientific Data journal</a>:</p> <aside id="dataset-publication" class="example"><div class="marker"> <a class="self-link" href="#dataset-publication">Example<bdi> 59</bdi></a> </div> <pre class="nohighlight turtle">ex:globtherm dcterms:title "Data from: GlobTherm, a global database on thermal tolerances for aquatic and terrestrial organisms"@en ; dcterms:description "How climate affects species distributions is a longstanding question receiving renewed interest owing to the need to predict the impacts of global warming on biodiversity. Is climate change forcing species to live near their critical thermal limits? Are these limits likely to change through natural selection? These and other important questions can be addressed with models relating geographical distributions of species with climate data, but inferences made with these models are highly contingent on non-climatic factors such as biotic interactions. Improved understanding of climate change effects on species will require extensive analysis of thermal physiological traits, but such data are scarce and scattered. To overcome current limitations, we created the GlobTherm database. The database contains experimentally derived species’ thermal tolerance data currently comprising over 2,000 species of terrestrial, freshwater, intertidal and marine multicellular algae, plants, fungi, and animals. The GlobTherm database will be maintained and curated by iDiv with the aim of expanding it, and enable further investigations on the effects of climate on the distribution of life on Earth."@en ; dcterms:identifier "https://doi.org/10.5061/dryad.1cv08"^^xsd:anyURI ; dcterms:creator <https://orcid.org/0000-0002-7883-3577> ; dcterms:relation <https://doi.org/10.5061/dryad.1cv08/6> ; dcterms:relation <https://doi.org/10.5061/dryad.1cv08/7> ; dcterms:isReferencedBy <https://doi.org/10.1038/sdata.2018.22>.</pre> </aside> <p> This example is available from the <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/examples/vocab-dcat-3">DXWG DCAT 3 code repository</a> at <a href="https://w3c.github.io/dxwg/dcat/examples/vocab-dcat-3/dryad-globtherm-sdata.ttl"><code>dryad-globtherm-sdata.ttl</code></a> </p> </section> <section id="examples-data-service"><div class="header-wrapper"><h3 id="c-4-data-services"><bdi class="secno">C.4 </bdi>Data services</h3><a class="self-link" href="#examples-data-service" aria-label="Permalink for Appendix C.4"></a></div> <p> Data services may be described using DCAT. The values of the classifiers <code>dcterms:type</code>, <code>dcterms:conformsTo</code>, and <code>dcat:endpointDescription</code> provide progressively more detail about a service, whose actual endpoint is given by the <code>dcat:endpointURL</code>. </p> <p> The first example describes a data catalog hosted by the European Environment Agency (EEA). This is classified as a <a href="#Class:Data_Service"><code>dcat:DataService</code></a> and has the <code>dcterms:type</code> set to "<a href="http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/discovery">discovery</a>" from the INSPIRE classification of spatial data service types [<cite><a class="bibref" data-link-type="biblio" href="#bib-inspire-sdst" title="INSPIRE Registry: Spatial data service types">INSPIRE-SDST</a></cite>]. </p> <p> This example is available from the <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/examples/vocab-dcat-3">DXWG DCAT 3 code repository</a> at <a href="https://w3c.github.io/dxwg/dcat/examples/vocab-dcat-3/eea-csw.ttl"><code>eea-csw.ttl</code></a> </p> <aside id="ex-service-eea" class="example"><div class="marker"> <a class="self-link" href="#ex-service-eea">Example<bdi> 60</bdi></a> </div> <pre class="nohighlight turtle">ex:EEA-CSW-Endpoint rdf:type dcat:DataService ; dcterms:type <http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceCategory/infoCatalogueService> ; dcterms:accessRights <http://publications.europa.eu/resource/authority/access-right/PUBLIC> ; dcterms:conformsTo <http://www.opengis.net/def/serviceType/ogc/csw> ; dcterms:description "The EEA public catalogue of spatial datasets references the spatial datasets used by the European Environment Agency as well as the spatial datasets produced by or for the EEA. In the latter case, when datasets are publicly available, a link to the location from where they can be downloaded is included in the dataset's metadata. The catalogue has been initially populated with the most important spatial datasets already available on the data&maps section of the EEA website and is currently updated with any newly published spatial dataset."@en ; dcterms:identifier "eea-sdi-public-catalogue" ; dcterms:issued "2012-01-01"^^xsd:date ; dcterms:license <https://creativecommons.org/licenses/by/2.5/dk/> ; dcterms:spatial [ rdf:type dcterms:Location ; dcat:bbox "POLYGON((-180 90,180 90,180 -90,-180 -90,-180 90))"^^gsp:wktLiteral ; ] ; dcterms:title "European Environment Agency's public catalogue of spatial datasets."@en ; dcterms:type <http://inspire.ec.europa.eu/metadata-codelist/ResourceType/service> ; dcterms:type <http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/discovery> ; dcat:contactPoint ex:EEA ; dcat:endpointDescription <https://sdi.eea.europa.eu/catalogue/srv/eng/csw?service=CSW&request=GetCapabilities> ; dcat:endpointURL <http://sdi.eea.europa.eu/catalogue/srv/eng/csw> ; .</pre> </aside> <p> <a href="#ex-service-gsa" class="box-ref">Example<bdi> 61</bdi></a> shows a dataset hosted by Geoscience Australia, which is available from three distinct services, as indicated by the value of the <a href="#Property:data_service_serves_dataset"><code>dcat:servesDataset</code></a> property of each of the service descriptions. These are classified as a <a href="#Class:Data_Service"><code>dcat:DataService</code></a> and also have the <code>dcterms:type</code> set to "<a href="http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/download">download</a>" and "<a href="http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/view">view</a>" from the INSPIRE classification of spatial data service types [<cite><a class="bibref" data-link-type="biblio" href="#bib-inspire-sdst" title="INSPIRE Registry: Spatial data service types">INSPIRE-SDST</a></cite>]. </p> <p> <a href="#ex-service-gsa" class="box-ref">Example<bdi> 61</bdi></a> is available from the <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/examples/vocab-dcat-3">DXWG DCAT 3 code repository</a> at <a href="https://w3c.github.io/dxwg/dcat/examples/vocab-dcat-3/ga-courts.ttl"><code>ga-courts.ttl</code></a> </p> <aside id="ex-service-gsa" class="example"><div class="marker"> <a class="self-link" href="#ex-service-gsa">Example<bdi> 61</bdi></a> </div> <pre class="nohighlight turtle">ga-courts:jc rdf:type dcat:Dataset ; dcterms:description "The dataset contains spatial locations, in point format, of the Australian High Court, Australian Federal Courts and the Australian Magistrates Courts."@en ; dcterms:spatial [ rdf:type dcterms:Location ; dcat:bbox """<http://www.opengis.net/def/crs/EPSG/0/4283> POLYGON(( -42.885989 115.864566 , -12.460578 115.864566 , -12.460578 153.276835 , -42.885989 153.276835 , -42.885989 115.864566 ))"""^^geosparql:wktLiteral ; ] ; dcterms:title "Judicial Courts"@en ; dcterms:type <http://purl.org/dc/dcmitype/Dataset> ; dcat:landingPage <https://ecat.ga.gov.au/geonetwork/srv/eng/catalog.search#/metadata/cc365600-294a-597d-e044-00144fdd4fa6> ; . ga-courts:jc-esri rdf:type dcat:DataService ; dcterms:conformsTo <https://developers.arcgis.com/rest/> ; dcterms:description "This web service provides access to the National Judicial Courts dataset and presents the spatial locations of all the known Australian High Courts, Australian Federal Courts and the Australian Federal Circuit Courts located within Australia, all complemented with feature attribution."@en ; dcterms:identifier "2b8540c8-4a43-144d-e053-12a3070a3ff7" ; dcterms:title "National Judicial Courts MapServer"@en ; dcterms:type <http://purl.org/dc/dcmitype/Service> ; dcterms:type <https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/download> ; dcterms:type <https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/view> ; dcat:endpointURL <http://services.ga.gov.au/gis/rest/services/Judicial_Courts/MapServer> ; dcat:landingPage <https://ecat.ga.gov.au/geonetwork/srv/eng/catalog.search#/metadata/2b8540c8-4a43-144d-e053-12a3070a3ff7> ; dcat:servesDataset ga-courts:jc ; . ga-courts:jc-wfs rdf:type dcat:DataService ; dcterms:conformsTo <http://www.opengis.net/def/serviceType/ogc/wfs/2.0.0> ; dcterms:conformsTo <http://www.opengis.net/def/serviceType/ogc/wfs/1.1.0> ; dcterms:conformsTo <http://www.opengis.net/def/serviceType/ogc/wfs/1.0.0> ; dcterms:description "This web service provides access to the National Judicial Courts dataset and presents the spatial locations of all the known Australian High Courts, Australian Federal Courts and the Australian Federal Circuit Courts located within Australia, all complemented with feature attribution."@en ; dcterms:identifier "2b8540c8-4a42-144d-e053-12a3070a3ff7" ; dcterms:title "National Judicial Courts WFS"@en ; dcterms:type <http://purl.org/dc/dcmitype/Service> ; dcterms:type <https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/download> ; dcat:endpointDescription <http://services.ga.gov.au/gis/services/Judicial_Courts/MapServer/WFSServer?request=GetCapabilities&service=WFS> ; dcat:endpointURL <http://services.ga.gov.au/gis/services/Judicial_Courts/MapServer/WFSServer> ; dcat:landingPage <https://ecat.ga.gov.au/geonetwork/srv/eng/catalog.search#/metadata/2b8540c8-4a42-144d-e053-12a3070a3ff7> ; dcat:servesDataset ga-courts:jc ; . ga-courts:jc-wms rdf:type dcat:DataService ; dcterms:conformsTo <http://www.opengis.net/def/serviceType/ogc/wms/1.3> ; dcterms:description "This web service provides access to the National Judicial Courts dataset and presents the spatial locations of all the known Australian High Courts, Australian Federal Courts and the Australian Federal Circuit Courts located within Australia, all complemented with feature attribution."@en ; dcterms:identifier "2b8540c8-4a41-144d-e053-12a3070a3ff7" ; dcterms:title "National Judicial Courts WMS"@en ; dcterms:type <http://purl.org/dc/dcmitype/Service> ; dcterms:type <https://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/view> ; dcat:endpointDescription <http://services.ga.gov.au/gis/services/Judicial_Courts/MapServer/WMSServer?request=GetCapabilities&service=WMS> ; dcat:endpointURL <http://services.ga.gov.au/gis/services/Judicial_Courts/MapServer/WMSServer> ; dcat:landingPage <https://ecat.ga.gov.au/geonetwork/srv/eng/catalog.search#/metadata/2b8540c8-4a41-144d-e053-12a3070a3ff7> ; dcat:servesDataset ga-courts:jc ; .</pre> </aside> </section> <section id="examples-compressed-and-packaged-distributions"><div class="header-wrapper"><h3 id="c-5-compressed-and-packaged-distributions"><bdi class="secno">C.5 </bdi>Compressed and packaged distributions</h3><a class="self-link" href="#examples-compressed-and-packaged-distributions" aria-label="Permalink for Appendix C.5"></a></div> <p>The first example is for a distribution with a downloadable file that is compressed into a GZIP file. </p> <aside id="compressed-distribution" class="example"><div class="marker"> <a class="self-link" href="#compressed-distribution">Example<bdi> 62</bdi></a> </div> <pre class="nohighlight turtle">@prefix dcat: <http://www.w3.org/ns/dcat#> . @prefix dcterms: <http://purl.org/dc/terms/> . <https://data.gov.cz/zdroj/datová-sada/247025684/22> a dcat:Distribution ; dcat:downloadURL <https://mvcr1.opendata.cz/czechpoint/2007.csv.gz> ; dcterms:license <https://data.gov.cz/podmínky-užití/volný-přístup/> ; dcterms:conformsTo <https://mvcr1.opendata.cz/czechpoint/2007.json> ; dcterms:format <http://publications.europa.eu/resource/authority/file-type/CSV> ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/csv> ; dcat:compressFormat <http://www.iana.org/assignments/media-types/application/gzip> .</pre> </aside> <p>The second example is for a distribution with several files packed into a TAR file. </p> <aside id="packaged-distribution" class="example"><div class="marker"> <a class="self-link" href="#packaged-distribution">Example<bdi> 63</bdi></a> </div> <pre class="nohighlight turtle">@prefix dcat: <http://www.w3.org/ns/dcat#> . @prefix dcterms: <http://purl.org/dc/terms/> . <https://data.gov.cz/zdroj/datová-sada/247025684/22> a dcat:Distribution ; dcat:downloadURL <https://mvcr1.opendata.cz/czechpoint/data.tar> ; dcterms:license <https://data.gov.cz/podmínky-užití/volný-přístup/> ; dcterms:conformsTo <https://mvcr1.opendata.cz/czechpoint/2007.json> ; dcterms:format <http://publications.europa.eu/resource/authority/file-type/CSV> ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/csv> ; dcat:packageFormat <http://publications.europa.eu/resource/authority/file-type/TAR> .</pre> </aside> <p>The third example is for a distribution with several files packed into a TAR file which has been compressed into a GZIP file. </p> <aside id="packaged-and-compressed-distribution" class="example"><div class="marker"> <a class="self-link" href="#packaged-and-compressed-distribution">Example<bdi> 64</bdi></a> </div> <pre class="nohighlight turtle">@prefix dcat: <http://www.w3.org/ns/dcat#> . @prefix dcterms: <http://purl.org/dc/terms/> . <https://data.gov.cz/zdroj/datová-sada/247025684/22> a dcat:Distribution ; dcat:downloadURL <https://mvcr1.opendata.cz/czechpoint/data.tar.gz> ; dcterms:conformsTo <https://mvcr1.opendata.cz/czechpoint/2007.json> ; dcterms:license <https://data.gov.cz/podmínky-užití/volný-přístup/> ; dcterms:format <http://publications.europa.eu/resource/authority/file-type/CSV> ; dcat:mediaType <http://www.iana.org/assignments/media-types/text/csv> ; dcat:packageFormat <http://publications.europa.eu/resource/authority/file-type/TAR> ; dcat:compressFormat <http://www.iana.org/assignments/media-types/application/gzip> .</pre> </aside> <p> These examples are available from the <a href="https://github.com/w3c/dxwg/tree/gh-pages/dcat/examples/vocab-dcat-3">DXWG DCAT 3 code repository</a> at <a href="https://w3c.github.io/dxwg/dcat/examples/vocab-dcat-3/compress-and-package.ttl"><code>compress-and-package.ttl</code></a> </p> </section> </section> <section id="changes" class="appendix"><div class="header-wrapper"><h2 id="d-change-history"><bdi class="secno">D. </bdi>Change history</h2><a class="self-link" href="#changes" aria-label="Permalink for Appendix D."></a></div> <p>A full change-log is available on <a href="https://github.com/w3c/dxwg/commits/gh-pages/dcat">GitHub</a></p> </section> <section id="changes-since-20240118"><div class="header-wrapper"><h2 id="e-changes-since-the-candidate-recommendation-snapshot-18-january-2024"><bdi class="secno">E. </bdi>Changes since the Candidate Recommendation Snapshot 18 January 2024</h2><a class="self-link" href="#changes-since-20240118" aria-label="Permalink for Section E."></a></div> <p>The document has undergone the following changes since the Candidate Recommendation Snapshot 18 January 2024 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-3-20240118" title="Data Catalog Vocabulary (DCAT) - Version 3">VOCAB-DCAT-3-20240118</a></cite>]:</p> <ul> <li> <p>Editorial fixes as suggested in Issues <a href="https://github.com/w3c/dxwg/issues/1581">#1581</a>, <a href="https://github.com/w3c/dxwg/issues/1583">#1583</a>, <a href="https://github.com/w3c/dxwg/issues/1591">#1591</a>.</p> </li> <li><p>Fixed the wrong link to SPDX 2.2 - see Issue <a href="https://github.com/w3c/dxwg/issues/1592">#1592</a>.</p></li> <li><p>Removed the references at risk features in status section, as implementations for those features have been collected in the implementation report.</p> </li> </ul> </section> <section id="changes-since-20220510"><div class="header-wrapper"><h2 id="f-changes-since-the-fourth-public-working-draft-of-10-may-2022"><bdi class="secno">F. </bdi>Changes since the fourth public working draft of 10 May 2022</h2><a class="self-link" href="#changes-since-20220510" aria-label="Permalink for Section F."></a></div> <p>The document has undergone the following changes since the DCAT 3 fourth public working draft of 10 May 2022 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-3-20220510" title="Data Catalog Vocabulary (DCAT) - Version 3">VOCAB-DCAT-3-20220510</a></cite>]:</p> <ul> <li><p>The recommended range of properties <a href="#Property:dataset_spatial_resolution" class="sec-ref"><bdi class="secno">6.6.5 </bdi>Property: spatial resolution</a> and <a href="#Property:distribution_spatial_resolution" class="sec-ref"><bdi class="secno">6.8.13 </bdi>Property: spatial resolution</a> has been extended to include <a href="https://www.w3.org/TR/xmlschema11-2/#double"><code>xsd:double</code></a> in addition to <a href="https://www.w3.org/TR/xmlschema11-2/#decimal"><code>xsd:decimal</code></a> - see Issue <a href="https://github.com/w3c/dxwg/issues/1536">#1536</a>.</p> </li> <li> <p>Updated section <a href="#security_and_privacy" class="sec-ref"><bdi class="secno">17. </bdi>Security and Privacy Considerations</a> to include suggestions about integrity and authenticity - see Issue <a href="https://github.com/w3c/dxwg/issues/1526">#1526</a>.</p> </li> <li> <p>Updated usage note in <a href="#Property:resource_language" class="sec-ref"><bdi class="secno">6.4.9 </bdi>Property: language</a> to provide guidance on the use of <code>dcterms:language</code> in multilingual distributions - see Issue <a href="https://github.com/w3c/dxwg/issues/1532">#1532</a>.</p> </li> <li> <p>Added health warning related to BCP 47 - see Issue <a href="https://github.com/w3c/dxwg/issues/959">#959</a>.</p> </li> <li> <p>Updated <a href="#ex-versioning-with-dcat-and-owl" class="box-ref">Example<bdi> 36</bdi></a> (<a href="#versioning-complementary-approaches" class="sec-ref"><bdi class="secno">11.4 </bdi>Complementary approaches to versioning</a>) to illustrate how to use OWL and DCAT to version DCAT 3.</p> </li> <li> <p>Editorial and bug fixes throughout the document.</p> </li> </ul> </section> <section id="changes-since-20220111"><div class="header-wrapper"><h2 id="g-changes-since-the-third-public-working-draft-of-11-january-2022"><bdi class="secno">G. </bdi>Changes since the third public working draft of 11 January 2022</h2><a class="self-link" href="#changes-since-20220111" aria-label="Permalink for Section G."></a></div> <p>The document has undergone the following changes since the DCAT 3 third public working draft of 11 January 2022 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-3-20220111" title="Data Catalog Vocabulary (DCAT) - Version 3">VOCAB-DCAT-3-20220111</a></cite>]:</p> <ul> <li> <p>Editorial fix to the inconsistent use of "item" and "resource" throughout the document, by replacing "item" with "resource" when referring to an instance of <code>dcat:Resource</code> - see Issue <a href="https://github.com/w3c/dxwg/issues/1490">#1490</a>. This revision has affected the definitions and/or the usage notes of the following terms in section <a href="#Class:Resource" class="sec-ref"><bdi class="secno">6.4 </bdi>Class: Cataloged Resource</a>: <a href="#Property:resource_description" class="sec-ref"><bdi class="secno">6.4.5 </bdi>Property: description</a>, <a href="#Property:resource_title" class="sec-ref"><bdi class="secno">6.4.6 </bdi>Property: title</a>, <a href="#Property:resource_release_date" class="sec-ref"><bdi class="secno">6.4.7 </bdi>Property: release date</a>, <a href="#Property:resource_update_date" class="sec-ref"><bdi class="secno">6.4.8 </bdi>Property: update/modification date</a>, <a href="#Property:resource_language" class="sec-ref"><bdi class="secno">6.4.9 </bdi>Property: language</a>, <a href="#Property:resource_publisher" class="sec-ref"><bdi class="secno">6.4.10 </bdi>Property: publisher</a>, <a href="#Property:resource_identifier" class="sec-ref"><bdi class="secno">6.4.11 </bdi>Property: identifier</a>, <a href="#Property:resource_relation" class="sec-ref"><bdi class="secno">6.4.14 </bdi>Property: relation</a>. </p> </li> <li> <p>Added <a href="#ex-catalog-record-schema" class="box-ref">Example<bdi> 45</bdi></a> (<a href="#quality-conformance-statement" class="sec-ref"><bdi class="secno">14.2.1 </bdi>Conformance to a standard</a>) and introductory paragraph to show how to use property <code>dcterms:conformsTo</code> with a <code>dcat:CatalogRecord</code> - see Issue <a href="https://github.com/w3c/dxwg/issues/1489">#1489</a>.</p> </li> <li> <p>Added property <code>dcat:inCatalog</code> as the inverse of <a href="#Property:catalog_resource"><code>dcat:resource</code></a> in section <a href="#inverse-properties" class="sec-ref"><bdi class="secno">7. </bdi>Use of inverse properties</a> - see Issue <a href="https://github.com/w3c/dxwg/issues/1484">#1484</a>.</p> </li> <li> <p>Updated class diagram in <a href="#fig-dcat-all-attributes" class="fig-ref" title="Overview of DCAT model, showing the classes of resources that can be members of a Catalog, and the relationships between them. Except where specifically indicated, DCAT does not provide cardinality constraints.">Figure <bdi class="">1</bdi></a> to align it with the current version of the specification. In particular:</p><p> </p><ul> <li>Added newly defined properties - see Issue <a href="https://github.com/w3c/dxwg/issues/1469">#1469</a>.</li> <li>Removed inverse properties listed in section <a href="#inverse-properties" class="sec-ref"><bdi class="secno">7. </bdi>Use of inverse properties</a> - see Issues <a href="https://github.com/w3c/dxwg/issues/1410">#1410</a> and <a href="https://github.com/w3c/dxwg/issues/1413">#1413</a>.</li> <li>Removed cardinality restrictions not present in the RDF definition - see <a href="https://www.w3.org/2022/03/08-dxwgdcat-minutes#r03">resolution #3 of 8 March 2022</a>.</li> </ul> </li> <li> <p>Added property <code>dcat:seriesMember</code> as the inverse of <a href="#Property:dataset_in_series"><code>dcat:inSeries</code></a> in section <a href="#inverse-properties" class="sec-ref"><bdi class="secno">7. </bdi>Use of inverse properties</a> - see Issue <a href="https://github.com/w3c/dxwg/issues/1335">#1335</a>.</p> </li> <li> <p>Added <a href="#ex-dataset-series-and-versions" class="box-ref">Example<bdi> 39</bdi></a> (<a href="#dataset-series-specification" class="sec-ref"><bdi class="secno">12.1 </bdi>How to specify dataset series</a>) and introductory paragraph to show how to combine dataset series and dataset versions - see Issue <a href="https://github.com/w3c/dxwg/issues/1409">#1409</a>.</p> </li> <li> <p>Defined a new property <a href="#Property:catalog_resource"><code>dcat:resource</code></a> to link a <code>dcat:Catalog</code> to a <code>dcat:Resource</code>, thus replacing property <code>dcterms:hasPart</code> that in DCAT 2 was introduced for this purpose. As a consequence, properties <a href="#Property:catalog_dataset"><code>dcat:dataset</code></a>, <a href="#Property:catalog_service"><code>dcat:service</code></a>, and <a href="#Property:catalog_catalog"><code>dcat:catalog</code></a> have been revised to be sub-properties of <code>dcat:resource</code> - see Issue <a href="https://github.com/w3c/dxwg/issues/1469">#1469</a>.</p> </li> <li> <p>Added property <a href="#Property:resource_has_part"><code>dcterms:hasPart</code></a> under <code>dcat:Resource</code> - see Issue <a href="https://github.com/w3c/dxwg/issues/1469">#1469</a>.</p> </li> <li> <p>Fixed inconsistent URIs in <a href="#ex-adms-identifier" class="box-ref">Example<bdi> 15</bdi></a> (<a href="#dereferenceable-identifiers" class="sec-ref"><bdi class="secno">8. </bdi>Dereferenceable identifiers</a>) - see Issue <a href="https://github.com/w3c/dxwg/issues/1459">#1459</a>.</p> </li> <li> <p>Aligned the definitions of the properties <a href="#Property:catalog_dataset"><code>dcat:dataset</code></a>, <a href="#Property:catalog_service"><code>dcat:service</code></a>, <a href="#Property:catalog_catalog"><code>dcat:catalog</code></a> - see Issue <a href="https://github.com/w3c/dxwg/issues/1465">#1465</a>.</p> </li> <li> <p>The definition of property <a href="#Property:resource_version"><code>dcat:version</code></a> has been revised to make it explicit that version indicators can be numeric or textual - see Issue <a href="https://github.com/w3c/dxwg/issues/1442">#1442</a>.</p> </li> <li> <p>Revised <a href="#compressed-distribution" class="box-ref">Example<bdi> 62</bdi></a>, <a href="#packaged-distribution" class="box-ref">Example<bdi> 63</bdi></a>, and <a href="#packaged-and-compressed-distribution" class="box-ref">Example<bdi> 64</bdi></a> (<a href="#examples-compressed-and-packaged-distributions" class="sec-ref"><bdi class="secno">C.5 </bdi>Compressed and packaged distributions</a>) to remove all occurrences of property <code>dcat:accessURL</code> when taking as value the same URL of <code>dcat:downloadURL</code> - see Issue <a href="https://github.com/w3c/dxwg/issues/1437">#1437</a>.</p> </li> <li> <p>Revised usage note of property <a href="#Property:distribution_packaging_format"><code>dcat:packageFormat</code></a> to include the ZIP format as one of the examples of packaging formats - see Issue <a href="https://github.com/w3c/dxwg/issues/1438">#1438</a>.</p> </li> <li> <p>Editorial fixes to <a href="#dcat-scope" class="sec-ref"><bdi class="secno">5.1 </bdi>DCAT scope</a> - see Issue <a href="https://github.com/w3c/dxwg/issues/1440">#1440</a>.</p> </li> </ul> </section> <section id="changes-since-20210504"><div class="header-wrapper"><h2 id="h-changes-since-the-second-public-working-draft-of-4-may-2021"><bdi class="secno">H. </bdi>Changes since the second public working draft of 4 May 2021</h2><a class="self-link" href="#changes-since-20210504" aria-label="Permalink for Section H."></a></div> <p>The document has undergone the following changes since the DCAT 3 second public working draft of 4 May 2021 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-3-20210504" title="Data Catalog Vocabulary (DCAT) - Version 3">VOCAB-DCAT-3-20210504</a></cite>]:</p> <ul> <li><p> New section <a href="#inverse-properties" class="sec-ref"><bdi class="secno">7. </bdi>Use of inverse properties</a> has been added, and properties <code>dcat:isVersionOf</code>, <code>dcat:next</code>, and <code>dcterms:isReplacedBy</code> have been removed from <a href="#vocabulary-specification" class="sec-ref"><bdi class="secno">6. </bdi>Vocabulary specification</a> - see Issue <a href="https://github.com/w3c/dxwg/issues/1336">#1336</a>.</p></li> <li><p> New section <a href="#accessibility" class="sec-ref"><bdi class="secno">18. </bdi>Accessibility Considerations</a> has been added - see Issue <a href="https://github.com/w3c/dxwg/issues/1358">#1358</a>.</p> </li> <li><p> Revision of UML diagrams - see Issues <a href="https://github.com/w3c/dxwg/issues/1383">#1383</a>, <a href="https://github.com/w3c/dxwg/issues/1294">#1294</a>, <a href="https://github.com/w3c/dxwg/issues/1252">#1252</a>.</p> </li> <li><p> Revision of the usage note of <a href="#Class:Resource"><code title="http://www.w3.org/ns/dcat#Class:Resource">dcat:Resource</code></a> - see Issue <a href="https://github.com/w3c/dxwg/issues/1388">#1388</a>.</p> </li> <li><p> Clarified the scope of <a href="#Property:resource_identifier"><code title="http://purl.org/dc/terms/identifier">dcterms:identifier</code></a> - see Issue <a href="https://github.com/w3c/dxwg/issues/771">#771</a>.</p> </li> <li><p><a href="#basic-example" class="sec-ref"><bdi class="secno">5.3 </bdi>Basic example</a> has been updated to tell a more coherent story (see Issue <a href="https://github.com/w3c/dxwg/issues/1155">#1155</a>) and express temporal coverage by using <a href="#Class:Period_of_Time"><code>dcterms:PeriodOfTime</code></a>, <a href="#Property:period_start_date"><code>dcat:startDate</code></a>, and <a href="#Property:period_end_date"><code>dcat:endDate</code></a>.</p> </li> <li>The usage notes of properties <a href="#Property:location_bbox"><code title="http://www.w3.org/ns/dcat#bbox">dcat:bbox</code></a> and <a href="#Property:location_centroid"><code title="http://www.w3.org/ns/dcat#centroid">dcat:centroid</code></a> have been revised to make it clearer that they are supposed to be used only with geometry literals - see Issue <a href="https://github.com/w3c/dxwg/issues/1359">#1359</a>. </li> <li>The property <a href="#Property:resource_theme"><code title="http://www.w3.org/ns/dcat#theme">dcat:theme</code></a> have been explicitly defined as an OWL object property and its range is dropped; consistency of the usage note of <a href="#Property:resource_theme"><code title="http://www.w3.org/ns/dcat#themeTaxonomy">dcat:themeTaxonomy</code></a> has been improved - see Issues <a href="https://github.com/w3c/dxwg/issues/1364">#1364</a> and <a href="https://github.com/w3c/dxwg/issues/1153">#1153</a>. </li> </ul> </section> <section id="changes-since-20201217"><div class="header-wrapper"><h2 id="i-changes-since-the-first-public-working-draft-of-17-december-2020"><bdi class="secno">I. </bdi>Changes since the first public working draft of 17 December 2020</h2><a class="self-link" href="#changes-since-20201217" aria-label="Permalink for Section I."></a></div> <p>The document has undergone the following changes since the DCAT 3 first public working draft of 17 December 2020 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-3-20201217" title="Data Catalog Vocabulary (DCAT) - Version 3">VOCAB-DCAT-3-20201217</a></cite>]:</p> <ul> <li><p><a href="#basic-example" class="sec-ref"><bdi class="secno">5.3 </bdi>Basic example</a> has been extended to include titles, labels, and keywords in two different languages (English and Spanish) to illustrate the use of language tags.</p></li> </ul> <ul> <li><p>The recommended range of property <a href="#Property:distribution_size" class="sec-ref"><bdi class="secno">6.8.12 </bdi>Property: byte size</a> has been changed from <a href="https://www.w3.org/TR/xmlschema11-2/#decimal"><code>xsd:decimal</code></a> to <a href="https://www.w3.org/TR/xmlschema11-2/#nonNegativeInteger"><code>xsd:nonNegativeInteger</code></a> </p></li> </ul> <ul> <li><p><a href="#dataset-versions" class="sec-ref"><bdi class="secno">11. </bdi>Versioning</a> has been revised to focus specifically on versions derived from the revision of a resource, and by following the [<cite><a class="bibref" data-link-type="biblio" href="#bib-pav" title="PAV - Provenance, Authoring and Versioning. Version 2.3.1">PAV</a></cite>] approach for the specification of version chains and hierarchies - previous, next, current, last version. In particular:</p> <ul> <li>The introductory text has been revised according to the new scope.</li> <li>The section on <a href="https://www.w3.org/TR/2020/WD-vocab-dcat-3-20201217/#version-types">version types</a> (link to previous version) has been removed, and <a href="#version-relationships">a new section</a> has been added to describe how to specify relationships between versions.</li> <li>Dropped support to the specification of backward (in)compatibility between versions by using properties <code>owl:backwardCompatibleWith</code> and <code>owl:incompatibleWith</code>, originally included in <a href="#version-info" class="sec-ref"><bdi class="secno">11.2 </bdi>Version information</a>.</li> <li><a href="#versioning-complementary-approaches">A new section</a> has been added at the end to compare the DCAT versioning approach with those used in OWL, [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>], and [<cite><a class="bibref" data-link-type="biblio" href="#bib-prov-o" title="PROV-O: The PROV Ontology">PROV-O</a></cite>].</li> </ul> <p>The other sections include only editorial changes.</p> </li> <li><a href="#Class:Resource" class="sec-ref"><bdi class="secno">6.4 </bdi>Class: Cataloged Resource</a> has been updated to include the definition of the properties illustrated in <a href="#dataset-versions" class="sec-ref"><bdi class="secno">11. </bdi>Versioning</a>.</li> <li><p><a href="#dataset-series" class="sec-ref"><bdi class="secno">12. </bdi>Dataset series</a> has been revised making dataset series first class citizens of data catalogs and introducing new properties for linking dataset series and datasets. In particular:</p> <ul> <li>A new class <code>dcat:DatasetSeries</code> has been defined (see <a href="#Class:Dataset_Series" class="sec-ref"><bdi class="secno">6.7 </bdi>Class: Dataset Series</a>) - see Issue <a href="https://github.com/w3c/dxwg/issues/1272">#1272</a>.</li> <li>Property <a href="#Property:dataset_in_series"><code>dcat:inSeries</code></a> has been added to <a href="#Class:Dataset" class="sec-ref"><bdi class="secno">6.6 </bdi>Class: Dataset</a> - see Issue <a href="https://github.com/w3c/dxwg/issues/1307">#1307</a>.</li> <li>Properties <a href="#Property:resource_first"><code>dcat:first</code></a>, <a href="#Property:resource_previous"><code>dcat:prev</code></a>, <code>dcat:next</code>, and <a href="#Property:resource_last"><code>dcat:last</code></a> have been added to <a href="#Class:Resource" class="sec-ref"><bdi class="secno">6.4 </bdi>Class: Cataloged Resource</a> - see Issue <a href="https://github.com/w3c/dxwg/issues/1308">#1308</a>.</li> </ul> </li> <li>Added property <a href="#Property:distribution_checksum"><code>spdx:checksum</code></a> to <a href="#Class:Distribution" class="sec-ref"><bdi class="secno">6.8 </bdi>Class: Distribution</a>; added class <code>spdx:Checksum</code> (see <a href="#Class:Checksum" class="sec-ref"><bdi class="secno">6.17 </bdi>Class: Checksum</a>), and its properties <a href="#Property:checksum_algorithm"><code>spdx:algorithm</code></a> and <a href="#Property:checksum_checksum_value"><code>spdx:checksumValue</code></a> - see Issue <a href="https://github.com/w3c/dxwg/issues/1287">#1287</a>.</li> <li>Revised range of property <a href="#Property:location_geometry"><code title="http://www.w3.org/ns/locn#geometry">locn:geometry</code></a>, to align it with its definition in [<cite><a class="bibref" data-link-type="biblio" href="#bib-locn" title="ISA Programme Location Core Vocabulary">LOCN</a></cite>]. The usage note of this property has been also revised to make it clear that it can be used with either geometry literals or classes - see Issue <a href="https://github.com/w3c/dxwg/issues/1293">#1293</a>.</li> <li>Added examples to <a href="#license-rights" class="sec-ref"><bdi class="secno">9. </bdi>License and rights statements</a> - see Issues <a href="https://github.com/w3c/dxwg/issues/676">#676</a> and <a href="https://github.com/w3c/dxwg/issues/1333">#1333</a>.</li> <li>Replaced [<cite><a class="bibref" data-link-type="biblio" href="#bib-dcterms" title="DCMI Metadata Terms">DCTERMS</a></cite>] namespace prefix <code>dct:</code> with <code>dcterms:</code> throughout the document - see Issue <a href="https://github.com/w3c/dxwg/issues/1314">#1314</a>.</li> <li>Fixed inconsistent use of "URI" and "<abbr title="Internationalized Resource Identifier">IRI</abbr>" throughout the document - see Issue <a href="https://github.com/w3c/dxwg/issues/1341">#1341</a>.</li> <li>Removed NOTE in <a href="#ex-spatial-coverage-centroid" class="box-ref">Example<bdi> 31</bdi></a> showing an example of the use of [<cite><a class="bibref" data-link-type="biblio" href="#bib-w3c-basic-geo" title="Basic Geo (WGS84 lat/long) Vocabulary">W3C-BASIC-GEO</a></cite>] for the specification of point geometries - see Issue <a href="https://github.com/w3c/dxwg/issues/1347">#1347</a>.</li> <li>Revised textual descriptions of classes and properties to clarify that the resources in a catalog are not limited to datasets and data services - see Issue <a href="https://github.com/w3c/dxwg/issues/1349">#1349</a>.</li> <li>Fixed inconsistent use of property labels - see Issue <a href="https://github.com/w3c/dxwg/issues/1350">#1350</a>.</li> <li>Updated definition for <code>dcat:catalog</code> - see Issue <a href="https://github.com/w3c/dxwg/issues/1156">#1156</a>.</li> </ul> </section> <section id="changes-since-20200204"><div class="header-wrapper"><h2 id="j-changes-since-the-w3c-recommendation-of-4-february-2020"><bdi class="secno">J. </bdi>Changes since the <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation of 4 February 2020</h2><a class="self-link" href="#changes-since-20200204" aria-label="Permalink for Section J."></a></div> <p>The document has undergone the following changes since the DCAT 2 <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation of 4 February 2020 [<cite><a class="bibref" data-link-type="biblio" href="#bib-vocab-dcat-2-20200204" title="Data Catalog Vocabulary (DCAT) - Version 2">VOCAB-DCAT-2-20200204</a></cite>]:</p> <ul> <li> Examples about <a href="#examples-bag-of-files">loosely structured catalog</a> were updated replacing <code>dcterms:relation</code> with more specific subrelations and emphasizing the use of <code>dcterms:hasPart</code>. </li> <li> Section <a href="#dataset-versions" class="sec-ref"><bdi class="secno">11. </bdi>Versioning</a> was extended with draft guidelines to deal with version delta (Issue <a href="https://github.com/w3c/dxwg/issues/89">#89</a>), version release date (Issue <a href="https://github.com/w3c/dxwg/issues/91">#91</a>), version identifier (Issue <a href="https://github.com/w3c/dxwg/issues/92">#92</a>), version compatibility (Issue <a href="https://github.com/w3c/dxwg/issues/1258">#1258</a>) and resource status (Issue <a href="https://github.com/w3c/dxwg/issues/1238">#1238</a>). </li> <li> A new section <a href="#dataset-series" class="sec-ref"><bdi class="secno">12. </bdi>Dataset series</a> was added to draft guidelines on dataset series (Issue <a href="https://github.com/w3c/dxwg/issues/868">#868</a>) and to show related examples (Issue <a href="https://github.com/w3c/dxwg/issues/806">#806</a>). </li> </ul> </section> <section id="references" class="appendix"><div class="header-wrapper"><h2 id="k-references"><bdi class="secno">K. </bdi>References</h2><a class="self-link" href="#references" aria-label="Permalink for Appendix K."></a></div><section id="normative-references"><div class="header-wrapper"><h3 id="k-1-normative-references"><bdi class="secno">K.1 </bdi>Normative references</h3><a class="self-link" href="#normative-references" aria-label="Permalink for Appendix K.1"></a></div> <dl class="bibliography"><dt id="bib-dc11">[DC11]</dt><dd> <a href="http://dublincore.org/documents/dces/"><cite>Dublin Core Metadata Element Set, Version 1.1</cite></a>. DCMI. 14 June 2012. DCMI Recommendation. URL: <a href="http://dublincore.org/documents/dces/">http://dublincore.org/documents/dces/</a> </dd><dt id="bib-dcterms">[DCTERMS]</dt><dd> <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/"><cite>DCMI Metadata Terms</cite></a>. DCMI Usage Board. DCMI. 20 January 2020. DCMI Recommendation. URL: <a href="https://www.dublincore.org/specifications/dublin-core/dcmi-terms/">https://www.dublincore.org/specifications/dublin-core/dcmi-terms/</a> </dd><dt id="bib-dwbp">[DWBP]</dt><dd> <a href="https://www.w3.org/TR/dwbp/"><cite>Data on the Web Best Practices</cite></a>. Bernadette Farias Loscio; Caroline Burle; Newton Calegari. W3C. 31 January 2017. W3C Recommendation. URL: <a href="https://www.w3.org/TR/dwbp/">https://www.w3.org/TR/dwbp/</a> </dd><dt id="bib-foaf">[FOAF]</dt><dd> <a href="http://xmlns.com/foaf/spec"><cite>FOAF Vocabulary Specification 0.99 (Paddington Edition)</cite></a>. Dan Brickley; Libby Miller. FOAF project. 14 January 2014. URL: <a href="http://xmlns.com/foaf/spec">http://xmlns.com/foaf/spec</a> </dd><dt id="bib-geosparql">[GeoSPARQL]</dt><dd> <a href="https://docs.ogc.org/is/22-047r1/22-047r1.html"><cite>OGC GeoSPARQL - A Geographic Query Language for RDF Data</cite></a>. Nicholas J. Car; Timo Homburg; Matthew Perry; Frans Knibbe; Simon J.D. Cox; Joseph Abhayaratna; Mathias Bonduel; Paul J. Cripps; Krzysztof Janowicz. OGC. 29 January 2024. OGC Standard. URL: <a href="https://docs.ogc.org/is/22-047r1/22-047r1.html">https://docs.ogc.org/is/22-047r1/22-047r1.html</a> </dd><dt id="bib-iana-media-types">[IANA-MEDIA-TYPES]</dt><dd> <a href="https://www.iana.org/assignments/media-types/"><cite>Media Types</cite></a>. IANA. URL: <a href="https://www.iana.org/assignments/media-types/">https://www.iana.org/assignments/media-types/</a> </dd><dt id="bib-locn">[LOCN]</dt><dd> <a href="https://www.w3.org/ns/locn"><cite>ISA Programme Location Core Vocabulary</cite></a>. Andrea Perego; Michael Lutz. European Commission. 23 March 2015. Second version in w3.org/ns space. URL: <a href="https://www.w3.org/ns/locn">http://www.w3.org/ns/locn</a> </dd><dt id="bib-odrl-model">[ODRL-MODEL]</dt><dd> <a href="https://www.w3.org/TR/odrl-model/"><cite>ODRL Information Model 2.2</cite></a>. Renato Iannella; Serena Villata. W3C. 15 February 2018. W3C Recommendation. URL: <a href="https://www.w3.org/TR/odrl-model/">https://www.w3.org/TR/odrl-model/</a> </dd><dt id="bib-odrl-vocab">[ODRL-VOCAB]</dt><dd> <a href="https://www.w3.org/TR/odrl-vocab/"><cite>ODRL Vocabulary & Expression 2.2</cite></a>. Renato Iannella; Michael Steidl; Stuart Myles; Víctor Rodríguez-Doncel. W3C. 15 February 2018. W3C Recommendation. URL: <a href="https://www.w3.org/TR/odrl-vocab/">https://www.w3.org/TR/odrl-vocab/</a> </dd><dt id="bib-owl-time">[OWL-TIME]</dt><dd> <a href="https://www.w3.org/TR/owl-time/"><cite>Time Ontology in OWL</cite></a>. Simon Cox; Chris Little. W3C. 15 November 2022. W3C Candidate Recommendation. URL: <a href="https://www.w3.org/TR/owl-time/">https://www.w3.org/TR/owl-time/</a> </dd><dt id="bib-owl2-overview">[OWL2-OVERVIEW]</dt><dd> <a href="https://www.w3.org/TR/owl2-overview/"><cite>OWL 2 Web Ontology Language Document Overview (Second Edition)</cite></a>. W3C OWL Working Group. W3C. 11 December 2012. W3C Recommendation. URL: <a href="https://www.w3.org/TR/owl2-overview/">https://www.w3.org/TR/owl2-overview/</a> </dd><dt id="bib-owl2-syntax">[OWL2-SYNTAX]</dt><dd> <a href="https://www.w3.org/TR/owl2-syntax/"><cite>OWL 2 Web Ontology Language Structural Specification and Functional-Style Syntax (Second Edition)</cite></a>. Boris Motik; Peter Patel-Schneider; Bijan Parsia. W3C. 11 December 2012. W3C Recommendation. URL: <a href="https://www.w3.org/TR/owl2-syntax/">https://www.w3.org/TR/owl2-syntax/</a> </dd><dt id="bib-pav">[PAV]</dt><dd> <a href="https://pav-ontology.github.io/pav/"><cite>PAV - Provenance, Authoring and Versioning. Version 2.3.1</cite></a>. Paolo Ciccarese; Stian Soiland-Reyes. Mind Informatics. 16 March 2015. URL: <a href="https://pav-ontology.github.io/pav/">https://pav-ontology.github.io/pav/</a> </dd><dt id="bib-prov-o">[PROV-O]</dt><dd> <a href="https://www.w3.org/TR/prov-o/"><cite>PROV-O: The PROV Ontology</cite></a>. Timothy Lebo; Satya Sahoo; Deborah McGuinness. W3C. 30 April 2013. W3C Recommendation. URL: <a href="https://www.w3.org/TR/prov-o/">https://www.w3.org/TR/prov-o/</a> </dd><dt id="bib-rdf-schema">[RDF-SCHEMA]</dt><dd> <a href="https://www.w3.org/TR/rdf-schema/"><cite>RDF Schema 1.1</cite></a>. Dan Brickley; Ramanathan Guha. W3C. 25 February 2014. W3C Recommendation. URL: <a href="https://www.w3.org/TR/rdf-schema/">https://www.w3.org/TR/rdf-schema/</a> </dd><dt id="bib-rdf-syntax-grammar">[RDF-SYNTAX-GRAMMAR]</dt><dd> <a href="https://www.w3.org/TR/rdf-syntax-grammar/"><cite>RDF 1.1 XML Syntax</cite></a>. Fabien Gandon; Guus Schreiber. W3C. 25 February 2014. W3C Recommendation. URL: <a href="https://www.w3.org/TR/rdf-syntax-grammar/">https://www.w3.org/TR/rdf-syntax-grammar/</a> </dd><dt id="bib-rfc2119">[RFC2119]</dt><dd> <a href="https://www.rfc-editor.org/rfc/rfc2119"><cite>Key words for use in RFCs to Indicate Requirement Levels</cite></a>. S. Bradner. IETF. March 1997. Best Current Practice. URL: <a href="https://www.rfc-editor.org/rfc/rfc2119">https://www.rfc-editor.org/rfc/rfc2119</a> </dd><dt id="bib-rfc8174">[RFC8174]</dt><dd> <a href="https://www.rfc-editor.org/rfc/rfc8174"><cite>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</cite></a>. B. Leiba. IETF. May 2017. Best Current Practice. URL: <a href="https://www.rfc-editor.org/rfc/rfc8174">https://www.rfc-editor.org/rfc/rfc8174</a> </dd><dt id="bib-skos-reference">[SKOS-REFERENCE]</dt><dd> <a href="https://www.w3.org/TR/skos-reference/"><cite>SKOS Simple Knowledge Organization System Reference</cite></a>. Alistair Miles; Sean Bechhofer. W3C. 18 August 2009. W3C Recommendation. URL: <a href="https://www.w3.org/TR/skos-reference/">https://www.w3.org/TR/skos-reference/</a> </dd><dt id="bib-spdx">[SPDX]</dt><dd> <a href="https://spdx.org/rdf/spdx-terms-v2.2/"><cite>SPDX 2.2</cite></a>. SPDX. URL: <a href="https://spdx.org/rdf/spdx-terms-v2.2/">https://spdx.org/rdf/spdx-terms-v2.2/</a> </dd><dt id="bib-understanding-wcag20">[UNDERSTANDING-WCAG20]</dt><dd> <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/"><cite>Understanding WCAG 2.0</cite></a>. Michael Cooper; Andrew Kirkpatrick; Joshue O'Connor et al. W3C. 21 September 2023. W3C Working Group Note. URL: <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/">https://www.w3.org/TR/UNDERSTANDING-WCAG20/</a> </dd><dt id="bib-vcard-rdf">[VCARD-RDF]</dt><dd> <a href="https://www.w3.org/TR/vcard-rdf/"><cite>vCard Ontology - for describing People and Organizations</cite></a>. Renato Iannella; James McKinney. W3C. 22 May 2014. W3C Working Group Note. URL: <a href="https://www.w3.org/TR/vcard-rdf/">https://www.w3.org/TR/vcard-rdf/</a> </dd><dt id="bib-vocab-adms">[VOCAB-ADMS]</dt><dd> <a href="https://www.w3.org/TR/vocab-adms/"><cite>Asset Description Metadata Schema (ADMS)</cite></a>. Phil Archer; Gofran Shukair. W3C. 1 August 2013. W3C Working Group Note. URL: <a href="https://www.w3.org/TR/vocab-adms/">https://www.w3.org/TR/vocab-adms/</a> </dd><dt id="bib-vocab-dcat">[VOCAB-DCAT]</dt><dd> <a href="https://www.w3.org/TR/vocab-dcat/"><cite>Data Catalog Vocabulary (DCAT)</cite></a>. Fadi Maali; John Erickson. W3C. 4 February 2020. W3C Recommendation. URL: <a href="https://www.w3.org/TR/vocab-dcat/">https://www.w3.org/TR/vocab-dcat/</a> </dd><dt id="bib-xmlschema11-2">[XMLSCHEMA11-2]</dt><dd> <a href="https://www.w3.org/TR/xmlschema11-2/"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes</cite></a>. David Peterson; Sandy Gao; Ashok Malhotra; Michael Sperberg-McQueen; Henry Thompson; Paul V. Biron et al. W3C. 5 April 2012. W3C Recommendation. URL: <a href="https://www.w3.org/TR/xmlschema11-2/">https://www.w3.org/TR/xmlschema11-2/</a> </dd></dl> </section><section id="informative-references"><div class="header-wrapper"><h3 id="k-2-informative-references"><bdi class="secno">K.2 </bdi>Informative references</h3><a class="self-link" href="#informative-references" aria-label="Permalink for Appendix K.2"></a></div> <dl class="bibliography"><dt id="bib-adms-skos">[ADMS-SKOS]</dt><dd> <a href="https://web.archive.org/web/20210521035614/https://joinup.ec.europa.eu/svn/adms/ADMS_v1.00/ADMS_SKOS_v1.00.html"><cite>Joinup. ADMS Controlled Vocabularies</cite></a>. European Commission. URL: <a href="https://web.archive.org/web/20210521035614/https://joinup.ec.europa.eu/svn/adms/ADMS_v1.00/ADMS_SKOS_v1.00.html">https://web.archive.org/web/20210521035614/https://joinup.ec.europa.eu/svn/adms/ADMS_v1.00/ADMS_SKOS_v1.00.html</a> </dd><dt id="bib-annotation-vocab">[ANNOTATION-VOCAB]</dt><dd> <a href="https://www.w3.org/TR/annotation-vocab/"><cite>Web Annotation Vocabulary</cite></a>. Robert Sanderson; Paolo Ciccarese; Benjamin Young. W3C. 23 February 2017. W3C Recommendation. URL: <a href="https://www.w3.org/TR/annotation-vocab/">https://www.w3.org/TR/annotation-vocab/</a> </dd><dt id="bib-bcp47">[BCP47]</dt><dd> <a href="https://www.rfc-editor.org/rfc/rfc5646"><cite>Tags for Identifying Languages</cite></a>. A. Phillips, Ed.; M. Davis, Ed.. IETF. September 2009. Best Current Practice. URL: <a href="https://www.rfc-editor.org/rfc/rfc5646">https://www.rfc-editor.org/rfc/rfc5646</a> </dd><dt id="bib-csw">[CSW]</dt><dd> <a href="http://www.opengeospatial.org/standards/cat"><cite>Catalogue Services 3.0 - General Model</cite></a>. Douglas Nebert; Uwe Voges; Lorenzo Bigagli. OGC. 10 June 2016. URL: <a href="http://www.opengeospatial.org/standards/cat">http://www.opengeospatial.org/standards/cat</a> </dd><dt id="bib-datacite">[DataCite]</dt><dd> <a href="https://schema.datacite.org/"><cite>DataCite Metadata Schema</cite></a>. DataCite Metadata Working Group. DataCite e.V. 22 January 2024. URL: <a href="https://schema.datacite.org/">https://schema.datacite.org/</a> </dd><dt id="bib-datetime">[DATETIME]</dt><dd> <a href="https://www.w3.org/TR/NOTE-datetime"><cite>Date and Time Formats</cite></a>. W3C. 27 August 1998. W3C Working Group Note. URL: <a href="https://www.w3.org/TR/NOTE-datetime">https://www.w3.org/TR/NOTE-datetime</a> </dd><dt id="bib-dats">[DATS]</dt><dd> <a href="https://datatagsuite.github.io/docs/html/"><cite>Data Tag Suite</cite></a>. Alejandra Gonzalez-Beltran; Philippe Rocca-Serra. NIH Big Data 2 Knowledge bioCADDIE and NIH Data Commons projects. 2016. URL: <a href="https://datatagsuite.github.io/docs/html/">https://datatagsuite.github.io/docs/html/</a> </dd><dt id="bib-dbpedia-ont">[DBPEDIA-ONT]</dt><dd> <a href="http://dbpedia.org/ontology/"><cite>DBPedia ontology</cite></a>. URL: <a href="http://dbpedia.org/ontology/">http://dbpedia.org/ontology/</a> </dd><dt id="bib-dcap">[DCAP]</dt><dd> <a href="http://dublincore.org/documents/profile-guidelines/"><cite>Guidelines for Dublin Core Application Profiles</cite></a>. Karen Coyle; Thomas Baker. DCMI. 18 May 2009. DCMI Recommended Resource. URL: <a href="http://dublincore.org/documents/profile-guidelines/">http://dublincore.org/documents/profile-guidelines/</a> </dd><dt id="bib-dcat-ap">[DCAT-AP]</dt><dd> <a href="https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe"><cite>DCAT Application Profile for data portals in Europe. Version 2.0.1</cite></a>. European Commission. 8 June 2020. URL: <a href="https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe">https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe</a> </dd><dt id="bib-dcat-ap-it">[DCAT-AP-IT]</dt><dd> <a href="https://docs.italia.it/italia/daf/linee-guida-cataloghi-dati-dcat-ap-it/it/stabile/dcat-ap_it.html"><cite>Profilo metadatazione DCAT-AP_IT</cite></a>. AgID & Team Digitale. URL: <a href="https://docs.italia.it/italia/daf/linee-guida-cataloghi-dati-dcat-ap-it/it/stabile/dcat-ap_it.html">https://docs.italia.it/italia/daf/linee-guida-cataloghi-dati-dcat-ap-it/it/stabile/dcat-ap_it.html</a> </dd><dt id="bib-dcat-ap-no">[DCAT-AP-NO]</dt><dd> <a href="https://data.norge.no/specification/dcat-ap-no/"><cite>Standard for beskrivelse av datasett, datatjenester og datakataloger (DCAT-AP-NO)</cite></a>. URL: <a href="https://data.norge.no/specification/dcat-ap-no/">https://data.norge.no/specification/dcat-ap-no/</a> </dd><dt id="bib-dcat-ap-se">[DCAT-AP-SE]</dt><dd> <a href="https://docs.dataportal.se/dcat/en/"><cite>DCAT-AP-SE: Clarifications, translations and explanations of DCAT-AP for Sweden</cite></a>. Matthias Palmér. URL: <a href="https://docs.dataportal.se/dcat/en/">https://docs.dataportal.se/dcat/en/</a> </dd><dt id="bib-dcat-ap.de">[DCAT-AP.de]</dt><dd> <a href="https://dcat-ap.de/def/"><cite>Vokabulare und Dokumente für DCAT-AP.de</cite></a>. URL: <a href="https://dcat-ap.de/def/">https://dcat-ap.de/def/</a> </dd><dt id="bib-dcat-be">[DCAT-BE]</dt><dd> <a href="http://dcat.be/"><cite>Linking data portals across Belgium.</cite></a>. URL: <a href="http://dcat.be/">http://dcat.be/</a> </dd><dt id="bib-dcat-ucr">[DCAT-UCR]</dt><dd> <a href="https://www.w3.org/TR/dcat-ucr/"><cite>Dataset Exchange Use Cases and Requirements</cite></a>. Jaroslav Pullmann; Rob Atkinson; Antoine Isaac; Ixchel Faniel. W3C. 17 January 2019. W3C Working Group Note. URL: <a href="https://www.w3.org/TR/dcat-ucr/">https://www.w3.org/TR/dcat-ucr/</a> </dd><dt id="bib-doap">[DOAP]</dt><dd> <a href="https://github.com/ewilderj/doap/wiki"><cite>Description of a Project</cite></a>. Edd Wilder-James. URL: <a href="https://github.com/ewilderj/doap/wiki">https://github.com/ewilderj/doap/wiki</a> </dd><dt id="bib-earl10-schema">[EARL10-Schema]</dt><dd> <a href="https://www.w3.org/TR/EARL10-Schema/"><cite>Evaluation and Report Language (EARL) 1.0 Schema</cite></a>. Shadi Abou-Zahra. W3C. 2 February 2017. W3C Working Group Note. URL: <a href="https://www.w3.org/TR/EARL10-Schema/">https://www.w3.org/TR/EARL10-Schema/</a> </dd><dt id="bib-euv-ar">[EUV-AR]</dt><dd> <a href="https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/access-right"><cite>Named Authority List: Access rights</cite></a>. Publications Office of the European Union. URL: <a href="https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/access-right">https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/access-right</a> </dd><dt id="bib-euv-cs">[EUV-CS]</dt><dd> <a href="https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/concept-status"><cite>Named Authority List: Concept statuses</cite></a>. Publications Office of the European Union. URL: <a href="https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/concept-status">https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/concept-status</a> </dd><dt id="bib-euv-ds">[EUV-DS]</dt><dd> <a href="https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/dataset-status"><cite>Named Authority List: Dataset statuses</cite></a>. Publications Office of the European Union. URL: <a href="https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/dataset-status">https://publications.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/dataset-status</a> </dd><dt id="bib-fair">[FAIR]</dt><dd> <a href="https://doi.org/10.1038/sdata.2016.18"><cite>The FAIR Guiding Principles for scientific data management and stewardship</cite></a>. Mark D. Wilkinson et al. Nature. Scientific Data, vol. 3, Article nr. 160018. URL: <a href="https://doi.org/10.1038/sdata.2016.18">https://doi.org/10.1038/sdata.2016.18</a> </dd><dt id="bib-geodcat-ap">[GeoDCAT-AP]</dt><dd> <a href="https://semiceu.github.io/GeoDCAT-AP/releases/"><cite>GeoDCAT-AP: A geospatial extension for the DCAT application profile for data portals in Europe</cite></a>. European Commission. 23 December 2020. URL: <a href="https://semiceu.github.io/GeoDCAT-AP/releases/">https://semiceu.github.io/GeoDCAT-AP/releases/</a> </dd><dt id="bib-geodcat-ap-it">[GeoDCAT-AP-IT]</dt><dd> <a href="https://web.archive.org/web/20200506120557/https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/news/geodcat-apit"><cite>GeoDCAT-AP in Italy, the national guidelines published</cite></a>. URL: <a href="https://web.archive.org/web/20200506120557/https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/news/geodcat-apit">https://web.archive.org/web/20200506120557/https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/news/geodcat-apit</a> </dd><dt id="bib-hcls-dataset">[HCLS-Dataset]</dt><dd> <a href="https://www.w3.org/TR/hcls-dataset/"><cite>Dataset Descriptions: HCLS Community Profile</cite></a>. Alasdair Gray; M. Scott Marshall; Michel Dumontier. W3C. 14 May 2015. W3C Working Group Note. URL: <a href="https://www.w3.org/TR/hcls-dataset/">https://www.w3.org/TR/hcls-dataset/</a> </dd><dt id="bib-html-rdfa">[HTML-RDFa]</dt><dd> <a href="https://www.w3.org/TR/html-rdfa/"><cite>HTML+RDFa 1.1 - Second Edition</cite></a>. Manu Sporny. W3C. 17 March 2015. W3C Recommendation. URL: <a href="https://www.w3.org/TR/html-rdfa/">https://www.w3.org/TR/html-rdfa/</a> </dd><dt id="bib-hydra">[HYDRA]</dt><dd> <a href="https://www.hydra-cg.com/spec/latest/core/"><cite>Hydra Core Vocabulary</cite></a>. Markus Lanthaler. Hydra W3C Community Group. 15 March 2018. Unofficial Draft. URL: <a href="https://www.hydra-cg.com/spec/latest/core/">https://www.hydra-cg.com/spec/latest/core/</a> </dd><dt id="bib-iana-relations">[IANA-RELATIONS]</dt><dd> <a href="https://www.iana.org/assignments/link-relations/"><cite>Link Relations</cite></a>. IANA. URL: <a href="https://www.iana.org/assignments/link-relations/">https://www.iana.org/assignments/link-relations/</a> </dd><dt id="bib-iana-uri-schemes">[IANA-URI-SCHEMES]</dt><dd> <a href="https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml"><cite>Uniform Resource Identifier (URI) Schemes</cite></a>. IANA. URL: <a href="https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml">https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml</a> </dd><dt id="bib-inspire-doc">[INSPIRE-DoC]</dt><dd> <a href="http://inspire.ec.europa.eu/metadata-codelist/DegreeOfConformity/"><cite>INSPIRE Registry: Degrees of conformity</cite></a>. European Commission. URL: <a href="http://inspire.ec.europa.eu/metadata-codelist/DegreeOfConformity/">http://inspire.ec.europa.eu/metadata-codelist/DegreeOfConformity/</a> </dd><dt id="bib-inspire-sdst">[INSPIRE-SDST]</dt><dd> <a href="http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/"><cite>INSPIRE Registry: Spatial data service types</cite></a>. European Commission. URL: <a href="http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/">http://inspire.ec.europa.eu/metadata-codelist/SpatialDataServiceType/</a> </dd><dt id="bib-iso-19115">[ISO-19115]</dt><dd> <a href="https://www.iso.org/standard/26020.html"><cite>Geographic information -- Metadata</cite></a>. ISO/TC 211. ISO. 2003. International Standard. URL: <a href="https://www.iso.org/standard/26020.html">https://www.iso.org/standard/26020.html</a> </dd><dt id="bib-iso-19115-1">[ISO-19115-1]</dt><dd> <a href="https://www.iso.org/standard/53798.html"><cite>Geographic information -- Metadata -- Part 1: Fundamentals</cite></a>. ISO/TC 211. ISO. 2014. International Standard. URL: <a href="https://www.iso.org/standard/53798.html">https://www.iso.org/standard/53798.html</a> </dd><dt id="bib-iso-19128">[ISO-19128]</dt><dd> <a href="https://www.iso.org/standard/32546.html"><cite>Geographic information -- Web map server interface</cite></a>. ISO/TC 211. ISO. 2005. International Standard. URL: <a href="https://www.iso.org/standard/32546.html">https://www.iso.org/standard/32546.html</a> </dd><dt id="bib-iso-19135">[ISO-19135]</dt><dd> <a href="https://www.iso.org/standard/32553.html"><cite>Geographic information -- Procedures for item registration</cite></a>. ISO/TC 211. ISO. 2005. International Standard. URL: <a href="https://www.iso.org/standard/32553.html">https://www.iso.org/standard/32553.html</a> </dd><dt id="bib-iso-19142">[ISO-19142]</dt><dd> <a href="https://www.iso.org/standard/42136.html"><cite>Geographic information -- Web Feature Service</cite></a>. ISO/TC 211. ISO. 2010. International Standard. URL: <a href="https://www.iso.org/standard/42136.html">https://www.iso.org/standard/42136.html</a> </dd><dt id="bib-iso-26324">[ISO-26324]</dt><dd> <a href="https://www.iso.org/standard/43506.html"><cite>Information and documentation -- Digital object identifier system</cite></a>. ISO/TC 46/SC 9. ISO. 2012. International Standard. URL: <a href="https://www.iso.org/standard/43506.html">https://www.iso.org/standard/43506.html</a> </dd><dt id="bib-iso-iec-25012">[ISO-IEC-25012]</dt><dd> <a href="http://iso25000.com/index.php/en/iso-25000-standards/iso-25012"><cite>ISO/IEC 25012 - Data Quality model</cite></a>. URL: <a href="http://iso25000.com/index.php/en/iso-25000-standards/iso-25012">http://iso25000.com/index.php/en/iso-25000-standards/iso-25012</a> </dd><dt id="bib-json-ld">[JSON-LD]</dt><dd> <a href="https://www.w3.org/TR/json-ld/"><cite>JSON-LD 1.0</cite></a>. Manu Sporny; Gregg Kellogg; Markus Lanthaler. W3C. 3 November 2020. W3C Recommendation. URL: <a href="https://www.w3.org/TR/json-ld/">https://www.w3.org/TR/json-ld/</a> </dd><dt id="bib-linkeddatapatterns">[LinkedDataPatterns]</dt><dd> <a href="http://patterns.dataincubator.org/book/"><cite>Linked Data Patterns: A pattern catalogue for modelling, publishing, and consuming Linked Data</cite></a>. Leigh Dodds; Ian Davis. 31 May 2012. URL: <a href="http://patterns.dataincubator.org/book/">http://patterns.dataincubator.org/book/</a> </dd><dt id="bib-n3">[N3]</dt><dd> <a href="https://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/"><cite>Notation3 (N3): A readable RDF syntax</cite></a>. Tim Berners-Lee; Dan Connolly. W3C. 14 January 2008. W3C Team Submission. URL: <a href="https://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/">https://www.w3.org/TeamSubmission/2008/SUBM-n3-20080114/</a> </dd><dt id="bib-netcdf">[netCDF]</dt><dd> <a href="https://www.unidata.ucar.edu/software/netcdf/"><cite>Network Common Data Form (NetCDF)</cite></a>. UNIDATA. URL: <a href="https://www.unidata.ucar.edu/software/netcdf/">https://www.unidata.ucar.edu/software/netcdf/</a> </dd><dt id="bib-odrs">[ODRS]</dt><dd> <a href="http://schema.theodi.org/odrs"><cite>Open Data Rights Statement Vocabulary</cite></a>. Leigh Dodds. ODI. 29 July 2013. URL: <a href="http://schema.theodi.org/odrs">http://schema.theodi.org/odrs</a> </dd><dt id="bib-openapi">[OpenAPI]</dt><dd> <a href="https://www.openapis.org/"><cite>OpenAPI Specification</cite></a>. Darrell Miller; Jason Harmon; Jeremy Whitlock; Marsh Gardiner; Mike Ralphson; Ron Ratovsky; Tony Tam; Uri Sarid. OpenAPI Initiative. URL: <a href="https://www.openapis.org/">https://www.openapis.org/</a> </dd><dt id="bib-opensearch">[OpenSearch]</dt><dd> <a href="https://github.com/dewitt/opensearch/blob/master/opensearch-1-1-draft-6.md"><cite>OpenSearch 1.1 Draft 6</cite></a>. DeWitt Clinton. OpenSearch. 17 April 2018. URL: <a href="https://github.com/dewitt/opensearch/blob/master/opensearch-1-1-draft-6.md">https://github.com/dewitt/opensearch/blob/master/opensearch-1-1-draft-6.md</a> </dd><dt id="bib-rdf11-concepts">[RDF11-CONCEPTS]</dt><dd> <a href="https://www.w3.org/TR/rdf11-concepts/"><cite>RDF 1.1 Concepts and Abstract Syntax</cite></a>. Richard Cyganiak; David Wood; Markus Lanthaler. W3C. 25 February 2014. W3C Recommendation. URL: <a href="https://www.w3.org/TR/rdf11-concepts/">https://www.w3.org/TR/rdf11-concepts/</a> </dd><dt id="bib-rdf11-primer">[RDF11-PRIMER]</dt><dd> <a href="https://www.w3.org/TR/rdf11-primer/"><cite>RDF 1.1 Primer</cite></a>. Guus Schreiber; Yves Raimond. W3C. 24 June 2014. W3C Working Group Note. URL: <a href="https://www.w3.org/TR/rdf11-primer/">https://www.w3.org/TR/rdf11-primer/</a> </dd><dt id="bib-re3data-schema">[RE3DATA-SCHEMA]</dt><dd> <a href="https://doi.org/10.2312/re3.008"><cite>Metadata Schema for the Description of Research Data Repositories: version 3</cite></a>. Jessika Rücknagel et al. GFZ Potsdam. 17 December 2015. URL: <a href="https://doi.org/10.2312/re3.008">https://doi.org/10.2312/re3.008</a> </dd><dt id="bib-rfc3986">[RFC3986]</dt><dd> <a href="https://www.rfc-editor.org/rfc/rfc3986"><cite>Uniform Resource Identifier (URI): Generic Syntax</cite></a>. T. Berners-Lee; R. Fielding; L. Masinter. IETF. January 2005. Internet Standard. URL: <a href="https://www.rfc-editor.org/rfc/rfc3986">https://www.rfc-editor.org/rfc/rfc3986</a> </dd><dt id="bib-rfc3987">[RFC3987]</dt><dd> <a href="https://www.rfc-editor.org/rfc/rfc3987"><cite>Internationalized Resource Identifiers (IRIs)</cite></a>. M. Duerst; M. Suignard. IETF. January 2005. Proposed Standard. URL: <a href="https://www.rfc-editor.org/rfc/rfc3987">https://www.rfc-editor.org/rfc/rfc3987</a> </dd><dt id="bib-schema-org">[SCHEMA-ORG]</dt><dd> <a href="https://schema.org/"><cite>Schema.org</cite></a>. URL: <a href="https://schema.org/">https://schema.org/</a> </dd><dt id="bib-sdw-bp">[SDW-BP]</dt><dd> <a href="https://www.w3.org/TR/sdw-bp/"><cite>Spatial Data on the Web Best Practices</cite></a>. Payam Barnaghi; Jeremy Tandy; Linda van den Brink; Timo Homburg. W3C. 19 September 2023. W3C Working Group Note. URL: <a href="https://www.w3.org/TR/sdw-bp/">https://www.w3.org/TR/sdw-bp/</a> </dd><dt id="bib-shacl">[SHACL]</dt><dd> <a href="https://www.w3.org/TR/shacl/"><cite>Shapes Constraint Language (SHACL)</cite></a>. Holger Knublauch; Dimitris Kontokostas. W3C. 20 July 2017. W3C Recommendation. URL: <a href="https://www.w3.org/TR/shacl/">https://www.w3.org/TR/shacl/</a> </dd><dt id="bib-shex">[ShEx]</dt><dd> <a href="http://shex.io/shex-semantics/"><cite>Shape Expressions Language 2.1</cite></a>. Shape Expressions W3C Community Group. 17 November 2018. Draft Community Group Report. URL: <a href="http://shex.io/shex-semantics/">http://shex.io/shex-semantics/</a> </dd><dt id="bib-sparql11-protocol">[SPARQL11-PROTOCOL]</dt><dd> <a href="https://www.w3.org/TR/sparql11-protocol/"><cite>SPARQL 1.1 Protocol</cite></a>. Lee Feigenbaum; Gregory Williams; Kendall Clark; Elias Torres. W3C. 21 March 2013. W3C Recommendation. URL: <a href="https://www.w3.org/TR/sparql11-protocol/">https://www.w3.org/TR/sparql11-protocol/</a> </dd><dt id="bib-sparql11-query">[SPARQL11-QUERY]</dt><dd> <a href="https://www.w3.org/TR/sparql11-query/"><cite>SPARQL 1.1 Query Language</cite></a>. Steven Harris; Andy Seaborne. W3C. 21 March 2013. W3C Recommendation. URL: <a href="https://www.w3.org/TR/sparql11-query/">https://www.w3.org/TR/sparql11-query/</a> </dd><dt id="bib-sparql11-service-description">[SPARQL11-SERVICE-DESCRIPTION]</dt><dd> <a href="https://www.w3.org/TR/sparql11-service-description/"><cite>SPARQL 1.1 Service Description</cite></a>. Gregory Williams. W3C. 21 March 2013. W3C Recommendation. URL: <a href="https://www.w3.org/TR/sparql11-service-description/">https://www.w3.org/TR/sparql11-service-description/</a> </dd><dt id="bib-statdcat-ap">[StatDCAT-AP]</dt><dd> <a href="https://joinup.ec.europa.eu/solution/statdcat-application-profile-data-portals-europe"><cite>StatDCAT-AP – DCAT Application Profile for description of statistical datasets. Version 1.0.1</cite></a>. European Commission. 28 May 2019. URL: <a href="https://joinup.ec.europa.eu/solution/statdcat-application-profile-data-portals-europe">https://joinup.ec.europa.eu/solution/statdcat-application-profile-data-portals-europe</a> </dd><dt id="bib-turtle">[Turtle]</dt><dd> <a href="https://www.w3.org/TR/turtle/"><cite>RDF 1.1 Turtle</cite></a>. Eric Prud'hommeaux; Gavin Carothers. W3C. 25 February 2014. W3C Recommendation. URL: <a href="https://www.w3.org/TR/turtle/">https://www.w3.org/TR/turtle/</a> </dd><dt id="bib-ukgovld-reg">[UKGOVLD-REG]</dt><dd> <a href="https://github.com/UKGovLD/registry-core/wiki/Principles-and-concepts"><cite>Linked Data Registry - Principles and Concepts</cite></a>. UK Government Linked Data Working Group. URL: <a href="https://github.com/UKGovLD/registry-core/wiki/Principles-and-concepts">https://github.com/UKGovLD/registry-core/wiki/Principles-and-concepts</a> </dd><dt id="bib-vivo-isf">[VIVO-ISF]</dt><dd> <a href="https://github.com/vivo-isf/vivo-isf"><cite>VIVO-ISF Data Standard</cite></a>. URL: <a href="https://github.com/vivo-isf/vivo-isf">https://github.com/vivo-isf/vivo-isf</a> </dd><dt id="bib-vocab-data-cube">[VOCAB-DATA-CUBE]</dt><dd> <a href="https://www.w3.org/TR/vocab-data-cube/"><cite>The RDF Data Cube Vocabulary</cite></a>. Richard Cyganiak; Dave Reynolds. W3C. 16 January 2014. W3C Recommendation. URL: <a href="https://www.w3.org/TR/vocab-data-cube/">https://www.w3.org/TR/vocab-data-cube/</a> </dd><dt id="bib-vocab-dcat-1">[VOCAB-DCAT-1]</dt><dd> <a href="https://www.w3.org/TR/vocab-dcat-1/"><cite>Data Catalog Vocabulary (DCAT)</cite></a>. Fadi Maali; John Erickson. W3C. 4 February 2020. W3C Recommendation. URL: <a href="https://www.w3.org/TR/vocab-dcat-1/">https://www.w3.org/TR/vocab-dcat-1/</a> </dd><dt id="bib-vocab-dcat-2">[VOCAB-DCAT-2]</dt><dd> <a href="https://www.w3.org/TR/vocab-dcat-2/"><cite>Data Catalog Vocabulary (DCAT) - Version 2</cite></a>. Riccardo Albertoni; David Browning; Simon Cox; Alejandra Gonzalez Beltran; Andrea Perego; Peter Winstanley. W3C. 4 February 2020. W3C Recommendation. URL: <a href="https://www.w3.org/TR/vocab-dcat-2/">https://www.w3.org/TR/vocab-dcat-2/</a> </dd><dt id="bib-vocab-dcat-2-20200204">[VOCAB-DCAT-2-20200204]</dt><dd> <a href="https://www.w3.org/TR/2020/REC-vocab-dcat-2-20200204/"><cite>Data Catalog Vocabulary (DCAT) - Version 2</cite></a>. Riccardo Albertoni; David Browning; Simon Cox; Alejandra Gonzalez Beltran; Andrea Perego; Peter Winstanley. W3C. 4 February 2020. W3C Recommendation. URL: <a href="https://www.w3.org/TR/2020/REC-vocab-dcat-2-20200204/">https://www.w3.org/TR/2020/REC-vocab-dcat-2-20200204/</a> </dd><dt id="bib-vocab-dcat-3-20201217">[VOCAB-DCAT-3-20201217]</dt><dd> <a href="https://www.w3.org/TR/2020/WD-vocab-dcat-3-20201217/"><cite>Data Catalog Vocabulary (DCAT) - Version 3</cite></a>. Riccardo Albertoni; David Browning; Simon Cox; Alejandra Gonzalez Beltran; Andrea Perego; Peter Winstanley. W3C. 17 December 2020. W3C Working Draft. URL: <a href="https://www.w3.org/TR/2020/WD-vocab-dcat-3-20201217/">https://www.w3.org/TR/2020/WD-vocab-dcat-3-20201217/</a> </dd><dt id="bib-vocab-dcat-3-20210504">[VOCAB-DCAT-3-20210504]</dt><dd> <a href="https://www.w3.org/TR/2021/WD-vocab-dcat-3-20210504/"><cite>Data Catalog Vocabulary (DCAT) - Version 3</cite></a>. Riccardo Albertoni; David Browning; Simon Cox; Alejandra Gonzalez Beltran; Andrea Perego; Peter Winstanley. W3C. 4 May 2021. W3C Working Draft. URL: <a href="https://www.w3.org/TR/2021/WD-vocab-dcat-3-20210504/">https://www.w3.org/TR/2021/WD-vocab-dcat-3-20210504/</a> </dd><dt id="bib-vocab-dcat-3-20220111">[VOCAB-DCAT-3-20220111]</dt><dd> <a href="https://www.w3.org/TR/2022/WD-vocab-dcat-3-20220111/"><cite>Data Catalog Vocabulary (DCAT) - Version 3</cite></a>. Riccardo Albertoni; David Browning; Simon Cox; Alejandra Gonzalez Beltran; Andrea Perego; Peter Winstanley. W3C. 11 January 2022. W3C Working Draft. URL: <a href="https://www.w3.org/TR/2022/WD-vocab-dcat-3-20220111/">https://www.w3.org/TR/2022/WD-vocab-dcat-3-20220111/</a> </dd><dt id="bib-vocab-dcat-3-20220510">[VOCAB-DCAT-3-20220510]</dt><dd> <a href="https://www.w3.org/TR/2022/WD-vocab-dcat-3-20220510/"><cite>Data Catalog Vocabulary (DCAT) - Version 3</cite></a>. Riccardo Albertoni; David Browning; Simon Cox; Alejandra Gonzalez Beltran; Andrea Perego; Peter Winstanley. W3C. 10 May 2022. W3C Working Draft. URL: <a href="https://www.w3.org/TR/2022/WD-vocab-dcat-3-20220510/">https://www.w3.org/TR/2022/WD-vocab-dcat-3-20220510/</a> </dd><dt id="bib-vocab-dcat-3-20240118">[VOCAB-DCAT-3-20240118]</dt><dd> <a href="https://www.w3.org/TR/2024/CR-vocab-dcat-3-20240118/"><cite>Data Catalog Vocabulary (DCAT) - Version 3</cite></a>. Simon Cox; Andrea Perego; Alejandra Gonzalez Beltran; Peter Winstanley; Riccardo Albertoni; David Browning. W3C. 18 January 2024. W3C Candidate Recommendation. URL: <a href="https://www.w3.org/TR/2024/CR-vocab-dcat-3-20240118/">https://www.w3.org/TR/2024/CR-vocab-dcat-3-20240118/</a> </dd><dt id="bib-vocab-dqv">[VOCAB-DQV]</dt><dd> <a href="https://www.w3.org/TR/vocab-dqv/"><cite>Data on the Web Best Practices: Data Quality Vocabulary</cite></a>. Riccardo Albertoni; Antoine Isaac. W3C. 15 December 2016. W3C Working Group Note. URL: <a href="https://www.w3.org/TR/vocab-dqv/">https://www.w3.org/TR/vocab-dqv/</a> </dd><dt id="bib-vocab-org">[VOCAB-ORG]</dt><dd> <a href="https://www.w3.org/TR/vocab-org/"><cite>The Organization Ontology</cite></a>. Dave Reynolds. W3C. 16 January 2014. W3C Recommendation. URL: <a href="https://www.w3.org/TR/vocab-org/">https://www.w3.org/TR/vocab-org/</a> </dd><dt id="bib-vocab-ssn">[VOCAB-SSN]</dt><dd> <a href="https://www.w3.org/TR/vocab-ssn/"><cite>Semantic Sensor Network Ontology</cite></a>. Armin Haller; Krzysztof Janowicz; Simon Cox; Danh Le Phuoc; Kerry Taylor; Maxime Lefrançois. W3C. 19 October 2017. W3C Recommendation. URL: <a href="https://www.w3.org/TR/vocab-ssn/">https://www.w3.org/TR/vocab-ssn/</a> </dd><dt id="bib-void">[VOID]</dt><dd> <a href="https://www.w3.org/TR/void/"><cite>Describing Linked Datasets with the VoID Vocabulary</cite></a>. Keith Alexander; Richard Cyganiak; Michael Hausenblas; Jun Zhao. W3C. 3 March 2011. W3C Working Group Note. URL: <a href="https://www.w3.org/TR/void/">https://www.w3.org/TR/void/</a> </dd><dt id="bib-w3c-basic-geo">[W3C-BASIC-GEO]</dt><dd> <a href="https://www.w3.org/2003/01/geo/"><cite>Basic Geo (WGS84 lat/long) Vocabulary</cite></a>. Dan Brickley. W3C Semantic Web Interest Group. 1 February 2006. URL: <a href="https://www.w3.org/2003/01/geo/">https://www.w3.org/2003/01/geo/</a> </dd><dt id="bib-wfs">[WFS]</dt><dd> <a href="http://www.opengeospatial.org/standards/wfs"><cite>Web Feature Service 2.0 Interface Standard</cite></a>. Panagiotis (Peter) A. Vretanos. OGC. 10 July 2014. OGC Interface Standard. URL: <a href="http://www.opengeospatial.org/standards/wfs">http://www.opengeospatial.org/standards/wfs</a> </dd><dt id="bib-wms">[WMS]</dt><dd> <a href="http://www.opengeospatial.org/standards/wms"><cite>Web Map Service Implementation Specification</cite></a>. Jeff de la Beaujardiere. OGC. 15 March 2006. OpenGIS Implementation Standard. URL: <a href="http://www.opengeospatial.org/standards/wms">http://www.opengeospatial.org/standards/wms</a> </dd><dt id="bib-wsdl20">[WSDL20]</dt><dd> <a href="https://www.w3.org/TR/wsdl20/"><cite>Web Services Description Language (WSDL) Version 2.0 Part 1: Core Language</cite></a>. Roberto Chinnici; Jean-Jacques Moreau; Arthur Ryman; Sanjiva Weerawarana et al. W3C. 26 June 2007. W3C Recommendation. URL: <a href="https://www.w3.org/TR/wsdl20/">https://www.w3.org/TR/wsdl20/</a> </dd><dt id="bib-xhtml-vocab">[XHTML-VOCAB]</dt><dd> <a href="https://www.w3.org/1999/xhtml/vocab"><cite>XHTML Vocabulary</cite></a>. XHTML 2 Working Group. W3C. 27 October 2010. URL: <a href="https://www.w3.org/1999/xhtml/vocab">https://www.w3.org/1999/xhtml/vocab</a> </dd><dt id="bib-zaverietal">[ZaveriEtAl]</dt><dd> <a href="https://doi.org/10.3233/SW-150175"><cite>Quality assessment for Linked Data: A Survey</cite></a>. Amrapali Zaveri et al. IOS Press. 2015. Semantic Web, vol. 7, no. 1, pp. 63-93. URL: <a href="https://doi.org/10.3233/SW-150175">https://doi.org/10.3233/SW-150175</a> </dd></dl> </section></section><p role="navigation" id="back-to-top"> <a href="#title"><abbr title="Back to Top">↑</abbr></a> </p><script id="respec-dfn-panel">(() => { // @ts-check if (document.respec) { document.respec.ready.then(setupPanel); } else { setupPanel(); } function setupPanel() { const listener = panelListener(); document.body.addEventListener("keydown", listener); document.body.addEventListener("click", listener); } function panelListener() { /** @type {HTMLElement} */ let panel = null; return event => { const { target, type } = event; if (!(target instanceof HTMLElement)) return; // For keys, we only care about Enter key to activate the panel // otherwise it's activated via a click. if (type === "keydown" && event.key !== "Enter") return; const action = deriveAction(event); switch (action) { case "show": { hidePanel(panel); /** @type {HTMLElement} */ const dfn = target.closest("dfn, .index-term"); panel = document.getElementById(`dfn-panel-for-${dfn.id}`); const coords = deriveCoordinates(event); displayPanel(dfn, panel, coords); break; } case "dock": { panel.style.left = null; panel.style.top = null; panel.classList.add("docked"); break; } case "hide": { hidePanel(panel); panel = null; break; } } }; } /** * @param {MouseEvent|KeyboardEvent} event */ function deriveCoordinates(event) { const target = /** @type HTMLElement */ (event.target); // We prevent synthetic AT clicks from putting // the dialog in a weird place. The AT events sometimes // lack coordinates, so they have clientX/Y = 0 const rect = target.getBoundingClientRect(); if ( event instanceof MouseEvent && event.clientX >= rect.left && event.clientY >= rect.top ) { // The event probably happened inside the bounding rect... return { x: event.clientX, y: event.clientY }; } // Offset to the middle of the element const x = rect.x + rect.width / 2; // Placed at the bottom of the element const y = rect.y + rect.height; return { x, y }; } /** * @param {Event} event */ function deriveAction(event) { const target = /** @type {HTMLElement} */ (event.target); const hitALink = !!target.closest("a"); if (target.closest("dfn:not([data-cite]), .index-term")) { return hitALink ? "none" : "show"; } if (target.closest(".dfn-panel")) { if (hitALink) { return target.classList.contains("self-link") ? "hide" : "dock"; } const panel = target.closest(".dfn-panel"); return panel.classList.contains("docked") ? "hide" : "none"; } if (document.querySelector(".dfn-panel:not([hidden])")) { return "hide"; } return "none"; } /** * @param {HTMLElement} dfn * @param {HTMLElement} panel * @param {{ x: number, y: number }} clickPosition */ function displayPanel(dfn, panel, { x, y }) { panel.hidden = false; // distance (px) between edge of panel and the pointing triangle (caret) const MARGIN = 20; const dfnRects = dfn.getClientRects(); // Find the `top` offset when the `dfn` can be spread across multiple lines let closestTop = 0; let minDiff = Infinity; for (const rect of dfnRects) { const { top, bottom } = rect; const diffFromClickY = Math.abs((top + bottom) / 2 - y); if (diffFromClickY < minDiff) { minDiff = diffFromClickY; closestTop = top; } } const top = window.scrollY + closestTop + dfnRects[0].height; const left = x - MARGIN; panel.style.left = `${left}px`; panel.style.top = `${top}px`; // Find if the panel is flowing out of the window const panelRect = panel.getBoundingClientRect(); const SCREEN_WIDTH = Math.min(window.innerWidth, window.screen.width); if (panelRect.right > SCREEN_WIDTH) { const newLeft = Math.max(MARGIN, x + MARGIN - panelRect.width); const newCaretOffset = left - newLeft; panel.style.left = `${newLeft}px`; /** @type {HTMLElement} */ const caret = panel.querySelector(".caret"); caret.style.left = `${newCaretOffset}px`; } // As it's a dialog, we trap focus. // TODO: when <dialog> becomes a implemented, we should really // use that. trapFocus(panel, dfn); } /** * @param {HTMLElement} panel * @param {HTMLElement} dfn * @returns */ function trapFocus(panel, dfn) { /** @type NodeListOf<HTMLAnchorElement> elements */ const anchors = panel.querySelectorAll("a[href]"); // No need to trap focus if (!anchors.length) return; // Move focus to first anchor element const first = anchors.item(0); first.focus(); const trapListener = createTrapListener(anchors, panel, dfn); panel.addEventListener("keydown", trapListener); // Hiding the panel releases the trap const mo = new MutationObserver(records => { const [record] = records; const target = /** @type HTMLElement */ (record.target); if (target.hidden) { panel.removeEventListener("keydown", trapListener); mo.disconnect(); } }); mo.observe(panel, { attributes: true, attributeFilter: ["hidden"] }); } /** * * @param {NodeListOf<HTMLAnchorElement>} anchors * @param {HTMLElement} panel * @param {HTMLElement} dfn * @returns */ function createTrapListener(anchors, panel, dfn) { const lastIndex = anchors.length - 1; let currentIndex = 0; return event => { switch (event.key) { // Hitting "Tab" traps us in a nice loop around elements. case "Tab": { event.preventDefault(); currentIndex += event.shiftKey ? -1 : +1; if (currentIndex < 0) { currentIndex = lastIndex; } else if (currentIndex > lastIndex) { currentIndex = 0; } anchors.item(currentIndex).focus(); break; } // Hitting "Enter" on an anchor releases the trap. case "Enter": hidePanel(panel); break; // Hitting "Escape" returns focus to dfn. case "Escape": hidePanel(panel); dfn.focus(); return; } }; } /** @param {HTMLElement} panel */ function hidePanel(panel) { if (!panel) return; panel.hidden = true; panel.classList.remove("docked"); } })()</script><script src="https://www.w3.org/scripts/TR/2021/fixup.js"></script></body></html>