meetingApril2000

OLIF2 Consortium: Organizational Meeting : 

OLIF2 Consortium: Organizational Meeting April 6, 2000 SAP AG Walldorf, Germany

Agenda: 

Agenda 9.00 – 9.15 Welcome and introductory Remarks: Daniel Grasmick 9.15 – 9.45 Structure of the OLIF2 Consortium: Daniel Grasmick, Susan McCormick 9.45 – 10.30 Time frame for OLIF2: Daniel Grasmick, Susan McCormick Financial issues for the consortium: Daniel Grasmick 10.30 – 10.45 Coffee break 10.45 – 12.00 Current status of OLIF: Gregor Thurmair 12.00 – 13.00 Discussion of changes to OLIF currently envisaged for OLIF2: Susan McCormick 13.00 – 14.00 Lunch 14.00 – 14.30 Review of current level of support for OLIF among tool vendors: Daniel Grasmick, Susan McCormick 14.30 – 15.30 Review of other interchange formats and initiatives: all participants Discussion of interaction of OLIF2 Consortium with SALT and/or OSCAR: all participants 15.30 – 15.45 Coffee break 15.45 – 17.00 Task descriptions for work groups to review current OLIF and suggest changes/additions in linguistic, terminology, and technical specifications; recommendations to be completed in April/May, 2000: all participants

Consortium Participants: 

Consortium Participants Gregor Thurmair, Sail Labs Johannes Ritzke, Sail Labs Alex Muzarku, Logos Pierre-Yves Foucou, Systran Yves Mahe, Xerox Paolo Martins, EU Chris Pyne, L10NBRIDGE Jörgen Danielsen, L10NBRIDGE Nils van der Laan, Trados Peter Quartier, Lotus Ulrike Irmler, Microsoft Daniel Grasmick, SAP Susan McCormick, SAP Jennifer Brundage, SAP Christian Lieske, SAP Christoph Pahlke-Lerch, SAP

Welcome and Introductions: 

Welcome and Introductions Company Professional background Terminology volume Languages supported Organization of terminology management in your company Terminology database(s) used Other tools related to terminology Any exchange formats? Future plans for terminology/lexicon management

Purpose of OLIF2: 

Purpose of OLIF2 To upgrade the current OLIF standard so that it can be supported by tool vendors and applied by users in 2001

Why a New Consortium?: 

Why a New Consortium? OLIF was developed in the OTELO project as a prototype, but is not usable in its current form The SALT project plans to use the OLIF format as part of its XLT standard, but will not edit OLIF1 for content LISA TBX will be based on SALT XLT None of the other formats supports MT requirements Thus, usable OLIF is required e.g., SAP will double its terminology volume by the end of 2000 and add additional NLP tools needing term data

Structure of the Consortium: 

OTELO participants SAIL Labs, Logos, Lotus, SAP New MT representative Systran Term Management representatives Trados, Xerox Service (and tool) providers L10NBRIDGE, L&H via SAIL Labs Users EU, Microsoft... ... And open to interested parties Structure of the Consortium

Time Frame for OLIF2: 

Time Frame for OLIF2 Phase I: Specification Working groups make recommendations for changes to OLIF format by May 31, 2000 Specifications for OLIF2 complete by September, 2000 Phase II: Implementation Tool vendors support new format in 2001 Maintenance tools developed by end of 2000/beginning of 2001

Changes to OLIF for OLIF2 : 

Changes to OLIF for OLIF2

OLIF to OLIF2: 

OLIF to OLIF2 technical structure linguistic analysis terminology handling Review current OLIF format for changes to:

XML: 

XML well-supported industry standard extensible - new element types easily defined well-suited for data exchange formats SALT project already working on XML-based standard in which they want to embed OLIF Make OLIF compliant with XML: technical

Achieving XML-Compliance: 

Achieving XML-Compliance OLIF2 is primarily ‘rewrite’ of OLIF, but with XML-compliance OLIF entry structure remains basically the same for OLIF2 technical

XML-Driven Design Changes: 

