![[logo] US EPA](http://www.epa.gov/epafiles/images/logo_epaseal.gif){kind=logo}
Questions and Answers: New XML File Format
ECMPS Additional Information
New FAQs appear at the beginning of each section.
Q: In which record/entity are SO2 mass emissions (RT310) reported? I could not find SO2R in the test files, and could not find reference to RT310 in the schema description.
A: The SO2 mass emissions rate in lb/hr will be reported for each hour of operation in the "Derived Hourly Value" complex element. This applies to any unit, stack, or pipe that must report this value, regardless of the methodology used to determine it (CEM, Formula F-23, or Appendix D). The parameter code in this element should be SO2, not SO2R.
Q: Can you explain when HI should be reported in the OverallParameterValueData record vs. the DerivedHourlyData record?
A: The OverallParameterValueData element has been abolished. The heat input rate in mmBtu/hr will be reported for each hour of operation in the "Derived Hourly Value" complex element. This applies to any unit, stack, or pipe that must report this value, regardless of the methodology used to determine it.
Q: In the monitoring plan schema, RT510 has been split into 3 records: one for component, one for monitoring system and the MonitoringSystemComponentData record. Your intent seems to be to correctly model the many-to-many relationship between component and monitoring system, so I was surprised to see that a 1-to-many relationship from MonitoringSystemData to MonitoringSystemComponentData seems to be missing. The foreign key MonitoringSystemID is present in the MonitoringSystemComponentData record, but the relationship is not explicitly defined.
A: The many-to-many relationship is correctly modeled in the database. However, it has not been done in the XML schema because it would require that the MonitoringSystemComponentData be repeated as a child element of both the ComponentData and the MonitoringSystemData. Instead, there will be logic on the data loading during file import to check that each System ID in the MonitoringSystemComponentData exists in a MonitoringSystemData element.
Q: What is the EPA's progress on the XML schema development?
A: EPA has made substantial progress on XML schema specification development. Instead of waiting to release a complete XML schema, EPA is releasing the draft schema for each category of data, i.e., monitoring plan, QA and certification test data, emissions, when they are ready. You can access and download the ECMPS XML schemas .
Q: The description/name of the CalibrationInjectionData element seems to indicate that it could be used to supply data other than 7 day calibration error test data, for example, all daily calibration error tests. Is this by design, or should/could the name indicate that this is for 7 day calibration error test data only?
A: CalibrationInjectionData does contain data related to the 7 day calibration test, however, using a normal database naming convention, the database table, and consequently, the XML data element, is named based on what it contains. Since the table contains calibration data, it is named that way. However, as noted, the calibration data makes up the 7 day calibration test. The results for that 7 day calibration test, along with the results for all other tests, has its results stored in the TestSummaryData element. The Draft XML documents identify the equivalent record types. These should be a good guide for determining what data should be included a particular data element.
Q: How do I test the XML schema files?
A: The XML schema itself is useful for determining how files which are currently produced in the EDR format can be produced in an XML format. In other words, the current process which produces an EDR must be modified to produce an XML file, and the XML schema is a guide for how the file should be organized. The test files can be used as examples of how to produce an XML file which will conform to the XML schema.
In order to check whether an XML file conforms to a particular XML schema, you can use an XML editor that provides schema validation. If you participate in Beta testing, you can use the Client Tool to validate your XML files. For more information about participating in Beta testing, contact Laurel DeSantis at desantis.laurel@epa.gov.
Q: When will EPA issue the final XML schema?
A: EPA understands the need for a stable XML schema, and intends to issue a "final" XML schema prior to full implementation of the ECMPS process in 2008. Although EPA has released DRAFT schemas prior to the start of the Beta test period, it is anticipated that there will be changes based on the ongoing review of the schema by stakeholders and the testing of the client tool by stakeholders. Consequently, EPA anticipates making changes to the schema during and after the Beta test period. A rigorous testing of the schema during the Beta test period is vital to ensuring that the ECMPS process can be implemented with a stable XML schema. However, even after a stable version of the schema has been released, EPA reserves the right to make modifications to the schema in the future when necessary. (For example, when new program data are required to be reported, EPA may need to make changes to the schema.). EPA is committed to making "routine" schema modifications effective at appropriate boundaries and to release such modifications well in advance of implementation. However, in certain circumstances EPA may be forced to make schema modifications outside this schedule in order to accommodate new units or units that make changes which cannot be supported by the current XML structure. EPA believes that these unplanned modifications can be incorporated without requiring all sources to reprogram outside the "routine" update schedule.
Q: To whom should comments or questions about the XML schemas be addressed?
A: All comments and questions on the DRAFT XML schema are welcome and should be addressed to either Matt Boze at boze.matthew@epa.gov or Laurel DeSantis at desantis.laurel@epa.gov.