Add fields for storing curator information

[gaurav]

This is needed by Klados, and should only include the curator name and ORCID. Looking at some other ontologies, there are a number of ways in which this information is recorded:

• Adding the term editor's URL as a dc:contributor field (e.g. https://github.com/cmungall in http://purl.obolibrary.org/obo/UBERON_0000020)
• Adding ORCIDs as a dc:contributor to the ontology rather than to individual terms as documented by the Cell Ontology, which also proposed using dc:creator to record per-term creator information.
• Adding the term editor in the description as an ORCID (e.g. http://purl.obolibrary.org/obo/UBERON_0000020)
  • As far as I can tell this is linked anywhere, but UBERON includes a definition of this ORCID to provide some more information about C. Mungall.
• Adding the term editor using the IAO:0000117 "term editor" field (e.g. "Emma Griffiths" in FOODON:00002584, "Alan Ruttenberg" in IAO:0000409)
• Adding the definition source using the IAO:0000119 "definition source" (e.g. "Barry Smith, Werner Ceusters" in IAO:0000409)

I propose we add a contributors field as a list of strings to phyloreferences and map it to dc:contributor in JSON-LD. We would recommend that contributors should be recorded as a string in the format Name (orcid:1111-2222-3333-4444).

[hlapp]

@matentzn or @cmungall if either of you have any additional pointers or comments on where to look for ontology term curator attribution recommended practices for OBO, that'd be useful.

(FYI, in the OG issue documentation above, a phyloreference becomes a (defined) class in an ontology, so it's about documenting curators at the level of terms/classes.)

[matentzn]

Here is a nice issue that illustrates the chaos: information-artifact-ontology/ontology-metadata#60

If you cover all properties mentioned by this thread you are probably in a good place.

We are pushing hard (against plenty resistance) to standardise on dcterms:contributor orcid:123, but its a slow process.

dc:creator is found as well, always check the dcterms vs dc elements variants of IRIs if you want everything.

My two cents: dcterms:contributor plus orcid/ror/wikidata is the right way to go.

[gaurav]

@balhoff pointed out that Dublin Core recommends that creators and contributors are identified by URI if feasible, and suggested the following approach:

:phyloref0 dc:contributor <http://orcid.org/0000-0003-0587-0454> .
<http://orcid.org/0000-0003-0587-0454> foaf:name "Gaurav Vaidya"

This can be represented in JSON-LD in a pretty compact way by adding two additional terms to our JSON-LD context:

{
  "@context": {
    "contributors": {
      "@id": "http://purl.org/dc/terms/contributor",
      "@container": "@set"
    },
    "name": "http://xmlns.com/foaf/0.1/name"
  },

  "contributors": [{
    "@id": "http://orcid.org/0000-0003-0587-0454",
    "name": "Gaurav Vaidya"
  }, {
    "@id": "https://orcid.org/0000-0001-9107-0714",
    "name": "Hilmar Lapp"
  }]
}

A contributor without an ORCID could either be represented by a blank node with a foaf:name property (i.e. "contributors": [{ "name": "Albert Einstein" }]) or by just including their directly in the contributors list (i.e. "contributors": [ "Albert Einstein" ]).

[hlapp]

Sounds like a good plan to me, and I agree, the dcterms namespace properties should have a URI or object as value.