SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
36.
Goals of the Specification <ul><li>Consistency </li><ul><li>Can a client follow one path and always arrive at an answer? </li></ul><li>Simplicity </li><ul><li>When choosing between Registries and Consumers, favor simplicity for Consumers </li></ul><li>Documentation </li><ul><li>How do we implement and test our work?
37.
What do other registries do to work with the deeds? </li></ul></ul>
44.
Why Two Paths? <ul><li>Works are identified by URI
45.
Users may Register “patterns” </li><ul><li>http://creativecommons.org/* </li></ul><li>Registrations may contain multiple Works </li><ul><li>Multiple versions
46.
Multiple portions </li></ul><li>Registrations provide a “container”
47.
Supported direct ownership for simplicity </li></ul>
48.
Single Ownership Model <ul><li>Registries must publish the “Registration” metadata
79.
Science Commons MTA <ul><li>An MTA describes how biological materials can be used by researchers, collaborators
80.
More complex than our copyright licenses </li><ul><li>Parameters for “engaging” the agreement
81.
The basic document may describe a class of restriction, need additional details to understand it
82.
May be layered with an “implementing letter” </li></ul></ul>
83.
Current MTA Developments <ul><li>First iteration developed in 2007 </li><ul><li>Used the URL query string to carry additional details </li></ul><li>Working on deploying 2.0 now </li><ul><li>MTA work informed by our Attribution and CC Network tools
84.
Changing our model for including “parameters” </li></ul></ul>
85.
Why Change? <ul><li>Current approach is only useful to CC/SC
96.
Conclusion <ul><li>CC Network was a new way to develop for us </li><ul><li>Ignore the database, drive things with metadata </li></ul><li>Our experience there is informing other work
97.
MTA, CC Network will both help us improve our core “business” – the licenses
98.
Continue to see evidence that RDFa was a smart bet </li></ul>