Skip to content

Specify the acceptable way to have multiple values in different languages #41

@moranegg

Description

@moranegg

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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions