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: [xliff] @disabled in Validation Module. Fix example. Add constraint?

I think the text that truly defines what the attributes does is:

"This rule attribute determines whether a rule MUST or MUST NOT be applied within the scope of its enclosing element."

It doesn't exclude <file> as an enclosing element.

Then we have "For example, a rule defined at the <file> level can be disabled at the <unit> level." Which provides an example of

The text "This attribute is provided to allow for overriding execution of rules set at higher levels" seems to be a) redundant and
b) missing a "for example". We could delete it without changing any expected behavior since it seems to cause confusion.

I would be on favor to not add new constraints because using disabled='yes' at the <file> level is a perfectly fine use case: you
can need to temporarily disable rules for examples.


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