Introduction
The Person API is a method of getting access to descriptions of people, living or dead. This would include artists and collectors, but also museum staff such as curators or conservators that perform their professional activities on or using artwork. The Person model is of average complexity, with many familiar properties and patterns, plus a few more specific fields. This results in an average complexity API that can result in reasonably long JSON responses if all of the fields have values.
For more information about the usage of Person data, please see the Person model description.
Property Definitions
Dereferencing an entity via the Person endpoint would result in a JSON-LD document containing a single JSON object with the following properties.
Properties of People
Property Name | Datatype | Requirement | Description |
---|---|---|---|
@context |
string, array | Required | The value MUST be the URI of the Linked Art context as a string, "https://linked.art/ns/v1/linked-art.json" or an array in which the URI is the last entry to allow for extensions |
id |
string | Required | The value MUST be the HTTP(S) URI at which the person's representation can be dereferenced |
type |
string | Required | The class for the person, which MUST be the value "Person" |
_label |
string | Recommended | A human readable label for the person, intended for developers |
classified_as |
array | Recommended | An array of json objects, each of which is a classification of the person and MUST follow the requirements for Type |
identified_by |
array | Recommended | An array of json objects, each of which is a name of the person and MUST follow the requirements for Name, or an identifier for the person and MUST follow the requirements for Identifier |
referred_to_by |
array | Optional | An array of json objects, each of which is a human readable statement about the person and MUST follow the requirements for Statement |
equivalent |
array | Optional | An array of json objects, each of which is a reference to an external identity and description of the current Person |
representation |
array | Optional | An array of json objects, each of which is a reference to a Visual Work that represents the current Person, and MUST follow the requirements for a reference |
member_of |
array | Optional | An array of json objects, each of which is a Group that the current Person is a member of and MUST follow the requirements for a reference to a Group |
subject_of |
array | Optional | An array of json objects, each of which is a reference to a Textual Work, the content of which focuses on the current Person, and MUST follow the requirements for a reference |
attributed_by |
array | Optional | An array of json objects, each of which is a Relationship Assignment that relates the current Person to another entity |
carried_out |
array | Optional | An array of json objects, each of which represents professional activities of the person and follows the requirements for Professional Activities described below. |
participated_in |
array | Optional | An array of json objects, each of which represents an event in which the person participated and follows the requirements for Events described below. |
contact_point |
array | Optional | An array of json objects, each of which is an address at which the person is reachable and MUST follow the requirements for an Identifier |
residence |
array | Optional | A place that the person was associated with, and MUST follow the requirements for a reference to a Place |
born |
json object | Optional | A json object representing the birth of the person, which follows the requirements for Births described below. |
died |
json object | Optional | A json object representing the death of the person, which follows the requirements for Deaths described below. |
Properties of Births, Deaths, Events and Professional Activities
Property Name | Datatype | Requirement | Description |
---|---|---|---|
id |
string | Optional | If present, the value MUST be a URI identifying the birth, death or professional activity |
type |
string | Required | The class for the birth, death or professional activity, which MUST be the value "Birth" , "Death" , "Event", or "Activity" respectively |
_label |
string | Recommended | A human readable label for the event, intended for developers |
identified_by |
array | Recommended | An array of json objects, each of which is a name for the event and MUST follow the requirements for Name, or an identifier for the event and MUST follow the requirements for Identifier |
classified_as |
array | Recommended | An array of json objects, each of which is a further classification of the event and MUST follow the requirements for Type |
timespan |
json object | Recommended | A json object recording when the event occured, which MUST follow the requirements for timespans |
referred_to_by |
array | Optional | An array of json objects, each of which is an embedded statement about the measurement |
took_place_at |
array | Optional | An array of json objects, each of which is a reference to a Place where the event occured |
caused_by |
array | Optional | An array of json objects, each of which is a reference to an Event that caused the current event to occur |
Property Diagram
JSON Schema
See the schema documentation and the schema itself
Incoming Properties
Person instances are typically found as the object of the following properties, other than the self-referential properties above. This list is not exhaustive, but is intended to cover the likely cases where other endpoints refer to people.
Property Name | Source Endpoint | Description |
---|---|---|
carried_out_by |
All | An activity that the Person carried out |
current_owner |
Object | An object owned by the Person |
current_custodian |
Object | An object in the custody of the Person |
current_permanent_custodian |
Object | An object that is normally in the custody of the Group |
represents |
Visual Work | Image content which represents the Person (the inverse of representation ) |
about |
Textual Work | Textual content that is about the Person |
transferred_custody_to |
Provenance | The activity of transferring custody of an object to the Person |
transferred_custody_from |
Provenance | The activity of transferring custody of an object away from the Person |
transferred_title_to |
Provenance | The activity of transferring ownership of an object to the Person |
transferred_title_from |
Provenance | The activity of transferring ownership of an object away from the Person |
paid_to |
Provenance | The activity of paying money to the Person from someone else |
paid_from |
Provenance | The activity of paying money from the Person to someone else |
Example
The JSON for a Person entry for the artist Rembrandt could be as below.
- It has the Linked Art context reference in
@context
- It self-documents its URI in
id
- It has a
type
of "Person" - It has a
_label
with the value "Rembrandt" for humans reading the JSON - It has a
classified_as
property with entries for ...- ... Male, which is in turn
classified_as
a Gender - ... Dutch, which is in turn
classified_as
a Nationality
- ... Male, which is in turn
- It has an
identified_by
property, with aName
for his full name of "Rembrandt Harmenszoon van Rijn" - It has a
referred_to_by
for a statement,classified_as
a Biography - It has a
born
property for his birth, with atimespan
and a location intook_place_at
. - It has a
died
property for his death, with atimespan
and a location intook_place_at
. - It has a
carried_out
for his professional activity, again withtimespan
andtook_place_at
properties, but alsoclassified_as
being professional activities - It has an
equivalent
to his ULAN identity - It has a
residence
with a reference to the Place where he lived - It has a
contact_point
for his former street address
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/0",
"type": "Person",
"_label": "Rembrandt",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300189559",
"type": "Type",
"_label": "Male",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300055147",
"type": "Type",
"_label": "Gender"
}
]
},
{
"id": "http://vocab.getty.edu/aat/300111175",
"type": "Type",
"_label": "Dutch",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300379842",
"type": "Type",
"_label": "Nationality"
}
]
}
],
"identified_by": [
{
"type": "Name",
"content": "Rembrandt Harmenszoon van Rijn"
}
],
"referred_to_by": [
{
"type": "LinguisticObject",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300435422",
"type": "Type",
"_label": "Biography Statement",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300418049",
"type": "Type",
"_label": "Brief Text"
}
]
}
],
"content": "Rembrandt was a Dutch draughtsman, painter and printmaker."
}
],
"born": {
"type": "Birth",
"_label": "Birth of Rembrandt",
"timespan": {
"type": "TimeSpan",
"begin_of_the_begin": "1606-07-15T00:00:00Z",
"end_of_the_end": "1606-07-16T00:00:00Z"
},
"took_place_at": [
{
"type": "Place",
"_label": "Leiden"
}
]
},
"died": {
"type": "Death",
"_label": "Death of Rembrandt",
"timespan": {
"type": "TimeSpan",
"begin_of_the_begin": "1669-10-04T00:00:00Z",
"end_of_the_end": "1669-10-05T00:00:00Z"
},
"took_place_at": [
{
"type": "Place",
"_label": "Amsterdam"
}
]
},
"carried_out": [
{
"type": "Activity",
"_label": "Active Dates",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300393177",
"type": "Type",
"_label": "Professional Activities"
}
],
"timespan": {
"type": "TimeSpan",
"begin_of_the_begin": "1631-01-01T00:00:00Z",
"end_of_the_end": "1669-10-05T00:00:00Z"
},
"took_place_at": [
{
"type": "Place",
"_label": "Amsterdam"
}
]
}
],
"residence": [
{
"type": "Place",
"_label": "Nieuwe Doelenstraat"
}
],
"contact_point": [
{
"type": "Identifier",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300386983",
"type": "Type",
"_label": "Street Address"
}
],
"content": "Jodenbreestraat 4, 1011NK Amsterdam"
}
],
"equivalent": [
{
"id": "http://vocab.getty.edu/ulan/500011051",
"type": "Person",
"_label": "Rembrandt"
}
]
}