[OASIS Issue Tracker] (XLIFF-5) ITS Localization Notes should be not represented

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/XLIFF-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65199#comment-65199 ] 

David Filip commented on XLIFF-5:
---------------------------------

Scope Warning added:

There is a one-to-one mapping for all parts of the Localization Note information to and from the XLIFF Core <note> and the Comment Annotation mechanism. This means that the whole data category can be losslessly Extracted from the native format, Merged back to the native format or even round-tripped, however ITS Processors and XLIFF Agents will parse the Localization Note with different scopes within XLIFF Documents.
While XLIFF Core <note> elements apply to the whole content of the structural element where it was placed in the business sense, it doesn't technically inherit in the XML sense. The scopes of the Comment Annotation mechanism will differ where the unextended ITS Processors cannot identify pseudo-spans formed by <sm/> / <em/> pairs, the scope will be the same on the well-formed <mrk> spans. The content and type of the Localization Note will be always mapped properly. 

> ITS Localization Notes should be not represented
> ------------------------------------------------
>
>                 Key: XLIFF-5
>                 URL: https://issues.oasis-open.org/browse/XLIFF-5
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Improvement
>          Components: ITS Module
>    Affects Versions: 2.1_csprd01
>         Environment: https://lists.oasis-open.org/archives/xliff-comment/201610/msg00016.html
> https://lists.oasis-open.org/archives/xliff/201609/msg00048.html
>            Reporter: Yves Savourel
>            Assignee: Felix Sasaki
>              Labels: work_required
>             Fix For: 2.1_csprd02
>
>
> The ITS Localization Notes data category has specific semantics, and can be deemed represented in a given format only if the same
> semantics applies.
> In other words: an ITS-aware XLIFF processor and a pure ITS processor should get the same results when processing the given data
> category. That is not the case for the XLIFF notes.
> See also https://lists.oasis-open.org/archives/xliff/201609/msg00048.html for details.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)