[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Implementation Option: <segment> inside <trans-unit>
Hi all, This email is to kick off the thread discussing the option
of representing segmentation in XLIFF though a new <segment> element at
<trans-unit> level. This is the representation used throughout my samples
in the document I wrote to develop the process and use cases for segmentation
in XLIFF (http://www.oasis-open.org/apps/org/workgroup/xliff-seg/download.php/6067/Case%20for%20Segmentation%20in%20XLIFF%20Draft%201.zip). The idea is to allow optional <segment> elements
directly below the <trans-unit>, where each segment contains a
<source> and optional <target>, <alt-trans> etc. The
functionality of the <trans-unit> remains the same as in today’s
XLIFF implementation. Here are some pros and cons that I can think of with this
model: Pros:
Cons:
NOTE: On the compatibility issue, is it not reasonable to
assume that the use of a new feature in a future version of XLIFF may break forward
compatibility with an earlier version? That is at least the case with XLIFF 1.1
vs. XLIFF 1.0 – new tags can be used in XLIFF 1.1 that would have to be
removed for the content to be compatible with XLIFF 1.0. After all, if no new
elements or new structure were introduced there would be no need for a new
version… Cheers, Magnus |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]