currently are using strings with syntax to separate a role and person name. Generalize to allow a name, identifier, affiliation, and role. Name required?
Basing on schema.org fields suggest:
name: value is a string
affiliation: an organization. In scheme.org values is a structure, but for now we can probably just go with a string
identifier: a URI that identifies the person. ORCID favored
role: relationship of person to the sample collection or curation. see draft vocab at https://github.com/isamplesorg/metadata/blob/main/notes/vocabulary/RoleVocabulary.xlsx. Schema.org implementation is convoluted. Use prov-o definition: "the function of an agent with respect to an activity, in the context of a usage, generation, invalidation, association, start, and end."
smrgeoinfo
commented
1 year ago
currently are using strings with syntax to separate a role and person name. Generalize to allow a name, identifier, affiliation, and role. Name required? Basing on schema.org fields suggest: name: value is a string affiliation: an organization. In scheme.org values is a structure, but for now we can probably just go with a string identifier: a URI that identifies the person. ORCID favored role: relationship of person to the sample collection or curation. see draft vocab at https://github.com/isamplesorg/metadata/blob/main/notes/vocabulary/RoleVocabulary.xlsx. Schema.org implementation is convoluted. Use prov-o definition: "the function of an agent with respect to an activity, in the context of a usage, generation, invalidation, association, start, and end."