Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

license metadata for JATS ignored #8040

Closed
castedo opened this issue Apr 26, 2022 · 3 comments
Closed

license metadata for JATS ignored #8040

castedo opened this issue Apr 26, 2022 · 3 comments
Labels

Comments

@castedo
Copy link
Contributor

castedo commented Apr 26, 2022

According to https://pandoc.org/jats.html "It is recommended to use the license field ..." instead of the copyright field (key value) for metadata values for JATS. Either the documentation needs to be updated or there is the following bug of ignoring the license field (key value):

STEPS:
With with-copyright.md and with-license.md

diff with-license.md with-copyright.md 
2c2
< license:
---
> copyright:

pandoc with-license.md -s -t jats -o with-license.xml
pandoc with-copyright.md -s -t jats -o with-copyright.xml

diff with-license.xml with-copyright.xml 
15a16,21
> <permissions>
> <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
> <license-p>This document is distributed under a Creative Commons
> Attribution 4.0 International license.</license-p>
> </license>
> </permissions>

RESULT:
with-license.xml is missing a <permissions> element completely

EXPECTED:
For with-license.xml and with-copyright.xml to be the same, as suggested by the documentation.

Pandoc version?
2.18

@castedo castedo added the bug label Apr 26, 2022
@castedo
Copy link
Contributor Author

castedo commented Apr 26, 2022

I suspect this is for @tarleb. You probably have a preference on whether the doc vs the code gets updated.

@castedo
Copy link
Contributor Author

castedo commented Apr 26, 2022

I see now that using only the license by itself without any copyright key results in this problem.
I can use license key, but I have to also add some values under the copyright key too.

@tarleb tarleb closed this as completed in 3f354ce Apr 26, 2022
@tarleb
Copy link
Collaborator

tarleb commented Apr 26, 2022

Thanks. The <permissions> element is now always included. That should fix the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants