How should I model parts of Actor names?

Priority 2, Best Practice Established

Problem Statement

When representing an actor within a museum Collection Management System, it is a common practice to break apart names into their components. For instance, "John Smith" could be represented by a first name of "John" and a last name of "Smith".

Additional name parts might include titles, suffixes, prefixes, or middle names.

Are these essential components of the record, and if so, how should they be modeled?

Best Practice:

AAC best practice is to represent the parts of the names as separate Actor Appelations, typed using the AAT vocabulary. If this information is provided by an institution, is conceivably useful for users (for example by an academic researching name parts), and should thus be made available.

We do NOT recommend splitting names into components as part of a mapping process. Additionally, we acknowledge that this modelling may occasionaly mis-represent the ground truth if the institution's provided data is inaccurate, however that is broadly true of all data. Care should be taken in mapping to correctly understand the institution's intention when providing the information.

Additionally, the existing common practice for mapping this information is to use E82 Actor Appellation for representing Actor names. We recommend continuing this practice.

Discussion:

TODO: Include references to the github discussion of this issue here.

(From Rob, via email, 9/19/2016)

I prefer the much simpler pattern of predicates, as established for many years by foaf and practically every other ontology and model out there. has_type to an AAT entry on a class with a note for the string ... see complexity and why everyone hates CRM.

Reference:

Linked Open Data FAQs

Defining Types

How do I specify types for entities?
Priority 1
✔ Best Practice Established
How do I specify types for predicates?
Priority 1
✔ Best Practice Established
What existing extensions to the CIDOC-CRM should I use?
Priority 2
✔ Best Practice Established

Defining URL Structures

What URL should I use for unknown Actors?
Priority 2
✔ Best Practice Established
What is the root URL for each AAC Partner?
Priority 2
✔ Best Practice Established
What is returned when a URL is dereferenced?
Priority 3
✔ Best Practice Established
Which ID is most appropriate for URL construction?
Priority 3
✔ Best Practice Established

Labeling

What are best practices for modeling text strings?
Priority 2
✔ Best Practice Established
What is best practice for labeling external authorities?
Priority 3
✔ Best Practice Established
How do I handle strings in languages other than english?
Priority 4
✔ Best Practice Established

Modeling

How do I handle complexity in knowledge representation?
Priority 1
✔ Best Practice Established
How do I model lists of entities or multiple values?
Priority 2
✔ Best Practice Established
How should I model parts of Actor names?
Priority 2
✔ Best Practice Established

Reconciliation

How do I reconcile objects to authorities?
Priority 2
✔ Best Practice Established
Which entity should I link to in an authority file?
Priority 2
✔ Best Practice Established

Triplestores, RDF, and Inferencing

Which namespace should I use for the CIDOC CRM as LOD?
Priority 1
✔ Best Practice Established
How do I create an RDF representation of an entity?
Priority 3
✔ Best Practice Established
Where should AAC-created vocabularies be hosted?
Priority 3
✔ Best Practice Established
What serialization of RDF should I publish?
Priority 4
✔ Best Practice Established