Schema Conformance Report

Flow Documentation Status and Contact Information

Flow Name: Toxic Release Inventory (TRI)

Schemas/Versions included in Conformance Report: TRI schema version 4.0

Conformance Report Author: WDavid Ripley, III Contact Information: Computer Sciences Corporation 8400 Corporate Drive, Suite 150 New Carrollton, MD 20785 301.429.8223 [email protected]

Schema Developer: WDavid Ripley III Contact Information: Same as above

Flow Owner or Other Point of Contact for Flow Documentation Package: Juan Parra Contact Information: U.S. Environmental Protection Agency OEI/OIAA/TRI Program Division Information and Outreach Branch Washington, DC 20460 202.566.0499 [email protected]

Date Flow Documentation Package Submitted: XXX, 2008

W3C Conformance and Validation

W3C’s XSV Tool Output: [X] yes [ ] no Output pasted in the last section of the Conformance Report [X] yes [ ] no Zero errors identified by XSV Tool

Explanation of Warnings Listed in XSV Tool Output:

Warning Explanation No warnings observed Schema was developed using industry best-practice whenever possible

EPA/CSC 1 December, 2008 Schema and Instance Document Validation:

Names of XML parser(s) intended for use in conjunction with the flow and development tool(s) used to validate the schema and instance documents:

Altova xmlspy Professional Edition, v2006.sp2 Development tool XSV W3C Conformance and Validation Facility Registry System (FRS) schema design tool EPA on-line standards validation tool Microsoft DotNet Parser v2.0 CDX Test and Production servers

[ ] yes [ ] no All schema files validate using all parsers and tools listed above [ ] yes [ ] no All sample instance documents validate using all parsers and tools listed above [ ] yes [ ] no All sample instance documents validate using the CDX validator service

EXPLANATON:

None of the above three questions can be answered globally for all parsers in the above list but can be addressed individually. Explanations follow concerning each question not answered with “Yes” as well as when an answer is expected to be obtained.

File Type xmlspy XSV FRS Tool DotNet 2.0 Schema Yes Yes Yes Likely3 Instance Yes NA1 NA2 Likely3

1: A TRI instance document cannot be validated with the XSV tool because, among other reasons, XML files in draft form do not yet reside at the intended http address that must be specified in the schema file headers and the XSV tools tries to load these files from that intended location.

2: The FRS schema design tool is only meant to check conformance of schema to design rules but it only checks design rules that can be verified electronically. Some EPA schema design rules identified in the XML Schema Design Rule and Conventions (DRC) document must be check by manual inspection. Additionally, there is no functionality to check an instance document with the FRS schema design tool. This schema validation tool is used as a matter of routine because it has identified schema design errors in the past that are easily overlooked during development and not considered problems in other schema validation tools.

3: The DotNet 2.0 parser is used in the CDX Test and Production environments. A customized version of it is also used by XMLSpy. Because all TRI schema and instance files are considered valid by XMLSpy, it is likely, but not proven, that the same is true for the DotNet 2.0 parser used by the CDX Test and Production environments. Because the CDX Test server is used for integration testing, it is not considered appropriate or cost-effective to configure the server for a schema validation test. This test is typically performed during the integration test phase of flow deployment. Additionally, CSC does not consider it cost-effective to create a test environment specifically targeted to this purpose because the test is considered redundant and, to date, no known discrepancy between schemas considered valid by XMLSpy and not by DotNet 2.0 has been observed.

EPA/CSC 2 December, 2008 Design Rules and Conventions Conformance

Explanation of DRC Violations Identified by FRS Schema Design Tool:

The following 2 violations were identified for the TRI schema version 4.0 by using the FRS schema design tool, down from 4 violations identified for the TRI schema version 3.0. The TRI schema version 3.0 violations SD2-1 and SD2-3 were corrected in TRI schema version 4.0. Both remaining violations occur in the TRI_TRI_v4.0_draft.xsd schema file. After investigating the source of these violations, it was determined that they both were present in the original version 1.2 of the schema because this file has not required modification, with the exception of changing the schema version number and adding header documentation, for any subsequent version. Unfortunately, it is not possible to correct these violations and make the TRI schema version 4.0 backward compatible with the TRI schema version 3.0, a requirement stated in the associated Statement of Work. In addition to this, it should be noted that the schema construct causing both violations is modeled exactly as similar constructs found in file SC_SimpleContent_v1.0.xsd from the Shared Schema Component (SSC) library which contains the same violations when submitted to the FRS schema design tool. Because of this, a waiver is requested for these 2 violations for the TRI schema version 4.0. Each violation is cross-referenced to the location in TRI_TRI_v4.0_draft.xsd where it occurs in the following section.

