< Back | Home | Edit page | 🙋 Check for open issues |
Artsdata Guidelines regarding Persistent Identifiers
As per the W3C’s RDF specifications for linked open data, each named entity (for example, an event, a place or a person), class and property loaded in the Artsdata triple store must be denoted by a persistent identifier, represented as a URI (see this article to learn more about persistent identifiers).
Supported and recommended persistent identifiers
Artsdata assigns its own persistent identifiers (URIs) to named entities that meet minimum requirements for ID minting. Registered users can use the “Minter” feature to link or mint a new Artsdata ID for entities that are already loaded to the knowledge graph. They can also use the “Mint using Wikidata” feature to load a Wikidata item and mint a new Artsdata ID.
Artsdata also relies on external URIs. Artsdata supports all persistent identifiers from open knowledge bases, including:
- Wikidata;
- ISNI;
- VIAF;
- Musicbrainz.
Artsdata also accepts local URIS minted by data providers (read more below).
In order to guide data providers and consumers in the adoption and implementation of persistent identifiers, here are recommended persistent identifiers according to the entity type.
| Type | Artsdata ID | Wikidata ID | ISNI | Local URI |
|---|---|---|---|---|
| schema:Person | Recommended | Recommended | Recommended | Optional |
| schema:Organization schema:PerformingGroup |
Recommended | Recommended | Optional | Optional |
| schema:Place | Recommended | Recommended | Not a valid type for this ID | Optional |
| schema:Event | Recommended | Optional | Not a valid type for this ID | Optional |
The Artsdata ID, the Wikidata ID and the ISNI are globally-unique persistent identifiers intended to be referenced across a wide range of information systems, outside of their own web domain. This explains why they are sometimes called “global” identifiers, “bridge” identifiers or “external” identifiers. In these guidelines, they are called external URIs.
By contrast, “local” identifiers, for example database keys, are meant to be referenced internally, within the local information system. Local identifiers can also be expressed in the form of a URI within the web domain where the system – or the website – is hosted. These local URIs can be reconciled (i.e. matched) with external URIs to indicate that these URIs are identifying the same real-world entity (for example, a person, a place or an event)
In Schema structured data and in the Artsdata data model, local URIs are expected values for the @id property, whereas external URIs are expected values for the sameAs property.
How to integrate local URIs to structured data
See: Artsdata guidelines regarding the @id property and URIs
How to integrate external URIs into structured data
See: Artsdata guidelines regarding the sameAs property
How to retrieve persistent identifiers’ URIs
Option 1: Manual retrieval via the Artsdata interface
Anyone can use Artsdata’s search tool on the knowledge graph’s interface to find a entity and retrieve its Artsdata URI. You can find step-by-step instructions in this article. Once you’ve become familiar with the process, it takes less than 10 seconds to retrieve an Artsdata URI.
Option 2: Automated retrieval via the Artsdata reconciliation service
Developers can also call the Artsdata Reconciliation API to retrieve the Artsdata URIs. Depending on the application’s setting, this can work in a similar fashion as Google Search’s auto-suggestion feature: the user types in a performer name and the reconciliation service returns entities with similar names along with their Artsdata URI. When the user selects an entity, the full name and the Artsdata URI are automatically loaded in the application. Additional data points, including other persistent identifiers, can also be passed along with the Artsdata URI.
How to store external URIs in a local database
Coming soon…
About the Artsdata Identifier
The Artsdata ID is a globally-unique persistent identifier for any concept or named entity in the Artsdata knowledge graph. It can be assigned to performing arts entity types for which there exists at present no good persistent identifier (for example, an event). Any entity that meets minimal requirements and that passes SHACL validation can be minted an ID.
Third parties are welcome to contribute to assigning Artsdata IDs. Registered users may:
- Use the “Minter” feature, in the Artsdata interface, to mint or link an ID to an entity loaded to the knowledge graph;
- Use the “Mint using Wikidata” feature, in the Artsdata interface, to load an entity from Wikidata and to mint or link an ID for it;
- Use the Minting API to assign IDs to entities that have not been loaded to Artsdata yet.
Specifications
- URI format:
http://kg.artsdata.ca/resource/$1 - Regex for the ID:
^K\d+-\d+$ - Sample URI:
http://kg.artsdata.ca/resource/K12-438 - Note : The URI format doesn’t use a secured “https” protocol, as is often the case for URIs with content negotiation.