Download to read offline
![Getting Started with Apache Spark: Big Data Made Simple [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/apachesparkgettingstarted-260203175547-8361bcc3-thumbnail.jpg?width=640&height=640&fit=bounds)
3 Legal Mechanisms for Sharing Data
- 1. 3 legal mechanisms forsharing data { The limits of using the law to ensure proper credit Sarah Hinchliff Pearson Senior Counsel, Creative Commons August 22, 2011
- 2. attribution ≠ credit ≠citation
- 3.
- 4. licenses & contracts require { attribution
- 5. waivers do not { require attribution
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13. EU Sui generis database rights
- 14.
- 15.
- 16.
- 17.
- 18.
- 20.
- 21.
- 22.
- 23.
- 25.
- 27.
- 28.
- 29.
- 30. 1. ©=? 2. attribution ≠ norms licenses
- 31. 1. attribution ≠ norms 2. obligations > rights contracts
- 32. 1. waiver ≠ control waivers
- 33.
- 34. Sarah Hinchliff Pearson,August 22, 2011 slide show licensed under the CC BY international 3.0 license
Editor's Notes
- #2 Sharing data = easy. But lose control, including credit. Obvious if no license, contract or waiver. But true even if any one of those legal mechanisms is used.
- #3 Define terms. Attribution = legally-imposed, remedy is lawsuit. Credit = what we want. Citation = rooted in norms of scholarly communication, purpose to support with evidence, but now proxy for credit. Important starting point.Attribution ≠ expectations for credit or citation standards. When remedy is lawsuit, recognize incongruity.
- #4 Turn to the law. 3 main legal mechanisms. When data shared, possibility it won’t be properly cited.
- #5 Licenses and contracts impose attribution
- #6 Waivers do not. Consequences to each and will address each
- #7 Licenses – grant permission under conditions like BY
- #8 Sound like contracts
- #9 Built on underlying exclusive right. To understand scope of license, must understand right. Typically © or SGDR
- #10 © - bundle of rights
- #11 Automatic when fixed
- #12 Limited in scope and duration. Most important limit is © does not extend facts. No one can © fact, but can © collection of factsScientific data not subject © But collection of data could be
- #13 Line is murky, varies by countryEven where subject to ©, it only extends to original aspects and never facts. General rule = can extract facts from © database without infringing
- #14 Not in EU. They have SGDR. License can be © or SGDR, or both
- #15 Example = CCIF applied to database, license applies to data and databases, all to extent ©. Use of data that implicates © triggers attribution.Use of data that does not implicate © - e.g. if in public domain, does not trigger attribution.
- #16 Difficult to decipher © in scientific data and databases, hard to know when license applies. Creates risks.Risk that data provider be misledRisk that data user will under or over comply
- #17 Impose burdensome reqts – data from many sources, attribution stacking
- #18 Attribution reqts = inflexible. Absurd situations, must cite 1000 diff providers in 1000 ways. Could do all this and still not satisfy norms or expectations
- #20 Variety of names
- #21 Does not require underlying right, requires formalities, offer/acceptance, click thru, terms of use. Terms often require attribution.
- #22 Downsides = confusing obligations, no standardization, each user agreement has diff reqtsPeople may avoid data source b/c can’t understand the terms
- #23 Only binds parties, unlike licenses. Contracts more limited than licenses in that respect.If someone obtains licensed data and shares it, someone who obtains data from second user still bound by license. If data had been shared by contract alone, person who obtained data from second user would not be bound by contract terms b/c not party.In this respect, contracts more limited than licenses.
- #24 Broader reach than licenses. Not tied to right, can take away rights of public.
- #25 Example = Govt of Canada terms, violation if hurt rep of govt, was removed quicklyTroublesome. Esp when rarely read or negotiated.
- #26 Waiver. Can take many forms, but places in pd.
- #27 Not enforceable in all places. CCZero – 3 levels, waiver, fall-back license, non-assertion pledge.
- #28 Means no control. Can’t require attribution.But think back to probs with licenses and contracts. (attrib stacking, inappropriate obligations imposed on given community)Avoided when waiver used and relies on norms
- #29 Waiver provides legal certainty. No need to decipher © protection or sift through confusing legalese. If silent, people have to guess and may avoid b/c of risk of liability.
- #30 Summarize, each approach has consequences.
- #31 Licenses – (1) legal uncertainty about scope, (2) reqts that can be inconsistent with norms
- #32 Contracts – (1) burdensome reqts as each institution creates its own terms, (2) exceed scope of rights with reqts that take away rights of users.
- #33 Waivers – avoid problems. But lose control.
- #34 Each approach requires loss of control. No mechanism that imposes legally-binding obligations in way that perfectly maps to citation norms or academic expectations. By trying to use law, we risk unnecessary transaction costs on data sharing and pushing potential users away from our data.
- #35 Choosing right approach requires understanding consequences. Today’s conversations good start.