RE: [xliff] cos-301 proposed changed text

I agree with Yves assessment, we cannot afford to insert a new constraint. We could insert a warning. But the former part seems fine.
It actually leaves the default undefined but gives a clear hint how to determine missing values.
We can slate such a constraint for 2.1 or errata.
I will tentatively implement an editorial solution based on this later this week and will call for dissent.
Cheers
dF

dF is AFK, so please bear with the typos and call me at +353860222158 if my answer seems insufficient..

On Jun 17, 2014 2:12 PM, "Yves Savourel" <ysavourel@enlaso.com> wrote:

Hi everyone,

I think Fredrik’s additional sentence for the default value is quite good and clear.

For the additional constraint however, I’m not sure we can/want do this at this stage.
Adding a constraint is likely to be seen as a major change rather than just editorial one.

Cheers,

-yves

From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Estreen, Fredrik
Sent: Tuesday, June 17, 2014 2:34 AM
To: xliff@lists.oasis-open.org
Subject: [xliff] cos-301 proposed changed text

Hi,

Here is my attempt at wording for the default value of the ’order’ attribute on <target> elements. The change makes the default behavior easy to understand and also adds a constraint that enforces that order must be set on multiple targets when reordering. It is however not necessary to specify it on all targets all the time, for example when swapping the order of two targets other targets may be left at the undefined state.

----- New Wording -----
4.3.1.24 order

target order - indicates the order, in which to compose the target content parts.
Value description: A positive integer.

Default value: undefined
When order is undefined the <target> corresponds to the <source> of its parent element.

Used in: <target>.

Constraints

• The value of the order attribute MUST be unique within the enclosing <unit> element unless left undefined.

• When order is specified on one <target>, it MUST also be specified on other <target>s in the <unit> such that each <source> has at most one corresponding <target> after resolving the order for all <target>s in the <unit>.

See the Segments Order section for the normative usage description.

----- Current wording -----

4.3.1.24 order

target order - indicates the order, in which to compose the target content parts.
Value description: A positive integer.

Default value: undefined

Used in: <target>.

Constraints

• The value of the order attribute MUST be unique within the enclosing <unit> element.

See the Segments Order section for the normative usage description.

----- end -----

Regards,

Fredrik Estreen

xliff message