Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
License introduction page needs a serious update (including donation bug) #839
I was working on policy document and I linked to this https://creativecommons.org/licenses/ page. Upon reviewing this needs a serious update to be able to be readable for first time visitors.
For one the video cannot be resized or seen on vimeo (next to that it is very old).
Reviewing the code it seems that the license where once a nice table but that has been removed with the style update, making it less readable.
It also does not show the donation banner as caused by these js errors:
For me it could probably redirect to https://creativecommons.org/share-your-work/licensing-types-examples/licensing-examples/
However that would mean that there is no page on the technological infrastructure of the licenses anymore.
Also I believe that once played a role as the main page for the machine readable infrastructure. You might have broken some linked data links. I could also be misremembering where the master rdf file was presented as machine readable on the web though.
Found it. Creativecommons.org/licenses/ should have some content negotiation with a machine readable link to Creativecommons.org/licenses/index.rdf, which in turn delivers: https://github.com/creativecommons/cc.licenserdf/blob/master/cc/licenserdf/rdf/index.rdf
I believe that content negotiation is broken.
We need the /licenses/ page to be a one-sheet for the licenses, I think. It's Very Old Content but it's translated nicely.
Forgive me for asking but do you remember anything else about the content negotiation setup? This isn't an area I am an expert in and there isn't anything on the wiki.
I'm also not an expert. I can point you to Mark Matienzo at Stanford and Antoine Isaac at Europeana who are very versed in this.
But this is what I looked at earlier today. Have a look at the source of a deed page (CC BY 4.0 in my case). there is a link there:
Which is what you would want as well on the /licenses/ page. but you want
You can then let your code request the rdf+xml from that page and they can find the index.rdf if I'm not mistaken.
Now content negotiation has been taken steps forward since this code was set up in the mid-2000's. So you might want to have a look at how rightsstatements solve the RDF JSON-LD stores of their statements: http://rightsstatements.org/files/180117requirements_for_the_technical_infrastructure_for_standardized_international_rights_statements_v1.2.1.pdf This would be a whole project in itself.