- General Information
- Connecting Third-party Systems
- crossConnect for content systems
- crossConnect for External Editing
- Purpose and usage
- Across XLIFF format
- Across-specific Extensions
- <xliff> Element Attributes
- <file> Element Extensions
- <trans-unit> Element Extension
- Paragraph States
- Paragraph State Flags
- <source> and <target> Element Content
- <bpt> Element Attributes
- <ph> Element Attributes
- <x> Element Attributes
- Across-specific Properties
- Analysis Results
- Sample Files
- Across XLIFF - import, export and segmentation
- Context information
- Exporting best matches in Across XLIFF
- Hyperlinks to XLIFF
- Secure file handling with C#
- Secure file handling with JAVA
- Workflow and vendor configuration
- Sample code - Integrated solution
- Across XLIFF format
- Generic File Connector
- Display Texts
- Solution approaches
- The Across solution in detail
- The display text format
- The display text package
- APIs - Technology
- crossTank API v1
- crossTank API v2
- crossTerm API v1
- crossTerm API v2
- crossAPI SI
- Function Return Types
- crossAPI SI and Java
- List of Objects in crossAPI SI
- ObjectManager - Overview
- ProjectManager - Overview
- WanGridManager - Overview
- Sample - transferring checkout files via FileManager
- Sample - VBS
- Text Preprocessing API
crossTerm API v1
The crossTerm API v1 provides read access to local content of the terminology management database crossTerm.
crossTerm API v2 provides read/write access to local crossTerm content, enriched by various search possibilities. In contrast to v1, v2 requires to log in as a specific user and respects the rights of this user.
- crossTerm is a terminology management system. In general, the advantages of creating and maintaining a terminology database are:
- Represent knowledge (of a specialized field, of a company, of an industry...)
- Make knowledge accessible
- Facilitate monolingual and multilingual specialized communication and translation
- Settle and promote standards with respect to terminology usage ("word choice"), for example, to forge a corporate identity by consistent wording.
- The different levels and types of crossTerm contents are:
- Instances: These can be viewed as separate dictionaries with their own data model, represented by crossTerm data categories. Data Categories define the properties that contents of the instance might have.
- Entries: In the world of crossTerm, an entry represents a concept (any concrete or abstract thing or process)
- Each entry belongs to exactly one crossTerm instance.
- Entries can have meta data in the form of properties (instantiations of data categories) and attachments. Examples: Definition; Image (figure).
- An entry typically holds a set of terms designating the concept.
- Terms: A term designates ("labels") a concept with a natural language string ("word") in one language.
- Each term belongs to exactly one entry.
- Terms can have meta data in the form of properties (instantiations of data categories) and attachments. Examples: Part of speech; Term type.
- Each term has a language code.
- Terms belonging to the same entry can be regarded as synonyms (if their language code is identical) or translation equivalents (if their language code is different).
By default, crossTerm contains one instance with a set of pre-defined data categories. These are in line with the Term Base eXchange (TBX) standard, (identical to ISO 30042:2008).
This diagram shows how a crossTerm database is subdivided into instances, which hold entries that in turn may have one or more terms in different languages.
The following diagram illustrates how terms may be grouped into entries. Since "shoe lace" and "shoe string" in English both refer to the same concept, they are in the same entry. Similar, in German, there are also two terms referring to this concept ("Schnürband" and "Schnürsenkel"). The terms in different languages belonging to the same entry are translations of each other.
As part of the installation the API documentation is deployed. This documentation is always up to date and describes the functionalities of the installed API.
You can open the documentation at the server with this default URL: