Standards-based representation of term translations based on XLIFF 2.1 Resource Data Module (and Linguistic Linked Open Data) in XLIFF 1.2

Hi,

As an alternative to the route sketched in https://lists.oasis-open.org/archives/xliff-comment/202007/msg00001.html
 (Standards-based representation of term translations based on XLIFF 2.1 glossary module in XLIFF 1.2), I also explored a standards-based representation of term translations based on XLIFF 2.1 Resource Data Module (and JSON-LD).

I wonder if the XLIFF 2.1 Resource Data Module could be used as indicated below .

 

Cheers,

Christian

 

==

The first example in
http://docs.oasis-open.org/xliff/xliff-core/v2.1/os/xliff-core-v2.1-os.html#resourceData_module
 exemplifies 

a. how to use a <resourceData> module at <file> level to reference an external file

b. how to use a <resourceItemRef> element contained in the <resourceData> module at <unit> level to refer to a.

In the context of term translations, from my understanding this facilitates XLIFF such as

<file>

     
<res:resourceData

     
xmlns:res="urn:oasis:names:tc:xliff:resourcedata:2.0">

            
<res:resourceItem
id="termbase-concept-1"

                  
mimeType="application/ld+json"
context="no">

                  
<res:source
href="termbase-extract.json"
/>

                  
<res:target
href="termbase-extract.json"
/>

            
</res:resourceItem>

     
</res:resourceData>

     
<trans-unit
id="1">

            
<source>

                   This indicator is only necessary for

                  
<mrk
id="m1"
mtype="term"
type="itsm:generic"

                        
its:taIdentRef="termbase-concept-1"

                  
xmlns:its="http://www.w3.org/2005/11/its">manual depreciation</mrk>

                   .

            
</source>

     
</trans-unit>

</file>

This is meant to capture the following:

1. Something that has been marked as a term: <mrk> element

2. Supplementary information about the term is provided by the "Text Analysis" data category of the W3C Internationalization Tag Set (see
https://www.w3.org/TR/its20/#textanalysis): 'type=
 "itsm:generic"' and 'its:taIdentRef="termbase-concept-1"'

3. 'its:taIdentRef="termbase-concept-1"' is used as identifier for a <resourceItem> on <file> level

4. The actual resource for <source> and <target> respectively is a JSON-LD (see
https://www.w3.org/TR/json-ld11/) file: termbase-extract.json

5. The JSON-LD file holds information (about single language terms, and translation equivalences) - adhering to Linguistic Linked Open Data (LLOD) principles (see
https://en.wikipedia.org/wiki/Linguistic_Linked_Open_Data)
 - from a "concept-oriented terminology database"

{

     
"@context": 
{

            
"dct": "http://purl.org/dc/terms/",

            
"dcterms": 
"http://purl.org/dc/terms/",

            
"ontolex": 
"http://www.w3.org/ns/lemon/ontolex#",

            
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",

            
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",

            
"skos": "http://www.w3.org/2004/02/skos/core#",

            
"vartrans": 
"http://www.w3.org/ns/lemon/vartrans#",

            
"xsd": "http://www.w3.org/2001/XMLSchema#"

     
},

     
"@graph": 
[

            
{

                  
"@id": "http://www.example.com/def/termbase/concept-1",

                  
"@type": "skos:Concept",

                  
"skos:exactMatch":
{

                         
"@id": "https://www.wikidata.org/wiki/Q114403"

                  
}

            
},

            
{

                  
"@id": "http://www.example.com/def/termbase/term-1",

                  
"@type": "ontolex:LexicalEntry",

                  
"dcterms:language":
{

                         
"@id": "http://lexvo.org/id/iso639-1/en"

                  
},

                  
"ontolex:canonicalForm":
{

                         
"@id": "wr-1",

                        
"ontolex:writtenRep":
{

                               
"@language": 
"en",

                               
"@value": 
"manual depreciation"

                         
}

                  
},

                  
"ontolex:denotes":
{

                         
"@id": "http://www.example.com/def/termbase/concept-1"

                  
},

                  
"vartrans:translatableAs":
{

                         
"@id": "http://www.example.com/def/termbase/term-2"

                  
}

            
},

            
{

                  
"@id": "http://www.example.com/def/termbase/term-2",

                  
"@type": "ontolex:LexicalEntry",

                  
"dcterms:language":
{

                         
"@id": "http://lexvo.org/id/iso639-1/de"

                  
},

                  
"ontolex:canonicalForm":
{

                         
"@id": "wr-2",

                        
"ontolex:writtenRep":
{

                               
"@language":
"de",

                               
"@value": 
"Manuelle Abschreibung"

                         
}

                  
},

                  
"ontolex:denotes":
{

                         
"@id": "http://www.example.com/def/termbase/concept-1"

                  
},

                  
"vartrans:translatableAs":
{

                         
"@id": "http://www.example.com/def/termbase/term-1"

                  
}

            
}

     
]

}

Of course, one could also encode this in an XML file, rather than a JSON one.

Another option would be to have the LLOD encoded information within the XLIFF file - possibly by having something like

<htm:script type='application/ld+json;profile="">http://www.w3.org/ns/anno.jsonld"'>

at an extension point.

Aside: Julia Bosque-Gil and John McCrae assisted to get the LLOD information of the example in shape, and Felix Sasaki brainstormed options to get it into XLIFF 1.2