The example validates with the 0.9 schema and represents a nominal usage of the
proposed format based on SEED 2.4 data. It does not contain an example of
every possible element because there are many optional elements and some elements
that will only be used in special cases.

Please use it in your review process and inform the group in case you have remarks
or suggestions, or simply support this proposal. Please provide feedback before
Nov 24 or it is assumed you agree :-)

The example validates with the 0.9 schema and represents a nominal usage of the
proposed format based on SEED 2.4 data. It does not contain an example of
every possible element because there are many optional elements and some elements
that will only be used in special cases.

Please use it in your review process and inform the group in case you have remarks
or suggestions, or simply support this proposal. Please provide feedback before
Nov 24 or it is assumed you agree :-)

During development of software using this schema we have identified some minor issues listed below. Regarding one of the issues I would like to solicit feedback from the working group.

The CreationDate and TerminationDate elements under the Channel element refer to "station" but should be "channel", this is a simple typo and can be easily fixed. However I wonder if we need these elements at all. These are not the Start and End dates that define an epoch, only data-producer notations of a lifetime for a channel. There are already CreationDate and TerminationDate elements at the Station level. So the question is are these needed at the Channel level also?

Other small issues to be fixed in 1.0:

* Misspelled SECOND in the enumeration value of "LAPLACE (RADIANS/SECCOND)"

* maxOccurs should be removed (defaulting to 1) instead of maxOccurs="unbounded" for the FIR element in ResponseStageType:
<xs:element name="FIR" type="fsx:FIRType" minOccurs="0" maxOccurs="unbounded"/>

And some minor spelling mistakes in the comments will be fixed.

If anyone else has any feedback that should be included in the 1.0 schema please let us know before the 24th.

The example validates with the 0.9 schema and represents a nominal usage of the
proposed format based on SEED 2.4 data. It does not contain an example of
every possible element because there are many optional elements and some elements
that will only be used in special cases.

Please use it in your review process and inform the group in case you have remarks
or suggestions, or simply support this proposal. Please provide feedback before
Nov 24 or it is assumed you agree :-)

During development of software using this schema we have identified some minor issues listed below. Regarding one of the issues I would like to solicit feedback from the working group.

The CreationDate and TerminationDate elements under the Channel element refer to "station" but should be "channel", this is a simple typo and can be easily fixed. However I wonder if we need these elements at all. These are not the Start and End dates that define an epoch, only data-producer notations of a lifetime for a channel. There are already CreationDate and TerminationDate elements at the Station level. So the question is are these needed at the Channel level also?

Other small issues to be fixed in 1.0:

* Misspelled SECOND in the enumeration value of "LAPLACE (RADIANS/SECCOND)"

* maxOccurs should be removed (defaulting to 1) instead of maxOccurs="unbounded" for the FIR element in ResponseStageType:
<xs:element name="FIR" type="fsx:FIRType" minOccurs="0" maxOccurs="unbounded"/>

And some minor spelling mistakes in the comments will be fixed.

If anyone else has any feedback that should be included in the 1.0 schema please let us know before the 24th.

The example validates with the 0.9 schema and represents a nominal usage of the
proposed format based on SEED 2.4 data. It does not contain an example of
every possible element because there are many optional elements and some elements
that will only be used in special cases.

Please use it in your review process and inform the group in case you have remarks
or suggestions, or simply support this proposal. Please provide feedback before
Nov 24 or it is assumed you agree :-)

please consider the suggested additions to the original proposed schema
and share your comments with the working group before Dec 7. In case
there are no other suggestions or concerns by then I consider the original
schema plus the new additions as being accepted by this working group.

During development of software using this schema we have identified some minor issues listed below. Regarding one of the issues I would like to solicit feedback from the working group.

The CreationDate and TerminationDate elements under the Channel element refer to "station" but should be "channel", this is a simple typo and can be easily fixed. However I wonder if we need these elements at all. These are not the Start and End dates that define an epoch, only data-producer notations of a lifetime for a channel. There are already CreationDate and TerminationDate elements at the Station level. So the question is are these needed at the Channel level also?

Other small issues to be fixed in 1.0:

