4.6 The reference component (`{reference}`)

The utility of the reference component is to uniquely identify a particular thing. ### 4.6.1 Reference components with type `model` For classes, collections, concepts, properties, and shapes, a human-readable reference component is strongly preferred. This makes it easier to type such IRIs in SPARQL queries. #### 4.6.1.1 Use of camelCase and CamelCase The following conventions are widely applied for the reference component of model IRIs: - The reference component for classes and node shapes starts with an uppercase letter and applies CamelCase. - The reference component for properties and property shapes starts with a lowercase letter and applies camelCase. When CamelCase and camelCase are applied, acronyms and abbreviations are treated as one word. In the absence of whitespace or reading characters, a sequence of two or more acronyms or abbreviations ― while an unlikely construct ― would otherwise become unidentifiable. The difference between using CamelCase for classes and camelCase for properties is often useful because a class and a property that links to instances of that class often have the same human-readable name. The following example illustrated this: ```turtle prefix album: <{scheme}://{domain}/{context}/id/album/> prefix def: <{scheme}://{domain}/{context}/def/> prefix person: <{scheme}://{domain}/{context}/id/person/> album:petSounds a def:Album. person:brianWilson def:album album:petSounds. ``` Notice how the album class (`def:Album`) can be distinguished from the property of having created an album (`def:album`). #### 4.6.1.2 Equivalent reference components For node shapes (`shp:`), the `{reference}` component is identical to the `{reference}` component of the corresponding class (`def:`) or concept (`con:`) IRI. For property shapes (`shp:`), the `{reference}` component is identical to the `{reference}` component of the corresponding RDF (`con:`) or OWL (`def:`) property IRI. If a property shape is uniquely connected to one node shape, then the `{reference}` component of the node shape IRI is also part of the property shape `{reference}` component. The following example uses one node shape IRI and one property shape IRI to illustrate this principle: ```turtle shp:Person sh:property shp:Person_name; sh:targetClass foaf:Person. shp:Person_name sh:path foaf:name. ``` ## 4.6.2 The `{reference}` component of graphs When the value of `type` is `graph`, the following reference components are commonly used:

graph:metadata: The graph that contains dataset metadata.
graph:model: The graph that contains the folksonomy and/or ontology.
graph:instances: The graph that contains records describing instance data.

#### 4.6.2.1 Graph names for linksets Linksets are graphs that contain links from a source dataset onto a target dataset. Graphs that contain linksets use the following naming scheme for the `{reference}` component: `graph:source-2-target` For example, a graph that contains the linkset from persons in one dataset to Wikidata instances can look as follows: `graph:person-2-wikidata` #### 4.6.2.2 IRIs with empty reference - The IRI that identifies the graph collection of a dataset have type `graph` and empty reference. - The IRIs that identify well-known IRIs have type `.well-known` and subtype `genid` and have empty reference.

4.6 The reference component ({reference})

4.6 The reference component (`{reference}`)

example

How to model

Graphs

Assets