Closed Data Examples

This page describe few examples of closed data which are not already collected in Use_Cases .

Contributed By : Eric Stephan, Sumit Purohit

Candidate Closed Data Requirements extracted from current github Use Cases

R-DataUnavailabilityReference

For explaining open data in proper context, open data should refer to other known data that is not open (e.g. available or inaccessible).

Motivation: (use cases): 1,6,8,10,14,18,24

R-DataMissingIncomplete

Open data should indicate if it is published in a partially missing or incomplete form.

Motivation: (use cases): 1,9,10,18,24

R-DataLifecyclePrivacy

Preliminary data in a data lifecycle should not infringe upon individual’s right to intellectual property

Motivation: (use cases): 1,14,24

R-SensitiveSecurity

Data should not infringe upon an organization’s (local government, national government, business) right to privacy.

Motivation: (use cases): 1,13,17,24

1. Behind The Firewall Data

Any data generated in an organization that blocks that data using Firewall or other Access control system is a closed data for rest of the world. Generated data may have links to other "open" data hosted outside organization's Local Area Network(LAN) and it may be represented using open standard but that data can not be considered "Open Data".

2. Proprietary data by Policy

Data can be made closed because of policies of data publisher and data provider. Business sensitive data which is not made accessible to rest of the world is a closed data. Data controlled by local government law, policies are also example of closed data i.e. National Security data, law enforcement, health care etc. This is related to: DWBP Retrato da Violência (Violence Map) Use Case, Dutch basic registers Use Case

3. Lifecycle state of data

State of data after its generation but before it is published as open data should be considered as "Closed". After data generation it may remain in closed state for a indefinite period of time while the data is validated, analyzed, and insights and discoveries are published. It may also remain closed because data publisher prefers to maximize their advantage gained by availability of data before they publish it to public. Currently this is a common practice in scientific research.

4. Non HTTP protocol based data

Historically data have been exposed using for example various non-HTTP IETF protocol based end points, including but not limited to FTP, SFTP, SCP, Rsync. While their protocols are considered "open" their inter-operability with HTTP based web protocol is currently a limiting factor. From an Open Data perspective, data only available using these these non-HTTP protocols and should be considered as closed data. Additionally, data accessibile by private or application specific proprietary access protocol end points are also deemed as closed data. See DWBP Wind Characterization Scientific Study Use Case, DWBP Publication of Data via APIs Use Case