|
Subject: [jats-list] how to best write multilingual permissions From: "Середа Владимир Владимирович vladimir.sereda@xxxxxxx" <jats-list-service@xxxxxxxxxxxxxxxxxxxxxx> Date: Fri, 30 Jan 2026 06:28:29 -0000 |
Greetings! Kind people at NISO suggested I post the question to this list, so here I am. We're going to use JATS v. 1.4 (archiving) for the purpose of keeping the metadata of published scientific articles in a standardized way. One of the main reasons for using JATS is its multilingual capabilities. It is not clear for us what is the preferred way of writing bi- and multilingual permissions. For instance, for two languages where the copyright belongs to the same author whose name should be written in a native language and in English, the permissions element(s) can be written as two repeated permissions: <permissions xml:lang="en"> \x9A <copyright-statement>Copyright \xBF 2022 Author</copyright-statement> \x9A <copyright-year>2022</copyright-year> \x9A <copyright-holder>Author</copyright-holder> \x9A <ali:free_to_read/> \x9A <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by-nc/4.0/"> \x9A \x9A <ali:license_ref>https://creativecommons.org/licenses/by-nc/4.0/</ali:license _ref> \x9A </license> </permissions> <permissions xml:lang="ru"> \x9A <copyright-statement>Copyright \xBF 2022 \xE1\xD7\xD4\xCF\xD2</copyright-statement> \x9A <copyright-year>2022</copyright-year> \x9A <copyright-holder>\xE1\xD7\xD4\xCF\xD2</copyright-holder> \x9A <ali:free_to_read/> \x9A <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by-nc/4.0/"> \x9A \x9A <ali:license_ref>https://creativecommons.org/licenses/by-nc/4.0/</ali:license _ref> \x9A </license> </permissions> It can also be specified as one permissions with the child elements in different langs: <permissions> \x9A <copyright-statement xml:lang="en">Copyright \xBF 2022 Author</copyright-statement> \x9A <copyright-statement xml:lang="ru">Copyright \xBF 2022 \xE1\xD7\xD4\xCF\xD2</copyright-statement> \x9A <copyright-year>2022</copyright-year> \x9A <copyright-holder xml:lang="en">Author</copyright-holder> \x9A <copyright-holder xml:lang="ru">\xE1\xD7\xD4\xCF\xD2</copyright-holder> \x9A <ali:free_to_read/> \x9A <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by-nc/4.0/"> \x9A \x9A <ali:license_ref>https://creativecommons.org/licenses/by-nc/4.0/</ali:license _ref> \x9A </license> </permissions> Jeff from NISO suggested that the "first example - with multiple permissions elements is a cleaner way to tag the multi-language content". I think that the second example is more succinct and conveys the message that there is actually one permission that can be written in different languages. The second example breaks the JATS4R validator, but I've been informed that "JATS4R has not addressed the newer multi-language recommendations in the JATS Standard" so it doesn't mean much in this case. I'm interested in hearing what do you think, and what would you suggest. Yours, V
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: [jats-list] Registration for JA, Debbie Lapeyre dalap | Thread | [jats-list] how to best write multi, Dorothy Hoskins doro |
| Re: [jats-list] Registration for JA, Debbie Lapeyre dalap | Date | [jats-list] how to best write multi, Dorothy Hoskins doro |
| Month |