| Apr 24, 2012
Cal/EPA has released the final CERS EDT Schemas (Version 1.00), which are available at: http://cers.calepa.ca.gov/TempDocs/EDT/CERS2EDT-Ver-1dot00.zip
This ZIP file includes a cover letter, change log from the RC4 release in December 2011, the Schemas, and technical documentation.
Cal/EPA considers these XML Schemas as final unless Cal/EPA or EDT clients uncover any serious errors that could not be ignored or reasonably worked around in client and/or endpoint code. If such an issue(s) were to arise, Cal/EPA would communicate the nature of the problem(s) and anticipated changes as soon as practical to CERS EDT Listserv subscribers. Cal/EPA will recommend to the Unified Program's Data Steering Committee that any future schema changes be staged annually, with the first adoption deadline being a specific date sometime in the March 2013-October 2013 timeframe, and technical implementation in CERS and local systems occurring in an 8-16 month timeframe after that, depending upon the nature and complexity of the changes.
In late May 2012 TSU will be releasing draft/testing EDT endpoints handling the following data exchanges: Facility Submittal Exports (RFSE), Facility Submittal Action Notifications (RFSAN), and a selection of "library" services for CERS resources such as the Violation Library and the Chemical Library. The draft endpoints release will be accompanied by an updated version of the EDT Services Manual (a minor revision of the Dec.2011 0.90 release is available at http://cers.calepa.ca.gov/TempDocs/EDT/EDTManual-dot91.pdf
). TSU anticipates a production release of these endpoints during July 2012. In late 2012 TSU will implement additional endpoints for Regulator Facility Submittal (RFSI; needed by local reporting portals), the various CME endpoints, and other "library" services.
If you have technical questions, review the CERS EDT web site (http://cers.calepa.ca.gov/EDT/
), and then contact Chris Allen at email@example.com
. More general/program-related questions should be directed to Dan Firth at firstname.lastname@example.org
or CERS Technical Support at email@example.com
[This message was cross-posted on the CERS Regulator User Group listserv]