Proposed constraint: the range of an attribution field should not be a literal.

[cmungall]

Please read #60 for background

The proposal here is that the range of dcterms:contributor and dcterms:creator should be an entity, i.e. not an rdf Literal

This issue is NOT for discussing:

• whether creator should be abandoned in favor of contributor. The proposal is simple IF either of these two properties are used THEN the range should be a thing.
• other annotation properties, whether from IAO or from oio

I'd also rather not discuss any properties that should be attached to the creator entity (e.g. how to model labels on creators, or what the value of the rdf:type on a creator/contributor is)

I would also rather avoid discussing which kinds of IRIs can be used here (orcid, wikidata, ROR, ...), unless you think it's pertinent.

Let's first determine if the proposal is clear, then we can vote on it

[matentzn]

The proposal is glass clear, and I am wholly in favour. Thank you for writing this up!

[hoganwr]

The dcterms standard itself says not to use literals, or at least Dublin Core user guide says this. See here: https://www.dublincore.org/resources/userguide/publishing_metadata/#exrih1

From the document linked above: "dcterms:contributor must not be used with literal values.

You may use dcterms:contributor only with non-literal values.

ex:myMusic dcterms:contributor gnd:135066719 .

gnd:135066719 foaf:familyName "Elliott" ; foaf:givenName "Missy" ; foaf:nick "Missy E" . "