Schemas/Versions included in Conformance Report

tarix	26.06.2016
ölçüsü	76.5 Kb.

Schema Conformance Report

Flow Documentation Status and Contact Information

Flow Name: AQS (federal) and AQDE (Air Quality Data Exchange; State to State)

Schemas/Versions included in Conformance Report: AQDE XML Schema and AQS Submission Schema (same schema with two names based on user community)

Conformance Report Author: Nick Mangus

Contact Information: mangus.nick@epa.gov, 919-541-5549

Schema Developer: AQDE Challenge Grant Team, Enfotech, US EPA OAR, LMIT

Contact Information: mangus.nick@epa.gov, 919-541-5549

Flow Owner or Other Point of Contact for Flow Documentation Package: Nick Mangus

Contact Information: mangus.nick@epa.gov, 919-541-5549

Date Flow Documentation Package Submitted: AQS Submission, complete package.

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

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:

XMLSpy

[ 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

Explanation of DRC Violations Identified:

DRC Rule ID	Schema Filenames	Explanation
[SD3-9] Data-centric schemas MUST NOT use attributes in place of data elements	EN_AQS_AirQualitySubmission_v2.0.xsd	“Version” is not a data element but is instead schema metadata. It is used to facilitate correct processing of submitted transactions by the AQS Load system.

Shared Schema Components Conformance

High Level of SSC Integration:

Element Name	Schema Path
Measure (SC Data Type)	There are 16 uses of Measure in this schema. One example is: AirQualitySubmission / FacilitySiteList / OpenPathMonitoringLocation / BeamHeightMeasure

Please note, the high level of incorporation of the Measure shared component throughout the schema caused significant development costs (>>$10k) to the AQS system. This just information for the NTG regarding potential unanticipated costs of data standards.

Medium Level of SSC Integration:
None

Element Name	Complex SSC Element or Data Type	Derived By

Low Level of SSC Integration:

Element Name	Simple SSC Element or Data Type
AddressPostalCode	AddressPostalCode
AgencyCode	AgencyCode
CountyCode	CountyCode
LatitudeMeasure	LatitudeMeasure
LongitudeMeasure	LongitudeMeasure
LocationAddressText	LocationAddressText
MeasureUnitCode*	MeasureUnitCode
MeasureValue*	MeasureValue
MethodIdentifierCode	MethodIdentifierCode
StateCode	StateCode
SubstanceIdentifier	SubstanceIdentifier
TribalCode	TribalCode

Modifications were made to two of the types:

AddressPostalCode adds restrictions to limit it to digits.

StateCode limited to 2 characters.

* Note, simple types also used separately from highly integrated type.

Explanation for Not Integrating Available SSCs:
There are a few simple SSCs that were not fully integrated into this schema at the low level. In all cases, we thought the components were not the best fit for the information in the schema.

Schema Name	Element or Type	SSC Element or Type	Explanation
AQS	SampleCollectionStartDate	DataCollectionDate	The DataCollectionDate is not sufficiently descriptive to capture the information required by AQS, mostly since air samplers can run for multiple days.
AQS	HorizontalReferenceDatumName VerticalDatumIdentifier	GeographicalReferenceDatumName	Using GeographicalReferenceDatumName would have required the creation of enclosing elements to distinguish horizontal from vertical datums

Candidates for New SSCs:
None

Schema Name	Element or Type Name	CRM data block

Recommendations (optional)

W3C’s XSV Tool Output

Schema validating with XSV 2.10-1 of 2005/04/22 13:10:49

Target: http://www.lmit-rtp.com/~jhall/AQDE2_Work/EN_AQS_AirQualitySubmission_v2.0.xsd
   (Real name: http://www.lmit-rtp.com/~jhall/AQDE2_Work/EN_AQS_AirQualitySubmission_v2.0.xsd
    Last Modified: Thu, 16 Nov 2006 21:51:22 GMT
    Server: Apache/2.2.0 (Linux/SUSE))
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