XLIFF 2.0 and BCM

Localization World 2015 Berlin

Patrik Mazanek, Product Owner, SDL

2nd June 2015

2

Powering

marketing

campaigns

for 400+

global brands

2700Employees Worldwide

Founded in 1992

72 out of the top 100 global brands work with SDL

Publicly traded

company (LSE:SDL)

$430M

Leading Global

CXM Capabilities• Analytics

• Social

• Campaigns

• eCommerce

• Language

• Web

• Documentation

Driving $14B in

online revenue

annually with

our ecommerce

technology

Rated number 1

in web content

management for

Customer

Experience

Enabling

companies to

communicate

with customers

in 100+

countries

7 BILLION words

translated every

month

annual

revenue

70offices

38countries

1500enterprise

customers

3

SDL works with 72 of the Top 100 Global Brands

4

Language

Knowledge

Center

Digital Experience

Customer Analytics

5

APIs

SDL Language

Translation Management Automated Translation Translation Productivity Terminology Global Insights

Global Consultancy

SDL offers a complete language platform

6

History of the bilingual data representation in SDL

○ Multiple proprietary file formats

– DOC, ITD, TTX

○ Standard based file format – SDL XLIFF – introduced with

new platform in 2009

○ SDL XLIFF is now used in majority of SDL products

7

Cloud and the bilingual data

○ Technology mix makes usage of multiple models difficult

and costly

○ Data should be expressed through a model

○ Model needs to be understand in same way by all

components

○ Model needs to be extensible so all relevant data can be

covered

○ Serialization form is irrelevant

8

XLIFF 2.0

○ Does address all requirement for localizable files exchange

○ Is using modules to describe additional data

○ Is strict enough to prevent different understanding of

previously ambiguous information

○ Is not right place for all data we need to handle

○ Not all the data stored via modules are relevant for file type

9

BCM

○ Is just a model, not format for data serialization

○ Describes bilingual data with all required properties

○ Is modular to cover different properties product needs for

processing

○ Can be serialized into multiple file formats

○ Is technology agnostic

○ Is the only data model supported within the Language Cloud

10

Comparison of BCM and XLIFF 2.0

○ BCM was created with keeping XLIFF 2.0 capabilities in

mind

○ As XLIFF 2.0 BCM has modules

– File Formats

– Terminology

– Translation Memory

○ Some of the XLIFF 2.0 modules are directly supported

○ Offers metadata support on all levels

11

12

Elements consistent in XLIFF and BCM

File File

Notes Comments

Unit ParagraphUnit

Segment Segment

Subflows LocalizableSubContent

Annotation AnnotationContainer

Translate Annotation LockedContent

Term Annotation TerminologyData

Comment Annotation Comment

13

Elements not available in BCM

Group

Original Data

Custom Annotation

Splitting Annotation

Skeleton

14

Modules support

Glossary

Format Style

Metadata

Change Tracking

Resource data

15

Current usage of BCM

○ BCM is instrumental part of the SDL Language Cloud

– All internal data exchange is happening on BCM

– BCM as JSON is the only stored form of data

– Universal Editor is using BCM while visualizing data for user

○ Studio 2014 SP2 and later is using BCM when

communicating with MT (via Language Cloud provider)

16

XLIFF 2.0 in suite of SDL products

○ XLIFF 2.0 is not planned to be used as native serialization

○ Will be recognized as 3rd party file type

○ TBC as serialization form for data accessed by 3rd party

products when integrating with SDL Language cloud

Copyright © 2008-2014 SDL plc. All rights reserved. All company names, brand names, trademarks,

service marks, images and logos are the property of their respective owners.

This presentation and its content are SDL confidential unless otherwise specified, and may not be

copied, used or distributed except as authorised by SDL.

Global Customer Experience Management