[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltru] Re: Finishing off #1026 (Was: Re: status? last call?)



Addison Phillips scripsit:

> If it becomes necessary to
> identify a region for which only a UN M.49 code exists in language tags,
> then the registration authority for ISO 3166 SHOULD be petitioned to
> assign a code: such a code could then be registered for use in language
> tags. 

I think this "could" ==> SHOULD, or at the very least MAY.

While I'm at it, in the 2005-7-11 draft:

	"could be included" in 3.4 ==> MAY;
	"might be interpreted", "could be taken", "could be regarded", "one
		could write", "could be used" ==> MAY;
	"could be used" in 4.5 ==> MAY;
	"cannot" in 2.2.3 ==> MUST NOT;
	"can" in 2.2.4 ==> MAY;
	"cannot" in 2.2.6 items 1 and 3 ==> MUST NOT;
	"can be split" and "can use the registry" in 3.1 ==> MAY;
	"can raise objections" in 3.4 ==> MAY;
	"can be registered" in 3.5 ==> MAY;
	"can only give possible examples" in 4.2 needs no modal, and
		==> "gives only possible examples";
	"can use" in 7 ==> MAY;
	"ought not" in 4.1 ==> SHOULD NOT;
	"will" in 2.2.1 item 5 ==> SHOULD or perhaps MUST;
	"will not be added" in 2.2.1 ==> MUST NOT;
	"will maintain" in 2.2.8 ==> MUST;
	"will be maintained" in 3 ==> MUST;
	"will consist" in 3.1 ==> MUST;
	"no registration records will be maintained" in 3.1 ==>
		"registration records MUST NOT be maintained";
	"will be in a modified" in 3.1 ==> MUST;
	"will evaluate" in 3.2 ==> MUST;
	"no new entries will be added and none of the entries will be removed"
		in 3.2 ==> "new entries MUST NOT be added or removed";
	"will be maintained" in 3.4 ==> MUST;
	"No subtags will be registered" in 3.5 ==> "Subtags MUST NOT
		be registered";
	TYPO: "will lend" in 3.6 ==> "will tend";
	"will use" and "will forward" in 3.6 ==> MUST;
	"will be initialized", "will be relabeled", "will be limited", and
		"will be sent" in 5.1 ==> MUST;
	"will include" in 5.2 ==> MUST;
	"will continue" in 8 ==> SHOULD;

Some of these changes may be inappropriate because of the broader context;
I haven't fully investigated.

-- 
Winter:  MIT,                                   John Cowan
Keio, INRIA,                                    jcowan at reutershealth.com
Issue lots of Drafts.                           http://www.ccil.org/~cowan
So much more to understand!                     http://www.reutershealth.com
Might simplicity return?                        (A "tanka", or extended haiku)

_______________________________________________
Ltru mailing list
Ltru at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ltru




Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.