Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to CC Technology Summit 3 Update
Similar to CC Technology Summit 3 Update (20)
More from Nathan Yergler
Recently uploaded
Recently uploaded (20)
CC Technology Summit 3 Update
- 1. share, reuse, and remix— legally
- 2. Distributed & Decentralized Work Registrations
- 3. or
- 4. A Mid-Year Update in 3 Parts
- 5. 1
- 9. MySpace
- 10. SlideShare
- 11. Flickr
- 13. They're exploring ways to make this easier for “webmasters”
- 15. Search Monkey lets you build “info bars”
- 16. BOSS lets you query for presence of metadata
- 17. 2
- 20. A place creators to collect work references
- 21. A platform for digital copyright registry exploration
- 22. Built on ccREL
- 23. Free Software: AGPL 3, available from code.creativecommons.org
- 26. Standardization
- 27. Development
- 28. Growth
- 30. Solution: use RDFa to bind deeds + Network
- 31. We'll never be the only registry
- 32. Needed to document our practices
- 33. Did a thorough review of what we developed
- 34. Sent to OSCRI as RFC in May
- 37. What do other registries do to work with the deeds?
- 38. Describing Ownership User Work
- 40. User
- 42. Users own Registrations, which contain Works
- 43. Ownership Model User Work Registration
- 47. Supported direct ownership for simplicity
- 49. Simplifies verification model for clients
- 51. Registration is clearly the place for most of those
- 53. Envisioned as a complement to Regsistration
- 54. Now part of the core specification
- 55. Used as part of the Client verification process
- 56. Richer results
- 58. Registries can just redirect to the Registration
- 61. Failure (404)
- 64. Extract any RDFa
- 65. Follow any rdf:see_also or cc:owner_of
- 66. Extract any RDFa
- 69. Just use the lookup service
- 70. Returned document guaranteed to contain the needed graph
- 72. Looking for feedback from people here today
- 73. CC Network / CC deeds will be updated later this summer
- 75. Developing support for group/org accounts
- 77. Exploring use a seed for better CC Search
- 78. 3
- 81. The basic document may describe a class of restriction, need additional details to understand it
- 82. May be layered with an “implementing letter”
- 84. Changing our model for including “parameters”
- 86. Exposing all the information enables reuse
- 87. We can build common tools across domains
- 90. Return JSON encoded nested arrays
- 92. Write lookups as SPARQL instead of array access
- 93. Easily translate from our spec to code
- 94. More easily test our code
- 95. jSPARQL YAHOO.cc.mta.MTA_INFO = { select: [ "offer", "material", "disease", "offer_permits"], where: [ { pattern: [ "?offer", "http://www.w3.org/1999/02/22-rdf-syntax-ns#type", "http://mta.sciencecommons.org/ns#Offer" ] }, { pattern: [ "?offer", "http://mta.sciencecommons.org/ns#agreement", document.URL ] }, ... }
- 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
- 99. Nathan R. Yergler Chief Technology Officer Creative Commons [email_address] @nyergler {twitter | identi.ca} http://wiki.creativecommons.org/Tech_Summit_3_Update