Indicating multiple roles for people that have no ORCiD or record

[rebeccaringuette]

Hi everyone,
Question 1: We are trying to indicate multiple roles for a person that has no ORCiD and no metadata record associated with the person. The role names are not from a controlled vocabulary and so have no identifiers or associated URLs. If we follow the example on the dataset guidance, we get schema.org metadata without ids to link between the different role names:

{
  "@context": "https://schema.org/",
  "@type": "Dataset",
  "name": "Removal of organic carbon by natural bacterioplankton communities as a function of pCO2 from laboratory experiments between 2012 and 2016",
  ...
  "creator": [
    {
      "@type": "Role",
      "roleName": "Principal Investigator",
      "creator": {
        "@type": "Person",
        "name": "Dr Uta Passow",
        "givenName": "Uta",
        "familyName": "Passow"
      }
    },
    {
      "@type": "Role",
      "roleName": "Contact",
      "creator": { }
    },

I expect that this will cause a problem with the empty creator field and the lack of @id values to connect the differing types of roles together for the same person.
What we are considering implementing instead is the following, where the roleName is added to the original object:

"creator": [
    {
      "@type": "Role",
      "roleName": ["Principal Investigator", "Contact"]
      "creator": {
        "@type": "Person",
        "name": "Dr Uta Passow",
        "givenName": "Uta",
        "familyName": "Passow",
      }
    },

Question 2: We are also trying to indicate multiple roles for a person that has an ORCiD but no other metadata record. The role names are not from a controlled vocabulary and so have no identifiers or associated URLs. If we follow the example on the dataset guidance, we get schema.org metadata without ids to link between the different role names:

{
  "@context": "https://schema.org/",
  "@type": "Dataset",
  "name": "Removal of organic carbon by natural bacterioplankton communities as a function of pCO2 from laboratory experiments between 2012 and 2016",
  ...
 {
      "@type": "Role",
      "roleName": "Principal Investigator",
      "creator": {
        "@type": "Person",
        "name": "Dr Uta Passow",
        "givenName": "Uta",
        "familyName": "Passow",
        "identifier": {
          "@id": "https://orcid.org/0000-0003-3432-2297",
          "@type": "PropertyValue",
          "propertyID": "https://registry.identifiers.org/registry/orcid",
          "url": "https://orcid.org/0000-0003-3432-2297",
          "value": "orcid:0000-0003-3432-2297"
        },
      }
    },
    {
      "@type": "Role",
      "roleName": "Contact",
      "creator": {  }
    }
}

Again, I expect that this will cause a problem with the empty creator field and the lack of @id values to connect the differing types of roles together for the same person.
What we are considering implementing instead is one of the following:
Option 1: where the roleName is added to the original object (similar to above):

"creator": [
    {
      "@type": "Role",
      "roleName": ["Principal Investigator", "Contact"]
      "creator": {
        "@type": "Person",
        "name": "Dr Uta Passow",
        "givenName": "Uta",
        "familyName": "Passow",
        "identifier": {
          "@id": "https://orcid.org/0000-0003-3432-2297",
          "@type": "PropertyValue",
          "propertyID": "https://registry.identifiers.org/registry/orcid",
          "url": "https://orcid.org/0000-0003-3432-2297",
          "value": "orcid:0000-0003-3432-2297"
        },
      }
    },

Option 2: where the ORCiD is used as the @id value for the creator and roleName is added to the original object (similar to proposed solution for question 1)"

"creator": [
    {
      "@type": "Role",
      "roleName": ["Principal Investigator", "Contact"]
      "creator": {
        "@type": "Person",
        "@id": "https://orcid.org/0000-0003-3432-2297",
        "name": "Dr Uta Passow",
        "givenName": "Uta",
        "familyName": "Passow",
        "identifier": {
          "@id": "https://orcid.org/0000-0003-3432-2297",
          "@type": "PropertyValue",
          "propertyID": "https://registry.identifiers.org/registry/orcid",
          "url": "https://orcid.org/0000-0003-3432-2297",
          "value": "orcid:0000-0003-3432-2297"
        },
      }
    },

Option 3: where the ORCiD is used as the @id value for the creator and roleName is kept separate as in the example in the dataset.md file:

  "creator": [
    {
      "@type": "Role",
      "roleName": "Principal Investigator",
      "creator": {
        "@type": "Person",
        "@id": "https://orcid.org/0000-0003-3432-2297",
        "name": "Dr Uta Passow",
        "givenName": "Uta",
        "familyName": "Passow"
        "identifier": {
          "@id": "https://orcid.org/0000-0003-3432-2297",
          "@type": "PropertyValue",
          "propertyID": "https://registry.identifiers.org/registry/orcid",
          "url": "https://orcid.org/0000-0003-3432-2297",
          "value": "orcid:0000-0003-3432-2297"
        },
      }
    },
    {
      "@type": "Role",
      "roleName": "Contact",
      "creator": {"@id": "https://orcid.org/0000-0003-3432-2297"}
    },

I completely agree with the opinion that it is better for the role names to come from a controlled vocabulary (e.g. CRediT), but that is unfortunately not the current situation. Hopefully that is supported soon for Heliophysics.
With that said, what is the recommendation from this group? I assuming the recommendation will be the same for the same issues for people in the contributor object.
For those aware of SPASE, there are currently person records, but I consider those to be likely temporary since they are likely to not be supported in the ongoing redesign. I do not want to include links in the schema.org information that may be removed.