network name and description

[WayneCrawford]

On the FDSN.org site, both a "Network name" and "Description" are specified for a given FDSN code. But, in StationXML, only "description" is allowed. More confusingly, the StationXML "description" often corresponds to the "Network name" and not the "Description" (see example screenshots below, taken from the fdsn.org website and the https://www.fdsn.org/webservices/fdsnws-station-1.1.pdf example.

I think that either a "name" field should be added to StationXML , or the fdsn.org site should rename "Network name" to "Description" (and "Decription" to "Long Description"?)

[crotwell]

Seems reasonable.

Currently Station has a description, but also a name inside Site. Perhaps adding Site to Network would also be useful, where the "site" in this case means the whole geographical area for the network? That would allow the use of other tags like country that may be useful for national networks.

In the meantime, perhaps put the name into description and the longer description into a comment with subject being set to "long description" or something similar.

Alternatively, setting website in the network operator at least allows people to find more description if desired.

[megies]

Everybody please keep in mind that changes to the standard have a lot of downstream implications (e.g. to software tools supporting said standard) that can force tough decisions like causing backwards incompatible changes that affect thousands of users writing code.
On the other hand text fields on websites that are designed for humans reading them and not necessarily for automated applications can easily shuffle around field names without disruptions.

Adding new fields/tags in the standard isn't the worst for downstream applications but making changes to existing fields, their meaning and semantics creates problems for maintainers and users.
I guess what I'm trying to say is, we should try and keep standard changes to a bare minimum whenever they can't be avoided but in cases like this I'd massively argue it's better to adjust the webpage to use the existing standard first of all (and "Network name" simply isn't part of FDSN's own standard so it should get adjusted/fixed on the webpage IMO).

[crotwell]

Yes, but I suspect the chances of a stationxml revision in the next decade are really small. So this is more about remembering things that might need to be updated if/when a revision happens. The FDSN rarely moves very fast! :)

Use of <Comment> seems the best for holding longer descriptions for foreseeable future.

[petrrr]

Hi just a comment on this issue from experience.

This misalignment in naming indeed creates quite some confusion with users. In particular we occasionally get StationXML files which report the whole "Description" (as named in the portal) into the <Description> element, which is usually used more as a long name.

I would not consider a <Side> element for the Network level, I do not really think if fits well on that level. If you want to consider changes to the StationXML, maybe we could introduce an simple <Name> element of string type.

On the other hand, I understand the considerations by @crotwell and @megies, regarding slow adoption and the down stream impact.

Therefore, my suggestion would be to honour practice, where <Descrition> is usually used as a "extended name", and change the representation on the FDSN web registry portal accordingly.

Specifically i suggest to rename "Description" to "Abstract", and change change the field "Network name" to "Network name (description).

In this occasion, I would also suggest to present the "Acronym" as an separate and indipendent field, rather then presenting the Acronym as part of the Name/Description.

But maybe this would should then go to a specific repository for the portal?

[WayneCrawford]

I like changing the webpage fields, with the new names clearly related to their corresponding StationXML elements. So I would be in favor of renaming "Name" to "Description" on the webpage. For the current "Description", would you all like/prefer one of the below (each one based on a previous response)?

Webpage Current	Webpage New	StationXML element
Description	Comment	<Network><Comment>
Description	Abstract	<Network><Comment subject="Abstract">
Description	Long Description	<Network><Comment subject="Long Description">