Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision Next revisionBoth sides next revision | ||
project:legal:openprivacypolicy [2013/09/11 23:48] – created loleg | project:legal:openprivacypolicy [2013/09/30 10:03] – loleg | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | This is a [[event: | + | ====== Open Privacy Legislation ====== |
- | ====== Open Privacy Policy ====== | + | The web holds enormous potential to make legislation openly available as a public resource. Not just so you can read pieces of legislation online, but also to analyse, annotate, combine and reference using new tools. The Declaration of Parliamentary Openness was released in 2012 (http:// |
- | When reading online privacy policies, it is difficult to know the legal jurisdiction | + | We rated countries on a 1-4 scale based on the following criteria; |
- | Knowing which countries and companies have been approved for international | + | We mapped this data: **[[http:// |
- | - Create data schema for international privacy law | + | [[http:// |
- | - Input data (e.g. existing policies) | + | |
- | - Visualise data transfer agreements | + | |
- | There is already | + | This project started as a [[event:2013-09|LegalHack@OKCon 2013]] challenge. |
- | Previous work visualising data protection issues: [[http:// | + | === 18 Stars of Open Legislation? |
- | ====== Project ===== | + | John Sheridan also came up with a set of additional criteria, a little like Tim Berners-Lee' |
- | (screenshots or sketches up here) | + | Basic: |
- | Brief description goes here. Add sections below if you need more room. | + | * there is a URI for each legislative act |
+ | * the URI resolves on the web to open legislation | ||
- | Include links to your demo and/or source code. | + | Standard: |
- | ===== Data ===== | + | * the URI Set is persistent with guarantees about availability |
+ | * Occam' | ||
- | * List and link your actual and ideal data sources. | + | Advanced: |
- | ===== Team ===== | + | * URI set contains abstract identifiers and document identifiers |
+ | * URI set supports multiple manifestations (XML, PDF) | ||
+ | * URI resolution supports content negotiation (e.g. browser can request content as plain text rather | ||
+ | than html) | ||
+ | * traditional citation scheme can be mapped to new style URIs with no additional information | ||
+ | * the URIs are human readable / reader friendly | ||
+ | * the URIs are hackable | ||
+ | * there are batch and list views available as well as identifiers for documents | ||
+ | * URIs support provision level addressing | ||
+ | * URIs support point in time addressing | ||
+ | * URIs support jurisdiction variations | ||
+ | * URIs support known future states (prospective versions) | ||
+ | * URIs support possible future states (proposed versions) | ||
+ | * URIs support a variety of aliases and searches to aid use | ||
+ | * URIs are formally described with a IETF URI Template specification | ||
- | * List your [[user: | + | ===== Data ===== |
- | ===== Links ===== | + | * [[https:// |
+ | |||
+ | ===== Team ===== | ||
- | * Relevant documentation ... | + | * Reuben Binns (@rdbinns) |
- | * Blog or forum posts ... | + | |
- | * Tools you used ... | + | |
| | ||
- | {{tag> | + | {{tag> |