Violation Explanation [SD3-9] Data-centric schemas MUST NOT use Line 47: the attribute SubmissionIdentifierContext is attributes in place of data elements. defined as the only content of data element TRISubmissionIdentifier. [SD3-19] Data-centric schemas SHOULD NOT use Line 47: the “use” indicator defines the attribute to the “use” indicator when the required value is the be optional when the associated data element is default value. already defined as optional.

Violation Locations Identified in TRI_TRI_v4.0_draft.xsd:

Schema Name : TRI_TRI_v4.0.xsd

EPA/CSC 3 December, 2008 Current Version Available At : Description : This is the root schema for Toxic Release Inventory reporting data Aplication : Toxic Release Inventory Developed by : Environmental Protection Agency, Windsor Solutions, Inc. Point of Contact : William Rensmith Maintained by : Environmental Protection Agency, CSC Point of Contact : WDavid Ripley III [[email protected]] A container for one or more TRI Reports for a given facility. A number used to uniquely identify a TRI submission, which contains data for one facility and one or more chemicals.  Violations SD3-9 and SD3-19 (Line 47)

EPA/CSC 4 December, 2008 Explanation of DRC Violations Identified by Manual Inspection:

No violations were identified by manual inspection of the schema. This is because the 8 violations identified for the TRI schema version 3.0, all GD3-A, were resolved for the TRI schema version 4.0.

EPA/CSC 5 December, 2008 Shared Schema Components Conformance

High Level of SSC Integration:

The following SSC library data elements, presented in the order in which they are found in the schema, are used by the TRI v4.0 schema:

SSC Data Element Name Schema Path FacilitySiteName TRI/Submission/Facility LocationAddress TRI/Submission/Facility LocationAddressText TRI/Submission/Facility/LocationAddress SupplementalLocationText TRI/Submission/Facility/LocationAddress LocalityName TRI/Submission/Facility/LocationAddress StateIdentity TRI/Submission/Facility/LocationAddress StateCode TRI/Submission/Facility/LocationAddress/StateIdentity StateCodeListIdentifier TRI/Submission/Facility/LocationAddress/StateIdentity StateName TRI/Submission/Facility/LocationAddress/StateIdentity AddressPostalCode TRI/Submission/Facility/LocationAddress CountryIdentity TRI/Submission/Facility/LocationAddress CountryCode TRI/Submission/Facility/LocationAddress/CountryIdentity CountryCodeListIdentifier TRI/Submission/Facility/LocationAddress/CountryIdentity CountryName TRI/Submission/Facility/LocationAddress/CountryIdentity CountyIdentity TRI/Submission/Facility/LocationAddress CountyCode TRI/Submission/Facility/LocationAddress/CountyIdentity CountyCodeListIdentifier TRI/Submission/Facility/LocationAddress/CountyIdentity CountyName TRI/Submission/Facility/LocationAddress/CountyIdentity TribalIdentity TRI/Submission/Facility/LocationAddress TribalCode TRI/Submission/Facility/LocationAddress/TribalIdentity TribalCodeListIdentifier TRI/Submission/Facility/LocationAddress/TribalIdentity TribalName TRI/Submission/Facility/LocationAddress/TribalIdentity TribalLandName TRI/Submission/Facility/LocationAddress TribalLandIndicator TRI/Submission/Facility/LocationAddress LocationDescriptionText TRI/Submission/Facility/LocationAddress MailingAddressText TRI/Submission/Facility/MailingAddress SupplementalAddressText TRI/Submission/Facility/MailingAddress MailingAddressCityName TRI/Submission/Facility/MailingAddress StateIdentity TRI/Submission/Facility/MailingAddress StateCode TRI/Submission/Facility/MailingAddress/StateIdentity StateCodeListIdentifier TRI/Submission/Facility/MailingAddress/StateIdentity StateName TRI/Submission/Facility/MailingAddress/StateIdentity AddressPostalCode TRI/Submission/Facility/MailingAddress/StateIdentity

