OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [xliff] a quick question regarding the Localization Note mapping in XLIFF 2.1


Thanks, Yves
1. mapping into two different features does not mean it is only partially covered IMHO
also in XLIFF these are related. The comment annotation can reference a note.

We do not need to introduce the itsm locNoteType if we mandate referencing to Note in order to discern between alerts and descriptions and/or set a default assumed LocNoteType when the Note is given as a value and not reference. The natural deafult would be alert, as the Note priority deafault is '1'.


2.
I think it is unresolved as yet, if the ITS appendix will be informative or normative. However, there is very little what can be normatively stated  about XLIFF features as being used to express ITS features. It mainly falls into the extraction or merge area that XLIFF has been traditionally silent about. My current thinking on this is that this part is informative in the same way as the planned TBX mapping Note. Even if we decided that the appendix is normative, it would contain very little if any normative language.
IMHO, Anything normative should be stated separately in the ITS module.

I do see value in separating what is available through XLIFF features and what needs the module implementation.
For instance, core only implementers can refer to the appendix to see what's available to them and do not need to go to the module at all.

Since the ITS features available through XLIFF features are mostly core and we do not want to change core. It lends itself to describe the ITS corollaries of XLIFF features in an Informative Appendix. The advantage of the appendix being to provide a single starting point, pointing all over the specification, including the module.

From the spec point of view, the module, defines everything (and nothing else) that is not available elsewhere.

I feel strongly that the two parts should be kept separated
dF   
 

Dr. David Filip
=======================
OASIS XLIFF TC Secretary, Editor, and Liaison Officer 
LRC | CNGL | CSIS
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734

On Thu, Nov 20, 2014 at 1:15 PM, Yves Savourel <ysavourel@enlaso.com> wrote:

Hi David,

 

The Localization Note maps to two Core features:

 

a)  The <note> element, with locNoteType set through priority=’1’ as an ‘alert’ and other values as a ‘description’

b)  The comment annotation with either value or ref, but it misses a locNoteType, so we have to provide it through itsm.

 

BTW: as I said a few times already, I really think having all the ITS mapping defined in a single section, per data category would be a lot easier to understand than having that split into several parts.

Also, I’m not sure why some parts would not be normative: For example, defining the translate attribute as the mapping to the Translate data category is normative in my opinion.

 

Cheers,

-ys

 

From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Dr. David Filip
Sent: Thursday, November 20, 2014 5:30 AM
To: xliff@lists.oasis-open.org; public-i18n-its-ig@w3.org
Subject: [xliff] a quick question regarding the Localization Note mapping in XLIFF 2.1

 

Hi all,

 

in the current working draft of XLIFF 2.1 I list the Localization Note category under the partially supported categories.

Now, on partially supported categories we have an informative description how XLIFF features can be used and then we add in the normative ITS module what's needed to fully support that category.

 

Now I was going to add what's needed to fully support the Localization Note, but cannot think of anything that is not expressed by the core mechanism.

 

Should I move the category to fully supported?

Or someone please tell me what other elements, attributes, or even values we need to define in XLIFF in order to fully support that category.

 

Cheers

dF 

 


Dr. David Filip

=======================

OASIS XLIFF TC Secretary, Editor, and Liaison Officer 

LRC | CNGL | CSIS

University of Limerick, Ireland

telephone: +353-6120-2781

cellphone: +353-86-0222-158

facsimile: +353-6120-2734




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]