Deprecate entity.orcid

[sdruskat]

I can actually see no case for an entity having an ORCID id, unless the entity hacks ORCID.
I believe that this is a bug, which should be fixed.

It could be replaced by ROR or FundRef ID, but perhaps websites are the best identifiers for orgs, and they're already possible to supply.

Doesn't need a "hotfix", as no one will use the key because there cannot be an entity ORCID.

[sdruskat]

@jspaaks I would consider removing entity.orcid for 1.3.0 as a bugfix similar to the changes in #462. And change the milestone to 1.3.0 as well.

I'm also in favour of supporting ROR instead as part of this work, as it has emerged as the community standard for identifying organizations over the last few years. See, e.g., https://ror.org/04bwf3e34 and https://ror.org/00rbjv475.

What do you think?

[jspaaks]

1. I'm OK with removing orcid from entity as a bugfix, especially because you mentioned one can't really get an ORCID account for a group, right?
2. spawned Consider adding ROR as identifier for entities #480 to facilitate the discussion regarding RORs

[jspaaks]

FWIW entity has ror now, but also still has orcid. Should we remove it before releasing 1.3.0?

citation-file-format/schema.json

Lines 346 to 349 in 8c59428

	"orcid": {
	"$ref": "#/$defs/orcid",
	"description": "The entity's orcid."
	},

[sdruskat]

Closing as resolved in #522.