Introduction
All activities are carried out by some actor, either a person (Person
) or a group of people (Group
) such as an organization or company. The identity and description of these actors are very important to record in order to provide the human context for the activities, and their related places and objects. The creators, finders, owners, sellers and curators of objects are all relevant to understanding our cultural heritage.
As far as scope goes, the model does not consider that non-humans (such as software or animals) can perform activities, as activities require some notion of intent. Thus the productions of the infamous monkey selfies from 2011 are not carried out by anyone, as the monkey cannot do it and the photographer did not intend for the photographs to be taken.
This model does not aim to capture all of the possible information about a Person or Group, or their relationships to other people, objects, places or activities. Instead it attempts to capture sufficient information to distinguish the actor from others, and to align the actor with other systems.
Types
There are two primary types of acting agent, Person
and Group
. Person
is used for humans, and Group
is used for any collective set of humans. Groups typically are able to take action as a coherent whole, but in some cases this is overlooked for simplicity's sake. For example, it is useful to be able to say that "The Museum" acquired a painting or "The Workshop" produced a sculpture, when in fact it was some subset of the members of the group that actually performed the activity but we do not know exactly who.
Person
and Group
are sub-classes of the Actor
class, which might be used as a fallback when it is not known whether the actor is a Person or a Group. For example, if a sale of an object is listed as being from an art dealer called "Smith", it is unclear whether it refers to a person via their family name, or to an organization named after its owner. Equally, if there is no information about the actor currently available, but identity is desired such that it can later be reconciled or used because there is some other information known, then the use of Actor
is likely needed in this case as well. This is only to be used when the nature of the actor is unknown to avoid asserting the existence of a Person when it might have been a Group, or vice versa.
Example:
The person J. Smith is a member of a group, Museum Organization.
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/2",
"type": "Person",
"_label": "J. Smith",
"member_of": [
{
"type": "Group",
"_label": "Museum Organization",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300312281",
"type": "Type",
"_label": "Museum"
}
]
}
]
}
Names
Names are described in detail in the shared patterns section.
Example:
A person named "J. Smith"
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/3",
"type": "Person",
"_label": "J. Smith",
"identified_by": [
{
"type": "Name",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300404670",
"type": "Type",
"_label": "Primary Name"
}
],
"content": "J. Smith"
}
]
}
Parts of Names
Personal names can often be broken down into parts, with different types. The types are given using the classified_as
property. The name parts are themselves Name
s, and are included in the part
set in the same way as other partitioning. The type of name is given using classified_as
, in the regular fashion. Western name division vocabulary is given below, and other name part types should be suggested.
Example:
A person named 'Joan A. Smith"
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/4",
"type": "Person",
"_label": "Joan A. Smith",
"identified_by": [
{
"type": "Name",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300404670",
"type": "Type",
"_label": "Primary Name"
}
],
"content": "Joan A. Smith",
"part": [
{
"type": "Name",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300404651",
"type": "Type",
"_label": "Given Name"
}
],
"content": "Joan"
},
{
"type": "Name",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300404654",
"type": "Type",
"_label": "Middle Name"
}
],
"content": "A."
},
{
"type": "Name",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300404652",
"type": "Type",
"_label": "Family Name"
}
],
"content": "Smith"
}
]
}
]
}
Identity
People and Organizations are often assigned identifiers that should be recorded and tracked in the same way as any other identity. These follow the same basic pattern as for other identifiers, with identified_by
being used with an Identifier
resource.
Example:
A local identifier for the person is "643".
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/5",
"type": "Person",
"_label": "Xavier Y. Zeelander",
"identified_by": [
{
"type": "Identifier",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300404621",
"type": "Type",
"_label": "Owner-Assigned Number"
}
],
"content": "643"
}
]
}
Equivalent Resources
There may be other identifiers for the person available in external systems, such as ULAN or any of a dozen others. If all of the information needed about the person is available from that system, then it is recommended to simply use that identifier directly as the URI for the Person. If there is a requirement to maintain separate information about the person, then the equivalent
property should be used to align the two. This might happen when, for example, the local data has additional information about which documents refer to the person, or more detailed biographical information.
Example:
The equivalent resource in ULAN for a local Vincent Van Gogh Person entity is http://vocab.getty.edu/ulan/500115588
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/6",
"type": "Person",
"_label": "Vincent Van Gogh",
"equivalent": [
{
"id": "http://vocab.getty.edu/ulan/500115588",
"type": "Person",
"_label": "Vincent Van Gogh"
}
]
}
Addresses
People and Organizations often have addresses, physical or online, via which they can be contacted. This includes mailing addresses, email addresses and so forth. These are referenced separately from Names and Identifiers, as many Actors might have the same contact point. The address is an identifier for a location or service, and is thus modeled as an Identifier. This means it does not have language information, unlike Names, but addresses are not inherently linguistic.
This Identifier
is then related to the actor via the contact_point
property. They can be classified_as
different types, and use the content
property to capture the address itself.
Example:
The person A. Bacchus has an email address, and can be contacted via mail at the museum they are employed by.
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/7",
"type": "Person",
"_label": "A. Bacchus",
"member_of": [
{
"type": "Group",
"_label": "Example City Museum",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300312281",
"type": "Type",
"_label": "Museum"
}
],
"contact_point": [
{
"type": "Identifier",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300386983",
"type": "Type",
"_label": "Street Address"
}
],
"content": "1200 Museum Drive, Example City"
}
]
}
],
"contact_point": [
{
"type": "Identifier",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300435686",
"type": "Type",
"_label": "Email Address"
}
],
"content": "a.person@example.org"
}
]
}
Life Events
There are key events in a person or organization's lifespan that are often recorded as they contribute core information for determining the identity of the actor. These include the birth or formation, death or dissolution, and the period in which they carried out the work they are known for.
Birth and Death / Formation and Dissolution
Like the production of objects or the creation of texts, people and organizations also come into and out of existence through events. These events can take place at certain Places, and happen at certain times.
People are born in Birth
events and die in Death
events, related to the person by the born
and died
properties respectively. Groups are formed in Formation
events, and dissolved in Dissolution
events, referenced via the formed_by
and dissolved_by
properties. These classes are modeled not as Activities, but as Events that are not themselves carried out by anyone. They are the coming into existence instant of the person, not the conception of the couple, the labor of the mother, or potentially the killing by a murderer. These activities can be modeled as causes, as described below.
Birth and Death do not have any properties of their own that are used in the model, only those inherited from the event superclass, such as timespan
and took_place_at
.
!!! "note" "Inanimate Thing or Dead Person?"
After death, people are still instances of Person
which is a subclass of Actor
, even though they can no longer carry out activities. People in comas or otherwise completely incapacitated also cannot carry out activities, but are not temporarily non-Actors. The modeling that death is a transformation from an instance of Person to an instance of Thing adds complexity for the sake of purity, but does not add any actual value. Thus a burial activity (aat:300263485) buries a Person, not a Thing-that-used-to-be-a-Person. However if the skeleton is then dug up and exhibited, it is exhibited as a Thing. There is, therefore, a transition at some undetermined point.
Example: The birth and death of Amanda B. Curtlett.
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/8",
"type": "Person",
"_label": "Amanda B. Curtlett",
"born": {
"type": "Birth",
"timespan": {
"type": "TimeSpan",
"begin_of_the_begin": "1767-01-09T00:00:00",
"end_of_the_end": "1767-01-09T23:59:59"
}
},
"died": {
"type": "Death",
"timespan": {
"type": "TimeSpan",
"begin_of_the_begin": "1824-08-21T00:00:00",
"end_of_the_end": "1824-08-21T23:59:59"
},
"took_place_at": [
{
"type": "Place",
"_label": "Death Place"
}
]
}
}
Example: The formation and dissolution of the ill-fated Example Organization
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/group/1",
"type": "Group",
"_label": "Example Organization",
"formed_by": {
"type": "Formation",
"_label": "Formation of Example Organization",
"timespan": {
"type": "TimeSpan",
"begin_of_the_begin": "1639-12-01T00:00:00",
"end_of_the_end": "1639-12-31T23:59:59"
}
},
"dissolved_by": {
"type": "Dissolution",
"_label": "Dissolution of Example Organization",
"timespan": {
"type": "TimeSpan",
"begin_of_the_begin": "1790-06-12T00:00:00",
"end_of_the_end": "1790-06-12T23:59:59"
}
}
}
Active Dates
It is often useful to know where and when the person or organization was active in their professional function. For example, an artist might have started painting when they were 20, stopped by 30, and only painted in Italy. This information can be used to help eliminate dubious attributions, for example.
The property for the Person or Group is carried_out
, the inverse of the more familiar carried_out_by
from Activities to Actors. The Activity
resource should be classified_as
aat:300393177, meaning the time when the actor is actively performing their primary professional function. The other properties of activities can and should also be used.
Example: Patrick Q. Robertson was active between 1910-01-01 and 1934-03-21
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/9",
"type": "Person",
"_label": "Patrick Q. Robertson",
"carried_out": [
{
"type": "Activity",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300393177",
"type": "Type",
"_label": "Professional Activities"
}
],
"timespan": {
"type": "TimeSpan",
"begin_of_the_begin": "1910-01-01T00:00:00",
"end_of_the_end": "1934-03-21T00:00:00"
}
}
]
}
Participation in Events
As well as activities which are carried out by the person, there are also events in which the person participates, but it would not be correct to say that they were solely responsible for them. In these cases we can use a similar term: participated_in
. This would be useful for baptisms, engagements, weddings, traveling such as a "Grand Tour", and so forth.
Example: Baby C. D'Ernesto was baptized on 1879-10-14.
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/10",
"type": "Person",
"_label": "Baby C. D'Ernesto",
"participated_in": [
{
"type": "Event",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300069030",
"type": "Type",
"_label": "Baptism"
}
],
"timespan": {
"type": "TimeSpan",
"begin_of_the_begin": "1879-10-14T00:00:00",
"end_of_the_end": "1879-10-14T23:59:59"
}
}
]
}
Biographical Information
Biography Note
Biographical descriptions follow the LinguisticObject
pattern, with biography (aat:300080102) as the classification. In all other respects, it is a vanilla usage of a resource being referred_to_by
a particular text.
Example: David E. Frederickson's very short example biography.
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/11",
"type": "Person",
"_label": "David E. Frederickson",
"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": "David was born at a very early age."
}
]
}
Nationality
Nationality is modeled as a Type that is associated with the Person, rather than as a Group as described in the CIDOC-CRM ontology document. This is because all of the people, across all time, who have had a particular nationality, cannot take action as a single coherent entity. As Group is a sub-class of Actor, it is not thought to be an appropriate class for this use. Without proliferating new classes (e.g. sets of people that are not actors), the traditional and perfectly consistent way to describe nationality is as a flag on the person, which is modeled as a Type.
The Type
resource should have aat:300379842 as one of its classifications, such that a consuming application can find all of the nationality types from amongst the person's classifications. The nationality resource should either be from an established vocabulary of nationalities, or have an exact_match
to an established vocabulary entry if additional local information is necessary to record, such as a particular name for that nationality.
Example: Jeremy K. Lintott is a British national.
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/12",
"type": "Person",
"_label": "Jeremy K. Lintott",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300111159",
"type": "Type",
"_label": "British",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300379842",
"type": "Type",
"_label": "Nationality"
}
]
}
]
}
Ethnicity
Ethnicity is separate from nationality, as it refers to a social group or culture as opposed to a political nation or state. The same rationale as for Nationality being a classification also applies to ethnicity or culture -- it is unlikely to be a coherent collective capable of intentional action.
Gender
Gender is a debated and politically charged topic. The intent of this section is not to take a stand on those debates, but instead to allow the representation of data in museum and other information management systems to be made accessible.
Gender is not specifically discussed in CRM, in fact it was even deleted from a previous version, and the modeling follows the same classification pattern as for nationality and culture. This allows a plethora of gender diversity, and does not make any specific statements about biological versus assumed versus preferred gender roles. The gender must be classified_as
aat:300055147.
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/13",
"type": "Person",
"_label": "Mabel N. Overton",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300189557",
"type": "Type",
"_label": "Feminine",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300055147",
"type": "Type",
"_label": "Gender"
}
]
}
]
}
Digital Integration
Images of the person can also be provided, following the common pattern for digital resources. Only the basic image case is shown below, the other scenarios can easily be determined from the referenced digital integration for objects.
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/14",
"type": "Person",
"_label": "Gertrude H. Ingram",
"representation": [
{
"type": "VisualItem",
"digitally_shown_by": [
{
"type": "DigitalObject",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300215302",
"type": "Type",
"_label": "Digital Image"
}
],
"access_point": [
{
"id": "http://example.org/images/gertrude.jpg",
"type": "DigitalObject"
}
]
}
]
}
]
}
Social Relationships
Social relationships or bonds are very important for understanding how an individual fits in to society, tracing influences and interactions. That said, they are not a core part of the Linked Art model, as there are many (many!) different types of relationship that are both recorded and interesting. Instead, we use the extension pattern of an AttributeAssignment
to assert that a relationship exists or existed, with a reference to a vocabulary term to make the type of relationship explicit.
For more information about Attribute Assignments, please see the assertions page.
Example: Mary is the student of Henrietta
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/15",
"type": "Person",
"_label": "Henrietta I. Little",
"attributed_by": [
{
"type": "AttributeAssignment",
"_label": "Assign Mary as Student of Henrietta",
"assigned": [
{
"id": "https://linked.art/example/person/16",
"type": "Person",
"_label": "Mary N. Oppleton"
}
],
"assigned_property": {
"id": "http://vocab.getty.edu/aat/300025909",
"type": "Type",
"_label": "Student"
}
}
]
}
Organization Membership
As discussed above, Organizations can be seen as the actor when it comes to their roles in various events. For example, an auction is likely to be carried out by an organization, and they can own and curate objects.
The only significantly new aspect to organizational actors, compared to people, is that they can have members. These members can be either sub-groups, such as a department within a museum, or individuals.
For example, a curator could be a member_of
a department, which is in turn a member of the wider institution. This is simply the inverse of member
relationship described in the base patterns.
{
"@context": "https://linked.art/ns/v1/linked-art.json",
"id": "https://linked.art/example/person/17",
"type": "Person",
"_label": "Sameen T. Underwood",
"member_of": [
{
"type": "Group",
"_label": "Paintings Department",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300263534",
"type": "Type",
"_label": "Department"
}
],
"member_of": [
{
"type": "Group",
"_label": "Example Museum",
"classified_as": [
{
"id": "http://vocab.getty.edu/aat/300312281",
"type": "Type",
"_label": "Museum"
}
]
}
]
}
]
}