spec update and /prefixes/

the prefixes.jsonld file is now generated from _data/prefixes.yaml

Author: letmaik

_data/prefixes.json

@@ -0,0 +1,10 @@
+covjson: https://covjson.org/def/core#
+covjsondt: https://covjson.org/def/domainTypes#
+xsd: http://www.w3.org/2001/XMLSchema#
+ssn: http://www.w3.org/2005/Incubator/ssn/ssnx/ssn#
+skos: http://www.w3.org/2004/02/skos/core#
+dct: http://purl.org/dc/terms/
+hydra: http://www.w3.org/ns/hydra/core#
+qudt: http://qudt.org/schema/qudt#
+ignf: http://data.ign.fr/def/ignf#
+inspiregloss: http://inspire.ec.europa.eu/glossary/

_data/prefixes.yaml

@@ -1,9 +1,53 @@
 ---
 layout: default
-title: Prefixes
+title: Namespace Prefixes
 permalink: /prefixes/
 ---
 
-{% for prefsuf in site.data.prefixes['@context'] %}
-  {{ prefsuf[0] }}: {{ prefsuf[1] }}
-{% endfor %}
+<div class="container">
+	<div class="page-header">
+	  <h2>Prefix Registry</h2>
+	</div>
+	<p>
+	  An easy way to extend CoverageJSON is to add new fields to it.
+	  In order to avoid name clashes (both with other extensions and future versions of the format)
+	  it is recommended to use names of the form <code>"prefix:suffix"</code>.
+	  If CoverageJSON documents using that prefix shall be published more widely,
+	  then it should be registered together with the corresponding namespace URI.
+	  A registration avoids name clashes and eases common understanding of extensions without establishing the full
+	  machinery of JSON-LD for example.
+	  More details can be found in the <a href="http://covjson.org/spec/#extensions">"Extensions" section</a>
+	  of the specification.
+	</p>
+	
+	<div class="panel panel-primary">
+	  <div class="panel-heading">
+	    <h3 class="panel-title">How to register a prefix</h3>
+	  </div>
+	  <div class="panel-body">
+	    <strong>Very simple!</strong>
+	    The only thing you have to do is edit the 
+	    <a href="https://github.com/covjson/covjson.github.io/blob/master/_data/prefixes.yaml">prefixes.yaml</a>
+	    file on GitHub and submit a pull request. Once the request is accepted, the prefix entry immediately appears in
+	    the table below, as well as in the <a href="http://covjson.org/prefixes.jsonld">covjson.org/prefixes.jsonld</a>
+	    file which is included in the <a href="http://covjson.org/context.jsonld">default JSON-LD context</a>,
+	    making it available for linked data applications.
+	    If you register a prefix for a common namespace, try to use an established prefix.
+	    The website <a href="http://prefix.cc/">prefix.cc</a> may provide some help for that.
+	  </div>
+	</div>
+	
+	<table class="table">
+	  <thead>
+	    <tr>
+	      <th>Prefix</th>
+	      <th>URI</th>
+	    </tr>
+	  </thead>
+	  <tbody>
+			{% for entry in site.data.prefixes %}
+			  <tr><td>{{ entry[0] }}</td><td><a href="{{ entry[1] }}" target="_blank">{{ entry[1] }}</a></td></tr>
+			{% endfor %}
+	  </tbody>
+	</table>
+</div>

prefixes.html

@@ -0,0 +1,8 @@
+---
+permalink: /prefixes.jsonld
+---
+{
+  "@context": {
+{% for entry in site.data.prefixes %}    "{{ entry[0] }}": "{{ entry[1] }}"
+{% endfor %}  }
+}