Requirement: Combine and drop unused / underspecified bit flags

[krischer]

Simplification of MiniSEED2: Combine and drop unused / underspecified bit flags.

[crotwell]

Provide standard mapping for any that are deemed important to the addition/optional header structure.

[krischer]

Summary

(Please let me know if I missed a point or misunderstood something)

Please vote on:

1. Should unused/underspecified bit-flags be dropped? (Yes/No)

[kaestli]

do we need to agree on what is "widely unused" or "underspecified"?
imho, i have seen little recent usage of everything except the a) time correction flag, b) the leap second flags and c) the the clock lock flag (however for a and b better solutions are available),
and i think everything is underspecified except the time correction and the leap second flags (thus, the clock lock flag is actually underspecified too)

[krischer]

I'd say no as I think most of us agree on which fields are actually used. Furthermore it is a detail that can be figured out in the final stage with a fully specified format.

[crotwell]

yes

[chad-earthscope]

1. Yes.

The ones I would like to drop are:

• I/O flags, Bit 0: station volume parity error possibly present
• I/O flags, Bit 1: long record read
• I/O flags, Bit 2: short record read
• I/O flags, Bit 3: start of time series
• I/O flags, Bit 4: end of time series

But to be honest all of them can be retained if we have optional header capability. With some marked as deprecated if we wish to discourage their use. The ones above are just the most worthless of the flags and we could drop them to ease the coding to the new standard a bit.

[kaestli]

yes

[ozym]

1. Yes

[ketchum-usgs]

Yes, Chad's list is a good starting list. I suspect that "clock locked" is also useless and that this should be communicated with a better value.

[claudiodsf]

Yes

[ihenson-bsl]

1. Yes

[ValleeMartin]

1. Yes

[JoseAntonioJara]

1. Yes