Sunlight Foundation

New York City, Technical Standards Manual, City Policies, 2012

Open By Default. All public data sets must be considered open unless they contain information designated as sensitive, private, or confidential as defined by the Citywide Data Classification Policy or information that is exempt pursuant to the Public Officers Law, or any other provision of a federal or state law, rule or regulation or local law. The Agency submitting the data set is required to review its status and maintain currency with public disclosure requirements.

http://cityofnewyork.github.io/opendatatsm/citypolicies.html

South Bend, Open Data Executive Order, 2013

Public Data or Information means any data or information generated or received by the City of South Bend (the City) as defined by the Indiana Access to Public Records Act (APRA) at Ind. Code 5-14-3-2(n) which is fully disclosable under APRA or which the City has no discretion to refrain from disclosing under APRA at Ind. Code 5-14-3-4(b).

http://www.ci.south-bend.in.us/sites/default/files/files/Mayor_2013-Open%20Portal%20Exec%20Order.pdf

• Sunlight's "Whereas, Open Data" Roundup

U.S. Federal, Supplemental Guidance on the Implementation of M-13-13, 2013

Create and Maintain an Enterprise Data Inventory. Purpose: To develop a clear and comprehensive understanding of what data assets they possess, Federal Agencies are required to create an Enterprise Data Inventory (Inventory) that accounts for all data assets created or collected by the agency. This includes, but is not limited to, data assets used in the agency’s information systems. The Inventory must be enterprise-wide, accounting for data assets across programs and bureaus, and must use the required common core metadata available on Project Open Data. After creating the Inventory, agencies should continually improve the usefulness of the Inventory by expanding, enriching, and opening the Inventory (concepts described in the framework below)…

http://project-open-data.github.io/implementation-guide/

• Department of Transportation Enterprise Data Inventory Case Study

• United States: Enterprise Data Inventories

• United Kingdom: Department for Communities and Local Government's Data Inventory

• Canada: Data Inventory Project

• International Inventory Examples

• U.S. Inventory Examples

• Sunlight's Audits and Indexes blog coverage

New York: Executive Order 95

Prioritization of publication of data [is] based on the extent to which the data can be used to increase the covered State entity’s accountability and responsiveness, improve public knowledge of the entity and its operations, further the mission of the entity, create economic opportunity, or respond to a need or demand identified after public consultation

Each covered State entity shall create schedules and prioritize data publication in accordance with guidelines set forth in the Open Data Handbook.

http://nys-its.github.io/open-data-handbook/ExecutiveOrder95.html

• Montgomery County: Open Data Implementation Plan, Appendix B – Dataset Scoring Methodology and Outreach

• New York: Open Data Handbook Guidelines Release Prioritization

• Civic Commons' "Open Data Priorities"

• Sunlight's "The chicken or the egg? Deciding which data to release first"

United States: M-13-13 — Memorandum for the Heads of Executive Departments and Agencies (pending edits)

