Mass Collaboration [Policy]: What, Why, and Choices
Upcoming SlideShare
Loading in...5
×
 

Mass Collaboration [Policy]: What, Why, and Choices

on

  • 4,543 views

 

Statistics

Views

Total Views
4,543
Views on SlideShare
4,446
Embed Views
97

Actions

Likes
1
Downloads
3
Comments
0

3 Embeds 97

http://www.scoop.it 93
https://twitter.com 3
http://www.linkedin.com 1

Accessibility

Categories

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.

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

    Mass Collaboration [Policy]: What, Why, and Choices Mass Collaboration [Policy]: What, Why, and Choices Presentation Transcript

    • Mass Collaboration [Policy]:What, Why, and Choices 1620 2012 1605 Mike Linksvayer (@mlinksva) CODATA2012 / Taipei 2012-10-30 1
    • Intellectual Provenance ? 2
    • easy to get hung up on vulgar policy,eg licensingthink broadly about what, where, ends 3
    • what is a mass collaboration dataproject? x: latent / explicit y: distributed / centralized z: crowdsourced / collaborative …: ... 4
    • consider location of “science” “semantic web” freebase musicbrainz openstreetmap wikidata dbpedia zooniverse ... 5
    • what is a mass collaboration datapolicy? 6
    • restrictions & permissionstry to be Open; use terms otherprojects do; if you have to think, publicdomain for max donor, copyleft [lookagain at nearby projects] for maxrecipient, but also possibly be bold,assume facts are free... 7
    • “IP” never the ideal answerpoor substitute for other regulation... 8
    • ...privacy, security, integritypublic licenses dull instruments forthese legitimate objectiveswhen so used overly restrictive,incompatible 9
    • ...transparency, replicability,modifiabilitycopyleft!part copyright etc neutralization, partregulatorywholesome goalsbeware FUD, incompatibility 10
    • explicit+centralized+collaborative= evinces need for public licenses likenothing else 11
    • governanceof what?depends on location in each dimension 12
    • software to facilitate masscollaboration, egwikis~source controlsemantic stuff 13
    • data management 14
    • consider key ~policy choices (so far)made by a couple of aforementionedprojects 15
    • at what level should “policy” beconsidered (depends...)internationaljurisdicitoninstitutionalstandardsprojectindividual contributor 16
    • some things to desire (~ends) frommass collaboration projects (thus toconsider in “policy”)curationprovenancedata improvement, normalization...innovation/disruption/not imaginedusesorientation toward public good 17
    • at least 3 methods of promoting andprotecting commonslaw&policybuildingextralegaleach has reactionary and progressiveaspects 18
    • buildingfree knowledge & software invalidatesassumptions of, mitigates, and buildsconstituency against bad policyeach contribution to a commons is astrike against bad policy and dystopianfuture; that’s something to celebrateand proclaim! 19
    • imagine a world in which Wikipedia isnot unusual:where mass collaboration obtains...disruptive innovationsuperior “product”greater equalitygreater freedom...in all of the most crucial humanenterprises 20
    • links: convey yourself togondwanaland.com/mlog@mlinksva 21 K✳0♡