CMS Neutral External ITS Rules and Readiness

From MultilingualWeb-LT EC Project Wiki
Jump to: navigation, search

1 Summary

This implementation demonstrates how external global ITS rules can be handled through the OASIS Content Management Interoperability Services (CMIS) API vendor neutral CMS interaction. In this use case ITS meta-data is use to solve the following problems:

  • Externally associate individual ITS rules with multiple documents using CMIS
    • Benefit:Provides a vendor-neutral way of applying one or more ITS rules, with precedence ordering, to a specific set of documents without editing those documents. Allows content managers to easily maintain large ITS rule-sets as applied to sets of documents, e.g. groups by specific schema or meta-data usage.
    • The implementation has been tested with ITS translate rule, but the same approach could be applied to any data category with an global rule.
  • External Monitoring CMS for updates to documents that trigger further processing.
    • Benefit:In situations where content is being continuous authored, revised and then translated, this allows TMS to monitor all relevant document and retrieve in a timely manner any that need to undergo translation or translation review. Thereby ensures consistency between a changing source content and content submitted for localization.
    • Uses a proposed version of the readiness attribute suggested in the ITS Requirements and Use Case document.

2 Use Case Description

While ITS supports interoperability of internationalization, localization and language technology processes operating over individual HTML and XML documents, it does not provide strong support for interoperability when performing such processes over multiple document. Such document group support may however ease the consistent application, processing and maintenance of ITS rules over multiple documents with similar schema, e.g. a large number of DITA or HTML documents making up an online user manual, by using external ITS rules.

Further, enterprises also find themselves operating such processes of files stored in different CMS products from different vendors. Similarly, LSPs, operating such processes as services that interface directly with customer CMS must find ways to interoperate with multiple CMS types. As CMS typically only offer proprietary APIs for accessing document, enterprises and LSPs must bear the cost of developing adaptor from their systems to these APIs.

This use case demonstrates a solution to both these classes of problems based on the Content Management Interoperability Services (CMIS)recently developed at OASIS. This use case supports the following actors:

  • Client-based Localization Manager who is preparing batches of source documents on a CMS for localization by applying and revising different ITS rules to all or sub-sets of document.
  • Client-based Localization Manager who needs to signal to a Translation Process Manager that specific documents are now ready for translation.
  • Content Authors who need to signal to a translation process manager that specific source documents have been revised and therefore need re-transaltion
  • Translation Process Manager who need to monitor the availability or revision of source document in order manage the allocation of translation resources in an efficient and timely manner.

This use case therefore illustrate potential new interoperability between CMS and Translation Management Systems, Content Authoring Tools, Source Quality Assurance Tools and Machine Translation Services.

3 Use Case Implementation

This demonstration is an initial prototype involving the following components developed at TCD by Master's student Aonghus Ó hAirt

  • ITS-aware CMS:
    • An aspect-oriented extension to the CMIS implementation of the Alfresco open source content management platform to enable object to support ITS rule meta-data for document objects
  • Content readiness monitor:
    • A polling monitor that uses CMIS queries to detect sought changes in document status and altering any registered listeners with a configurable notification
  • Content readiness listener:
    • A test client that can receive document object readiness notification from the content readiness monitor

Limitations: This implementation is configured for functional and performance testing rather than interactive use in content management. Currently only translate ITS rules are supported, though the implementation is readily extensible to other rules

4 Use Case Demonstration

  • Status:initial concept and performance testing prototype available
  • Demonstration:TO BE PROVIDED. See overview slides
  • ITS Data Categories:translate

5 Interoperability Behaviour

A step by step description of the demonstration, giving examples of how content and data is passed between components as visible at the interoperability points identified in the systems description. Any initial assumptions about the state of the system should be clearly stated. These examples should be consistent with each other from step to step so that the the outcomes of various ITS-related processing can be clearly understood. A short explanation should be provided for each step, hihglighting the role of the ITS data categories used.