oaxal - oasis · oaxal scenario 2/1 • xml cms publishing system • editor checks out a topic for...
TRANSCRIPT
![Page 1: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/1.jpg)
OAXAL Open Architecture for XML Authoring and Localization
Andrzej Zydroń: [email protected]
June 2010
![Page 2: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/2.jpg)
Why OAXAL?
![Page 3: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/3.jpg)
Why OAXAL?
![Page 4: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/4.jpg)
Globalization Standards
![Page 5: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/5.jpg)
Globalization Standards
![Page 6: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/6.jpg)
Interoperability
![Page 7: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/7.jpg)
Interoperability
![Page 8: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/8.jpg)
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
![Page 9: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/9.jpg)
Why Open Standards?
• Usability • Interoperability • Exchange • Risk reduction • Investment protection • Reduced implementation costs
![Page 10: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/10.jpg)
Why Open standards
• Free – no fees • Input is from accredited volunteers • Democratic process • Extensive peer review • Extensive public review • Well documented
![Page 11: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/11.jpg)
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
![Page 12: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/12.jpg)
Localization Standards
Standards matter Reduce costs Improve interoperability Improve quality Create more competition
![Page 13: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/13.jpg)
True Cost of Translation
![Page 14: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/14.jpg)
Localization without Standards
![Page 15: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/15.jpg)
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
![Page 16: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/16.jpg)
SR
X
GM
X
Unicode TR
29
XLIFF
TMX
W3C
ITS
xml:tm
DITA ?
![Page 17: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/17.jpg)
OAXAL
Open Architecture for XML Authoring and Localization (OAXAL)
– OASIS TC Standard – http://docs.oasis-open.org/oaxal/V1.0/oaxal-v1.0.html
![Page 18: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/18.jpg)
Why OAXAL?
1. Encourage the use of Open Standards for XML Authoring and Localization
2. Provide a SOA Architecure for XML Authoring and Localization
3. Provide a template of how to integrate Open Standards for XML Authoring and Localization
![Page 19: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/19.jpg)
OAXAL
OAXAL Stack
![Page 20: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/20.jpg)
Putting it all together: OAXAL
![Page 21: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/21.jpg)
OAXAL
• OAXAL enables Open Architecture approach • Open Standards - Open APIs • Easy Exchange • Modular design • Interoperability • Very high level of automation
![Page 22: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/22.jpg)
Web 2.0 and Standards
![Page 23: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/23.jpg)
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
![Page 24: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/24.jpg)
XML CONTENT
Document Creation
QA/Post-Edit
Localization
Source Document Lifecycle
Authoring Publish
Publish Localized
![Page 25: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/25.jpg)
Source Document
Match
QA/Post-Edit
Localization Workflow
Prepare Translate
Publish Localized
![Page 26: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/26.jpg)
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
![Page 27: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/27.jpg)
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
![Page 28: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/28.jpg)
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
![Page 29: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/29.jpg)
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
![Page 30: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/30.jpg)
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
![Page 31: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/31.jpg)
OAXAL In Action
![Page 32: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/32.jpg)
Web 2.0 Localization
![Page 33: OAXAL - OASIS · 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 •](https://reader033.vdocuments.us/reader033/viewer/2022052003/6016250490946b0ac817fbd9/html5/thumbnails/33.jpg)
OAXAL TC
http://www.oasis-open.org/committees/oaxal
OAXAL 1.0 Reference Reference Model: http://www.l24.cm/OAXAL
/