Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!usc!orion.oac.uci.edu!ucivax!gateway
From: Dan@dna.lth.se (Dan Oscarsson)
Newsgroups: comp.protocols.iso.x400
Subject: Re: Order of fields in business card printed O/R-address format
Message-ID: <1991Mar31.094530.20474@lth.se>
Date: 1 Apr 91 04:38:53 GMT
References: <670472*JPALME@QZ.qz.se>
Organization: Computer Science, Lund Institute of Technology, Sweden
Lines: 31
Approved: usenet@ICS.UCI.EDU
x-attn: jns
ReSent-From: Jerry Sweet <mhsnews-request@ICS.UCI.EDU>
ReSent-To: mhsnews@ICS.UCI.EDU

In article <670472*JPALME@QZ.qz.se> JPALME@qz.qz.se (Jacob Palme QZ) writes:
>A couple of weeks ago I got the question of the standards
>meeting in february on X.400/MOTIS development really
>intends to list the OU-s starting with the largest unit,
>but list all other attributes starting with the smallest
>unit, since this could be confusing to humans using the
>recommendation for "representation of o/r addresses for
>human usage".
>
>I have now checked the output document from the meeting,
>and, unfortunately, yes, the case is as described above.
>
>For example, a printed O/R-address might look like this:
>G=John;S=Smith;O=XYZ University;OU1=Computer
>division;OU2=Software unit;A=" ",C=SE
>
Do X.400 really think a normal user would like to use such a complex
address structure like the O/R-address?
All these irretating tags on every part of the address, why do you
need them?

The domain address used by the Internet is much simpler.

   Dan


--
Dan Oscarsson                              Department of Computer Science
                                           Lund Institute of Technology
e-mail:  Dan.Oscarsson@dna.lth.se          Box 118
                                           S-221 00 Lund, Sweden