https://wiki.creativecommons.org/index.php?action=history&feed=atom&title=File%3AProposal_3.pngFile:Proposal 3.png - Revision history2026-04-23T02:49:16ZRevision history for this page on the wikiMediaWiki 1.30.0https://wiki.creativecommons.org/index.php?title=File:Proposal_3.png&diff=58519&oldid=prevJonathan Palecek: 1. User requests a webpage (either one)
2. The respective server responds to the user's request with the expected files, except for...
3. The license badge is (usually) served directly by CC. This allows us to build estimated adoption of the different...2012-08-09T20:55:08Z<p>1. User requests a webpage (either one) 2. The respective server responds to the user's request with the expected files, except for... 3. The license badge is (usually) served directly by CC. This allows us to build estimated adoption of the different...</p>
<p><b>New page</b></p><div>1. User requests a webpage (either one)<br />
2. The respective server responds to the user's request with the expected files, except for...<br />
3. The license badge is (usually) served directly by CC. This allows us to build estimated adoption of the different licenses (and of which versions)<br />
4. On request of a license badge, a CC server could then read the metadata from the corresponding webpage, and use that to maintain a robust graph of re-use information, using metadata.<br />
<br />
Note that steps one through three are how things ''already are''. Some of our existing infrastructure could be adapted to provide step four, making this proposal fairly easy to implement.</div>Jonathan Palecek