bring up to modern respec, prep for CR
authorSandro Hawke <sandro@hawke.org>
Fri, 01 Nov 2013 14:49:53 -0400
changeset 614 85d0150b326a
parent 613 949f82b9be98
child 615 bcdb7aea1fc6
bring up to modern respec, prep for CR
dcat/index.html
--- a/dcat/index.html	Wed Oct 30 20:35:45 2013 +1100
+++ b/dcat/index.html	Fri Nov 01 14:49:53 2013 -0400
@@ -6,11 +6,106 @@
 	<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='../respec/respec3/builds/respec-w3c-common.js' class='remove'></script>
-	<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 src="../local-biblio.js" class="remove"></script>
+    <script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
+    <script class='remove'>
+      var respecConfig = {
+          // extend the bibliography entries
+          //localBiblio: localBibliography,
+
+          // specification status (e.g. WD, LC, WG-NOTE, etc.). If in doubt use ED.
+          specStatus:           "ED",
+
+          // the specification's short name, as in http://www.w3.org/TR/short-name/
+          shortName:            "vocab-dcat",
+
+          // if your specification has a subtitle that goes below the main
+          // formal title, define it here
+          // subtitle   :  "an excellent document",
+
+          // if you wish the publication date to be other than today, set this
+          publishDate:  "2013-11-05",
+          crEnd:        "2013-11-26",
+
+          // if the specification's copyright date is a range of years, specify
+          // the start date here:
+          copyrightStart: "2012",
+
+          // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+          // and its maturity status
+          previousPublishDate:  "2013-08-01",
+          previousMaturity:  "LC",
+
+          // if there a publicly available Editor's Draft, this is the link
+          edDraftURI:           "https://dvcs.w3.org/hg/gld/raw-file/default/dcat/index.html",
+
+          // if this is a LCWD, uncomment and set the end of its review period
+          // lcEnd: "2013-09-06",
+
+          // if there is an earler version of this specification at the Recommendation level,
+          // set this to the shortname of that version. This is optional and not usually
+          // necessary.
+	  //          prevRecShortname: "rdf-concepts",
+
+          // editors, add as many as you like
+          // only "name" is required
+
+	  editors:  [
+	  { name: "Fadi Maali", url: "mailto:[email protected]", company: "DERI, NUI Galway", companyURL: "http://www.deri.ie"},
+	  { name: "John Erickson", url: "mailto:[email protected]", company: "Tetherless World Constellation (RPI)", companyURL: "http://tw.rpi.edu/" },
+	  ],
+	  
+          otherLinks: [
+              {
+                  key: "Contributors",
+                  data: [
+		  {value: "Phil Archer, W3C/ERCIM",
+		  href: "mailto:[email protected]"}
+		  ]
+		  }
+		  ],
+
+          // authors, add as many as you like.
+          // This is optional, uncomment if you have authors as well as editors.
+          // only "name" is required. Same format as editors.
+
+          //authors:  [
+          //    { name: "Your Name", url: "http://example.org/",
+          //      company: "Your Company", companyURL: "http://example.com/" },
+          //],
+
+          // name of the WG
+	  wg:           "Government Linked Data Working Group",
+
+
+          // URI of the public WG page
+	  wgURI:        "http://www.w3.org/2011/gld/",
+
+          // name (WITHOUT the @w3.org) of the public mailing to which comments are due
+	  wgPublicList: "public-gld-comments",
+
+
+          // URI of the patent status for this WG, for Rec-track documents
+          // !!!! IMPORTANT !!!!
+          // This is important for Rec-track documents, do not copy a patent URI from a random
+          // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+          // Team Contact.
+          wgPatentURI:  "http://www.w3.org/2004/01/pp-impl/47663/status",
+
+          // if this parameter is set to true, ReSpec.js will embed various RDFa attributes
+          // throughout the generated specification. The triples generated use vocabulary items
+          // from the dcterms, foaf, and bibo. The parameter defaults to false.
+          doRDFa: "1.1",
+
+          alternateFormats: [ { uri: "diff-20130801.html", label: "diff to previous version" } ],
+
+	  implementationReportURI: "http://www.w3.org/2011/gld/wiki/DCAT_Implementations",
+	  maxTocLevel: 2,
+
+      };
+    </script>
+
   <style type="text/css">
   table {
     border-collapse:collapse;
@@ -52,7 +147,6 @@
 	line-height: 1.1em;
 }
   </style>
-<!--  <link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8" /> -->
 </head>
 <body>
 
@@ -71,7 +165,7 @@
 
 <section class="informative">
 <h2 id="intro">Introduction</h2>
