RE: [xliff] Call for Dissent was Re: [xliff] csprd01 comments 11 and 41

[Yves Savourel <ysavourel@enlaso.com>]

> Then we have the Constraints in state:
> [[
> - The optional attribute state MUST NOT be set to final if 
> and only if the required attribute approved on the same
>  <segment> element
> is set to no.
> - The optional attribute state MUST NOT be set to initial 
> if and only if the required attribute approved on the 
> same <segment> element is set to yes.
> ]]
>
> d) The second constraint is (hopefully) incorrect: we can't 
> have state='final' also when approved='yes'? so we can never have
> state='final'? Obviously you meant "MUST" instead of "MUST NOT" here.

Obviously I was not completely awake when I read the second constraint.
It's not incorrect, and therefore we can't infer the approved value when state is neither initial or final.

But the bottom line remain the same, perhaps even worst: there is no clear relation between when a segment is ready to be merged and
its state. And the tools do whatever they want anyway.

So I would say that while the approved information is not always redundant, it's not interoperable and rather useless to the XLIFF
processors. If the tool wants to base the merging on information about the status of the translation they should look at state.

Cheers,
-yves



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php