You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following base URI pattern is to be used at each data center implementing FDSN services: <site>/fdsnws/<service>/<majorversion>/
But that limits datacenters to a single instance of each type of web service, and this requirement is already an issue, for example IRIS with the PH5 repository at: http://service.iris.edu/ph5ws/dataselect/1
So, maybe should relax this requirement by saying a compliant service url should be <site>/<repository>/<service>/<majorversion>/
where <repository> can be defined by the datacenter if needed, but the primary url for a fdsn web service with a datacenter should have repository be 'fdsnws'.
The text was updated successfully, but these errors were encountered:
I support a slight relaxation of this pattern as well. I've heard multiple folks express the opinion that that the consistent path pattern was very valuable, a requirement to use 'fdsnws' for the primary repository strikes a good balance.
Current (1.2) spec says:
The following base URI pattern is to be used at each data center implementing FDSN services: <site>/fdsnws/<service>/<majorversion>/
But that limits datacenters to a single instance of each type of web service, and this requirement is already an issue, for example IRIS with the PH5 repository at:
http://service.iris.edu/ph5ws/dataselect/1
So, maybe should relax this requirement by saying a compliant service url should be
<site>/<repository>/<service>/<majorversion>/
where
<repository>
can be defined by the datacenter if needed, but the primary url for a fdsn web service with a datacenter should have repository be 'fdsnws'.The text was updated successfully, but these errors were encountered: