[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: XLIFF 2.0 and multiple <file> elements
Hi TC members,
I see little benefit to having multiple <file> elements within a single XLIFF container unless there is some higher level data above the <file> elements common to all <file>s. Do any of you know of tools making use of multiple files at all within a single XLIFF container?
I do see a benefit if we have some common data shared between the various file-level resources within the container.
Our current 1.2 model is something like:
<xliff>
<file original='myfile.txt'>
<header> .. </header>
<body> .. </body>
</file>
...
<file>...</file>
</xliff>
I suggest we either go to a model where <xliff> becomes the 'file-level' element, for example:
<xliff original='myfile.txt'>
<header> .. </header>
<body> .. </body>
</xliff>
or, we use <xliff> as a richer container with meta data, for example:
<xliff>
<header>
// workflow data
// tool information
// other meta-data relating to the whole container
</header>
<files>
<file original='myfile.txt'>..</file>
</files>
</xliff>
I'll put in a feature page on the wiki for this if there's interest in the committee on something like this, so please reply to this thread if you have any input.
cheers,
asgeir
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]