Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
project:legal:openprivacypolicy [2013/09/12 00:25] – loleg | project:legal:openprivacypolicy [2013/09/30 10:04] (current) – 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 [[http:// |
- | When reading online | + | Taking data protection and privacy |
- | Knowing which countries and companies have been approved for international | + | We mapped this data: **[[http:// |
- | === Hackathon goals === | + | [[http:// |
- | | + | This project started as a [[event: |
- | - Input data (e.g. existing policies) | + | |
- | - Visualise data transfer agreements | + | |
- | There is already a proprietary, | + | === 18 Stars of Open Legislation? |
- | Previous work visualising data protection issues: [[http:// | + | John Sheridan also came up with a set of additional criteria, a little like Tim Berners-Lee's Five Stars of Linked Data, which set out some additional technical best practices for publishing legislation; |
- | ====== Project ===== | + | Basic: |
- | (screenshots or sketches up here) | + | * there is a URI for each legislative act |
+ | * the URI resolves on the web to open legislation | ||
- | Brief description goes here. Add sections below if you need more room. | + | Standard: |
- | Include links to your demo and/or source code. | + | * the URI Set is persistent with guarantees about availability |
+ | * Occam' | ||
- | ===== Data ===== | + | Advanced: |
- | * List and link your actual and ideal data sources. | + | * URI set contains abstract 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 | ||
- | ===== Team ===== | + | ===== Data ===== |
- | * Florian Ducommun, Creative Commons Switzerland | + | * [[https:// |
- | * List your [[user:home|team members]] here ... | + | |
- | ===== Links ===== | + | ===== Team ===== |
- | * Relevant documentation ... | + | * Reuben Binns (@rdbinns) |
- | * Blog or forum posts ... | + | |
- | * Tools you used ... | + | |
| | ||
- | {{tag> | + | {{tag> |