Dear all,
I’m writing to propose adding i18n support for Contact fields in GetCapabilities Response of WMS 1.1, 1.3, WFS 2.0 and WCS 2.0 as already done for tile and abstract in LayerGroups, Layers and Services.
Along with the modification of the ContactPanel UI component and the Capabilities generators of involved services, the addition will imply the extension of the ContactInfo interface due the addition of getters and setters for InternationalString type attributes
.
I’m wondering if it is possible and preferable to integrate and modify the existing GSIP for title and abstract https://github.com/geoserver/geoserver/wiki/GSIP-203, or if a separate GSIP is needed.
···
Regards,
Marco Volpini
==
GeoServer Professional Services from the experts!
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
Adding more details to the existing proposal should be fine, just ask for review here when the new section is added.
I had some questions from the geoserver meetings where this proposal was discussed:
How the internationalization works, specifically how you determine the primary lanaguage of the generated GetCapabilities xml document. It could be quite tricky when combining a single document with information from lots of layers. I expected an additional field, or some logic to determine primary language.
Does the root layer title and abstract also need to be updated for Internationalization?
When capabilities are encoded if no specific language is requested then the one set as default will be used.
If specific language is requested: if no internationalContent for any configurable resource or services has been set, geoserver will return an error message; if there is at least one international content defined GeoServer will encode the capability response, but if some resource misses i18n content for mandatory elements (like ) an error message will be put as the text content of the element.
···
Regards,
Marco Volpini
==
GeoServer Professional Services from the experts!
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
The one thing missing from the proposal, and documentation is the handling of root layer title and abstract. Perhaps it is just obvious that all titles and abstracts are being handled…
Thanks for your point. Yes, it was implicit that they are handled too. Anyway I’ll make this explicit by adding it to the documentation, I’ve also amended the gsip to add them.
···
Regards,
Marco Volpini
==
GeoServer Professional Services from the experts!
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.