1) Station::CreationDate should be optional. This value denotes when a station/site was
originally installed and is distinct from the startDate attribute used to note the station
epoch start. There is no need for it to be required, it cannot be retained in conversions
and many data centers do not have this information forcing them to set it to, e.g., the startDate.

2) Use xs:double type instead of xs:decimal type for ApproximationLowerBound, ApproximationUpperBound
and MaximumError values (in PolynomialType::ApproximationType). For consistency, xs:double is used
for most other floating point values in the schema. Also xs:double allows values in scientific notation.

3) Change startDate attribute (for Network, Station and Channel) to be optional. The issue is that
startDate for Network is not commonly known or contained in SEED, forcing the insertion of potentially
bad dates.

4) Remove redundancy of FrequencyType and SampleRateType, they are effectively the same except units
described as HERTZ versus SAMPLES/S. SampleRateType can be replaced with FrequencyType. If that is
not desired the DecimationType::InputSampleRate should be changed to SampleRateType for consistency.

5) Include data availability elements described in the fdsn-station+availability-1.0.xsd extension schema
as optional elements of the main schema.

6) Add "updated" attribute to important response elements (PolesZeros, Coefficients, etc.) and other
important elements (Latitude, Longitude, Azimuth, etc.) to track when these details were last changed.
Required or optional? Required means no backwards compatibility.

7) Add an optional ChannelGroup element to explicitly define groups of channels that should be considered
a "set", i.e. from the same instrument. This would allowing explicit grouping of BHE, BHN & BHZ and other
combinations like BH1, BH2 & BHZ.

Dear Reinoud and all,
FDSN WS station is implemented at RESIF datacentre, as reported in the
slide joinded. We also plan to implement IRIS 'output=text' extension,
as well IRIS 'dataAvailability' extension before the end of 2013.

As part as our reflexion on station.xml within RESIF, we would like to
propose some extensions linked to OBS needs, plus some addtionnal
features for the level Network. We put a short summary of those possible
extension in the joined document.

Best reagrds,
Catherine Péquegnat, for the RESIF 'station.xml' working group.

1) Station::CreationDate should be optional. This value denotes when a station/site was
originally installed and is distinct from the startDate attribute used to note the station
epoch start. There is no need for it to be required, it cannot be retained in conversions
and many data centers do not have this information forcing them to set it to, e.g., the startDate.

2) Use xs:double type instead of xs:decimal type for ApproximationLowerBound, ApproximationUpperBound
and MaximumError values (in PolynomialType::ApproximationType). For consistency, xs:double is used
for most other floating point values in the schema. Also xs:double allows values in scientific notation.

3) Change startDate attribute (for Network, Station and Channel) to be optional. The issue is that
startDate for Network is not commonly known or contained in SEED, forcing the insertion of potentially
bad dates.

4) Remove redundancy of FrequencyType and SampleRateType, they are effectively the same except units
described as HERTZ versus SAMPLES/S. SampleRateType can be replaced with FrequencyType. If that is
not desired the DecimationType::InputSampleRate should be changed to SampleRateType for consistency.

5) Include data availability elements described in the fdsn-station+availability-1.0.xsd extension schema
as optional elements of the main schema.

6) Add "updated" attribute to important response elements (PolesZeros, Coefficients, etc.) and other
important elements (Latitude, Longitude, Azimuth, etc.) to track when these details were last changed.
Required or optional? Required means no backwards compatibility.

7) Add an optional ChannelGroup element to explicitly define groups of channels that should be considered
a "set", i.e. from the same instrument. This would allowing explicit grouping of BHE, BHN & BHZ and other
combinations like BH1, BH2 & BHZ.

Dear Reinoud and all,
FDSN WS station is implemented at RESIF datacentre, as reported in the
slide joinded. We also plan to implement IRIS 'output=text' extension,
as well IRIS 'dataAvailability' extension before the end of 2013.

As part as our reflexion on station.xml within RESIF, we would like to
propose some extensions linked to OBS needs, plus some addtionnal
features for the level Network. We put a short summary of those possible
extension in the joined document.

Best reagrds,
Catherine Péquegnat, for the RESIF 'station.xml' working group.

1) Station::CreationDate should be optional. This value denotes when a station/site was
originally installed and is distinct from the startDate attribute used to note the station
epoch start. There is no need for it to be required, it cannot be retained in conversions
and many data centers do not have this information forcing them to set it to, e.g., the startDate.

