OpenTMS: Difference between revisions

Line 27: Line 27:


The following core models are identified:
The following core models are identified:
* '''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).
* '''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).
* '''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.
* '''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.
* '''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.
* '''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.
* '''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.
* '''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.
* '''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.
* '''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.
* '''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.
* '''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.
* '''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.
* '''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.
Line 53: Line 53:
There are several downloads available:
There are several downloads available:
# A [[Virtual machine|VM]] for Sun [[VirtualBox]] is hosted here: [openTMS http://www.opentms.de/?q=node/29]. This download also contains a [[php]] based Web [[Graphical user interface]].
# A [[Virtual machine|VM]] for Sun [[VirtualBox]] is hosted here: [openTMS http://www.opentms.de/?q=node/29]. This download also contains a [[php]] based Web [[Graphical user interface]].
# A Windows installer (containing the XML-RPC server) is hosted here: [openTMS Windows Installer http://www.heartsome.de/arayatest/opentmsserver.exe]
# A [[Windows Installer|Windows installer]] (containing the XML-RPC server) is hosted here: [openTMS Windows Installer http://www.heartsome.de/arayatest/opentmsserver.exe]
# A version integrated in the Araya XLIFF Editor can be found here: [Araya XLIFF Editor with openTMS plugin Windows Installer http://www.heartsome.de/en/freearaya.php]
# A version integrated in the Araya XLIFF Editor can be found here: [Araya XLIFF Editor with openTMS plugin Windows Installer http://www.heartsome.de/en/freearaya.php]