-
Notifications
You must be signed in to change notification settings - Fork 3
/
prefixes.html
53 lines (50 loc) · 2.08 KB
/
prefixes.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
---
layout: default
title: Prefix Registry
permalink: /prefixes/
---
<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 the prefix 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="https://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="https://covjson.org/prefixes.jsonld">covjson.org/prefixes.jsonld</a>
file which is included in the <a href="https://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>