[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff] cos-301 proposed changed text
----- 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: implicit, see below
When order is not explicitly set on any of the <target> elements of the enclosing <unit> element, each <target> element corresponds to the <source> element of its parent element.
When at at least one <target> element has the order attribute value set explicitly, all <target> elements with set order values correspond to the <source> elements whose order is naturally designated by the set order values. The remaining implicit values (if any) correspond to implicit ordinals of the remaining (if any) <source> elements, i.e. those that have had no <target> elements assigned by explicit order attribute values.
[I am fully aware that the above language is awkward and complicated, so improvement ideas are welcome.]
Example:
[a valid example similar to the pseudo-code above, showing how tragets are shifted along the remaining free values]
Used in: <target>.
Constraints
• The explicit values of the order attribute MUST be unique within the enclosing <unit> element.
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 -----
+1
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of David Filip
Sent: Tuesday, June 17, 2014 6:48 AM
To: Yves Savourel
Cc: xliff@lists.oasis-open.org
Subject: 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
dFdF 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]