Open jrmerz opened 3 years ago
Looking at Bryan Jenkins, I see jobTitle represented as
"jobTitle": [
"AGRON AES-B/E/E",
"PROF-FY-B/E/E",
"DEPARTMENT CHAIR",
"Chair and Professor"
],
In the Schema.org example, there's this example:
"jobTitle": {
"@type": "DefinedTerm",
"inDefinedTermSet": "https://targetjobs.co.uk/careers-advice/job-descriptions",
"termCode": "277133-aid-workerhumanitarian-worker-job-description",
"name": "Aid worker/humanitarian worker",
"url": "https://targetjobs.co.uk/careers-advice/job-descriptions/277133-aid-workerhumanitarian-worker-job-description"
}
Perhaps our jobTitle should be changed to an array of name objects, e.g.,
"jobTitle": [
{
"@type": "Text",
"name": "AGRON AES-B/E/E"
},
{
"@type": "Text",
"name": "PROF-FY-B/E/E""
},
{
"@type": "Text",
"name": "DEPARTMENT CHAIR""
},
{
"@type": "Text",
"name": "Chair and Professor"
}
]
Re: "knowsAbout," the application of DefinedTerms to people appears to be an AE (JM) innovation, as this page doesn't appear to depict that but rather limits terms to describing a work's aboutness.
Given a VIVO Person object (https://wiki.lyrasis.org/display/VIVODOC110x/Person+Model), the transform should spit out a schema.org Person object (https://schema.org/Person). This should be isomorphic, ie run in both Node and browser JS lands.