Language Competencies in Schema.org
HughP opened this issue · 2 comments
Greetings,
In the context of expressing a CV/Resume (for an academic linguist) I am looking for the best way to express in the schema.org vocabulary the languages that the individual knows. Typically on a CV (for a linguist) we will see something like the following:
Languages:
Spanish (excellent),
German (good),
Portuguese (read well, speak limited);
Russian (studied, no speaking competency);
Nahuatl (good, field research language);
K’iche’ (good, field research language);
Quechua (fair, field research language);
Maori (structure, poor reading knowledge);
Samoan (course taken).
I could describe this in the following way:
<script type="application/ld+json">
{ "@context": {
"@vocab": "http://www.schema.org/",
"@language": "en-US"},
"@graph": [
{
"@type": "person",
"name": "Hugh Paterson III",
"knowsLanguage": [
"de-DE",
"en-US",
"es",
"qu",
"pt-colb1945",
"nah",
"quc",
"mi",
"sm"
]
}
]
}
</script>
However, this method does not allow me to describe the various levels of proficiency that a person is attributed with. In the documentation it says
We do not distinguish skill levels or reading/writing/speaking/signing here.
- Also note that in many smaller languages of the world there is no formal test for proficiency. So I can not simply structure this as
hasCredential
https://schema.org/hasCredential. - I thought about looking at these as skills but, https://schema.org/skills does not extend to people.
- https://schema.org/Specialty also does not seem to extend to people.
- I also thought about using
knowsAbout
https://schema.org/knowsAbout but its documentation says: "to indicate a topic that is known about - suggesting possible expertise but not implying it. We do not distinguish skill levels here, or relate this to educational content, events, objectives or JobPosting descriptions." Discussion in schemaorg/schemaorg#1688 has some relevant issues as they occur in Journalism, but coming from the point of view of a Resume or CV this is perhaps a different sort of use case. However, in terms of search and discovery this is certainly a similar function to the journalism use case — A resume helps organizations find talent and skills for a job to be done.
Any pointers or suggestions would be appreciated.
See issue #7 for the context of the move from the main Schema.org issue tracker to this repository.