Good catch Fredrik. It looks like KAVI stripped out the elements that I pasted in from David’s note.
I’ll see if I can add an addendum. I hope so. The timing was perfect (ballot ending one hour before our meeting).
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org]
On Behalf Of Estreen, Fredrik
Sent: Tuesday, November 13, 2012 7:53 AM
To: Rodolfo M. Raya (rmraya@maxprograms.com); xliff@lists.oasis-open.org; tc_admin@oasis-open.org
Subject: RE: [xliff] Groups - Ballot opened: "Namespace in modules"
Hi Rodolfo, All,
I believe that there is a small error in the second paragraph of the description. Third sentence reads:
“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.”
I think the intent is that it should be:
“Modules can generally be placed in locations that are not extension points, with some restrictions, for example module elements are not allowed inside <source>
or <target> elements.”
Regards,
Fredrik Estreen
"Namespace in modules" has opened.
|
Ballot Title:
Namespace in modules
Question
Namespace in modules follow the rules in this description:
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.
Closing Date: Tuesday, 20 November 2012 @ 7:00 am EST
Vote
Group: OASIS XML Localisation Interchange File Format (XLIFF) TC
Date Opened: Tuesday, 13 November 2012 @ 7:00 am EST
|