The NYC Open Data Policy Hack Day will follow an unconference-style format. There will be two, hour-long breakout sessions where smaller groups will focus on topics of specific interest. To get a jump-start on the day, use the links to the left to familiarize yourself with the policies, standards, and guidelines. Then, return to this page; add topics or issues you'd like to address directly to the list, or in the comments below. (We've put in a few ideas to get things started.)

To enter your own suggestion, just enter a short title for your suggestion and click on "Make a Suggestion"

Potential Group Topics

	Description	Category	Date	Suggester
Technical standards for releasing public data which may not be hosted on the NYC Open Data platform.			2456050.47013892 May 2012 23:17:00	Technickle
Improving the guidelines for prioritizing the release of public datasets.			2456050.47013892 May 2012 23:17:00	Technickle
Policy recommending the creation of a citywide open data coordinator or Chief (Open) Data Officer and associated responsibilities.			2456050.47013892 May 2012 23:17:00	Technickle
Recommending approaches to metadata management and/or standards.			2456050.47013892 May 2012 23:17:00	Technickle
Take into account the ongoing NYC.gov redesign effort as a lot of city data is exposed through websites		nyc.gov	2456051.33055563 May 2012 19:56:00	Jnatividad
The .nyc TLD - Where does it fit within Open Data?			2456053.09027785 May 2012 14:10:00	Thomas-Lowenhaupt
The role of the DNS's Data Query Log is worthy of a discussion. Open or Closed?			2456054.49166676 May 2012 23:48:00	Thomas-Lowenhaupt
How to support/address crowd-sourced data? -Do we need to set standards or best practices for how data can be collected to make it sustainable and useful			2456063.195833315 May 2012 16:42:00	Technickle
Redefine the ambiguous language around Data Principles' Data is Secure			2456064.961805617 May 2012 11:05:00	Noneck
Real-time data	how to incentivize agencies, how to put in place infrastructure (e.g. LIVE Singapore), how is this going to complicate existing challenges of open data	Future issues; future-proofing strategies	2456066.118055618 May 2012 14:50:00	Anthonymobile
Agile planning and policymaking	the NYC open data law will be obsolete long before its fully implemented. how do we create a more agile framework for evolving the law and its spirit, its implementation, amendment, etc.	Future issues; future-proofing strategies	2456066.118055618 May 2012 14:50:00	Anthonymobile
Transparent models and algorithms	Going beyond just open data, and starting to think about regulatory frameworks for exposing code and models that shape the city, embed regulations into technical/automated systems, etc.	Future issues; future-proofing strategies	2456066.118055618 May 2012 14:50:00	Anthonymobile
Nyc.gov domain for OpenData portal			2456066.519 May 2012	Technickle
Adapting Mapped in NY to include social impact ventures (both social enterprise and non-profit) specifically based on issue of interest	Same interface as Mapped in NY, just with more information on start-ups so that site visitors can filter the display based on environmental/social/economic issue of interest	Social entrepreneurship	2456066.519 May 2012	Yangbodu
Define new standards for encoding Government events and actions. Look carefully at the application of ActivityStreams in this domain.			2456066.519 May 2012	Bobwyman
For nyc TLD, AUTOMATICALLY assign entries to all nyc addresses		nyc tld	2456066.519 May 2012	Jnatividad
What intersection can be found with semantic web effort?			2456066.519 May 2012	Brendanr

Info: PLEASE DO NOT MANUALLY ADD SUGGESTIONS BELOW. USE THE MAKE A SUGGESTION BUTTON ABOVE. The suggestions below were entered before the MAKE A SUGGESTION form was created, and are only being retained for reference during the quick training session on Policy Hack Day

• Policy recommending the creation of a citywide open data coordinator or Chief (Open) Data Officer and associated responsibilities.
• Technical standards for releasing public data which may not be hosted on the NYC Open Data platform.
• Improving the guidelines for prioritizing the release of public datasets.
• Recommending approaches to metadata management and/or standards.
• Take into account the ongoing NYC.gov redesign effort as a lot of city data is exposed through websites. Per the NYC.gov Redesign RFP, Section II.B.8 Design Considerations,. "The redesign should provide real‐time feeds, Web services, and machine readable data and content. [emphasis mine]" Perhaps, it should be explicitly specified that the machine readable data be marked up using standards-compliant RDFa 1.1 Lite, which Schema.org is also supporting - supporting search engine discoverability, while at the same time, complying with W3C standards that support machine-readable applications beyond search --Jnatividad 19:56, 3 May 2012 (EDT)
• The .nyc TLD - Where does it fit within Open Data?
• The role of the DNS's Data Query Log is worthy of a discussion. Open or Closed?
• How to support/address crowd-sourced data? -Do we need to set standards or best practices for how data can be collected to make it sustainable and useful.
• Redefine the ambitious language around Data Principles' Data is Secure.
• Future issues / future-proofing strategies
  **Transparent models and algorithms - Going beyond just open data, and starting to think about regulatory frameworks for exposing code and models that shape the city, embed regulations into technical/automated systems, etc.
  • Real-time data - how to incentivize agencies, how to put in place infrastructure (e.g. LIVE Singapore), how is this going to complicate existing challenges of open data
  • Agile planning and policymaking - the NYC open data law will be obsolete long before its fully implemented. how do we create a more agile framework for evolving the law and its spirit, its implementation, amendment, etc.

Comments