29-Dec-2009

ATT Schema Conformance Report

Flow Documentation Status and Contact Information

Flow Name: Integrated Report Water Assessment Database (ATT) flow for EPA Office of Water

Schemas/Versions included in Conformance Report: ATT v1.2

Conformance Report Author: Scott Kocher

Contact Information: INDUS Corporation, Vienna, VA, 22182; 703-506-6700

Schema Developer: Scott Kocher

Contact Information: INDUS Corporation, Vienna, VA, 22182; 703-506-6700

Other Point of Contact for Flow Documentation Package: Bob Booher

Contact Information: INDUS Corporation, Vienna, VA, 22182; 703-506-6700

Date Flow Documentation Package Submitted: December 29, 2009

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
None

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:

Xerxes
Oracle XML Parser

[X] yes [ ] no All schema files validate using all parsers and tools listed above

[X] yes [ ] no All sample instance documents validate using all parsers and tools listed above

[X] yes [ ] no All sample instance documents validate using the CDX validator service

Design Rules and Conventions Conformance

Note: The DRC Schema Design Tool at http://www.epa.gov/enviro/html/frs_demo/design_tool.html is no longer operational. The conformance results below are from version 1.1 of the ATT schema.

Explanation of DRC Violations Identified:

DRC Rule ID / Schema Filenames / Explanation
SD5-20: Data-centric schemas SHOULD include a version number (1.1) in their filename. / index.xsd / This violation occurs only in the index.xsd file, the default file for the ATT schema directory. Since the default file enables access to a schema without having to know any of the schema's filenames, it should not include a version number. The violation is not valid for this file.
SD6-10: Extreme caution SHOULD be applied when writing an XPath expression in a selector element to ensure it specifies the intended range. / ATT_AssessmentMethods_v1.1.xsd
ATT_AssessmentUnitBlobs_v1.1.xsd
ATT_AssessmentUnitCauses_v1.1.xsd
ATT_AssessmentUnitDelist_v1.1.xsd
ATT_AssessmentUnitLocations_v1.1.xsd
ATT_AssessmentUnits_v1.1.xsd
ATT_AssessmentWaters_v1.1.xsd
ATT_Causes_v1.1.xsd
ATT_CycleTrack_v1.1.xsd
ATT_UserCategories_v1.1.xsd
ATT_WQSAttainments_v1.1.xsd / This violation occurs in files that use XPath expressions to enforce uniqueness of schema elements. Uniqueness must be enforced to ensure that duplicate data is not provided, and this uniqueness is enforced using XPath expressions in selector elements. This violation is a caution rather than an actual conformity error. Extreme caution has been applied to the use of XPath expressions in the ATT schema. A sample XML file has been used to verify the accuracy of the schema's XPath expressions in selector elements.
SD6-19: Special attention SHOULD be paid to the restrictions on UNIQUE declaration names given above. / ATT_AssessmentMethods_v1.1.xsd
ATT_AssessmentUnitBlobs_v1.1.xsd
ATT_AssessmentUnitCauses_v1.1.xsd
ATT_AssessmentUnitDelist_v1.1.xsd
ATT_AssessmentUnitLocations_v1.1.xsd
ATT_AssessmentUnits_v1.1.xsd
ATT_AssessmentWaters_v1.1.xsd
ATT_Causes_v1.1.xsd
ATT_CycleTrack_v1.1.xsd
ATT_UserCategories_v1.1.xsd
ATT_WQSAttainments_v1.1.xsd / This violation occurs in several files that use the UNIQUE declaration to enforce uniqueness of schema elements. Uniqueness must be enforced to ensure that duplicate data is not provided, and this uniqueness is enforced using UNIQUE declarations. This violation is a caution rather than an actual conformity error. Extreme caution has been applied to the use of UNIQUE declarations in the ATT schema. A sample XML file has been used to verify the accuracy of the schema's UNIQUE declarations.

Shared Schema Components Conformance

High Level of SSC Integration:

Element Name / Schema Path
StateIdentity / http://www.exchangenetwork.net/schema
/SC/SC_StateIdentity_v2.0.xsd
GeographicLocationDescription / http://www.exchangenetwork.net/schema
/SC/SC_GeographicLocationDescription_v2.0.xsd

Medium Level of SSC Integration:

Element Name / Complex SSC Element or Data Type / Derived By
None

Low Level of SSC Integration:

Element Name / Simple SSC Element or Data Type
None

Explanation for Not Integrating Available SSCs:

Schema Name / Element or Type / SSC Element or Type / Explanation
None

Explanation for Not Integrating Available EDSC Element Names:

