[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff] 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,
> ...
> However, I think that static Constraints are more naturally
> expressed using the wording with REQUIRED/OPTIONAL than the
> verb variants MUST/MAY.
> This said, I can live with the MUST formulations if you orGood to know you MAY live with it if you MUST.
> others are not convinced by the above reasoning for the
> REQUIRED formulations, because they are after all equivalent.
In addition to the reasoning stated, the current text in this definition uses MUST in cspr02.
I think we should not change text when it's not necessary.
In the csp02 draft there is about 17 Constraints sections in the core and 18 in the modules.
> [BTW, I have been doing these reformulations
> from MUST to REQUIRED in Constraints as part of the normative
> language rehaul after csprd01)]
In those 35 sections I've found:
- 9 occurrences of REQUIRED, OPTIONAL or with OPTIONAL+REQUIRED
- 21 MUST/MUST NOT
- 9 OPTIONAL with MUST/MUST NOT
- 4 SHOULD
My count is probably off by a few, but it's clear that the constraints after csp01 are still overwhelmingly using the MUST/etc.
terms. That's fine with me: I don't think we should change text that doesn't need to be changed.
Cheers,
-ys
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]