xliff-inline — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Sample for metadata inline representation
Hi Yves/all,
The samples for the requirement http://wiki.oasis-open.org/xliff/OneContentModel/Requirements#Mustallowtoassociatespansofcontentwithmetadata are
1. flag indicating the span must not be translated
2. flag indicating the span is a term
3. Reference ID used to point to external annotation
4. Translator comment
5. Tool-specific processing instructions
To me, the most natural choice for 1., 2. (to a certain degree 3.) and 4. would be W3C ITS. This choice would fit with our mantra "Don't reinvent the wheel".
1. flag indicating the span must not be translated
<unit id='1' xmlns:its=" http://www.w3.org/2005/11/its" ;>
<!-- Of course, the namespace declaration for ITS might be able to go elsewhere - no need to have it on each "unit" -->
<segment>
<source>It would certainly be quite a <youNameIt its:translate="no">faux pas</youNameIt> ... </note></source>
...
</unit>
2. flag indicating the span is a term
<unit id='1' xmlns:its=" http://www.w3.org/2005/11/its" ;>
<!-- Of course, the namespace declaration for ITS might be able to go elsewhere - no need to have it on each "unit" -->
<segment>
<source>... on the origin of <tb its:term its:termInfoRefPointer='t1'>modern novel</tb> ... </note></source>
...
<termDefs>
<termDef id='t1'>Info about the term 'modern novel'</termDef>
</termDefs>
</unit>
3. Reference ID used to point to external annotation
Not sure that ITS already has something like this. However, the Resource Description Format (RDF) has :-) Here's a fictional example that show how to use RDF (in connection with Dublin Core) to attach meta data on the XLIFF file level. The example does not point to an external annotation. However, that's of course possible with RDF as well.
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
<file original="hello.txt" source-language="en" target-language="fr" datatype="plaintext">
<header>
<rdf:RDF xmlns:dc=" http://purl.org/dc/elements/1.1/" ; xmlns:rdf=" http://www.w3.org/1999/02/22-rdf-syntax-ns#" ; xmlns:xsd=" http://www.w3.org/2001/XMLSchema#" ; xmlns:sls-prod=" http://www.sap.com/sls/1.0#" ;>
<rdf:Description rdf:about="&res;5a04a406b4a511dd80a80019bbd3174047ade3870fad11ddaa4d0019bbd31740">
<dc:title xml:lang="en-US" rdf:datatype http://www.w3.org/2001/XMLSchema#string" ;>XSR Test Object 1</dc:title>
</rdf:Description>
</rdf:RDF>
</header>
<body>
<trans-unit id="hi">
<source>Hello world</source>
</trans-unit>
</body>
</file>
</xliff>
4. Translator comment
<unit id='1' xmlns:its=" http://www.w3.org/2005/11/its" ;>
<!-- Of course, the namespace declaration for ITS might be able to go elsewhere - no need to have it on each "unit" -->
<segment>
<source>... without mentioning <note its:locNote='Comments about the two cited stories.' origin='author'>the ... </note></source>
<!-- Unfortunately, I currently don't know what to do about the "origin". RDF here as well? -->
...
</unit>
5. Tool-specific processing instructions
See 3. (use RDF).
Cheers,
Christian
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]