Creative Commons & “Interface Design for Legal Systems” New and Emerging Legal Infrastructures Conference (NELIC) Mike Linksvayer 2011-04-15 / Berkeley
Really Obscure Fun Licenses flickr.com/photos/dcoetzee/3566415826/  ·  CC0
Really Obvious Fun Licenses flickr.com/photos/dcoetzee/3566410256/  ·  CC0
creative commons . org non-profit organization foundation, corporate, individual supporters 100+ global affiliate institutions
sharing infrastructure respect the law, build a sustainable and scalable society  legal and technical tools enabling effective “some rights reserved” and “no rights reserved” culture, education, public sector, science…
known for tools with ‘3 forms’ licenses, “legalcode”, “lawyer-readable”  “ human-readable” “deeds”, buttons “ machine-readable” metadata
known for tools with ‘3 forms’ licenses, “legalcode”, “lawyer-readable”  “ human-readable” “deeds”, buttons “ machine-readable” metadata
 
known for tools with ‘3 forms’ licenses, “legalcode”, “lawyer-readable”  “ human-readable” “deeds”, buttons “ machine-readable” metadata
wikipedia
 
known for tools with ‘3 forms’ licenses, “legalcode”, “lawyer-readable”  “ human-readable” “deeds”, buttons “ machine-readable” metadata
<rdf:RDF xmlns=&quot;http://creativecommons.org/ns#&quot; xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;> <License rdf:about=&quot;http://creativecommons.org/licenses/ by-nc-sa /3.0/&quot;> < permits rdf:resource=&quot;http://creativecommons.org/ns# Reproduction &quot;/> < permits rdf:resource=&quot;http://creativecommons.org/ns# Distribution &quot;/> < requires rdf:resource=&quot;http://creativecommons.org/ns# Notice &quot;/> < requires rdf:resource=&quot;http://creativecommons.org/ns# Attribution &quot;/> < prohibits rdf:resource=&quot;http://creativecommons.org/ns# CommericialUse &quot;/> < permits rdf:resource=&quot;http://creativecommons.org/ns# DerivativeWorks &quot;/> < requires rdf:resource=&quot;http://creativecommons.org/ns# ShareAlike &quot;/> </License> </rdf:RDF>
<span xmlns:cc=&quot;http://creativecommons.org/ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot;> <span rel=&quot; dc:type &quot; href=&quot; http://purl.org/dc/dcmitype/Text &quot;  property=&quot; dc:title &quot; > My Book </span> by  <a  rel=&quot; cc:attributionURL &quot; property=&quot; cc:attributionName &quot; href=&quot; http://example.org/me &quot;> My Name </a>  is licensed under a  <a  rel=&quot; license &quot; href=&quot; http://creativecommons.org/licenses/by/3.0/ &quot; >Creative Commons Attribution 3.0 License</a>.  <span  rel=&quot; dc:source &quot; href=&quot; http://example.net/her_book &quot; /> Permissions beyond the scope of this license may be available at <a  rel=&quot; cc:morePermissions &quot; href=&quot; http://example.com/revenue_sharing_agreement &quot;>example.com</a>. </span>
all 3  are user interfaces for humans, and enable more such user interfaces: lawyers, informed non-lawyers, policy general public, general zeitgeist software developers, cc-aware applications
legal user interfaces  Я hard
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
endless opportunities for legal user interface design
 
 
 
tieguy.org/blog/2011/03/31/mpl-beta-2-as-faq/
 
“ cc for x” often sounds good, but not feasible for many values of x public copyright licenses a naturally fairly constrained space we work to keep space much more constrained than natural: “license proliferation” = broken commons, network effects left on table
consider, for all LUIs (assuming access, democratization as goals) make the underlying legal arrangement conceptually simple and user-friendly (for several meanings of user-friendly!) attempt simple and short legal documents provide readily-accessible explanations, eg contextual FAQs
LUIcons (2) can very small number of important legal concepts be distilled? maybe “cc like” icons will help, but don’t get stuck here encourage an informed cadre to read and understand the “legalcode”
LUIcons (3) non-English interfaces modeling key legal concepts (e.g., with RDF) can force good thinking on all of above, or be a rathole! what additional user interafaces might be enabled by a “machine-readable” interface?
LUIcons (4) all of the democratic issues around standards, e.g. free documentation royalty-free patent permission free/open source implementation open-by-rule governance
links : con vey your self to http://creativecommons.org (Creative Commons NGO) http://wiki.creativecommons.org/NELIC_LUI (these slides)

