CC Technology Summit 3 Update
Upcoming SlideShare
Loading in...5

CC Technology Summit 3 Update



An update on Creative Commons' work on CC Network and RDFa driven applications, presented at the 3rd CC Technology Summit.

An update on Creative Commons' work on CC Network and RDFa driven applications, presented at the 3rd CC Technology Summit.



Total Views
Views on SlideShare
Embed Views



2 Embeds 3 2 1



Upload Details

Uploaded via as OpenOffice

Usage Rights

CC Attribution License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

CC Technology Summit 3 Update CC Technology Summit 3 Update Presentation Transcript

  • share, reuse, and remix— legally
  • Distributed & Decentralized Work Registrations
  • or
  • A Mid-Year Update in 3 Parts
  • 1
  • RDFa Update
    • Adoption continues to grow rapidly
    • Google, Yahoo indexing
    • Publishers:
      • UK Office of Information publishing
      • MySpace
      • SlideShare
      • Flickr
  • Google
    • Recently announced support for RDFa in “Rich Snippets”
    • They're exploring ways to make this easier for “webmasters”
  • Yahoo
    • Supports RDFa in many properties
    • Search Monkey lets you build “info bars”
    • BOSS lets you query for presence of metadata
  • 2
  • CC Network
    • Launched October 2008
    • A place creators to collect work references
    • A platform for digital copyright registry exploration
    • Built on ccREL
    • Free Software: AGPL 3, available from
  • CC Network
    • Growth
    • Standardization
    • Development
  • Growth
  • Standardization
    • Goal: make it easy to integrate with our tools
    • Solution: use RDFa to bind deeds + Network
    • We'll never be the only registry
    • Needed to document our practices
    • Did a thorough review of what we developed
    • Sent to OSCRI as RFC in May
  • Goals of the Specification
    • Consistency
      • Can a client follow one path and always arrive at an answer?
    • Simplicity
      • When choosing between Registries and Consumers, favor simplicity for Consumers
    • Documentation
      • How do we implement and test our work?
      • What do other registries do to work with the deeds?
  • Describing Ownership User Work
  • Describing Ownership
    • Three entities involved
      • Work
      • User
      • Registration
    • Two ways to work:
      • Users own Works directly
      • Users own Registrations, which contain Works
  • Ownership Model User Work Registration
  • Why Two Paths?
    • Works are identified by URI
    • Users may Register “patterns”
    • Registrations may contain multiple Works
      • Multiple versions
      • Multiple portions
    • Registrations provide a “container”
    • Supported direct ownership for simplicity
  • Single Ownership Model
    • Registries must publish the “Registration” metadata
    • Simplifies verification model for clients
    • Provides clear direction for adding features
      • You may want to publish hashes, fingerprints, keys etc
      • Registration is clearly the place for most of those
  • Lookup Service
    • Previously only used to link to the Registration
    • Envisioned as a complement to Regsistration
    • Now part of the core specification
    • Used as part of the Client verification process
    • Richer results
  • Lookup Service: Results
    • Re-use approach for describing registrations
    • Registries can just redirect to the Registration
    • Use HTTP status to indicate high level result
      • Success (200 or 302)
      • Multiple matches (300)
      • Failure (404)
  • Resolution
    • A Consumer needs to establish a Graph for Verification
    • Previously:
      • Retrieve the User document (has_owner)
      • Extract any RDFa
      • Follow any rdf:see_also or cc:owner_of
      • Extract any RDFa
      • Repeat up to some ill-defined limit
    • Previously favored simplicity for Registry
  • Resolution
    • New approach favors Consumers
    • Just use the lookup service
    • Returned document guaranteed to contain the needed graph
  • Specification Status
    • Up for comment from OSCRI
    • Looking for feedback from people here today
    • CC Network / CC deeds will be updated later this summer
  • CC Network Development
    • Working on updating to support revised spec
    • Developing support for group/org accounts
    • Exploring citation service
    • Exploring use a seed for better CC Search
  • 3
  • Science Commons MTA
    • An MTA describes how biological materials can be used by researchers, collaborators
    • More complex than our copyright licenses
      • Parameters for “engaging” the agreement
      • The basic document may describe a class of restriction, need additional details to understand it
      • May be layered with an “implementing letter”
  • Current MTA Developments
    • First iteration developed in 2007
      • Used the URL query string to carry additional details
    • Working on deploying 2.0 now
      • MTA work informed by our Attribution and CC Network tools
      • Changing our model for including “parameters”
  • Why Change?
    • Current approach is only useful to CC/SC
    • Exposing all the information enables reuse
    • We can build common tools across domains
  • New Tooling
    • The deeds currently use a custom server-side proxy
    • Return JSON encoded nested arrays
    • Using WebBackplane's Ubiquity project to clean up the code
      • Possible to use without server side proxy
      • Write lookups as SPARQL instead of array access
      • Easily translate from our spec to code
      • More easily test our code
  • jSPARQL = { select: [ "offer", "material", "disease", "offer_permits"], where: [ { pattern: [ "?offer", "", "" ] }, { pattern: [ "?offer", "", document.URL ] }, ... }
  • Conclusion
    • CC Network was a new way to develop for us
      • Ignore the database, drive things with metadata
    • Our experience there is informing other work
    • MTA, CC Network will both help us improve our core “business” – the licenses
    • Continue to see evidence that RDFa was a smart bet
  • Nathan R. Yergler Chief Technology Officer Creative Commons [email_address] @nyergler {twitter |}