MLHIM Specifications

Create a Method for Internationalization/Localization CCD strings

Registered by Tim Cook

This blueprint has been superseded. See the newer blueprint "Governance Policy Development" for updated plans.

With the removal of the Ontology, the previous approach to translations no longer exists. This is a good trade off for the simplicity gained. However, being able to translate CCDs using common 'gettext' tools is essential. Primarily the strings that need translating will exist in the enumeration facet of attributes (XML elements). Is there a best practices approach already in place for this? If not, what is the best approach?

When speaking of translations in this context it is meant to include i18n and l10n.

There is a W3C spec here: http://www.w3.org/TR/xml-i18n-bp/#DesignTime can someone examine and summarize it for the group?

Blueprint information

Status:
Complete
Approver:
Tim Cook
Priority:
Essential
Drafter:
Tim Cook
Direction:
Needs approval
Assignee:
MLHIM Specifications Developers
Definition:
Superseded
Series goal:
Accepted for 2.0
Implementation:
Not started
Milestone target:
milestone icon 2.3.0
Completed by
Tim Cook

Related branches

Sprints

Whiteboard

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

Nearby

This blueprint contains Public information 
Everyone can see this information.