-
Notifications
You must be signed in to change notification settings - Fork 3
TAPICC Tracks and Working Groups
JanHusarcik edited this page Oct 17, 2017
·
1 revision
Four main standardization tracks have been identified and sorted by relevance and priority:
-
Track 1 — Supply chain automation: Enable the exchange of business metadata, localizable content
and automation-relevant functionality between content repositories and localization environments*
- Working group 1 — Business metadata
- Working group 2 — Payload specification
- Working group 3 — XLIFF extraction
- Working group 4 — API specification
-
Track 2 — Transfer of localizable content on a segment or unit level: Enable the handing over of
segments and units within the localization process, for instance between different
localization tools
- No working groups defined yet
-
Track 3 — Enrichment of localizable content: Enable the markup of localizable content with linguistic
information such as TM matches, MT output, terminology markup, “good enough” layout
markup and other meaningful data for the actual localization work
- No working groups defined yet
-
Track 4 — In-layout translation: Enable an abstract layout representation in localization content to
allow translation and review process to happen in layout, independent of the content source
- No working groups defined yet
Any specification work should strive to be or become grounded in the OASIS Universal Business Language (UBL) as the business metadata model and XLIFF 2.1 or higher as the content representation standard wherever possible
See also original TAPICC Charter