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

Asset distribustion dct:license #19

Open
sandervd opened this issue Feb 6, 2020 · 1 comment
Open

Asset distribustion dct:license #19

sandervd opened this issue Feb 6, 2020 · 1 comment

Comments

@sandervd
Copy link

sandervd commented Feb 6, 2020

I would consider changing the range to spdx:License, and constrain instances to the spdx reference dataset (https://github.com/spdx/license-list-data/tree/master/rdfturtle)

@bertvannuffelen
Copy link
Contributor

if spdx:License is compatible with the notion of a dct:LicenseDocument it might be considered.

definition spdx:License

A License represents a copyright license. The SPDX license list website is annotated with these properties (using RDFa) to allow license data published there to be easily processed. The license list is populated in accordance with the License List fields guidelines. These guidelines are not normative and may change over time. SPDX tooling should not rely on values in the license list conforming to the current guidelines." (en)

definition dct:LicenseDocument

A legal document giving official permission to do something with a resource.

Aside from that, does the spdx project will maintain the stability of the URLs? Instead of directly referring to the legaltext of the license we refer to an item in a code list. In order to take benefit from that as a decentralized publishing, the URLs should be stable. It is worth to check that.

Finally I see that the github promotes the http resources instead of the https resources. Honestly I think we should pursue the https variant.

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

No branches or pull requests

2 participants