Browse Prior Art Database

Extending RAS to support multilingual assets

IP.com Disclosure Number: IPCOM000129008D
Original Publication Date: 2005-Sep-26
Included in the Prior Art Database: 2005-Sep-26
Document File: 2 page(s) / 31K

Publishing Venue

IBM

Abstract

The Reusable Asset Specification (RAS http://www.omg.org/cgi-bin/doc?ptc/2004-06-06) does not provide multi-language support for an asset. This solution extends the Reusable Asset Specification to include localization. It enables an asset to be expressed using multiple languages by adding a localized extension to every existing section and subsection.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 91% of the total text.

Page 1 of 2

Extending RAS to support multilingual assets

The Reusable Asset Specification (RAS http://www.omg.org/cgi-bin/doc?ptc/2004-06-06
) does not provide multi-language support for an asset. The only workaround would be to duplicate the asset in other languages.The drawbacks of the workaround are: lag time in acquiring assets in other languages; inability to use assets in multi-language environment on demand; storage of entire asset in every language needed. Our solution allows instant multi-language asset assembly with only the specified, necessary elements of an asset localized.

The diagram below illustrates our solution.

The top block in the diagram is the asset section of the Default RAS profile. (Note: The asset section of the Default RAS profile is used as an example. The asset-localizer can be added to any section in a RAS profile.)

The rest of the diagram describes the extension that is the essence of our solution.

The "asset-localizer".

The asset-localizer has a "default-locale", which is the locale of the original section, and also has an optional array of localized-attributes.

The "localized-attribute".

Each localized-attribute specifies the "translation" which is the name of the field within the section that is translated, for example "name" in the asset section.

Each localized-attribute also specifies a "reference". The reference may either be the id of a localized string asset, or "self", which indicates that an array of translations is available.

The "tra...