Closed azaroth42 closed 8 years ago
Strawprofile:
Person:
Note that the above is based on the information managed by LCNAF, such as: http://id.loc.gov/authorities/names/n79005673.html
Note that LCNAF RDF is not usable directly, as the authority identifies a Concept, not a Person.
Seems like a reasonable set of base properties, assuming they are optional (all of them? do we need a base label
property for all of these classes?).
:+1: to foaf:Person
, for sure.
Note that LCNAF RDF is not usable directly, as the authority identifies a Concept, not a Person.
:+1:
So .... rdfs:label vs foaf:name?
@azaroth42 Based on conversation with @hybox/drs-team group membership transitivity needs to be back on the table.
I'm going to ask them to generate user stories for that.
We also have a open question about the need to have context-specific names.
If an author is credited under multiple names on different objects, we may need to be able to model the distinction.
@hannahfrost we would like to follow up on this.
@hybox/drs-team suggests looking at ULAN for possible descriptive metadata.
rdfs:label and foaf:name (plus other name-y properties) are both useful. For example, a label of "Anonymous" or "Master of the Berry Apocalypse" is good, whereas those are clearly not names.
Context specific names seems very difficult, as it would mean reifying the name literals. I would push this out of scope unless there is a well established business value associated with it.
Select most useful subset of FOAF as a strawperson