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

add license URL to EML #282

Closed
mbjones opened this issue Jan 16, 2018 · 3 comments
Closed

add license URL to EML #282

mbjones opened this issue Jan 16, 2018 · 3 comments
Assignees
Labels
Milestone

Comments

@mbjones
Copy link
Contributor

@mbjones mbjones commented Jan 16, 2018

EML currently supports a textual description of usage rights, but lacks a clear, machine-readable declaration of the license for a data set. Consider adding an optional field for licenseURL or an SPDX license key that makes it simple for end users to be explicit about which license they follow. See discussion in codemeta/codemeta#67 .

@mbjones mbjones added this to the EML2.2.0 milestone Jan 16, 2018
@mbjones mbjones self-assigned this Jan 16, 2018
@mbjones mbjones added backlog enhancement and removed backlog labels Jan 16, 2018
@mbjones

This comment has been minimized.

Copy link
Contributor Author

@mbjones mbjones commented Feb 24, 2018

Added a new licensed element and LicenseType. See SHA 491b715. And here's an example of it in use:

<licensed>
    <licenseName>Apache License 2.0</licenseName>
    <url>https://spdx.org/licenses/Apache-2.0.html</url>
    <identifier>Apache-2.0</identifier>
</licensed>

Note that the element is named licensed because the element name license was already in use in eml-software for the text of a software license. I decided to leave the software elements in place for backwards compatibility.

@mbjones mbjones added in progress needs-review and removed next labels Feb 24, 2018
@mbjones

This comment has been minimized.

Copy link
Contributor Author

@mbjones mbjones commented Feb 27, 2018

@cjones @jgoldstein @gothub @cboettig Please review for compatibility with the licensing needs for Arctic Data Center and with the CodeMeta licensing approach. Thanks.

@csjx

This comment has been minimized.

Copy link
Member

@csjx csjx commented Feb 27, 2018

👍 This looks good to me. I reviewed the Creative Commons embedding guide to see if we are in alignment. Using RDFa it seems like they express the same information that we do between both the usageRights element and this licensed element. They emphasize i18n of license descriptions, but that seems more to do with usageRights for EML. They also explicitly point to a license image, but I'm not too concerned about that. Ship it ™️ .

@mbjones mbjones closed this Apr 19, 2018
@mbjones mbjones removed the needs-review label Apr 19, 2018
@mbjones mbjones added hacktoberfest and removed hacktoberfest labels Jun 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.