Open mtrekels opened 4 years ago
Parent | |
Label | Person |
Definition | A person (alive, dead, undead, or fictional). |
Usage | A person (alive or dead). |
Required | No |
Repeatable | Yes |
Relationships | Range: PersonRole | Class-level properties: Identifer, MeasurementOrFact, ContactDetail, Address, Reference |
Potential standards/vocabularies/ontologies to adopt | https://schema.org/Person |
Notes | This concept should map to the Schema.org Person class (https://schema.org/Person), and the prov:Person class (http://www.w3.org/ns/prov#Person) in the PROV ontology. In the latter, it is a subclass of prov:Agent, which through which it can map to the RDA recommendations on attribution (http://dx.doi.org/10.15497/RDA00029). The definition is appropriated from the Schema.org class. |
Other people are the creator
and editor
properties of the CollectionDescription class.
I think merging Class:Collector and Class:CollectionContact into a single Class:Person is a good idea and will allow for future flexibility in the implementation of the standard
The problem is that Class:Collector was intended for collections where the whole collection was from one, or a few collectors. Whereas Class:CollectionContact was more about the specifics of a living person who runs the collection. I wonder if these can be merged so cleanly.
wouldn't @mtrekels suggestion to create a property for role within the class person solve this concern? A collector or collections could be identified by role=collector, vs. a collection contact by role=contact or something or the sort.
Include property for ORCID if possible?
This class should include another property to allow you to document/acknowledge that an individual was connected to a particular PersonRole even though that person cannot at the time of creating the LtC record be identified by name. This property would/could also be used to indicate that name information might have been redacted for the purposes of the LtC record.