Specification of packet header for INFO responses is ambiguous

FDSN / SeedLink

https://docs.fdsn.org/projects/seedlink/

Creative Commons Zero v1.0 Universal

1 stars 1 forks source link

Specification of packet header for INFO responses is ambiguous #48

Open chad-earthscope opened 2 months ago

chad-earthscope commented 2 months ago

The current specification does not appear to specify what the sequence number and station ID fields would be for responses to INFO packets.

One could image the sequence number is 0 and the station ID is omitted or some fixed value. Either way clarity would be good for completeness, even if the values are left to the server.

chad-earthscope commented 2 months ago

On the point of what a station ID would be for such transient packets, it might be nice to have a fixed value here instead of empty to help downstream processors that are potentially using the value to print diagnostics, organize/save data, etc.

Perhaps a fixed value of SLINFO?

crotwell commented 2 months ago

Maybe an alternative is to have the station ID for info packets be the INFO command item, so one of: ID, FORMATS, CAPABILITIES, STATIONS, STREAMS, CONNECTIONS? That at least gives something minimally useful.

crotwell commented 2 months ago

Also maybe ERROR for station id in instance of J E error json response to INFO?