2) Use xs:double type instead of xs:decimal type for ApproximationLowerBound, ApproximationUpperBound
and MaximumError values (in PolynomialType::ApproximationType). For consistency, xs:double is used
for most other floating point values in the schema. Also xs:double allows values in scientific notation.

3) Change startDate attribute (for Network, Station and Channel) to be optional. The issue is that
startDate for Network is not commonly known or contained in SEED, forcing the insertion of potentially
bad dates.

4) Remove redundancy of FrequencyType and SampleRateType, they are effectively the same except units
described as HERTZ versus SAMPLES/S. SampleRateType can be replaced with FrequencyType. If that is
not desired the DecimationType::InputSampleRate should be changed to SampleRateType for consistency.

5) Include data availability elements described in the fdsn-station+availability-1.0.xsd extension schema
as optional elements of the main schema.

6) Add "updated" attribute to important response elements (PolesZeros, Coefficients, etc.) and other
important elements (Latitude, Longitude, Azimuth, etc.) to track when these details were last changed.
Required or optional? Required means no backwards compatibility.

7) Add an optional ChannelGroup element to explicitly define groups of channels that should be considered
a "set", i.e. from the same instrument. This would allowing explicit grouping of BHE, BHN & BHZ and other
combinations like BH1, BH2 & BHZ.

FYI I will be at the FDSN WG-II meeting in Göteborg, so I will be
available for any further information on RESIF and RESIF data
distribution. I will make sure that any technical questions make it back
to the RESIF team and in particular Catherine who is coordinating the
activities of the RESIF station.xml working group.

We would be happy to receive any comments to the documents before the
meeting (mail to Catherine and myself)

Dear Reinoud and all,
FDSN WS station is implemented at RESIF datacentre, as reported in the
slide joinded. We also plan to implement IRIS 'output=text' extension,
as well IRIS 'dataAvailability' extension before the end of 2013.

As part as our reflexion on station.xml within RESIF, we would like to
propose some extensions linked to OBS needs, plus some addtionnal
features for the level Network. We put a short summary of those possible
extension in the joined document.

Best reagrds,
Catherine Péquegnat, for the RESIF 'station.xml' working group.

1) Station::CreationDate should be optional. This value denotes when a station/site was
originally installed and is distinct from the startDate attribute used to note the station
epoch start. There is no need for it to be required, it cannot be retained in conversions
and many data centers do not have this information forcing them to set it to, e.g., the startDate.

2) Use xs:double type instead of xs:decimal type for ApproximationLowerBound, ApproximationUpperBound
and MaximumError values (in PolynomialType::ApproximationType). For consistency, xs:double is used
for most other floating point values in the schema. Also xs:double allows values in scientific notation.

3) Change startDate attribute (for Network, Station and Channel) to be optional. The issue is that
startDate for Network is not commonly known or contained in SEED, forcing the insertion of potentially
bad dates.

4) Remove redundancy of FrequencyType and SampleRateType, they are effectively the same except units
described as HERTZ versus SAMPLES/S. SampleRateType can be replaced with FrequencyType. If that is
not desired the DecimationType::InputSampleRate should be changed to SampleRateType for consistency.

5) Include data availability elements described in the fdsn-station+availability-1.0.xsd extension schema
as optional elements of the main schema.

6) Add "updated" attribute to important response elements (PolesZeros, Coefficients, etc.) and other
important elements (Latitude, Longitude, Azimuth, etc.) to track when these details were last changed.
Required or optional? Required means no backwards compatibility.

7) Add an optional ChannelGroup element to explicitly define groups of channels that should be considered
a "set", i.e. from the same instrument. This would allowing explicit grouping of BHE, BHN & BHZ and other
combinations like BH1, BH2 & BHZ.

FYI I will be at the FDSN WG-II meeting in Göteborg, so I will be
available for any further information on RESIF and RESIF data
distribution. I will make sure that any technical questions make it back
to the RESIF team and in particular Catherine who is coordinating the
activities of the RESIF station.xml working group.

We would be happy to receive any comments to the documents before the
meeting (mail to Catherine and myself)

please find a request for additional elements in FDSN Station XML
provided by RESIF. I will insert this item in the agenda

As part as our reflexion on station.xml within RESIF, we would like to
propose some extensions linked to OBS needs, plus some addtionnal
features for the level Network. We put a short summary of those possible
extension in the joined document.

I expect those who have proposed changes or additions to the schema
to motivate these during the meeting.