-
Notifications
You must be signed in to change notification settings - Fork 12
Open
Description
If we want to specify for example a description in two or more languages, how should the .json file be formatted?
We need an acceptable way to do so in different infrastructures, in a way that can be interoperable.
A few options/ideas below:
First idea from SWH team:
{
"@context": "https://doi.org/10.5063/schema/codemeta-2.0",
"@type" : "SoftwareSourceCode",
"description": [
{"@value": "Functionellement, SOFA est...", "@language": "fr"},
{"@value": "Functionally, SOFA is...", "@language": "en"},
{"@value": "Scientifiquement, SOFA est...", "@language": "fr"},
{"@value": "Scientifically, SOFA is...", "@language": "en"}
],
"https://example.org/FunctionalDescription": [
{"@value": "Functionellement, SOFA est...", "@language": "fr"},
{"@value": "Functionally, SOFA is...", "@language": "en"}
],
"https://example.org/scientificDescription": [
{"@value": "Scientifiquement, SOFA est...", "@language": "fr"},
{"@value": "Scientifically, SOFA is...", "@language": "en"}
],
}Are there any other infrastructure that are using different languages in codemeta.json files?
Feel free to suggest other options.
Metadata
Metadata
Assignees
Labels
No labels