Schema Name / Element or Type / SSC Element or Type / Explanation
ATT_WQSAttainments_v1.1.xsd / AssessmentConfidence / DataQualityIndicator / The EDSC standard uses numeric values rather than text qualifiers, and is therefore more complex and precise than is needed for ATT.
ATT_WQSAttainments_v1.1.xsd / WQSAttainment / SamplePreparation / Attainments are different entities from samples, and so do not fit neatly into the data structure in the EDSC.
ATT_StateMethods_v1.1.xsd, ATT_AssessmentMethods_v1.1.xsd / StateMethod, AssessmentMethod / ReferenceMethod / The ReferenceMethod standard is meant for standardized lab/analytical methods used to arrive at a result, rather than assessment methods used to arrive at a conclusion.
SC_GeographicLocationDescription_v2.0.xsd / GeographicLocationDescription / MandatoryLatitudeLongitude & OptionalLatitudeLongitude / The SSC structure and naming conventions for this element are different from the EDSC.
SC_GeographicLocationDescription_v2.0.xsd / SourceMapScaleNumber / SourceMapScaleNumeric / The SSC structure and naming conventions for this element are different from the EDSC.
SC_GeographicLocationDescription_v2.0.xsd / HorizontalCollectionMethod / HorizontalCollectionMethodCode & HorizontalCollectionMethodName / The SSC structure and naming conventions for this element are different from the EDSC.
SC_GeographicLocationDescription_v2.0.xsd / GeographicReferencePoint / GeographicReferencePointCode & GeographicReferencePointName / The SSC structure and naming conventions for this element are different from the EDSC.
SC_GeographicLocationDescription_v2.0.xsd / HorizontalReferenceDatum / HorizontalCoordinateReferenceSystemDatumCode & HorizontalCoordinateReferenceSystemDatumName / The SSC structure and naming conventions for this element are different from the EDSC.
SC_GeographicLocationDescription_v2.0.xsd / VerticalCollectionMethod / VerticalCollectionMethodCode & VerticalCollectionMethodName / The SSC structure and naming conventions for this element are different from the EDSC.
SC_GeographicLocationDescription_v2.0.xsd / VerticalReferenceDatum / VerticalCoordinateReferenceSystemDatumCode & VerticalCoordinateReferenceSystemDatumName / The SSC structure and naming conventions for this element are different from the EDSC.
SC_GeographicLocationDescription_v2.0.xsd / VerificationMethod / VerificationMethodCode & VerificationMethodName / The SSC structure and naming conventions for this element are different from the EDSC.
SC_GeographicLocationDescription_v2.0.xsd / CoordinateDataSource / CoordinateDataSourceCode & CoordinateDataSourceName / The SSC structure and naming conventions for this element are different from the EDSC.
SC_GeographicLocationDescription_v2.0.xsd / GeometricType / GeometricTypeCode & GeometricTypeName / The SSC structure and naming conventions for this element are different from the EDSC.

Candidates for New SSCs:

Schema Name / Element or Type Name / CRM data block
None

Recommendations

  1. The Schema Design Tool should be modified to exclude validation check SD5-20 for the default schema file, index.xsd.
  2. Shared Schema Components could be more useful to developers if they made greater use of enumerations, maxLengths, decimal constraints, and required elements. Too many restrictions will limit the flexibility of schemas implementing these shared components, but there are many opportunities to include useful and appropriate refinements.
    For example, the SSC elements LatitudeMeasure and LongitudeMeasure are unrestricted strings. Their datatypes should instead be decimals, as below:

    Adding restrictions to datatypes in the SSC will improve their usefulness to schema developers and allow a higher degree of direct integration. With version 2.0 of the SSC components, developers of previous schemas, including WQX, have not made full use of them; instead, they have copied the SSC datatypes and redefined them using custom restrictions. This may not be necessary if greater refinement was added to the shared components. We recommend that version 3.0 of the SSC incorporate more datatype restrictions.
  3. Data elements were chosen carefully with an attempt to use the EDSC standards while not sacrificing the functionality of the data exchange process. ATT elements and data blocks that do not have corresponding data standards should be considered for inclusion in the next EDSC standards release, to make the structure of water assessment data available to other exchanges.
    In addition, there are discrepancies between the EDSC standards and the Shared Schema Components (for example: SSC element SourceMapScaleNumber vs. EDSC element SourceMapScaleNumeric). These two standards should be brought into conformance with each other. Having two different sets of element names and data structures may lead to confusion and incompatibilities in future data exchanges.
  4. The Schema Conformance Report Template should be updated to include the section “Explanation for Not Integrating Available EDSC Element Names”, as used above, to provide developers an opportunity to review and justify their exclusion of existing EDSC elements which do not yet have matching SSC schema elements.

W3C’s XSV Tool Output

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

