Document:
02317: Namespace in modules

Draft (A preliminary unapproved sketch, outline, or version.)

Details

Submitted By Bryan Schnabel on 2012-11-20 12:03 pm UTC

Publication Type

None at this time.

Group / Folder

OASIS XML Localisation Interchange File Format (XLIFF) TC / System Ballot Results

Modified by

Not modified.

Copy

This document is not a copy.

Technical Contact

None at this time.

Download Count

696

Download Agreement

None at this time.

Description

A module is an optional set of XML elements and attributes that stores information about a process applied to an XLIFF document and the data incorporated into the document as result of that process. Each module is defined in a section of the XLIFF specification. The schemas of the XLIFF core or modules indicate where the elements and attributes of each module can be used. Modules can generally be placed in locations that are not extension points, with some restrictions, for example module elements are not allowed inside or elements. Each version of XLIFF has a fix set of modules. Adding or removing one or more modules from the latest version of XLIFF requires to increment the version of XLIFF. A module MUST use namespaces of only final specifications from OASIS (including the ones produced by the XLIFF TC) or from other established standardization bodies such as the World Wide Web Consortium (W3C), the European Telecommunications Standards Institute (ETSI), the International Standards Organization, or the Unicode Consortium. Private custom namespaces MUST NOT be used in modules. The IPR mode and license of a proposed module MUST be compatible with the OASIS XLIFF TC IPR mode (RF on RAND terms) and conform to relevant OASIS license requirements and policies.