User:CoNE Person
General[edit]
- Implementation status: The schema is implemented in RDF Schema, so for now there are just inference rules. It should be extended by owl to define more restrictions and constraints --Kurt 14:23, 4 February 2009 (UTC)
- would check again if properties such as modified-by, created-by etc. should not be modeled as separate class in future. NIMS asked for these things, and they were created without proper definition before. I think these are actual system properties (i.e. those that need to be automatically populated by the Cone service). Therefore imho these do not belong to the core Person RDF properties (i.e. descriptive metadata). --Natasa 09:01, 18 February 2009 (UTC)
Traugott comments[edit]
- add disambiguation metadata
- year of birth, death
- topic of research, e.g. PhD topic
- keywords
- IDs from other systems that may include a bit more information on a person
- revise metadata on person profile (make it more clear semantically)
- format of dates
- affiliation and position vs org units
- check position vs affiliation
- for disambiguation affiliation is more important
- end-date is not mandatory in position
- email - what is the email: personal, organizational email etc.
- check metadata vs. properties
- identifiers for persons should not be described as internal person identifiers (openID, etc.)
- check in general the name of the property vs. description
Historical[edit]
Following are the first functional requirements for describing a person via controlled manner.
Person[edit]
Potential metadata elements[edit]
Complete name The complete name of a person, usually a concatenation of given names and family name
- Remark Inga: I would assume that the given name can be automatically be generated from given name and first name. Therefore I wouldn't consider this as additional element --Inga 12:19, 28 December 2007 (CET)
Given name A given name of a person
Family name The family name of a person
Alternative name Any alternative name used for the person
Title The title or peerage of a person in one string
Pseudonym The pen or stage name of a person
- Remark Sabine: Can pseudonym also be covered by alternative name?
- Remark Ulla: Let's assume: yes
- Remark Inga: But in this case we should again consider a typization of alternative names --Inga 12:19, 28 December 2007 (CET)
Affiliation The institution the person was affiliated to when creating the item
- Remark Inga: The above information is only available in the context of one publication. Therefore, I would suggest to point to the affiliation, the person is currently working for. In addition, we might list all former (known) affiliations as well. --Inga 12:23, 28 December 2007 (CET)
Identifier Identifier in the Personennormdatei, provided by the Deutsche Nationalbibliothek
- Remark Sabine: IMO other identifier should be allowed as well (e.g. Identifier of Library of Congress Name Authority File)
- Remark Ulla: Can be modified if needed
- Remark Inga: Schema has to be indicated --Inga 12:19, 28 December 2007 (CET)
Email Email address of the person (e.g. will allow users to send an email to the author asking for the fulltext in case it is not available)
- Remark Sabine: I am not sure whether the email address is an important information for all persons or for registered PubMan users only. The handling of this "private data" has also be clarified.
- Remark Traugott: Problem of regularly updating the email address
- Remark Ulla: IMO updating controlled vocab. is always a challenge, not only for emails...?
- Remark Inga: I agree with Sabine, email address is of special importance for eSciDoc users only. If we don't find a reliable source for importing this information regularly (PND?), we shouldn't try to maintain this information ourself --Inga 12:19, 28 December 2007 (CET)
Homepage The location of a personal homepage (e.g. in case fulltext is available via personal homepage)
- Remark Sabine: same as for Email
Date of Birth
Place of Birth
Date of Death
Place of Death
Resources[edit]
to be defined, which external sources might be used