Path: utzoo!news-server.csri.toronto.edu!rutgers!ucsd!orion.oac.uci.edu!ucivax!gateway
From: hta@isolde.er.sintef.no (Harald Tveit Alvestrand)
Newsgroups: comp.protocols.iso.x400
Subject: O/R name component ordering (was: Report from X.400 development.....)
Message-ID: <1991Mar14.095445.16312@ugle.unit.no>
Date: 15 Mar 91 03:24:36 GMT
References: <605950*@MHS>
Reply-To: harald.alvestrand@elab-runit.sintef.no
Organization: ELAB-RUNIT, SINTEF, Norway
Lines: 33
Approved: usenet@ICS.UCI.EDU
x-attn: jns
ReSent-From: Jerry Sweet <mhsnews-request@ICS.UCI.EDU>
ReSent-To: mhsnews@ICS.UCI.EDU

Jacob, thanks a LOT for giving us this stuff early enough to comment on it!

In article <605950*@MHS>, JPALME@qz.qz.se (Jacob Palme QZ) writes:

|>
|> Representation of O/R-addresses for human exchange
|> --------------------------------------------------
|>
|> Further work was done on this. It is now accepted that
|> only semicolon (;) or new line in tables, and not slash
|> (/) shall be used between attributes in the
|> representation. The fields will be given with the
|> innermost value (Given name) first, and the outermost
|> value (country) last, except that Organizational Units
|> are listed in the reverse order from this.
|>
|> User Interfaces should to some extent be suitable for
|> this format, in the order in which attributes are
|> handled and in the abbreviated names given to the
|> attributes in the user interface.
|>

Jacob, please tell us it isn't so, and that the O attribute should still
be placed closest to the most significant OU, like before!
If your quote is the full and complete truth, there will be NO software
capable of deciding whether an address is input in "ISO/CCITT order"
or the currently used "complete little-endian" format.

--
                   Harald Tveit Alvestrand
Harald.Alvestrand@elab-runit.sintef.no
(big-endian) C=no;PRMD=uninett;O=sintef;OU=elab-runit;S=alvestrand;G=harald
+47 7 59 70 94