* Misspelled SECOND in the enumeration value of "LAPLACE (RADIANS/SECCOND)"

* maxOccurs should be removed (defaulting to 1) instead of maxOccurs="unbounded" for the FIR element in ResponseStageType:
<xs:element name="FIR" type="fsx:FIRType" minOccurs="0" maxOccurs="unbounded"/>

And some minor spelling mistakes in the comments will be fixed.

If anyone else has any feedback that should be included in the 1.0 schema please let us know before the 24th.

The example validates with the 0.9 schema and represents a nominal usage of the
proposed format based on SEED 2.4 data. It does not contain an example of
every possible element because there are many optional elements and some elements
that will only be used in special cases.

Please use it in your review process and inform the group in case you have remarks
or suggestions, or simply support this proposal. Please provide feedback before
Nov 24 or it is assumed you agree :-)

please consider the suggested additions to the original proposed schema
and share your comments with the working group before Dec 7. In case
there are no other suggestions or concerns by then I consider the original
schema plus the new additions as being accepted by this working group.

During development of software using this schema we have identified some minor issues listed below. Regarding one of the issues I would like to solicit feedback from the working group.

The CreationDate and TerminationDate elements under the Channel element refer to "station" but should be "channel", this is a simple typo and can be easily fixed. However I wonder if we need these elements at all. These are not the Start and End dates that define an epoch, only data-producer notations of a lifetime for a channel. There are already CreationDate and TerminationDate elements at the Station level. So the question is are these needed at the Channel level also?

Other small issues to be fixed in 1.0:

* Misspelled SECOND in the enumeration value of "LAPLACE (RADIANS/SECCOND)"

* maxOccurs should be removed (defaulting to 1) instead of maxOccurs="unbounded" for the FIR element in ResponseStageType:
<xs:element name="FIR" type="fsx:FIRType" minOccurs="0" maxOccurs="unbounded"/>

And some minor spelling mistakes in the comments will be fixed.

If anyone else has any feedback that should be included in the 1.0 schema please let us know before the 24th.

The example validates with the 0.9 schema and represents a nominal usage of the
proposed format based on SEED 2.4 data. It does not contain an example of
every possible element because there are many optional elements and some elements
that will only be used in special cases.

Please use it in your review process and inform the group in case you have remarks
or suggestions, or simply support this proposal. Please provide feedback before
Nov 24 or it is assumed you agree :-)

Although I have not been directly involved in IRIS' development, I strongly support adopting this proposal. Establishing a convention for the use of XML is key to meeting evolving needs for handling seismic data.

please consider the suggested additions to the original proposed schema
and share your comments with the working group before Dec 7. In case
there are no other suggestions or concerns by then I consider the original
schema plus the new additions as being accepted by this working group.

During development of software using this schema we have identified some minor issues listed below. Regarding one of the issues I would like to solicit feedback from the working group.

The CreationDate and TerminationDate elements under the Channel element refer to "station" but should be "channel", this is a simple typo and can be easily fixed. However I wonder if we need these elements at all. These are not the Start and End dates that define an epoch, only data-producer notations of a lifetime for a channel. There are already CreationDate and TerminationDate elements at the Station level. So the question is are these needed at the Channel level also?

Other small issues to be fixed in 1.0:

* Misspelled SECOND in the enumeration value of "LAPLACE (RADIANS/SECCOND)"

* maxOccurs should be removed (defaulting to 1) instead of maxOccurs="unbounded" for the FIR element in ResponseStageType:
<xs:element name="FIR" type="fsx:FIRType" minOccurs="0" maxOccurs="unbounded"/>

And some minor spelling mistakes in the comments will be fixed.

If anyone else has any feedback that should be included in the 1.0 schema please let us know before the 24th.

The example validates with the 0.9 schema and represents a nominal usage of the
proposed format based on SEED 2.4 data. It does not contain an example of
every possible element because there are many optional elements and some elements
that will only be used in special cases.

Please use it in your review process and inform the group in case you have remarks
or suggestions, or simply support this proposal. Please provide feedback before
Nov 24 or it is assumed you agree :-)