OAXAL
Download as ppt, pdf1 like453 views
This document discusses the Open Architecture for XML Authoring and Localization (OAXAL) standard. It explains that OAXAL aims to encourage the use of open standards for XML authoring and localization by providing a service-oriented architecture and best practices for integrating existing standards. The document provides examples of how OAXAL allows for automated localization workflows between content management systems and translation tools on the web, enabling real-time localization of authored content. Adopting open standards-based approaches like OAXAL can reduce costs, improve quality and increase interoperability for organizations.
1 of 36
Download to read offline
Ad
Recommended
Systematic Migration of Monolith to Microservices
Systematic Migration of Monolith to MicroservicesPradeep Dalvi
油
The document discusses the transition from monolithic applications to microservices, highlighting the benefits of agility, flexibility, and rapid deployment. It outlines strategies for migration, including incremental refactoring, defining boundaries, and handling partial failures, while cautioning against risky big bang rewrites. Additionally, it covers key concepts such as authentication, inter-process communication, and database splitting to support this transformation.Marketplace integration
Marketplace integrationMaria do Ceu Morais
油
This document discusses various challenges and considerations for integrating an e-commerce business with online marketplaces. It outlines the common integration tasks including product listing, pricing, inventory, orders, and payments. It then describes the different integration methods used by marketplaces like eBay, Amazon, Play.com and Tesco which can include APIs, file uploads, and manual processes. The document emphasizes the importance of proper integration to avoid issues like suspensions or loss of sales, and stresses planning for ongoing management and responding to changes from the marketplaces.An Overview of Web Services: SOAP and REST
An Overview of Web Services: SOAP and REST Ram Awadh Prasad, PMP
油
The document discusses the complexities of web services, focusing on both SOAP and RESTful architectures. It highlights the characteristics, advantages, and disadvantages of each approach while emphasizing the need to move beyond siloed enterprise applications through service-oriented architecture. Additionally, it provides a comparative analysis to help in choosing between SOAP and RESTful services based on specific use cases. "Hook, Line and Syncer": Migrating existing websites within TERMINALFOUR Sit...
"Hook, Line and Syncer": Migrating existing websites within TERMINALFOUR Sit...Terminalfour
油
The document outlines the migration process for over 300 websites during the University College Cork redesign project, initiated in 2011 and completed in early 2014. Key challenges included reskinning existing sites, coordinating with numerous moderators, and mapping old content types to new ones using an external content syncer. The migration successfully reduced the initial timeline from 18 months to 12 months, enabling improved user experience and streamlined site management.Introduction to Restful Web Services
Introduction to Restful Web Servicesweili_at_slideshare
油
This document provides an introduction to RESTful web services. It defines REST and its architectural principles including addressing resources with URIs, using a uniform and constrained interface, focusing on representations of resources, stateless communication, and hypermedia as the engine of application state. It discusses implementing RESTful services with Java using JAX-RS annotations and frameworks like Jersey and CXF. It also covers testing REST APIs, content negotiation, error handling, versioning, and security considerations.DEV-1129 How Watson, Bluemix, Cloudant, and XPages Can Work Together In A Rea...
DEV-1129 How Watson, Bluemix, Cloudant, and XPages Can Work Together In A Rea...Frank van der Linden
油
The document discusses the integration of various IBM technologies, including Watson, Bluemix, Cloudant, and XPages, to create a Human Resource Assistant application. It highlights the application's backend written in Java, data storage in Cloudant, and analysis using Watson services like Tone Analyzer and Personality Insight. Key lessons learned emphasize the challenges of handling attachments and inconsistencies across APIs, while also noting the effectiveness of Cloudant and Watson services in building flexible applications.Using the Cascade Server Web Service API, by Artur Tomusiak
Using the Cascade Server Web Service API, by Artur Tomusiakhannonhill
油
This document provides an overview of Cascade Server web services. It discusses what a web service is and examples of how they can be used. It covers the main operations available through the Cascade Server web services API like create, read, edit, delete, copy, and managing access rights. It also explains how to authenticate to the web services and understand the WSDL file. Code examples are provided for common operations in PHP. Limitations of the web services are outlined and upcoming features in Cascade Server 7.2 are previewed.UWP apps development - Part 2
UWP apps development - Part 2Jiri Danihelka
油
This document discusses structuring a Universal Windows Platform (UWP) application. It outlines where to place different types of code components like views, view models, models, and repositories. It also discusses using complementary technologies like WebAPI, Entity Framework, and T4 templates. It covers consuming WebAPIs in UWP apps and validation requirements. Finally, it discusses authentication using Azure Active Directory and securing apps and services.Site speed Server Optimization
Site speed Server OptimizationShelly Fagin
油
The document discusses options for optimizing server performance including using alternative databases like MariaDB instead of MySQL, implementing caching at the page level and web server level using techniques like mod_pagespeed, using Nginx as a web server or reverse proxy, and load balancing. It promotes using these advanced techniques to achieve wicked fast website performance.Building & Testing Scalable Rails Applications
Building & Testing Scalable Rails Applicationsevilmike
油
This document discusses building scalable Rails applications. It covers using multiple Rails processes and servers to handle concurrent requests. It recommends optimizing database queries, caching, offloading long tasks, and serving static assets externally. It also provides tips for load testing including using realistic data and environments, considering location and caching effects, and paying attention to request headers.Solving trust issues at scale - Omer Levi Hevroni
Solving trust issues at scale - Omer Levi HevroniDevOpsDays Tel Aviv
油
The document discusses building a scalable authorization system that ensures trust across microservices using a zero-trust approach and least privilege principles. It highlights key components like the Envoy proxy and Open Policy Agent (OPA) for managing authentication and authorization, as well as the importance of audit logs and decision logging. The focus is on enabling developers to implement secure policies while minimizing the impact on development speed and complexity.Performance Testing w/ WebPage Test Private Instance (DrupalCamp Ohio)
Performance Testing w/ WebPage Test Private Instance (DrupalCamp Ohio)Bill Condo
油
The document covers performance testing for web pages, including definitions, challenges, and available tools such as WebPageTest and YSlow. It discusses key metrics like milestone timings, speed index, and various quantity and rule-based metrics. The presentation emphasizes the importance of setting up a proper testing environment and outlines next steps for improvement.ShopBack Catalog with Elastic
ShopBack Catalog with ElasticAlberto Resco P辿rez
油
The document outlines ShopBack's journey in enhancing their shopping platform using Elasticsearch for scalable product catalog and search functionalities. Key highlights include the transition to a multi-country, multi-language setup with improved performance and metrics collection, as well as lessons learned from the migration process. Future developments involve further optimizations like fuzzy matching, type-ahead suggestions, and machine learning applications for fraud detection.Dropping ACID: Wrapping Your Mind Around NoSQL Databases
Dropping ACID: Wrapping Your Mind Around NoSQL DatabasesKyle Banerjee
油
This document discusses NoSQL databases as an alternative to traditional relational databases. It provides an overview of different types of NoSQL databases like document stores, wide column stores, key-value stores and graph databases. It also discusses advantages of NoSQL databases like horizontal scalability and ease of use with large amounts of unstructured data, as well as disadvantages like lack of transactions and joins. The document recommends choosing a database based on the type of queries, data size, read/write needs, and whether the data needs to be accessed by other applications.EDF2013: Selected Talk S淡ren Roug: Reportnet a Case Study
EDF2013: Selected Talk S淡ren Roug: Reportnet a Case StudyEuropean Data Forum
油
Reportnet is a 14-year-old system that enables countries to upload and archive data, primarily in XML format, for about 400 reporting obligations. It includes features like automatic quality assurance (QA) and an online questionnaire, allowing users to validate and remix data more efficiently. Recent enhancements consider transitioning to a database with a REST web service to manage heterogeneous data and improve the semantic linking of vocabularies.Rosenblum Workflow Choices Introducing XML
Rosenblum Workflow Choices Introducing XMLNational Information Standards Organization (NISO)
油
The document discusses the importance of XML in modern publishing workflows, emphasizing its role in enhancing user experiences through responsive design, accessibility, and rich hyperlinks. It outlines the challenges and considerations involved in integrating XML into the publishing process, including managing vendor relationships and ensuring XML quality. The document further suggests evaluating business goals and developing standards to successfully implement XML solutions in publishing.Why real integration developers ride Camels
Why real integration developers ride CamelsChristian Posta
油
This document provides an agenda and summaries of key points from a presentation on integrating systems using Apache Camel. The presentation discusses how Apache Camel is an open-source integration library that uses enterprise integration patterns to connect disparate systems. It highlights features of Camel including components, data formats, and testing frameworks. Customer examples are presented that demonstrate large returns on investment and cost savings from using Camel for integration projects. The presenters argue that Camel provides flexibility, reusability and rapid development of integrations.Published in 1885 and shared on facebook
Published in 1885 and shared on facebookJoe Kepley
油
The Christian Science Publishing Society handles all publishing operations for the Christian Science Church. It publishes several periodicals, including the Christian Science Monitor, a daily newspaper, as well as weekly and monthly magazines. The project involves digitizing all back issues of these publications by scanning and converting articles to XML format in order to make the entire archives available online through a new digital platform. The goals are to grant subscribers access to the content while also allowing free sharing and access to selected articles. The project will use an agile methodology with phases and sprints to develop the new system incrementally.Integrating Alfresco with SharePoint & Drupal Using CMIS
Integrating Alfresco with SharePoint & Drupal Using CMISBenjamin Chevallereau
油
The document describes a solution for integrating Alfresco with SharePoint and Drupal using CMIS, allowing direct access to ECM repositories and enhancing document management features. It highlights the benefits of increased user adoption, elimination of content silos, and customization options for various platforms. Additionally, it outlines use cases such as collaboration, secure storage, and compliance applications, along with a sample business application demonstration.Hopkins Leveraging XML to Enhance Semantic Value of Standards
Hopkins Leveraging XML to Enhance Semantic Value of StandardsNational Information Standards Organization (NISO)
油
The document discusses the integration of XML to enhance the semantic value of standards in manufacturing. It emphasizes how standards are utilized as data rather than just documents, impacting various stakeholders such as engineers and IoT users. The content highlights the importance of usability and connected documentation in industrial processes.Service oriented architecture
Service oriented architectureKhaled Musaied
油
This document provides an orientation on SOA (Service-Oriented Architecture) and WCF (Windows Communication Foundation). It defines SOA as an architecture based on discrete software services providing functionality to other applications independently of vendor, product, or technology. A service is defined as a self-contained unit of functionality. WCF is introduced as a framework for building service-oriented applications that supports SOA principles like loose coupling and interoperability. The presentation includes an overview of SOA benefits and service design principles, as well as how WCF maps to the core components of SOA.Events in a microservices architecture
Events in a microservices architectureSaul Caganoff
油
The document discusses the integration of event-driven architecture with microservices, highlighting the challenges of maintaining consistency in distributed systems. It covers the importance of understanding service interactions, such as commands, queries, and events, along with trade-offs between orchestration and choreography. Additionally, it emphasizes the role of events in providing loose coupling and improving state communication across different system components.Building better SQL Server Databases
Building better SQL Server DatabasesColdFusionConference
油
This document provides an overview of a presentation on building better SQL Server databases. The presentation covers how SQL Server stores and retrieves data by looking under the hood at tables, data pages, and the process of requesting data. It then discusses best practices for database design such as using the right data types, avoiding page splits, and tips for writing efficient T-SQL code. The presentation aims to teach attendees how to design databases for optimal performance and scalability.Growing an API Culture - APIdays LIVE AU 2020
Growing an API Culture - APIdays LIVE AU 2020Saul Caganoff
油
The document discusses challenges in API culture, including bottlenecks and anti-patterns like silos and version churn. It advocates for product thinking over project paradigms to enhance durability and reusability of APIs by aligning organizational structures with domain capabilities. The proposed model shifts focus from compartmentalized projects to creating domain-oriented APIs, enabling integration to emerge naturally through API consumption.SOA to Microservices
SOA to MicroservicesChristian Posta
油
Christian Posta discusses the transition from SOA to microservices, emphasizing the importance of autonomy, scalability, and organizational agility in modern software architecture. He highlights the necessity of defining boundaries in complex domains and adopting eventual consistency using domain aggregates, along with the need for automation in deployment and monitoring. The document also presents various tools and frameworks that facilitate the implementation of microservices, including Kubernetes, Apache Kafka, and Spring Boot.Chicago Microservices Integration Talk
Chicago Microservices Integration TalkChristian Posta
油
This document discusses integration in the age of DevOps. It describes how microservices help solve the problem of decoupling services and teams to move quickly at scale. Apache Camel is presented as a solution for integration that allows for reliable and distributed integration through mechanisms like messaging. Kubernetes and Docker are discussed as platforms that help develop and run microservices locally and at scale by providing automation, configuration, isolation and service discovery capabilities.Intro to API Design Principles
Intro to API Design PrinciplesVictor Osimitz
油
An API is an interface that allows software components to interact and abstracts away complexity. When designing a system, getting the interfaces right is important. RESTful APIs follow principles like being stateless and using standard HTTP actions and errors to organize resources in a discoverable and uniform manner. APIs should focus on the data model and use standards like JSON and HTTP verbs, while pragmatically modifying REST principles only to ease the consumer's experience.GemStone/S @ Vienna University
GemStone/S @ Vienna University ESUG
油
GemStone/S was used to build a "Swiss Army knife" application to handle all administrative tasks for a university support organization with 25,000 customers. It provides services like campus software, student software, systems support, and account management. The application was implemented entirely within GemStone/S using its persistence, transactions, constraints, and access control features. It has a web interface built inside GemStone/S using a message passing paradigm. The development environment is accessed entirely through the secure web interface. The application handles around 370,000 hits per month and the machine it runs on is mostly idle, demonstrating it is stable, efficient, and supports rapid application development.OASIS OAXAL Presentation
OASIS OAXAL PresentationAndrzej Zydro MBCS
油
1. The document discusses the Open Architecture for XML Authoring and Localization (OAXAL) standard which encourages the use of open standards for XML authorizing and localization.
2. OAXAL provides a service-oriented architecture and template for how to integrate open standards for XML authoring and localization.
3. Implementing open standards through OAXAL can reduce costs, improve quality, and increase automation for XML localization.OAXAL
OAXALAndrzej Zydro MBCS
油
The document discusses OAXAL (Open Architecture for XML Authoring and Localization) and xml:tm (XML-based Text Memory) as standards for authoring and localizing XML documents. It provides an overview of related standards like DITA, ITS, TMX, SRX, GMX, and XLIFF. It then describes how xml:tm uses these standards and creates an XML namespace to embed contextual information, link source and target texts, and automate workflows for translation and localization of XML documents.More Related Content
What's hot (20)
Site speed Server Optimization
Site speed Server OptimizationShelly Fagin
油
The document discusses options for optimizing server performance including using alternative databases like MariaDB instead of MySQL, implementing caching at the page level and web server level using techniques like mod_pagespeed, using Nginx as a web server or reverse proxy, and load balancing. It promotes using these advanced techniques to achieve wicked fast website performance.Building & Testing Scalable Rails Applications
Building & Testing Scalable Rails Applicationsevilmike
油
This document discusses building scalable Rails applications. It covers using multiple Rails processes and servers to handle concurrent requests. It recommends optimizing database queries, caching, offloading long tasks, and serving static assets externally. It also provides tips for load testing including using realistic data and environments, considering location and caching effects, and paying attention to request headers.Solving trust issues at scale - Omer Levi Hevroni
Solving trust issues at scale - Omer Levi HevroniDevOpsDays Tel Aviv
油
The document discusses building a scalable authorization system that ensures trust across microservices using a zero-trust approach and least privilege principles. It highlights key components like the Envoy proxy and Open Policy Agent (OPA) for managing authentication and authorization, as well as the importance of audit logs and decision logging. The focus is on enabling developers to implement secure policies while minimizing the impact on development speed and complexity.Performance Testing w/ WebPage Test Private Instance (DrupalCamp Ohio)
Performance Testing w/ WebPage Test Private Instance (DrupalCamp Ohio)Bill Condo
油
The document covers performance testing for web pages, including definitions, challenges, and available tools such as WebPageTest and YSlow. It discusses key metrics like milestone timings, speed index, and various quantity and rule-based metrics. The presentation emphasizes the importance of setting up a proper testing environment and outlines next steps for improvement.ShopBack Catalog with Elastic
ShopBack Catalog with ElasticAlberto Resco P辿rez
油
The document outlines ShopBack's journey in enhancing their shopping platform using Elasticsearch for scalable product catalog and search functionalities. Key highlights include the transition to a multi-country, multi-language setup with improved performance and metrics collection, as well as lessons learned from the migration process. Future developments involve further optimizations like fuzzy matching, type-ahead suggestions, and machine learning applications for fraud detection.Dropping ACID: Wrapping Your Mind Around NoSQL Databases
Dropping ACID: Wrapping Your Mind Around NoSQL DatabasesKyle Banerjee
油
This document discusses NoSQL databases as an alternative to traditional relational databases. It provides an overview of different types of NoSQL databases like document stores, wide column stores, key-value stores and graph databases. It also discusses advantages of NoSQL databases like horizontal scalability and ease of use with large amounts of unstructured data, as well as disadvantages like lack of transactions and joins. The document recommends choosing a database based on the type of queries, data size, read/write needs, and whether the data needs to be accessed by other applications.EDF2013: Selected Talk S淡ren Roug: Reportnet a Case Study
EDF2013: Selected Talk S淡ren Roug: Reportnet a Case StudyEuropean Data Forum
油
Reportnet is a 14-year-old system that enables countries to upload and archive data, primarily in XML format, for about 400 reporting obligations. It includes features like automatic quality assurance (QA) and an online questionnaire, allowing users to validate and remix data more efficiently. Recent enhancements consider transitioning to a database with a REST web service to manage heterogeneous data and improve the semantic linking of vocabularies.Rosenblum Workflow Choices Introducing XML
Rosenblum Workflow Choices Introducing XMLNational Information Standards Organization (NISO)
油
The document discusses the importance of XML in modern publishing workflows, emphasizing its role in enhancing user experiences through responsive design, accessibility, and rich hyperlinks. It outlines the challenges and considerations involved in integrating XML into the publishing process, including managing vendor relationships and ensuring XML quality. The document further suggests evaluating business goals and developing standards to successfully implement XML solutions in publishing.Why real integration developers ride Camels
Why real integration developers ride CamelsChristian Posta
油
This document provides an agenda and summaries of key points from a presentation on integrating systems using Apache Camel. The presentation discusses how Apache Camel is an open-source integration library that uses enterprise integration patterns to connect disparate systems. It highlights features of Camel including components, data formats, and testing frameworks. Customer examples are presented that demonstrate large returns on investment and cost savings from using Camel for integration projects. The presenters argue that Camel provides flexibility, reusability and rapid development of integrations.Published in 1885 and shared on facebook
Published in 1885 and shared on facebookJoe Kepley
油
The Christian Science Publishing Society handles all publishing operations for the Christian Science Church. It publishes several periodicals, including the Christian Science Monitor, a daily newspaper, as well as weekly and monthly magazines. The project involves digitizing all back issues of these publications by scanning and converting articles to XML format in order to make the entire archives available online through a new digital platform. The goals are to grant subscribers access to the content while also allowing free sharing and access to selected articles. The project will use an agile methodology with phases and sprints to develop the new system incrementally.Integrating Alfresco with SharePoint & Drupal Using CMIS
Integrating Alfresco with SharePoint & Drupal Using CMISBenjamin Chevallereau
油
The document describes a solution for integrating Alfresco with SharePoint and Drupal using CMIS, allowing direct access to ECM repositories and enhancing document management features. It highlights the benefits of increased user adoption, elimination of content silos, and customization options for various platforms. Additionally, it outlines use cases such as collaboration, secure storage, and compliance applications, along with a sample business application demonstration.Hopkins Leveraging XML to Enhance Semantic Value of Standards
Hopkins Leveraging XML to Enhance Semantic Value of StandardsNational Information Standards Organization (NISO)
油
The document discusses the integration of XML to enhance the semantic value of standards in manufacturing. It emphasizes how standards are utilized as data rather than just documents, impacting various stakeholders such as engineers and IoT users. The content highlights the importance of usability and connected documentation in industrial processes.Service oriented architecture
Service oriented architectureKhaled Musaied
油
This document provides an orientation on SOA (Service-Oriented Architecture) and WCF (Windows Communication Foundation). It defines SOA as an architecture based on discrete software services providing functionality to other applications independently of vendor, product, or technology. A service is defined as a self-contained unit of functionality. WCF is introduced as a framework for building service-oriented applications that supports SOA principles like loose coupling and interoperability. The presentation includes an overview of SOA benefits and service design principles, as well as how WCF maps to the core components of SOA.Events in a microservices architecture
Events in a microservices architectureSaul Caganoff
油
The document discusses the integration of event-driven architecture with microservices, highlighting the challenges of maintaining consistency in distributed systems. It covers the importance of understanding service interactions, such as commands, queries, and events, along with trade-offs between orchestration and choreography. Additionally, it emphasizes the role of events in providing loose coupling and improving state communication across different system components.Building better SQL Server Databases
Building better SQL Server DatabasesColdFusionConference
油
This document provides an overview of a presentation on building better SQL Server databases. The presentation covers how SQL Server stores and retrieves data by looking under the hood at tables, data pages, and the process of requesting data. It then discusses best practices for database design such as using the right data types, avoiding page splits, and tips for writing efficient T-SQL code. The presentation aims to teach attendees how to design databases for optimal performance and scalability.Growing an API Culture - APIdays LIVE AU 2020
Growing an API Culture - APIdays LIVE AU 2020Saul Caganoff
油
The document discusses challenges in API culture, including bottlenecks and anti-patterns like silos and version churn. It advocates for product thinking over project paradigms to enhance durability and reusability of APIs by aligning organizational structures with domain capabilities. The proposed model shifts focus from compartmentalized projects to creating domain-oriented APIs, enabling integration to emerge naturally through API consumption.SOA to Microservices
SOA to MicroservicesChristian Posta
油
Christian Posta discusses the transition from SOA to microservices, emphasizing the importance of autonomy, scalability, and organizational agility in modern software architecture. He highlights the necessity of defining boundaries in complex domains and adopting eventual consistency using domain aggregates, along with the need for automation in deployment and monitoring. The document also presents various tools and frameworks that facilitate the implementation of microservices, including Kubernetes, Apache Kafka, and Spring Boot.Chicago Microservices Integration Talk
Chicago Microservices Integration TalkChristian Posta
油
This document discusses integration in the age of DevOps. It describes how microservices help solve the problem of decoupling services and teams to move quickly at scale. Apache Camel is presented as a solution for integration that allows for reliable and distributed integration through mechanisms like messaging. Kubernetes and Docker are discussed as platforms that help develop and run microservices locally and at scale by providing automation, configuration, isolation and service discovery capabilities.Intro to API Design Principles
Intro to API Design PrinciplesVictor Osimitz
油
An API is an interface that allows software components to interact and abstracts away complexity. When designing a system, getting the interfaces right is important. RESTful APIs follow principles like being stateless and using standard HTTP actions and errors to organize resources in a discoverable and uniform manner. APIs should focus on the data model and use standards like JSON and HTTP verbs, while pragmatically modifying REST principles only to ease the consumer's experience.GemStone/S @ Vienna University
GemStone/S @ Vienna University ESUG
油
GemStone/S was used to build a "Swiss Army knife" application to handle all administrative tasks for a university support organization with 25,000 customers. It provides services like campus software, student software, systems support, and account management. The application was implemented entirely within GemStone/S using its persistence, transactions, constraints, and access control features. It has a web interface built inside GemStone/S using a message passing paradigm. The development environment is accessed entirely through the secure web interface. The application handles around 370,000 hits per month and the machine it runs on is mostly idle, demonstrating it is stable, efficient, and supports rapid application development.Hopkins Leveraging XML to Enhance Semantic Value of Standards
Hopkins Leveraging XML to Enhance Semantic Value of StandardsNational Information Standards Organization (NISO)
油
Similar to OAXAL (7)
OASIS OAXAL Presentation
OASIS OAXAL PresentationAndrzej Zydro MBCS
油
1. The document discusses the Open Architecture for XML Authoring and Localization (OAXAL) standard which encourages the use of open standards for XML authorizing and localization.
2. OAXAL provides a service-oriented architecture and template for how to integrate open standards for XML authoring and localization.
3. Implementing open standards through OAXAL can reduce costs, improve quality, and increase automation for XML localization.OAXAL
OAXALAndrzej Zydro MBCS
油
The document discusses OAXAL (Open Architecture for XML Authoring and Localization) and xml:tm (XML-based Text Memory) as standards for authoring and localizing XML documents. It provides an overview of related standards like DITA, ITS, TMX, SRX, GMX, and XLIFF. It then describes how xml:tm uses these standards and creates an XML namespace to embed contextual information, link source and target texts, and automate workflows for translation and localization of XML documents.Open Standards
Open StandardsAndrzej Zydro MBCS
油
The document discusses open standards for localization and translation. It describes how standards enable greater interoperability, efficiency, and lower costs. It presents OAXAL, an open architecture for XML authoring and localization that uses various standards like XLIFF and TBX. OAXAL allows localization of content like English soccer articles into other languages around the clock in a browser-based workbench.LISA OASIS-feb2011
LISA OASIS-feb2011Jamie Clark
油
This document discusses international content standards developed by OASIS and LISA to remove communication barriers. OASIS is an international non-profit consortium with over 650 members and 70 technical committees producing open standards. Key OASIS standards discussed include DocBook for structured document authoring, DITA for modular topic-based information, CMIS for content management interoperability, and XLIFF for localization interchange. The document emphasizes that open standards must be publicly available, stable, published with open rules and processes, and have explicit intellectual property terms.DITA and Translation Best Praticices
DITA and Translation Best PraticicesAndrzej Zydro MBCS
油
The document discusses best practices for translating DITA (Darwin Information Typing Architecture) content and using the xml:tm (XML-based text memory) standard. It recommends using a CMS, avoiding translatable attributes, keeping topics granular, and using xml:tm to maintain author and translation memories for reuse and alignment between source and translated content. xml:tm allows embedding of contextual information to link source and translated text segments for more accurate matching.The Standards Mosaic Opening the Way to New Technologies
The Standards Mosaic Opening the Way to New TechnologiesDave Lewis
油
The document discusses the evolution of internationalization standards, particularly the integration of the Internationalization Tag Set (ITS) and XLIFF formats, in the context of new technological advancements such as the Semantic Web and machine translation. It outlines the emerging requirements for localization, including finer granularity and various serializations, while emphasizing the importance of linked data and quality in training data for language technology. Additionally, it highlights collaborative efforts and community groups aimed at enhancing language technology through shared resources and best practices.Dos and donts
Dos and dontsAndrzej Zydro MBCS
油
The document discusses best practices and common issues when localizing XML documents, including using standard libraries and formats like XLIFF, avoiding issues with word substitution, translatable attributes, and encoding, and marking non-translatable text. It also promotes the use of standards for interoperability and the Open Architecture for XML Authoring and Localization framework.Ad
More from Andrzej Zydro MBCS (8)
Xtm webinar presentation xtm system overview
Xtm webinar presentation xtm system overviewAndrzej Zydro MBCS
油
This webinar provides an overview of the XTM translation management system. It discusses the translation process and requirements of project managers, clients, and linguists. XTM is presented as a complete translation ecosystem that can help collaborators work more efficiently through real-time data sharing and tracking. The webinar agenda includes a demonstration of XTM's features and a question and answer session.Falcon
FalconAndrzej Zydro MBCS
油
The document discusses the FALCON project, which aims to enhance the digital single market by integrating open data with language technologies for better localization solutions. It highlights the challenges of customer engagement across multilingual terrains and the need for SMEs to adopt systematic multilingual approaches. Additionally, it mentions the company's decision to reduce production capacity for certain appliances while outlining methods to manage linguistic resources and improve terminology management.Understanding linport
Understanding linportAndrzej Zydro MBCS
油
The document discusses language interoperability and standards for translation projects. It introduces the Language Interoperability Portfolio (Linport), an open format for translation containers. It also describes the Translation Interoperability Protocol Package (TIPP), a standard proposed by the group Interoperability Now to enable full interoperability between translation management systems. TIPP uses a ZIP container with a manifest and payload to package translation assets like XLIFF files, terminology, and specifications. The document advocates for TIPP and the XLIFF:doc subset as solutions to issues with roundtripping between tools and a lack of standardization.The tipping point
The tipping pointAndrzej Zydro MBCS
油
The document discusses the evolution of machine translation technology from early systems in the 1950s to modern statistical machine translation approaches. It outlines key developments like increased processing power, large aligned text corpora, and integration with other language technologies. While making progress, current statistical MT still has limitations in areas like morphology, syntax and ambiguity. The document proposes that future advances may require new approaches inspired by neuroscience understanding of human intelligence and the brain's hierarchical temporal memory architecture.Interverbum falcon-10oct14-az
Interverbum falcon-10oct14-azAndrzej Zydro MBCS
油
This document discusses building the localization web by publishing localization data on the semantic web using W3C standards. This enables terms and translations to become linkable resources that can add value when leveraged for machine translation and text analytics. The localization web is envisioned as a decentralized, annotated global translation memory and term base. Examples of use cases involving publishing linguistic data as linked open data are provided, as well as how different language resources, technology, and workflows are interdependent in the language lifecycle.Easyling xtm lt-innovate joint-final
Easyling xtm lt-innovate joint-finalAndrzej Zydro MBCS
油
Website translation made easy is a presentation that discusses the $3.5 billion website translation market which is currently only accessible to large language service providers with significant IT resources. It introduces Easyling, which extracts content from websites, translates it contextually, and delivers the translated content without hassle through an integrated solution that provides real-time previews and publishing through the power of Easyling in XTM's editor and translation proxy. The presentation highlights key features such as being CMS independent and scalable through Google's CDN, as well as being SEO friendly.DITA for Localization
DITA for LocalizationAndrzej Zydro MBCS
油
This document discusses better translation technology and DITA localization. It begins by describing the early history of technical documentation formats. It then discusses how XML and standards like DITA improved the situation by enabling modularity, reuse, and translation of content. The document outlines benefits of DITA like writing once and translating once, but also challenges like word substitution and specialization. It recommends focusing DITA on its intended use of modular technical documentation and avoiding overuse of features like substitution. The contact details of the author are also provided.The Tipping Point
The Tipping PointAndrzej Zydro MBCS
油
The document discusses the evolution of machine translation technology from early systems in the 1950s to modern statistical machine translation approaches. It outlines key developments like increased processing power, large datasets, and integration with other tools. While making progress, current statistical MT still has limitations in areas like syntax, morphology, and context. The document suggests future systems may need a new approach, discussing neuroscience concepts like hierarchical temporal memory as a way to better simulate human intelligence.Ad
OAXAL
- 1. OAXAL Open Architecture for XML Authoring and Localization Andrzej Zydro: azydron@xtm-intl.com November 2010
- 9. Usability
- 10. Interoperability
- 11. 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
- 12. Why Open Standards? Usability Interoperability Exchange Risk reduction Investment protection Reduced implementation costs
- 13. Why Open standards Free no fees Input is from accredited volunteers Democratic process Extensive peer review Extensive public review Well documented
- 14. 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
- 15. Localization Standards Standards matter Reduce costs Improve interoperability Improve quality Create more competition
- 16. True Cost of Translation
- 17. Localization without Standards Customer source text source text extract extracted text tm process prepared text translatetranslated text target texttarget text merge target text QA Update tm
- 18. 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
- 20. Open Architecture for XML Authoring and Localization (OAXAL) OASIS TC Standard http://docs.oasis-open.org/oaxal/V1.0/oaxal-v1.0.html
- 21. Why OAXAL? Encourage the use of Open Standards for XML Authoring and Localization Provide a SOA Architecure for XML Authoring and Localization Provide a template of how to integrate Open Standards for XML Authoring and Localization
- 23. Putting it all together: OAXAL
- 24. OAXAL OAXAL enables Open Architecture approach Open Standards - Open APIs Easy Exchange Modular design Interoperability Very high level of automation
- 25. OAXAL Workflow source text extract extracted text tm process XLIFF file translate target text merge Internet exact matching leveraged matching Automated Workflow web browserweb browserQA Automated Workflow Update tm
- 26. 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
- 27. XML CONT ENT Document Creation Document Creation QA/Post-EditQA/Post-Edit LocalizationLocalization Source Document Lifecycle AuthoringAuthoring PublishPublish Publish Localized Publish Localized
- 29. 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
- 30. 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
- 31. 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
- 32. 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
- 33. 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
- 34. OAXAL In Action
- 36. OAXAL TC http://www.oasis-open.org/committees/oaxal OAXAL 1.0 Reference Reference Model: http://www.l24.cm/OAXAL /