XLIFF Wiki |
![/!\](/modern/img/alert.png "/!\"){kind=small}
The following content is a draft and may not represent the view of the XLIFF TC.
1. Ideas for XLIFF 2.0
This is a list of ideas collected for XLIFF 2.0
1.1. Change Tracking / Version Control
Importance: Uncategorized
Category: Data Model, Extension
XLIFF 1.2 has preliminary support for change tracking through the <phase> element and phase-name attribute. However, it doesn't support all features, e.g. what if I want to know in which process the merged-trans attribute was set for a <group>?
1.2. Document-centric Localisation
Importance: Uncategorized
Category: Data Model, XML Schema
XLIFF 1.2 is in many ways a resource-centric approach to translation, and doesn't take into account some of the needs in document-centric translation, such as e.g. reordering of paragraphs, 1-n, n-1 and n-n translations. Is there a need or a case for developing a document-centric and a resource-centric extension, with a common core schema?
1.3. Native support for ITS
Importance: Uncategorized
Category: Data Model, Representation Guides
The W3C International Tag Set (ITS) standard defines i18n properties for XML based files. Could we use this to better handle XML files within XLIFF?
1.4. Permission Control and Validation
Importance: Uncategorized
Category: Data Model, Extension
It would be useful to have a language to be able to specify e.g. that in the 'review' process, a reviewer can only change the state attribute and add notes, and in the 'tm matching' process, a tool can only add <alt-trans> elements. After a process is completed, we could then automatically validate the XLIFF files that the constraints have been met according to the specification.
1.5. XLIFF as a Project Model
Importance: Should Have
Category: Data Model
XLIFF 1.2 uses a File/Resource as the model. We wish in XLIFF 2.0 to implement a richer project container
1.6. Resource Inheritance
Importance: Uncategorized
Category: Data Model, XML Schema
For some l10n libraries, it is common to support language inheritance, in that if a resource is not specified in the specific locale (e.g. en-AU), then look at the more generic locale (e.g. en). Handling localisation of these resources in XLIFF is quite ad-hoc with XLIFF 1.x. I.e. there is no 'right' way for an editor to specify 'use the more generic locale for this resource'.
1.7. Improved Whitespace Handling
Importance: Uncategorized
Category: Data Model, XML Schema
XLIFF 1.2 have some support for handling various types of whitespace in XML through the xml:space attribute, although this support is broken at times, as described in the following email. For XLIFF 2.0 we should implement support for improved whitespace handling.
To create a new Idea, simply add a page under XLIFF2.0/Ideas/MyIdeaTitle and use IdeaTemplate as a template.