reanalyze some current tags as attributes of XML element types, e.g., <LINK=“synonym”> allow for more embedding of structure Use some of the features of XML to make design changes for OLIF2: XML-Driven Design Changes technical

Character Sets: 

Current OLIF: ISO-Latin-1 OLIF2 functionality: double-byte characters bidirectionality XML supports ISO/IEC 10646, which is similar to unicode Character Sets technical

Changes to the OLIF Concept: 

company-code as part of central entry base formally distinguish bilingual from monolingual links develop protocol for user-defined fields Make substantive changes to the structure Changes to the OLIF Concept technical

Converging with other Standards: 

Converging with other Standards Achieve as much overlap as possible with, e.g., names of element types structure of entries Coordination with other standardization initiatives such as SALT technical

Review of Linguistic Features : 

Review of Linguistic Features are features in correct feature groups? are all of the features that are essential for the different vendors covered? transitivity for Logos Systran requirements Xerox what about other NLP products or users? Comprehensive review of linguistic features linguistic

Morphology : 

Morphology currently includes only German, Danish and English theoretical underpinnings of analysis are inconsistent Review the current morphological analysis linguistic

Syntax and Semantics : 

Syntax and Semantics selectional restrictions (transfer conditions) - representation should be improved syntactic frames - currently for German, Danish and English only semantic types - should be reviewed and expanded Special attention to: linguistic

Features and Values : 

Features and Values Make sure feature names and values conform to general practice Make sure all element types that we want to cover are actually in DTD linguistic

Canonical Forms : 

Canonical Forms defined for formulation of entry string in given language necessary for optimal convergence of entries from different systems based on language-specific lexical conventions published as part of formal specification Conventions for formulating canonical forms linguistic

Structure of Terminology : 

Structure of Terminology allow for deeper structure, more embedding (in line with MARTIF?) expand on feature/value pairs to allow more admin detail Expand current structure? terminology

Entry Identifier : 

Entry Identifier current OLIF does not support a unique identifier for each entry, although many termbanks require this Add unique entry identifier terminology

Review of OLIF Support Among Tool Vendors: 

Review of OLIF Support Among Tool Vendors

Overview of Other Exchange Formats and Initiatives : 

Overview of Other Exchange Formats and Initiatives

MARTIF : 

MARTIF SGML-based strictly terminology formal concept-orientation extensive DTD lots of administrative information relatively complex embedding in structure ISO 12200:1999 Standard

X-MARTIF : 

extended MARTIF - attempt to coordinate with TMX and OLIF adapted to XML extends MARTIF to include NLP some features Proposal ISO/TC 37/SC 3 N 318 X-MARTIF

SALT : 

SALT XLT (lex/term exchange) OLIF (lex) MSC (term < MARTIF) SALT Project - Currently funded by the EU

OSCAR : 

OSCAR TMX - format for re-use of translation memory data TBX - lex/termbase exchange (subset of XLT) Group within LISA Organization

Geneter : 

Geneter for DB management compatibility with internet fairly complex hierarchical structure reworked to allow multiple word senses alongside concept model “Generic model for the distribution and reuse of heterogeneous terminological data”

Meeting Results:Participation of all companies invitedworking in 3 action groups ... : 

Meeting Results: Participation of all companies invited working in 3 action groups ...

TG1: Technical Structure : 

TG1: Technical Structure Goal: provide formal structure of the format Review for XML compliance Redundancy Links representation Definition of the header Incorporation of user-defined fields = Output: OLIF DTD

TG2: Linguistic Analysis: 

TG2: Linguistic Analysis Goal: provide a “final” list of feature-value pairs for the linguistic component Canonical form formulation Morphology, syntax and semantics Transfer conditions and transformations Cross-references (based on ISO)

TG3: Terminology Handling: 

TG3: Terminology Handling Goal: to provide a “final” list of feature-value pairs for terminology Concordance with other standards Administrative information

Languages Supported in OLIF2: 

Languages Supported in OLIF2 Priority 1 EN DE DA FR ES PT JA Priority 2 RU IT NL Other priorities... EL HU ZH ZF KO AR

Other Items: 

Other Items Terminology samples from all participants at least 100 entries incl. description at least 2 languages and different categories