XLIFF Symposium reaches out through Twitter for a call for paper

19 January 2021
XLIFF Symposium reaches out through Twitter for a call for paper

Posted: 16/05/17

Save the date for OASIS XLIFF (XML Localisation Interchange File Format) TC symposium, 31 October through 1 November 2017. This event is scheduled to be the 8th Annual Symposium at FEISGILTT in Silicon Valley. Authors can submit publications online.

David Filip, Research Fellow at the ADAPT Centre, will act as a TC liaison on the Unicode Localisation Interoperability Technical Committee (ULI): “This committee works to ensure interoperable data interchange of critical localisation-related assets, including: 1. Translation memory: A translation memory system stores words or phrases that have been translated previously; 2. Segmentation rules: Segmentation rules define the way to segment text for translation or other text processing; 3. Translation source strings and their translations: Translation source is natural language text, typically with markup, that will be translated into another language, and finally, 3. Word count: Defining best practices around how to best count words in the context of translation interchange… Whether a translation request is completed by human or machine, these assets play a vital role in the overall translation process. Interoperable interchange of these assets reduces errors, lowers costs, and improves throughput.”

The purpose of this event is to encourage collaboration in the need to find extensible XML vocabularies, promote adoption of a specification for the interchange of localisable software while documenting based objects and related metadata. Webinars are available for review, titled, “Two Complimentary Standards” and “Understanding the Technical Solution” both within DITA to XLIFF and Back.

Guidelines have been set within the registry of FragID prefixes for Extensions. Researchers using your own extension elements or attributes in XLIFF 2, and the extension has identifiers, must register the prefix corresponding to your extension’s namespace, so that tools can point to the element following the Fragment Identifier mechanism of XLIFF 2. For further details on registry, visit their website. Follow the social media conversation on collaborative efforts using the hashtag #XLIFF and research partners, @AdaptCentre and @OASISopen.

Share this article: