[OASIS Issue Tracker] (XLIFF-4) Simplify Change Tracking Data Model

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

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

Yves Savourel commented on XLIFF-4:
-----------------------------------

I agree that the CTR-specific attribute for mrk auto-completed is not a great solution.
But using the full unit for storing a change in a segment is not great either. It brings some usability issues: the tracks for the same segment can be sometimes in an item marked for that segment, or sometimes in an item for the whle unit. It will be difficult for the user to follow this.

If we don't have the auto-completed mrk, I'm not sure it's worth having an item for the segments.

I'm also not clear on what the user can and cannot do in the item for the unit: Can it stores several changes at once? (e.g. change of a state and some edit), or only one change?

> Simplify Change Tracking Data Model
> -----------------------------------
>
>                 Key: XLIFF-4
>                 URL: https://issues.oasis-open.org/browse/XLIFF-4
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Improvement
>          Components: Change Tracking Module
>    Affects Versions: 2.1_csprd01
>         Environment: https://lists.oasis-open.org/archives/xliff-comment/201610/msg00015.html
>            Reporter: Yves Savourel
>            Assignee: David Filip
>              Labels: request_tc_discussion
>             Fix For: 2.1_csprd02
>
>
> It seems to me the new model for change tracking is too complicated to be implemented without a) a lot of efforts and b) mistakes.
> Having different types of content in <item> and <simpleItem> based on the property attribute and the grand-parent element's
> appliesTo attribute is not going to make things easy.
> I would propose to simplify things:
> If the change is on the content of a <source> or <target>:
> -> Use a <contentItem> element that contains text and zero or more inline codes (same as a source or target content)
> If the change is on the content of a <unit> (e.g. segmentation):
> -> Use a <unitItem> element that contains one or more <segment> and zero or more <ignorable> (same as in <unit>)
> In all other cases:
> -> Use an <item> element that has plain text
> - Neither <contentItem> nor <unitItem> would have a property attribute, or if they do it would be default and fixed to 'content'.
> - The property in <item> could be set to 'content' only if the revisions' appliesTo is 'note'
> As for dealing with orphan <sm/> and <em> in <contentItem>: I would propose to make them <mrk> with a new CTR attribute
> ctr:added='sm|em' to indicate that the original was either a <em/> (added='em')or a <sm/> (added='sm'). 



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