In reality of e.g. WP8, there is a many-to-many relationship between web services and data sets:
Web services are run by institutions to distribute several datasets (e.g., data from an experiment or a seismic network).
However, datasets (e.g.: waveform data of the Z3 network) may be distributed over several institutions, and (mutually exclusive or overlapping) parts of them may be distributed by multiple web services run by multiple institutions.
by requesting a 1:m:n relationship between data set, distribution and web service in each ttl file provided from an agency, a artificial multiplication of datasets is introduced, and the information is lost that 1 effective dataset is (partly) distributed by many services
In reality of e.g. WP8, there is a many-to-many relationship between web services and data sets:
Web services are run by institutions to distribute several datasets (e.g., data from an experiment or a seismic network). However, datasets (e.g.: waveform data of the Z3 network) may be distributed over several institutions, and (mutually exclusive or overlapping) parts of them may be distributed by multiple web services run by multiple institutions.
by requesting a 1:m:n relationship between data set, distribution and web service in each ttl file provided from an agency, a artificial multiplication of datasets is introduced, and the information is lost that 1 effective dataset is (partly) distributed by many services