Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!jarthur!ucivax!gateway
From: osa538b@vaxc.cc.monash.edu.au (Alan Chee)
Newsgroups: comp.protocols.iso.x400
Subject: <None>
Message-ID: <39641.26c470df@vaxc.cc.monash.edu.au>
Date: 12 Aug 90 20:59:12 GMT
References: <1360*harald.alvestrand@elab-runit.sintef.no>
Organization: Computer Centre, Monash University, Australia
Lines: 24
Approved: usenet@ICS.UCI.EDU
x-attn: jns


In article <1360*harald.alvestrand@elab-runit.sintef.no>, harald.alvestrand@elab-runit.sintef.no (Harald Tveit Alvestrand) writes:
> Organization: ELAB-RUNIT, SINTEF, Norway
> References:  <9008081714.AA10475@cbmark.cbcc.att.com>
> As a member of RARE WG1, which is more or less responsible for putting the
> format forward, I think I can state that the reason ; was chosen for a
> delimiter
> and not / was that / is a PrintableString character, while ; is not.
> This means that in order to use /, we have to define a quoting syntax, while
> using ; quotes would not be needed.

I must be missing something here.
 / and ; both *are printable* characters ( ASCII code 47 and 59 ).

I believe / has more visual contrast as opposed to ; that 'blends' with the
address string.


--
-----------------------------------------------------------------------------
 Alan Chee,			   |	internet: alanC@VAXC.cc.monash.edu.au
 P.O. Box 413, World Trade Centre, |	X.25:  PSI%AUSTPAC.0505224122018::chee
 Melbourne, Vic. AUSTRALIA  3005   |    voice:	  +61 3 345 4717 (BH)
-----------------------------------------------------------------------------