Introduction
Statements are a human-readable expression of the content or note about the entity being referred to. Even if there are structured forms of the resources, these textual descriptions are useful to render to end users. They can have both internationalized content, as well as internationalized labels in the form of Name instances associated with them. These statements are embedded within the resource being described, rather than separate long form texts.
Statements are described in the base patterns of the model documentation, and examples are present for practically every class.
Property Definitions
Properties of Names
| Property Name | Datatype | Requirement | Description |
|---|---|---|---|
type |
string | Required | The class for the statement, which MUST be the value "LinguisticObject" |
_label |
string | Optional | A human readable label, intended for developers |
content |
string | Required | The string value of the statement |
classified_as |
array | Recommended | An array of json objects, each of which is a further classification of the statement and MUST follow the requirements for Type |
language |
array | Recommended | An array of json objects, each of which is a language present in the content of the statement and MUST follow the requirements for Language |
identified_by |
array | Recommended | An array of json objects, each of which is a label or name for the statement, and MUST follow the requirements for Name |
referred_to_by |
array | Optional | An array of json objects, each of which is either a reference to a textual work that refers to the statement, or an embedded statement about this Statement |
Property Diagram
Incoming Properties
Statements are typically found as the object of the following properties. This list is not exhaustive, but is intended to cover the most likely cases.
| Property Name | Source Endpoint | Description |
|---|---|---|
referred_to_by |
All | Statements are almost always found in the referred_to_by property, and can be present in any of the API endpoints |
(And that's all!)
Example
An object is referred_to_by a Description in English.
- The description has a
typeof "LinguisticObject" - It is
classified_asa description, with anidof aat:300411780 andtypeof "Type". The description concept is in turnclassified_asa type of "brief text" - It has
contentof "A small greenstone pendant..." - It is
identified_bya display label, which has atypeof "Name", andcontentof "Description" - It has a
languageof English, which has anidof aat:300388277 - It has a statement about the description, saying that it was provided by the artist.
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/object/10",
"type": "HumanMadeObject",
"referred_to_by": [
{
"type": "LinguisticObject",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300435416",
"type": "Type",
"_label": "Description",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300418049",
"type": "Type",
"_label": "Brief Text"
}
]
}
],
"content": "A small greenstone pendant surrounded by silver",
"identified_by": [
{
"type": "Name",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300404669",
"type": "Type",
"_label": "Display Title"
}
],
"content": "Description"
}
],
"referred_to_by": [
{
"type": "LinguisticObject",
"content": "Description provided by the artist"
}
],
"language": [
{
"id": "http://vocab.getty.edu/aat/300388277",
"type": "Language",
"_label": "English"
}
]
}
]
}