* Target: [standalone schema assessment]

(Real name: http://amdbob1.induscorp.com/OWIR/ATT/index.xsd

Length: 1016 bytes

Last Modified: Tue, 29 Dec 2009 15:40:42 GMT

Server: Oracle-Application-Server-10g/10.1.2.0.2 Oracle-HTTP-Server)

* schemaDocs: http://amdbob1.induscorp.com/OWIR/ATT/index.xsd

* The schema(s) used for schema-validation had

no errors

* The target was not assessed

Schema resources involved

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/index.xsd

(source: command line) for

no namespace,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_StateAssessments_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_AssessmentUnits_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_UserCategories_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_AssessmentWaters_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_CycleTrack_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_AssessmentUnitCauses_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Causes_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_WQSAttainments_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_AssessmentUnitCauses_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_AssessmentMethods_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_StateMethods_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Causes_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_AssessmentUnitDelist_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_AssessmentUnitCauses_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_UserCategories_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_StateMethods_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_StateLocations_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_ATLAS_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://amdbob1.induscorp.com/OWIR/ATT/1/2/ATT_Shared_v1.2.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

skipped, already loaded

Attempt to load a schema document from

http://www.exchangenetwork.net/schema/SC/SC_StateIdentity_v2.0.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

Attempt to load a schema document from

http://www.exchangenetwork.net/schema/SC/SC_SimpleContent_v2.0.xsd

(source: include) for

http://www.exchangenetwork.net/schema/OWIR/ATT/1,

succeeded

DRC Schema Design Tool Output

Note: The DRC Schema Design Tool at http://www.epa.gov/enviro/html/frs_demo/design_tool.html is no longer operational. The conformance results below are from version 1.1 of the ATT schema.

Violations for File : index.xsd

Wed Mar 04 15:55:24 EST 2009

1 [SD5-20] Data-centric schemas SHOULD include a version number (1.0) in their filename.

Total Number of Violations = 1

Violations for File : ATT_v1.1.xsd

Wed Mar 04 15:56:07 EST 2009

Total Number of Violations = 0

Violations for File : ATT_StateAssessments_v1.1.xsd

Wed Mar 04 15:56:36 EST 2009

Total Number of Violations = 0

Violations for File : ATT_AssessmentMethods_v1.1.xsd

Wed Mar 04 15:57:13 EST 2009

1 [unique name=AMPK] [SD6-19] Special attention SHOULD be paid to the restrictions on UNIQUE declaration names given above. Line Number : 18

2 [selector name=] [SD6-10] Extreme caution SHOULD be applied when writing an XPath expression in a selector element to ensure it specifies the intended range. Line Number : 19

Total Number of Violations = 2

Violations for File : ATT_AssessmentUnitBlobs_v1.1.xsd

Wed Mar 04 15:57:32 EST 2009

1 [unique name=AUBPK] [SD6-19] Special attention SHOULD be paid to the restrictions on UNIQUE declaration names given above. Line Number : 23

2 [selector name=] [SD6-10] Extreme caution SHOULD be applied when writing an XPath expression in a selector element to ensure it specifies the intended range. Line Number : 24

Total Number of Violations = 2

Violations for File : ATT_AssessmentUnitCauses_v1.1.xsd

Wed Mar 04 15:57:53 EST 2009

1 [unique name=AUCPK] [SD6-19] Special attention SHOULD be paid to the restrictions on UNIQUE declaration names given above. Line Number : 42

2 [selector name=] [SD6-10] Extreme caution SHOULD be applied when writing an XPath expression in a selector element to ensure it specifies the intended range. Line Number : 43

3 [unique name=IAPK] [SD6-19] Special attention SHOULD be paid to the restrictions on UNIQUE declaration names given above. Line Number : 91

4 [selector name=] [SD6-10] Extreme caution SHOULD be applied when writing an XPath expression in a selector element to ensure it specifies the intended range. Line Number : 92

Total Number of Violations = 4

Violations for File : ATT_AssessmentUnitDelist_v1.1.xsd

Wed Mar 04 15:58:14 EST 2009

1 [unique name=AUDPK] [SD6-19] Special attention SHOULD be paid to the restrictions on UNIQUE declaration names given above. Line Number : 26

2 [selector name=] [SD6-10] Extreme caution SHOULD be applied when writing an XPath expression in a selector element to ensure it specifies the intended range. Line Number : 27

Total Number of Violations = 2

Violations for File : ATT_AssessmentUnitLocations_v1.1.xsd

Wed Mar 04 15:58:33 EST 2009

1 [unique name=AULPK] [SD6-19] Special attention SHOULD be paid to the restrictions on UNIQUE declaration names given above. Line Number : 26