-<p>Data can come in many formats, ranging from spreadsheets over XML and RDF to various speciality formats. DCAT does not make any assumptions about the format of the datasets described in a catalog. Other, complementary vocabularies may be used together with DCAT to provide more detailed format-specific information. For example, properties from the VoID vocabulary [[VOID]] can be used to express various statistics about a DCAT-described dataset if that dataset is in RDF format.</p>
+<p>Data can come in many formats, ranging from spreadsheets over XML and RDF to various speciality formats. DCAT does not make any assumptions about the format of the datasets described in a catalog. Other, complementary vocabularies may be used together with DCAT to provide more detailed format-specific information. For example, properties from the VoID vocabulary [[void]] can be used to express various statistics about a DCAT-described dataset if that dataset is in RDF format.</p>
 <p>This document does not prescribe any particular method of deploying data expressed in DCAT. DCAT is applicable in many contexts including RDF accessible via SPARQL endpoints, embedded in HTML pages as RDFa, or serialized as e.g. RDF/XML or Turtle. The examples in this document use Turtle simply because of Turtle's readability.</p>
 </section>
 
@@ -142,7 +236,7 @@
 <p>Another important class in DCAT is <code><a href="#Class:_Catalog_record">dcat:CatalogRecord</a></code> which describes a dataset entry in the catalog. Notice that while dcat:Dataset represents the dataset itself, dcat:CatalogRecord represents the record that describes a dataset in the catalog. The use of the CatalogRecord is considered optional. It is used to capture provenance information about dataset entries in a catalog. If this distinction is not necessary then CatalogRecord can be safely ignored.</p>
 
 <p><img alt="UML model of DCAT classes and properties" src="dcat-model.jpg"/></p>
-<p>All RDF examples in this document are written in Turtle syntax [[TURTLE-TR]].</p>
+<p>All RDF examples in this document are written in Turtle syntax [[turtle]].</p>
 <section>
 <h2 id="example">Basic Example</h2>
 <p>This example provides a quick overview of how DCAT might be used to represent a government catalog and its datasets. </p>
@@ -185,7 +279,7 @@
 </pre>
 
 <p>In order to express frequency of update in the example above, we chose to use an instance from the <a href="http://www.w3.org/TR/vocab-data-cube/#dsd-cog">Content-Oriented Guidelines</a> developed as part 
-of the W3C Data Cube Vocabulary efforts. Additionally, we chose to describe the spatial and temporal coverage of the example dataset using URIs from <a href="http://www.geonames.org/">Geonames</a> and <a href="http://reference.data.gov.uk/id/interval">the Interval dataset</a> from data.gov.uk, respectively. A contact point is also provided where comments and feedback about the dataset can be sent. Further details about the contact point, such as email address or telephone number, can be provided using <a href="http://www.w3.org/Submission/vcard-rdf/">VCard</a>.</p>
+of the W3C Data Cube Vocabulary efforts. Additionally, we chose to describe the spatial and temporal coverage of the example dataset using URIs from <a href="http://www.geonames.org/">Geonames</a> and <a href="http://reference.data.gov.uk/id/interval">the Interval dataset</a> from data.gov.uk, respectively. A contact point is also provided where comments and feedback about the dataset can be sent. Further details about the contact point, such as email address or telephone number, can be provided using VCard [[vcard-rdf]].</p>
 
 <p>The dataset distribution :dataset-001-csv can be downloaded as a 5Kb CSV file. This information is 
 represented via an RDF resource of type dcat:Distribution.
@@ -344,7 +438,7 @@
   <tbody>
     <tr><td  class="prop">Definition:</td><td>Date of formal issuance (e.g., publication) of the catalog.</td></tr>
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> 
-    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[XMLSCHEMA-2]]
+    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[xmlschema-2]]
     </td></tr>
     <tr><td class="prop">See also:</td><td><a href="#Property:dataset_release_date" title=""> dataset release date</a>, <a href="#Property:record_release_date" title=""> catalog record listing date</a> and <a href="#Property:distribution_release_date" title=""> distribution release date</a></td></tr>
   </tbody>
@@ -358,7 +452,7 @@
   <tbody>
     <tr><td  class="prop">Definition:</td><td>Most recent date on which the catalog was changed, updated or modified.</td></tr>
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> 
-    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[XMLSCHEMA-2]]
+    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[xmlschema-2]]
     </td></tr>
     <tr><td class="prop">See also:</td><td><a href="#Property:dataset_update_date" title=""> dataset modification date</a>, <a href="#Property:record_update_date" title=""> catalog record modification date</a> and <a href="#Property:distribution_update_date" title=""> distribution modification date</a></td></tr>
   </tbody>
@@ -505,14 +599,14 @@
     a <em>dataset</em> and metadata about the <em>dataset's entry in the catalog</em>. For example, the <i>publication date</i> property of the <i>dataset</i> reflects 
     the date when the information was originally made available by the publishing agency, while the publication date of the <i>catalog record</i> is the date when the dataset was added to the catalog. 
     In cases where both dates differ, or where only the latter is known, the <em>publication date</em> should only be specified for the catalog record.
