search

FDSN / SeedLink

https://docs.fdsn.org/projects/seedlink/
Creative Commons Zero v1.0 Universal
1 stars 1 forks source link

Station and Stream ID selection #20

Closed djeastonca closed 1 year ago

djeastonca commented 1 year ago

Was it considered to use regular expressions for station and stream ID selection to provide additional flexibility? It is arguably overkill for SeedLink use cases, but, on the other hand, anyone designing such an expression has to be familiar with the basics of regular expressions anyway in order to understand what the SeedLink documentation means by "...the pattern is anchored to the beginning and end of string". Everyone now has ready access to AI-based regular expression generation and it would allow server implementations to benefit from existing regex libraries and reduce custom code.

crotwell commented 1 year ago

Personally I think regular expressions would be better, but I think the glob style patterns are for backwards compatibility, so best to keep them. Regular expressions could be supported via an optional capability/command I suppose, but not sure if it is worth adding it to the specification.

andres-h commented 1 year ago

Feedback from proposal team

Regular expressions would add complexity and potential security risk that would be hard to justify.