Hi Dan
You are correct - the TMF Open API team is considering what the best approach to this is - we have an open JIRA issue for national language handling and it has been discussed in recent team meetings. Specifically regarding the catalog APIs (product, service, resource, entity) there will be a need to allow authoring for fields such as name and descriptions for all the relevant entities (not just product spec).
When we have more news it will no doubt be reflected in updated specifications and guidelines.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Dec 17, 2019 03:46
From: Dan d'Albuquerque
Subject: Internationalisation of TMF OpenAPI
Hi All.
Currently there appears to be no support for Internationalisation within OpenAPI v2/3.0. I can see that there has been consideration to support multiple languages, e.g. within description fields, using the concept of overlays or a mechanism using JSON-LD langauge maps.
I am imagining that there would especially be a need within TMF620 Product Catalog Management to provide multiple languages for both the name and description fields within the ProductSpecification resource.
Any suggestions?
Thanks
Dan.
------------------------------
Dan d'Albuquerque
------------------------------