Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
| project:legal:openprivacypolicy [2013/09/19 11:23] – [Open Privacy Policy] rbinns | project:legal:openprivacypolicy [2013/09/30 10:04] – 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:// |
| - | The web holds enormous potential to make legislation | + | Taking data protection and privacy |
| - | The Declaration of Parliamentary Openness was released in 2012 (http://www.openingparliament.org/declaration ). It lays out a set of best practices for national parliaments to make their information open. Taking data protection and privacy legislation as a case study, we assessed a range of government websites and rated them according to a few of the criteria from the Declaration. | + | We mapped this data: **[[http://cdb.io/19dvTYx|live demo]]** |
| - | === Ratings === | + | [[http:// |
| - | We rated countries on a 1-4 scale based on the following criteria; is there a URI for the original act (1 point), the most current version of the act (1), is there a permissive license (1), and is the URI ' | + | This project started as a [[event: |
| - | + | ||
| - | We mapped this data; | + | |
| - | http://cdb.io/19dvTYx | + | |
| === 18 Stars of Open Legislation? | === 18 Stars of Open Legislation? | ||
| Line 20: | Line 17: | ||
| Basic: | Basic: | ||
| - | * there is a URI for each legislative act | + | |
| - | + | * the URI resolves on the web to open legislation | |
| - | * the URI resolves on the web to open legislation | + | |
| Standard: | Standard: | ||
| - | * the URI Set is persistent with guarantees about availability | + | |
| - | + | * Occam' | |
| - | * Occam' | + | |
| Advanced: | Advanced: | ||
| - | * URI set contains abstract identifiers and document identifiers | + | |
| - | + | * URI set supports multiple manifestations (XML, PDF) | |
| - | * URI set supports multiple manifestations (XML, PDF) | + | * URI resolution supports content negotiation (e.g. browser can request content as plain text rather |
| - | + | ||
| - | * URI resolution supports content negotiation (e.g. browser can request content as plain text rather | + | |
| than html) | 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 | ||
| - | * 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 | ||
| ===== Data ===== | ===== Data ===== | ||
| - | * List and link your actual and ideal data sources. | + | * [[https:// |
| ===== Team ===== | ===== Team ===== | ||
| - | * Reuben Binns | + | * Reuben Binns (@rdbinns) |
| - | * List your [[user: | + | |
| - | + | ||
| - | ===== Links ===== | + | |
| - | + | ||
| - | * Relevant documentation ... | + | |
| - | * Blog or forum posts ... | + | |
| - | * Tools you used ... | + | |
| | | ||
| - | {{tag> | + | {{tag> |