As Chair of the WG2, I'm writing you regarding the evaluation of the
proposal submitted by Chad Trabant about "FDSN Source Identifier scheme".
First of all, I want to thank a lot to the three members of the Review
Team, Philip Crotwell, Wayne Crawford, and Florian Fuchs, who have
invested so much energy on this.
In the last couple of months, making use for the first time of the
"Framework for adoption of features", an Evaluation Review team was
formed to evaluate the potential implementation aspects and impact, as
well as the resources (e.g. prototype, scripts) included in the
proposal. The Review Team has already sent a recommendation (see PDF
attached) and the decision was that
"The review committee recommends approval of the specification as revised."
Let me remind you that this proposal went through an open discussion in
the first semester of 2019 in order to clarify objectives and receive
feedback from the members. After that, it was made available again for
comments on May 2020. During both discussion phases the proposal was
well received by the community and, despite that the discussion was kept
open for some time, it was good to see that most of the opinions
considered it a proper approach to deal with the limitations of the
current naming scheme.
I will open now a window of *2 weeks* for comments and discussion
considering the positive decision from the Evaluation Review Team. After
that, we will vote following the usual rules:
Voting rules (consistent with current FDSN Terms of Reference):
1 vote per FDSN member (i.e. each network or datacentre)
Votes are agreed with at least 2/3 majority. Quorum for any decision is 5 FDSN member votes.
Please, keep in mind that it is important to express your constructive
opinion in cases in which standards are being defined. Also taking into
account that the final aim is to find solutions for issues that the
community needs to solve in the near future.
General discussion is expected to be held on this mailing list. Really
detailed and technical comments can be posted in the Issue Tracker of
the repository. In this way, we can keep track of the technical
discussion and (un)solved issues.