<http://terminology.lido-schema.org/lido00099> <http://purl.org/dc/terms/licence> <http://creativecommons.org/licenses/by/4.0/> .
<http://terminology.lido-schema.org/lido00099> <http://www.w3.org/2004/02/skos/core#inScheme> <http://terminology.lido-schema.org/identifier_type> .
<http://terminology.lido-schema.org/lido00099> <http://creativecommons.org/ns#licence> <http://creativecommons.org/licenses/by/4.0/> .
<http://terminology.lido-schema.org/lido00099> <http://schema.vocnet.org/editingState> "Finalized" .
<http://terminology.lido-schema.org/lido00099> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2004/02/skos/core#Concept> .
<http://terminology.lido-schema.org/lido00099> <http://www.w3.org/2004/02/skos/core#example> "**HDL** (Handle) can be expressed as URIs by prefixing the resolver URL http://hdl.handle.net/:\nhttp://hdl.handle.net/2027/mdp.39015000000482\n\n**ISSN**s (International Standard Serial Number) can be expressed as URIs in the urn scheme according to https://tools.ietf.org/html/rfc3044: \nurn:ISSN:1534-0481\n\n**ISNI**s (International Standard Name Identifiers) can be expressed as URIs by prefixing the resolver URL http://isni.org/:\nhttp://isni.org/000000012150090X\n\n**ARK**s (Archival Resource Keys) can be expressed as URIs by prefixing the Name Mapping Authority Hostport (NMAH) part as described in https://tools.ietf.org/html/draft-kunze-ark-18:\n\n    [http://gallica.bnf.fr/ark:/12148/bpt6k107371t]\n    [      NMAH           /       ark             ]\n \n**DOI**s (Digital Object Identifiers ISO 26324) can be expressed as URIs by prefixing the resolver URL http://dx.doi.org/:\nhttp://dx.doi.org/10.1594/PANGAEA.726855\n\n**ISBN**s (International Standard Book Numbers ISO 2108:2005) can be expressed as URIs in two different ways (which might complicate comparison of identifiers). \n\nExample of an ISBN in the urn scheme according to (https://tools.ietf.org/html/rfc3187):\nURN:ISBN:978-3-7657-1538-9\n\nIt is possible to use the ISBN as an actionable ISBN (ISBN-A https://www.doi.org/factsheets/ISBN-A.html and https://www.isbn-international.org/content/other-identifiers ) within the resolvable DOI namespace (prefix 10.978 and 10.979 are reserved within the DOI namespace). The URIs are defined to be unique but not neccessarily resolvable, if not registered:\nhttp://dx.doi.org/10.978.37657/15389\n\nFor other published identifiers (including URNs as URIs) use a community accepted (and adopted) good pratice depending on the scope and potential use. In Germany, for example, cultural heritage institutions might be identified by an **ISIL** (International Standard Identifier for Libraries and Related Organizations, ISO 15511). A good practice in that case is to use the resolver URI http://ld.zdb-services.de/resource/organisations/*ISIL* (e.g., http://ld.zdb-services.de/resource/organisations/DE-1).\n\n[Based on [Request for Comments: 3650 – Handle System Overview](http://www.rfc-editor.org/rfc/rfc3650.txt)]"@en .
<http://terminology.lido-schema.org/lido00099> <http://purl.org/dc/terms/created> "2010-04-30T18:12:09+01:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
<http://terminology.lido-schema.org/lido00099> <http://xe.vocnet.org/alias> <http://terminology.lido-schema.org/identifier_type/uri> .
<http://terminology.lido-schema.org/lido00099> <http://www.w3.org/2004/02/skos/core#scopeNote> "Universal Resource Identifiers (URIs) can be used to establish relationships between resources from disparate source systems.\n\nIdentifiers, such as Digital Object Identifier (DOI), Handle (HDL), International Standard Book Number (ISBN), International Standard Music Number (ISMN), International Standard Name Identifier (ISNI), International Standard Recording Code (ISRC), International Standard Serials Number (ISSN), should be expressed as Universal Resource Identifiers (URIs). See examples for recommendations.\nDue to the lack of discovery options for resolvers for the various Uniform Resource Name (URN) schemes it is recommended to express URNs as URLs including the resolver address.\n\nIt is highly recommended to express URIs as HTTP URIs whenever applicable."@en .
<http://terminology.lido-schema.org/lido00099> <http://purl.org/dc/terms/modified> "2022-12-13T13:44:51+01:00"^^<http://www.w3.org/2001/XMLSchema#dateTime> .
<http://terminology.lido-schema.org/lido00099> <http://www.w3.org/2004/02/skos/core#prefLabel> "URI"@de .
<http://terminology.lido-schema.org/lido00099> <http://www.w3.org/2004/02/skos/core#prefLabel> "URI"@en .
<http://terminology.lido-schema.org/lido00099> <http://www.w3.org/2004/02/skos/core#altLabel> "Uniform Resource Identifier"@en .
<http://terminology.lido-schema.org/lido00099> <http://www.w3.org/2004/02/skos/core#altLabel> "Uniform Resource Identifier"@de .
<http://terminology.lido-schema.org/lido00099> <http://purl.org/iso25964/skos-thes#status> "Approved" .
<http://terminology.lido-schema.org/lido00099> <http://www.w3.org/2004/02/skos/core#definition> "**URI**, as a value for the type attribute of  any of the LIDO identifier elements, such as *Actor Identifier*, *Concept Identifier*, *Event Identifier*, designates a globally unique assigned code that conforms to the syntax as defined in [IETF RFC3986](https://www.ietf.org/rfc/rfc3986.txt &quot;Internet Engineering Task Force: Request for Comments 3986 – Uniform Resource Identifier (URI): Generic Syntax&quot;). An URI may have meaning outside of the local system.\n[Based on [Request for Comments: 3986 – Uniform Resource Identifier (URI): Generic Syntax](https://www.ietf.org/rfc/rfc3986.txt)]"@en .