Initial meeting discussion

Some points to take into account for the meeting

This first task will focus only on the implementation of a schema to represent the “network” level of StationXML and the outer envelope to contain responses.
FDSN SourceIDs are the stream identifier for networks, stations, and channels. No fields for SEED codes.
- Consistently use transitional mapping codes for temporary networks so they are globally unique.
Try to discuss and propose ways to reference an external entity with information of the “station” level. This could be used in some cases instead of encapsulation to connect different pieces of information.
There should be some sort of support regarding the “version” of the metadata document. Not many data centres support this currently, but we need to be prepared.
- miniSEED v3 has a “publication version”
Conversion from StationXML to JSON should be “mostly” lossless
Specification of the schemas using JSON Schema
Format validation cannot cover all validation needs of the content
Open coordination of the discussion and prototypes should be tracked in a repository under the FDSN’s GitHub organization
Do not attempt to create a metadata standard extending to (sub) fields that require significantly different information, e.g. DAS. The primary objective is a functional replacement of StationXML with some extensions for the use cases of StationXML.

We will set up the next meeting in around 4 weeks at the same time (a doodle will be sent to choose a day).

Focus points, initial issues:

Provide feedback