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