-    Notice that the W3C PROV Ontology [[PROV-O]] allows describing further provenance information such as the details of the process and the agent involved in a particular change to a dataset.
+    Notice that the W3C PROV Ontology [[prov-o]] allows describing further provenance information such as the details of the process and the agent involved in a particular change to a dataset.
     </td></tr>
     <tr><td class="prop">See also</td><td><a href="#Class:_Dataset">Dataset</a></td></tr>
   </tbody>
 </table>
 
 
-<p>If a catalog is represented as an RDF Dataset with named graphs (as defined in [[SPARQL-QUERY-11]]), 
+<p>If a catalog is represented as an RDF Dataset with named graphs (as defined in [[sparql11-query]]), 
 then it is appropriate to place the description of each dataset 
 (consisting of all RDF triples that mention the dcat:Dataset, dcat:CatalogRecord, and any of its dcat:Distributions) 
 into a separate named graph. The name of that graph should be the IRI of the catalog record.
@@ -547,7 +641,7 @@
   <tbody>
     <tr><td  class="prop">Definition:</td><td>The date of listing the corresponding dataset in the catalog.</td></tr>
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> 
-    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[XMLSCHEMA-2]]
+    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[xmlschema-2]]
      </td></tr>
     <tr><td class="prop">Usage note:</td><td>This indicates the date of listing the dataset in the catalog and not the publication date of the dataset itself.</td></tr>
     <tr><td class="prop">See also:</td><td><a href="#Property:dataset_release_date" title=""> dataset release date</a></td></tr>
@@ -563,7 +657,7 @@
   <tbody>
     <tr><td  class="prop">Definition:</td><td>Most recent date on which the catalog entry was changed, updated or modified.</td></tr>
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> 
-    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[XMLSCHEMA-2]] 
+    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[xmlschema-2]] 
      </td></tr>
     <tr><td class="prop">Usage note:</td><td>This indicates the date of last change of a catalog entry, i.e. the catalog metadata description of the dataset, and not the date of the dataset itself.</td></tr>
     <tr><td class="prop">See also:</td><td><a href="#Property:dataset_update_date" title=""> dataset modification date</a></td></tr>
@@ -645,7 +739,7 @@
   <tbody>
     <tr><td  class="prop">Definition:</td><td>Date of formal issuance (e.g., publication) of the dataset.</td></tr>
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> 
-    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[XMLSCHEMA-2]]
+    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[xmlschema-2]]
     </td></tr>
     <tr><td class="prop">Usage note:</td><td>This property should be set using the first known date of issuance.</td></tr>
   </tbody>
@@ -659,7 +753,7 @@
   <tbody>
     <tr><td  class="prop">Definition:</td><td>Most recent date on which the dataset was changed, updated or modified.</td></tr>
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> 
-    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[XMLSCHEMA-2]]
+    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[xmlschema-2]]
     </td></tr>
     <tr><td class="prop">Usage note:</td><td>The value of this property indicates a change to the actual dataset, not a change to the catalog record. An absent value may indicate that the dataset has never changed after its initial publication, or that the date of last modification is not known, or that the dataset is continuously updated.</td></tr>
     <tr><td class="prop">See also:</td><td><a href="#Property:dataset_frequency">frequency</a></td></tr>
@@ -782,7 +876,7 @@
 <table class="definition">
   <thead><tr><th>RDF Property:</th><th><a href="http://www.w3.org/ns/dcat#contactPoint">dcat:contactPoint</a></th></tr></thead>
   <tbody>
-    <tr><td  class="prop">Definition:</td><td>Link a dataset to relevant contact information which is provided using VCard [[VCARD]].</td></tr>
+    <tr><td  class="prop">Definition:</td><td>Link a dataset to relevant contact information which is provided using VCard [[vcard-rdf]].</td></tr>
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2006/vcard/ns#Kind">vcard:Kind</a></td></tr>
   </tbody>
 </table>
@@ -875,7 +969,7 @@
   <tbody>
     <tr><td  class="prop">Definition:</td><td>Date of formal issuance (e.g., publication) of the distribution.</td></tr>
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> 
-    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[XMLSCHEMA-2]]
+    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[xmlschema-2]]
     </td></tr>
     <tr><td class="prop">Usage note:</td><td>This property should be set using the first known date of issuance.</td></tr>
     <tr><td class="prop">See also:</td><td><a href="#Property:dataset_release_date" title=""> dataset release date</a></td></tr>
@@ -890,7 +984,7 @@
   <tbody>
     <tr><td  class="prop">Definition:</td><td>Most recent date on which the distribution was changed, updated or modified.</td></tr>
     <tr><td class="prop">Range:</td><td><a href="http://www.w3.org/2000/01/rdf-schema#Literal">rdfs:Literal</a> 
-    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[XMLSCHEMA-2]]</td></tr>
+    encoded using the relevant <a href="http://www.w3.org/TR/NOTE-datetime">ISO 8601 Date and Time compliant string</a> and typed using the appropriate XML Schema datatype [[xmlschema-2]]</td></tr>
     <tr><td class="prop">See also:</td><td><a href="#Property:dataset_update_date" title=""> dataset modification date</a></td></tr>
   </tbody>
 </table>