EPA/CSC 6 December, 2008 SSC Data Element Name Schema Path CountryIdentity TRI/Submission/Facility/MailingAddress CountryCode TRI/Submission/Facility/MailingAddress/CountryIdentity CountryCodeListIdentifier TRI/Submission/Facility/MailingAddress/CountryIdentity CountryName TRI/Submission/Facility/MailingAddress/CountryIdentity SICCode TRI/Submission/Facility/FacilitySIC SICPrimaryIndicator TRI/Submission/Facility/FacilitySIC NAICSCode TRI/Submission/Facility/FacilityNAICS NAICSPrimaryIndicator TRI/Submission/Facility/FacilityNAICS LatitudeMeasure TRI/Submission/Facility/GeographicLocationDescription LongitudeMeasure TRI/Submission/Facility/GeographicLocationDescription SourceMapScaleNumber TRI/Submission/Facility/GeographicLocationDescription HorizontalAccuracyMeasure TRI/Submission/Facility/GeographicLocationDescription MeasureValue TRI/Submission/Facility/GeographicLocationDescription/ HorizontalAccuracyMeasure MeasureUnit TRI/Submission/Facility/GeographicLocationDescription/ HorizontalAccuracyMeasure MeasureUnitCode TRI/Submission/Facility/GeographicLocationDescription/ HorizontalAccuracyMeasure/MeasureUnitCode MeasureUnitCodeListIdentifier TRI/Submission/Facility/GeographicLocationDescription/ HorizontalAccuracyMeasure/MeasureUnitCode MeasureUnitName TRI/Submission/Facility/GeographicLocationDescription/ HorizontalAccuracyMeasure/MeasureUnitCode MeasurePrecisionText TRI/Submission/Facility/GeographicLocationDescription/ HorizontalAccuracyMeasure ResultQualifier TRI/Submission/Facility/GeographicLocationDescription/ HorizontalAccuracyMeasure ResultQualifierCode TRI/Submission/Facility/GeographicLocationDescription/ HorizontalAccuracyMeasure/ResultQualifier ResultQualifierCodeListIdentifier TRI/Submission/Facility/GeographicLocationDescription/ HorizontalAccuracyMeasure/ResultQualifier ResultQualifierName TRI/Submission/Facility/GeographicLocationDescription/ HorizontalAccuracyMeasure/ResultQualifier HorizontalCollectionMethod TRI/Submission/Facility/GeographicLocationDescription MethodIdentifierCode TRI/Submission/Facility/GeographicLocationDescription/ HorizontalCollectionMethod MethodIdentifierCodeListIdentifier TRI/Submission/Facility/GeographicLocationDescription/ HorizontalCollectionMethod MethodName TRI/Submission/Facility/GeographicLocationDescription/ HorizontalCollectionMethod MethodDescriptionText TRI/Submission/Facility/GeographicLocationDescription/ HorizontalCollectionMethod MethodDeviationsText TRI/Submission/Facility/GeographicLocationDescription/ HorizontalCollectionMethod GeographicReferencePoint TRI/Submission/Facility/GeographicLocationDescription

