>This looks reasonable to me.
> - include an attribute to indicate language in each tag,
> - give the endorsement statement both in a local language and English.
Excellent. I am using the xml:lang attribute to indicate language. Let me
think about how I can display the endorsement statement in both languages.
Currently the application is set to only display in the selected language
(unless "display all languages" is selected). It's not impossible, just
needs some thought of how best to manage it.
>We would need clarification of status for the endorsement statement,
>e.g. national standard, endorsed by local DCMI organization, endorsed
>..by a national maintenace agency, voluntary translation by Mr/MS X, etc.
>This would imply transition of translation status, which seems a big
>issue related to maintenance of DC terms.
I agree. This will have to me manually done until the VMS is done (it is
currently not past the very preliminary design stage). Fortunately, we are
not dealing with that many translations. I don't think we need to include
all of the translations in phase 1. I am thinking we should go with what is
there (and perhaps a few more) and add the rest later. Translations (both
UI and terms) are modularized and can be easily added later.