URIs and IRIs are character strings identifying the nodes and edges in the graph. Defining them is an important step in creating an exploitable Knowledge Graph for your Company.
RFC 3986 defines a generic syntax for URIs:
- The scheme-specific part is often structured:
URIs are limited to ASCII characters. IRIs (Internationalized Resource Identifiers) allow Unicode (RFC 3987).
The following list of example IRIs demonstrate the broad scope of this concept:
Best practices in Corporate Memory¤
A good IRI is unique, stable, simple and manageable.
Define a useful IRI-Scheme that can be used for resources.
- Define a Base URI which is the common authority for all resources in your graph.
- Define subspaces where necessary, e.g. for each subproject or domain. Provide a prefix for each subspace. Examples:
https://data.company.org/hardware/for hardware artifacts
https://data.company.org/software/for software artifacts
PREFIX cohw: <https://data.company.org/hardware/>
PREFIX cosw: <https://data.company.org/software/>
- Based on these, build consistent schemes that define how your IRIs have to be build. Examples:
https://data.company.org/hardware/<ProductClass>/<Serialnumber>to identify an individual product
https://data.company.org/hardware/<ProductClass>/<Modelnumber>to identify a product model
Do not put a trailing slash at the end of resource IRIs as these cannot be used with prefix definitions in Turtle or SPARQL, which makes them more difficult to use.
- Spanish Government, URIs for Open Data resources
- European Union, URIs for Legal Resources
- UK, “Designing URI sets for the UK public sector”
- Other Resources