Add two new spatial fields

There are now two new spatial fields to identify the geographical
coverage more specifically. The spatial-code will be used as a
standardized identifier that consists of a NUTS code and the
Amtlicher Gemeindeschlüssel which is separated by a slash.

The field spatial-uri is used to introduce linked data to the
metadata schema which makes it possible link resources which
embody the geographical coverage.

Signed-off-by: Konrad Reiche <konrad.reiche@fokus.fraunhofer.de>
Merge remote-tracking branch 'origin/master' into feature-spatial-extension
Add regular expression to specify spatial-code

I have added a regular expression to specify the spatial-code field.

Signed-off-by: Konrad Reiche <konrad.reiche@fokus.fraunhofer.de>
Update spatial-code description

Just made a small change to the spatial-code description.

Signed-off-by: Konrad Reiche <konrad.reiche@fokus.fraunhofer.de>
Relax regular expression for spatial-code

I have relaxed the pattern used to determine valid values for the
spatial-code field. In addition the example JSON is now complete
with respect to the newly updated schema.

Signed-off-by: Konrad Reiche <konrad.reiche@fokus.fraunhofer.de>
Change spatial fields into subfields

As decided by the data provider telephone conference the extended
spatial fields should become subfields of the spatial field.

Signed-off-by: Konrad Reiche <konrad.reiche@fokus.fraunhofer.de>
Merge branch 'master' into origin/feature/spatial-extensions

Signed-off-by: Konrad Reiche <konrad.reiche@fokus.fraunhofer.de>

Conflicts:
	OGPD_JSON_Schema.html
	beispiele/beispiel1.json
Add new proposal to encode spatial reference

In order to avoid conflicts between the ckanext-spatial field 'spatial'
a new field 'spatial_reference' is introduced to encapsulate the spatial
data. Also moved 'spatial-text' into this new field as well.

Signed-off-by: Konrad Reiche <konrad.reiche@fokus.fraunhofer.de>
Add new field to prevent duplicates in the future

A new field is added to prevent possible duplicates which can result
from harvesting other endpoints but CKAN. For instance, a CSV harvester
has to perform a metadata mapping. If different portals do that it
becomes unclear who 'owns' the dataset and which portal should be
prioritized when harvesting these duplicates. See #17.

Signed-off-by: Konrad Reiche <konrad.reiche@fokus.fraunhofer.de>
Merge branch 'feature/spatial-extension'
Merge branch 'feature/duplicate-precaution'
Merge spatial and duplicate precaution

Signed-off-by: Konrad Reiche <konrad.reiche@gmail.com>
Merge branch 'master' of github.com:fraunhoferfokus/ogd-metadata