EPA/CSC 7 December, 2008 SSC Data Element Name Schema Path GeographicReferencePointCode TRI/Submission/Facility/GeographicLocationDescription/ GeographicReferencePoint ReferencePointCodeListIdentifier TRI/Submission/Facility/GeographicLocationDescription/ GeographicReferencePoint GeographicReferencePointName TRI/Submission/Facility/GeographicLocationDescription/ GeographicReferencePoint HorizontalReferenceDatum TRI/Submission/Facility/GeographicLocationDescription GeographicReferenceDatumCode TRI/Submission/Facility/GeographicLocationDescription/ HorizontalReferenceDatum GeographicReferenceDatumCodeListIdentifier TRI/Submission/Facility/GeographicLocationDescription/ HorizontalReferenceDatum GeographicReferenceDatumName TRI/Submission/Facility/GeographicLocationDescription/ HorizontalReferenceDatum DataCollectionDate TRI/Submission/Facility/GeographicLocationDescription LocationCommentsText TRI/Submission/Facility/GeographicLocationDescription VerticalMeasure TRI/Submission/Facility/GeographicLocationDescription MeasureValue TRI/Submission/Facility/GeographicLocationDescription/ VerticalMeasure MeasureUnit TRI/Submission/Facility/GeographicLocationDescription/ VerticalMeasure MeasureUnitCode TRI/Submission/Facility/GeographicLocationDescription/ VerticalMeasure/MeasureUnit MeasureUnitCodeListIdentifier TRI/Submission/Facility/GeographicLocationDescription/ VerticalMeasure/MeasureUnit MeasureUnitName TRI/Submission/Facility/GeographicLocationDescription/ VerticalMeasure/MeasureUnit MeasurePrecisionText TRI/Submission/Facility/GeographicLocationDescription/ VerticalMeasure ResultQualifier TRI/Submission/Facility/GeographicLocationDescription/ VerticalMeasure ResultQualifierCode TRI/Submission/Facility/GeographicLocationDescription/ VerticalMeasure/ResultQualifier ResultQualifierCodeListIdentifier TRI/Submission/Facility/GeographicLocationDescription/ VerticalMeasure/ResultQualifier ResultQualifierName TRI/Submission/Facility/GeographicLocationDescription/ VerticalMeasure/ResultQualifier VerticalCollectionMethod TRI/Submission/Facility/GeographicLocationDescription MethodIdentifierCode TRI/Submission/Facility/GeographicLocationDescription/ VerticalCollectionMethod MethodIdentifierCodeListIdentifier TRI/Submission/Facility/GeographicLocationDescription/ VerticalCollectionMethod MethodName TRI/Submission/Facility/GeographicLocationDescription/ VerticalCollectionMethod MethodDescriptionText TRI/Submission/Facility/GeographicLocationDescription/ VerticalCollectionMethod

EPA/CSC 8 December, 2008 SSC Data Element Name Schema Path MethodDeviationsText TRI/Submission/Facility/GeographicLocationDescription/ VerticalCollectionMethod VerticalReferenceDatum TRI/Submission/Facility/GeographicLocationDescription GeographicReferenceDatumCode TRI/Submission/Facility/GeographicLocationDescription/ VerticalReferenceDatum GeographicReferenceDatumCodeListIdentifier TRI/Submission/Facility/GeographicLocationDescription/ VerticalReferenceDatum GeographicReferenceDatumName TRI/Submission/Facility/GeographicLocationDescription/ VerticalReferenceDatum VerificationMethod TRI/Submission/Facility/GeographicLocationDescription MethodIdentifierCode TRI/Submission/Facility/GeographicLocationDescription/ VerificationMethod MethodIdentifierCodeListIdentifier TRI/Submission/Facility/GeographicLocationDescription/ VerificationMethod MethodName TRI/Submission/Facility/GeographicLocationDescription/ VerificationMethod MethodDescriptionText TRI/Submission/Facility/GeographicLocationDescription/ VerificationMethod MethodDeviationsText TRI/Submission/Facility/GeographicLocationDescription/ VerificationMethod CoordinateDataSource TRI/Submission/Facility/GeographicLocationDescription CoordinateDataSourceCode TRI/Submission/Facility/GeographicLocationDescription/ CoordinateDataSource CoordinateDataSourceCodeListIdentifier TRI/Submission/Facility/GeographicLocationDescription/ CoordinateDataSource CoordinateDataSourceName TRI/Submission/Facility/GeographicLocationDescription/ CoordinateDataSource GeometricType TRI/Submission/Facility/GeographicLocationDescription GeometricTypeCode TRI/Submission/Facility/GeographicLocationDescription/ GeometricType GeometricTypeCodeListIdentifier TRI/Submission/Facility/GeographicLocationDescription/ GeometricType GeometricTypeName TRI/Submission/Facility/GeographicLocationDescription/ GeometricType ReportIdentifier TRI/Submission/Report ReplacedReportIdentifier TRI/Submission/Report ReportTypeCodeListIdentifier TRI/Submission/Report/ReportType ReportTypeName TRI/Submission/Report/ReportType ReportDueDate TRI/Submission/Report RevisionIndicator TRI/Submission/Report IndividualIdentifier TRI/Submission/Report/TechnicalContactNameText IndividualTitleText TRI/Submission/Report/TechnicalContactNameText NamePrefixText TRI/Submission/Report/TechnicalContactNameText IndividualFullName TRI/Submission/Report/TechnicalContactNameText