New and Emerging Legal Infrastructures Conference (NELIC): Creative Commons & Interface Design for Legal Systems

  • 1.
    Creative Commons &“Interface Design for Legal Systems” New and Emerging Legal Infrastructures Conference (NELIC) Mike Linksvayer 2011-04-15 / Berkeley
  • 2.
    Really Obscure FunLicenses flickr.com/photos/dcoetzee/3566415826/ · CC0
  • 3.
    Really Obvious FunLicenses flickr.com/photos/dcoetzee/3566410256/ · CC0
  • 4.
    creative commons .org non-profit organization foundation, corporate, individual supporters 100+ global affiliate institutions
  • 5.
    sharing infrastructure respectthe law, build a sustainable and scalable society legal and technical tools enabling effective “some rights reserved” and “no rights reserved” culture, education, public sector, science…
  • 6.
    known for toolswith ‘3 forms’ licenses, “legalcode”, “lawyer-readable” “ human-readable” “deeds”, buttons “ machine-readable” metadata
  • 7.
    known for toolswith ‘3 forms’ licenses, “legalcode”, “lawyer-readable” “ human-readable” “deeds”, buttons “ machine-readable” metadata
  • 8.
  • 9.
    known for toolswith ‘3 forms’ licenses, “legalcode”, “lawyer-readable” “ human-readable” “deeds”, buttons “ machine-readable” metadata
  • 10.
  • 11.
  • 12.
    known for toolswith ‘3 forms’ licenses, “legalcode”, “lawyer-readable” “ human-readable” “deeds”, buttons “ machine-readable” metadata
  • 13.
    <rdf:RDF xmlns=&quot;http://creativecommons.org/ns#&quot; xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot;><License rdf:about=&quot;http://creativecommons.org/licenses/ by-nc-sa /3.0/&quot;> < permits rdf:resource=&quot;http://creativecommons.org/ns# Reproduction &quot;/> < permits rdf:resource=&quot;http://creativecommons.org/ns# Distribution &quot;/> < requires rdf:resource=&quot;http://creativecommons.org/ns# Notice &quot;/> < requires rdf:resource=&quot;http://creativecommons.org/ns# Attribution &quot;/> < prohibits rdf:resource=&quot;http://creativecommons.org/ns# CommericialUse &quot;/> < permits rdf:resource=&quot;http://creativecommons.org/ns# DerivativeWorks &quot;/> < requires rdf:resource=&quot;http://creativecommons.org/ns# ShareAlike &quot;/> </License> </rdf:RDF>
  • 14.
    <span xmlns:cc=&quot;http://creativecommons.org/ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot;><span rel=&quot; dc:type &quot; href=&quot; http://purl.org/dc/dcmitype/Text &quot; property=&quot; dc:title &quot; > My Book </span> by <a rel=&quot; cc:attributionURL &quot; property=&quot; cc:attributionName &quot; href=&quot; http://example.org/me &quot;> My Name </a> is licensed under a <a rel=&quot; license &quot; href=&quot; http://creativecommons.org/licenses/by/3.0/ &quot; >Creative Commons Attribution 3.0 License</a>. <span rel=&quot; dc:source &quot; href=&quot; http://example.net/her_book &quot; /> Permissions beyond the scope of this license may be available at <a rel=&quot; cc:morePermissions &quot; href=&quot; http://example.com/revenue_sharing_agreement &quot;>example.com</a>. </span>
  • 15.
    all 3 are user interfaces for humans, and enable more such user interfaces: lawyers, informed non-lawyers, policy general public, general zeitgeist software developers, cc-aware applications
  • 16.
  • 17.
  • 18.
  • 19.
  • 20.
  • 21.
  • 22.
  • 23.
  • 24.
  • 25.
  • 26.
  • 27.
  • 28.
  • 29.
  • 30.
  • 31.
  • 32.
  • 33.
  • 34.
  • 35.
  • 36.
  • 37.
  • 38.
    endless opportunities forlegal user interface design
  • 39.
  • 40.
  • 41.
  • 42.
  • 43.
  • 44.
    “ cc forx” often sounds good, but not feasible for many values of x public copyright licenses a naturally fairly constrained space we work to keep space much more constrained than natural: “license proliferation” = broken commons, network effects left on table
  • 45.
    consider, for allLUIs (assuming access, democratization as goals) make the underlying legal arrangement conceptually simple and user-friendly (for several meanings of user-friendly!) attempt simple and short legal documents provide readily-accessible explanations, eg contextual FAQs
  • 46.
    LUIcons (2) canvery small number of important legal concepts be distilled? maybe “cc like” icons will help, but don’t get stuck here encourage an informed cadre to read and understand the “legalcode”
  • 47.
    LUIcons (3) non-Englishinterfaces modeling key legal concepts (e.g., with RDF) can force good thinking on all of above, or be a rathole! what additional user interafaces might be enabled by a “machine-readable” interface?
  • 48.
    LUIcons (4) allof the democratic issues around standards, e.g. free documentation royalty-free patent permission free/open source implementation open-by-rule governance
  • 49.
    links : convey your self to http://creativecommons.org (Creative Commons NGO) http://wiki.creativecommons.org/NELIC_LUI (these slides)