-
Notifications
You must be signed in to change notification settings - Fork 123
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
Guide to Open Data Licensing: next steps #145
Comments
Thank you for your feedback! Indeed the first issues you noted are broken refs, they exist in the source. The link to the instruction guide is missing, I think it should be this guide: I'll check tonight those references. |
The material listed under Australia is either old or incorrect and should Kind regards b Baden M Appleyard National Director - AusGOAL AusGOAL On Sun, Aug 21, 2016 at 6:33 PM, enyst [email protected] wrote:
|
I don't think this page has been worked on much since it was announced in 2007. Too bad the original links are broken. Can this be fixed with redirects? For anyone who wishes to find bits that may be been lost in wiki->wordpress->jekyll migrations, see http://web.archive.org/web/*/https://okfn.org/wiki/OpenDataLicensing/ @pietercolpaert https://en.wikipedia.org/wiki/Legal_advice does not mean vetted by legal experts. I feel disclaimers are overused and may not be necessary here, but care very little. |
@mlinksva thanks, I made a pass to fix things. Links seem to be working now without redirects: |
Thanks @enyst, merged. I'll leave this open for further discussion of next steps. |
I would suggest that an update of contents is among next steps. For one, the older science commons material it refers to is now the creative commons FAQ with updated info since 4.0 versions. I'm reviewing aspects like that. I have to check more things in depth. I agree with @pietercolpaert that this is a very interesting resource. But if you wish to make it into a reference to be cited by many and/or vetted and/or submitted to a journal, there's a lot more work to do on it. |
Great to see this being updated. Re location / home for this: my suggestion would be a move to https://github.com/okfn/opendatahandbook somewhere appropriate (perhaps and appendix). General point: let not the best be the enemy of the good ;-) |
Just came across this report for Europe: http://ec.europa.eu/internal_market/copyright/docs/studies/1403_study2_en.pdf - seems like a very interesting resource to link to? |
Under the law of most US states, only an attorney who is admitted to the I spend a lot of time cleaning up after do-it-yourself lawyering that goes Thanks Bruce On Oct 29, 2016 2:04 AM, "Pieter Colpaert" [email protected] wrote: Just came across this report for Europe: http://ec.europa.eu/internal_ — |
@pietercolpaert feel free to make a PR to add that link. Another possibility: RDA-CODATA Legal Interoperability Interest Group. (2016). Legal Interoperability of Research Data: Principles and Implementation Guidelines. https://zenodo.org/record/162241 |
I was impressed with the extensive explanation on data and intellectual property (IP) rights around the world at http://opendefinition.org/guide/data/. The page is an important resource to getting a global understanding of (the jungle of) data/content and IP.
However, in order for this page to be cited/linked by the many, we should be able to get rid of the disclaimer that this is not legal advise. Therefor, it would be interesting to call for legal experts in IPR to help out to validate the text for potential errors.
Furthermore, in order for this page to be seen as a scientific valuable resource, it seems interesting that, with the contributing authors, we submit this text to an open access journal.
Minor issues that might have been caused by jekyll:
<li>
elementsA short 1-page instruction guide to applying an open data license can be found on the Open Data Commons site:
→ shows an empty li element as wellThe text was updated successfully, but these errors were encountered: