--- a/adms/index.html Thu Jun 06 10:23:55 2013 +0200
+++ b/adms/index.html Mon Jun 10 11:25:29 2013 +0200
@@ -1,15 +1,12 @@
-<!DOCTYPE html>
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
- <title>Asset Description Metadata Schema (ADMS)</title>
- <meta name="description" content="A vocabulary for describing semantic interoperability assets - highly reusable metadata and reference data used for eGovernment system development." />
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <!--[if lt IE 9]>
- <script src="http://www.w3.org/2008/site/js/html5shiv.js"></script> <![endif]-->
- <script type="text/javascript" src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
- <script src="respec-ref.js"></script>
- <script src="respec-config.js"></script>
- <style type="text/css">
+ <!DOCTYPE html>
+ <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en" dir="ltr">
+ <head>
+ <title>Asset Description Metadata Schema (ADMS)</title>
+ <meta name="description" content="A vocabulary for describing semantic interoperability assets - highly reusable metadata and reference data used for eGovernment system development.">
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+ <!--[if lt IE 9]>
+ <script src="http://www.w3.org/2008/site/js/html5shiv.js"></script> <![endif]-->
+ <style type="text/css">
table {
border-collapse:collapse;
width:100%;
@@ -27,22 +24,6 @@
table tr.midtable th {
border-top: black medium double;
}
- .editorsnote::before {
- content: "Editor's Note";
- display: block;
- width: 150px;
- background: #F30023;
- color: #fff;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #cff6d9;
- padding: 3px 1em;
- }
- .editorsnote {
- margin: 1em 0em 1em 1em;
- padding: 1em;
- border: 2px solid #cff6d9;
- }
pre {
padding: 1em;
border: 1px dashed #2f6fab;
@@ -59,891 +40,2802 @@
font-style:italic;
font-weight:bold;
}
- </style>
-</head>
-<body>
+/*****************************************************************
+ * ReSpec CSS
+ * Robin Berjon (robin at berjon dot com)
+ * v0.05 - 2009-07-31
+ *****************************************************************/
-<section id="abstract">
-<p>ADMS is a profile of DCAT, used to describe <em>semantic assets</em> (or just 'Assets'), defined as highly reusable metadata (e.g. xml schemata,
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
+
+a.bibref {
+ text-decoration: none;
+}
+
+code {
+ color: #ff4500;
+}
+
+h1 abbr, h2 abbr, h3 abbr {border:none}
+
+/* --- TOC --- */
+.toc a {
+ text-decoration: none;
+}
+
+a .secno {
+ color: #000;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+ margin-top: 0;
+}
+
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
+.section dd {
+ margin-bottom: 1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+
+</style>
+ <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE"/>
+ </head>
+ <body style="display: inherit;">
+ <div class="head">
+ <p>
+ <a href="http://www.w3.org/">
+ <img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C">
+ </a>
+ </p>
+ <h1 class="title" id="title">Asset Description Metadata Schema (ADMS)</h1>
+ <h2 id="w3c-note-11-june-2013">
+ <abbr title="World Wide Web Consortium">W3C</abbr>
+ Working Group Note 11 June 2013
+ </h2>
+ <dl>
+ <dt>This version:</dt>
+ <dd>
+ <a href="http://www.w3.org/TR/2013/NOTE-vocab-adms-20130611/">http://www.w3.org/TR/2013/NOTE-vocab-adms-20130611/</a>
+ </dd>
+ <dt>Latest published version:</dt>
+ <dd>
+ <a href="http://www.w3.org/TR/vocab-adms/">http://www.w3.org/TR/vocab-adms/</a>
+ </dd>
+ <dt>Previous version:</dt>
+ <dd><a href="http://www.w3.org/TR/2013/NOTE-vocab-adms-20130528/">http://www.w3.org/TR/2013/NOTE-vocab-adms-20130528/</a></dd>
+ <dt>Editors:</dt>
+ <dd>
+ <a href="http://www.w3.org/People/all#phila">Phil Archer</a>
+ ,
+ <a href="http://www.w3.org">
+ <abbr title="World Wide Web Consortium">W3C</abbr>
+ /
+ <abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr>
+ </a>
+ </dd>
+ <dd>
+ <a href="mailto:Gofran.shakair@deri.org">Gofran Shukair</a>
+ ,
+ <a href="http://www.deri.ie">DERI, NUIG</a>
+ </dd>
+ <dt>Author:</dt>
+ <dd>
+ <a href="http://makxdekkers.com/">Makx Dekkers</a>
+ , AMI Consult (original document)
+ </dd>
+ </dl>
+ <p>The vocabulary defined in this document is also available in these non-normative formats: <a href="http://www.w3.org/ns/adms.rdf">RDF/XML</a> and <a href="http://www.w3.org/ns/adms.ttl">Turtle</a>.</p>
+ <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2013 <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
+ <hr>
+ </div>
+ <div id="abstract" class="introductory section">
+ <h2>Abstract</h2>
+ <p>
+ ADMS is a profile of DCAT, used to describe
+ <em>semantic assets</em>
+ (or just 'Assets'), defined as highly reusable metadata (e.g. xml schemata,
generic data models) and reference data (e.g. code lists, taxonomies, dictionaries,
-vocabularies) that are used for eGovernment system development.</p>
-<p>@@@ Move above the HR in publication version@@@ Terms in the ADMS namespace are available in both <a href="adms20130508.rdf">RDF/XML</a> and <a href="adms20130508.ttl">Turtle</a>.</p>
-</section>
+vocabularies) that are used for eGovernment system development.
+ </p>
+ </div>
+ <div id="sotd" class="introductory section">
+ <h2>Status of This Document</h2>
+ <p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
+ <p>This document was published by the <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a>
+ as a Note. If you wish to make comments regarding this document, please send them to
+ <a href="mailto:public-gld-comments@w3.org">public-gld-comments@w3.org</a> (<a href="mailto:public-gld-comments-request@w3.org?subject=subscribe">subscribe</a>,
+ <a href="http://lists.w3.org/Archives/Public/public-gld-comments/">archives</a>). All feedback is welcome.</p>
+<p>The only changes made since the <a href="http://www.w3.org/TR/2013/NOTE-vocab-adms-20130528/">previous version</a>
+of this document concern the acknowledgement section. No substantive changes have been made.</p>
-<section class="informative">
-<h2 id="intro">Introduction</h2>
-<p>ADMS, the Asset Description Metadata Schema, is a profile of DCAT [[!DCAT]] for describing so-called
-<em>Semantic Assets</em> (or just 'Assets'), that is, highly reusable metadata (e.g. xml schemata,
+ <p>Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft
+ document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to
+ cite this document as other than work in progress.</p>
+ <p> This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February
+ 2004 W3C Patent Policy</a>. W3C maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/47663/status">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="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a>
+ must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+ 6 of the W3C Patent Policy</a>. </p>
+
+ </div>
+ <div id="toc" class="section">
+ <h2 class="introductory">Table of Contents</h2>
+ <ul class="toc">
+ <li class="tocline">
+ <a href="#introduction" class="tocxref">
+ <span class="secno">1. </span>
+ Introduction
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#conformance" class="tocxref">
+ <span class="secno">2. </span>
+ Conformance
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#namespaces-1" class="tocxref">
+ <span class="secno">3. </span>
+ Namespaces
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#vocabulary-overview" class="tocxref">
+ <span class="secno">4. </span>
+ Vocabulary Overview
+ </a>
+ <ul class="toc">
+ <li class="tocline">
+ <a href="#example-1" class="tocxref">
+ <span class="secno">4.1 </span>
+ Example
+ </a>
+ </li>
+ </ul>
+ </li>
+ <li class="tocline">
+ <a href="#the-adms-domain-model" class="tocxref">
+ <span class="secno">5. </span>
+ The ADMS Domain Model
+ </a>
+ <ul class="toc">
+ <li class="tocline">
+ <a href="#the-primary-concepts" class="tocxref">
+ <span class="secno">5.1 </span>
+ The Primary Concepts
+ </a>
+ <ul class="toc">
+ <li class="tocline">
+ <a href="#asset-repository" class="tocxref">
+ <span class="secno">5.1.1 </span>
+ Asset Repository
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#asset" class="tocxref">
+ <span class="secno">5.1.2 </span>
+ Asset
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#asset-distribution-1" class="tocxref">
+ <span class="secno">5.1.3 </span>
+ Asset Distribution
+ </a>
+ </li>
+ </ul>
+ </li>
+ <li class="tocline">
+ <a href="#the-secondary-concepts" class="tocxref">
+ <span class="secno">5.2 </span>
+ The Secondary Concepts
+ </a>
+ <ul class="toc">
+ <li class="tocline">
+ <a href="#asset-type" class="tocxref">
+ <span class="secno">5.2.1 </span>
+ Asset Type
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#contact-information" class="tocxref">
+ <span class="secno">5.2.2 </span>
+ Contact Information
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#documentation" class="tocxref">
+ <span class="secno">5.2.3 </span>
+ Documentation
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#file-format" class="tocxref">
+ <span class="secno">5.2.4 </span>
+ File Format
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#geographical-coverage" class="tocxref">
+ <span class="secno">5.2.5 </span>
+ Geographical Coverage
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#identifier" class="tocxref">
+ <span class="secno">5.2.6 </span>
+ Identifier
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#interoperability-level" class="tocxref">
+ <span class="secno">5.2.7 </span>
+ Interoperability Level
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#language" class="tocxref">
+ <span class="secno">5.2.8 </span>
+ Language
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#license" class="tocxref">
+ <span class="secno">5.2.9 </span>
+ License
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#period-of-time" class="tocxref">
+ <span class="secno">5.2.10 </span>
+ Period of time
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#publisher" class="tocxref">
+ <span class="secno">5.2.11 </span>
+ Publisher
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#representation-technique" class="tocxref">
+ <span class="secno">5.2.12 </span>
+ Representation Technique
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#status" class="tocxref">
+ <span class="secno">5.2.13 </span>
+ Status
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#theme" class="tocxref">
+ <span class="secno">5.2.14 </span>
+ Theme
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#theme-taxonomy" class="tocxref">
+ <span class="secno">5.2.15 </span>
+ Theme Taxonomy
+ </a>
+ </li>
+ </ul>
+ </li>
+ <li class="tocline">
+ <a href="#properties-and-relationships" class="tocxref">
+ <span class="secno">5.3 </span>
+ Properties and Relationships
+ </a>
+ <ul class="toc">
+ <li class="tocline">
+ <a href="#dcat-accessurl" class="tocxref">
+ <span class="secno">5.3.1 </span>
+ dcat:accessURL
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#skos-altlabel" class="tocxref">
+ <span class="secno">5.3.2 </span>
+ skos:altLabel
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcat-contactpoint" class="tocxref">
+ <span class="secno">5.3.3 </span>
+ dcat:contactPoint
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-creator" class="tocxref">
+ <span class="secno">5.3.4 </span>
+ dcterms:creator
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcat-dataset" class="tocxref">
+ <span class="secno">5.3.5 </span>
+ dcat:dataset
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#wdrs-describedby" class="tocxref">
+ <span class="secno">5.3.6 </span>
+ wdrs:describedby
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-description" class="tocxref">
+ <span class="secno">5.3.7 </span>
+ dcterms:description
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcat-distribution" class="tocxref">
+ <span class="secno">5.3.8 </span>
+ dcat:distribution
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcat-downloadurl" class="tocxref">
+ <span class="secno">5.3.9 </span>
+ dcat:downloadURL
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#schema-enddate" class="tocxref">
+ <span class="secno">5.3.10 </span>
+ schema:endDate
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-format" class="tocxref">
+ <span class="secno">5.3.11 </span>
+ dcterms:format
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-identifier" class="tocxref">
+ <span class="secno">5.3.12 </span>
+ adms:identifier
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-includedasset" class="tocxref">
+ <span class="secno">5.3.13 </span>
+ adms:includedAsset
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-interoperabilitylevel" class="tocxref">
+ <span class="secno">5.3.14 </span>
+ adms:interoperabilityLevel
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-issued" class="tocxref">
+ <span class="secno">5.3.15 </span>
+ dcterms:issued
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcat-keyword" class="tocxref">
+ <span class="secno">5.3.16 </span>
+ dcat:keyword
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcat-landingpage" class="tocxref">
+ <span class="secno">5.3.17 </span>
+ dcat:landingPage
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-language" class="tocxref">
+ <span class="secno">5.3.18 </span>
+ dcterms:language
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-last" class="tocxref">
+ <span class="secno">5.3.19 </span>
+ adms:last
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-license" class="tocxref">
+ <span class="secno">5.3.20 </span>
+ dcterms:license
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcat-mediatype" class="tocxref">
+ <span class="secno">5.3.21 </span>
+ dcat:mediaType
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-modified" class="tocxref">
+ <span class="secno">5.3.22 </span>
+ dcterms:modified
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-next" class="tocxref">
+ <span class="secno">5.3.23 </span>
+ adms:next
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#skos-notation" class="tocxref">
+ <span class="secno">5.3.24 </span>
+ skos:notation
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-prev" class="tocxref">
+ <span class="secno">5.3.25 </span>
+ adms:prev
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-publisher" class="tocxref">
+ <span class="secno">5.3.26 </span>
+ dcterms:publisher
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#foaf-page" class="tocxref">
+ <span class="secno">5.3.27 </span>
+ foaf:page
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-relation" class="tocxref">
+ <span class="secno">5.3.28 </span>
+ dcterms:relation
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-representationtechnique" class="tocxref">
+ <span class="secno">5.3.29 </span>
+ adms:representationTechnique
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-sample" class="tocxref">
+ <span class="secno">5.3.30 </span>
+ adms:sample
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-schemaagency" class="tocxref">
+ <span class="secno">5.3.31 </span>
+ adms:schemaAgency
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-spatial" class="tocxref">
+ <span class="secno">5.3.32 </span>
+ dcterms:spatial
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#schema-startdate" class="tocxref">
+ <span class="secno">5.3.33 </span>
+ schema:startDate
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-status" class="tocxref">
+ <span class="secno">5.3.34 </span>
+ adms:status
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-supportedschema" class="tocxref">
+ <span class="secno">5.3.35 </span>
+ adms:supportedSchema
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-temporal" class="tocxref">
+ <span class="secno">5.3.36 </span>
+ dcterms:temporal
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcat-theme" class="tocxref">
+ <span class="secno">5.3.37 </span>
+ dcat:theme
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcat-themetaxonomy" class="tocxref">
+ <span class="secno">5.3.38 </span>
+ dcat:themeTaxonomy
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-title" class="tocxref">
+ <span class="secno">5.3.39 </span>
+ dcterms:title
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-translation" class="tocxref">
+ <span class="secno">5.3.40 </span>
+ adms:translation
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#dcterms-type" class="tocxref">
+ <span class="secno">5.3.41 </span>
+ dcterms:type
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#owl-versioninfo" class="tocxref">
+ <span class="secno">5.3.42 </span>
+ owl:versionInfo
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#adms-versionnotes" class="tocxref">
+ <span class="secno">5.3.43 </span>
+ adms:versionNotes
+ </a>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ <li class="tocline">
+ <a href="#acknowledgements" class="tocxref">
+ <span class="secno">A. </span>
+ Acknowledgements
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#references" class="tocxref">
+ <span class="secno">B. </span>
+ References
+ </a>
+ <ul class="toc">
+ <li class="tocline">
+ <a href="#normative-references" class="tocxref">
+ <span class="secno">B.1 </span>
+ Normative references
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#informative-references" class="tocxref">
+ <span class="secno">B.2 </span>
+ Informative references
+ </a>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </div>
+ <div class="informative section" id="introduction">
+ <!--OddPage-->
+ <h2 id="intro">
+ <span class="secno">1. </span>
+ Introduction
+ </h2>
+ <p>
+ <em>This section is non-normative.</em>
+ </p>
+ <p>
+ ADMS, the Asset Description Metadata Schema, is a profile of DCAT [
+ <cite>
+ <a class="bibref" href="#bib-DCAT">DCAT</a>
+ </cite>
+ ] for describing so-called
+
+ <em>Semantic Assets</em>
+ (or just 'Assets'), that is, highly reusable metadata (e.g. xml schemata,
generic data models) and reference data (e.g. code lists, taxonomies, dictionaries,
-vocabularies) that are used for eGovernment system development [[TOGD]]. Someone searching for an Asset
+vocabularies) that are used for eGovernment system development [
+ <cite>
+ <a class="bibref" href="#bib-TOGD">TOGD</a>
+ </cite>
+ ]. Someone searching for an Asset
is likely to have different needs, priorities and expectations
than someone searching for a dataset in a data catalog and these differences are reflected in ADMS.
-In particular, users seeking an Asset are likely to be searching for a document — something they
+In particular, users seeking an Asset are likely to be searching for a document — something they
can open and read using familiar desktop software, as opposed to something that needs to be processed.
Of course this is a very broad generalization. If a code list is published as a SKOS Concept scheme then it is both an Asset
and a dataset and it can be argued that all Assets are datasets. Therefore the difference in
-<em>user expectation</em> is at the heart of what distinguishes ADMS as a profile of DCAT. A further distinction
-between DCAT and ADMS can be made in that DCAT is <em>designed to facilitate interoperability between data catalogs</em>,
-i.e. the catalog itself is at the heart of the vocabulary. ADMS is focused on the assets within a catalog.</p>
-
-</section>
-
-<section id="conformance">
-
-<p>A data interchange, however that interchange occurs, is conformant with ADMS if:</p>
-<ul>
- <li>it uses terms (classes and properties) from ADMS in a way consistent with their semantics as defined in this specification;</li>
- <li>it does <strong>not</strong> use terms from other vocabularies <strong>instead</strong> of ones defined
- in this vocabulary that could reasonably be used (use of such terms in <strong>addition</strong> to ADMS is permissible)..</li>
-</ul>
-
-<p>A conforming data interchange:</p>
-<ul>
- <li><em class="rfc2119" title="may">may</em> include terms from other vocabularies;</li>
- <li><em class="rfc2119" title="may">may</em> use only a subset of ADMS terms.</li>
-</ul>
-
-<p>An <strong>ADMS profile</strong> is a specification for data interchange that adds additional constraints. Such additional
- constraints in a profile <em class="rfc2119" title="may">may</em>
- include (but are not limited to):</p>
-<ul>
- <li>a minimum set of required terms;</li>
- <li>classes and properties for additional terms not covered in ADMS;</li>
- <li>controlled vocabularies or URI sets as acceptable values for properties;</li>
- <li>specific concrete protocols, formats, and syntaxes.</li>
-</ul>
-<p>ADMS is technology-neutral and a publisher may use any of the terms defined in this
+ <em>user expectation</em>
+ is at the heart of what distinguishes ADMS as a profile of DCAT. A further distinction
+between DCAT and ADMS can be made in that DCAT is
+ <em>designed to facilitate interoperability between data catalogs</em>
+ ,
+i.e. the catalog itself is at the heart of the vocabulary. ADMS is focused on the assets within a catalog.
+ </p>
+ </div>
+ <div id="conformance" class="section">
+ <!--OddPage-->
+ <h2>
+ <span class="secno">2. </span>
+ Conformance
+ </h2>
+ <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" title="must">must</em>
+ ,
+ <em class="rfc2119" title="must not">must not</em>
+ ,
+ <em class="rfc2119" title="required">required</em>
+ ,
+ <em class="rfc2119" title="should">should</em>
+ ,
+ <em class="rfc2119" title="should not">should not</em>
+ ,
+ <em class="rfc2119" title="recommended">recommended</em>
+ ,
+ <em class="rfc2119" title="may">may</em>
+ , and
+ <em class="rfc2119" title="optional">optional</em>
+ in this specification are to be interpreted as described in [
+ <cite>
+ <a class="bibref" href="#bib-RFC2119">RFC2119</a>
+ </cite>
+ ].
+ </p>
+ <p>A data interchange, however that interchange occurs, is conformant with ADMS if:</p>
+ <ul>
+ <li>it uses terms (classes and properties) from ADMS in a way consistent with their semantics as defined in this specification;</li>
+ <li>
+ it does
+ <strong>not</strong>
+ use terms from other vocabularies
+ <strong>instead</strong>
+ of ones defined
+ in this vocabulary that could reasonably be used (use of such terms in
+ <strong>addition</strong>
+ to ADMS is permissible)..
+ </li>
+ </ul>
+ <p>A conforming data interchange:</p>
+ <ul>
+ <li>
+ <em class="rfc2119" title="may">may</em>
+ include terms from other vocabularies;
+ </li>
+ <li>
+ <em class="rfc2119" title="may">may</em>
+ use only a subset of ADMS terms.
+ </li>
+ </ul>
+ <p>
+ An
+ <strong>ADMS profile</strong>
+ is a specification for data interchange that adds additional constraints. Such additional
+ constraints in a profile
+ <em class="rfc2119" title="may">may</em>
+
+ include (but are not limited to):
+ </p>
+ <ul>
+ <li>a minimum set of required terms;</li>
+ <li>classes and properties for additional terms not covered in ADMS;</li>
+ <li>controlled vocabularies or URI sets as acceptable values for properties;</li>
+ <li>specific concrete protocols, formats, and syntaxes.</li>
+ </ul>
+ <p>ADMS is technology-neutral and a publisher may use any of the terms defined in this
document encoded in any technology although RDF and XML are preferred.</p>
-
-</section>
-
-<section class="informative">
-<h2 id="ns">Namespaces</h2>
-<p>The namespace for ADMS is <code>http://www.w3.org/ns/adms#</code>. However,
+ </div>
+ <div class="informative section" id="namespaces-1">
+ <!--OddPage-->
+ <h2 id="ns">
+ <span class="secno">3. </span>
+ Namespaces
+ </h2>
+ <p>
+ <em>This section is non-normative.</em>
+ </p>
+ <p>
+ The namespace for ADMS is
+ <code>http://www.w3.org/ns/adms#</code>
+ . However,
it should be noted that ADMS makes extensive use of terms from other vocabularies,
-in particular Dublin Core [[!DC11]]. It re-uses and subclasses DCAT wherever possible
+in particular Dublin Core [
+ <cite>
+ <a class="bibref" href="#bib-DC11">DC11</a>
+ </cite>
+ ]. It re-uses and subclasses DCAT wherever possible
and therefore defines a minimal set of classes and properties of its own.
-A full set of namespaces and prefixes used in this document is shown in the table below.</p>
-
-<table id="namespaces">
- <thead><tr><th>Prefix</th><th>Namespace</th></tr></thead>
- <tbody>
- <tr><td>adms</td><td>http://www.w3.org/ns/adms#</td></tr>
- <tr><td>dcat</td><td>http://www.w3.org/ns/dcat#</td></tr>
- <tr><td>dcterms</td><td>http://purl.org/dc/terms/</td></tr>
- <tr><td>foaf </td><td>http://xmlns.com/foaf/0.1/</td></tr>
- <tr><td>schema </td><td>http://schema.org/</td></tr>
- <tr><td>rdfs</td><td>http://www.w3.org/2000/01/rdf-schema#</td></tr>
- <tr><td>skos </td><td>http://www.w3.org/2004/02/skos/core#</td></tr>
- <tr><td>v</td><td>http://www.w3.org/2006/vcard/ns#</td></tr>
- <tr><td>wdrs</td><td>http://www.w3.org/2007/05/powder-s#</td></tr>
- <tr><td>xhv </td><td>http://www.w3.org/1999/xhtml/vocab#</td></tr>
- </tbody>
-</table>
-</section>
-
-<section class="informative">
-<h2 id="overview">Vocabulary Overview</h2>
-<p>ADMS is intended as a model that facilitates federation and co-operation.
+A full set of namespaces and prefixes used in this document is shown in the table below.
+ </p>
+ <table id="namespaces">
+ <thead>
+ <tr>
+ <th>Prefix</th>
+ <th>Namespace</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>adms</td>
+ <td>http://www.w3.org/ns/adms#</td>
+ </tr>
+ <tr>
+ <td>dcat</td>
+ <td>http://www.w3.org/ns/dcat#</td>
+ </tr>
+ <tr>
+ <td>dcterms</td>
+ <td>http://purl.org/dc/terms/</td>
+ </tr>
+ <tr>
+ <td>foaf </td>
+ <td>http://xmlns.com/foaf/0.1/</td>
+ </tr>
+ <tr>
+ <td>schema </td>
+ <td>http://schema.org/</td>
+ </tr>
+ <tr>
+ <td>rdfs</td>
+ <td>http://www.w3.org/2000/01/rdf-schema#</td>
+ </tr>
+ <tr>
+ <td>skos </td>
+ <td>http://www.w3.org/2004/02/skos/core#</td>
+ </tr>
+ <tr>
+ <td>v</td>
+ <td>http://www.w3.org/2006/vcard/ns#</td>
+ </tr>
+ <tr>
+ <td>wdrs</td>
+ <td>http://www.w3.org/2007/05/powder-s#</td>
+ </tr>
+ <tr>
+ <td>xhv </td>
+ <td>http://www.w3.org/1999/xhtml/vocab#</td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div class="informative section" id="vocabulary-overview">
+ <!--OddPage-->
+ <h2 id="overview">
+ <span class="secno">4. </span>
+ Vocabulary Overview
+ </h2>
+ <p>
+ <em>This section is non-normative.</em>
+ </p>
+ <p>
+ ADMS is intended as a model that facilitates federation and co-operation.
Like DCAT, ADMS has the concepts of a repository (catalog), assets within the repository
that are often conceptual in nature, and accessible realizations of those assets, known
-as distributions. An asset may have zero or multiple distributions. As an example, a W3C namespace document
+as distributions. An asset may have zero or multiple distributions. As an example, a
+ <abbr title="World Wide Web Consortium">W3C</abbr>
+ namespace document
can be considered to be a Semantic Asset that is typically available in multiple distributions, typically one
or more machine processable versions and one in HTML for human consumption. An asset without any distributions
-is effectively a concept with no tangible realization, such as a planned output of a working group that has not yet been drafted.</p>
-<p>ADMS is an RDF vocabulary with an RDF schema available at its namespace <a href="http://www.w3.org/ns/adms">http://www.w3.org/ns/adms</a>.
-The original ADMS specification published by the European Commission [[ADMS1]] includes an XML schema that also defines
-all the controlled vocabularies and cardinality constraints associated with the original document.</p>
-
-<section>
-<h2 id="example">Example</h2>
-<p>This example provides a quick overview of how ADMS might be used to represent a Semantic Asset Repository and its assets.</p>
-<p>Examples in this document are serialized in <a href="http://www.w3.org/TR/turtle/">Turtle</a>.</p>
-<p>First, the repository description:</p>
-
-<pre id="sarEg">:Repository a adms:AssetRepository ;
+is effectively a concept with no tangible realization, such as a planned output of a working group that has not yet been drafted.
+ </p>
+ <p>
+ ADMS is an RDF vocabulary with an RDF schema available at its namespace
+ <a href="http://www.w3.org/ns/adms">http://www.w3.org/ns/adms</a>
+ .
+The original ADMS specification published by the European Commission [
+ <cite>
+ <a class="bibref" href="#bib-ADMS1">ADMS1</a>
+ </cite>
+ ] includes an XML schema that also defines
+all the controlled vocabularies and cardinality constraints associated with the original document.
+ </p>
+ <div id="example-1" class="section">
+ <h3 id="example">
+ <span class="secno">4.1 </span>
+ Example
+ </h3>
+ <p>This example provides a quick overview of how ADMS might be used to represent a Semantic Asset Repository and its assets.</p>
+ <p>
+ Examples in this document are serialized in
+ <a href="http://www.w3.org/TR/turtle/">Turtle</a>
+ .
+ </p>
+ <p>First, the repository description:</p>
+ <pre id="sarEg">:Repository a adms:AssetRepository ;
dcterms:created "1947-02-07"^^xsd:date ;
dcterms:description "A complete catalog of code lists and standards created by the Exemplary Standards Body"@en ;
- dcterms:publisher <http://example.com/data#org> ;
+ dcterms:publisher <http://example.com/data#org> ;
dcterms:title "The Exemplary Standards Body Catalog"@en .</pre>
-
-<p>This assumes that the Exemplary Standards Body is described at <code>http://example.com/data#org</code>.</p>
-
-<p>Next, an Asset. We'll create an imaginary code list called 'Fruit I like' for our example:</p>
-<ul>
- <li>apples</li>
- <li>pears</li>
- <li>oranges</li>
- <li>peaches</li>
-</ul>
-<p>We might describe this Asset thus:</p>
-<pre id="saEg">
-1 :Fruit_02 a adms:Asset ;
+ <p>
+ This assumes that the Exemplary Standards Body is described at
+ <code>http://example.com/data#org</code>
+ .
+ </p>
+ <p>Next, an Asset. We'll create an imaginary code list called 'Fruit I like' for our example:</p>
+ <ul>
+ <li>apples</li>
+ <li>pears</li>
+ <li>oranges</li>
+ <li>peaches</li>
+ </ul>
+ <p>We might describe this Asset thus:</p>
+ <pre id="saEg">1 :Fruit_02 a adms:Asset ;
2 dcterms:created "1999-05-24" ;
3 dcterms:description "Fruits that are found to be generally liked by most people." ;
-4 dcterms:publisher <http://example.com/data#org> ;
+4 dcterms:publisher <http://example.com/data#org> ;
5 dcterms:title "Fruit I like"@en ;
-6 adms:status <http://purl.org/adms/status/Completed> ;
-7 dcterms:type <http://purl.org/adms/assettype/CodeList> ;
+6 adms:status <http://purl.org/adms/status/Completed> ;
+7 dcterms:type <http://purl.org/adms/assettype/CodeList> ;
8 adms:previous :Fruit_01 ;
9 adms:last :Fruit ;
10 dcat:distribution :Fruit_02.csv ;
11 dcat:distribution :Fruit_02.xml .</pre>
-
-<p>This provides the creation date (line 2), description (line 3),
+ <p>
+ This provides the creation date (line 2), description (line 3),
publisher (line 4) and a title (line 5) for the Asset.
The status of the Asset is given in line 6 using one of the values made available in the original ADMS
-specification [[ADMS1]]. Likewise the type of Asset in line 7. In line 8 we can see that there was a previous
-version of this asset (Fruit_01) and that the latest version can be found by appending 'Fruit' to the data's root (line 9).</p>
-<p>This Asset has two distributions linked in lines 11 and 12. One of these might be described thus:</p>
-
-<pre id="sadEg">
-:Fruit_02.xml a adms:AssetDistribution ;
+specification [
+ <cite>
+ <a class="bibref" href="#bib-ADMS1">ADMS1</a>
+ </cite>
+ ]. Likewise the type of Asset in line 7. In line 8 we can see that there was a previous
+version of this asset (Fruit_01) and that the latest version can be found by appending 'Fruit' to the data's root (line 9).
+ </p>
+ <p>This Asset has two distributions linked in lines 11 and 12. One of these might be described thus:</p>
+ <pre id="sadEg">:Fruit_02.xml a adms:AssetDistribution ;
dcterms:description "XML encoding of Fruits that are found to be generally liked by most people." ;
- dcterms:license <http://creativecommons.org/licenses/by/3.0/> ;
- dcterms:format <http://purl.org/NET/mediatypes/application/xml> .</pre>
-
-<p>This is a very simple description of the Asset Distribution that just gives its
+ dcterms:license <http://creativecommons.org/licenses/by/3.0/> ;
+ dcterms:format <http://purl.org/NET/mediatypes/application/xml> .</pre>
+ <p>
+ This is a very simple description of the Asset Distribution that just gives its
description, format, and license. In this example we've used Ed Summers' media types application to
-provide a URI for the XML MIME type [[EDSU]]</p>
-<p>The missing triple from this example is the one that includes the Asset in the Repository. This is done with a simple triple:</p>
-
-<pre id="saDsl">
-:Repository dcat:dataset :Fruit_02 .
+provide a URI for the XML MIME type [
+ <cite>
+ <a class="bibref" href="#bib-EDSU">EDSU</a>
+ </cite>
+ ]
+ </p>
+ <p>The missing triple from this example is the one that includes the Asset in the Repository. This is done with a simple triple:</p>
+ <pre id="saDsl">:Repository dcat:dataset :Fruit_02 .
</pre>
-
-
-</section> <!-- Example -->
-</section> <!-- Overview -->
-
-<section>
-<h2 id="domainmodel">The ADMS Domain Model</h2>
-
-<figure id="uml">
- <img src="adms20130520.png" width="838" height="575" alt="UML Diagram of ADMS" />
- <figcaption>UML model of ADMS classes and properties</figcaption>
-</figure>
-
-<p>The classes and properties are described in the following sub-sections</p>
-<section>
-<h3 id="primary">The Primary Concepts</h3>
-<section>
- <h4 id="pc_AssetRepository">Asset Repository</h4>
- <p><code class="rdfEncoding">adms:AssetRepository</code><br />A system or service that provides facilities for storage and maintenance of
+ </div>
+ <!-- Example -->
+ </div>
+ <!-- Overview -->
+ <div id="the-adms-domain-model" class="section">
+ <!--OddPage-->
+ <h2 id="domainmodel">
+ <span class="secno">5. </span>
+ The ADMS Domain Model
+ </h2>
+ <figure id="uml">
+ <img src="adms20130520.png" width="838" height="575" alt="UML Diagram of ADMS">
+ <figcaption>UML model of ADMS classes and properties</figcaption>
+ </figure>
+ <p>The classes and properties are described in the following sub-sections</p>
+ <div id="the-primary-concepts" class="section">
+ <h3 id="primary">
+ <span class="secno">5.1 </span>
+ The Primary Concepts
+ </h3>
+ <div id="asset-repository" class="section">
+ <h4 id="pc_AssetRepository">
+ <span class="secno">5.1.1 </span>
+ Asset Repository
+ </h4>
+ <p>
+ <code class="rdfEncoding">adms:AssetRepository</code>
+ <br>
+ A system or service that provides facilities for storage and maintenance of
descriptions of Assets and Asset Distributions, and
functionality that allows users to search and access these descriptions. An
- Asset Repository will typically contain descriptions of several Assets and related Asset Distributions.</p>
- <p><code>adms:AssetRepository</code> is a sub class of <code>dcat:Catalog</code></p>
-</section>
-
-<section>
- <h4 id="pc_Asset">Asset</h4>
- <p><code class="rdfEncoding">adms:Asset</code><br />
+ Asset Repository will typically contain descriptions of several Assets and related Asset Distributions.
+ </p>
+ <p>
+ <code>adms:AssetRepository</code>
+ is a sub class of
+ <code>dcat:Catalog</code>
+ </p>
+ </div>
+ <div id="asset" class="section">
+ <h4 id="pc_Asset">
+ <span class="secno">5.1.2 </span>
+ Asset
+ </h4>
+ <p>
+ <code class="rdfEncoding">adms:Asset</code>
+ <br>
+
An abstract entity that reflects the intellectual content of the asset and
represents those characteristics of the asset that are independent of its physical
- embodiment. This abstract entity combines the FRBR entities <em>work</em> (a distinct
- intellectual or artistic creation) and <em>expression</em> (the intellectual or artistic realization of a work) [[FRBR]].
- <p>Assets can be versioned. Every time the intellectual content of an asset changes, the result is considered to
+ embodiment. This abstract entity combines the FRBR entities
+ <em>work</em>
+ (a distinct
+ intellectual or artistic creation) and
+ <em>expression</em>
+ (the intellectual or artistic realization of a work) [
+ <cite>
+ <a class="bibref" href="#bib-FRBR">FRBR</a>
+ </cite>
+ ].
+
+ </p>
+ <p>Assets can be versioned. Every time the intellectual content of an asset changes, the result is considered to
be a new asset that can be linked to previous and next versions of the Asset.</p>
- <p>The physical embodiment of an Asset is called an Asset Distribution. A particular Asset may have zero or more Distributions.</p>
- <p><code>adms:Asset</code> is a sub class of <code>dcat:Dataset</code></p>
- <p>Assets are included in Repositories using DCAT's <code>dcat:dataset</code> property.</p>
-</section>
-<section>
- <h4 id="pc_AssetDistribution">Asset Distribution</h4>
- <p><code class="rdfEncoding">adms:AssetDistribution</code><br />
+ <p>The physical embodiment of an Asset is called an Asset Distribution. A particular Asset may have zero or more Distributions.</p>
+ <p>
+ <code>adms:Asset</code>
+ is a sub class of
+ <code>dcat:Dataset</code>
+ </p>
+ <p>
+ Assets are included in Repositories using DCAT's
+ <code>dcat:dataset</code>
+ property.
+ </p>
+ </div>
+ <div id="asset-distribution-1" class="section">
+ <h4 id="pc_AssetDistribution">
+ <span class="secno">5.1.3 </span>
+ Asset Distribution
+ </h4>
+ <p>
+ <code class="rdfEncoding">adms:AssetDistribution</code>
+ <br>
+
A particular physical embodiment of an Asset, which is an example of
- the FRBR <em>entity manifestation</em> (the physical embodiment of an expression of a work).</p>
- <p>A Distribution is typically a downloadable computer file (but in principle it
+ the FRBR
+ <em>entity manifestation</em>
+ (the physical embodiment of an expression of a work).
+ </p>
+ <p>A Distribution is typically a downloadable computer file (but in principle it
could also be a paper document or API response) that implements the intellectual content of an Asset.</p>
- <p>A particular Distribution is associated with one and only one Asset, while all
+ <p>A particular Distribution is associated with one and only one Asset, while all
Distributions of an Asset share the same intellectual content in different physical formats.</p>
- <p>Distributions themselves are not versioned. If Distribution 1A is the manifestation of Asset 1
+ <p>Distributions themselves are not versioned. If Distribution 1A is the manifestation of Asset 1
and Distribution 2A is the manifestation of Asset 2, a version relationship will be expressed
between Asset 1 and Asset 2, not between Distribution 1A and Distribution 2A. For an
illustration of two Assets that each have two Distributions (representations in different formats) see the diagram below.</p>
- <figure id="asset-distribution">
- <img src="asset-distribution.png" width="535" height="161" alt="Diagram showing that Assets are versioned, Distributions are not" />
- <figcaption>The relationship between versioned Assets and their Distributions</figcaption>
- </figure>
- <p><code>adms:AssetDistribution</code> is a sub class of <code>dcat:Distribution</code></p>
- <p>Assets are linked to Asset Distributions using DCAT's <code>dcat:distribution</code> property.</p>
-</section>
-<p>Examples of the relationship between Assets and Asset Distributions are:</p>
-<dl>
- <dt>An Asset without an Asset Distribution</dt>
- <dd>Even before an Asset is finalized, a description of what it will be can often be made; for example, a description of
+ <figure id="asset-distribution">
+ <img src="asset-distribution.png" width="535" height="161" alt="Diagram showing that Assets are versioned, Distributions are not">
+ <figcaption>The relationship between versioned Assets and their Distributions</figcaption>
+ </figure>
+ <p>
+ <code>adms:AssetDistribution</code>
+ is a sub class of
+ <code>dcat:Distribution</code>
+ </p>
+ <p>
+ Assets are linked to Asset Distributions using DCAT's
+ <code>dcat:distribution</code>
+ property.
+ </p>
+ </div>
+ <p>Examples of the relationship between Assets and Asset Distributions are:</p>
+ <dl>
+ <dt>An Asset without an Asset Distribution</dt>
+ <dd>Even before an Asset is finalized, a description of what it will be can often be made; for example, a description of
it can be written, the publisher is already known as is the language. A link to
the distribution, the physical document, can only be made when the work is done;
until that time, the Asset will have no Distribution associated with it.</dd>
- <dt>An Asset and Asset Distribution embedded in a single file</dt>
- <dd>Some Assets, such as technical specifications, have some characteristics that are related to the
+ <dt>An Asset and Asset Distribution embedded in a single file</dt>
+ <dd>
+ Some Assets, such as technical specifications, have some characteristics that are related to the
intellectual content such as its description, its language and its version, and
some characteristics that are related to the file itself such as its location (if its identifier is not a URL),
- its format and the usage conditions. In such cases, a single entity is <em>both</em> an Asset <em>and</em>
- an Asset Distribution. Even so, best practice is to assert the Asset → Asset Distribution relationship (i.e.
- to point to itself) so that queries looking for that relationship will still return a result.<dd>
- <dt>An Asset with multiple Asset Distributions</dt>
- <dd>It is common for a single work to be expressed in multiple formats. For example, RDF documents are
+ its format and the usage conditions. In such cases, a single entity is
+ <em>both</em>
+ an Asset
+ <em>and</em>
+
+ an Asset Distribution. Even so, best practice is to assert the Asset → Asset Distribution relationship (i.e.
+ to point to itself) so that queries looking for that relationship will still return a result.
+ </dd>
+ <dd>
+ </dd>
+ <dt>An Asset with multiple Asset Distributions</dt>
+ <dd>It is common for a single work to be expressed in multiple formats. For example, RDF documents are
often serialized in RDF/XML, Turtle and triples, each of which would be a discrete Distribution.</dd>
-</dl>
-</section> <!-- Primary Concepts -->
-
-<section>
-<h3 id="secondary">The Secondary Concepts</h3>
-<p>In addition to the primary concepts, ADMS includes a number of secondary or supporting concepts:</p>
-<section><h4 id="sec_assetType">Asset Type</h4>
- <p><code class="rdfEncoding">skos:Concept</code><br />
- The classification of an Asset according to a controlled vocabulary, e.g. code list, metadata schema. Use <code><a href="#dcterms_type">dcterms:type</a></code> to link an Asset to an Asset Type.</p>
-</section>
-<section>
-<h4 id="sec_contactInformation">Contact Information</h4>
- <p><code class="rdfEncoding">v:VCard</code><br />
- A contact point for further information about an Asset. Use <code><a href="#dcat_contactPoint">dcat:contactPoint</a></code> to link an Asset to a VCard.</p>
-</section>
-<section>
- <h4 id="sec_documentation">Documentation</h4>
- <p><code class="rdfEncoding">foaf:Document</code><br />
- Any document that further describes an Asset or gives guidelines for its use. See
- <code><a href="#dcat_landingPage">dcat:landingPage</a></code>, <code><a href="#wdrs_describedby">wdrs:describedby</a></code>
- <code><a href="#adms_relatedDocumentation">adms:relatedDocumentation</a></code> and <code><a href="#adms_relatedWebPage">adms:relatedWebPage</a></code>.</p>
-</section>
-<section>
- <h4 id="sec_fileFormat">File Format</h4>
- <p><code class="rdfEncoding">dcterms:FileFormat</code><br />
+ </dl>
+ </div>
+ <!-- Primary Concepts -->
+ <div id="the-secondary-concepts" class="section">
+ <h3 id="secondary">
+ <span class="secno">5.2 </span>
+ The Secondary Concepts
+ </h3>
+ <p>In addition to the primary concepts, ADMS includes a number of secondary or supporting concepts:</p>
+ <div id="asset-type" class="section">
+ <h4 id="sec_assetType">
+ <span class="secno">5.2.1 </span>
+ Asset Type
+ </h4>
+ <p>
+ <code class="rdfEncoding">skos:Concept</code>
+ <br>
+
+ The classification of an Asset according to a controlled vocabulary, e.g. code list, metadata schema. Use
+ <code>
+ <a href="#dcterms_type">dcterms:type</a>
+ </code>
+ to link an Asset to an Asset Type.
+ </p>
+ </div>
+ <div id="contact-information" class="section">
+ <h4 id="sec_contactInformation">
+ <span class="secno">5.2.2 </span>
+ Contact Information
+ </h4>
+ <p>
+ <code class="rdfEncoding">v:VCard</code>
+ <br>
+
+ A contact point for further information about an Asset. Use
+ <code>
+ <a href="#dcat_contactPoint">dcat:contactPoint</a>
+ </code>
+ to link an Asset to a VCard.
+ </p>
+ </div>
+ <div id="documentation" class="section">
+ <h4 id="sec_documentation"><span class="secno">5.2.3 </span>Documentation</h4>
+ <p><code class="rdfEncoding">foaf:Document</code><br/>
+ Any document that further describes an Asset or gives guidelines for its use. See
+ <code><a href="#dcat_landingPage">dcat:landingPage</a></code>,
+ <code><a href="#wdrs_describedby">wdrs:describedby</a></code> and
+ <code><a href="#foaf_page">foaf:page</a></code>.</p>
+ </div>
+ <div id="file-format" class="section">
+ <h4 id="sec_fileFormat">
+ <span class="secno">5.2.4 </span>
+ File Format
+ </h4>
+ <p>
+ <code class="rdfEncoding">dcterms:FileFormat</code>
+ <br>
+
The technical format in which a Distribution is available, e.g.
- <abbr title="Portable Document Format">PDF</abbr>, <abbr title="XML Schema Definition">XSD</abbr> etc.
- See also <a href="#sec_representationTechnique">representation technique</a>, <code><a href="#dcterms_format">dcterms:format</a></code> and <code><a href="#dcat_mediaType">dcat:mediaType</a></code>.</p>
-</section>
-<section>
- <h4 id="sec_geographicalCoverage">Geographical Coverage</h4>
- <p><code class="rdfEncoding">dcterms:Location</code><br />
- The country or region to which an Asset or Repository applies, linked using <code><a href="#dcterms_spatial">dcterms:spatial</a></code>.</p>
-</section>
-<section>
- <h4 id="dt_identifier">Identifier</h4>
- <p><code class="rdfEncoding">adms:Identifier</code><br />
- This is based on the UN/CEFACT Identifier class. [[UNCEFACT]]) which consists of:</p><ul>
- <li>a content string which is the identifier;</li>
- <li>an optional identifier for the identifier scheme;</li>
- <li>an optional identifier for the version of the identifier scheme;</li>
- <li>an optional identifier for the agency that manages the identifier scheme.</li></ul>
-
- <p>In ADMS this is expressed using the <code>adms:Identifier</code> class with the following properties:</p><ul>
- <li>the content string should be provided using <code><a href="#skos_notation">skos:notation</a></code>, datatyped with
- the identifier scheme (including the version number if appropriate);</li>
- <li>use <code><a href="#dcterms_creator">dcterms:creator</a></code> to link to a class that represents the agency that manages the identifier scheme and/or
- <code><a href="#adms_schemaAgency">adms:schemaAgency</a></code> to provide the name of the agency as a literal;</li>
- <li>it may also be useful to provide further properties such as <code><a href="#dcterms_issued">dcterms:issued</a></code> to provide the
- date on which the identifier was issued.</li></ul>
- <p>An important point to note is that properties of <code>adms:Identifier</code> are properties of the
- Identifier, not the resource that it identifies or the agency that issued it.</p>
-</section>
-
-<!-- <dt id="sec_item">Item <code class="rdfEncoding">adms:Item</code></dt>
+
+ <abbr title="Portable Document Format">PDF</abbr>
+ ,
+ <abbr title="XML Schema Definition">XSD</abbr>
+ etc.
+ See also
+ <a href="#sec_representationTechnique">representation technique</a>
+ ,
+ <code>
+ <a href="#dcterms_format">dcterms:format</a>
+ </code>
+ and
+ <code>
+ <a href="#dcat_mediaType">dcat:mediaType</a>
+ </code>
+ .
+ </p>
+ </div>
+ <div id="geographical-coverage" class="section">
+ <h4 id="sec_geographicalCoverage">
+ <span class="secno">5.2.5 </span>
+ Geographical Coverage
+ </h4>
+ <p>
+ <code class="rdfEncoding">dcterms:Location</code>
+ <br>
+
+ The country or region to which an Asset or Repository applies, linked using
+ <code>
+ <a href="#dcterms_spatial">dcterms:spatial</a>
+ </code>
+ .
+ </p>
+ </div>
+ <div id="identifier" class="section">
+ <h4 id="dt_identifier">
+ <span class="secno">5.2.6 </span>
+ Identifier
+ </h4>
+ <p>
+ <code class="rdfEncoding">adms:Identifier</code>
+ <br>
+
+ This is based on the UN/CEFACT Identifier class. [
+ <cite>
+ <a class="bibref" href="#bib-UNCEFACT">UNCEFACT</a>
+ </cite>
+ ]) which consists of:
+ </p>
+ <ul>
+ <li>a content string which is the identifier;</li>
+ <li>an optional identifier for the identifier scheme;</li>
+ <li>an optional identifier for the version of the identifier scheme;</li>
+ <li>an optional identifier for the agency that manages the identifier scheme.</li>
+ </ul>
+ <p>
+ In ADMS this is expressed using the
+ <code>adms:Identifier</code>
+ class with the following properties:
+ </p>
+ <ul>
+ <li>
+ the content string should be provided using
+ <code>
+ <a href="#skos_notation">skos:notation</a>
+ </code>
+ , datatyped with
+ the identifier scheme (including the version number if appropriate);
+ </li>
+ <li>
+ use
+ <code>
+ <a href="#dcterms_creator">dcterms:creator</a>
+ </code>
+ to link to a class that represents the agency that manages the identifier scheme and/or
+
+ <code>
+ <a href="#adms_schemaAgency">adms:schemaAgency</a>
+ </code>
+ to provide the name of the agency as a literal;
+ </li>
+ <li>
+ it may also be useful to provide further properties such as
+ <code>
+ <a href="#dcterms_issued">dcterms:issued</a>
+ </code>
+ to provide the
+ date on which the identifier was issued.
+ </li>
+ </ul>
+ <p>
+ An important point to note is that properties of
+ <code>adms:Identifier</code>
+ are properties of the
+ Identifier, not the resource that it identifies or the agency that issued it.
+ </p>
+ </div>
+ <!-- <dt id="sec_item">Item <code class="rdfEncoding">adms:Item</code></dt>
<dd><p>An item that is contained inside an Asset, e.g. an individual term in a vocabulary, an individual code in a code list or some other ‘atomic’ element of an Asset.</p></dd> -->
-<section>
- <h4 id="sec_interoperabilityLevel">Interoperability Level</h4>
- <p><code class="rdfEncoding">skos:Concept</code><br />
+ <div id="interoperability-level" class="section">
+ <h4 id="sec_interoperabilityLevel">
+ <span class="secno">5.2.7 </span>
+ Interoperability Level
+ </h4>
+ <p>
+ <code class="rdfEncoding">skos:Concept</code>
+ <br>
+
The interoperability level (e.g. legal, organizational, political etc.) of the Asset,
- linked using <code><a href="#adms_interoperabilityLevel">adms:interoperabilityLevel</a></code>. The
+ linked using
+ <code>
+ <a href="#adms_interoperabilityLevel">adms:interoperabilityLevel</a>
+ </code>
+ . The
interoperability level may be taken from a list of levels such as that of the European Interoperability
- Framework [[EIF2]].</p>
-</section>
-<section>
- <h4 id="sec_language">Language</h4>
- <p><code class="rdfEncoding">dcterms:LinguisticSystem</code><br />
+ Framework [
+ <cite>
+ <a class="bibref" href="#bib-EIF2">EIF2</a>
+ </cite>
+ ].
+ </p>
+ </div>
+ <div id="language" class="section">
+ <h4 id="sec_language">
+ <span class="secno">5.2.8 </span>
+ Language
+ </h4>
+ <p>
+ <code class="rdfEncoding">dcterms:LinguisticSystem</code>
+ <br>
+
The language of an Asset if it contains textual information, e.g. the language of the terms in a controlled vocabulary or
- the language in which a specification is written, linked using <code><a href="#dcterms_language">dcterms:language</a></code></p>
-</section>
-<section>
- <h4 id="sec_license">License</h4>
- <p><code class="rdfEncoding">dcterms:LicenseDocument</code><br />
+ the language in which a specification is written, linked using
+ <code>
+ <a href="#dcterms_language">dcterms:language</a>
+ </code>
+ </p>
+ </div>
+ <div id="license" class="section">
+ <h4 id="sec_license">
+ <span class="secno">5.2.9 </span>
+ License
+ </h4>
+ <p>
+ <code class="rdfEncoding">dcterms:LicenseDocument</code>
+ <br>
+
The conditions or restrictions that apply to the use of a Distribution, e.g. whether it is in the
public domain, or that some restrictions apply such as attribution being required, or that it can only be
- used for non-commercial purposes etc. Linked using <code><a href="#dcterms_license">dcterms:license</a></code></p>
-</section>
-<section>
- <h4 id="sec_periodOfTime">Period of time</h4>
- <p><code class="rdfEncoding">dcterms:PeriodOfTime</code><br />
+ used for non-commercial purposes etc. Linked using
+ <code>
+ <a href="#dcterms_license">dcterms:license</a>
+ </code>
+ </p>
+ </div>
+ <div id="period-of-time" class="section">
+ <h4 id="sec_periodOfTime">
+ <span class="secno">5.2.10 </span>
+ Period of time
+ </h4>
+ <p>
+ <code class="rdfEncoding">dcterms:PeriodOfTime</code>
+ <br>
+
The time period relevant for an Asset, e.g. for its validity. Linked from a Semanmtic Asset using
- <code><a href="#dcterms_temporal">dcterms:temporal</a></code>. The time period can be specified
- using <code><a href="#schema_startDate">schema:startDate</a></code> and <code><a href="#schema_endDate">schema:endDate</a></code>.</p>
-</section>
-<section>
- <h4 id="sec_publisher">Publisher</h4>
- <p><code class="rdfEncoding">dcterms:Agent</code><br />
- The organization making a Repository, Asset or Distribution available, linked using <code><a href="#dcterms_publisher">dcterms:publisher</a></code>.</p>
-</section>
-<section>
- <h4 id="sec_representationTechnique">Representation Technique</h4>
- <p><code class="rdfEncoding">skos:Concept</code><br />
- The machine-readable language in which a Distribution is expressed. This is more fine-grained than <a href="#sec_fileFormat">file format</a>,
- for example "Word 2003", linked using <code><a href="#adms_representationTechnique">representationTechnique</a></code>.
- See also <code><a href="#dcterms_format">dcterms:format</a></code> and <code><a href="#dcat_mediaType">dcat:mediaType</a></code>.</p>
- <p>This concept indicates that one of the files in an Asset Distribution is expressed in the Representation Technique.
+
+ <code>
+ <a href="#dcterms_temporal">dcterms:temporal</a>
+ </code>
+ . The time period can be specified
+ using
+ <code>
+ <a href="#schema_startDate">schema:startDate</a>
+ </code>
+ and
+ <code>
+ <a href="#schema_endDate">schema:endDate</a>
+ </code>
+ .
+ </p>
+ </div>
+ <div id="publisher" class="section">
+ <h4 id="sec_publisher">
+ <span class="secno">5.2.11 </span>
+ Publisher
+ </h4>
+ <p>
+ <code class="rdfEncoding">dcterms:Agent</code>
+ <br>
+
+ The organization making a Repository, Asset or Distribution available, linked using
+ <code>
+ <a href="#dcterms_publisher">dcterms:publisher</a>
+ </code>
+ .
+ </p>
+ </div>
+ <div id="representation-technique" class="section">
+ <h4 id="sec_representationTechnique">
+ <span class="secno">5.2.12 </span>
+ Representation Technique
+ </h4>
+ <p>
+ <code class="rdfEncoding">skos:Concept</code>
+ <br>
+
+ The machine-readable language in which a Distribution is expressed. This is more fine-grained than
+ <a href="#sec_fileFormat">file format</a>
+ ,
+ for example "Word 2003", linked using
+ <code>
+ <a href="#adms_representationTechnique">representationTechnique</a>
+ </code>
+ .
+ See also
+ <code>
+ <a href="#dcterms_format">dcterms:format</a>
+ </code>
+ and
+ <code>
+ <a href="#dcat_mediaType">dcat:mediaType</a>
+ </code>
+ .
+ </p>
+ <p>This concept indicates that one of the files in an Asset Distribution is expressed in the Representation Technique.
There may also be other files in the Distribution that are expressed in other Representation Techniques or even files
that are not representations at all.</p>
-</section>
-<section>
- <h4 id="sec_status">Status</h4>
- <p><code class="rdfEncoding">skos:Concept</code><br />
- An indication of the maturity of an Asset or Distribution, linked using <code><a href="#adms_status">adms:status</a></code>.</p>
-</section>
-<section>
- <h4 id="sec_theme">Theme</h4>
- <p><code class="rdfEncoding">skos:Concept</code><br />
+ </div>
+ <div id="status" class="section">
+ <h4 id="sec_status">
+ <span class="secno">5.2.13 </span>
+ Status
+ </h4>
+ <p>
+ <code class="rdfEncoding">skos:Concept</code>
+ <br>
+
+ An indication of the maturity of an Asset or Distribution, linked using
+ <code>
+ <a href="#adms_status">adms:status</a>
+ </code>
+ .
+ </p>
+ </div>
+ <div id="theme" class="section">
+ <h4 id="sec_theme">
+ <span class="secno">5.2.14 </span>
+ Theme
+ </h4>
+ <p>
+ <code class="rdfEncoding">skos:Concept</code>
+ <br>
+
The sector that an Asset applies to, e.g. "law" or "environment".
Best practice is to use terms from a controlled vocabulary expressed as a SKOS Concept Scheme and linked
- from the Asset using <code><a href="#dcat_theme">dcat:theme</a></code>.</p>
-</section>
-<section>
- <h4 id="sec_themeTaxonomy">Theme Taxonomy</h4>
- <p><code class="rdfEncoding">skos:ConceptScheme</code><br />
+ from the Asset using
+ <code>
+ <a href="#dcat_theme">dcat:theme</a>
+ </code>
+ .
+ </p>
+ </div>
+ <div id="theme-taxonomy" class="section">
+ <h4 id="sec_themeTaxonomy">
+ <span class="secno">5.2.15 </span>
+ Theme Taxonomy
+ </h4>
+ <p>
+ <code class="rdfEncoding">skos:ConceptScheme</code>
+ <br>
+
A controlled vocabulary that contains terms that are used as Themes for the Assets in a Repository,
- linked from the Repository using <code><a href="#dcat_themeTaxonomy">dcat:themeTaxonomy</a></code>.</p>
-</section>
-
-<p><strong>NB</strong> The original ADMS specification supports the provision of a description of
+ linked from the Repository using
+ <code>
+ <a href="#dcat_themeTaxonomy">dcat:themeTaxonomy</a>
+ </code>
+ .
+ </p>
+ </div>
+ <p>
+ <strong>NB</strong>
+ The original ADMS specification supports the provision of a description of
the metadata about an Asset, including its publisher and language (i.e. the human language in which the metadata is expressed,
irrespective of the language used in the Asset itself). The DCAT concept of a Catalog Record can be used for this
-purpose and so is not detailed in this document.</p>
-
-</section> <!-- Secondary Concepts -->
-
-
-<section><h2 id="propertiesAndRelationships">Properties and Relationships</h2>
-<p>In the following sub-sections, we set out the properties and relationships
+purpose and so is not detailed in this document.
+ </p>
+ </div>
+ <!-- Secondary Concepts -->
+ <div id="properties-and-relationships" class="section">
+ <h3 id="propertiesAndRelationships">
+ <span class="secno">5.3 </span>
+ Properties and Relationships
+ </h3>
+ <p>In the following sub-sections, we set out the properties and relationships
(object type properties) used in ADMS. These are listed in alphabetical order, irrespective of namespace.</p>
-
-
-<section>
-<h3 id="dcat_accessURL">dcat:accessURL</h3>
-<p>Any kind of URL that gives access to an Asset Repository or Asset Distribution, e.g. a landing page, download, feed URL, SPARQL endpoint etc.
+ <div id="dcat-accessurl" class="section">
+ <h4 id="dcat_accessURL">
+ <span class="secno">5.3.1 </span>
+ dcat:accessURL
+ </h4>
+ <p>Any kind of URL that gives access to an Asset Repository or Asset Distribution, e.g. a landing page, download, feed URL, SPARQL endpoint etc.
Use dcat:accessURL when you do not have information on which it is or when it is definitely not a download.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/dcat#accessURL">dcat:accessURL</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
- <tr><td class="prop">Usage note</td><td><ul>
- <li>the value is a URL.</li>
- <li>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 title="should" class="rfc2119">should</em> be duplicated as accessURL on a distribution (see also <a href="#dcat_landingPage">dcat:landingPage</a>).</li>
- </ul></td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="skos_altLabel">skos:altLabel</h3>
-<p>An alternative name for the Asset.</p>
-<table class="definition">
- <thead><tr><th>Datatype Property</th><th><a href="http://www.w3.org/2004/02/skos/core#altLabel">skos:altLabel</a></th></tr></thead>
- <tbody><tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr></tbody>
-</table>
-</section>
-
-<section>
-<h3 id="dcat_contactPoint">dcat:contactPoint</h3>
-<p>Links an asset to a contact point from where further information about an Asset can be obtained.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/dcat#contactPoint">dcat:contactPoint</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2006/vcard/ns#">v:VCard</a></td></tr>
- </tbody>
-</table>
-</section>
-
-
-<section>
-<h3 id="dcterms_creator">dcterms:creator</h3>
-<p>Used in ADMS to link an <code><a href="#dt_identifier">adms:Identifier</a></code> to a
- <code><a href="http://dublincore.org/documents/dcmi-terms/#terms-Agent">dcterms:Agent</a></code>
- (equivalent class <code><a href="http://xmlns.com/foaf/spec/#term_Agent">foaf:Agent</a></code>)</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://purl.org/dc/terms/creator">dcterms:creator</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://purl.org/dc/terms/Agent">dcterms:Agent</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="dcat_dataset">dcat:dataset</h3>
-<p>Used to link an Asset Repository to an Asset.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/dcat#dataset">dcat:dataset</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain</td><td><a href="http://www.w3.org/ns/dcat#Catalog">dcat:Catalog</a></td></tr>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/ns/dcat#Dataset">dcat:Dataset</a></td></tr>
- </tbody>
-</table>
-</section>
-
-
-
-<section>
-<h3 id="wdrs_describedby">wdrs:describedby</h3>
-<p>The main documentation or specification of the Asset</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/2007/05/powder-s#describedby">wdrs:describedby</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
- <tr><td class="prop">Usage note</td><td>See also <a href="#dcat_landingPage">dcat:landingPage</a>, <a href="#foaf_page">foaf:page</a> </td></tr>
- </tbody>
-</table>
-</section>
-
-
-<section>
-<h3 id="dcterms_description">dcterms:description</h3>
-<p>A description of the Asset, Asset Repository or Asset Distribution.</p>
-<table class="definition">
- <thead><tr><th>Datatype Property</th><th><a href="http://purl.org/dc/terms/description">dcterms:description</a></th></tr></thead>
- <tbody><tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr></tbody>
-</table>
-</section>
-<section>
-<h3 id="dcat_distribution">dcat:distribution</h3>
-<p>Links an Asset to an implementation in a particular format.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/dcat#distribution">dcat:distribution</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain</td><td><a href="http://www.w3.org/ns/dcat#Dataset">dcat:Dataset</a></td></tr>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/ns/dcat#Distribution">dcat:Distribution</a></td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="dcat_downloadURL">dcat:downloadURL</h3>
-<p>This is a direct link from an Asset Distribution to a downloadable file in a given format, e.g. CSV file or RDF file. The format is described by the distribution's dcterms:format and/or dcat:mediaType.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/dcat#downloadURL">dcat:downloadURL</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>.</td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="schema_endDate">schema:endDate</h3>
-<p>Used in ADMS to define the end of a period of time during which an Asset is valid or applicable.</p>
-<table class="definition">
- <thead><tr><th>Datat Type Property</th><th><a href="http://schema.org/endDate">schema:endDate</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> which should be typed, typically with <code>xsd:date</code>.</td></tr>
- </tbody>
-</table>
-</section>
-
-
-
-<section>
-<h3 id="dcterms_format">dcterms:format</h3>
-<p>The file format of the distribution.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://purl.org/dc/terms/format">dcterms:format</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://purl.org/dc/terms/MediaTypeOrExtent">dcterms:MediaTypeOrExtent</a></td></tr>
- <tr><td class="prop">Usage note</td><td><a href="#dcat_mediaType">dcat:mediaType</a> should be used if the type of the distribution is defined by <a href="http://www.iana.org/assignments/media-types/">IANA</a>.
- Suitable values for <code>dcterms:format</code> include URIs as used in the <a href="#sadEg">example</a>. See also <a href="#adms_representationTechnique">adms:representationTechnique</a>.</td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="adms_identifier">adms:identifier</h3>
-<p>Links a resource to an <code>adms:Identifier</code> class.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#identifier">adms:identifier</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/ns/adms#Identifier">adms:Identifier</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="adms_includedAsset">adms:includedAsset</h3>
-<p>An Asset that is contained in the Asset being described, e.g. when there are several vocabularies defined in a single document.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#includedAsset">adms:includedAsset</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain</td><td><a href="http://www.w3.org/ns/adms#Asset">adms:Asset</a></td></tr>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/ns/adms#Asset">adms:Asset</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="adms_interoperabilityLevel">adms:interoperabilityLevel</h3>
-<p>The interoperability level for which the Asset is relevant.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#interoperabilityLevel">adms:interoperabilityLevel</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain</td><td><a href="http://www.w3.org/ns/adms#Asset">adms:Asset</a></td></tr>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
- </tbody>
-</table>
-</section>
-
-
-<section>
-<h3 id="dcterms_issued">dcterms:issued</h3>
-
-<p>Date of formal issuance (e.g., publication) of the Asset, Asset Repository or Asset Distribution.</p>
-<table class="definition">
- <thead><tr><th>Datatype Property</th><th><a href="http://purl.org/dc/terms/issued">dcterms:issued</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
- using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time</a> compliant string and
- typed using the appropriate XML Schema datatype [[!XMLSCHEMA-2]]</td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="dcat_keyword">dcat:keyword</h3>
-<p>A word, phrase or tag to describe the Asset.</p>
-<table class="definition">
- <thead><tr><th>Datatype Property</th><th><a href="http://www.w3.org/ns/dcat#keyword">dcat:keyword</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="dcat_landingPage">dcat:landingPage</h3>
-<p>A Web page that can be navigated to in a Web browser to gain access to the Asset, its distributions and/or additional information.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/dcat#landingPage">dcat:landingPage</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://xmlns.com/foaf/0.1/Document">foaf:Document</a></td></tr>
- <tr><td class="prop">Usage note</td><td>If the Asset Distribution(s) are accessible only through a landing page (i.e. direct download URLs are not known), then the landing page link should be duplicated as accessURL on a distribution.</td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="dcterms_language">dcterms:language</h3>
-<p>The language of the Asset</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://purl.org/dc/terms/LinguisticSystem">dcterms:LinguisticSystem</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a><br/>
- Resources defined by the Library of Congress (<a href="http://id.loc.gov/vocabulary/iso639-1.html">1</a>, <a href="http://id.loc.gov/vocabulary/iso639-2.html">2</a>)
- <em title="should" class="rfc2119">should</em> be used. <br/>
- If an ISO 639-1 (two-letter) code is defined for language, then its corresponding IRI <em title="should" class="rfc2119">should</em>
- be used; if no ISO 639-1 code is defined, then IRI corresponding to the ISO 639-2 (three-letter) code <em title="should" class="rfc2119">should</em>
- be used.</td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="adms_last">adms:last</h3>
-<p>A link to the current or latest version of the Asset.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#last">adms:last</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Sub property of</td><td><a href="http://www.w3.org/1999/xhtml/vocab#last">xhv:last</a></td></tr>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="dcterms_license">dcterms:license</h3>
-<p>Links to the conditions or restrictions for (re-)use of the Asset Distribution.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://purl.org/dc/terms/license">dcterms:license</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://purl.org/dc/terms/LicenseDocument">dcterms:LicenseDocument</a>.</td></tr>
- <tr><td class="prop">Usage note</td><td>If multiple licenses are given, these licenses apply to all files in the Asset Distribution.</td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="dcat_mediaType">dcat:mediaType</h3>
-<p>The media type of the distribution as defined by <a href="http://www.iana.org/assignments/media-types/">IANA</a>.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/dcat#mediaType">dcat:mediaType</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://purl.org/dc/terms/MediaTypeOrExtent">dcterms:MediaTypeOrExtent</a>.</td></tr>
- <tr><td class="prop">Usage note</td><td>This property <em title="should" class="rfc2119">should</em> be used when the media type of the distribution is defined in
- <a href="http://www.iana.org/assignments/media-types/">IANA</a>, e.g. <code>text/csv</code> otherwise <a href="#dcterms_format">dcterms:format</a> <em title="may" class="rfc2119">may</em> be used with different values.
- See also <a href="#adms_representationTechnique">adms:representationTechnique</a>.</td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="dcterms_modified">dcterms:modified</h3>
-<p>Date of the latest update of the Asset, Asset Repository or Asset Distribution.</p>
-<table class="definition">
- <thead><tr><th>Datatype Property</th><th><a href="http://purl.org/dc/terms/modified">dcterms:modified</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
- using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time</a> compliant string and
- typed using the appropriate XML Schema datatype [[!XMLSCHEMA-2]]</td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="adms_next">adms:next</h3>
-<p>A link to the next version of the Asset.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#next">adms:next</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Sub property of</td><td><a href="http://www.w3.org/1999/xhtml/vocab#next">xhv:next</a></td></tr>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="skos_notation">skos:notation</h3>
-<p>Used in ADMS to provide the actual identifier string as a property of an <a href="#dt_identifier"><code>adms:Identifier</code></a></p>
-<table class="definition">
- <thead><tr><th>Data Type Property</th><th><a href="http://www.w3.org/2004/02/skos/core#">skos:notation</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> which should be typed.</td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="adms_prev">adms:prev</h3>
-<p>A link to the previous version of the Asset.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#prev">adms:prev</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Sub property of</td><td><a href="http://www.w3.org/1999/xhtml/vocab#prev">xhv:prev</a></td></tr>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="dcterms_publisher">dcterms:publisher</h3>
-<p>Links an Asset, Asset Repository or Asset Distribution to the publishing foaf:Agent.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://purl.org/dc/terms/publisher">dcterms:publisher</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a></td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="foaf_page">foaf:page</h3>
-<p>Links to documentation that contains information related to the Asset.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://xmlns.com/foaf/0.1/page">foaf:page</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://xmlns.com/foaf/0.1/Document">foaf:Document</a></td></tr>
- <tr><td class="prop">Usage note</td><td>See also <a href="#dcat_landingPage">dcat:landingPage</a>, <a href="#wdrs_describedby">wdrs:describedby</a> </td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="dcterms_relation">dcterms:relation</h3>
-<p>A link between two Assets that are related in some (unspecified) way.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://purl.org/dc/terms/relation">dcterms:relation</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="adms_representationTechnique">adms:representationTechnique</h3>
-<p>More information about the format in which an Asset Distribution is released. This is different from the file format as, for example, a ZIP file (file format) could contain an XML schema (representation technique).</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#representationTechnique">adms:representationTechnique</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
- <tr><td class="prop">Usage note</td><td>See also <a href="#dcterms_format">dcterms:format</a> and <a href="#dcat_mediaType">dcat:mediaType</a>.</td></tr>
-
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="adms_sample">adms:sample</h3>
-<p>Links to a sample of an Asset (which is itself an Asset).</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#sample">adms:sample</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/ns/adms#Asset">adms:Asset</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="adms_schemaAgency">adms:schemaAgency</h3>
-<p>The name of the agency that issued the identifier.</p>
-<table class="definition">
- <thead><tr><th>Data Type Property</th><th><a href="http://www.w3.org/ns/adms#schemaAgency">adms:schemaAgency</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Domain</td><td><a href="#dt_identifier">adms:Identifier</a></td></tr>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr>
- </tbody>
-</table>
-</section>
-
-
-
-
-<section>
-<h3 id="dcterms_spatial">dcterms:spatial</h3>
-<p>The geographic region to which the Asset or Asset Repository applies.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://purl.org/dc/terms/spatial">dcterms:spatial</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://purl.org/dc/terms/Location">dcterms:Location</a></td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="schema_startDate">schema:startDate</h3>
-<p>Used in ADMS to define the start of a period of time during which an Asset is valid or applicable.</p>
-<table class="definition">
- <thead><tr><th>Datat Type Property</th><th><a href="http://schema.org/startDate">schema:startDate</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> which should be typed, typically with <code>xsd:date</code>.</td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="adms_status">adms:status</h3>
-<p>The status of the Asset in the context of a particular workflow process.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#status">adms:status</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="adms_supportedSchema">adms:supportedSchema</h3>
-<p>A schema according to which the Asset Repository can provide data about its content, e.g. ADMS.</p>
-<table class="definition">
- <thead><tr><th>Datatype Property</th><th><a href="http://www.w3.org/ns/adms#supportedSchema">adms:supportedSchema</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/ns/adms#Asset">adms:Asset</a></td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="dcterms_temporal">dcterms:temporal</h3>
-<p>The time period to which the Asset applies, e.g. its validity.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://purl.org/dc/terms/temporal">dcterms:temporal</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://purl.org/dc/terms/PeriodOfTime">dcterms:PeriodOfTime</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="dcat_theme">dcat:theme</h3>
-<p>The theme or sector to which the Asset applies.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/dcat#theme">dcat:theme</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Sub property of</td><td><a href="http://purl.org/dc/terms/subject">dcterms:subject</a></td></tr>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="dcat_themeTaxonomy">dcat:themeTaxonomy</h3>
-<p>The SKOS Concept Scheme used to classify an Asset Repository's assets.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/dcat#themeTaxonomy">dcat:themeTaxonomy</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2004/02/skos/core#ConceptScheme">skos:ConceptScheme</a></td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="dcterms_title">dcterms:title</h3>
-<p>A name given to the Asset, Asset Repository or Asset Distribution.</p>
-<table class="definition">
- <thead><tr><th>Datatype Property</th><th><a href="http://purl.org/dc/terms/title">dcterms:title</a></th></tr></thead>
- <tbody><tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr></tbody>
-</table>
-</section>
-<section>
-<h3 id="adms_translation">adms:translation</h3>
-<p>Links Assets that are translations of each other.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://www.w3.org/ns/adms#translation">adms:translation</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a></td></tr>
- </tbody>
-</table>
-</section>
-<section>
-<h3 id="dcterms_type">dcterms:type</h3>
-<p>This property is used to point to the specific type of publisher, Asset and License Document. In each case
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/dcat#accessURL">dcat:accessURL</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Usage note</td>
+ <td>
+ <ul>
+ <li>the value is a URL.</li>
+ <li>
+ 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 title="should" class="rfc2119">should</em>
+ be duplicated as accessURL on a distribution (see also
+ <a href="#dcat_landingPage">dcat:landingPage</a>
+ ).
+ </li>
+ </ul>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="skos-altlabel" class="section">
+ <h4 id="skos_altLabel">
+ <span class="secno">5.3.2 </span>
+ skos:altLabel
+ </h4>
+ <p>An alternative name for the Asset.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Datatype Property</th>
+ <th>
+ <a href="http://www.w3.org/2004/02/skos/core#altLabel">skos:altLabel</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcat-contactpoint" class="section">
+ <h4 id="dcat_contactPoint">
+ <span class="secno">5.3.3 </span>
+ dcat:contactPoint
+ </h4>
+ <p>Links an asset to a contact point from where further information about an Asset can be obtained.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/dcat#contactPoint">dcat:contactPoint</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2006/vcard/ns#">v:VCard</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-creator" class="section">
+ <h4 id="dcterms_creator">
+ <span class="secno">5.3.4 </span>
+ dcterms:creator
+ </h4>
+ <p>
+ Used in ADMS to link an
+ <code>
+ <a href="#dt_identifier">adms:Identifier</a>
+ </code>
+ to a
+
+ <code>
+ <a href="http://dublincore.org/documents/dcmi-terms/#terms-Agent">dcterms:Agent</a>
+ </code>
+
+ (equivalent class
+ <code>
+ <a href="http://xmlns.com/foaf/spec/#term_Agent">foaf:Agent</a>
+ </code>
+ )
+ </p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/creator">dcterms:creator</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://purl.org/dc/terms/Agent">dcterms:Agent</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcat-dataset" class="section">
+ <h4 id="dcat_dataset">
+ <span class="secno">5.3.5 </span>
+ dcat:dataset
+ </h4>
+ <p>Used to link an Asset Repository to an Asset.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/dcat#dataset">dcat:dataset</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Domain</td>
+ <td>
+ <a href="http://www.w3.org/ns/dcat#Catalog">dcat:Catalog</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/ns/dcat#Dataset">dcat:Dataset</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="wdrs-describedby" class="section">
+ <h4 id="wdrs_describedby">
+ <span class="secno">5.3.6 </span>
+ wdrs:describedby
+ </h4>
+ <p>The main documentation or specification of the Asset</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/2007/05/powder-s#describedby">wdrs:describedby</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Usage note</td>
+ <td>
+ See also
+ <a href="#dcat_landingPage">dcat:landingPage</a>
+ ,
+ <a href="#foaf_page">foaf:page</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-description" class="section">
+ <h4 id="dcterms_description">
+ <span class="secno">5.3.7 </span>
+ dcterms:description
+ </h4>
+ <p>A description of the Asset, Asset Repository or Asset Distribution.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Datatype Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/description">dcterms:description</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcat-distribution" class="section">
+ <h4 id="dcat_distribution">
+ <span class="secno">5.3.8 </span>
+ dcat:distribution
+ </h4>
+ <p>Links an Asset to an implementation in a particular format.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/dcat#distribution">dcat:distribution</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Domain</td>
+ <td>
+ <a href="http://www.w3.org/ns/dcat#Dataset">dcat:Dataset</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/ns/dcat#Distribution">dcat:Distribution</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcat-downloadurl" class="section">
+ <h4 id="dcat_downloadURL">
+ <span class="secno">5.3.9 </span>
+ dcat:downloadURL
+ </h4>
+ <p>This is a direct link from an Asset Distribution to a downloadable file in a given format, e.g. CSV file or RDF file. The format is described by the distribution's dcterms:format and/or dcat:mediaType.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/dcat#downloadURL">dcat:downloadURL</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>
+ .
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="schema-enddate" class="section">
+ <h4 id="schema_endDate">
+ <span class="secno">5.3.10 </span>
+ schema:endDate
+ </h4>
+ <p>Used in ADMS to define the end of a period of time during which an Asset is valid or applicable.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Datat Type Property</th>
+ <th>schema:endDate</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
+ which should be typed, typically with
+ <code>xsd:date</code>
+ .
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-format" class="section">
+ <h4 id="dcterms_format">
+ <span class="secno">5.3.11 </span>
+ dcterms:format
+ </h4>
+ <p>The file format of the distribution.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/format">dcterms:format</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://purl.org/dc/terms/MediaTypeOrExtent">dcterms:MediaTypeOrExtent</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Usage note</td>
+ <td>
+ <a href="#dcat_mediaType">dcat:mediaType</a>
+ should be used if the type of the distribution is defined by
+ <a href="http://www.iana.org/assignments/media-types/">IANA</a>
+ .
+ Suitable values for
+ <code>dcterms:format</code>
+ include URIs as used in the
+ <a href="#sadEg">example</a>
+ . See also
+ <a href="#adms_representationTechnique">adms:representationTechnique</a>
+ .
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-identifier" class="section">
+ <h4 id="adms_identifier">
+ <span class="secno">5.3.12 </span>
+ adms:identifier
+ </h4>
+ <p>
+ Links a resource to an
+ <code>adms:Identifier</code>
+ class.
+ </p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#identifier">adms:identifier</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/ns/adms#Identifier">adms:Identifier</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-includedasset" class="section">
+ <h4 id="adms_includedAsset">
+ <span class="secno">5.3.13 </span>
+ adms:includedAsset
+ </h4>
+ <p>An Asset that is contained in the Asset being described, e.g. when there are several vocabularies defined in a single document.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#includedAsset">adms:includedAsset</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Domain</td>
+ <td>
+ <a href="http://www.w3.org/ns/adms#Asset">adms:Asset</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/ns/adms#Asset">adms:Asset</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-interoperabilitylevel" class="section">
+ <h4 id="adms_interoperabilityLevel">
+ <span class="secno">5.3.14 </span>
+ adms:interoperabilityLevel
+ </h4>
+ <p>The interoperability level for which the Asset is relevant.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#interoperabilityLevel">adms:interoperabilityLevel</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Domain</td>
+ <td>
+ <a href="http://www.w3.org/ns/adms#Asset">adms:Asset</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-issued" class="section">
+ <h4 id="dcterms_issued">
+ <span class="secno">5.3.15 </span>
+ dcterms:issued
+ </h4>
+ <p>Date of formal issuance (e.g., publication) of the Asset, Asset Repository or Asset Distribution.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Datatype Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/issued">dcterms:issued</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
+
+ using the relevant
+ <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time</a>
+ compliant string and
+ typed using the appropriate XML Schema datatype [
+ <cite>
+ <a class="bibref" href="#bib-XMLSCHEMA-2">XMLSCHEMA-2</a>
+ </cite>
+ ]
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcat-keyword" class="section">
+ <h4 id="dcat_keyword">
+ <span class="secno">5.3.16 </span>
+ dcat:keyword
+ </h4>
+ <p>A word, phrase or tag to describe the Asset.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Datatype Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/dcat#keyword">dcat:keyword</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcat-landingpage" class="section">
+ <h4 id="dcat_landingPage">
+ <span class="secno">5.3.17 </span>
+ dcat:landingPage
+ </h4>
+ <p>A Web page that can be navigated to in a Web browser to gain access to the Asset, its distributions and/or additional information.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/dcat#landingPage">dcat:landingPage</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://xmlns.com/foaf/0.1/Document">foaf:Document</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Usage note</td>
+ <td>If the Asset Distribution(s) are accessible only through a landing page (i.e. direct download URLs are not known), then the landing page link should be duplicated as accessURL on a distribution.</td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-language" class="section">
+ <h4 id="dcterms_language">
+ <span class="secno">5.3.18 </span>
+ dcterms:language
+ </h4>
+ <p>The language of the Asset</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/LinguisticSystem">dcterms:LinguisticSystem</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>
+ <br>
+
+ Resources defined by the Library of Congress (
+ <a href="http://id.loc.gov/vocabulary/iso639-1.html">1</a>
+ ,
+ <a href="http://id.loc.gov/vocabulary/iso639-2.html">2</a>
+ )
+
+ <em title="should" class="rfc2119">should</em>
+ be used.
+ <br>
+
+ If an ISO 639-1 (two-letter) code is defined for language, then its corresponding IRI
+ <em title="should" class="rfc2119">should</em>
+
+ be used; if no ISO 639-1 code is defined, then IRI corresponding to the ISO 639-2 (three-letter) code
+ <em title="should" class="rfc2119">should</em>
+
+ be used.
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-last" class="section">
+ <h4 id="adms_last">
+ <span class="secno">5.3.19 </span>
+ adms:last
+ </h4>
+ <p>A link to the current or latest version of the Asset.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#last">adms:last</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Sub property of</td>
+ <td>
+ <a href="http://www.w3.org/1999/xhtml/vocab#last">xhv:last</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-license" class="section">
+ <h4 id="dcterms_license">
+ <span class="secno">5.3.20 </span>
+ dcterms:license
+ </h4>
+ <p>Links to the conditions or restrictions for (re-)use of the Asset Distribution.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/license">dcterms:license</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://purl.org/dc/terms/LicenseDocument">dcterms:LicenseDocument</a>
+ .
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Usage note</td>
+ <td>If multiple licenses are given, these licenses apply to all files in the Asset Distribution.</td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcat-mediatype" class="section">
+ <h4 id="dcat_mediaType">
+ <span class="secno">5.3.21 </span>
+ dcat:mediaType
+ </h4>
+ <p>
+ The media type of the distribution as defined by
+ <a href="http://www.iana.org/assignments/media-types/">IANA</a>
+ .
+ </p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/dcat#mediaType">dcat:mediaType</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://purl.org/dc/terms/MediaTypeOrExtent">dcterms:MediaTypeOrExtent</a>
+ .
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Usage note</td>
+ <td>
+ This property
+ <em title="should" class="rfc2119">should</em>
+ be used when the media type of the distribution is defined in
+
+ <a href="http://www.iana.org/assignments/media-types/">IANA</a>
+ , e.g.
+ <code>text/csv</code>
+ otherwise
+ <a href="#dcterms_format">dcterms:format</a>
+ <em title="may" class="rfc2119">may</em>
+ be used with different values.
+ See also
+ <a href="#adms_representationTechnique">adms:representationTechnique</a>
+ .
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-modified" class="section">
+ <h4 id="dcterms_modified">
+ <span class="secno">5.3.22 </span>
+ dcterms:modified
+ </h4>
+ <p>Date of the latest update of the Asset, Asset Repository or Asset Distribution.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Datatype Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/modified">dcterms:modified</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
+
+ using the relevant
+ <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time</a>
+ compliant string and
+ typed using the appropriate XML Schema datatype [
+ <cite>
+ <a class="bibref" href="#bib-XMLSCHEMA-2">XMLSCHEMA-2</a>
+ </cite>
+ ]
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-next" class="section">
+ <h4 id="adms_next">
+ <span class="secno">5.3.23 </span>
+ adms:next
+ </h4>
+ <p>A link to the next version of the Asset.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#next">adms:next</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Sub property of</td>
+ <td>
+ <a href="http://www.w3.org/1999/xhtml/vocab#next">xhv:next</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="skos-notation" class="section">
+ <h4 id="skos_notation">
+ <span class="secno">5.3.24 </span>
+ skos:notation
+ </h4>
+ <p>
+ Used in ADMS to provide the actual identifier string as a property of an
+ <a href="#dt_identifier">
+ <code>adms:Identifier</code>
+ </a>
+ </p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Data Type Property</th>
+ <th>
+ <a href="http://www.w3.org/2004/02/skos/core#">skos:notation</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
+ which should be typed.
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-prev" class="section">
+ <h4 id="adms_prev">
+ <span class="secno">5.3.25 </span>
+ adms:prev
+ </h4>
+ <p>A link to the previous version of the Asset.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#prev">adms:prev</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Sub property of</td>
+ <td>
+ <a href="http://www.w3.org/1999/xhtml/vocab#prev">xhv:prev</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-publisher" class="section">
+ <h4 id="dcterms_publisher">
+ <span class="secno">5.3.26 </span>
+ dcterms:publisher
+ </h4>
+ <p>Links an Asset, Asset Repository or Asset Distribution to the publishing foaf:Agent.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/publisher">dcterms:publisher</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://xmlns.com/foaf/0.1/Agent">foaf:Agent</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="foaf-page" class="section">
+ <h4 id="foaf_page">
+ <span class="secno">5.3.27 </span>
+ foaf:page
+ </h4>
+ <p>Links to documentation that contains information related to the Asset.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://xmlns.com/foaf/0.1/page">foaf:page</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://xmlns.com/foaf/0.1/Document">foaf:Document</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Usage note</td>
+ <td>
+ See also
+ <a href="#dcat_landingPage">dcat:landingPage</a>
+ ,
+ <a href="#wdrs_describedby">wdrs:describedby</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-relation" class="section">
+ <h4 id="dcterms_relation">
+ <span class="secno">5.3.28 </span>
+ dcterms:relation
+ </h4>
+ <p>A link between two Assets that are related in some (unspecified) way.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/relation">dcterms:relation</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-representationtechnique" class="section">
+ <h4 id="adms_representationTechnique">
+ <span class="secno">5.3.29 </span>
+ adms:representationTechnique
+ </h4>
+ <p>More information about the format in which an Asset Distribution is released. This is different from the file format as, for example, a ZIP file (file format) could contain an XML schema (representation technique).</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#representationTechnique">adms:representationTechnique</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Usage note</td>
+ <td>
+ See also
+ <a href="#dcterms_format">dcterms:format</a>
+ and
+ <a href="#dcat_mediaType">dcat:mediaType</a>
+ .
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-sample" class="section">
+ <h4 id="adms_sample">
+ <span class="secno">5.3.30 </span>
+ adms:sample
+ </h4>
+ <p>Links to a sample of an Asset (which is itself an Asset).</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#sample">adms:sample</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/ns/adms#Asset">adms:Asset</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-schemaagency" class="section">
+ <h4 id="adms_schemaAgency">
+ <span class="secno">5.3.31 </span>
+ adms:schemaAgency
+ </h4>
+ <p>The name of the agency that issued the identifier.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Data Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#schemaAgency">adms:schemaAgency</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Domain</td>
+ <td>
+ <a href="#dt_identifier">adms:Identifier</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-spatial" class="section">
+ <h4 id="dcterms_spatial">
+ <span class="secno">5.3.32 </span>
+ dcterms:spatial
+ </h4>
+ <p>The geographic region to which the Asset or Asset Repository applies.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/spatial">dcterms:spatial</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://purl.org/dc/terms/Location">dcterms:Location</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="schema-startdate" class="section">
+ <h4 id="schema_startDate">
+ <span class="secno">5.3.33 </span>
+ schema:startDate
+ </h4>
+ <p>Used in ADMS to define the start of a period of time during which an Asset is valid or applicable.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Datat Type Property</th>
+ <th>schema:startDate</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
+ which should be typed, typically with
+ <code>xsd:date</code>
+ .
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-status" class="section">
+ <h4 id="adms_status">
+ <span class="secno">5.3.34 </span>
+ adms:status
+ </h4>
+ <p>The status of the Asset in the context of a particular workflow process.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#status">adms:status</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-supportedschema" class="section">
+ <h4 id="adms_supportedSchema">
+ <span class="secno">5.3.35 </span>
+ adms:supportedSchema
+ </h4>
+ <p>A schema according to which the Asset Repository can provide data about its content, e.g. ADMS.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Datatype Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#supportedSchema">adms:supportedSchema</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/ns/adms#Asset">adms:Asset</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-temporal" class="section">
+ <h4 id="dcterms_temporal">
+ <span class="secno">5.3.36 </span>
+ dcterms:temporal
+ </h4>
+ <p>The time period to which the Asset applies, e.g. its validity.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/temporal">dcterms:temporal</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://purl.org/dc/terms/PeriodOfTime">dcterms:PeriodOfTime</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcat-theme" class="section">
+ <h4 id="dcat_theme">
+ <span class="secno">5.3.37 </span>
+ dcat:theme
+ </h4>
+ <p>The theme or sector to which the Asset applies.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/dcat#theme">dcat:theme</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Sub property of</td>
+ <td>
+ <a href="http://purl.org/dc/terms/subject">dcterms:subject</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcat-themetaxonomy" class="section">
+ <h4 id="dcat_themeTaxonomy">
+ <span class="secno">5.3.38 </span>
+ dcat:themeTaxonomy
+ </h4>
+ <p>The SKOS Concept Scheme used to classify an Asset Repository's assets.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/dcat#themeTaxonomy">dcat:themeTaxonomy</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2004/02/skos/core#ConceptScheme">skos:ConceptScheme</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-title" class="section">
+ <h4 id="dcterms_title">
+ <span class="secno">5.3.39 </span>
+ dcterms:title
+ </h4>
+ <p>A name given to the Asset, Asset Repository or Asset Distribution.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Datatype Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/title">dcterms:title</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-translation" class="section">
+ <h4 id="adms_translation">
+ <span class="secno">5.3.40 </span>
+ adms:translation
+ </h4>
+ <p>Links Assets that are translations of each other.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#translation">adms:translation</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="dcterms-type" class="section">
+ <h4 id="dcterms_type">
+ <span class="secno">5.3.41 </span>
+ dcterms:type
+ </h4>
+ <p>This property is used to point to the specific type of publisher, Asset and License Document. In each case
the type should be provided using a controlled vocabulary encoded as a SKOS Concept.</p>
-<table class="definition">
- <thead><tr><th>Object Type Property</th><th><a href="http://purl.org/dc/terms/type">dcterms:type</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td>Formally <a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a> but
- <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a> <em title="should" class="rfc2119">should</em> be used.</td></tr>
- </tbody>
-</table>
-</section>
-
-
-<section>
-<h3 id="owl_version">owl:versionInfo</h3>
-<p>A version number or other designation of the Asset.</p>
-<table class="definition">
- <thead><tr><th>Annotation Property</th><th><a href="http://www.w3.org/2002/07/owl#versionInfo">owl:versionInfo</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr>
- </tbody>
-</table>
-</section>
-
-<section>
-<h3 id="adms_versionNotes">adms:versionNotes</h3>
-<p>A description of changes between this version and the previous version of the Asset.</p>
-<table class="definition">
- <thead><tr><th>Datatype Property</th><th><a href="http://www.w3.org/ns/adms#version">adms:versionNotes</a></th></tr></thead>
- <tbody>
- <tr><td class="prop">Range</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a></td></tr>
- </tbody>
-</table>
-</section>
-
-</section> <!-- Properties and relationships -->
-
-</section> <!-- Domain Model -->
-
-<section id="acknowledgements" class="appendix">
-<h2>Acknowledgements</h2>
-<p>ADMS was first developed by PwC EU Services and <a href="http://joinup.ec.europa.eu/asset/adms/home">published
- by the European Commission</a>. Further development and review has been undertaken by the
- <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> (GLD WG).</p>
-
-<p>The original development of ADMS was carried out under the
-Interoperability Solutions for European Public Administrations (<a href="http://ec.europa.eu/isa/">ISA Programme</a>)
-of the European Commission (EC). Contributors included representatives of Member
-States of the European Union, operators of national repositories, standardization
-bodies and independent experts whose work was published in April 2012 [[ADMS1]].
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Object Type Property</th>
+ <th>
+ <a href="http://purl.org/dc/terms/type">dcterms:type</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ Formally
+ <a href="http://www.w3.org/2000/01/rdf-schema#Resource">rdfs:Resource</a>
+ but
+
+ <a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a>
+ <em title="should" class="rfc2119">should</em>
+ be used.
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="owl-versioninfo" class="section">
+ <h4 id="owl_version">
+ <span class="secno">5.3.42 </span>
+ owl:versionInfo
+ </h4>
+ <p>A version number or other designation of the Asset.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Annotation Property</th>
+ <th>
+ <a href="http://www.w3.org/2002/07/owl#versionInfo">owl:versionInfo</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="adms-versionnotes" class="section">
+ <h4 id="adms_versionNotes">
+ <span class="secno">5.3.43 </span>
+ adms:versionNotes
+ </h4>
+ <p>A description of changes between this version and the previous version of the Asset.</p>
+ <table class="definition">
+ <thead>
+ <tr>
+ <th>Datatype Property</th>
+ <th>
+ <a href="http://www.w3.org/ns/adms#version">adms:versionNotes</a>
+ </th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="prop">Range</td>
+ <td>
+ <a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ </div>
+ <!-- Properties and relationships -->
+ </div>
+ <!-- Domain Model -->
+ <div id="acknowledgements" class="appendix section">
+ <!--OddPage-->
+ <h2>
+ <span class="secno">A. </span>
+ Acknowledgements
+ </h2>
+ <p>ADMS was first developed by and <a href="http://joinup.ec.europa.eu/asset/adms/home">published</a>
+ by the European Commission <a href="http://ec.europa.eu/isa/">ISA Programme</a>.
+Contributors included representatives of Member States of the European Union, operators of national repositories, standardization
+bodies and independent experts whose work was published in April 2012 [<cite><a class="bibref" href="#bib-ADMS1">ADMS1</a></cite>].
That document includes the history and motivation behind the development of ADMS, as well as the
-business need and usage scenario for it.</p>
-<p>This version of ADMS builds on that work in a broader, global context. It also includes some changes to the original
+business need and usage scenario for it.
+ </p>
+<p>Further development and review has been undertaken by the
+<a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a>
+ (GLD WG).
+This version of ADMS builds on the original work in a broader, global context. It also includes some changes to the original
version made as a result of implementation experience, particularly on the
European Commission's <a href="http://joinup.ec.europa.eu/">Joinup Platform</a>.</p>
-
-</section>
+ </div>
+ <div id="references" class="appendix section">
+ <!--OddPage-->
+ <h2>
+ <span class="secno">B. </span>
+ References
+ </h2>
+ <div id="normative-references" class="section">
+ <h3>
+ <span class="secno">B.1 </span>
+ Normative references
+ </h3>
+ <dl class="bibliography">
+ <dt id="bib-DC11">[DC11]</dt>
+ <dd>
+ Dublin Core metadata initiative.
+ <a href="http://dublincore.org/documents/dcmi-terms/">
+ <cite>Dublin Core metadata element set, version 1.1.</cite>
+ </a>
+ July 1999. Dublin Core recommendation. URL:
+ <a href="http://dublincore.org/documents/dcmi-terms/">http://dublincore.org/documents/dcmi-terms/</a>
+ </dd>
+ <dt id="bib-DCAT">[DCAT]</dt>
+ <dd>
+ <cite>
+ <a href="http://www.w3.org/TR/vocab-dcat/">Data Catalog Vocabulary (DCAT)</a>
+ </cite>
+ F. Maali, J. Erickson, P. Archer, W3C Recommendations Track URL: http://www.w3.org/TR/vocab-dcat/
-
+ </dd>
+ <dt id="bib-RFC2119">[RFC2119]</dt>
+ <dd>
+ S. Bradner.
+ <a href="http://www.ietf.org/rfc/rfc2119.txt">
+ <cite>Key words for use in RFCs to Indicate Requirement Levels.</cite>
+ </a>
+ March 1997. Internet RFC 2119. URL:
+ <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
+ </dd>
+ <dt id="bib-XMLSCHEMA-2">[XMLSCHEMA-2]</dt>
+ <dd>
+ Paul V. Biron; Ashok Malhotra.
+ <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">
+ <cite>XML Schema Part 2: Datatypes Second Edition.</cite>
+ </a>
+ 28 October 2004. W3C Recommendation. URL:
+ <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/</a>
+ </dd>
+ </dl>
+ </div>
+ <div id="informative-references" class="section">
+ <h3>
+ <span class="secno">B.2 </span>
+ Informative references
+ </h3>
+ <dl class="bibliography">
+ <dt id="bib-ADMS1">[ADMS1]</dt>
+ <dd>
+ <cite>
+ <a href="http://joinup.ec.europa.eu/asset/adms/release/100">ADMS 1.0</a>
+ </cite>
+ European Commission ADMS (link is to a page offering various downloadable files in a variety of formats). URL: http://joinup.ec.europa.eu/asset/adms/release/100
+ </dd>
+ <dt id="bib-EDSU">[EDSU]</dt>
+ <dd>
+ <cite>
+ <a href="http://mediatypes.appspot.com/">Media Types Application</a>
+ </cite>
+ Ed Summers' work on providing URIs for media types URL: http://mediatypes.appspot.com/
-</body></html>
+ </dd>
+ <dt id="bib-EIF2">[EIF2]</dt>
+ <dd>
+ <cite>
+ <a href="http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf">European Interoperability Framework (EIF) for European public services</a>
+ </cite>
+ (PDF) European Commission. URL: http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf.
+
+ </dd>
+ <dt id="bib-FRBR">[FRBR]</dt>
+ <dd>
+ <cite>
+ <a href="http://archive.ifla.org/VII/s13/frbr/frbr_current_toc.htm">Functional Requirements for Bibliographic Records</a>
+ </cite>
+ OFLA 1998 URL: http://archive.ifla.org/VII/s13/frbr/frbr_current_toc.htm
+
+ </dd>
+ <dt id="bib-TOGD">[TOGD]</dt>
+ <dd>
+ <cite>
+ <a href="http://joinup.ec.europa.eu/sites/default/files/towards_open_government_metadata_0.pdf">Towards Open Government Metadata</a>
+ </cite>
+ (PDF) European Commission Joinup e-Library. URL: http://joinup.ec.europa.eu/sites/default/files/towards_open_government_metadata_0.pdf
+
+ </dd>
+ <dt id="bib-UNCEFACT">[UNCEFACT]</dt>
+ <dd>
+ <cite>
+ <a href="http://www.unece.org/fileadmin/DAM/cefact/codesfortrade/CCTS/CCTS-DTCatalogueVersion3p1.pdf"> (PDF) Core Components Data Type Catalogue Version 3.1</a>
+ </cite>
+ UNECE United Nations Economic Commission for Europe. UN Centre for Trade Facilitation and Electronic Business (UN/CEFACT). URL: http://www.unece.org/fileadmin/DAM/cefact/codesfortrade/CCTS/CCTS-DTCatalogueVersion3p1.pdf
+
+ </dd>
+ </dl>
+ </div>
+ </div>
+ </body>
+ </html>
\ No newline at end of file
--- a/bp/index.html Thu Jun 06 10:23:55 2013 +0200
+++ b/bp/index.html Mon Jun 10 11:25:29 2013 +0200
@@ -13,7 +13,8 @@
<script type="text/javascript" src="respec-ref.js" class="remove"></script>
<script type="text/javascript" src="../respec/gld-bib.js" class="remove"></script>
<script type="text/javascript" src="respec-config.js" class="remove"></script>
- <script type="text/javascript" src="respec-contributor-hack.js" class="remove"></script>
+ <script type="text/javascript" src="respec-contributor-hack.js" class="remove"></script>
+
<link rel="stylesheet" type="text/css" href="local-style.css" />
</head>
<body>
@@ -47,7 +48,7 @@
<h2>Scope</h2>
<p>
-This document aims to facilitate the adoption of Linked Open Data Principles for publishing open government data on the Web. Linked Data utilizes the Resource Description Framework (RDF).
+This document aims to facilitate the adoption of Linked Open Data Principles for publishing open government data on the Web. Linked Data utilizes the Resource Description Framework [[!RDF]].
<p>
Linked Data refers to a set of best practices for publishing and interlinking structured data for access by both humans and machines via the use of the RDF family of syntaxes (e.g., RDF/XML, N3, Turtle and N-Triples) and HTTP URIs. RDF and Linked Data are not the same thing.
@@ -121,7 +122,7 @@
The process of publishing Government Linked Open Data should be comprised of tractable and manageable steps, forming a life cycle in the same way Software Engineering uses life cycles in development projects. A GLD life cycle should cover all steps from identifying appropriate datasets to actually publishing and maintaining them. In the following paragraph three different life cycle models are presented, however it is evident that they all share common (and sometimes overlapping) characteristics in their constituents. For example, they all identify the need to specify, model and publish data in acceptable LOD formats. In essence, they capture the same tasks that are needed in the process, but provide different boundaries between these tasks.
</p>
-<p class="todo"> (Editors) - Please provide a brief description of lifecycle diagrams.
+<p class="issue"> (Editors) - Please provide a brief description of lifecycle diagrams.
</p>
<ul>
@@ -142,7 +143,7 @@
<ul>
<li>
- <p>Villazón-terrazas et al. cpropose a Linked Data life cycle that consists of the following steps: (1) Specify, (2) Model, (3) Generate, (4) Publish, and (5) Exploit.
+ <p>Villazón-terrazas et al. propose a Linked Data life cycle that consists of the following steps: (1) Specify, (2) Model, (3) Generate, (4) Publish, and (5) Exploit.
</p>
</li>
</ul>
@@ -155,27 +156,28 @@
<h2>Vocabulary Selection</h2>
<p>
-There are several core W3C vocabularies that allow a developer to describe basic or more complex relationships as Linked Data. Standardized vocabularies should be reused as much as possible to facilitate inclusion and expansion of the <a href="https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html#web-of-data">Web of data</a>. Government publishers are encouraged to use standardized vocabularies rather than reinventing the wheel, wherever possible.
+There are several core W3C vocabularies that allow a developer to describe basic or more complex relationships as Linked Data. Standardized vocabularies should be reused as much as possible to facilitate inclusion and expansion of the <a href="http://www.w3.org/TR/ld-glossary/#web-of-data" target="_blank">Web of data</a>. Government publishers are encouraged to use standardized vocabularies rather than reinventing the wheel, wherever possible.
</p>
<p>
-For example, organizational structures and activities are often described by government authorities. The <a href="http://www.w3.org/TR/vocab-org/" target="_blank">Organization Ontology</a> aims to support publishing of organizational information across a number of domains, as Linked Data. The Organizational Ontology is designed to allow domain-specific extensions to add classification of organizations and roles, as well as extensions to support neighbouring information such as organizational activities.
+For example, organizational structures and activities are often described by government authorities. The <a href="http://www.w3.org/TR/vocab-org/" target="_blank">Organization Ontology</a> [[!ORG]] aims to support publishing of organizational information across a number of domains, as Linked Data. The Organizational Ontology is designed to allow domain-specific extensions to add classification of organizations and roles, as well as extensions to support neighbouring information such as organizational activities.
</p>
<p>
-The <a href="http://www.w3.org/TR/vocab-dcat/" target="_blank">Data Catalog Vocabulary (DCAT)</a> is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. By using DCAT to describe datasets in data catalogs, publishers increase discoverability and enable applications easily to consume metadata from multiple catalogs. It further enables decentralized publishing of catalogs and facilitates federated dataset search across sites. Aggregated DCAT metadata can serve as a manifest file to facilitate digital preservation.
+The <a href="http://www.w3.org/TR/vocab-dcat/" target="_blank">Data Catalog Vocabulary (DCAT)</a> [[!DCAT]] is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. By using DCAT to describe datasets in data catalogs, publishers increase discoverability and enable applications easily to consume metadata from multiple catalogs. It further enables decentralized publishing of catalogs and facilitates federated dataset search across sites. Aggregated DCAT metadata can serve as a manifest file to facilitate digital preservation.
</p>
<p>
Many government agencies publish statistical information on the public Web. The <a href="http://www.w3.org/TR/vocab-data-cube/" target="_blank">
-Data Cube Vocabulary</a> provides a means to do this using the <a href="http://www.w3.org/TR/gld-glossary/index.html#rdf" target="_blank">Resource Description Framework (RDF)</a>. The model underpinning the Data Cube vocabulary is compatible with the cube model that underlies SDMX (Statistical Data and Metadata eXchange), an ISO standard for exchanging and sharing statistical data and metadata among organizations. The Data Cube vocabulary is a core foundation which supports extension vocabularies to enable publication of other aspects of statistical data flows or other multi-dimensional data sets.
+Data Cube Vocabulary</a> [[QB]] provides a means to do this using the <a href="http://www.w3.org/TR/ld-glossary/#rdf" target="_blank">Resource Description Framework (RDF)</a>. The model underpinning the Data Cube vocabulary is compatible with the cube model that underlies SDMX (Statistical Data and Metadata eXchange), an ISO standard for exchanging and sharing statistical data and metadata among organizations. The Data Cube vocabulary is a core foundation which supports extension vocabularies to enable publication of other aspects of statistical data flows or other multi-dimensional data sets.
</p>
<!--<p class="todo"> To include: Phil suggests to include <a href="http://www.w3.org/QA/2012/07/conformance_for_vocabularies.html" target="_blank">Conformance for Vocabularies</a>.
</p> -->
+<!-- section conformance -->
<section>
<h2>Conformance for Vocabularies</h2>
-A data interchange, however that interchange occurs, is conformant with a vocabulary if:
+A data interchange, however that interchange occurs, is <b>conformant</b> with a vocabulary if:
<ul>
<li>it is within the scope and objectives of the vocabulary;</li>
@@ -187,8 +189,8 @@
</ul>
A conforming data interchange:
<ul>
- <li>may include terms from other vocabularies;</li>
- <li> may use a non-empty subset of terms from the vocabulary.</li>
+ <li>MAY include terms from other vocabularies;</li>
+ <li> MAY use a non-empty subset of terms from the vocabulary.</li>
</ul>
A vocabulary profile is a specification that adds additional constraints
to it. Such additional constraints in a profile may include:
@@ -209,45 +211,53 @@
</p>
<p class="highlight"><b>Specify the domain</b><br/>
-<i>What it means:</i>
-Examples of domain: Geography, Environment, Administrations, State Services, Statistics, People, Organisation.</p>
+<i>What it means:</i> Identify the domain scope of the vocabulary <br/>
+<i>Examples of domain: Geography, Environment, Administrations, State Services, Statistics, People, Organisation.</i> </p>
<p class="highlight"><b>Identify relevant keywords in the dataset</b><br/>
- <i>What it means:</i> Identify words that describe the main ideas or concepts. By identifying the relevant keywords or categories of your dataset, it helps for the searching process using a Semantic Web Search Engine.
- <!-- If you have raw data in <a href='http://www.w3.org/TR/gld-glossary/#csv'>CSV</a>, the columns of the tables can be used for the searching process.--> <br/><br/>
- Examples: commune, county, feature
+ <i>What it means:</i> Identify words that describe the main ideas or concepts. By identifying the relevant keywords or categories of your dataset, it helps for the searching process using a Semantic Web Search Engine. <br/><br/>
+ <!-- If you have raw data in <a href='http://www.w3.org/TR/gld-glossary/#csv'>CSV</a>, the columns of the tables can be used for the searching process.-->
+ <i>Examples: commune, county, feature. </i>
</p>
+<div class="note">
<p class="highlight"><b>Searching for a vocabulary in one specific language</b><br/>
- <i>What it means:</i>Many of the available vocabularies are in English. You may be aware of having a vocabulary in your own language.
+ <i>What it means:</i> Many of the available vocabularies are in English. You may be aware of having a vocabulary in your own language.
Consider this issue as it may restrict your search. Sometimes it might be useful to translate some of the keywords to English.
</p>
+</div>
<p class="highlight"><b>How to find vocabularies</b><br/>
<i>What it means:</i>There are some specific search tools (<a href="http://ws.nju.edu.cn/falcons/" target="_blank">Falcons</a>, <a href="http://watson.kmi.open.ac.uk/WatsonWUI/" target="_blank">Watson</a>, <a href="http://sindice.com/" target="_blank">Sindice</a>, <a href="http://swse.deri.org/" target="_blank">Semantic Web Search Engine</a>, <a href="http://swoogle.umbc.edu/" target="_blank">Swoogle</a>, <a href="http://schemapedia.com/" target="_blank">Schemapedia</a>) that collect, analyse and index vocabularies and semantic data available online for efficient access.<br/><br/>
- Examples: It is possible to perform a search on a relevant term or category present in your data.
+ <i>Examples: It is possible to perform a search on a relevant term or category present in your data.</i>
</p>
<p class="highlight"><b>Where to find existing vocabularies in datasets catalogues</b><br/>
<i>What it means:</i>Another way around is to perform search using the previously identified key terms in datasets catalogues. Some of these catalogues provide samples of how the underlying data was modelled and how it was used for.<br/><br/>
- Some existing catalogues are: <a href="http://thedatahub.org/" target="_blank">Data Hub</a> (former CKAN), <a href="http://labs.mondeca.com/dataset/lov/" target="_blank">LOV</a> directory, etc.
+ Some existing catalogues are: <a href="http://thedatahub.org/" target="_blank">Data Hub</a> (former CKAN), <a href="http://labs.mondeca.com/dataset/lov/" target="_blank">LOV</a> directory, <a href="http://prefix.cc">Prefix.cc</a> and <a href="http://bioportal.bioontology.org/">Bioportal</a>.
+
</p>
</section>
<!-- Discovery Checklist -->
<h2>Using SKOS to Create a Controlled Vocabulary</h2>
-<p class="todo"> (Editors) - Requested (12-Apr-2013, GLD WG F2F) - guidance on creating a simple controlled vocabulary using SKOS. Confirm this fits with the scope of BP document.
+<p class="issue"> (Editors) - Requested (12-Apr-2013, GLD WG F2F) - guidance on creating a simple controlled vocabulary using SKOS. Confirm this fits with the scope of BP document. <br/>
+ Some pointers: <br/>
+ + SKOS datasets: http://www.w3.org/2001/sw/wiki/SKOS/Datasets <br/>
+ + SKOS implementation records: http://www.w3.org/2006/07/SWD/SKOS/reference/20090315/implementation.html <br/>
+ + An introduction to SKOS: http://www.xml.com/pub/a/2005/06/22/skos.html
+
</p>
-<!-- << is your Linked Data Vocabulary 5 star? -->
+<!-- << is your Linked Data Vocabulary 5 star?
<p class="todo"> (Editors) - Update with attribution to Bernard Vatant's 5 Star Linked Data Vocabulary scheme (proposed).
</p>
-
+ -->
<section>
<h2>Is your Linked Data Vocabulary 5-star?</h2>
-Inspired by the 5-star linked data scale <a href="http://5stardata.info/" target="_blank">5-Star Scheme</a>, suggestions on creating a 5-star vocabulary <a href="http://blog.hubjects.com/2012/02/is-your-linked-data-vocabulary-5-star_9588.html" target="_blank">REF4</a>.
+Inspired by the 5-star linked data scale <a href="http://5stardata.info/" target="_blank">5-Star Scheme</a>, suggestions on creating a 5-star vocabulary <a href="http://bvatant.blogspot.fr/2012/02/is-your-linked-data-vocabulary-5-star_9588.html" target="_blank">[[BV5STAR]]</a>.
<p class="highlight">☆ <b>Publish your vocabulary on the Web at a stable URI using an open license.</b>
</p>
@@ -273,10 +283,10 @@
<section>
<h2>Vocabulary Selection Criteria</h2>
-This checklist aims to help in vocabulary selection, in summary:
-<li>Ensure vocabularies you use are published by a trusted group or organization</li>
-<li>Ensure vocabularies have permanent URIs</li>
-<li>Confirm the versioning policy </li>
+<p class="note"> This checklist aims to help in vocabulary selection, in summary: (1)-
+<b>Ensure vocabularies you use are published by a trusted group or organization</b>; (2)-
+<b>Ensure vocabularies have permanent URIs</b> and (3)
+<b>Confirm the versioning policy</b>.
</p>
<p class="highlight"><b>Vocabularies MUST be documented</b><br/>
@@ -286,22 +296,23 @@
<p class="highlight"><b>Vocabularies SHOULD be self-descriptive</b><br/>
<i>What it means:</i> Each property or term in a vocabulary should have a Label, Definition and Comment defined.
Self-describing data suggests that information about the encodings used for each representation is provided explicitly within the representation. The ability for Linked Data to describe itself, to place itself in context, contributes to the usefulness of the underlying data.<br/><br/>
-For example, popular vocabulary called DCMI Metadata Terms has a Term Name <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a> which has a:</br>
- Label: Contributor<br/>
- Definition: An entity responsible for making contributions to the resource<br/>
- Comment: Examples of a Contributor include a person, an organization, or a service.<br/>
+For example, popular vocabulary called <code>DCMI Metadata Terms</code> has a Term Name <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a> which has a:</br>
+ <code>Label: Contributor </code><br/>
+ <code>Definition: An entity responsible for making contributions to the resource </code><br/>
+ <code>Comment: Examples of a Contributor include a person, an organization, or a service.</code><br/>
</p>
<p class="highlight"><b>Vocabularies SHOULD be described in more than one language</b><br/>
<i>What it means:</i> Multilingualism should be supported by the vocabulary, i.e., all the elements of the vocabulary should have labels, definitions and comments available in the government's official language, e.g., Spanish, and at least in English.
That is also very important as the documentation should be clear enough with appropriate tag for the language used for the comments or labels.<br/><br/>
For example, for the same term <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a></br>
- rdfs:label "Contributor"@en, "Colaborador"@es<br/>
- rdfs:comment "Examples of a Contributor include a person, an organization, or a service"@en , "Ejemplos de collaborator incluyen persona, organización o servicio"@es<br/>
+ <code>rdfs:label "Contributor"@en, "Colaborador"@es<br/>
+ rdfs:comment "Examples of a Contributor include a person, an organization, or a service"@en , "Ejemplos de collaborator incluyen persona, organización o servicio"@es<br/></code>
</p>
<p class="highlight"><b>Vocabularies SHOULD be used by other data sets</b><br/>
- <i>What it means:</i> If the vocabulary is used by other authoritative Linked Open Data sets that is helpful. It is in re-use of vocabularies that we achieve the benefits of Linked Open Data. Selected vocabularies from third parties should be already in use by other data sets, as shows that they are already established in the LOD community, and thus better candidates for wider adoption and reuse. For example: An analysis on the <a href="http://stats.lod2.eu/vocabularies" target="_blank">use of vocabularies</a> on the Linked Data cloud reveals that <a href="http://xmlns.com/foaf/0.1" target="_blank">FOAF</a> is reused by more than 55 other vocabularies.
+ <i>What it means:</i> If the vocabulary is used by other authoritative Linked Open Data sets that is helpful. It is in re-use of vocabularies that we achieve the benefits of Linked Open Data. Selected vocabularies from third parties should be already in use by other data sets, as shows that they are already established in the LOD community, and thus better candidates for wider adoption and reuse. <br/><br/>
+ For example: An analysis on the <a href="http://stats.lod2.eu/vocabularies" target="_blank">use of vocabularies</a> on the Linked Data cloud reveals that <a href="http://xmlns.com/foaf/0.1" target="_blank">FOAF</a> is reused by more than 55 other vocabularies.
</p>
<p class="highlight"><b>Vocabularies SHOULD be accessible for a long period</b><br/>
@@ -314,7 +325,7 @@
<p class="highlight"><b>Vocabularies SHOULD have persistent URLs</b><br/>
<i>What it means:</i> Persistent access to the server hosting the vocabulary, facilitating reusability is necessary.<br/><br/>
- Example: The <a href="http://www.w3.org/2003/01/geo/wgs84_pos#/" target="_blank">Geo W3C vocabulary</a> is one of the most used vocabulary for basic representation of geometry points (latitute/longitude) and has been around since 2009, always available at the same namespace.
+ Example: The <a href="http://lov.okfn.org/dataset/lov/details/vocabulary_geo.html" target="_blank">Geo W3C vocabulary</a> [[GEOW3C]] is one of the most used vocabulary for basic representation of geometry points (latitute/longitude) and has been around since 2009, always available at the same namespace.
</p>
<p class="highlight"><b>Vocabularies should provide a versioning policy</b><br/>
@@ -340,31 +351,35 @@
Partial or full deprecation
Cross-cutting issues: "Hit-by-bus" -->
-<p>There will be cases in which authorities will need to mint their own vocabulary terms. This section provides a set of considerations aimed at helping to government stakeholders mint their own vocabulary terms. This section includes some items of the previous section because some recommendations for vocabulary selection also apply to vocabulary creation. Ensure new vocabularies you create are:
-<li>Self-descriptive </li>
-<li>Described in more than one language, ideally </li>
-<li>Accessible for a long period</li>
+<p><i>There will be cases in which authorities will need to mint their own vocabulary terms. This section provides a set of considerations aimed at helping to government stakeholders mint their own vocabulary terms. This section includes some items of the previous section because some recommendations for vocabulary selection also apply to vocabulary creation.</i> </p>
+<p class="note"> Ensure new vocabularies you create are:
+<b>Self-descriptive </b>,
+<b>Described in more than one language, ideally </b> and
+<b>Accessible for a long period</b>
</p>
<p class="highlight"><b>Define the URI of the vocabulary.</b><br/>
- <i>What it means:</i> The URI that identifies your vocabulary must be defined. This is strongly related to the Best Practices described in section URI Construction.<br/><br/>
+ <i>What it means:</i> The URI that identifies your vocabulary must be defined. This is strongly related to the Best Practices described in section URI Construction.
+ <br/><br/>
+
For example: If we are minting new vocabulary terms from a particular government, we should define the URI of that particular vocabulary.
-</p>
+ </p>
+
<p class="highlight"><b>Vocabularies should be self-descriptive</b><br/>
<i>What it means:</i> Each property or term in a vocabulary should have a Label, Definition and Comment defined.
Self-describing data suggests that information about the encodings used for each representation is provided explicitly within the representation. The ability for Linked Data to describe itself, to place itself in context, contributes to the usefulness of the underlying data.<br/><br/>
-For example, popular vocabulary called DCMI Metadata Terms has a Term Name <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a> which has a:</br>
- Label: Contributor<br/>
+For example, popular vocabulary called DCMI Metadata has a Term Name <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a> which has a:</br>
+ <code>Label: Contributor <br/>
Definition: An entity responsible for making contributions to the resource<br/>
- Comment: Examples of a Contributor include a person, an organization, or a service.<br/>
+ Comment: Examples of a Contributor include a person, an organization, or a service.</code>
</p>
<p class="highlight"><b>Vocabularies should be described in more than one language</b><br/>
<i>What it means:</i> Multilingualism should be supported by the vocabulary, i.e., all the elements of the vocabulary should have labels, definitions and comments available in the government's official language, e.g., Spanish, and at least in English. That is also very important as the documentation should be clear enough with appropriate tag for the language used for the comments or labels.<br/><br/>
-For example, for the same term <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank">Contributor</a></br>
- rdfs:label "Contributor"@en, "Colaborador"@es<br/>
- rdfs:comment "Examples of a Contributor include a person, an organization, or a service"@en , "Ejemplos de collaborator incluyen persona, organización o servicio"@es<br/>
+For example, for the same term <a href="http://dublincore.org/documents/dcmi-terms/#terms-contributor" target="_blank"><code>Contributor</code></a></br>
+ <code>rdfs:label "Contributor"@en, "Colaborador"@es<br/>
+ rdfs:comment "Examples of a Contributor include a person, an organization, or a service"@en , "Ejemplos de collaborator incluyen persona, organización o servicio"@es<br/></code>
</p>
<p class="highlight"><b>Vocabularies should provide a versioning policy</b><br/>
@@ -376,7 +391,7 @@
</p>
<p class="highlight"><b>Vocabulary should be published following available best practices</b><br/>
- <i>What it means:</i> One of the goals is to contribute to the community by sharing the new vocabulary. To this end, it is recommended to follow available recipes for publishing RDF vocabularies, e.g., <a href="http://www.w3.org/TR/swbp-vocab-pub/" target="_blank">Best Practice Recipes for Publishing RDF Vocabularies</a>.
+ <i>What it means:</i> One of the goals is to contribute to the community by sharing the new vocabulary. To this end, it is recommended to follow available recipes for publishing RDF vocabularies e.g., <a href="http://www.w3.org/TR/swbp-vocab-pub/" target="_blank">Best Practice Recipes for Publishing RDF Vocabularies</a>[[BP-PUB]].
</p>
<!-- Vocabulary Creation -->
@@ -384,40 +399,43 @@
<!-- TODO -->
-<p class="todo">Add references to Felix Sasaka's work on multilingual Web and new W3C WG
+<p class="todo">Add references to Felix Sasaka's work on multilingual Web and new W3C WG</p>
-<section>
+<section id="multilingual" class="informative">
<h2>Multilingual Vocabularies</h2>
<p>
-This section provides some considerations when we are dealing with multilingualism in vocabularies. We have identified that multilingualism in vocabularies can be found nowadays in the following formats:
+This section provides some considerations when we are dealing with multilingualism in vocabularies. For more details on the multilingualism on the Web, see the <a href="http://www.w3.org/International/multilingualweb/lt/" target="_blank"> MultilingualWeb-LT Working Group</a> </p>
+<p> We have identified that multilingualism in vocabularies can be found nowadays in the following formats:
</p>
<ul>
- <li>As a set of rdfs:label in which the language has been restricted (@en, @fr...). Currently, this is the most commonly used approach. It is also a best practice to always include an rdfs:label for which the language tag in not indicated. This term corresponds to the "default" language of the vocabulary</li>
- <li>As skos:prefLabel (or skosxl:Label), in which the language has also been restricted.</li>
+ <li>As a set of <code>rdfs:label</code> in which the language has been restricted (@en, @fr...). Currently, this is the most commonly used approach. It is also a best practice to always include an <code>rdfs:label</code> for which the language tag in not indicated. This term corresponds to the <b>"default"</b>language of the vocabulary</li>
+ <li>As <code>skos:prefLabel</code> (or <code>skosxl:Label</code>), in which the language has also been restricted.</li>
<li>As a set of monolingual ontologies (ontologies in which labels are expressed in one natural language) in the same domain mapped or aligned to each other (see the example of EuroWordNet, in which wordnets in different natural languages are mapped to each other through the so-called ILI - inter-lingual-index-, which consists of a set of concepts common to all categorizations).</li>
- <li>As a set of ontology + lexicon. This represents the latest trend in the representation of linguistic (multilingual) information associated to ontologies. The idea is that the ontology is associated to an external ontology of linguistic descriptions. One of the best exponents in this case is the lemon model <a href="http://tia2011.crim.fr/Workshop-Proceedings/pdf/TIAW15.pdf" target="_blank">REF1</a>, <a href="http://lexinfo.net/" target="_blank">REF2</a>, an ontology of linguistic descriptions that is to be related with the concepts and properties in an ontology to provide lexical, terminological, morphosintactic, etc., information. One of the main advantages of this approach is that semantics and linguistic information are kept separated. One can link several lemon models in different natural languages to the same ontology.</li>
+ <li>As a set of ontology + lexicon. This represents the latest trend in the representation of linguistic (multilingual) information associated to ontologies. The idea is that the ontology is associated to an external ontology of linguistic descriptions. One of the best exponents in this case is the lemon model [[TIAW-LEMON]]</a>, <a href="http://lexinfo.net/" target="_blank">[[LEXINFO]]</a>, an ontology of linguistic descriptions that is to be related with the concepts and properties in an ontology to provide lexical, terminological, morphosintactic, etc., information. One of the main advantages of this approach is that semantics and linguistic information are kept separated. One can link several lemon models in different natural languages to the same ontology.</li>
</ul>
-The current trend is to follow the first approach, i.e., to use rdfs:label and rdfs:comment for each term in the vocabulary.
+<p class="note">The current trend is to follow the first approach, i.e., to use at least a <code>rdfs:label</code> and <code>rdfs:comment</code> for each term in the vocabulary.</p>
</section>
<!-- Multilingualism in vocabs >> -->
-<section>
-</section> <!-- VOCABULARY SELECTION >> -->
<!-- << URI CONSTRUCTION -->
-<section>
+<section class="informative">
<h2>URI Construction</h2>
-The following guidance is provided with the intention to address URI minting, i.e., URI creation for vocabularies, concepts and datasets. This section specifies how to create good URIs for use in government linked data. Input documents include
+<p class="issue"> The editors will rephrase better this content and may extend it </p>
+The following guidance is provided with the intention to address URI minting, i.e., URI creation for vocabularies, concepts and datasets. This section specifies how to create good URIs for use in government linked data. Input documents include:
<ul>
- <li><a href="http://www.w3.org/TR/cooluris/" title="Cool URIs for the Semantic Web">Cool URIs for the Semantic Web</a></li>
- <li><a href="http://www.cabinetoffice.gov.uk/media/308995/public_sector_uri.pdf">Designing URI Sets for the UK Public Sector</a> (PDF)</li>
- <li><a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Creating URIs</a> (data.gov.uk).</li>
+ <li>Cool URIs for the Semantic Web [[!COOL-SWURIS]]</li>
+ <li>Designing URI Sets for the UK Public Sector [[BPURI-GOVUK]]</li>
+ <!--<li><a href="http://data.gov.uk/resources/uris" title="Creating URIs | data.gov.uk">Creating URIs</a> (data.gov.uk).</li> -->
+ <li> <a href="http://philarcher.org/diary/2013/uripersistence/" target="_blank">10 rules for persistence URI</a> [[ISA-URI]] </li>
+ <li> <a href="http://www.w3.org/2013/04/odw/odw13_submission_14.pdf">Draft URI Strategy for the NL Public Sector</a> </li>
+
</ul>
-<p>The purpose of URIs is to uniquely and reliably name resources on the Web. According to <a href="http://www.w3.org/TR/cooluris/" target="_blank">Cool URIs for the Semantic Web</a> (W3C IG Note), URIs should be designed with simplicity, stability and manageability in mind, thinking about them as identifiers rather than as names for Web resources.
+<p>The purpose of URIs is to uniquely and reliably name resources on the Web. According to Cool URIs for the Semantic Web [[!COOL-SWURIS]] (W3C IG Note), URIs should be designed with simplicity, stability and manageability in mind, thinking about them as identifiers rather than as names for Web resources.
</p>
<p>
@@ -428,12 +446,12 @@
<p>The Web makes use of the URI (Uniform Resource Identifiers) as a single global identification system. The global scope of URIs promotes large-scale "network effects". Therefore, in order to benefit from the value of LD, government and governmental agencies need to identify their resources using URIs. This section provides a set of general principles aimed at helping government stakeholders to define and manage URIs for their resources.</p>
<p class="highlight"><b>Use HTTP URIs</b><br>
-What it means: To benefit from and increase the value of the World Wide Web, governments and agencies SHOULD provide HTTP URIs as identifiers for their resources. There are many benefits to participating in the existing network of URIs, including linking, caching, and indexing by search engines. As stated in [LDPrinciples], HTTP URIs enable people to "look-up" or "dereference" a URI in order to access a representation of the resource identified by that URI.
+What it means: To benefit from and increase the value of the World Wide Web, governments and agencies SHOULD provide HTTP URIs as identifiers for their resources. There are many benefits to participating in the existing network of URIs, including linking, caching, and indexing by search engines. As stated in [[!HOWTO-LODP]], HTTP URIs enable people to "look-up" or "dereference" a URI in order to access a representation of the resource identified by that URI.
To benefit from and increase the value of the World Wide Web, data publishers SHOULD provide URIs as identifiers for their resources.
</p>
<p class="highlight"><b>Provide at least one machine-readable representation of the resource identified by the URI</b><br>
-What it means: In order to enable HTTP URIs to be "dereferenced", data publishers have to set up the necessary infrastructure elements (e.g. TCP-based HTTP servers) to serve representations of the resources they want to make available (e.g. a human-readable HTML representation or a machine-readable RDF/XML). A publisher may supply zero or more representations of the resource identified by that URI. However, there is a clear benefit to data users in providing at least one machine-readable representation. More information about serving different representations of a resource can be found in <a href="http://www.w3.org/TR/cooluris/" target="_blank">Cool URIs for the Semantic Web</a>.
+What it means: In order to enable HTTP URIs to be "dereferenced", data publishers have to set up the necessary infrastructure elements (e.g. TCP-based HTTP servers) to serve representations of the resources they want to make available (e.g. a human-readable HTML representation or a machine-readable RDF/XML). A publisher may supply zero or more representations of the resource identified by that URI. However, there is a clear benefit to data users in providing at least one machine-readable representation. More information about serving different representations of a resource can be found in [[!COOL-SWURIS]]</a>.
</p>
<p class="highlight"><b>A URI structure will not contain anything that could change</b><br>
@@ -449,19 +467,22 @@
</p>
<p class="highlight"><b>Compliance with http-range-14</b><br>
-The World Wide Web Consortium's (W3C) Technical Architecture Group (TAG) attempted to settle a long standing debate about the use of URL resolution on 15 June 2005. Specifically, they decided:
+The World Wide Web Consortium's (W3C) Technical Architecture Group (TAG) attempted to settle a long standing debate about the use of URL resolution on 15 June 2005. Specifically, they decided: <p class="todo"> Statement not finished </p>
+</p>
-The TAG provides advice to the community that they may mint "http" URIs for any resource provided that they follow this simple rule for the sake of removing ambiguity:
-<ul>
+<p class="note"><b>TAG advices on http issues</b><br>
+The TAG provides advice to the community that they may mint "http" URIs for any resource provided that they follow this simple rule for the sake of removing ambiguity as below:
+<pre class="example">
<li> If an "http" resource responds to a GET request with a 2xx response, then the resource identified by that URI is an information resource;</li>
<li> If an "http" resource responds to a GET request with a 303 (See Other) response, then the resource identified by that URI could be any resource;</li>
<li> If an "http" resource responds to a GET request with a 4xx (error) response, then the nature of the resource is unknown.
</li>
</ul>
+
+ </pre>
-
-The practical implication of http-range-14 for Linked Data and Semantic Web implementors is the requirement to return an HTTP 303 (See Other) response when resolving HTTP URI identifiers for conceptual or physical resources (that is, for resources whose canonical content is non-informational in nature, c.f. [Wood2007]). Current implementations of the Persistent URL (PURL) server provide support for 303 URIs [Wood2010]. Although the issue remains unsettled, and occasional attempts have been (and probably will be) made to revisit the TAG’s decision, however compliance with the http-range-14 decision until such time as it may be updated is recommended.
+The practical implication of http-range-14 for Linked Data and Semantic Web implementors is the requirement to return an HTTP 303 (See Other) response when resolving HTTP URI identifiers for conceptual or physical resources (that is, for resources whose canonical content is non-informational in nature, c.f. [[Wood2007]]). Current implementations of the Persistent URL (PURL) server provide support for 303 URIs [[Wood2010]]. Although the issue remains unsettled, and occasional attempts have been (and probably will be) made to revisit the TAG’s decision, however compliance with the http-range-14 decision until such time as it may be updated is recommended.
</p>
</section>
@@ -545,7 +566,7 @@
<p>
PURLs implement one form of persistent identifier for virtual resources. Other persistent identifier schemes include Digital Object Identifiers (DOIs), Life Sciences Identifiers (LSIDs) and INFO URIs. All persistent identification
-schemes provide unique identifiers for (possibly changing) virtual resources, but not all schemes provide curation opportunities. Curation of virtual resources has been defined as, “the active involvement of information professionals in the management, including the preservation, of digital data for future use.” [Yakel, E (2007)] For a persistent identification scheme to provide a curation opportunity for a virtual resource, it must allow real-time resolution of that resource and also allow real-time administration of the identifier.
+schemes provide unique identifiers for (possibly changing) virtual resources, but not all schemes provide curation opportunities. Curation of virtual resources has been defined as, <b>“the active involvement of information professionals in the management, including the preservation, of digital data for future use.”</b> [[YAKEL-07]] For a persistent identification scheme to provide a curation opportunity for a virtual resource, it must allow real-time resolution of that resource and also allow real-time administration of the identifier.
</p>
<p>URI persistence is a matter of policy and commitment on the part of the URI owner. The choice of a particular URI scheme provides no guarantee that those URIs will be persistent or that they will not be persistent. HTTP [[!RFC2616]] has been designed to help manage URI persistence. For example, HTTP redirection (using the 3xx response codes) permits servers to tell an agent that further action needs to be taken by the agent in order to fulfill the request (for example, a new URI is associated with the resource).
@@ -559,7 +580,7 @@
<section>
<h3>Internationalized Resource Identifiers</h3>
-<p><i>This section on Internationalized Resource Identifiers focuses on using non-ASCII characters in URIs and provides guidelines for those interested in minting URIs in their own languages (German, Dutch, Spanish, Chinese, etc.)</i></p>
+<p><i>This section on Internationalized Resource Identifiers focuses on using non-ASCII characters in URIs and provides guidelines for those interested in minting URIs in their own languages (German, Dutch, Spanish, French, Chinese, etc.)</i></p>
<p>The URI syntax defined in [[!RFC3986]]</a> STD 66 (Uniform Resource Identifier (URI): Generic Syntax) restricts URIs to a small number of characters: basically, just upper and lower case letters of the English alphabet, European numerals and a small number of symbols. There is now a growing need to enable use of characters from any language in URIs.
</p>
@@ -568,21 +589,21 @@
</p>
<p>
-<a href='http://www.w3.org/TR/gld-glossary/index.html#iri'>IRI</a> (<a href="http://tools.ietf.org/html/rfc3987" target="_blank">RFC 3987</a>) is a new protocol element, that represents a complement to the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646) that can be therefore used to mint identifiers that use a wider set of characters than the one defined in [[!RFC3986]]</a>.
+<a href='http://www.w3.org/TR/ld-glossary/index.html#iri'>IRI</a> (<a href="http://tools.ietf.org/html/rfc3987" target="_blank">RFC 3987</a>) is a new protocol element, that represents a complement to the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646) that can be therefore used to mint identifiers that use a wider set of characters than the one defined in [[!RFC3986]]</a>.
</p>
-<p>The Internationalized Domain Name or IDN is a standard approach to dealing with multilingual domain names was agreed by the IETF in March 2003.
+<p>The Internationalized Domain Name or IDN is a standard approach to dealing with multilingual domain names was agreed by the <a href="http://www.w3.org/TR/ld-glossary/#internet-engineering-task-force-ietf">IETF</a> in March 2003.
</p>
<p>Although there exist some standards focused on enabling the use of international characters in Web identifiers, government stakeholders need to take into account several issues before constructing such internationalized identifiers. This section is not meant to be exhaustive and we point the interested audience to <a ref="http://www.w3.org/International/articles/idn-and-iri/" target="_blank">An Introduction to Multilingual Web Addresses</a>, however some of the most relevant issues are following:
</p>
<ul>
- <li><b>Domain Name lookup:</b> Numerous domain name authorities already offer registration of internationalized domain names. These include providers for top level country domains as .cn, .jp, .kr, etc., and global top level domains such as .info, .org and .museum.
+ <li><b>Domain Name lookup:</b> Numerous domain name authorities already offer registration of internationalized domain names. These include providers for top level country domains as <code>.cn, .jp, .kr </code>, etc., and global top level domains such as <code>.info, .org </code> and <code> .museum. </code>
</li>
<li><b>Domain names and phishing:</b> One of the problems associated with IDN support in browsers is that it can facilitate phishing through what are called 'homograph attacks'. Consequently, most browsers that support IDN also put in place some safeguards to protect users from such fraud.
</li>
- <li><b>Encoding problems:</b> IRI provides a standard way for creating and handling international identifiers, however the support for IRIs among the various semantic Web technology stacks and libraries is not homogenic and may lead to difficulties for applications working with this kind of identifiers. A good reference on this subject can be found in "I18n of Semantic Web Applications" by Auer et al.
+ <li><b>Encoding problems:</b> IRI provides a standard way for creating and handling international identifiers, however the support for IRIs among the various semantic Web technology stacks and libraries is not homogenic and may lead to difficulties for applications working with this kind of identifiers. A good reference on this subject can be found in [[I18n-WEB]] .
</li>
</ul>
@@ -598,7 +619,7 @@
It is best practice to explicitly attach a license statement to each data set. Governments typically define ownership of works produced by government employees or contractors in legislation. It is beyond the charter of this working group to describe and recommend appropriate licenses for Open Government content published as Linked Data, however there are useful Web sites that offer detailed guidance and licenses. One valuable resource is the <a href="http://creativecommons.org/">Creative Commons</a> website. Creative Commons develops, supports, and stewards legal and technical infrastructure for digital content publishing.
</p>
-<p>
+<p class="note">
As an informative note, the UK and many former Commonwealth countries maintain the concept of the Crown Copyright. It is important to know who owns your data and to say so. The US Government designates information produced by civil servants as a U.S. Government Work, whereas contractors may produce works under a variety of licenses and copyright assignments. U.S. Government Works are not subject to copyright restrictions in the United States. It is critical for US government officials to know their rights and responsibilities under the Federal Acquisition Regulations (especially FAR Subpart 27.4, the Contract Clauses in 52.227-14, -17 and -20 and any agency-specific FAR Supplements) and copyright assignments if data is produced by a government contractor. It is recommended that governmental authorities publishing Linked Data review the relevant guidance for data published on the Web.
</p>
</section>
@@ -611,15 +632,15 @@
<p>Within government agencies, hosting linked data may require submission and review of a security plan to the authority's security team. While security plan specifics will vary widely based on a range of factors like hosting environment and software configuration, the process for developing and getting a security plan approved can be streamlined if the following guidelines and best practices are considered:</p>
-<p>Notify your security official of your intent to publish open government data.</p>
-<ul>
+<p class="highlight"><b>1- Notify your security official of your intent to publish open government data.</b></p>
+<ul class="note">
<li>Provide an overview of the Linked Data project</li>
<li>Describe how you plan to host the data (e.g., cloud, agency data center), and provide implementation timelines</li>
<li>Consider including your hosting service/software vendor in discussion(s)</li>
</ul>
-<p>Solicit assistance from the security official:</p>
-<ul>
+<p class="highlight"><b>2- Solicit assistance from the security official</b></p>
+<ul class="note">
<li>Identify guidance that should be used (e.g. for US Federal Agencies this typically would entail compliance with security control recommendations from NIST Special Publication 800-53)</li>
<li>Request clarification on regarding specific content/areas that the plan should address</li>
<li>Request a system security plan template to ensure the plan is organized to facilitate the review process (if a vendor is contributing information on controls related to their service/software, the vendor needs to adhere to the template in their response)</li>
@@ -641,16 +662,16 @@
<p>
Publishers of Linked Data enter into an implicit social contract with users of their data. Publishers should recognize the responsibility to maintain data once it is published by a government authority. Ensure that the Linked Open Data set(s) your organization publishes remains available where you say it will be. Here is a summary of best practices that relate to the implicit "social contract". Additional informational details are included for reference.
</p>
-
-<ul>
-<li>Publish a VoID description for each published data set;</li>
-<li>Associate metadata on the frequency of data updates;</li>
-<li>Associate a government appropriate license with all content your agency publishes if you wish to encourage re-use;</li>
-<li>Plan and implement a persistence strategy;</li>
-<li>Ensure data is accurate to the greatest degree possible;</li>
-<li>Publish an email address to report problematic data;</li>
-<li>Ensure the contact person or team responds to enquires via email or telephone, if necessary.</li>
-</ul>
+<div class="note">
+<ul class="highlight">
++ Publish a [[VoID]] description for each published data set;<br/>
++ Associate metadata on the frequency of data updates;<br/>
++ Associate a government appropriate license with all content your agency publishes if you wish to encourage re-use;<br/>
++ Plan and implement a persistence strategy;<br/>
++ Ensure data is accurate to the greatest degree possible;<br/>
++ Publish an email address to report problematic data;<br/>
++ Ensure the contact person or team responds to enquires via email or telephone, if necessary.<br/>
+</ul> </div>
<p>
Giving due consideration to your organization's URI strategy should be one of the first activities your team undertakes as they prepare a Linked Open Data strategy. Authoritative data requires the permanence and resolution of HTTP URIs. If publishers move or remove data that was published to the Web, third party applications or mashups may break. This is considered rude for obvious reasons and is the basis for the Linked Data "social contract." A good way to prevent causing HTTP 404's is for your organization to implement a persistence strategy.
@@ -664,7 +685,7 @@
<h2>Procurement</h2>
<p>
-This procurement checklist and <a href='https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html'> Linked Data Glossary</a> are intended to assist contract officers understand the requirements associated with publishing open government content as Linked Data.
+This procurement checklist and <a href='http://www.w3.org/TR/ld-glossary/'> Linked Data Glossary</a> are intended to assist contract officers understand the requirements associated with publishing open government content as Linked Data.
</p>
<h3>Overview</h3>
@@ -676,7 +697,8 @@
<h3>Procurement Checklist</h3>
The following is an outline of questions a department/agency should consider reviewing as part of their decision to choose a service provider:
-<ul>
+<div class="example">
+<ul >
<li>Is there a government approved federal-wide or agency-specific contract vehicle to obtain this service or product?</li>
<li>What is the vendor’s past performance with government agencies or authorities?</li>
@@ -691,14 +713,17 @@
<li>Is the government data accessible for developers once it is published?</li>
-<li>Can the data be queried programmatically, e.g., through an <a href='http://www.w3.org/TR/gld-glossary/index.html#api'>Application Programming Interface</a> (API), <a href='http://www.w3.org/TR/gld-glossary/index.html#sparql-endpoint'>SPARQL endpoint</a>, other mechanism?</li>
+<li>Can the data be queried programmatically, e.g., through an <a href='http://www.w3.org/TR/ld-glossary/#api'>Application Programming Interface</a> (API), <a href='http://www.w3.org/TR/gld-glossary/index.html#sparql-endpoint'>SPARQL endpoint</a>, other mechanism?</li>
<li>What is the vendor’s Service Level Agreement?</li>
<li>Does the vendor adhere to the agency's published Open Source Policy, if one exists?</li>
</ul>
+
</p>
+</div>
+
</section>
@@ -710,8 +735,7 @@
<!-- <p class='todo'>John Erickson (RPI)</p> -->
<p>
-Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. The <a href="http://www.w3.org/TR/prov-overview/
-" target="_blank">PROV Family of Documents</a> defines a model, corresponding serializations and other supporting defintions to enable the inter-operable interchange of provenance information in heterogeneous environments such as the Web.
+Provenance is information about entities, activities, and people involved in producing a piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness. The PROV Family of Documents [[!PROV-O]] defines a model, corresponding serializations and other supporting defintions to enable the inter-operable interchange of provenance information in heterogeneous environments such as the Web.
</p>
<!-- todo: Talk to John Erickson to develop this more for possible inclusion
@@ -773,7 +797,7 @@
<h3>Stability Properties</h3>
-<p>There are characteristics that influence the stability or longevity of useful open government data. Many of these properties are not unique to government <a href='http://www.w3.org/TR/gld-glossary/index.html#linked-open-data'>Linked Open Data</a>, yet they influence data cost and therefore data value. Several data properties that a government authority should contemplate include:</p>
+<p>There are characteristics that influence the stability or longevity of useful open government data. Many of these properties are not unique to government <a href='http://www.w3.org/TR/ld-glossary/index.html#linked-open-data'>Linked Open Data</a>, yet they influence data cost and therefore data value. Several data properties that a government authority should contemplate include:</p>
<ul>
<li>Provide contact name consistency - aliases are a helpful mechanism for contacting the data steward for a given data set.</li>
@@ -809,24 +833,26 @@
<!-- REFERENCE: LINKED DATA COOKBOOK -->
-<section>
-<h2>References</h2>
-
-<h3>Linked Open Data Cookbook</h3>
-<p>
+<!-- <section>
+ <h2>References</h2>
+ <h3>Linked Open Data Cookbook</h3>
+ <p>
See <a href="http://www.w3.org/2011/gld/wiki/Linked_Data_Cookbook">Cookbook for Open Government Linked Data</a>.
</p>
-</section>
-
-
+ </section>
+-->
<!-- ACK -->
<section class="appendix">
<h2>Acknowledgments</h2>
This document has been produced by the Government Linked Data Working Group, and its contents reflect extensive discussion within the Working Group as a whole.
<p>
-The editors gratefully acknowledge the many contributors to this Best Practices document including: <a href="http://mhausenblas.info/#i">Michael Hausenblas</a> (MapR), <a href="http://logd.tw.rpi.edu/person/john_erickson" target="_blank">John Erickson</a> (Rensselaer Polytechnic Institute), <a href="http://3roundstones.com/about-us/leadership-team/david-wood/" target="_blank">David Wood</a> (3 Round Stones), <a href="http://data.semanticweb.org/person/bernard-vatant/">Bernard Vatant </a> (Semantic Web - Modeca), Michael Pendleton (U.S. Environmental Protection Agency), <a href="http://researcher.watson.ibm.com/researcher/view_person_subpage.php?id=3088" target="_blank">Biplav Srivastava</a> (IBM India), <a href="http://www.oeg-upm.net">Daniel Vila </a> (Ontology Engineering Group), Martín Álvarez Espinar (CTIC-Centro Tecnológico), and <a href="http://linkedgov.org">Hadley Beeman </a> (UK LinkedGov).
+The editors gratefully acknowledge the many contributors to this Best Practices document including: <a href="http://mhausenblas.info/#i">Michael Hausenblas</a> (MapR), <a href="http://logd.tw.rpi.edu/person/john_erickson" target="_blank">John Erickson</a> (Rensselaer Polytechnic Institute), <a href="http://3roundstones.com/about-us/leadership-team/david-wood/" target="_blank">David Wood</a> (3 Round Stones), <a href="http://data.semanticweb.org/person/bernard-vatant/">Bernard Vatant </a> (Semantic Web - Mondeca), Michael Pendleton (U.S. Environmental Protection Agency), <a href="http://researcher.watson.ibm.com/researcher/view_person_subpage.php?id=3088" target="_blank">Biplav Srivastava</a> (IBM India), <a href="http://www.oeg-upm.net">Daniel Vila </a> (Ontology Engineering Group), Martín Álvarez Espinar (CTIC-Centro Tecnológico), and <a href="http://linkedgov.org">Hadley Beeman </a> (UK LinkedGov).
</p>
</section>
+
+
+
+
</body>
</html>
--- a/bp/respec-config.js Thu Jun 06 10:23:55 2013 +0200
+++ b/bp/respec-config.js Mon Jun 10 11:25:29 2013 +0200
@@ -1,7 +1,7 @@
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
specStatus: "NOTE",
- publishDate: "2013-04-18",
+ publishDate: "2013-06-06",
//copyrightStart: "2010",
// the specification's short name, as in http://www.w3.org/TR/short-name/
--- a/bp/respec-ref.js Thu Jun 06 10:23:55 2013 +0200
+++ b/bp/respec-ref.js Mon Jun 10 11:25:29 2013 +0200
@@ -5,13 +5,30 @@
berjon.biblio["XHTML-RDFA"] = "<cite><a href=\"http://www.w3.org/TR/xhtml-rdfa/\">XHTML+RDFa</a></cite> Manu Sporny; et al. 31 March 2011. W3C Working Draft. URL: http://www.w3.org/TR/xhtml-rdfa/ ";
berjon.biblio["HTML-RDFA"] = "<cite><a href=\"http://dev.w3.org/html5/rdfa/\">HTML+RDFa</a></cite> Manu Sporny; et al. 24 May 2011. W3C Working Draft. URL: http://dev.w3.org/html5/rdfa/ ";
berjon.biblio["HOWTO-LODP"] = "<cite><a href=\"http://linkeddata.org/docs/how-to-publish\">How to Publish Linked Data on the Web</a></cite>, C. Bizer, R. Cyganiak, and Tom Heath, Community Tutorial 17 July 2008. URL: http://linkeddata.org/docs/how-to-publish";
- berjon.biblio["COOL-SWURIS"] = "<cite><a href=\"http://www.w3.org/TR/cooluris/\">Cool URIs for the Semantic Web</a></cite>, L. Sauermann and R. Cyganiak, W3C Interest Group Note 03 December 2008. URL: http://www.w3.org/TR/cooluris/";
+ berjon.biblio["COOL-SWURIS"] = "<cite><a href=\"http://www.w3.org/TR/cooluris/\">Cool URIs for the Semantic Web</a></cite>, L. Sauermann and R. Cyganiak, W3C Interest Group Note 03 December 2008. URL: <a href=\"http://www.w3.org/TR/cooluris/\">http://www.w3.org/TR/cooluris/</a>";
berjon.biblio["VOID-GUIDE"] = "<cite><a href=\"http://www.w3.org/TR/void/\">Describing Linked Datasets with the VoID Vocabulary</a></cite>, K. Alexander, R. Cyganiak, M. Hausenblas, and J. Zhao, W3C Interest Group Note 03 March 2011. URL: http://www.w3.org/TR/void/";
berjon.biblio["RDFA-CORE-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/rdfa-1.1\">RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 02 June 2011. URL: http://www.w3.org/profile/rdfa-1.1";
berjon.biblio["XHTML-RDFA-PROFILE"] = "<cite><a href=\"http://www.w3.org/profile/html-rdfa-1.1\">HTML+RDFa Core Default Profile</a></cite>, I. Herman, W3C RDF Web Applications Working Group 24 May 2011. URL: http://www.w3.org/profile/html-rdfa-1.1";
berjon.biblio["RFC2616"] = "<cite><a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616.html\">Hypertext Transfer Protocol -- HTTP/1.1</a></cite>, R. Fielding; et al. June 1999. Internet RFC 2616. URL: <a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616.html\">http://www.w3.org/Protocols/rfc2616/rfc2616.html</a>.";
- berjon.biblio["RFC3986"] = "<cite><a href=\"http://tools.ietf.org/html/rfc3986\">Uniform Resource Identifier (URI): Generic Syntax</a></cite>, Berners-Lee, et al. January 2005. Internet RFC 3986. URL: <a href=\"http://tools.ietf.org/html/rfc3986\">http://tools.ietf.org/html/rfc3986</a>.";
- berjon.biblio["LOD-COOKBOOK"] = "<cite><a href=\"http://www.w3.org/2011/gld/wiki/Linked_Data_Cookbook\">Cookbook for Open Government Linked Data</a></cite>, B. Hyland, B. Villazon-Terrazas, December 2011. GLD Wiki Document. URL: <a href=\"http://www.w3.org/2011/gld/wiki/Linked_Data_Cookbook\">http://www.w3.org/2011/gld/wiki/Linked_Data_Cookbook</a>.";
+ berjon.biblio["RFC3986"] = "<cite><a href=\"http://tools.ietf.org/html/rfc3986\">Uniform Resource Identifier (URI): Generic Syntax</a></cite>, Berners-Lee, et al. January 2005. Internet RFC 3986. URL: <a href=\"http://tools.ietf.org/html/rfc3986\">http://tools.ietf.org/html/rfc3986</a>.";
+ berjon.biblio["LOD-COOKBOOK"] = "<cite><a href=\"http://www.w3.org/2011/gld/wiki/Linked_Data_Cookbook\">Cookbook for Open Government Linked Data</a></cite>, B. Hyland, B. Villazon-Terrazas, December 2011. GLD Wiki Document. URL: <a href=\"http://www.w3.org/2011/gld/wiki/Linked_Data_Cookbook\">http://www.w3.org/2011/gld/wiki/Linked_Data_Cookbook</a>.";
+ berjon.biblio["DCAT"] = "<cite><a href=\"http://www.w3.org/TR/vocab-dcat/\">Data Catalog Vocabulary (DCAT)</a></cite>, F. Maali, J. Erickson, and P. Archer, 12 March 2013. W3C Working Draft. URL: <a href=\"http://www.w3.org/TR/gld/vocab-dcat/\">http://www.w3.org/TR/gld/vocab-dcat/</a>.";
+ berjon.biblio["ORG"] = "<cite><a href=\"http://www.w3.org/TR/vocab-org/\">An Organization ontology (ORG)</a></cite>, Dave Reynolds, 23 October 2013. W3C Last Call Working Draft. URL: <a href=\"http://www.w3.org/TR/gld/vocab-org/\">http://www.w3.org/TR/gld/vocab-org/</a>.";
+ berjon.biblio["QB"] = "<cite><a href=\"http://www.w3.org/TR/vocab-data-cube/\">The RDF Data Cube Vocabulary </a></cite>, R. Cyganiak, D. Reynolds, 06 June 2013. W3C Candidate Recommendation. URL: <a href=\"http://www.w3.org/TR/vocab-data-cube/\">http://www.w3.org/TR/vocab-data-cube/</a>.";
+ berjon.biblio["RDF"] = "<cite><a href=\"http://www.w3.org/TR/REC-rdf-syntax/\">RDF/XML Syntax Specification (Revised)</a></cite>, Dave Beckett (eds), 10 February 2004, W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/REC-rdf-syntax/\">http://www.w3.org/TR/REC-rdf-syntax/</a>";
+ berjon.biblio["BV5STAR"] = "<cite><a href=\"http://bvatant.blogspot.fr/2012/02/is-your-linked-data-vocabulary-5-star_9588.html/\">, Is Your Linked Data vocabulary 5 Stars</a></cite>, Bernard Vatant, 05 March 2012. URL: <a href=\"http://bvatant.blogspot.fr/2012/02/is-your-linked-data-vocabulary-5-star_9588.html\">http://bvatant.blogspot.fr/2012/02/is-your-linked-data-vocabulary-5-star_9588.html</a>";
+ berjon.biblio["SKOS-REFERENCE"] = "<cite><a href=\"http://www.w3.org/TR/2009/REC-skos-reference-20090818/\">SKOS: Simple Knowledge Organization System Reference</a></cite>, Sean Bechhofer, Alistair Miles (eds), 18 August 2009, W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/2009/REC-skos-reference-20090818/\">http://www.w3.org/TR/2009/REC-skos-reference-20090818/</a>";
+ berjon.biblio["VoID"] = "<cite><a href=\"http://www.w3.org/TR/void/\">Describing Linked Datasets with the VoID Vocabulary</a></cite>, K. Alexander, R. Cyganiak, M. Hausenblas, and J. Zhao, W3C Interest Group Note 03 March 2011. URL: <a href=\"http://www.w3.org/TR/void/\">http://www.w3.org/TR/void/</a>";
+ berjon.biblio["PROV-O"] = "<cite><a href=\"http://www.w3.org/TR/prov-o/\">PROV-O: The PROV Ontology</a></cite>, T. Lebo, S. Sahoo, and D. McGuinness, URL: http://www.w3.org/TR/2013/REC-prov-o-20130430/";
+ berjon.biblio["GEOW3C"] = "<cite><a href=\"http://www.w3.org/2003/01/geo/\">Basic Geo (WGS84 lat/long) Vocabulary</a></cite>, Dan Brickley, Tim Berners-Lee, URL: <a href=\"http://www.w3.org/2003/01/geo/\">http://www.w3.org/2003/01/geo/</a>";
+ berjon.biblio["LEXINFO"] = "<cite> Towards Linguistically Grounded Ontologies</cite>, Paul Buitelaar, Philipp Cimiano, Peter Haase, Michael Sintek, URL: <a href=\"http://lexinfo.net\">http://lexinfo.net</a>";
+ berjon.biblio["BP-PUB"] = "<cite><a href=\"http://www.w3.org/TR/swbp-vocab-pub/\"></a></cite>Diego Berrueta, Jon Phipps (eds), 28 August 2008. W3C Working Group Note URL: <a href=\"http://www.w3.org/TR/swbp-vocab-pub/\">http://www.w3.org/TR/swbp-vocab-pub/</a>";
+ berjon.biblio["BPURI-GOVUK"] = "<cite><a href=\"https://www.gov.uk/government/publications/designing-uri-sets-for-the-uk-public-sector/\">Designing URI sets for the UK public sector</a></cite>, Cabinet Office GOV.UK, 5 October 2010. URL: <a href=\"https://www.gov.uk/government/publications/designing-uri-sets-for-the-uk-public-sector\">https://www.gov.uk/government/publications/designing-uri-sets-for-the-uk-public-sector</a>";
+ berjon.biblio["I18n-WEB"] = "<cite>I18n of Semantic Web Applications</cite>, S. Auer, M. Weidl, J. Lehmann, Amrapali J. Zaveri, Key-Sun Choi, In Lecture Notes in Computer Science Volume 6497, 2010, pp 1-16 ";
+ berjon.biblio["ISA-URI"] = "<cite><a href=\"https://joinup.ec.europa.eu/sites/default/files/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf/\"> Study on persistent URIs</a></cite>, P. Archer, S. Goedertier, N. Loutas, 17 Dicember 2012. URL: <a href=\"https://joinup.ec.europa.eu/sites/default/files/D7.1.3%20-%20Study%20on%20persistent%20URIs.pdf\">D7.1.3 - Study on persistent URIs, with identification of best practices and recommendations on the topic for the MSs and the EC</a>";
+ berjon.biblio["TIAW-LEMON"] = "<cite><a href=\"http://tia2011.crim.fr/Workshop-Proceedings/pdf/TIAW15.pdf\">Ontology Lexicalisation: The lemon Perspective</a></cite>, P. Buitelaar, P. Cimiano⋆, J. McCrae, E. Montiel-Ponsoda, T. Declerck. URL: <a href=\"hhttp://tia2011.crim.fr/Workshop-Proceedings/pdf/TIAW15.pdf\">http://tia2011.crim.fr/Workshop-Proceedings/pdf/TIAW15.pdf</a>";
+ berjon.biblio["YAKEL-07"] = "<cite> Digital curation</cite> Elizabeth Yakel, (2007) , OCLC Systems & Services, Vol. 23 Iss: 4, pp.335 - 340 DOI: 10.1108/10650750710831466";
+
// process the document before anything else is done
var refs = document.querySelectorAll('adef') ;
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/data-cube/vocab/cube.rdf Mon Jun 10 11:25:29 2013 +0200
@@ -0,0 +1,342 @@
+<rdf:RDF
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:skos="http://www.w3.org/2004/02/skos/core#"
+ xmlns:foaf="http://xmlns.com/foaf/0.1/"
+ xmlns:scovo="http://purl.org/NET/scovo#"
+ xmlns:owl="http://www.w3.org/2002/07/owl#"
+ xmlns:dcterms="http://purl.org/dc/terms/"
+ xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
+ xmlns:void="http://rdfs.org/ns/void#"
+ xmlns:qb="http://purl.org/linked-data/cube#"
+ xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
+ <owl:Ontology rdf:about="http://purl.org/linked-data/cube">
+ <dcterms:contributor rdf:parseType="Resource">
+ <foaf:mbox>richard@cyganiak.de</foaf:mbox>
+ </dcterms:contributor>
+ <owl:versionInfo>0.2</owl:versionInfo>
+ <dcterms:contributor rdf:parseType="Resource">
+ <foaf:mbox>ian@epimorphics.com</foaf:mbox>
+ </dcterms:contributor>
+ <dcterms:title>Vocabulary for multi-dimensional (e.g. statistical) data publishing</dcterms:title>
+ <rdfs:label>The data cube vocabulary</rdfs:label>
+ <dcterms:contributor rdf:parseType="Resource">
+ <foaf:mbox>arofan.gregory@earthlink.net</foaf:mbox>
+ </dcterms:contributor>
+ <dcterms:contributor rdf:parseType="Resource">
+ <foaf:mbox>dave@epimorphics.com</foaf:mbox>
+ </dcterms:contributor>
+ <dcterms:contributor rdf:parseType="Resource">
+ <foaf:mbox>jeni@jenitennison.com</foaf:mbox>
+ </dcterms:contributor>
+ <dcterms:license rdf:resource="http://www.opendatacommons.org/licenses/pddl/1.0/"/>
+ <dcterms:created rdf:datatype="http://www.w3.org/2001/XMLSchema#date"
+ >2010-07-12</dcterms:created>
+ <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#date"
+ >2010-11-27</dcterms:modified>
+ <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#date"
+ >2013-03-02</dcterms:modified>
+ <rdfs:comment>This vocabulary allows multi-dimensional data, such as statistics, to be published in RDF. It is based on the core information model from SDMX (and thus also DDI).</rdfs:comment>
+ </owl:Ontology>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#DataSet">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Data set</rdfs:label>
+ <rdfs:comment xml:lang="en">Represents a collection of observations, possibly organized into various slices, conforming to some common dimensional structure.</rdfs:comment>
+ <rdfs:subClassOf>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#Attachable"/>
+ </rdfs:subClassOf>
+ <owl:equivalentClass rdf:resource="http://purl.org/NET/scovo#Dataset"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#MeasureProperty">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Measure property</rdfs:label>
+ <rdfs:comment xml:lang="en">The class of components which represent the measured value of the phenomenon being observed</rdfs:comment>
+ <rdfs:subClassOf>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#ComponentProperty"/>
+ </rdfs:subClassOf>
+ <owl:disjointWith>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#AttributeProperty"/>
+ </owl:disjointWith>
+ <owl:disjointWith>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#DimensionProperty"/>
+ </owl:disjointWith>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#Slice">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:subClassOf>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#ObservationGroup"/>
+ </rdfs:subClassOf>
+ <rdfs:label xml:lang="en">Slice</rdfs:label>
+ <rdfs:comment xml:lang="en">Denotes a subset of a DataSet defined by fixing a subset of the dimensional values, component properties on the Slice</rdfs:comment>
+ <rdfs:subClassOf>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#Attachable"/>
+ </rdfs:subClassOf>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#ComponentSpecification">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Component specification</rdfs:label>
+ <rdfs:comment xml:lang="en">Used to define properties of a component (attribute, dimension etc) which are specific to its usage in a DSD.</rdfs:comment>
+ <rdfs:subClassOf>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#ComponentSet"/>
+ </rdfs:subClassOf>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#ComponentSet">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Component set</rdfs:label>
+ <rdfs:comment xml:lang="en">Abstract class of things which reference one or more ComponentProperties</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#AttributeProperty">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Attribute property</rdfs:label>
+ <rdfs:comment xml:lang="en">The class of components which represent attributes of observations in the cube, e.g. unit of measurement</rdfs:comment>
+ <rdfs:subClassOf>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#ComponentProperty"/>
+ </rdfs:subClassOf>
+ <owl:disjointWith rdf:resource="http://purl.org/linked-data/cube#MeasureProperty"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#Attachable">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Attachable (abstract)</rdfs:label>
+ <rdfs:comment xml:lang="en">Abstract superclass for everything that can have attributes and dimensions</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#ComponentProperty">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Component property (abstract)</rdfs:label>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
+ <rdfs:comment xml:lang="en">Abstract super-property of all properties representing dimensions, attributes or measures</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#DataStructureDefinition">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Data structure definition</rdfs:label>
+ <rdfs:comment xml:lang="en">Defines the structure of a DataSet or slice</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://purl.org/linked-data/cube#ComponentSet"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#DimensionProperty">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Dimension property</rdfs:label>
+ <rdfs:comment xml:lang="en">The class of components which represent the dimensions of the cube</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://purl.org/linked-data/cube#ComponentProperty"/>
+ <rdfs:subClassOf>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#CodedProperty"/>
+ </rdfs:subClassOf>
+ <owl:disjointWith rdf:resource="http://purl.org/linked-data/cube#MeasureProperty"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#CodedProperty">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Coded property</rdfs:label>
+ <rdfs:subClassOf rdf:resource="http://purl.org/linked-data/cube#ComponentProperty"/>
+ <rdfs:comment xml:lang="en">Superclass of all coded ComponentProperties</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#HierarchicalCodeList">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:subClassOf rdf:resource="http://purl.org/linked-data/cube#CodeList"/>
+ <rdfs:label xml:lang="en">Hierarchical Code List</rdfs:label>
+ <rdfs:comment xml:lang="en">Represents a generalized hierarchy of concepts which can be used for coding. The hierarchy is defined by one or more roots together with a property which relates concepts in the hierarchy to thier child concept . The same concepts may be members of multiple hierarchies provided that different qb:parentChildProperty values are used for each hierarchy.</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#ObservationGroup">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Observation Group</rdfs:label>
+ <rdfs:comment xml:lang="en">A, possibly arbitrary, group of observations.</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#Observation">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Observation</rdfs:label>
+ <rdfs:comment xml:lang="en">A single observation in the cube, may have one or more associated measured values</rdfs:comment>
+ <rdfs:subClassOf rdf:resource="http://purl.org/linked-data/cube#Attachable"/>
+ <owl:equivalentClass rdf:resource="http://purl.org/NET/scovo#Item"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#SliceKey">
+ <rdfs:subClassOf rdf:resource="http://purl.org/linked-data/cube#ComponentSet"/>
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#Class"/>
+ <rdfs:label xml:lang="en">Slice key</rdfs:label>
+ <rdfs:comment xml:lang="en">Denotes a subset of the component properties of a DataSet which are fixed in the corresponding slices</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdfs:Class>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#order">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#DatatypeProperty"/>
+ <rdfs:label xml:lang="en">order</rdfs:label>
+ <rdfs:comment xml:lang="en">indicates a priority order for the components of sets with this structure, used to guide presentations - lower order numbers come before higher numbers, un-numbered components come last</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#ComponentSpecification"/>
+ <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#int"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#codeList">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">code list</rdfs:label>
+ <rdfs:comment xml:lang="en">gives the code list associated with a CodedProperty</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#CodedProperty"/>
+ <rdfs:range rdf:parseType="Resource">
+ <owl:unionOf rdf:parseType="Collection">
+ <rdf:Description rdf:about="http://www.w3.org/2004/02/skos/core#ConceptScheme"/>
+ <rdf:Description rdf:about="http://www.w3.org/2004/02/skos/core#Collection"/>
+ <rdfs:Class rdf:about="http://purl.org/linked-data/cube#HierarchicalCodeList"/>
+ </owl:unionOf>
+ </rdfs:range>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#observationGroup">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">observation group</rdfs:label>
+ <rdfs:comment xml:lang="en">Indicates a group of observations. The domain of this property is left open so that a group may be attached to different resources and need not be restricted to a single DataSet</rdfs:comment>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#ObservationGroup"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#structure">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">structure</rdfs:label>
+ <rdfs:comment xml:lang="en">indicates the structure to which this data set conforms</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#DataSet"/>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#DataStructureDefinition"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#componentAttachment">
+ <rdfs:label xml:lang="en">component attachment</rdfs:label>
+ <rdfs:comment xml:lang="en">Indicates the level at which the component property should be attached, this might an qb:DataSet, qb:Slice or qb:Observation, or a qb:MeasureProperty.</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#ComponentSpecification"/>
+ <rdfs:range rdf:resource="http://www.w3.org/2000/01/rdf-schema#Class"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#sliceKey">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">slice key</rdfs:label>
+ <rdfs:comment xml:lang="en">indicates a slice key which is used for slices in this dataset</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#DataSet"/>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#SliceKey"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#observation">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">observation</rdfs:label>
+ <rdfs:comment xml:lang="en">indicates a observation contained within this slice of the data set</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#ObservationGroup"/>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#Observation"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#dimension">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">dimension</rdfs:label>
+ <rdfs:comment xml:lang="en">An alternative to qb:componentProperty which makes explicit that the component is a dimension</rdfs:comment>
+ <rdfs:subPropertyOf>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#componentProperty"/>
+ </rdfs:subPropertyOf>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#DimensionProperty"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#componentProperty">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">component</rdfs:label>
+ <rdfs:comment xml:lang="en">indicates a ComponentProperty (i.e. attribute/dimension) expected on a DataSet, or a dimension fixed in a SliceKey</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#ComponentSet"/>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#ComponentProperty"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#sliceStructure">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">slice structure</rdfs:label>
+ <rdfs:comment xml:lang="en">indicates the sub-key corresponding to this slice</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#Slice"/>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#SliceKey"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#component">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">component specification</rdfs:label>
+ <rdfs:comment xml:lang="en">indicates a component specification which is included in the structure of the dataset</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#DataStructureDefinition"/>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#ComponentSpecification"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#measure">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">measure</rdfs:label>
+ <rdfs:comment xml:lang="en">An alternative to qb:componentProperty which makes explicit that the component is a measure</rdfs:comment>
+ <rdfs:subPropertyOf rdf:resource="http://purl.org/linked-data/cube#componentProperty"/>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#MeasureProperty"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#measureDimension">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">measure dimension</rdfs:label>
+ <rdfs:comment xml:lang="en">An alternative to qb:componentProperty which makes explicit that the component is a measure dimension</rdfs:comment>
+ <rdfs:subPropertyOf rdf:resource="http://purl.org/linked-data/cube#componentProperty"/>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#DimensionProperty"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#componentRequired">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#DatatypeProperty"/>
+ <rdfs:label xml:lang="en">component required</rdfs:label>
+ <rdfs:comment xml:lang="en">Indicates whether a component property is required (true) or optional (false) in the context of a DSD. Only applicable
+ to components correspond to an attribute. Defaults to false (optional).</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#ComponentSpecification"/>
+ <rdfs:range rdf:resource="http://www.w3.org/2001/XMLSchema#boolean"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#slice">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:subPropertyOf rdf:resource="http://purl.org/linked-data/cube#observationGroup"/>
+ <rdfs:label xml:lang="en">slice</rdfs:label>
+ <rdfs:comment xml:lang="en">Indicates a subset of a DataSet defined by fixing a subset of the dimensional values</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#DataSet"/>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#Slice"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#parentChildProperty">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">parent-child property</rdfs:label>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#HierarchicalCodeList"/>
+ <rdfs:range rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
+ <rdfs:comment xml:lang="en">Specifies a property which relates a parent concept in the hierarchy to a child concept.</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#attribute">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">attribute</rdfs:label>
+ <rdfs:comment xml:lang="en">An alternative to qb:componentProperty which makes explicit that the component is a attribute</rdfs:comment>
+ <rdfs:subPropertyOf rdf:resource="http://purl.org/linked-data/cube#componentProperty"/>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#AttributeProperty"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#hierarchyRoot">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#HierarchicalCodeList"/>
+ <rdfs:comment xml:lang="en">Specifies a root of the hierarchy. A hierarchy may have multiple roots but must have at least one.</rdfs:comment>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#dataSet">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">data set</rdfs:label>
+ <rdfs:comment xml:lang="en">indicates the data set of which this observation is a part</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#Observation"/>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#DataSet"/>
+ <owl:equivalentProperty rdf:resource="http://purl.org/NET/scovo#dataset"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <rdf:Property rdf:about="http://purl.org/linked-data/cube#concept">
+ <rdf:type rdf:resource="http://www.w3.org/2002/07/owl#ObjectProperty"/>
+ <rdfs:label xml:lang="en">concept</rdfs:label>
+ <rdfs:comment xml:lang="en">gives the concept which is being measured or indicated by a ComponentProperty</rdfs:comment>
+ <rdfs:domain rdf:resource="http://purl.org/linked-data/cube#ComponentProperty"/>
+ <rdfs:range rdf:resource="http://www.w3.org/2004/02/skos/core#Concept"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </rdf:Property>
+ <qb:DimensionProperty rdf:about="http://purl.org/linked-data/cube#measureType">
+ <rdf:type rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#Property"/>
+ <rdfs:label xml:lang="en">measure type</rdfs:label>
+ <rdfs:comment xml:lang="en">Generic measure dimension, the value of this dimension indicates which measure (from the set of measures in the DSD) is being given by the obsValue (or other primary measure)</rdfs:comment>
+ <rdfs:range rdf:resource="http://purl.org/linked-data/cube#MeasureProperty"/>
+ <rdfs:isDefinedBy rdf:resource="http://purl.org/linked-data/cube"/>
+ </qb:DimensionProperty>
+</rdf:RDF>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/data-cube/vocab/cube.ttl Mon Jun 10 11:25:29 2013 +0200
@@ -0,0 +1,339 @@
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
+@prefix owl: <http://www.w3.org/2002/07/owl#> .
+@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
+@prefix foaf: <http://xmlns.com/foaf/0.1/> .
+@prefix scovo: <http://purl.org/NET/scovo#> .
+@prefix void: <http://rdfs.org/ns/void#> .
+@prefix qb: <http://purl.org/linked-data/cube#> .
+@prefix dcterms: <http://purl.org/dc/terms/> .
+
+<http://purl.org/linked-data/cube>
+ a owl:Ontology;
+ owl:versionInfo "0.2";
+ rdfs:label "The data cube vocabulary";
+ rdfs:comment "This vocabulary allows multi-dimensional data, such as statistics, to be published in RDF. It is based on the core information model from SDMX (and thus also DDI).";
+ dcterms:created "2010-07-12"^^xsd:date;
+ dcterms:modified "2010-11-27"^^xsd:date;
+ dcterms:modified "2013-03-02"^^xsd:date;
+ dcterms:title "Vocabulary for multi-dimensional (e.g. statistical) data publishing";
+ dcterms:license <http://www.opendatacommons.org/licenses/pddl/1.0/> ;
+ dcterms:contributor [foaf:mbox "richard@cyganiak.de"],
+ [foaf:mbox "jeni@jenitennison.com"],
+ [foaf:mbox "arofan.gregory@earthlink.net"],
+ [foaf:mbox "ian@epimorphics.com"],
+ [foaf:mbox "dave@epimorphics.com"];
+ .
+
+# --- DataSets ---------------------------
+
+qb:DataSet a rdfs:Class, owl:Class;
+ rdfs:label "Data set"@en;
+ rdfs:comment "Represents a collection of observations, possibly organized into various slices, conforming to some common dimensional structure."@en;
+ rdfs:subClassOf qb:Attachable;
+ owl:equivalentClass scovo:Dataset;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+# --- Observations ---------------------------
+
+qb:Observation a rdfs:Class, owl:Class;
+ rdfs:label "Observation"@en;
+ rdfs:comment "A single observation in the cube, may have one or more associated measured values"@en;
+ rdfs:subClassOf qb:Attachable;
+ owl:equivalentClass scovo:Item;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:dataSet a rdf:Property, owl:ObjectProperty;
+ rdfs:label "data set"@en;
+ rdfs:comment "indicates the data set of which this observation is a part"@en;
+ rdfs:domain qb:Observation;
+ rdfs:range qb:DataSet;
+ owl:equivalentProperty scovo:dataset;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:observation a rdf:Property, owl:ObjectProperty;
+ rdfs:label "observation"@en;
+ rdfs:comment "indicates a observation contained within this slice of the data set"@en;
+ rdfs:domain qb:ObservationGroup;
+ rdfs:range qb:Observation;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:ObservationGroup a rdfs:Class, owl:Class;
+ rdfs:label "Observation Group"@en;
+ rdfs:comment "A, possibly arbitrary, group of observations."@en;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:observationGroup a rdf:Property, owl:ObjectProperty;
+ rdfs:label "observation group"@en;
+ rdfs:comment "Indicates a group of observations. The domain of this property is left open so that a group may be attached to different resources and need not be restricted to a single DataSet"@en;
+ rdfs:range qb:ObservationGroup;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+# --- Slices ---------------------------
+
+qb:Slice a rdfs:Class, owl:Class;
+ rdfs:subClassOf qb:ObservationGroup;
+ rdfs:label "Slice"@en;
+ rdfs:comment "Denotes a subset of a DataSet defined by fixing a subset of the dimensional values, component properties on the Slice"@en;
+ rdfs:subClassOf qb:Attachable;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:slice a rdf:Property, owl:ObjectProperty;
+ rdfs:subPropertyOf qb:observationGroup;
+ rdfs:label "slice"@en;
+ rdfs:comment "Indicates a subset of a DataSet defined by fixing a subset of the dimensional values"@en;
+ rdfs:domain qb:DataSet;
+ rdfs:range qb:Slice;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+# Removed see http://www.w3.org/2011/gld/track/issues/34
+#qb:subSlice a rdf:Property, owl:ObjectProperty;
+# rdfs:label "sub slice"@en;
+# rdfs:comment "Indicates a narrower slice which has additional fixed dimensional values, for example a time-series slice might a subSlice of a slice which spans both time and geographic area"@en;
+# rdfs:domain qb:Slice;
+# rdfs:range qb:Slice;
+# rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+# .
+
+# --- Dimensions, Attributes, Measures ---------------------------
+
+qb:Attachable a rdfs:Class, owl:Class;
+ rdfs:label "Attachable (abstract)"@en;
+ rdfs:comment "Abstract superclass for everything that can have attributes and dimensions"@en;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:ComponentProperty a rdfs:Class, owl:Class;
+ rdfs:label "Component property (abstract)"@en;
+ rdfs:subClassOf rdf:Property;
+ rdfs:comment "Abstract super-property of all properties representing dimensions, attributes or measures"@en;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+qb:DimensionProperty a rdfs:Class, owl:Class;
+ rdfs:label "Dimension property"@en;
+ rdfs:comment "The class of components which represent the dimensions of the cube"@en;
+ rdfs:subClassOf qb:ComponentProperty;
+ rdfs:subClassOf qb:CodedProperty;
+ owl:disjointWith qb:MeasureProperty;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+qb:AttributeProperty a rdfs:Class, owl:Class;
+ rdfs:label "Attribute property"@en;
+ rdfs:comment "The class of components which represent attributes of observations in the cube, e.g. unit of measurement"@en;
+ rdfs:subClassOf qb:ComponentProperty;
+ owl:disjointWith qb:MeasureProperty;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+qb:MeasureProperty a rdfs:Class, owl:Class;
+ rdfs:label "Measure property"@en;
+ rdfs:comment "The class of components which represent the measured value of the phenomenon being observed"@en;
+ rdfs:subClassOf qb:ComponentProperty;
+ owl:disjointWith qb:AttributeProperty;
+ owl:disjointWith qb:DimensionProperty;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+qb:CodedProperty a rdfs:Class, owl:Class;
+ rdfs:label "Coded property"@en;
+ rdfs:subClassOf qb:ComponentProperty;
+ rdfs:comment "Superclass of all coded ComponentProperties"@en;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+# --- Reusable general purpose component properties ---------------------------
+
+qb:measureType a qb:DimensionProperty, rdf:Property;
+ rdfs:label "measure type"@en;
+ rdfs:comment "Generic measure dimension, the value of this dimension indicates which measure (from the set of measures in the DSD) is being given by the obsValue (or other primary measure)"@en;
+ rdfs:range qb:MeasureProperty;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+# --- Data Structure Definitions ---------------------------
+
+qb:DataStructureDefinition a rdfs:Class, owl:Class;
+ rdfs:label "Data structure definition"@en;
+ rdfs:comment "Defines the structure of a DataSet or slice"@en;
+ rdfs:subClassOf qb:ComponentSet ;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:structure a rdf:Property, owl:ObjectProperty;
+ rdfs:label "structure"@en;
+ rdfs:comment "indicates the structure to which this data set conforms"@en;
+ rdfs:domain qb:DataSet;
+ rdfs:range qb:DataStructureDefinition;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+
+qb:component a rdf:Property, owl:ObjectProperty;
+ rdfs:label "component specification"@en;
+ rdfs:comment "indicates a component specification which is included in the structure of the dataset"@en;
+ rdfs:domain qb:DataStructureDefinition;
+ rdfs:range qb:ComponentSpecification;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+# --- Component specifications - for qualifying component use in a DSD ---------------------------
+
+qb:ComponentSpecification a rdfs:Class, owl:Class ;
+ rdfs:label "Component specification"@en;
+ rdfs:comment """Used to define properties of a component (attribute, dimension etc) which are specific to its usage in a DSD."""@en;
+ rdfs:subClassOf qb:ComponentSet ;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:ComponentSet a rdfs:Class, owl:Class;
+ rdfs:label "Component set"@en;
+ rdfs:comment "Abstract class of things which reference one or more ComponentProperties"@en;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+qb:ComponentSpecification rdfs:subClassOf qb:ComponentSet .
+qb:SliceKey rdfs:subClassOf qb:ComponentSet .
+
+qb:componentProperty a rdf:Property, owl:ObjectProperty;
+ rdfs:label "component"@en;
+ rdfs:comment "indicates a ComponentProperty (i.e. attribute/dimension) expected on a DataSet, or a dimension fixed in a SliceKey"@en;
+ rdfs:domain qb:ComponentSet;
+ rdfs:range qb:ComponentProperty;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:order a rdf:Property, owl:DatatypeProperty;
+ rdfs:label "order"@en;
+ rdfs:comment """indicates a priority order for the components of sets with this structure, used to guide presentations - lower order numbers come before higher numbers, un-numbered components come last"""@en;
+ rdfs:domain qb:ComponentSpecification;
+ rdfs:range xsd:int;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:componentRequired a rdf:Property, owl:DatatypeProperty;
+ rdfs:label "component required"@en;
+ rdfs:comment """Indicates whether a component property is required (true) or optional (false) in the context of a DSD. Only applicable
+ to components correspond to an attribute. Defaults to false (optional)."""@en;
+ rdfs:domain qb:ComponentSpecification;
+ rdfs:range xsd:boolean;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:componentAttachment a rdf:Property;
+ rdfs:label "component attachment"@en;
+ rdfs:comment """Indicates the level at which the component property should be attached, this might an qb:DataSet, qb:Slice or qb:Observation, or a qb:MeasureProperty."""@en;
+ rdfs:domain qb:ComponentSpecification;
+ rdfs:range rdfs:Class;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:dimension a rdf:Property, owl:ObjectProperty;
+ rdfs:label "dimension"@en;
+ rdfs:comment "An alternative to qb:componentProperty which makes explicit that the component is a dimension"@en;
+ rdfs:subPropertyOf qb:componentProperty;
+ rdfs:range qb:DimensionProperty;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:measure a rdf:Property, owl:ObjectProperty;
+ rdfs:label "measure"@en;
+ rdfs:comment "An alternative to qb:componentProperty which makes explicit that the component is a measure"@en;
+ rdfs:subPropertyOf qb:componentProperty;
+ rdfs:range qb:MeasureProperty;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:attribute a rdf:Property, owl:ObjectProperty;
+ rdfs:label "attribute"@en;
+ rdfs:comment "An alternative to qb:componentProperty which makes explicit that the component is a attribute"@en;
+ rdfs:subPropertyOf qb:componentProperty;
+ rdfs:range qb:AttributeProperty;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:measureDimension a rdf:Property, owl:ObjectProperty;
+ rdfs:label "measure dimension"@en;
+ rdfs:comment "An alternative to qb:componentProperty which makes explicit that the component is a measure dimension"@en;
+ rdfs:subPropertyOf qb:componentProperty;
+ rdfs:range qb:DimensionProperty;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+# --- Slice definitions ---------------------------
+
+qb:SliceKey a rdfs:Class, owl:Class;
+ rdfs:label "Slice key"@en;
+ rdfs:comment "Denotes a subset of the component properties of a DataSet which are fixed in the corresponding slices"@en;
+ rdfs:subClassOf qb:ComponentSet ;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:sliceStructure a rdf:Property, owl:ObjectProperty;
+ rdfs:label "slice structure"@en;
+ rdfs:comment "indicates the sub-key corresponding to this slice"@en;
+ rdfs:domain qb:Slice;
+ rdfs:range qb:SliceKey;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:sliceKey a rdf:Property, owl:ObjectProperty;
+ rdfs:label "slice key"@en;
+ rdfs:comment "indicates a slice key which is used for slices in this dataset"@en;
+ rdfs:domain qb:DataSet;
+ rdfs:range qb:SliceKey;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+# --- Concepts ---------------------------
+
+qb:concept a rdf:Property, owl:ObjectProperty;
+ rdfs:label "concept"@en;
+ rdfs:comment "gives the concept which is being measured or indicated by a ComponentProperty"@en;
+ rdfs:domain qb:ComponentProperty;
+ rdfs:range skos:Concept;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:codeList a rdf:Property, owl:ObjectProperty;
+ rdfs:label "code list"@en;
+ rdfs:comment "gives the code list associated with a CodedProperty"@en;
+ rdfs:domain qb:CodedProperty;
+ rdfs:range [ owl:unionOf (skos:ConceptScheme skos:Collection qb:HierarchicalCodeList)] ;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:HierarchicalCodeList a rdfs:Class, owl:Class;
+ rdfs:subClassOf qb:CodeList;
+ rdfs:label "Hierarchical Code List"@en;
+ rdfs:comment "Represents a generalized hierarchy of concepts which can be used for coding. The hierarchy is defined by one or more roots together with a property which relates concepts in the hierarchy to thier child concept . The same concepts may be members of multiple hierarchies provided that different qb:parentChildProperty values are used for each hierarchy."@en;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:hierarchyRoot a rdf:Property, owl:ObjectProperty;
+ rdfs:domain qb:HierarchicalCodeList;
+ rdfs:comment "Specifies a root of the hierarchy. A hierarchy may have multiple roots but must have at least one."@en;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+qb:parentChildProperty a rdf:Property, owl:ObjectProperty;
+ rdfs:label "parent-child property"@en;
+ rdfs:domain qb:HierarchicalCodeList;
+ rdfs:range rdf:Property;
+ rdfs:comment "Specifies a property which relates a parent concept in the hierarchy to a child concept."@en;
+ rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+ .
+
+#qb:AggregatableHierarchy
+# rdfs:label "Aggregatable Hierarchy"@en;
+# rdfs:subClassOf qb:HierarchicalCodeList;
+# rdfs:comment "Indicates a hierarchy in which each parent concept is a disjoint union of its child concepts. So that measures such as simple counts may be aggregated up the hierarchy."@en;
+# rdfs:isDefinedBy <http://purl.org/linked-data/cube>;
+# .
+
+
--- a/legal/index.html Thu Jun 06 10:23:55 2013 +0200
+++ b/legal/index.html Mon Jun 10 11:25:29 2013 +0200
@@ -1,15 +1,12 @@
-<!DOCTYPE html>
-<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
-<head>
- <title>Registered Organization Vocabulary</title>
- <meta name="description" content="A vocabulary for describing organizations that gain legal entity status through a formal registration process." />
- <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
- <!--[if lt IE 9]>
- <script src="http://www.w3.org/2008/site/js/html5shiv.js"></script> <![endif]-->
- <script type="text/javascript" src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove"></script>
- <script src="respec-ref.js"></script>
- <script src="respec-config.js"></script>
- <style type="text/css">
+ <!DOCTYPE html>
+ <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en" dir="ltr">
+ <head>
+ <title>Registered Organization Vocabulary</title>
+ <meta name="description" content="A vocabulary for describing organizations that gain legal entity status through a formal registration process.">
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+ <!--[if lt IE 9]>
+ <script src="http://www.w3.org/2008/site/js/html5shiv.js"></script> <![endif]-->
+ <style type="text/css">
table {
border-collapse:collapse;
}
@@ -21,25 +18,6 @@
table#namespaces td {
font-family: monospace;
}
- table tr.midtable th {
- border-top: black medium double;
- }
- .editorsnote::before {
- content: "Editor's Note";
- display: block;
- width: 150px;
- background: #F30023;
- color: #fff;
- margin: -1.5em 0 0.5em 0;
- font-weight: bold;
- border: 1px solid #cff6d9;
- padding: 3px 1em;
- }
- .editorsnote {
- margin: 1em 0em 1em 1em;
- padding: 1em;
- border: 2px solid #cff6d9;
- }
pre {
padding: 1em;
border: 1px dashed #2f6fab;
@@ -71,398 +49,1228 @@
margin: 0 0.3em;
line-height:1.5em;
}
- </style>
-</head>
-<body>
-<section id="abstract">
-<p>The Registered Organization Vocabulary is a profile of the Organization Ontology for describing
+/*****************************************************************
+ * ReSpec CSS
+ * Robin Berjon (robin at berjon dot com)
+ * v0.05 - 2009-07-31
+ *****************************************************************/
+
+/* --- INLINES --- */
+em.rfc2119 {
+ text-transform: lowercase;
+ font-variant: small-caps;
+ font-style: normal;
+ color: #900;
+}
+
+a.bibref {
+ text-decoration: none;
+}
+
+code {
+ color: #ff4500;
+}
+
+h1 abbr, h2 abbr, h3 abbr {border:none}
+
+/* --- TOC --- */
+.toc a {
+ text-decoration: none;
+}
+
+a .secno {
+ color: #000;
+}
+
+/* --- DL --- */
+.section dd > p:first-child {
+ margin-top: 0;
+}
+
+.section dd > p:last-child {
+ margin-bottom: 0;
+}
+
+.section dd {
+ margin-bottom: 1em;
+}
+
+.section dl.attrs dd, .section dl.eldef dd {
+ margin-bottom: 0;
+}
+</style>
+ <link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-WG-NOTE"/>
+ </head>
+ <body style="display: inherit;">
+ <div class="head">
+ <p>
+ <a href="http://www.w3.org/">
+ <img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C">
+ </a>
+ </p>
+ <h1 class="title" id="title">Registered Organization Vocabulary</h1>
+ <h2 id="w3c-note-11-june-2013"><abbr title="World Wide Web Consortium">W3C</abbr> Working Group Note 11 June 2013</h2>
+ <dl>
+ <dt>This version:</dt>
+ <dd>
+ <a href="http://www.w3.org/TR/2013/NOTE-vocab-regorg-20130611/">http://www.w3.org/TR/2013/NOTE-vocab-regorg-20130611/</a>
+ </dd>
+ <dt>Latest published version:</dt>
+ <dd>
+ <a href="http://www.w3.org/TR/vocab-regorg/">http://www.w3.org/TR/vocab-regorg/</a>
+ </dd>
+ <dt>Previous version:</dt>
+ <dd>
+ <a href="http://www.w3.org/TR/2013/NOTE-vocab-regorg-20130528/">http://www.w3.org/TR/2013/NOTE-vocab-regorg-20130528/</a>
+ </dd>
+ <dt>Editors:</dt>
+ <dd>
+ <a href="http://www.w3.org/People/all#phila">Phil Archer</a>, <a href="http://www.w3.org"> <abbr title="World Wide Web Consortium">W3C</abbr> / <abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>
+ </dd>
+ <dd>
+ <a href="http://www.ntua.gr/">Marios Meimaris</a>
+ ,
+ <a href="http://www.ntua.gr/">National Technical University of Athens (Invited Expert)</a> (from 1 March 2013)
+ </dd>
+ <dd>
+ <a href="http://www.ntua.gr/">Agisilaos Papantoniou</a>
+ ,
+ <a href="http://www.ntua.gr/">National Technical University of Athens (Invited Expert)</a> (until 28 Feb 2013)
+ </dd>
+ </dl>
+ <p>The vocabulary defined in this document is also available in these non-normative formats: <a href="http://www.w3.org/ns/regorg.rdf">RDF/XML</a> and <a href="http://www.w3.org/ns/regorg.ttl">Turtle</a>.</p>
+ <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2013 <a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>, <a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p>
+ <hr>
+ </div>
+ <div id="abstract" class="introductory section">
+ <h2>Abstract</h2>
+ <p>The Registered Organization Vocabulary is a profile of the Organization Ontology for describing
organizations that have gained legal entity status through a formal registration process,
typically in a national or regional register.</p>
-<p>@@@ Move above the HR in publication version@@@ Terms in the ROV namespace are available in both <a href="regorg20130508.rdf">RDF/XML</a> and <a href="regorg20130508.ttl">Turtle</a>.</pa>
-</section>
-
-<section id="sotd">
-
-</section>
-
-<section class="informative">
-<h2 id="intro">Introduction</h2>
-<p>This is a vocabulary for describing organizations that have gained legal entity status
+ </div>
+ <div id="sotd" class="introductory section">
+ <h2>Status of This Document</h2>
+ <p>
+ <em>
+ This section describes the status of this document at the time of its publication. Other documents may supersede this document. 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="http://www.w3.org/TR/">
+ <abbr title="World Wide Web Consortium">W3C</abbr>
+ technical reports index
+ </a>
+ at http://www.w3.org/TR/.
+ </em>
+ </p>
+ <p>
+ This document was published by the
+ <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a>
+ as a Note. If you wish to make comments regarding this document, please send them to
+ <a href="mailto:public-gld-comments@w3.org">public-gld-comments@w3.org</a>
+ (
+ <a href="mailto:public-gld-comments-request@w3.org?subject=subscribe">subscribe</a>
+ ,
+ <a href="http://lists.w3.org/Archives/Public/public-gld-comments/">archives</a>
+ ). All feedback is welcome.
+ </p>
+<p>The only changes made since the <a href="http://www.w3.org/TR/2013/NOTE-vocab-regorg-20130528/">previous version</a>
+of this document concern the acknowledgement section. No substantive changes have been made.</p>
+<p>Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p>
+ <p> This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February
+ 2004 W3C Patent Policy</a>. W3C maintains a <a rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/47663/status">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="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a>
+ must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
+ 6 of the W3C Patent Policy</a>. </p>
+ </div>
+ <div id="toc" class="section">
+ <h2 class="introductory">Table of Contents</h2>
+ <ul class="toc">
+ <li class="tocline">
+ <a href="#introduction" class="tocxref">
+ <span class="secno">1. </span>
+ Introduction
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#ns" class="tocxref">
+ <span class="secno">2. </span>
+ Namespaces
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#overview-of-the-vocabulary" class="tocxref">
+ <span class="secno">3. </span>
+ Overview of the vocabulary
+ </a>
+ <ul class="toc">
+ <li class="tocline">
+ <a href="#vocIndex" class="tocxref">
+ <span class="secno">3.1 </span>
+ Vocabulary index
+ </a>
+ </li>
+ </ul>
+ </li>
+ <li class="tocline">
+ <a href="#regorg-usage" class="tocxref">
+ <span class="secno">4. </span>
+ RegOrg Usage
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#relationship-with-the-organization-ontology" class="tocxref">
+ <span class="secno">5. </span>
+ Relationship with the Organization Ontology
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#vocabDef" class="tocxref">
+ <span class="secno">6. </span>
+ Vocabulary Definitions
+ </a>
+ <ul class="toc">
+ <li class="tocline">
+ <a href="#the-registered-organization-class" class="tocxref">
+ <span class="secno">6.1 </span>
+ The Registered Organization Class
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#properties" class="tocxref">
+ <span class="secno">6.2 </span>
+ Properties
+ </a>
+ </li>
+ </ul>
+ </li>
+ <li class="tocline">
+ <a href="#conformance" class="tocxref">
+ <span class="secno">7. </span>
+ Conformance
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#changelog" class="tocxref">
+ <span class="secno">A. </span>
+ Change Log
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#app13" class="tocxref">
+ <span class="secno">B. </span>
+ Note on identifier and classification properties
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#acknowledgements" class="tocxref">
+ <span class="secno">C. </span>
+ Acknowledgements
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#references" class="tocxref">
+ <span class="secno">D. </span>
+ References
+ </a>
+ <ul class="toc">
+ <li class="tocline">
+ <a href="#normative-references" class="tocxref">
+ <span class="secno">D.1 </span>
+ Normative references
+ </a>
+ </li>
+ <li class="tocline">
+ <a href="#informative-references" class="tocxref">
+ <span class="secno">D.2 </span>
+ Informative references
+ </a>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ </div>
+ <div class="informative section" id="introduction">
+ <!--OddPage-->
+ <h2 id="intro">
+ <span class="secno">1. </span>
+ Introduction
+ </h2>
+ <p>
+ <em>This section is non-normative.</em>
+ </p>
+ <p>
+ This is a vocabulary for describing organizations that have gained legal entity status
through a formal registration process, typically in a national or regional register.
It focuses solely on such organizations and excludes natural persons, virtual organizations
and other types of legal entity or 'agent' that are able to act. It is a profile of the more
-flexible and comprehensive Organization Ontology [[ORG]]. The relationship between the Registered
-Organization Vocabulary (RegOrg) and the Organization Ontology is described <a href="#relOrg">below</a>.</p>
-<p>The Registered Organization Vocabulary includes a minimal number of classes and properties that are
+flexible and comprehensive Organization Ontology [
+ <cite>
+ <a class="bibref" href="#bib-ORG">ORG</a>
+ </cite>
+ ]. The relationship between the Registered
+Organization Vocabulary (RegOrg) and the Organization Ontology is described
+ <a href="#relOrg">below</a>
+ .
+ </p>
+ <p>The Registered Organization Vocabulary includes a minimal number of classes and properties that are
designed to capture the typical details recorded by business registers and thereby facilitate
information exchange between them, although there is significant variation between business
registers in what they record and publish. </p>
-
-</section> <!-- intro -->
-
-<section id="ns" class="informative">
-<h2>Namespaces</h2>
-<p>The namespace for the Registered Organization vocabulary is <code>http://www.w3.org/ns/regorg#</code> and the preferred prefix is
-<code>rov</code>. A full set of namespaces and prefixes used in this document is shown in the table below.</p>
-<table id="namespaces">
- <thead><tr><th>Prefix</th><th>Namespace</th></tr></thead>
- <tbody>
- <tr><td>adms</td><td>http://www.w3.org/ns/adms#</td></tr>
- <tr><td>dcterms</td><td>http://purl.org/dc/terms/</td></tr>
- <tr><td>org</td><td>http://www.w3.org/ns/org#</td></tr>
- <tr><td>skos</td><td>http://www.w3.org/2004/02/skos/core#</td></tr>
- <tr><td>xsd</td><td>http://www.w3.org/2001/XMLSchema#</td></tr>
- </tbody>
-</table>
-</section> <!--end of namespaces-->
-
-
-<section class="informative">
-<h2 id="intro">Overview of the vocabulary</h2>
-<p>The key class is <code>rov:RegisteredOrganization</code> and it is this class that represents a single business that became a
-legal entity through a formal registration process. It is a sub class of <code>org:FormalOrganization</code> that covers
-any legal entity, however created. The sub class relationship allows us to use all aspects of ORG such as the
-<code>org:hasRegisteredSite</code> property to link a registered organization with the site of its registered
-address. The registration process varies between different jurisdictions; in some cases it's the tax authority
-that registers a business, in others a separate register exists and so on.</p>
-<p>As well as defining the <code>rov:RegisteredOrganization</code> class, this
-vocabulary also makes use of classes defined elsewhere: the <code>adms:Identifier</code>
-class and the familiar <code>skos:Concept</code>. The Identifier class captures the legal and other identifiers, while the
-Concept class can be used to describe properties like the organization type, status and activity, that might be
-recognized across national borders.</p>
-<p>The Registered Organization class is associated with the Identifier and Concept classes through 2 properties,
-<code>adms:identifier</code> and <code>org:classification</code> respectively. These have sub-properties with more specific semantics
-as depicted in the diagram and the following sections.</p>
+ </div>
+ <!-- intro -->
+ <div id="ns" class="informative section">
+ <!--OddPage-->
+ <h2>
+ <span class="secno">2. </span>
+ Namespaces
+ </h2>
+ <p>
+ <em>This section is non-normative.</em>
+ </p>
+ <p>
+ The namespace for the Registered Organization vocabulary is
+ <code>http://www.w3.org/ns/regorg#</code>
+ and the preferred prefix is
-<figure id="uml">
- <img src="regorg20130508.png" width="368" height="343" alt="The Registered Organization Vocabulary UML diagram" />
- <br/>
- <figcaption>The Registered Organization Vocabulary</figcaption>
-</figure>
+ <code>rov</code>
+ . A full set of namespaces and prefixes used in this document is shown in the table below.
+ </p>
+ <table id="namespaces">
+ <thead>
+ <tr>
+ <th>Prefix</th>
+ <th>Namespace</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td>adms</td>
+ <td>http://www.w3.org/ns/adms#</td>
+ </tr>
+ <tr>
+ <td>dcterms</td>
+ <td>http://purl.org/dc/terms/</td>
+ </tr>
+ <tr>
+ <td>org</td>
+ <td>http://www.w3.org/ns/org#</td>
+ </tr>
+ <tr>
+ <td>skos</td>
+ <td>http://www.w3.org/2004/02/skos/core#</td>
+ </tr>
+ <tr>
+ <td>xsd</td>
+ <td>http://www.w3.org/2001/XMLSchema#</td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <!--end of namespaces-->
+ <div class="informative section" id="overview-of-the-vocabulary">
+ <!--OddPage-->
+ <h2 id="over">
+ <span class="secno">3. </span>
+ Overview of the vocabulary
+ </h2>
+ <p>
+ <em>This section is non-normative.</em>
+ </p>
+ <p>
+ The key class is
+ <code>rov:RegisteredOrganization</code>
+ and it is this class that represents a single business that became a
+legal entity through a formal registration process. It is a sub class of
+ <code>org:FormalOrganization</code>
+ that covers
+any legal entity, however created. The sub class relationship allows us to use all aspects of ORG such as the
-<section id="vocIndex">
-<h3>Vocabulary index</h3>
-<p>Normative definitions of each term in the vocabulary are provided in the <a href="#vocabDef">Vocabulary Definitions</a> section but for quick reference they are listed
-below.</p>
-<dl>
- <dt>Classes:</dt>
- <dd><ul><li><a href='#ref_rov_regorg'>rov:RegisteredOrganization</a></li></ul></dd>
- <dt>Properties:</dt>
- <dd><ul>
- <li><a href='#ref_rov_legalname'>rov:legalName</a></li>
- <li><a href='#ref_skos_altlabel'>skos:altLabel</a></li>
- <li><a href='#ref_rov_orgType'>rov:orgType</a></li>
- <li><a href='#ref_rov_orgStatus'>rov:orgStatus</a></li>
- <li><a href='#ref_rov_orgActivity'>rov:orgActivity</a></li>
- <li><a href='#ref_rov_registration'>rov:registration</a></li>
-<!-- <li><a href='#ref_rov_regaddress'>rov:registeredAddress</a></li> -->
- <li><a href='#ref_rov_hasRegOrg'>rov:hasRegisteredOrganization</a></li></ul></dd>
- </dl>
-</section> <!--end of voc index-->
+ <code>org:hasRegisteredSite</code>
+ property to link a registered organization with the site of its registered
+address. The registration process varies between different jurisdictions; in some cases it's the tax authority
+that registers a business, in others a separate register exists and so on.
+ </p>
+ <p>
+ As well as defining the
+ <code>rov:RegisteredOrganization</code>
+ class, this
+vocabulary also makes use of classes defined elsewhere: the
+ <code>adms:Identifier</code>
+
+class and the familiar
+ <code>skos:Concept</code>
+ . The Identifier class captures the legal and other identifiers, while the
+Concept class can be used to describe properties like the organization type, status and activity, that might be
+recognized across national borders.
+ </p>
+ <p>
+ The Registered Organization class is associated with the Identifier and Concept classes through 2 properties,
-
-</section> <!-- end of overview-->
-
-<section class="informative">
-<h2 id="usage">RegOrg Usage</h2>
-
-<p>The following is an example of a (real) company described using the Registered Organization vocabulary (in RDF/Turtle),
-which is also available as a <a href="apple.ttl">separate file</a>. This includes:</p><ul>
-<li>a description of the organization;</li>
-<li>a legal identifier (i.e. details of the registration with the authority that conferred legal status);</li>
-<li>a further identifier (Open Corporates).</li></ul>
-
-<p>We assume here that example.com is publishing information about registered organizations. This might be the
+ <code>adms:identifier</code>
+ and
+ <code>org:classification</code>
+ respectively. These have sub-properties with more specific semantics
+as depicted in the diagram and the following sections.
+ </p>
+ <figure id="uml">
+ <img src="regorg20130508.png" width="368" height="343" alt="The Registered Organization Vocabulary UML diagram">
+ <br>
+ <figcaption>The Registered Organization Vocabulary</figcaption>
+ </figure>
+ <div id="vocIndex" class="section">
+ <h3>
+ <span class="secno">3.1 </span>
+ Vocabulary index
+ </h3>
+ <p>
+ Normative definitions of each term in the vocabulary are provided in the
+ <a href="#vocabDef">Vocabulary Definitions</a>
+ section but for quick reference they are listed
+below.
+ </p>
+ <dl>
+ <dt>Classes:</dt>
+ <dd>
+ <ul>
+ <li>
+ <a href="#ref_rov_regorg">rov:RegisteredOrganization</a>
+ </li>
+ </ul>
+ </dd>
+ <dt>Properties:</dt>
+ <dd>
+ <ul>
+ <li>
+ <a href="#ref_rov_legalname">rov:legalName</a>
+ </li>
+ <li>
+ <a href="#ref_skos_altlabel">skos:altLabel</a>
+ </li>
+ <li>
+ <a href="#ref_rov_orgType">rov:orgType</a>
+ </li>
+ <li>
+ <a href="#ref_rov_orgStatus">rov:orgStatus</a>
+ </li>
+ <li>
+ <a href="#ref_rov_orgActivity">rov:orgActivity</a>
+ </li>
+ <li>
+ <a href="#ref_rov_registration">rov:registration</a>
+ </li>
+ <!-- <li><a href='#ref_rov_regaddress'>rov:registeredAddress</a></li> -->
+ <li>
+ <a href="#ref_rov_hasRegOrg">rov:hasRegisteredOrganization</a>
+ </li>
+ </ul>
+ </dd>
+ </dl>
+ </div>
+ <!--end of voc index-->
+ </div>
+ <!-- end of overview-->
+ <div class="informative section" id="regorg-usage">
+ <!--OddPage-->
+ <h2 id="usage">
+ <span class="secno">4. </span>
+ RegOrg Usage
+ </h2>
+ <p>
+ <em>This section is non-normative.</em>
+ </p>
+ <p>
+ The following is an example of a (real) company described using the Registered Organization vocabulary (in RDF/Turtle),
+which is also available as a
+ <a href="apple.ttl">separate file</a>
+ . This includes:
+ </p>
+ <ul>
+ <li>a description of the organization;</li>
+ <li>a legal identifier (i.e. details of the registration with the authority that conferred legal status);</li>
+ <li>a further identifier (Open Corporates).</li>
+ </ul>
+ <p>We assume here that example.com is publishing information about registered organizations. This might be the
company register itself or another organization.</p>
-
-<pre id="appleBinding">
-1 <http://business.data.gov.uk/id/company/04285910>
+ <pre id="appleBinding">1 <http://data.companieshouse.gov.uk/id/company/04285910>
2 a rov:RegisteredOrganization ;
3 rov:legalName "Apple Binding Ltd" ;
-4 rov:orgStatus <http://example.com/ref/status/NormalActivity> ;
-5 rov:orgType <http://example.com/ref/type/Plc> ;
-6 rov:orgActivity <http://example.com/ref/NACE/2/C/18/01/02> ;
-7 rov:orgActivity <http://example.com/ref/NACE/2/C/18/01/04> ;
-8 rov:registration <http://example.com/id/li04285910> ;
-9 adms:identifier <http://example.com/id/oc04285910> ;
-10 org:registeredSite <http://example.com/id/rs04285910> .
+4 rov:orgStatus <http://example.com/ref/status/NormalActivity> ;
+5 rov:orgType <http://example.com/ref/type/Plc> ;
+6 rov:orgActivity <http://example.com/ref/NACE/2/C/18/01/02> ;
+7 rov:orgActivity <http://example.com/ref/NACE/2/C/18/01/04> ;
+8 rov:registration <http://example.com/id/li04285910> ;
+9 adms:identifier <http://example.com/id/oc04285910> ;
+10 org:registeredSite <http://example.com/id/rs04285910> .
# The actual registration
-11 <http://example.com/id/li04285910> a adms:Identifier ;
+11 <http://example.com/id/li04285910> a adms:Identifier ;
12 skos:notation "04285910"^^ex:idType ;
13 adms:schemaAgency "UK Companies House" ;
14 dcterms:issued "2001-09-12"^^xsd:date .
# A supplementary identifier (Open Corporates)
-15 <http://example.com/id/oc04285910> a adms:Identifier ;
+15 <http://example.com/id/oc04285910> a adms:Identifier ;
16 skos:notation "http://opencorporates.com/companies/gb/04285910"^^ex:OCid ;
17 dcterms:issued "2010-10-21T15:09:59Z"^^xsd:dateTime ;
18 dcterms:modified "2012-04-26T15:16:44Z"^^xsd:dateTime ;
-19 dcterms:creator <http://opencorporates.com/companies/gb/07444723> .
+19 dcterms:creator <http://opencorporates.com/companies/gb/07444723> .
</pre>
-
-<p>Line 3 gives the legally registered name of the company. In some jurisdictions,
+ <p>
+ Line 3 gives the legally registered name of the company. In some jurisdictions,
especially those where there are multiple official languages, a single company
may have several legal names and therefore it can be appropriate to use
-multiple instances of the <code><a href="#ref_rov_legalname">legalName</a></code> property (language tags may, of course, be added).
+multiple instances of the
+ <code>
+ <a href="#ref_rov_legalname">legalName</a>
+ </code>
+ property (language tags may, of course, be added).
It is noteworthy that ORG assumes that an organization can only have a single legally recognized name (which is the common case)
-and therefore uses <code>skos:prefLabel</code> for this. It is the possibility of having more than one such name in a limited
-number of jurisdictions, that justifies the creation of <code>rov:legalName</code>.</p>
-<p>Where a company is known informally by an alternative name of some sort, or a trading name,
-in addition to its legal name, then <code>skos:altLabel</code> should be used to provide those alternatives as is done in ORG.</p>
+and therefore uses
+ <code>skos:prefLabel</code>
+ for this. It is the possibility of having more than one such name in a limited
+number of jurisdictions, that justifies the creation of
+ <code>rov:legalName</code>
+ .
+ </p>
+ <p>
+ Where a company is known informally by an alternative name of some sort, or a trading name,
+in addition to its legal name, then
+ <code>skos:altLabel</code>
+ should be used to provide those alternatives as is done in ORG.
+ </p>
+ <p>
+ In lines 4 and 5, URIs identify the
+ <a href="#ref_rov_orgStatus">organization status</a>
+ and
-<p>In lines 4 and 5, URIs identify the <a href="#ref_rov_orgstatus">organization status</a> and
-<a href="#ref_rov_orgType">organization type</a>. Different jurisdictions will
+ <a href="#ref_rov_orgType">organization type</a>
+ . Different jurisdictions will
typically define different values for organization status such as trading, insolvent and
ceased trading. Similarly there is a wide variety of organization types such as Plc, SA and GmbH
although within a given jurisdiction there will be a limited number of defined terms.
Even where the terms used in different jurisdictions are lexically identical, they may have slightly
different legal meanings. The controlled list of values for organization type and organization status
-should be encoded as a SKOS Concept Scheme so that each ones has a URI.</p>
-
-<p>Registers typically record the type of activity (or multiple activities) carried out.
+should be encoded as a SKOS Concept Scheme so that each ones has a URI.
+ </p>
+ <p>
+ Registers typically record the type of activity (or multiple activities) carried out.
These are normally set out in a controlled vocabulary and again, these can vary from one jurisdiction to another.
-The UN's ISIC Codes [[ISIC4]] form a common starting point for several such vocabularies including
-the European Union's NACE [[NACE]] Codes and UK's SIC codes [[SIC07]]. The URIs shown as the values
-of <code>rov:orgActivity</code> in lines 6 and 7 assume that NACE codes are encoded as SKOS concepts.</p>
-
-<p>Line 8 carries the crucial <code><a href="#ref_rov_registration">registration</a></code> property that points to an
-Identifier class (defined in <abbr title="Asset Description Metadata Schema">ADMS</abbr> [[!ADMS]]).
+The UN's ISIC Codes [
+ <cite>
+ <a class="bibref" href="#bib-ISIC4">ISIC4</a>
+ </cite>
+ ] form a common starting point for several such vocabularies including
+the European Union's NACE [
+ <cite>
+ <a class="bibref" href="#bib-NACE">NACE</a>
+ </cite>
+ ] Codes and UK's SIC codes [
+ <cite>
+ <a class="bibref" href="#bib-SIC07">SIC07</a>
+ </cite>
+ ]. The URIs shown as the values
+of
+ <code>rov:orgActivity</code>
+ in lines 6 and 7 assume that NACE codes are encoded as SKOS concepts.
+ </p>
+ <p>
+ Line 8 carries the crucial
+ <code>
+ <a href="#ref_rov_registration">registration</a>
+ </code>
+ property that points to an
+Identifier class (defined in
+ <abbr title="Asset Description Metadata Schema">ADMS</abbr>
+ [
+ <cite>
+ <a class="bibref" href="#bib-ADMS">ADMS</a>
+ </cite>
+ ]).
Although formally the Registered Organization vocabulary has no mandatory
classes or properties, the defining characteristic of a registered organization is that it is formally registered.
This is the property that captures that information and links to the formal registration which is described
in lines 15 - 18. In this case, Apple Binding became a registered company on 12 September 2001 when
UK Companies House issued it with the identifier 04285910. The identifier is typed in line with expected
-practice for <code>skos:notation</code> and the ORG ontology. Incidentally, UK Companies House
+practice for
+ <code>skos:notation</code>
+ and the ORG ontology. Incidentally, UK Companies House
publishes its information about registered companies as linked data and the example uses that URI
-as the subject of the description.</p>
-
-<p>Line 10 shows the <code>org:registeredSite</code> used to point to a description of the registered address of
-the organization (the address information itself is not shown).</p>
-
-<p>In addition to their company registration identifier, legal entities are very likely to
+as the subject of the description.
+ </p>
+ <p>
+ Line 10 shows the
+ <code>org:registeredSite</code>
+ used to point to a description of the registered address of
+the organization (the address information itself is not shown).
+ </p>
+ <p>In addition to their company registration identifier, legal entities are very likely to
have other identifiers associated with them, such as tax numbers, VAT numbers etc. Line 9 points
to an example of an additional identifier, one that does not confer legal status (or any other status) on
the company but that is potentially useful as an identifier.</p>
-
-
-</section> <!-- Example -->
-</section> <!-- Usage -->
-
-<section class="informative">
-<h2 id="relOrg">Relationship with the Organization Ontology</h2>
-<p>A Registered Organization (<code>rov:RegisteredOrganization</code>) is a sub class of
-the Organization Ontology's Formal Organization (<code>org:FormalOrganization</code>).
+ </div>
+ <!-- Example -->
+ <!-- Usage -->
+ <div class="informative section" id="relationship-with-the-organization-ontology">
+ <!--OddPage-->
+ <h2 id="relOrg">
+ <span class="secno">5. </span>
+ Relationship with the Organization Ontology
+ </h2>
+ <p>
+ <em>This section is non-normative.</em>
+ </p>
+ <p>
+ A Registered Organization (
+ <code>rov:RegisteredOrganization</code>
+ ) is a sub class of
+the Organization Ontology's Formal Organization (
+ <code>org:FormalOrganization</code>
+ ).
Furthermore, RegORG includes three sub properties of ORG's classification property covering
-status, activity and type.</p>
-<p>The key difference is the way in which identifiers are handled. In the ORG ontology, an organization
-may have an identifier expressed as a datatyped string (it uses a sub property of <code>skos:notation</code>).
+status, activity and type.
+ </p>
+ <p>
+ The key difference is the way in which identifiers are handled. In the ORG ontology, an organization
+may have an identifier expressed as a datatyped string (it uses a sub property of
+ <code>skos:notation</code>
+ ).
For Registered Organizations, it is the identifier issued by the relevant registration authority that
-confers legal status and therefore always has particular significance. RegORG uses the ADMS class
+confers legal status and therefore always has particular significance. RegORG uses the
+ <abbr title="Asset Description Metadata Schema">ADMS</abbr>
+ class
of Identifier (based on the UN/CEFACT class of the same name) to allow statements to be made
-<em>about</em> the identifier in a way not possible in ORG. Given data about a Registered Organization,
-it is possible to derive an <code>org:identifier</code> but the inverse is not true.</p>
-<p>In summary:</p>
-<p><code>rov:RegisteredOrganization</code> is a sub class of <code>org:FormalOrganization</code></p>
-<p><code>rov:orgType</code>, <code>rov:orgStatus</code> and <code>rov:orgActivity</code> are all sub properties of <code>org:classification</code>.</p>
-<p>Given data such as:</p>
- <pre>
-<http://example.com/id/123456>
- rov:registration <http://example.com/id/li123456> .
+ <em>about</em>
+ the identifier in a way not possible in ORG. Given data about a Registered Organization,
+it is possible to derive an
+ <code>org:identifier</code>
+ but the inverse is not true.
+ </p>
+ <p>In summary:</p>
+ <p>
+ <code>rov:RegisteredOrganization</code>
+ is a sub class of
+ <code>org:FormalOrganization</code>
+ </p>
+ <p>
+ <code>rov:orgType</code>
+ ,
+ <code>rov:orgStatus</code>
+ and
+ <code>rov:orgActivity</code>
+ are all sub properties of
+ <code>org:classification</code>
+ .
+ </p>
+ <p>Given data such as:</p>
+ <pre><http://example.com/id/123456>
+ rov:registration <http://example.com/id/li123456> .
-<http://example.com/id/li123456> a adms:Identifier ;
+<http://example.com/id/li123456> a adms:Identifier ;
skos:notation "123456"^^ex:idType .
</pre>
-<p>This SPARQL query</p>
- <pre>CONSTRUCT {
+ <p>This SPARQL query</p>
+ <pre>CONSTRUCT {
?org org:identifier ?id .
} WHERE {
?org rov:registration [skos:notation ?id] .
}</pre>
-<p>yields the <code>org:identifier</code> property and value, i.e.</p>
-<pre>
-<http://example.com/id/123456>
+ <p>
+ yields the
+ <code>org:identifier</code>
+ property and value, i.e.
+ </p>
+ <pre><http://example.com/id/123456>
org:identifier "123456"^^ex:idType .</pre>
-
-</section> <!--relORG -->
-
-<section id="vocabDef">
-<h2>Vocabulary Definitions</h2>
-<p>The classes and properties are described in the following sub-sections.</p>
-
-
-<section>
-<h2 id="ref_rov_regorg">The Registered Organization Class</h2>
-<table>
- <thead><tr><th>Class</th><th>Notes</th></tr>
- <tbody><tr><td class="code">rov:RegisteredOrganization</td><td>Sub class of <code>org:FormalOrganization</code></td></tr></tbody>
-</table>
-
-<p>The Registered Organization class is central to the vocabulary. It represents an organization that
-gains legal entity status by the act of registration cf. <code>org:FormalOrganization</code> that
+ </div>
+ <!--relORG -->
+ <div id="vocabDef" class="section">
+ <!--OddPage-->
+ <h2>
+ <span class="secno">6. </span>
+ Vocabulary Definitions
+ </h2>
+ <p>The classes and properties are described in the following sub-sections.</p>
+ <div id="the-registered-organization-class" class="section">
+ <h3 id="ref_rov_regorg">
+ <span class="secno">6.1 </span>
+ The Registered Organization Class
+ </h3>
+ <table>
+ <thead>
+ <tr>
+ <th>Class</th>
+ <th>Notes</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="code">rov:RegisteredOrganization</td>
+ <td>
+ Sub class of
+ <code>org:FormalOrganization</code>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <p>
+ The Registered Organization class is central to the vocabulary. It represents an organization that
+gains legal entity status by the act of registration cf.
+ <code>org:FormalOrganization</code>
+ that
applies to any legal entity, including those created by other legal means. In many countries
-there is a single registry although in others, such as Spain and Germany, multiple registries exist.</p>
-<p>Registered organizations are distinct from the broader concept of organizations, groups or, in some jurisdictions, sole traders.
+there is a single registry although in others, such as Spain and Germany, multiple registries exist.
+ </p>
+ <p>Registered organizations are distinct from the broader concept of organizations, groups or, in some jurisdictions, sole traders.
Many organizations exist that are not legal entities yet to the outside world they have staff, hierarchies,
locations etc. Other organizations exist that are an umbrella for several legal entities (universities
are often good examples of this).</p>
-<p><code>rov:RegisteredOrganization</code> is a sub class of the Organization Ontology's <code>org:FormalOrganization</code>
-which is itself a sub class of the more general 'Agent' class found in FOAF [[!FOAF]] and Dublin Core [[!DC11]] that
-<em>does</em> encompass organizations, natural persons, groups etc. — i.e. an Agent is
-any entity that is able to carry out actions.</p>
-
-</section> <!-- end of classes section-->
+ <p>
+ <code>rov:RegisteredOrganization</code>
+ is a sub class of the Organization Ontology's
+ <code>org:FormalOrganization</code>
+
+which is itself a sub class of the more general 'Agent' class found in FOAF [
+ <cite>
+ <a class="bibref" href="#bib-FOAF">FOAF</a>
+ </cite>
+ ] and Dublin Core [
+ <cite>
+ <a class="bibref" href="#bib-DC11">DC11</a>
+ </cite>
+ ] that
-<section>
-<h2 id="regorg_properties">Properties</h2>
-<h3 id="ref_rov_legalname">Legal Name</h3>
-<table>
- <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr>
- <tbody><tr><td class="code">rov:legalName</td><td>org:FormalOrganization</td><td><code>rdfs:Literal</code></td></tr></tbody>
-</table>
-<p>The legal name of the business. A business might have more than one legal name,
+ <em>does</em>
+ encompass organizations, natural persons, groups etc. — i.e. an Agent is
+any entity that is able to carry out actions.
+ </p>
+ </div>
+ <!-- end of classes section-->
+ <div id="properties" class="section">
+ <h3 id="regorg_properties">
+ <span class="secno">6.2 </span>
+ Properties
+ </h3>
+ <h3 id="ref_rov_legalname">Legal Name</h3>
+ <table>
+ <thead>
+ <tr>
+ <th>Property</th>
+ <th>Domain</th>
+ <th>Range</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="code">rov:legalName</td>
+ <td>org:FormalOrganization</td>
+ <td>
+ <code>rdfs:Literal</code>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <p>The legal name of the business. A business might have more than one legal name,
particularly in countries with more than one official language. In such cases the language of the string should be identified.</p>
-
-
-<h3 id="ref_skos_altlabel">skos:altLabel</h3>
-<table>
- <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr></thead>
- <tbody><tr><td class="code">skos:altLabel</td><td>rdfs:Resource</td><td><code>rdfs:Literal</code></td></tr></tbody>
-</table>
-<p>Some jurisdictions recognize concepts such as a trading name or alternative forms of a
-legal entity's name. Alternative names can be recorded using the <code>skos:altLabel</code> but
+ <h3 id="ref_skos_altlabel">skos:altLabel</h3>
+ <table>
+ <thead>
+ <tr>
+ <th>Property</th>
+ <th>Domain</th>
+ <th>Range</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="code">skos:altLabel</td>
+ <td>rdfs:Resource</td>
+ <td>
+ <code>rdfs:Literal</code>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <p>
+ Some jurisdictions recognize concepts such as a trading name or alternative forms of a
+legal entity's name. Alternative names can be recorded using the
+ <code>skos:altLabel</code>
+ but
should not be used to record translations of the primary legal name. Where more
than one legal name exists and where they have equal standing but are expressed
in different languages, identify the language used in each of the multiple legal
-names (see previous section).</p>
-<p>It is notable that some jurisdictions regard the use of any name other than the primary Legal Name as suspicious.</p>
-
-
-<h3 id="ref_rov_orgType">Organization Type</h3>
-<table>
- <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr></thead>
- <tbody><tr><td class="code"><code>rov:orgType<br />rdfs:subPropertyOf org:classification</code></td><td>org:Organization</td><td><code>skos:Concept</code></td></tr></tbody>
-</table>
-<p>This property records the type of company. Familiar types are SA, PLC, LLC,
+names (see previous section).
+ </p>
+ <p>It is notable that some jurisdictions regard the use of any name other than the primary Legal Name as suspicious.</p>
+ <h3 id="ref_rov_orgType">Organization Type</h3>
+ <table>
+ <thead>
+ <tr>
+ <th>Property</th>
+ <th>Domain</th>
+ <th>Range</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="code">
+ <code>
+ rov:orgType
+ <br>
+ rdfs:subPropertyOf org:classification
+ </code>
+ </td>
+ <td>org:Organization</td>
+ <td>
+ <code>skos:Concept</code>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <p>This property records the type of company. Familiar types are SA, PLC, LLC,
GmbH etc. At the time of publication, there is no agreed set of company types that
crosses borders. The term 'SA' is used in Poland and France for example although they
mean slightly different things. The UK's LLP and Greece's EPE provide further example of
close, but not exact, matches.</p>
-<p>That said, each jurisdiction will have a limited set of recognized company types and these
+ <p>That said, each jurisdiction will have a limited set of recognized company types and these
should be expressed in a consistent manner in a SKOS Concept Scheme.</p>
-
-
-<h3 id="ref_rov_orgStatus">Organization Status</h3>
-<table>
- <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr></thead>
- <tbody><tr><td class="code"><code>rov:orgStatus<br />rdfs:subPropertyOf org:classification</code></td><td>org:Organization</td><td><code>skos:Concept</code></td></tr></tbody>
-</table>
-<p>Recording the status of an organization presents the same issues as its type.
+ <h3 id="ref_rov_orgStatus">Organization Status</h3>
+ <table>
+ <thead>
+ <tr>
+ <th>Property</th>
+ <th>Domain</th>
+ <th>Range</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="code">
+ <code>
+ rov:orgStatus
+ <br>
+ rdfs:subPropertyOf org:classification
+ </code>
+ </td>
+ <td>org:Organization</td>
+ <td>
+ <code>skos:Concept</code>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <p>Recording the status of an organization presents the same issues as its type.
The terms 'insolvent', 'bankrupt' and 'in receivership,' for example, are likely to mean
slightly different things with different legal implications in different jurisdictions. </p>
-<p>Taking advice from <a href="www.xbrl-eu.org/">XBRL Europe</a> as a starting point, however, the term 'Normal Activity'
-does appear to have cross-border usefulness and this should be used in preference to terms like 'trading' or 'operating.'</p>
-<p>Best Practice for recording various other status levels is to use the relevant jurisdiction's
+ <p>
+ Taking advice from
+ <a href="http://www.xbrl-eu.org/">XBRL Europe</a>
+ as a starting point, however, the term 'Normal Activity'
+does appear to have cross-border usefulness and this should be used in preference to terms like 'trading' or 'operating.'
+ </p>
+ <p>Best Practice for recording various other status levels is to use the relevant jurisdiction's
terms and to encode these in a SKOS Concept Scheme.</p>
-
-<h3 id="ref_rov_orgActivity">Organization Activity</h3>
-<table>
- <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr></thead>
- <tbody><tr><td class="code"><code>rov:orgActivity<br />rdfs:subPropertyOf org:classification</code></td><td>org:Organization</td><td><code>skos:Concept</code></td></tr></tbody>
-</table>
-<p>The activity of an organization should be recorded using a controlled vocabulary. Several
-such vocabularies exist, many of which map to the UN's ISIC codes [[ISIC4]]. Where a particular controlled
+ <h3 id="ref_rov_orgActivity">Organization Activity</h3>
+ <table>
+ <thead>
+ <tr>
+ <th>Property</th>
+ <th>Domain</th>
+ <th>Range</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="code">
+ <code>
+ rov:orgActivity
+ <br>
+ rdfs:subPropertyOf org:classification
+ </code>
+ </td>
+ <td>org:Organization</td>
+ <td>
+ <code>skos:Concept</code>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <p>
+ The activity of an organization should be recorded using a controlled vocabulary. Several
+such vocabularies exist, many of which map to the UN's ISIC codes [
+ <cite>
+ <a class="bibref" href="#bib-ISIC4">ISIC4</a>
+ </cite>
+ ]. Where a particular controlled
vocabulary is in use within a given context, such as SIC codes in the UK, it is acceptable to use
-these, however, the preferred choice for European interoperability is NACE [[NACE]]. As with
-company type and status, activity codes should be expressed as SKOS Concept Schemes.</p>
-
-<h3 id="ref_rov_registration">Registration</h3>
-<table>
- <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr></thead>
- <tbody><tr><td class="code"><code>rov:registration<br />rdfs:subPropertyOf adms:identifier</code></td><td><code>rov:RegisteredOrganization</code></td><td><code>adms:Identifier</code></td></tr></tbody>
-</table>
-<p>The legal status of a registered organization is conferred on it by an authority within a given
+these, however, the preferred choice for European interoperability is NACE [
+ <cite>
+ <a class="bibref" href="#bib-NACE">NACE</a>
+ </cite>
+ ]. As with
+company type and status, activity codes should be expressed as SKOS Concept Schemes.
+ </p>
+ <h3 id="ref_rov_registration">Registration</h3>
+ <table>
+ <thead>
+ <tr>
+ <th>Property</th>
+ <th>Domain</th>
+ <th>Range</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="code">
+ <code>
+ rov:registration
+ <br>
+ rdfs:subPropertyOf adms:identifier
+ </code>
+ </td>
+ <td>
+ <code>rov:RegisteredOrganization</code>
+ </td>
+ <td>
+ <code>adms:Identifier</code>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <p>
+ The legal status of a registered organization is conferred on it by an authority within a given
jurisdiction. The registration is therefore a fundamental relationship between a the organization
and the authority with which it is registered. The details of the registration are
-provided as properties of the Identifier class which is defined by ADMS [[ADMS]]. The vocabulary
+provided as properties of the Identifier class which is defined by
+ <abbr title="Asset Description Metadata Schema">ADMS</abbr>
+ [
+ <cite>
+ <a class="bibref" href="#bib-ADMS">ADMS</a>
+ </cite>
+ ]. The vocabulary
sets no restriction on the type of legal identifier. In many countries, the business
-register's identifier is the relevant data point. The tax number often fulfils this function in Spain and elsewhere.</p>
-<p>Although there is no formal cardinality constraint on any property in the Registered Organization Vocabulary, it is
+register's identifier is the relevant data point. The tax number often fulfils this function in Spain and elsewhere.
+ </p>
+ <p>Although there is no formal cardinality constraint on any property in the Registered Organization Vocabulary, it is
questionable whether a description of a registered organization without this property and an associated Identifier class
will be of any value.</p>
-
-<h3 id="ref_rov_hasRegOrg">Has Registered Organization</h3>
-<table>
- <thead><tr><th>Property</th><th>Domain</th><th>Range</th></tr></thead>
- <tbody><tr><td class="code">rov:hasRegisteredOrganization</td><td>dcterms:Agent</td><td><code>rov:RegisteredOrganization</code></td></tr></tbody>
-</table>
-<p>The has registered organization relationship can be used to link any <code>dcterms:Agent</code> (equivalent class <code>foaf:Agent</code>)
+ <h3 id="ref_rov_hasRegOrg">Has Registered Organization</h3>
+ <table>
+ <thead>
+ <tr>
+ <th>Property</th>
+ <th>Domain</th>
+ <th>Range</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td class="code">rov:hasRegisteredOrganization</td>
+ <td>dcterms:Agent</td>
+ <td>
+ <code>rov:RegisteredOrganization</code>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ <p>
+ The has registered organization relationship can be used to link any
+ <code>dcterms:Agent</code>
+ (equivalent class
+ <code>foaf:Agent</code>
+ )
to a Registered Organization that in some way acts as a registered legal entity for it. This is useful, for example,
-where an organization includes one or more legal entities, or where a natural person is also registered as a legal entity.</p>
-
-</section>
-
-</section>
-
-
-<section id="conformance">
+where an organization includes one or more legal entities, or where a natural person is also registered as a legal entity.
+ </p>
+ </div>
+ </div>
+ <div id="conformance" class="section">
+ <!--OddPage-->
+ <h2>
+ <span class="secno">7. </span>
+ Conformance
+ </h2>
+ <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" title="must">must</em>
+ ,
+ <em class="rfc2119" title="must not">must not</em>
+ ,
+ <em class="rfc2119" title="required">required</em>
+ ,
+ <em class="rfc2119" title="should">should</em>
+ ,
+ <em class="rfc2119" title="should not">should not</em>
+ ,
+ <em class="rfc2119" title="recommended">recommended</em>
+ ,
+ <em class="rfc2119" title="may">may</em>
+ , and
+ <em class="rfc2119" title="optional">optional</em>
+ in this specification are to be interpreted as described in [
+ <cite>
+ <a class="bibref" href="#bib-RFC2119">RFC2119</a>
+ </cite>
+ ].
+ </p>
+ <p>A data interchange, however that interchange occurs, is conformant with the Registered Organization
+vocabulary if:</p>
+ <ul>
+ <li>it uses the terms (classes and properties)in a way consistent with their semantics as declared in this specification;</li>
+ <li>it does not use terms from other vocabularies instead of ones defined in this vocabulary that could reasonably be used.</li>
+ </ul>
+ <p>A conforming data interchange:</p>
+ <ul>
+ <li>
+ <span class="rfc2119">may</span>
+ include terms from other vocabularies;
+ </li>
+ <li>
+ <span class="rfc2119">may</span>
+ use only a subset of Registered Organization vocabulary terms.
+ </li>
+ </ul>
+ <p>A Registered Organization application profile is a specification for data interchange that adds additional constraints. Such additional
+constraints in a profile may include:</p>
+ <ul>
+ <li>a minimum set of required terms; </li>
+ <li>classes and properties for additional terms not covered in the Registered Organization vocabulary;</li>
+ <li>controlled vocabularies or URI sets as acceptable values for properties;</li>
+ </ul>
+ <p>The Registered Organization Vocabulary is technology-neutral and a publisher may use any of the terms defined in this
+document encoded in any technology although RDF and XML are preferred.</p>
+ </div>
+ <div id="changelog" class="appendix section">
+ <!--OddPage-->
+ <h2>
+ <span class="secno">A. </span>
+ Change Log
+ </h2>
+ <p>
+ Multiple changes have ben made since the
+ <a href="http://www.w3.org/TR/2013/WD-vocab-regorg-20130108/">previous version</a>
+ of
+RegOrg. These have been made to align the vocabulary more closely with other GLD WG outputs, notably DCAT and ORG. In particular
-<p>A data interchange, however that interchange occurs, is conformant with the Registered Organization
-vocabulary if:</p><ul>
-<li>it uses the terms (classes and properties)in a way consistent with their semantics as declared in this specification;</li>
-<li>it does not use terms from other vocabularies instead of ones defined in this vocabulary that could reasonably be used.</li>
-</ul>
-<p>A conforming data interchange:</p><ul>
-<li><span class="rfc2119">may</span> include terms from other vocabularies;</li>
-<li><span class="rfc2119">may</span> use only a subset of Registered Organization vocabulary terms.</li>
-</ul>
-<p>A Registered Organization application profile is a specification for data interchange that adds additional constraints. Such additional
-constraints in a profile may include:</p><ul>
-<li>a minimum set of required terms; </li>
-<li>classes and properties for additional terms not covered in the Registered Organization vocabulary;</li>
-<li>controlled vocabularies or URI sets as acceptable values for properties;</li>
-</ul>
-<p>The Registered Organization Vocabulary is technology-neutral and a publisher may use any of the terms defined in this
-document encoded in any technology although RDF and XML are preferred.</p>
+ <code>dcterms:created</code>
+ has been replaced with
+ <code>dcterms:issued</code>
+ , and
+ <code>dcterms:alternative</code>
+ has been
+replaced with
+ <code>skos:altLabel</code>
+ . The UML diagram is aligned with that used for
+ <abbr title="Asset Description Metadata Schema">ADMS</abbr>
+ and, in the same way that
+ <abbr title="Asset Description Metadata Schema">ADMS</abbr>
+ is
+defined as a profile of DCAT, RegOrg is now defined as a profile of ORG.
+ </p>
+ <p>
+ The use of the term 'company type' was seen as being too restrictive for other types of registered organizations such as charities
+so that
+ <code>rov:companyType</code>
+ ,
+ <code>rov:companyActivity</code>
+ and
+ <code>rov:companyStatus</code>
+ have been replaced with
-</section>
-
-<section id="changelog" class="appendix">
-<h2>Change Log</h2>
-<p>Multiple changes have ben made since the <a href="http://www.w3.org/TR/2013/WD-vocab-regorg-20130108/">previous version</a> of
-RegOrg. These have been made to align the vocabulary more closely with other GLD WG outputs, notably DCAT and ORG. In particular
-<code>dcterms:created</code> has been replaced with <code>dcterms:issued</code>, and <code>dcterms:alternative</code> has been
-replaced with <code>skos:altLabel</code>. The UML diagram is aligned with that used for ADMS and, in the same way that ADMS is
-defined as a profile of DCAT, RegOrg is now defined as a profile of ORG.</p>
-<p>The use of the term 'company type' was seen as being too restrictive for other types of registered organizations such as charities
-so that <code>rov:companyType</code>, <code>rov:companyActivity</code> and <code>rov:companyStatus</code> have been replaced with
-<code>rov:orgType</code>, <code>rov:orgActivity</code> and <code>rov:orgStatus</code> respectively.</p>
-</section>
-
-<section id="app13" class="appendix">
-<h2>Note on identifier and classification properties</h2>
-<p>There are several vocabularies in use with a property of 'identifier' and this vocabulary creates a sub property of one of them.
+ <code>rov:orgType</code>
+ ,
+ <code>rov:orgActivity</code>
+ and
+ <code>rov:orgStatus</code>
+ respectively.
+ </p>
+ </div>
+ <div id="app13" class="appendix section">
+ <!--OddPage-->
+ <h2>
+ <span class="secno">B. </span>
+ Note on identifier and classification properties
+ </h2>
+ <p>There are several vocabularies in use with a property of 'identifier' and this vocabulary creates a sub property of one of them.
The following table provides a summary of these related but semantically different properties
in terms of their domains and ranges</p>
-<table>
- <tr><th>property</th><th>domain</th><th>range</th></tr>
- <tr><td><code>adms:identifier</code></td><td><code>rdfs:Resource</code></td><td><code>adms:Identifier</code></td></tr>
- <tr><td><code>rov:registration</code></td><td><code>rov:RegisteredOrganization</code></td><td><code>adms:Identifier</code> (<code>rov:registration</code> is a sub property of <code>adms:identifier</code>)</td></tr>
- <tr><td><code>org:identifier</code></td><td><code>org:Organization</code></td><td><code>rdfs:Literal</code> (<code>org:identifier</code> is a sub property of <code>skos:notation</code>)</td></tr>
- <tr><td><code>dcterms:identifier</code></td><td><code>rdfs:Resource</code></td><td><code>rdfs:Literal</code></td></tr>
-</table>
-</section>
+ <table>
+ <tbody>
+ <tr>
+ <th>property</th>
+ <th>domain</th>
+ <th>range</th>
+ </tr>
+ <tr>
+ <td>
+ <code>adms:identifier</code>
+ </td>
+ <td>
+ <code>rdfs:Resource</code>
+ </td>
+ <td>
+ <code>adms:Identifier</code>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <code>rov:registration</code>
+ </td>
+ <td>
+ <code>rov:RegisteredOrganization</code>
+ </td>
+ <td>
+ <code>adms:Identifier</code>
+ (
+ <code>rov:registration</code>
+ is a sub property of
+ <code>adms:identifier</code>
+ )
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <code>org:identifier</code>
+ </td>
+ <td>
+ <code>org:Organization</code>
+ </td>
+ <td>
+ <code>rdfs:Literal</code>
+ (
+ <code>org:identifier</code>
+ is a sub property of
+ <code>skos:notation</code>
+ )
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <code>dcterms:identifier</code>
+ </td>
+ <td>
+ <code>rdfs:Resource</code>
+ </td>
+ <td>
+ <code>rdfs:Literal</code>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+ <div id="acknowledgements" class="appendix section">
+ <!--OddPage-->
+ <h2>
+ <span class="secno">C. </span>
+ Acknowledgements
+ </h2>
-<section id="acknowledgements" class="appendix">
-<h2>Acknowledgements</h2>
-<p>RegOrg was first developed by PwC EU Services and <a href="https://joinup.ec.europa.eu/asset/core_business/release/100">published
- by the European Commission</a> as the <i>Core Business Vocabulary</i>. Further development and review has been undertaken by the
- <a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> (GLD WG).</p>
-<p>The working group would also like to thank the directors of <a href="http://applebinding.co.uk/">Apple Binding</a> for
-permission to describe their company in the example.</p>
-</section>
+<p>RegOrg was first developed by and published by the European Commission
+<a href="http://ec.europa.eu/isa/">ISA Programme</a> with support from the
+Directorate General Internal Market and Services (DG MARKT)as the
+<a href="https://joinup.ec.europa.eu/asset/core_business/release/100">Core Business Vocabulary</a>.
+Contributors included representatives of Member States of the European Union, operators
+of national repositories, standardization bodies and independent experts whose work
+was published in May 2012. That document includes the history and motivation behind
+the development of RegOrg, as well as the business need and usage scenario for it.</p>
+<p>Further development and review has been undertaken by the
+<a href="http://www.w3.org/2011/gld/">Government Linked Data Working Group</a> (GLD WG).
+This version of the vocabulary builds on the original work in a broader, global context.</p>
+<p>The working group would also like to thank the directors of <a href="http://applebinding.co.uk/">Apple Binding</a>
+for permission to describe their company in the example.</p>
+ </div>
+ <div id="references" class="appendix section">
+ <!--OddPage-->
+ <h2>
+ <span class="secno">D. </span>
+ References
+ </h2>
+ <div id="normative-references" class="section">
+ <h3>
+ <span class="secno">D.1 </span>
+ Normative references
+ </h3>
+ <dl class="bibliography">
+ <dt id="bib-ADMS">[ADMS]</dt>
+ <dd>
+ <cite>
+ <a href="http://dvcs.w3.org/hg/gld/raw-file/default/adms/index.html">Asset Description Metadata Schema (ADMS)</a>
+ </cite>
+ P. Archer, G. Shukair, W3C Working Group Note. URL: http://www.w3.org/TR/vocab-adms/
+ </dd>
+ <dt id="bib-DC11">[DC11]</dt>
+ <dd>
+ Dublin Core metadata initiative.
+ <a href="http://dublincore.org/documents/dcmi-terms/">
+ <cite>Dublin Core metadata element set, version 1.1.</cite>
+ </a>
+ July 1999. Dublin Core recommendation. URL:
+ <a href="http://dublincore.org/documents/dcmi-terms/">http://dublincore.org/documents/dcmi-terms/</a>
+ </dd>
+ <dt id="bib-FOAF">[FOAF]</dt>
+ <dd>
+ Dan Brickley, Libby Miller.
+ <a href="http://xmlns.com/foaf/spec/">
+ <cite>FOAF Vocabulary Specification 0.98.</cite>
+ </a>
+ 9 August 2010. URL:
+ <a href="http://xmlns.com/foaf/spec/">http://xmlns.com/foaf/spec/</a>
+ </dd>
+ <dt id="bib-ORG">[ORG]</dt>
+ <dd>
+ <cite>
+ <a href="http://www.w3.org/TR/vocab-org/">An organization ontology</a>
+ </cite>
+ , D. Reynolds, W3C Recommendations Track URL: http://www.w3.org/TR/vocab-org/
+ </dd>
+ <dt id="bib-RFC2119">[RFC2119]</dt>
+ <dd>
+ S. Bradner.
+ <a href="http://www.ietf.org/rfc/rfc2119.txt">
+ <cite>Key words for use in RFCs to Indicate Requirement Levels.</cite>
+ </a>
+ March 1997. Internet RFC 2119. URL:
+ <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
+ </dd>
+ </dl>
+ </div>
+ <div id="informative-references" class="section">
+ <h3>
+ <span class="secno">D.2 </span>
+ Informative references
+ </h3>
+ <dl class="bibliography">
+ <dt id="bib-ISIC4">[ISIC4]</dt>
+ <dd>
+ <cite>
+ <a href="http://unstats.un.org/unsd/cr/registry/regcst.asp?Cl=27">International Standard Industrial Classification of All Economic Activities, Rev.4</a>
+ </cite>
+ , United Nations Statistics Division. URL: http://unstats.un.org/unsd/cr/registry/regcst.asp?Cl=27
-</body></html>
+ </dd>
+ <dt id="bib-NACE">[NACE]</dt>
+ <dd>
+ <cite>
+ <a href="http://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm?TargetUrl=LST_NOM_DTL&StrNom=NACE_REV2&StrLanguageCode=EN">Statistical Classification of Economic Activities in the European Community</a>
+ </cite>
+ , Eurostat URL: http://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm?TargetUrl=LST_NOM_DTL&StrNom=NACE_REV2&StrLanguageCode=EN
+
+ </dd>
+ <dt id="bib-SIC07">[SIC07]</dt>
+ <dd>
+ <cite>
+ <a href="http://www.companieshouse.gov.uk/infoAndGuide/sic/sic2007.shtml">Standard Industrial Classification of Economic Activities 2007</a>
+ </cite>
+ , UK Companies House URL: http://www.companieshouse.gov.uk/infoAndGuide/sic/sic2007.shtml
+
+ </dd>
+ </dl>
+ </div>
+ </div>
+ </body>
+ </html>
\ No newline at end of file