Issues
- Add other_contributors to TRANSLATION_DETAILSSPECBASE-23Resolved issue: SPECBASE-23Thomas Beale
- Move RM common.resource spec to BASE resource spec.SPECBASE-13Resolved issue: SPECBASE-13Thomas Beale
- Specify language attributes of `RESOURCE_DESCRIPTION_ITEM` and `TRANSLATION_DETAILS` as being coded by a subset of RFC 5646 language tag standard.SPECBASE-6Sebastian Iancu
Add other_contributors to TRANSLATION_DETAILS
Description
CR fixes the problem in
Details
Details
Activity
Diego BoscaMay 26, 2023 at 9:19 AM
I don’t see problems with option 1 for us
Sebastian GardeMay 26, 2023 at 8:55 AM
Thank you…I also agree with option 1, let’s do this - if is also happy with the required conversion algorithm?
Thomas BealeMay 26, 2023 at 8:49 AM
Agree on option #1 - it’s how we’ve done this before.
Rong ChenMay 26, 2023 at 1:45 AM
Option 1 seems better to me, since we have similar workaround before and it doesn’t require ADL 1.4 specs change.
The impact of this change (either option) on our tools, namely CKM is minimal.
Ian McNicollMay 25, 2023 at 8:33 AM
So to summarise, we appear to have 2 options both involving a little pain.
1. Use the ADL1.4 compatible workaround, similar to what we did for namespace metadataother_details = < ["other_contributors"] = <"Translator 1, Org1, Norway Translator 2, Org2, Norway Translator 3, Org3, Norway"> >
which requires no update to the ADL1.4 spec but will require conversion to ADL2 (already implemented for namespaces)
2. Update the ADL1.4 spec to use the ADL2 approach, which requires a spec change and parser change but no conversion.
In both cases tooling will need to support the changes.
Can we get quick consensus on the favoured approach as it is a pressing need in CKM now?
See