need to decide on the use of "itsm_" prefix in the JLIFF ITS Module

[DavidFatDavidF]

The XLIFF spec differentiates between two ITS Module namespaces. Most of the features reuse the original W3C ITS namespace
https://www.w3.org/2005/11/its/

Only attributes that don't exist in the original W3C ITS 2.0 spec use the OASIS hosted namespace
urn:oasis:names:tc:xliff:itsm:2.1

This distinction is meaningless in JLIFF, however we are trying to ease switching between XLIFF and JLIFF pipelines, so keeping the "itsm_" prefix as distinct from the "its_" prefix might be useful..

An example is the itsm:domains attribute that exists in XLIFF Version 2.1 to facilitate roundtrip of the ITS 2.0 Domain data category.

The other itsm: attribute in XLIFF Version 2.1 is itsm:lang that is used to express inline instances of the ITS 2.0 Language Information data category

[DavidFatDavidF]

Need to add itsm_lang to JLIFF schema

[DavidFatDavidF]

Meeting 28th July:
Consensus to preserve the its_ itsm_ distinction from XLIFF 21 (its: vs itsm:)

Pro
Easier on implementers when switching between XLIFF and JLIFF
Preserves the original distinction between the W3C namespace semantics and the local OASIS additions
Con
Schema impact

Long term benefits outweigh the inconvenience of current schema impact

To implement along with #11

• affects only itsm_lang and itsm_domains

[DavidFatDavidF]

Reviewed in meeting on 25th August