tables-06b.txt Pseudo-code clarification

John C Klensin klensin at jck.com
Wed Jul 22 05:26:20 CEST 2009



--On Tuesday, 21 July, 2009 18:46 -0700 Kenneth Whistler
<kenw at sybase.com> wrote:

> Patrik,
> 
> Before delving into the syntax issues remaining for
> the rule sets for A.5, A.6, A.8, and A.9, I want to
> back up and consider the pseudo-code conventions
> described at the top of Appendix A. Part of the
>...
> I suggest that this be addressed by rewriting the
> paragraph which explains the pseudo-code conventions.
> And among other things, for a set of conventions like
> these, breaking them out from a paragraph form into
> bullet-like sections will also make it easier for people
> to read and understand them.
> 
> In a set of rules like this, I think conciseness is less
> important than clarity, so my suggested rewrite will be
> a little more long-winded than the current draft, but I 
> hope much clearer in the long run.
> 
> Also, because of the way this pseudo-code is trying to
> mix property functions and string position functions,
> I think it is important to introduce an explicit
> "Undefined" term which can be then used consistently
> to deal with invalid string positions or property functions
> involving invalid codepoints.
> 
> So here is my attempt at a rewrite for clarity. I'm not
> trying to change the intent of any of this pseudo-code,
> as developed to express the rule sets for CONTEXTO --
> just to make it clearer and more rigorous.

I've read through this only a couple of times and cannot
guarantee that all of the cases are correct but the general
approach and text seem like a considerable improvement to me.

     john



More information about the Idna-update mailing list