Versions Compared

Version Old Version 10 New Version 11
Changes made by

Stefanos Kargas (Unlicensed)

Stefanos Kargas (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Until TermWeb version 3.17.8 not all concept/term fields are included in the decoration, but specifically the following:

SourceFieldReturns AsCommentsDate Implemented
Source Term

Source Term Id

sourceTermId
Initial version
Source Term

Source Concept Id

sourceConceptId
Initial version
Source Term

Source Term (name)

sourceTerm
Initial version
Target Term

Target Term Id

id
Initial version
Target Term

Target Concept Id

conceptIdIt should be the same as Source Concept IdInitial version
Target Term

Target Term (name)

tgt
Initial version
Target Term

Modified By

modifiedBy
Initial version
Target Term

Modified Date

modifiedDate
Initial version
Target Term

Client Name

customer
Initial version
Target Term

Domain Name

domain
Initial version
Target Term

Term Definition

definition
Initial version
Target Term

Term Usage Status

status
Initial version
Target Term

Term Process Status

processStatus
Initial version
Target Term

Term Context

context
Initial version
Target TermTerm Referencereference
Initial version
Target TermTerm Remarksremarks
Initial version
Target TermIndication whether Term is an abbreviationabbreviation
Initial version
Target TermIndication whether Term is deprecateddeprecatedAccording to TBX standards and custom template configuration of deprecated field/value20-10-2016 (3.17.3)
Target TermIndication whether Term is acceptedacceptedAccording to custom template configuration of accepted field/value15-2-2017 (3.17.4)


Starting from Since TermWeb version 3.17.8 all concept and term fields are included in the decoration.

...

Decoration takes a text segment as a source with a specific source language and 'decorates' it with term translations to another specific target language. Decorated terms are marked with <mrk> XML tags. Different cases and features during decoration are described here:

  1. When the input segment contains itself XML tags, like XLIFF tags, then these are ignored before searching for term translationsas the decoration is concerned. Firstly they are being parsed and removed from the segment. Then the decoration algorithm adds the translated terms to the segment and finally the removed XML tags are being added back to the decorated segment to the appropriate places. If the XML tags come in conflict with the <mrk> tags, then they get split. The <mrk> tags never get split, because one <mrk> tag always represent one translated term and splitting the XML tags <mrk> tags would affect the result of the decoration. Split XML tags, especially XLIFF tags with ids, might create inappropriate formats. This is why they should be handled by the user who receives the response.
  2. There are cases where multiple terms sharing common words are eligible to be included in the decoration. In this case not all of them can be included. Instead the longest one in characters is prioritized.