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: ITS module section(s) in the specification

Hi David, all,

(I'm starting a different thread on this topic, to avoid mixing it with the Localization-Note one)
> 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.

I'm not sure why we would make non-normative the descriptions of how existing XLIFF constructs map to ITS data categories. The ITS module is not just about the parts we have to add, it describes all data categories.

Having a list of the data categories and for each say how it is represented in XLIFF (through existing constructs and/or the itsm namespace) seems simple. And in that case having, for example, the description for Translate being non-normative while the one for LQI being normative seems difficult to justify.

Why make things complicated? Is translate='yes|no' the only way to represent the Translate data category? Yes, so why not stating it normatively? In addition one can say that all ITS data categories need to be complemented with itsm:annotatorsRef, so none is completely represented in the XLIFF core.


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