ITS 2.0 / XLIFF 2.0 implementation

Hi all,

 

Here is an update on the current status of the Okapi implementation of the mapping of ITS 2.0 in XLIFF 2.0:

 

As you may recall, the data categories are classified into several types:

 

- Existing in XLIFF <http://www.w3.org/International/its/wiki/XLIFF_2.0_Mapping#Data_Categories_Existing_in_XLIFF> 

- Partially Covered in XLIFF <http://www.w3.org/International/its/wiki/XLIFF_2.0_Mapping#Data_Categories_Partially_Covered_in_XLIFF>


- Represented using ITS Itself
<http://www.w3.org/International/its/wiki/XLIFF_2.0_Mapping#Data_Categories_Represented_Using_ITS_Itself> 

- Not Representing Metadata <http://www.w3.org/International/its/wiki/XLIFF_2.0_Mapping#Data_Categories_Not_Representing_Metadata> 

 

Note that several data categories have not been mapped at all yet:

http://www.w3.org/International/its/wiki/XLIFF_2.0_Mapping#Data_Categories_Not_Mapped_Yet

 

The library aims at implementing only the data categories that are partially covered in XLIFF or the ones represented using ITS
itself. The ones existing in XLIFF are simply accessible through the normal XLIFF API, and the ones not representing metadata are
just not useful in an XLIFF API.

 

Currently the library implements:

 

- Domain

- MT Confidence

- Terminology

- Text Analysis

- Provenance(*)

- Localization Quality Issue(*)

 

*: Both Provenance and LQI have some restriction currently: stand-off notation is supported within units only.

 

In addition, currently, the standoff notations are processed so they are assigned to their referrers directly. That is once the
reference is parsed the data exist in that object but not as a separate standoff object anymore. This cause the fragment
identification function to not find them if you try (because they are not standoff anymore: they are parsed and assigned to the
objects they were applied too). I'll have to refactor this to work with some kind of backing store and indirect access from the
referencing objects. That, hopefully, would be transparent from the caller of the API.

 

As usual you can get the library here:

http://okapi.opentag.com/snapshots/okapi-xliffLib_all-platforms_1.0-SNAPSHOT.zip

 

The Java documentation is here:

http://okapi.opentag.com/xlifflib/javadoc/

 

And all the project's information here:

https://code.google.com/p/okapi-xliff-toolkit/

 

Feedback and bug reports are welcome.

 

Thanks,

-yves