[OASIS Issue Tracker] (XLIFF-13) validation behavior of editing hints to depend on segment state

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

     [ https://issues.oasis-open.org/browse/XLIFF-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Filip updated XLIFF-13:
-----------------------------

    Resolution: 
Consensus 17th Jan, 2017:
Implement state dependency in core sch 
Describe the behavior in advanced validation prose [dF]

> validation behavior of editing hints to depend on segment state
> ---------------------------------------------------------------
>
>                 Key: XLIFF-13
>                 URL: https://issues.oasis-open.org/browse/XLIFF-13
>             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
>          Issue Type: Improvement
>          Components: validation artifacts
>    Affects Versions: 2.1_csprd01
>         Environment: http://markmail.org/thread/vxkffkv2btmrdftk
>            Reporter: David Filip
>            Assignee: Soroush Saadatfar
>              Labels: request_tc_discussion
>             Fix For: 2.1_csprd02
>
>
> FROM: Ján Husarčík <jan.husarcik@gmail.com>
> in relation to https://issues.oasis-open.org/browse/XLIFF-10 and https://lists.oasis-open.org/archives/xliff-comment/201611/msg00003.html could you please consider different type of validation of editing hints based on segment state?
> - initial state, no target present: no validation
> - translated /reviewed: report warning
> - final state: report error
> In case you decide to accept the suggestion, could you please update Processing Requirements in
> http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html#editinghints and reference them (at least) in http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html#state?



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