2017 ORS 276A.356¹
Open data standard

(1) The Chief Data Officer appointed under ORS 276A.353 (Chief Data Officer) shall establish an open data standard for state agencies publishing publishable data on the web portal maintained under ORS 276A.353 (Chief Data Officer). A local or tribal government may adopt the standard. The standard must include:

(a) A format that permits public notification of updates whenever possible.

(b) Requirements to update publishable data as often as is necessary to preserve the integrity and usefulness of publishable data.

(c) The availability of publishable data without registration or license requirements or restrictions on the use of publishable data. As used in this paragraph, “registration or license requirements or restrictions on the use of publishable data” does not include measures designed or required to ensure access to publishable data, to protect the web portal from abuse or attempts to damage or impair the use of the web portal, or to analyze the types of publishable data being accessed to improve service delivery.

(d) The ability to electronically search publishable data using external information technology.

(2) In establishing the open data standard, the Chief Data Officer shall consult with subject matter experts from state agencies, organizations specializing in technology and innovation, the academic community and other interested groups designated by the Chief Data Officer. Whenever feasible, the Chief Data Officer shall consult with these entities in the development of technical and open standards.

(3) The Chief Data Officer may adopt rules to implement the open data standard. [2017 c.720 §3]

1 Legislative Counsel Committee, CHAPTER 276A—Information Technology, https://­www.­oregonlegislature.­gov/­bills_laws/­ors/­ors276A.­html (2017) (last ac­cessed Mar. 30, 2018).
 
2 OregonLaws.org contains the con­tents of Volume 21 of the ORS, inserted along­side the per­tin­ent statutes. See the preface to the ORS An­no­ta­tions for more information.
 
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.