Schema Conformance Report

Flow Documentation Status and Contact Information

Flow Name: Toxics Release Inventory (TRI)

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

Conformance Report Author:Jonathan Cruise

Contact Information:CGI

12601 Fair Lakes Circle

Fairfax, VA 22033

703-227-4657

Schema Developer:Rajendra Bapat

Contact Information:CGI

12601 Fair Lakes Circle

Fairfax, VA 22033

703-227-4468

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

Date Flow Documentation Package Submitted: September 28, 2011

W3C Conformance and Validation

W3C’s XSV Tool Output:

[X] yes [ ] noOutput pasted in the last section of the Conformance Report

[X] yes [ ] noZero 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

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 Enterprise Edition version 2011 rel. 3 sp1 / Development tool
XSV / W3C Conformance and Validation
Exchange Network Document Validation Service / CDX XML validation (

[] 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”.

File Type / xmlspy / XSV / Exchange Network Document Validation Service
Schema / Yes / Yes / NA2
Instance / Yes / NA1 / Yes

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 Exchange Network Document Validation Service is designed to validate an XML document using an XML schema that has been made available through its interface. Thus, the XML schema itself was not validated using the Exchange Network Document Validation Service.

Design Rules and Conventions Conformance

Note: The DRC Schema Design Tool at is no longer operational. The conformance results below are from version 4.0 of the TRI schema.

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 attributes in place of data elements. / Line 47: the attribute SubmissionIdentifierContext is defined as the only content of data element TRISubmissionIdentifier.
[SD3-19] Data-centric schemas SHOULD NOT use the “use” indicator when the required value is the default value. / Line 47: the “use” indicator defines the attribute to be optional when the associated data element is already defined as optional.

Violation Locations Identified in TRI_TRI_v4.0_draft.xsd:

<?xml version="1.0" encoding="UTF-8"?>

<!-- edited with XMLSpy v2008 sp1 ( by WDavid Ripley, III (COMPUTER SCIENCES CORP) -->

<xsd:schema xmlns:TRI=" xmlns:xsd=" xmlns:sc="urn:us:net:exchangenetwork:sc:1:0" targetNamespace=" elementFormDefault="qualified" attributeFormDefault="unqualified" version="4.0">

<xsd:import namespace="urn:us:net:exchangenetwork:sc:1:0" schemaLocation="SC_SimpleContent_v1.0.xsd"/>

<xsd:import namespace="urn:us:net:exchangenetwork:sc:1:0" schemaLocation="SC_IndividualIdentity_v1.0.xsd"/>

<xsd:import namespace="urn:us:net:exchangenetwork:sc:1:0" schemaLocation="SC_ElectronicAddress_v1.0.xsd"/>

<xsd:include schemaLocation="TRI_Facility_v4.0_draft.xsd"/>

<xsd:include schemaLocation="TRI_Report_v4.0_draft.xsd"/>

<xsd:annotation>

<xsd:documentation>

Schema Name : TRI_TRI_v4.0.xsd

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 [

</xsd:documentation>

</xsd:annotation>

<xsd:element name="TRI" type="TRI:TRIDataType"/>

<xsd:complexType name="TRIDataType">

<xsd:sequence>

<xsd:element ref="TRI:Submission" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:complexType>

<xsd:element name="Submission" type="TRI:SubmissionDataType">

<xsd:annotation>

<xsd:documentation>A container for one or more TRI Reports for a given facility.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<xsd:complexType name="SubmissionDataType">

<xsd:sequence>

<xsd:element ref="TRI:TRISubmissionIdentifier" minOccurs="0"/>

<xsd:element ref="TRI:Facility" minOccurs="0"/>

<xsd:element ref="TRI:Report" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:complexType>

<xsd:element name="TRISubmissionIdentifier" type="TRI:SubmissionIdentifierDataType">

<xsd:annotation>

<xsd:documentation>A number used to uniquely identify a TRI submission, which contains data for one facility and one or more chemicals.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<xsd:complexType name="SubmissionIdentifierDataType">

<xsd:simpleContent>

<xsd:extension base="xsd:string">

<xsd:attribute name="SubmissionIdentifierContext" type="xsd:string" use="optional"/> Violations SD3-9 and SD3-19 (Line 47)

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

</xsd:schema>

Explanation of DRC Violations Identified by Manual Inspection:

No violations were identified by manual inspection of the schema.
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 v5.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
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
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
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
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

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 9TRI 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.

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/tmpK1XRQuuploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_ChemicalActivity_v5.0.xsd)
  • docElt: {
  • 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

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

  • Target: file:/usr/local/XSV/xsvlog/tmprQqRmzuploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_OnsiteRecyclingProcesses_v5.0.xsd)
  • docElt: {
  • 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

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

  • Target: file:/usr/local/XSV/xsvlog/tmpKwExynuploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_ChemicalIdentification_v5.0.xsd)
  • docElt: {
  • 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

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

  • Target: file:/usr/local/XSV/xsvlog/tmpc366Siuploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_WaterStream_v5.0.xsd)
  • docElt: {
  • 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

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

  • Target: file:/usr/local/XSV/xsvlog/tmpSrHqceuploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_WasteTreatmentMethod_v5.0.xsd)
  • docElt: {
  • 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

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

  • Target: file:/usr/local/XSV/xsvlog/tmp5hsbwuuploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_WasteTreatmentDetails_v5.0.xsd)
  • docElt: {
  • 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

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

  • Target: file:/usr/local/XSV/xsvlog/tmp6vHG5suploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_TRI_v5.0.xsd)
  • docElt: {
  • 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

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

  • Target: file:/usr/local/XSV/xsvlog/tmpHUMf3Duploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_TransferQuantity_v5.0.xsd)
  • docElt: {
  • 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

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

  • Target: file:/usr/local/XSV/xsvlog/tmpBr5grfuploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_TransferLocation_v5.0.xsd)
  • docElt: {
  • 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

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

  • Target: file:/usr/local/XSV/xsvlog/tmpx5Mdqpuploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_ToxicEqivalencyIdentification_v5.0.xsd)
  • docElt: {
  • 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

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

  • Target: file:/usr/local/XSV/xsvlog/tmpmWiecyuploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_SourceReductionQuantity_v5.0.xsd)
  • docElt: {
  • 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

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

  • Target: file:/usr/local/XSV/xsvlog/tmp3X1ryyuploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_SourceReductionActivity_v5.0.xsd)
  • docElt: {
  • 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

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

  • Target: file:/usr/local/XSV/xsvlog/tmpcO9zEnuploaded
    (Real name: C:\TRI_DRAFT_v5.0\5\0\TRI_SharedTypes_v5.0.xsd)
  • docElt: {
  • 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

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