Use both name and UUID as resolvable reference

[Sveino]

The reference data for SynchronousMachine.operatingMode is in Turle:

@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix nc: <http://entsoe.eu/ns/nc#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .

<http://energy.referencedata.eu/PropertyReference/SynchronousMachine.operatingMode> a <http://iec.ch/TC57/CIM100#PropertyReference>,
        skos:Concept ;
    nc:PropertyReference.mRID "1d3bb064-b765-4d06-992a-70f1ce3d0bd4" ;
    nc:PropertyReference.name "SynchronousMachine.operatingMode" ;
    dcterms:identifier "urn:uuid:1d3bb064-b765-4d06-992a-70f1ce3d0bd4" ;
    skos:definition "Current mode of operation." ;
    skos:inScheme "http://energy.referencedata.eu/PropertyReference" ;
    skos:prefLabel "SynchronousMachine.operatingMode" ;
    skos:topConceptOf "http://energy.referencedata.eu/PropertyReference" .

Only http://energy.referencedata.eu/PropertyReference/SynchronousMachine.operatingMode is resolvable should http://energy.referencedata.eu/PropertyReference/[SynchronousMachine.operatingMode](urn:uuid:1d3bb064-b765-4d06-992a-70f1ce3d0bd4) also be resolvable.

[Haigutus]

We need to be careful to not mix up intended use or URL and URN

https://www.rfc-editor.org/rfc/rfc3986#section-1.1.2
https://stackoverflow.com/questions/4913343/what-is-the-difference-between-uri-url-and-urn

Proposal:
In future develop a webservice where input of URN (example: urn:uuid:<resource_uuid>) will direct to the resource URL

[Sveino]

I am generally OK with this approach. This could in general be a ObjectRegistry Service that can include reference data and CGM.