Consider optional GivenName and FamilyName for people

It is best practice (e.g. schema.org) to allow givenName and familyName in addition to name. Makes it easier to generate correct citation, as names frequently need to be formatted.

[cboettig]

Yup, this makes sense to me,

Note that since we’re essentially defining a vocabulary, not a schema, nothing actually prevents you from using these existing schema.org terms in your codemeta.json, e.g.:

{
  "title":"dataone: R Interface to the DataONE REST API",
  "identifier":"http://dx.doi.org/10.5063/F1M61H5X",
  "@context":"https://raw.githubusercontent.com/codemeta/codemeta/master/codemeta.jsonld",
  "@type":"SoftwareSourceCode",
   "agents":[
      {
         "@id":"http://orcid.org/0000-0003-0077-4738",
         "@type":"person",
         "email":"[e-mail]",
         "schema:givenName":"Matt",
         "schema:familyName": "Jones"
      }
   ]
}

Is just as good as:

{
  "title":"dataone: R Interface to the DataONE REST API",
  "identifier":"http://dx.doi.org/10.5063/F1M61H5X",
  "@context":"https://raw.githubusercontent.com/codemeta/codemeta/master/codemeta.jsonld",
  "@type":"SoftwareSourceCode",
   "agents":[
      {
         "@id":"http://orcid.org/0000-0003-0077-4738",
         "@type":"person",
         "email":"[e-mail]",
         "name":"Matt Jones",
      }
   ]
}

the only difference being that you have to use the namespace since name is explicitly in the context and so far givenName & familyName are not.

For programmatic use, I believe we ought to be defining a JSON frame (#128) for framing input jsonld into a practical & predictably structured JSON tree. We don’t have such a frame defined yet; I suppose it should just permit all three options as possible members of an agent (e.g. name, givenName and familyName?)

[cboettig]

This has been added to the proposed codemeta-v2.jsonld, which goes along with the re-alignment towards schema.org anyhow (#134). So closing this out as subsumed by #134