Open fred-atherden opened 5 years ago
Including one example with inline-graphic to support creative commons icons.
<permissions>
<license-p>
<inline-graphic xlink:title="Creative Commons License" xlink:href="https://i.creativecommons.org/l/by/4.0/88x31.png" />This work is licensed under a <ext-link xlink:href="http://creativecommons.org/licenses/by/4.0/" ext-link-type="uri">Creative Commons Attribution 4.0 International License</ext-link>.
</license-p>
</permissions>
Thanks @fabiobatalha! - this was also included at the end of the license-p in the second permissions element in the example above
<permissions>
<copyright-statement xml:lang="en">© 2019 Smith et al.</copyright-statement>
<copyright-year>2019</copyright-year>
<copyright-holder xml:lang="en">Smith et al.</copyright-holder>
<license xml:lang="en" xlink:href="http://creativecommons.org/licenses/by/4.0/">
<license-p>Panel B is licensed under a <ext-link xlink:href="http://creativecommons.org/licenses/by/4.0/" ext-link-type="uri">Creative Commons Attribution 4.0 International License</ext-link> <inline-graphic xlink:title="Creative Commons License" xlink:href="https://i.creativecommons.org/l/by/4.0/88x31.png" /></license-p>
</license>
</permissions>
I've added the following to the ticket to make this more explicit:
license-p
must be able to containinline-graphic
I've updated the considerations here to account for public domain licenses where there will be no copyright holder. This means copyright-holder
, copyright-year
and copyright-statement
need to be optional, even if they will be there for most cases.
Description
We need to be able to support separate licenses for assets within the article as these (particularly figures) may reproduce material from other articles not published under CC-BY licenses.
User Stories
Author
Production staff
But what if . . . ?
Considerations [UPDATED: 03/06/2019]
XML requirements
JATS4R recommendation
Licensing information (for each license) is captured inside a
permissions
element as a child of the asset (whether that betable-wrap
,media
[for videos], orfig
- although it is most likely to be only used forfig
with eLife content). This holds the 4 following child elements:copyright-statement
copyright-year
copyright-holder
license
(which also contains alicense-p
).The
@xml:lang
attribute can be used to specify a language. An asset must be able to have more than onepermissions
element.@xlink:href
or<ali:license_ref>
can be used as a attribute/child (respectively) of<license>
to contain the URI which defines the license.Example:
or
license-p
must be able to containinline-graphic
Mock ups
This is not required, but if you have mock ups of what you would like to see please provide them here.
Proposal
This will be added by the Texture team after the feature request is discussed and agreed.