OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: Contsraints for start and end markers and codes was: Re: [xliff] RE: Resolution proposal/Call for Dissent Re: [xliff] mrk translate outside the content but in scope


Hi David, all,

> ? The attribute isolated MUST be set to yes when the <sc> 
>   element corresponding to this end code is not in the same <unit>.
> [The attribute does not need to be *set* to "no" otherwise, because
> "no" is the default value. The same is true for the sc constraint.]
> ? Exactly one of the attributes id or startRef MUST be specified:
>   o The startRef attribute is REQUIRED if and only if the value of 
>     the attribute isolated is "no".
>   o The id attribute is REQUIRED if and only if the value of isolated
>     is "yes".

How about this:

? The attribute isolated MUST be set to yes only when the <sc>
  element corresponding to this end code is not in the same <unit>.
? Exactly one of the attributes id or startRef MUST be specified:
  o The startRef attribute MUST be specified if and only if the 
    value of the attribute isolated is "no".
  o The id attribute MUST be specified if and only if the value 
    of isolated is "yes".

Rational: 
- adding 'only' in the first PR says yes is not to be used in other cases
- using "REQUIRED" just after OPTIONAL is used for the same attributes in the list of attributes looks a bit strange.


Cheers,
-ys



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]