The Federal government does not take copyright in works prepared by its employees as part of their official duties. In instances where government data may have been contributed by a nongovernmental individual or entity and does not fall squarely within the public domain, agencies must apply open licenses, in consultation with the best practices found in Project Open Data, to information as it is collected or created so that if data are made public there are no restrictions on copying, publishing, distributing, transmitting, adapting, or otherwise using the information for non-commercial or for commercial purposes. [In some circumstances, information is acquired or accessed by an agency through an independent contractor. This requires that appropriate existing clauses be utilized to meet open data objectives, for example, by requiring the contractor to apply an open license to data created or modified under the contract, while recognizing that protection of proprietary interests in data may in certain cases be necessary to encourage qualified contractors to participate in and apply innovative concepts to government programs.

https://github.com/project-open-data/project-open-data.github.io/pull/317/files

• United States: Digital Services Playbook

• Paris: OpenDataParis Procurement Provision

San Mateo County, Administrative Memo, 2013

The County’s Open Data Committee will be responsible for…developing standards to determine which data sets are appropriate for public disclosure, by balancing the benefits of Open Data with the need to protect disclosure of information that is confidential, proprietary, or protected by law.

https://data.smcgov.org/Government/San-Mateo-County-Open-Data-Policy/pebe-j2ye

• United States: National/Homeland Security and Privacy/Confidentiality Checklist and Guidance

• National Institute of Standards and Technology's Guide to Protecting the Confidentiality of Personally Identifiable Information (PII), 2010

• Sunlight's "Safeguarding sensitive information shouldn't be an all or nothing proposition"

New York City, Local Law 11 of 2012

The council hereby finds and declares that it is in the best interest of New York City that its agencies and departments make their data available online using open standards. Making city data available online using open standards will make the operation of city government more transparent effective and accountable to the public. It will streamline intra-governmental and inter-governmental communication and interoperability permit the public to assist in identifying efficient solutions for government promote innovative strategies for social progress and create economic opportunities.

‘Open standard’ means a technical standard developed and maintained by a voluntary consensus standards body that is available to the public without royalty or fee.

http://cityofnewyork.github.io/opendatatsm/LocalLaw11of2012.html

• New York City: Technical Standards Manual — Public Standards

Honolulu, Act 263, 2013

Technical requirements with the goal of making data sets available to the greatest number of users and for the greatest number of applications including whenever practicable the use of machine readable non-proprietary technical standards for web publishing.

http://www.slideshare.net/Bytemarks/bill-53-fd1

New York City, Local Law 11 of 2012

Such public data sets shall be made available without any registration requirement, license requirement or restrictions on their use provided that the department may require a third party providing to the public any public data set, or application utilizing such data set, to explicitly identify the source and version of the public data set, and a description of any modifications made to such public data set. Registration requirements, license requirements or restrictions as used in this section shall not include measures required to ensure access to public data sets, to protect the single web site housing public data sets from unlawful abuse or attempts to damage or impair use of the web site, or to analyze the types of data being used to improve service delivery.

http://cityofnewyork.github.io/opendatatsm/LocalLaw11of2012.html

• United States: FDA Terms of Service

Oakland, City Resolution 13-0057, 2013

The City of Oakland shall license any Open Data it publishes for free re-use to ensure clarity of copyright without legal responsibility or liability for publishing such data as described further below.

http://www.scribd.com/doc/171673962/Resolution-Establishing-An-Open-Data-Policy-For-The-City-Of-Oakland-For-Making-Public-Data-Available-In-Machine-Readable-Formats-Using-Open-Data-Stand

• Sunlight's "Open Government Data Best-Practices Language for Making Data 'License-Free'"

• United States: Project Open Data Open License Examples

• CC0 1.0 Universal (CC0 1.0) Public Domain Dedication

• Open Data Commons Public Domain Dedication and License (PDDL)

U.S. Food and Drug Administration Terms of Service

While not required, when using content, data, documentation, code, and related materials from openFDA in your own work, we ask that proper credit be given. An example citation is provided below:

Data provided by the U.S. Food and Drug Administration (https://open.fda.gov)

• Sunlight's "Don't attribute open data — cite it!"

New York, Open Data Handbook, 2013

The platform will support a common and fully described core metadata scheme for each hosted dataset and Application Program Interface (API) within the data catalogue. The metadata scheme would allow data publishers to classify selected contextual fields or elements within their dataset as well as adhere to common Meta attributes identified platform-wide empowering the data consumers to build automated discovery mechanisms at a granular-level. Using a common metadata taxonomy will allow Open New York to convey and increase discoverability of high-value datasets…

http://nys-its.github.io/open-data-handbook/directives.html

• DataSF's "Metadata: Existing Practices and Survey"

• United States: Common Core Metadata Schema

• Canada: Metadata Element Set

• Australia: AGLS Metadata Standard

• New York: Open Data Handbook Metadata Elements

• New York City: Technical Standards Manual.

• Seattle: Metadata Template Document.

• Albuquerque: Core Metadata Requirements

Want to be the first to include this principle in your open data policy? Read our Guidelines for inspiration and learn why this principle is important to open data.

• Sunlight's "A little math could make identifiers a whole lot better"

• Sunlight's Unique Corporate Identifier Roundup

• Sunlight's Open Civic Identifier system

New Hampshire, CHAPTER 21-R DEPARTMENT OF INFORMATION TECHNOLOGY Open Standards Section 21-R:11, 2013

Use of Open Source Software by State Agencies.

I. For all software acquisitions, each state agency, in consultation with the department of information technology, shall: (a) Consider whether proprietary or open source software offers the most cost effective software solution for the agency, based on consideration of all associated acquisition, support, maintenance, and training costs; (b) Except as provided in subparagraphs (d) and (e), acquire software products primarily on a value-for-money basis, based on consideration of the cost factors as described in subparagraph (a); (c) Provide a brief analysis of the purchase decision, including consideration of the cost factors in subparagraph (a), to the chief information officer; (d) Avoid the acquisition of products that do not comply with open standards for interoperability or data storage; and (e) Avoid the acquisition of products that are known to make unauthorized transfers of information to, or permit unauthorized control of or modification of a state agency’s computer.

II. All state procurement documents related to software acquisitions shall include language that requires adherence to this section.

http://www.gencourt.state.nh.us/rsa/html/i/21-r/21-r-11.htm

Want to be the first to include this principle in your open data policy? Read our Guidelines for inspiration and learn why this principle is important to open data.

Honolulu, Act 263, 2013

Each agency shall use reasonable efforts to make appropriate and existing electronic data sets maintained by the agency electronically available at no cost to the public through the city’s open data portal at data.honolulu.gov or its successor website designated by the city’s director of information technology.

http://www.slideshare.net/Bytemarks/bill-53-fd1

63A-3-403. Utah Transparency Advisory Board Amendment, 2013

the publication of bulk public information

http://le.utah.gov/~2013/bills/sbillenr/SB0283.pdf

• United States: API Resources for Federal Agencies

• United States: 18f API Standards

• Chicago: Chicago Digital Developer Resources

• Philadelphia: PHL API

• New York City: NYC Developer Portal API Showcase

• Civic.io's "The Promise and Pitfalls of Government APIs"

• Sunlight's "Government APIs Aren't A Backup Plan"

• Sunlight's "Government: Do You Really Need An API?"

Want to be the first to include this principle in your open data policy? Read our Guidelines for inspiration and learn why this principle is important to open data.

Honolulu, Act 263, 2013

Each agency shall update its electronic data sets in the manner prescribed by the chief information officer and as often as is necessary to preserve the integrity and usefulness of the data set

http://www.slideshare.net/Bytemarks/bill-53-fd1

63A-3-403. Utah Transparency Advisory Board Amendment, 2013

permanent, lasting, open access to public information

http://le.utah.gov/~2013/bills/sbillenr/SB0283.pdf

Philadelphia, Executive Order, 2012

As soon as practicable the Mayor and the Chief Innovation Officer (CIO) will establish an Open Data Working Group to focus on transparency accountability participation and collaboration within City government. The Working Group which will include senior level representation from program and management offices throughout the City will assist the CIO in selecting a Chief Data Officer. The Working Group will also provide a forum to develop innovative ideas for promoting open government goals including collaborations with researchers the private sector and the public and for developing resolutions to issues raised through the public feedback mechanisms of the Open Government Portal.

Within 90 days of the Effective Date of this Order the CIO with assistance from the Open Data Working Group shall hire or designate an individual to serve as Chief Data Officer (CDO). The CDO will lead the Open Data and Transparency initiatives outlined in this Order including working with City departments and agencies to establish standards for publication of data and the most effective means for making such data available. The CDO will report to the Chief Innovation Officer.

Within 120 days from the Effective Date of this Order the Mayor shall appoint a Data Governance Advisory Board. The Board shall consist of nine members including the Chief Innovation Officer and the CDO and shall be chaired by an individual designated by the Mayor. The Open Data Working Group shall solicit nominations for members of the Advisory Board and shall recommend appointments from the public private academic and nonprofit sectors. The Advisory Board shall meet regularly at such times as the Board decides and its members shall serve at the pleasure of the Mayor.

https://gist.github.com/PhillyCDO/3623582

• Sunlight's "An Open Data Ombudsman and rethinking oversight authorities"

Want to be the first to include this principle in your open data policy? Read our Guidelines for inspiration and learn why this principle is important to open data.

Oakland, City Resolution 13-0057, 2013

Include a public engagement strategy to ensure on-going feedback and collaboration with citizens and data users

FURTHER RESOLVED: Within one hundred eighty days of the effective date of this resolution, the City Administrator or his/her designee shall prepare and present to the City Council’s Finance and Management Committee for public review and comment, an informational report on the draft Regulations setting forth the technical requirements and standards for publishing Open Data sets in raw or unprocessed formats for the purpose of making Open Data available to the greatest number of users and for the greatest number of applications, as well as the guidelines and processes necessary for the effective implementation of this Open Data Policy; and be it

FURTHER RESOLVED: The City Administrator and his/her designee shall take into account such public review and comment before finalizing such Regulations for publication; and be it

and FURTHER RESOLVED: Within twelve months of the effective date of this resolution, the City Administrator or his/her designee shall publish an inventory of Open Data and a plan for disseminating it; and such plan should include any information regarding the current state that the data exists in, as well as the costs and barriers of releasing it as Open Data; such inventory and plan will be presented to the City Council’s Finance and Management Committee as an Informational Report for public review and comment;

http://www.scribd.com/doc/171673962/Resolution-Establishing-An-Open-Data-Policy-For-The-City-Of-Oakland-For-Making-Public-Data-Available-In-Machine-Readable-Formats-Using-Open-Data-Stand

Montgomery County: Bill 23-12

The Department must implement an online forum to solicit public feedback and encourage public discussion on open data policies and public data set availability on the web portal. An agency must consider any request that it receives through the online forum to include a particular public data set when making any determination as to priority for public data set inclusion on the single web portal.

http://www6.montgomerycountymd.gov/content/council/pdf/agenda/cm/2012/121126/20121126_GO2.pdf

• Montgomery County: Open Data Town Hall

• New York City: Transparency Working Group

• Philadelphia: Open Data Race

New York City Local Law 11 23-506 Agency compliance plan

a. Within eighteen months of the effective date of this chapter, the department shall submit a compliance plan to the mayor and the council and shall make such plan available to the public on the web portal. Each agency shall cooperate with the department in its preparation of such plan. The plan shall include a summary description of public data sets under the control of each agency on or after the effective date of this chapter, and shall prioritize such public data sets for inclusion on the single web portal on or before December 31, 2018 in accordance with the standards promulgated by the department pursuant to section 23-505 and shall create a timeline for their inclusion on the single web portal. If a public data set or sets cannot be made available on the single web portal on or before December 31, 2018, the plan shall state the reasons why such set or sets cannot be made available, and, to the extent practicable, the date by which the agency that owns the data believes that it will be available on the single web portal

• Montgomery County: 2014 Dataset Publishing Plan

• New York City: 2014 Updated Open Data Plan

• New York City: 2013 Open Data Plan

• New York City: Open Data Dashboard

• Philadelphia: Open Data Pipeline

South Bend, Open Data Executive Order, 2013

Annual Open Data Report. Within one year of the effective date of this Executive Order, and thereafter no later than September 1 of each year, the Open Data Management Team shall submit to the Mayor an annual open data report. Such annual report shall: (i) summarize and comment on the state of open data and dataset availability in City agencies from the previous year; (ii) provide a plan for the next year to improve online public access to public data and maintain data quality. The Open Data Management Team shall present an initial implementation plan to the Mayor within 180 days of this Executive Order.

http://www.ci.south-bend.in.us/sites/default/files/files/Mayor_2013-Open%20Portal%20Exec%20Order.pdf

• New York: Open NY One Year Report, 2014

• Oakland: Toward Collaborative Transparency, 2014

• Chicago: Open Data Annual Report, 2013

• Philadelphia: New Opportunities for Data Publishing, 2013

• New York City: Digital Leadership Roadmap, 2013

Want to be the first to include this principle in your open data policy? Read our Guidelines for inspiration and learn why this principle is important to open data.

Cook County, Open Government Plan, 2011

The Open Government Plan shall describe steps the County shall take to enhance and expand its practices to further cooperation among County Agencies, other governmental agencies, the public, and non-profit and private entities in fulfilling the goals and objectives of the County. The Plan shall include specific details about: (1) Proposed changes to internal management and administrative policies to improve collaboration; and (2) Proposals to use technology platforms to improve collaboration among employees and the public; and (3) Descriptions of and links to appropriate websites where the public can learn about existing collaboration efforts; and (4) Innovative methods, such as prizes and competitions, to obtain ideas from, and to increase collaboration with, the public, as well as those in the private sector, non-profit, and academic communities.

Within 45 days, the President shall establish a working group that focuses on transparency, accountability, public participation, and collaboration within County government. This group, with senior level representation from other County Agencies, shall serve several critical functions, including: (1) Transparency Forum. The working group shall provide a forum to share best practices on innovative ideas to promote transparency. This shall include system and process solutions for information collection, aggregation, validation, and dissemination; and (2) Participation and Collaboration Forum. The working group shall provide a forum to share best practices on innovative ideas to promote participation and collaboration, including how to experiment with new technologies, take advantage of the expertise and insight of people both inside and outside of County government, and form high-impact collaborations with researchers, the private sector, and the public; and (3) Public Input Forum. The working group shall provide a forum for developing resolutions to issues in accordance with Sec. 2-5(h) herein.

http://cookcountygov.com/ll_lib_pub_cook/cook_ordinance.aspx?WindowArgs=1458

• Regional — Open Gov Hacknight Resources

• Regional — Pacific Northwest Data Resources

• Smart Chicago Collaborative

• Video: Jake Porway explores how data can be used in the service of humanity.

Louisville, Executive Order, 2013

In acknowledgment that technology changes rapidly, in the future, the Open Data Policy should be reviewed and considered for revisions or additions that will continue to position Metro Government as a leader on issues of openness, efficiency, and technical best practices.

http://www.louisvilleky.gov/NR/rdonlyres/9E90910B-2D16-4F00-87B4-F5476BBEA792/0/opendata.pdf