OpenTMS: Difference between revisions
Added Model information |
|||
| Line 1: | Line 1: | ||
'''openTMS''' is an Acronym for "Open Source Translation Management System". The main web site of openTMS is [www.opentms.de http://www.opentms.de] | '''openTMS''' is an Acronym for "Open Source Translation Management System". The main web site of openTMS is [www.opentms.de http://www.opentms.de] [[File:OpenTMS.jpg|thumb|openTMS Logo]] | ||
==Goals== | ==Goals== | ||
| Line 12: | Line 13: | ||
The following core models are identified:<br /> | The following core models are identified:<br /> | ||
• Security model<br /> | • Security model: This model describes the security aspects and requirements of OpenTMS. Other models use the security model to allow or restrict the access to OpenTMS specific functions. OpenTMS uses a security model which on the one side secures the communication channel and on the other side secures data (e.g. the value of elements in an xml file or the values in a property file).<br /> | ||
• Document model<br /> | • Document model: The document model describes the core documents used in OpenTMS. Basically this is based on XLIFF and TMX. The document model also could be seen as part of the data model but due to the importance of documents as one of the core output produced by the translation and localization process they are modeled separately.<br /> | ||
• Process model<br /> | • Process model: This model implements the functions (combined finally into applications – see application model) of the OpenTMS, e.g. a converter or a translation memory search.<br /> | ||
• User model<br /> | • User model: This model realizes the user and its representation in the OpenTMS. The user model works in tight connection with the security. User does now only imply human users, but also other processes. User models have rights attached to them which in turn support the security model of OpenTMS.<br /> | ||
• Data model<br /> | • Data model: Basically this model implements the database side of OpenTMS. It uses a generalized database model, called data sources. Data sources are any kind of storage media for data, starting from plain text files towards SQL and other types of databases.<br /> | ||
• GUI model<br /> | • GUI model: This model specifies editors and other functionality which requires a GUI. The GUI model is not further detailed in the architecture specification here. The GUI model should be defined in a separate document.<br /> | ||
• Interface model<br /> | • Interface model: The model describes how to extend OpenTMS with new models. The Interface model is an abstract model and needs further inspection. An example of such an extension is the interface to CMS systems. Interface models are also of quite importance as they serve as the connection to other applications (e.g. Web servers, CMS systems) and in general to scripting languages like Perl, PHP etc.<br /> | ||
• Application Model: This model realizes programs, which performs tasks like translation etc.<br /> | |||
On top of those models the application model organises real applications (like the GUI model). | On top of those models the application model organises real applications (like the GUI model). | ||
openTMS uses a data source in the data model which organises the access to databases or any other kind of devices which allows to store (TM, [[terminology]], even [[machine translation]]) data. Currently the following data sources are supported: TMX files, XLIFF file, [[SQL]] databases. Data sources have to implement a set of methods based on the data source interface. | openTMS uses a data source in the data model which organises the access to databases or any other kind of devices which allows to store (TM, [[terminology]], even [[machine translation]]) data. Currently the following data sources are supported: TMX files, XLIFF file, [[SQL]] databases. Data sources have to implement a set of methods based on the data source interface. | ||