enfoTech & Consulting, Inc.01/18/2008
Open Dump XML Schema
(FRS XML Schema Extension)
Schema Review Conformance Report
Developed for:
Cherokee Nation Environmental Programs
PO Box 948
Tahlequah, OK74465
Developed by:
11 Princess Road, Unit A
Lawrenceville,New Jersey 08648
Table of Contents
Document Status
Section 1. Introduction
Section 2. Open Dump 1.0 Review Methodologies, Results, and Recommendations
2.1World Wide Web Consortium (W3C) Conformance
2.1.1Methodology
2.1.2Review Results
2.1.3Recommendations
2.2XML Design Rules and Conventions Conformance
2.2.1Methodology
2.2.2Review Results
2.2.3Recommendations
2.3Core Reference Model (CRM) Shared Schema Component (SSC) Conformance
2.3.1Methodology
2.3.2Review Results
2.3.3Recommendations
2.4EDSC Data Standards Conformance
2.4.1Methodology
2.4.2Review Results
2.4.3Recommendations
Section 3. Conclusion
Appendix A: W3C Schema Validation Results
Appendix B: EN Design Rules & Conventions Validation Results
Appendix C: EDSC Standards Validation Results
Open Dump Schema Review Conformance Report01182008.docPage 1 of 21
enfoTech & Consulting, Inc.01/18/2008
Document Status
Title: Open Dump v1.0 XML Schema Review Conformance Report
Author:Doug Timms, enfoTech & Consulting, Inc.
Subject:Full evaluation of the candidate Open Dump XML schema against design guidance.
Description:This document describes the findings resulting from a comparison of the CNEP – Open Dump schema against the guidelines for schema design as recommended by the National Environmental Information Exchange Network (NEIEN).
Publisher:CNEP
Contributors:Douglas Timms (enfoTech), David Yochim (enfoTech)
Date:1/18/2008 (revision date)
Comment Period:The comment period will be set by the Technical Resources Group.
Commenting Forum:Comments are to be exchanged via contributors and reviewer’s email.
Type:Report
Source:TRG/Schema Workgroup, Schema Review Process for Schema Developers
Changes:Initial production-ready version
Coverage:It is expected that this schema will cover the reporting of open dump data to the Exchange Network Node. This will cover data from organizations (and States and Tribes) which generate open dump data of interest to the EPA.
Section 1. Introduction
The National Environmental Information Exchange Network (EN) has created a schema reviewprocess to promote consistency and quality in XML schema. Through this process, schema areevaluated for conformance to EN standards in four areas:
- Conformance with the World Wide Web Consortium (W3C)XML schema requirements and standards
- Conformance with EN Design Rules and Conventions (DRCs) and XML Architecture Agreements
- Conformance with the Core Reference Model (CRM) and Shared Schema Components (SSC)
- Conformance with applicable data standards, especially those created by the Environmental Data Standards Council (EDSC)
This Schema Review Conformance Report is prepared on behalf of the Cherokee Nation Environmental Programs to provide an analysis of the CNEP – Open Dump Exchange XML Schema Version 1.0 in order to approve/certify the schema for the Exchange Network use. This report provides information about conformance of the schema to the established criteria listed above, as well as the methodology used to determine conformance.
The Open Dump schema is expected to be the primary schema for the sharing of open dump information among Exchange Network Partners. This will cover data from organizations (and States and Tribes) which generate open dump data of interest to EPA and other interested organizations. The Open Dump schema is built on and extends the FRS schema version 2.3.
Open Dump Schema Review Conformance Report01182008.docPage 1 of 21
enfoTech & Consulting, Inc.01/18/2008
Section 2. Open Dump 1.0 ReviewMethodologies, Results, and Recommendations
As outlined in the Schema Review Process for Schema Developers guidance document, the schemareview process consisted of performing the following steps:
- Determine the initial review requirements (as outlined in the Schema Review Process forSchema Developers guidance document)
- Perform the schema review
- Check for conformance with W3C schema standards
- Review schema for conformance with EN Design Rules and Conventions
- Compare the schema with SSCs
- Review schema for conformance with data standards
- Prepare the schema conformance report
- Submit the conformance report along with the schema and supporting documents
The format of this Schema Review Report was based on previous Schema Review Conformance Reports used by the Technical Resource Group (TRG) as well as guidance outlined in the TRG’s Schema Review Process for Schema Developers.
2.1World Wide Web Consortium (W3C) Conformance
Since the schemas are written in XML format, there are two (2) levels of error checks that must be performed to determine whether the XML schema conforms to the specification defined by W3C. The first level error check verifies if an XML schema is well-formed – ensures that the schema conforms to the XML syntax. A well-formed XML schema is syntactically correct, however, it does not verify the accuracy of the schema content. The second level error check looks for missing elements, incorrect element order, and invalid occurrences of an element within the schema. The schema must pass the first level error check to proceed to the second level.
2.1.1Methodology
To validate the schema against the W3C standards, the following XML schema processors were used:
Tool Name / URL / DescriptionAltova XML Spy 2006sp2 / / Altova XMLSpy® is the industry standard XML development environment for modeling, editing, debugging, and transforming all XML technologies, then automatically generating runtime code in multiple programming languages.
IBM Schema Quality
Checker 2.2 / / XML Schema Quality Checker is a program which takes as input an XML Schema written in the W3C XML schema language and diagnoses improper uses of the schema language.
XML Spy Methodology: The root file (OD_FacilitySiteAll_v1.0.xsd) for the Open DumpXML schema wasopened in XML Spy. The root file referencesall the other XML schema files. By highlighting the project name, all schemas can be checked and determined if they are well-formed, with valid content.
IBM Schema Quality Checker 2.2: The command line version of the Schema Quality Checker was run against theroot Open Dump XML schema file (OD_FacilitySiteAll_v1.0.xsd).
2.1.2Review Results
There were no errors reported by the Altova schema validation tool. The IBM Schema Checker came back with the following two error types:
1. cvc-attribute.3: The value '.\FACID_FacilitySiteAllDetails_v2.3.xsd' of attribute 'schemaLocation' on element 'xsd:include' is not valid with respect to its type.
2. cvc-datatype-valid.1.2.1: '.\FACID_FacilitySiteAllDetails_v2.3.xsd' is not a valid 'anyURI' value.
These errors occurred on the FRS schema files that had a “.\” in front of the file name in the xsd:include schemaLocation attribute.
The schemas were well-formed and had valid content. Validation result reports are recorded in Appendix A.
2.1.3Recommendations
These errors only existed in the FRS XML schema files, and not in the newly created Open Dump XML schema files. Since the FRS schema has already been accepted, the decision was to not use the “.\” in the new Open Dump schema files but leave it in the included FRS files.
2.2XML Design Rules and Conventions Conformance
2.2.1Methodology
The XML Design Rules and Conventions (DRC) for the Environmental Information EN document, published September 2003, was created to ensure that XML schema created for use on the Exchange Network consistently implement XML schema design practices to help promote interoperability between different schema and technical communities. In order to satisfy all requirements specified in the DRC, the XML schemas were reviewed both manually and through the automated Schema Design Tool available from the Facility Registry System (FRS) Web site at The design rules and conventions were supplemented in 2006 with EN_XML_Schema_Design_Rules_v1.1e.doc.
Automated Tool checking:
The automated Schema Design Tool checks the XML schema for conformance to those design rules for which clear, concise, and consistent specifications have been established that include “Must” or “Must Not” levels of enforcement. Design rules that could not be evaluated by the Schema Design Tool require interpretation by the reviewer inspecting the schemas manually.
As each of the Open DumpVersion 1.0 schemas went through the automated Schema Design Tool checking for certain DRC rules, the tool generated a violation report. The violation report specified the schema file name, the date and time processed, and the detailed information related to each detected violation, such as the violated DRC rule identification number, the rule description, and the schema line number where the violation was detected. Appendix B specifies the summarized violation reports for each of the schema files.
Manual checking:
The XML DRC categorizes its guidelines by chapters of specific topics, and various levels of enforcement (i.e., Must, Must Not, Should, Should Not, and May). Each rule has been assigned a unique identification following the naming convention of combining the chapter and sequence numbers.
2.2.2Review Results
Complete results are provided in Appendix B. In general, the Open Dump Version 1.0 schemas conformed to the design rules with few violations/exceptions.
Automated Tool Checking:
The Automated Tool found that the schemas were not in violation of any schema rules.
Manual Checking:
The manual inspection of the general design rules yielded no deviations from the DRCs. Filenaming conventions matched the rule and are consistent with other schema on the exchange network. Tag names have been derived using prescribed naming conventions.
2.2.3Recommendations
None.
2.3Core Reference Model (CRM) Shared Schema Component (SSC) Conformance
The Information Management Work Group (IMWG) under the Exchange Network created the CRM Version 2 to provide the EDSC, TRG, and Exchange Network Partners with guidelines for consistently building and sharing data on the Exchange Network. The Open Dump Version 1.0 schema was evaluated against the Shared Schema Components under this schema conformance review effort for its normalization and modularity.
2.3.1Methodology[1]
This process involved breaking downthe types of integration into three separate levels:
- High Integration Instances where SSC elements or data types with complex contentwere directly integrated into the target schema without modification.
- Medium Integration Instances where SSC elements or data types with complex contentwere modified through the process of XML extension and/orrestriction before being included into the target schema.
- Low Integration Instances where elements or data types with simple content wereintegrated into the target schema.
2.3.2Review Results
NoOpen Dump data elements could take advantage of the high or mediumlevel of integration with the SSCs as these elements either did not match any from the SSCs or there were already equivalents in the FRS schema. Four Open Dump data elements had a low level of integration by virtue of using existing data type definitions found in the SC_SimpleContent_v1.0.xsd.
The schema adopted a similar approach to the SSCs with respect to the creation of an XX_SimpleContent.xsd file for defining base elements and types as shown here:
Open Dump Data Block / Corresponding SSCOD_SimpleContent_v1.0.xsd / SC_SimpleContent_v1.0.xsd
Open Dump Data Elements that use the SSC data definition found in the SC_SimpleContent_v1.0.xsd
sc:OrganizationIdentifier
sc:TribalName
sc:TribalCode
sc:TribalLandName
2.3.3Recommendations
None.
Open Dump Schema Review Conformance Report01182008.docPage 1 of 21
enfoTech07/24/2007
2.4EDSC Data Standards Conformance
The EDSC data standards provide approved data elements and definitions to provide higher quality of data for data exchange exercises between various data partners. The Open DumpSchema Version 1.0 was evaluated against the EDSC data standards for conformance.
2.4.1Methodology
This review involved evaluating the conformance of data elements with existing standards. Data standard information was obtained from the EDSC. The elements in the schema were compared against the approved data standards. These standards are listed here:
EDSC Data Standard / Version / StatusContact Information / EX000019.2 (1/6/2006) / Approved
Latitude/Longitude / EX000017.2 (1/6/2006) / Approved
Tribal Identifier / EX000023.2 (1/6/2006) / Approved
Attached Binary Objects / EX000006.1 (1/6/2006) / Approved
Measure / EX000010.1 (1/6/2006) / Approved
Method / EX000011.1 (1/6/2006) / Approved
Facility Identification / EX000020.2 (1/6/2006) / Approved
During the XML schema development process, each element was created with consideration to the EDSC data standards.
2.4.2Review Results
A listing of the XML schema components that did not map to anyof the EDSC standards is included in AppendixC. This section describes in further the following area:
Open Dump elements that have a discrepancy in a mapping with an EDSC standard element: These are cases where an Open Dump data element has a corresponding EDSC element, but already maps to an FRS element.
Of the 51 elements, 11 could find a mapping to an existing FRS element,which itself was built close to EDSC data standards, 4 had a corresponding EDSC element, and the other 37 couldn’t map to any EDSC standard: thus the EDSC data standards cover over 25% of the data elements in the schema. The 11 elements with an FRS mapping that closely match the EDSC standards are:
Open Dump XML Elements with corresponding FRS mappingOpen Dump Schema Element / Justification
facid:OrganizationFormalName / Similar element found in Contact Information but element exists in FRS.
facid:LatitudeMeasure / Found in Latitude/Longitude standard but element exists in FRS.
facid:LongitudeMeasure / Found in Latitude/Longitude standard but element exists in FRS.
facid:Facility_Registry_Identifier / Found in Facility Identification standard but element exists in FRS.
facid:Facility_Site_Name / Found in Facility Identification standard but element exists in FRS.
facid:TribalLandIndicator / Similar element found in Contact Information but element exists in FRS.
facid:LastReportedDate / No similar element found in ESAR.
facid:IndividualFullName / Similar element found in Contact Information but element exists in FRS.
facid:CountyName / Found in Facility Identification standard but element exists in FRS.
facid:StateName / Found in Facility Identification standard but element exists in FRS.
facid:LocationDescriptionText / Found in Facility Identification standard but element exists in FRS.
2.4.3Recommendations
Data element selection for those that both mapped and did not map exactly to EDSC data standards were chosen carefully and with consistent attempts to make in line with the standards while not sacrificing the functionality of the submission process.The remaining discrepancies are the result of various decisions based on business needs.
Section 3. Conclusion
Based on the findings of the schema review process, the Open Dump v1.0 is in line with all but a few conformance requirements. These areas of non-conformance have been justified in the report.
As CNEPOpen Dump pilot activities have been completed, the team recommends publication of the schema on the Exchange Network registry at this time.
Appendix A: W3C Schema Validation Results
Altova XML Spy© 2006
IBM Schema Quality Checker 2.2
The IBM Schema Quality Checker 2.2 was run from the command prompt.
The FRS schema files have the error types shown above.
The Open Dump schema files have no errors as shown below.
Appendix B: EN Design Rules & Conventions Validation Results
Violations for File : OD_FacilitySiteAll_v1.0.xsdFri Jan 18 19:44:54 EST 2008
Total Number of Violations = 0
Violations for File : OD_HazardFactorDetails_v1.0.xsd
Fri Jan 18 19:42:53 EST 2008
Total Number of Violations = 0
Violations for File : OD_HealthThreatDetails_v1.0.xsd
Fri Jan 18 19:43:33 EST 2008
Total Number of Violations = 0
Violations for File : OD_LocationDetails_v1.0.xsd
Fri Jan 18 19:43:50 EST 2008
Total Number of Violations = 0
Violations for File : OD_OpenDumpDetails_v1.0.xsd
Fri Jan 18 19:44:05 EST 2008
Total Number of Violations = 0
Violations for File : OD_SimpleContent_v1.0.xsd
Fri Jan 18 19:44:15 EST 2008
Total Number of Violations = 0
Violations for File : OD_SiteInformationDetails_v1.0.xsd
Fri Jan 18 19:44:33 EST 2008
Total Number of Violations = 0
Violations for File : FACID_AffiliationDataType_v2.3.xsd
Wed Jul 25 16:40:30 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_AlternativeNameDetails_v2.3.xsd
Wed Jul 25 16:41:27 EDT 2007
Total Number of Violations = 0
Violations for File : Violations for File : FACID_AlternativeNameList_v2.3.xsd
Wed Jul 25 16:42:44 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_AltNameDataType_v2.3.xsd
Wed Jul 25 16:43:32 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_DistrictDataType_v2.3.xsd
Wed Jul 25 16:44:27 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_DUNSIdentifierDataType_v2.3.xsd
Wed Jul 25 16:45:21 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_EnvironmentalInterestDataType_v2.3.xsd
Wed Jul 25 16:46:41 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_EnvironmentalInterestDetails_v2.3.xsd
Wed Jul 25 16:47:30 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_EnvironmentalInterestList_v2.3.xsd
Wed Jul 25 16:48:10 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_FacilitySiteAll_v2.3.xsd
Wed Jul 25 16:49:38 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_FacilitySiteAllDetails_v2.3.xsd
Wed Jul 25 16:50:15 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_FacilitySiteDataType_v2.3.xsd
Wed Jul 25 16:50:51 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_FacilitySiteDetails_v2.3.xsd
Wed Jul 25 16:51:46 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_FacilitySiteList_v2.3.xsd
Wed Jul 25 16:52:21 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_FederalStateIndicatorDataType_v2.3.xsd
Wed Jul 25 16:52:59 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_FIPSCodeDataType_v2.3.xsd
Wed Jul 25 16:53:46 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_GeographicCoordinateDataType_v2.3.xsd
Wed Jul 25 16:54:31 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_GeographicCoordinateDetails_v2.3.xsd
Wed Jul 25 16:55:19 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_GeographicCoordinatesList_v2.3.xsd
Wed Jul 25 16:56:07 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_GeometricDataType_v2.3.xsd
Wed Jul 25 16:57:06 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_HorizontalDatumDataType_v2.3.xsd
Wed Jul 25 16:58:27 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_HorizontalMethodDataType_v2.3.xsd
Wed Jul 25 16:59:09 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_HUCCodeDataType_v2.3.xsd
Wed Jul 25 16:59:55 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_IndividualDataType_v2.3.xsd
Wed Jul 25 17:00:37 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_IndividualDetails_v2.3.xsd
Wed Jul 25 17:01:14 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_IndividualList_v2.3.xsd
Wed Jul 25 17:01:47 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_LatitudeDataType_v2.3.xsd
Wed Jul 25 17:02:27 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_LocationAddressDataType_v2.3.xsd
Wed Jul 25 17:03:05 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_LongitudeDataType_v2.3.xsd
Wed Jul 25 17:03:52 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_MailingAddressDataType_v2.3.xsd
Wed Jul 25 17:04:25 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_MailingAddressDetails_v2.3.xsd
Wed Jul 25 17:05:03 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_MailingAddressList_v2.3.xsd
Wed Jul 25 17:05:39 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_NAICSCodeDataType_v2.3.xsd
Wed Jul 25 17:06:16 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_NAICSCodeDetails_v2.3.xsd
Wed Jul 25 17:06:51 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_NAICSCodeList_v2.3.xsd
Wed Jul 25 17:07:17 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_OrganizationDataType_v2.3.xsd
Wed Jul 25 17:07:51 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_OrganizationDetails_v2.3.xsd
Wed Jul 25 17:08:23 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_OrganizationList_v2.3.xsd
Wed Jul 25 17:08:58 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_PhoneFaxEmailDataType_v2.3.xsd
Wed Jul 25 17:09:33 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_PrimaryIndicatorDataType_v2.3.xsd
Wed Jul 25 17:10:09 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_ReferencePointDataType_v2.3.xsd
Wed Jul 25 17:20:39 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_SICCodeDataType_v2.3.xsd
Wed Jul 25 17:21:55 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_SICCodeDetails_v2.3.xsd
Wed Jul 25 17:22:26 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_SICCodeList_v2.3.xsd
Wed Jul 25 17:23:01 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_StateCodeDataType_v2.3.xsd
Wed Jul 25 17:23:45 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_SubEntityDataType_v2.3.xsd
Wed Jul 25 17:24:22 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_VerticalDatumDataType_v2.3.xsd
Wed Jul 25 17:24:54 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_VerticalMeasureDataType_v2.3.xsd
Wed Jul 25 17:10:09 EDT 2007
Total Number of Violations = 0
Violations for File : FACID_VerticalMethodDataType_v2.3.xsd
Wed Jul 25 17:27:11 EDT 2007
Total Number of Violations = 0
Open Dump Schema Review Conformance Report01182008.docPage 1 of 21