Next in thread → Next in month →

[OASIS Issue Tracker] (XLIFF-20) Missing id uniqueness Constraints in mtc

From
OASIS Issues Tracker <>
Date
2017-02-07T16:25:20+00:00
ID
Thread
[OASIS Issue Tracker] (XLIFF-20) Missing id uniqueness Constraints in mtc
[ https://issues.oasis-open.org/browse/XLIFF-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Filip updated XLIFF-20:
-----------------------------

    Labels: ready-for-vote  (was: ready-for-vote request_tc_discussion)

> Missing id uniqueness Constraints in mtc
> ----------------------------------------
>
>                 Key: XLIFF-20
>                 URL: https://issues.oasis-open.org/browse/XLIFF-20
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Improvement
>          Components: other
>    Affects Versions: 2.1_csprd01
>         Environment: follows from https://issues.oasis-open.org/browse/XLIFF-4
>            Reporter: David Filip
>            Assignee: David Filip
>              Labels: ready-for-vote
>             Fix For: 2.1_csprd02
>
>
> It transpired that the Translation Candidates issue lacks core id uniqueness constraints. This is confusing for implementers as it might suggest a common uniqueness pool with the core unit structure, which is not the case



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →