Dear Andrea, your proposal is definitely amazing! My 2c.: - The usage of these fields looks strictly connected to the inspire specifications (chap. 3.2.6) so what about including it as module? Maybe an i18n or an improvement to the inspire one. - about metadata management i see your concern about backports and backward compatibility and I would follow your way. In addition I think that to keep things simple we can have an optional xml node (with the appropriate namespace) summarizing the entire i18n config (one in each StoreConfig, LayerConfig, ...):
... <NAMESPACE:i18n> <N: MultilangTitle /> <N: MultilangDesc /> ... </N:i18n> I’ve just read your post and it’s so interesting, so I decided to reply w/ my iphone. apologize if it’s not so clear. Feel free to comment, ask for clarifications or simply junk it. C. Ref https://inspire.ec.europa.eu/documents/Network_Services/Technical_Guidance_View_Services_v2.12.pdf Il giorno ven 10 apr 2020 alle 19:32 Andrea Aime < andrea.a...@geo-solutions.it> ha scritto: > Hi, > I'm looking into ways for internationalizing layer titles and abstracts. > Right now title and abstract are String > objects, appear as flat properties in the REST API and in configuration > storage, and have lots of call > points in the code (74 for title, 49 for abstract, including both Layer > and Resource property exposure). > > It would be tempting to turn them into InternationalizedString (or an > analogous class), but the API breakage > would be significant, and would likely prevent a backport (something that > might be a deal breaker funding wise). > REST wise it would also make existing clients fail, if they stumble into > an internationalized version of title and abstract > (which I supposed would show up inside the same tags, nested <value > lang="xy">title in lang</value> elements). > > I was wondering about doing something that would be more transparent to > users. How about a: > > - defaultLang property, indicating the language for the existing title > and abstract > - alternateTitles, a InternationalizedString > - alternateAbstract, a InternationalizedString > > This way they'd be new fields, could have defaults, and existing > applications that are not aware of them can blissfully > ignore them most of the time. > > The GUI would probably have a checkbox to enable internationalization, and > in that case, it would show a table based > editor with languages and values. > > How does this sound? > > Cheers > Andrea > > == > > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf > Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa > <https://www.google.com/maps/search/Via+di+Montramito+3%2FA%0D%0A55054++Massarosa?entry=gmail&source=g> > (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 > http://www.geo-solutions.it http://twitter.com/geosolutions_it > ------------------------------------------------------- *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.* > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > -- Mr. Carlo Cancellieri *skype*: ccancellieri *Twitter*: @cancellieric *LinkedIn*: http://it.linkedin.com/in/ccancellieri/
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
