100 likes | 236 Views
XLIFF metadata throughout workflows. Chat about best modular strategy for metadata in XLIFF 2.0. Panelists. Dag Schmidtke – Microsoft G á bor Ugray – Kilgray Heiko R ölke – DIPF Lorcan Ryan – LRC David Filip – Moravia Worldwide. New requirements.
E N D
XLIFF metadata throughout workflows Chat about best modular strategy for metadata in XLIFF 2.0
Panelists • Dag Schmidtke – Microsoft • Gábor Ugray – Kilgray • Heiko Rölke – DIPF • Lorcan Ryan – LRC • David Filip – Moravia Worldwide
New requirements • David: MT and automated linguistic processing in general brings new requirements • Cosmetic changes to the old standard won’t be enough • Heiko & Lorcan: Standards are changing too often. Need to work rather on thorough implementation of the current standard or at least stress backwards compatibility • Dag: What is the ROI? • Gábor: Adding new functionality through extension points is dangerous
Inline markup & segmentation • Lorcan: Type of standard inline markup encoding should be indicated via workflow level metadata • David: XLIFF needs a standardized way for transparently changing segmentation • Gábor: A radical change would lead to descreased interoperability over a transitional period • Dag: We also sense this need
Annotating segments • Gábor: XLIFF needs to put forward a standardized way for commenting on segment and subsegment level • Standardize inputs from CAT tools • Status flags, QA warnings etc. • Lorcan: Standardize for both source and target • David: First segmentation needs to be rectified to achieve this goal • Heiko: Need to mark notes as read only
BLOB and skeleton • Dag: Currently no standardized resizing roundtrip exists • Need support for containing and round-tripping standard resource types such as dialogs • Gábor: Current skeleton concept should be greatly enhanced with standardized metadata re rendering, processing, ~ mime-types • David: BLOB vs. structured skeleton
Automated linguistic processing • David: This area seems like a heavy separate module in XLIFF 2.0 • Automated TM and MT application • Semantic and morphologic tagging • Lorcan: • Advanced Leverage metadata throughout workflow
Q&A Thanks for your attention • Dag Schmidtke dags@MICROSOFT.com • Gábor Ugraygabor.ugray@kilgray.com • Heiko Rölke roelke@dipf.de • Lorcan Ryan Lorcan.Ryan@ul.ie • David Filip davidf@moraviaworldwide.com
Back-pocket questions • To all: Which parts of the standard must be backwards compatible in your view? • Some typical trap-points that metadata tend not to survive?