Article View: comp.protocols.iso.x400
Article #945Re: O/R name component ordering (was: Report from X.400 development
From: Nigel Bevan
Date: Fri, 21 Jun 1991 13:12
Date: Fri, 21 Jun 1991 13:12
4 lines
705 bytes
705 bytes
I would have thought that some minor changes to the parsing of the user interface were fairly minor in the context of a communications package? Since we have gathered that there are several incompatible conventions currently in use, perhaps it was time there was a standard?
Technical Details
Message-ID:
<9106210612.aa00770@ics.uci.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!spool.mu.edu!agate!ucbvax!ucsd!orion.oac.uci.edu!ucivax!gatewayShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!spool.mu.edu!agate!ucbvax!ucsd!orion.oac.uci.edu!ucivax!gateway From: nbevan@ess.cs.ucl.ac.uk (Nigel Bevan) Newsgroups: comp.protocols.iso.x400 Subject: Re: O/R name component ordering (was: Report from X.400 development Message-ID: <9106210612.aa00770@ics.uci.edu> Date: 21 Jun 91 13:12:48 GMT Lines: 4 Approved: usenet@ics.uci.edu