EPA/CSC 9 December, 2008 SSC Data Element Name Schema Path FirstName TRI/Submission/Report/TechnicalContactNameText MiddleName TRI/Submission/Report/TechnicalContactNameText LastName TRI/Submission/Report/TechnicalContactNameText NameSuffixText TRI/Submission/Report/TechnicalContactNameText IndividualIdentifier TRI/Submission/Report/PublicContactNameText IndividualTitleText TRI/Submission/Report/PublicContactNameText NamePrefixText TRI/Submission/Report/PublicContactNameText IndividualFullName TRI/Submission/Report/PublicContactNameText FirstName TRI/Submission/Report/PublicContactNameText MiddleName TRI/Submission/Report/PublicContactNameText LastName TRI/Submission/Report/PublicContactNameText NameSuffixText TRI/Submission/Report/PublicContactNameText CASNumber TRI/Submission/Report/ChemicalIdentification EPAChemicalIdentifier TRI/Submission/Report/ChemicalIdentification EPAChemicalRegistryName TRI/Submission/Report/ChemicalIdentification EPAChemicalRegistryNameContext TRI/Submission/Report/ChemicalIdentification

EPA/CSC 10 December, 2008 The following TRI data elements use SSC library data types:

TRI Data Element Name & SSC Data Type Schema Path FacilityIdentifier, sc:FacilitySiteIdentifierDataType TRI/Submission/Facility MailingFacilitySiteName, sc:FacilitySiteNameDataType TRI/Submission/Facility SubmissionFederalFacilityIndicator, sc:FederalFacilityIndicatorDataType TRI/Submission/Report TechnicalContactNameText, sc:IndividualIdentityDataType TRI/Submission/Report TechnicalContactPhoneText, sc:TelephoneNumberTextDataType TRI/Submission/Report TechnicalContactEmailAddressText, sc:ElectronicAddressTextDataType TRI/Submission/Report PublicContactNameText, sc:IndividualIdentityDataType TRI/Submission/Report PublicContactPhoneText, sc:TelephoneNumberTextDataType TRI/Submission/Report PublicContactEmailAddressText, sc:ElectronicAddressTextDataType TRI/Submission/Report

Candidates for New Shared Schema Components:

The 9 TRI data elements that use SSC data types identified in the above table only do so because no corresponding SSC data element currently exists. Note that there is nothing TRI-specific about any of these data elements. Each of these data elements should be considered a candidate for addition to the SSC library of reusable data elements.

EPA/CSC 11 December, 2008 W3C’s XSV Tool Output

The following messages were captured as the output from the on-line XSV schema validation tool (XSV version: XSV 3.1-1). All 23 files in the flow schema were submitted to the XSV schema validation tool individually.

Schema validating with XSV 3.1-1 of 2007/12/11 16:20:05

 Target: file:/usr/local/XSV/xsvlog/tmpD8XoWhuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_ChemicalActivity_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmprXehbHuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_ChemicalIdentification_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpMpuf29uploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_Facility_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

EPA/CSC 12 December, 2008 Schema validating with XSV 3.1-1 of 2007/12/11 16:20:05

 Target: file:/usr/local/XSV/xsvlog/tmpaSpMr8uploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_GeographicLocationDescription_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmp7HYcVDuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_MailingAddress_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpPnnyAbuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_OnsiteRecoveryProcesses_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpCLGp-Cuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_OnsiteRecyclingProcesses_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpjFEqwxuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_OnsiteReleaseQuantity_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpdUHGKDuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_Report_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpFs4BwVuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_ReportMetaData_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpEFj8gouploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_ReportType_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpWuNS-luploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_ReportValidation_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpcrr8Pduploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_SharedComponents_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpUfUnXEuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_SharedTypes_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpfTfkCnuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_SourceReductionActivity_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpQN_3rtuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_SourceReductionQuantity_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpYhAVqcuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_ToxicEqivalencyIdentification_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpvgN9kQuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_TransferLocation_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpzsF51Quploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_TransferQuantity_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpRhyDoguploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_TRI_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpdHkNReuploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_WasteTreatmentDetails_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmp8Ry3-Buploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_WasteTreatmentMethod_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

 Target: file:/usr/local/XSV/xsvlog/tmpFIez2euploaded (Real name: C:\TRI_DRAFT_v4.0\4\0\TRI_WaterStream_v4.0_draft.xsd)  docElt: {http://www.w3.org/2001/XMLSchema}schema  Validation was strict, starting with type [Anonymous]  The schema(s) used for schema-validation had no errors  No schema-validity problems were found in the target

EPA/CSC 17 December, 2008