Add additional container values about codemeta HOT 3 OPEN

We use the @list structure on science on schema.org as well, and have a writeup describing the uses for @list in the upcoming release that may be helpful. I think adding the container to clearly ordered fields makes a lot of sense, and would prevent complications for people that aren't familiar with the unordered nature of JSON-LD.

from codemeta.

The intent of declaring authors as an array is, as you note, that order matters, since somehow we academics have deeply ingrained that notion with respect to authorship. I'm not sure it was a good idea though. It is a principle of RDF (and of good data management elsewhere, including relational DBs right?) that data relationships should be semantically explicit, not hinted at in structural ways such as 'order'.

On a more immediately practical note, I worry about the array declaration not being as compatible with vanilla schema.org use, including prevailing practices for dealing with academic authorship order in schema.org; but maybe @mbjones, @mfenner or others would know better here.

from codemeta.

I've made an initial PR for contributor and keywords, which maps to the behavior of https://codemeta.github.io/codemeta-generator/ in including an array for all cases.

I think funding, funder, editor, and copyrightHolder are other candidates for containers, but these would be a larger change in behavior.

from codemeta.