Re: Ommitted components in the 1327 mapping

["Harald T. Alvestrand" <[e-mail]>]

Steve,
one thing I am not sure about:
Your approach still changes the "Representing O/R names"
document, doesn't it? So that the actual structure changes?

Otherwise, I kind of disagree with your conclusion:

I must agree with Michael in that I don't like an approach where
the strategy for handling a missing component in an RDN-O/R name
is radically different from the strategy for representing the
same missing component in an O/R name.

My favourite would still be 2) with "SPACE" (my favourite
interpretation of the battles over SPACE in ISO was that it is
only a placeholder because they couldn't agree to declare it
OPTIONAL, so that there is precedent for this usage).
Or $$$MISSING$$$.

It's not a show-stopper, but I think it actually makes the spec
more complex to read and to implement if we add another OID-valued
special case to the naming tree.

                    Harald A