Successfully reported this slideshow.

28 September 2011, TAUS XLIFF Symposium, Poland


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

28 September 2011, TAUS XLIFF Symposium, Poland

  1. 1. 2nd  XLIFF  Symposium  28  September  2011,  Warsaw,  Poland  Building  consensus  on  the  future  of  XLIFF   Rahzeb Choudhury Operations Director TAUS
  2. 2. XLIFF – TAUS Role Why  is  TAUS  working  on  XLIFF  now?     XLIFF  has  been  highlighted  by  each  TAUS  member  group  –  buyers,   service  and  technology  providers  –  as  (poten@ally)  important  to  their   opera@ons   Current  2.0  requirements  gathering  period  provides  an  opportunity   for  improvement  on  what  is  possible  with  current  XLIFF  specifica@ons   What  does  TAUS  aim  to  do?     Engage  stakeholders  in  the  requirements  gathering,  be  an  arbiter  on   non  proprietary  needs   Foster  environment  for  beLer  adop@on  paLerns  than  currently  
  3. 3. XLIFF – TAUS Activity Market  Survey     July  –  Undertook  survey  in  partnership  with  the  OASIS  XLIFF  TC  to   beLer  understand  adop@on,  usage  and  needs  at  a  high-­‐level     Buyers  ConsultaCon     September/October  –  More  detailed  consulta@on  with  transla@on   buyers     (Do  we)  Propose  to  Analyze  Variances  in  Current  ImplementaCons     November/December  –  Proposed  to  do  this  following  the  buyers   consulta@on    
  4. 4. Market  Survey  on  XLIFF  Respondents/Demographics  434  respondents  from  37  countries  85%  from  Europe  and  North  America  I am a/work at a: Translator  (107)   7% Transla@on  Buyer  (57)   30% Transla@on  Technology  (49)   33% Provider   Language  Service  Provider  (119)   Other  (mainly  consultants)  (26)   16% 14%
  5. 5. Market  Survey  on  XLIFF  Adoption/Intentions  Are you currently using XLIFF For the 41% (178) thatas part of your process? answered “No”: Dont Know 8% Yes 32% Dont know Yes No 44% 51% 41% No 24% Do you believe XLIFF will be used as part of your process within the next 12 months?
  6. 6. Market  Survey  on  XLIFF  Adoption  –  by  group   As  we  might  expect  good  level  of  adop@on  among  LSPs  and  Technology   Providers  (that  responded)  
  7. 7. Market  Survey  on  XLIFF  Usage   What is your main use for XLIFF? An  Interchange  file  format  between  the  systems  used  by   6% content  developers  and  those  used  by  transla@on   26% For  sending  files  to  translators  who  then  use  their  tool  of   choice   For  integra@ng  the  various  modules  of  my  transla@on   management  system   43% It  is  the  file  format  used  by  my  translaCon  tool   16% Used  as  a  format  for  exchanging  transla@on  memory   9%
  8. 8. Market  Survey  on  XLIFF  Usage  –  by  group  
  9. 9. Market  Survey  on  XLIFF  Future  scope  Which  of  these  statements  do  you  agree  with  most?   The  best  standard  for  transla@on  could  be   developed  by  concentra@ng  on  one  single   standard  which  covers  content   interchange,  transla@on  memory     45% exchange,  segmenta@on  rules  exchange   and  terminology  exchange.   55% The  best  standard  for  transla@on  could  be   developed  by  concentra@ng  on  four   standards  which  deal  with  the  following:   content  interchange,  transla@on  memory     exchange,  segmenta@on  rules  exchange   and  terminology  exchange.  
  10. 10. Market  Survey  on  XLIFF  Future  scope  –  by  group   A  need  for  communica@on  and  educa@on  
  11. 11. Market  Survey  on  XLIFF  Priorities   For me the single most important thing about XLIFF is: Its widespread use 15% I can see that it is making progress towards one day Its extensibility becoming a 11% useful standard 45% The majority of tools support it 29%
  12. 12. Market  Survey  on  XLIFF  Priorities  –  by  group  
  13. 13. Market  Survey  on  XLIFF  What  needs  to  happen  For XLIFF to become truly valuable the following needs to happen: More end customers need to use it 8% 16% XLIFF needs to be more standard with less flavours 28% for every tool and less extensions There is a need for clarity as to how tools support it and what functionality they support. 48% There needs to be less emphasis on new features and more documentation on using the existing ones.
  14. 14. Market  Survey  on  XLIFF  What  needs  to  happen  –  by  group  
  15. 15. Market  Survey  on  XLIFF  Conclusions  Good  level  of  engagement,  evidenced  by  the  response  level    Good  level  of  adop@on  among  LSPs  and  technology  providers  who  responded    People  want  less  extensibility  /  less  flavors  –  modulariza@on  makes  sense    Need  for  communica@on  and  educa@on  –  differences  of  opinion  on  whether  to  grow  of  scope  of  XLIFF  or  not      Use  scenarios  need  further  review  –  are  buyers  reques@ng  greater  considera@on  of  using  XLIFF  as  a  way  to  integrate  content  crea@on  with  transla@on  and  localiza@on?    
  16. 16. Buyers  Consultation  Why,  What,  Who,  When  and  How  Why  –  Engagement  and  use  among  buyers  is  a  key  success  factor  going  forward    What  –  Ask  buyers  to  consider  a  proposal  on  how  to  modularize  current  elements  and  provide  input  on  what  more  is  needed  as  a  priority  for  the  new  specificaCons    Who  –  Thirty  transla@on  buyers  –  mainly  from  the  IT  sector    When  –  September/October    How  –  Collect  responses,  TAUS  reviews  commonali@es  and  differences,  makes  a  refined  proposal,  collect  feedback  and  draf  report  on  survey  and  consulta@on  findings  for  TC  to  consider    
  17. 17. Buyers  Consultation  The  ProposalAsk  buyers  to  review  and  agree/not  –  if  not,  why  not    Prac@cal/concrete  common  star@ng  point  for  the  consulta@on    Modularize  -­‐  easier  to  understand  than  now,  easier  to  develop  tools,  easier  to  check  compliance  –arrive  at  clearer  defini@ons  of  compliance      Include  in  Core  those  elements  that  are  unlikely  to  change    
  18. 18. Buyers  Consultation  The  proposal  on  organizing  existing  elements Bold = Mandatory
  19. 19. Buyers  Consultation  Feedback  on  additions  to  XLIFF  scope   Worlflow   Basic  workflow  support   Enhanced  sta@s@cs  –  to  include  count,  match  and  cost  informa@on     Content descriptions Adding descriptions of types of content (CMS, document, software, ..) Multilinguality Move further from bilingual to multilingual Other feedback Documentation, guidance, reference implementation (analog into DITA) Great deal of alignment with the features currently being reviewed by the TC
  20. 20. Propose  to  analyze  variances  in  existing  implementations  Thoughts  on  Why,  What,  Who,  When  and  How   Why  –  Triangula@on  to  zero  in  on  facts.     What  –  Reviewing  features  currently  used  by  tools.  Checking  cross   compatability  between  tools     Who  –  Tool  developers     When  –  November/  December     How  –   1.  Survey  about  the  details  of  XLIFF  implementa@ons   2.  Test  implementa@ons  (transparently,  openly,  neutrally)   3.  Inform  TC  of  findings   NOTE THIS PROPOSAL WAS REJECTED BY TOOL VENDORS IN THE ROOM
  21. 21. Feedback, pleaseDoes  TAUS’  work  regarding  XLIFF  add  value?    How  can  our  approach  be  improved?    Should  we  analyze  current  implementa@ons?    Will  you  par@cipate  if  we  do?         Thank  you!