OAXALOpen Architecture for XMLAuthoring and Localization               June 2010Andrzej Zydroń: azydron@xml-intl.com
Why OAXAL?
Why OAXAL?
Globalization Standards
Globalization Standards
Interoperability
Interoperability
Globalization Standards• Can we imagine world trade without the  Shipping container• World trade would be significantly  h...
Why Open Standards?•   Usability•   Interoperability•   Exchange•   Risk reduction•   Investment protection•   Reduced imp...
Why Open standards•   Free – no fees•   Input is from accredited volunteers•   Democratic process•   Extensive peer review...
Localization Standards Parent organization  • LISA OSCAR, ISO, W3C, OASIS Constitution  • IP policy, membership and comm...
Localization Standards   Standards matter   Reduce costs   Improve interoperability   Improve quality   Create more c...
True Cost of Translation
Localization without     Standards
Too Many Standards?•   W3C ITS Document Rules•   Unicode TR29•   LISA OSCAR SRX•   LISA OSCAR xml:tm•   LISA OSCAR TMX•   ...
DITA   XLIFF                  SRX               ?  TMX                       GMXUnicode TR29             xml:tm           ...
Open Architecture for XML Authoring andLocalization (OAXAL)  – OASIS TC Standard  – http://docs.oasis-open.org/oaxal/V1.0/...
Why OAXAL?1. Encourage the use of Open Standards for   XML Authoring and Localization1. Provide a SOA Architecure for XML ...
OAXALOAXAL Stack
Putting it all together:        OAXAL
OAXAL•   OAXAL enables Open Architecture approach•   Open Standards - Open APIs•   Easy Exchange•   Modular design•   Inte...
Web 2.0 and Standards
So Why does this matter?•   Reduced Cost•   Improved Quality•   In Context Exact Matching•   Standard Metrics•   Quicker T...
XML                                                                 CONT                               QA/Post-Edit       ...
Match                              SourcePrepare                                                  Translate               ...
OAXAL Scenario 1/1• Flagship CMS Based Web Site• Author changes text on the page• Web Services client sends page for  tran...
OAXAL Scenario 1/2• On completion of translation reviewer is  notified by SMS/email• Reviewer reviews via web interface an...
OAXAL Scenario 2/1• XML CMS Publishing System• Editor checks out a topic for edit• On check out/in xml:tm is applied to  u...
OAXAL Scenario 2/2• The xml:tm form of the document is used  for matching and creation of XLIFF file• The XLIFF file is us...
OAXAL Scenario 2/3• On completion of translation the target  documents are created automatically• The target documents are...
OAXAL In Action
Web 2.0 Localization
OAXAL TChttp://www.oasis-open.org/committees/oaxalOAXAL 1.0 Reference Reference Model:  http://www.l24.cm/OAXAL/
Upcoming SlideShare
Loading in...5
×

OASIS OAXAL Presentation

270

Published on

OASIS Webinar series OAXAL Presentation

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
270
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "OASIS OAXAL Presentation"

  1. 1. OAXALOpen Architecture for XMLAuthoring and Localization June 2010Andrzej Zydroń: azydron@xml-intl.com
  2. 2. Why OAXAL?
  3. 3. Why OAXAL?
  4. 4. Globalization Standards
  5. 5. Globalization Standards
  6. 6. Interoperability
  7. 7. Interoperability
  8. 8. Globalization Standards• Can we imagine world trade without the Shipping container• World trade would be significantly hampered• World GDP would be significantly reduced• Billions of people would be condemned to a life of constant poverty
  9. 9. Why Open Standards?• Usability• Interoperability• Exchange• Risk reduction• Investment protection• Reduced implementation costs
  10. 10. Why Open standards• Free – no fees• Input is from accredited volunteers• Democratic process• Extensive peer review• Extensive public review• Well documented
  11. 11. Localization Standards Parent organization • LISA OSCAR, ISO, W3C, OASIS Constitution • IP policy, membership and committee rules Membership • Company, academic, individual Technical committee • OASIS XLIFF, LISA OSCAR GMX, W3C ITS Extensive peer review and discussions Public review process
  12. 12. Localization Standards Standards matter Reduce costs Improve interoperability Improve quality Create more competition
  13. 13. True Cost of Translation
  14. 14. Localization without Standards
  15. 15. Too Many Standards?• W3C ITS Document Rules• Unicode TR29• LISA OSCAR SRX• LISA OSCAR xml:tm• LISA OSCAR TMX• LISA OSCAR GMX• OASIS XLIFF• W3C/OASIS DITA, XHTML, DocBook, or any component based XML Vocabulary
  16. 16. DITA XLIFF SRX ? TMX GMXUnicode TR29 xml:tm W3C ITS
  17. 17. Open Architecture for XML Authoring andLocalization (OAXAL) – OASIS TC Standard – http://docs.oasis-open.org/oaxal/V1.0/oaxal-v1.0.html
  18. 18. Why OAXAL?1. Encourage the use of Open Standards for XML Authoring and Localization1. Provide a SOA Architecure for XML Authoring and Localization1. Provide a template of how to integrate Open Standards for XML Authoring and Localization
  19. 19. OAXALOAXAL Stack
  20. 20. Putting it all together: OAXAL
  21. 21. OAXAL• OAXAL enables Open Architecture approach• Open Standards - Open APIs• Easy Exchange• Modular design• Interoperability• Very high level of automation
  22. 22. Web 2.0 and Standards
  23. 23. So Why does this matter?• Reduced Cost• Improved Quality• In Context Exact Matching• Standard Metrics• Quicker Turnaround Times• Advanced Technology• Allows standards based interaction with CMS systems
  24. 24. XML CONT QA/Post-Edit ENT DocumentAuthoring Publish Creation Publish Localization Localized Source Document Lifecycle
  25. 25. Match SourcePrepare Translate Document Publish QA/Post-Edit Localized Localization Workflow
  26. 26. OAXAL Scenario 1/1• Flagship CMS Based Web Site• Author changes text on the page• Web Services client sends page for translation• Workflow and analysis automatically triggered• Translator notified by SMS/email• Translator logs into web page via hyperlink• Translator uses web based fully functional interface
  27. 27. OAXAL Scenario 1/2• On completion of translation reviewer is notified by SMS/email• Reviewer reviews via web interface and completes workflow• Web Services client sees translation completed• Updated web page is published• For small changes this can be done in minutes
  28. 28. OAXAL Scenario 2/1• XML CMS Publishing System• Editor checks out a topic for edit• On check out/in xml:tm is applied to uniquely identify each segment• During authoring author memory can be applied• Once the editing workflow has finished the topic is forwarded to translation
  29. 29. OAXAL Scenario 2/2• The xml:tm form of the document is used for matching and creation of XLIFF file• The XLIFF file is used to drive an online translation editor• Translators are notified by email and log in to translate• All TMs are shared and held centrally• Reviewers also access the Web based translation editor
  30. 30. OAXAL Scenario 2/3• On completion of translation the target documents are created automatically• The target documents are checked into the CMS• The target documents are ready for publishing
  31. 31. OAXAL In Action
  32. 32. Web 2.0 Localization
  33. 33. OAXAL TChttp://www.oasis-open.org/committees/oaxalOAXAL 1.0 Reference Reference Model: http://www.l24.cm/OAXAL/

×