Re: New WWW - X.500 Gateway at Brunel

Tim Howes <tim@terminator.rs.itd.umich.edu> Fri, 06 May 1994 03:47 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01030; 5 May 94 23:47 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa01026; 5 May 94 23:47 EDT
Received: from haig.cs.ucl.ac.uk by CNRI.Reston.VA.US id aa18164; 5 May 94 23:47 EDT
Received: from bells.cs.ucl.ac.uk by haig.cs.ucl.ac.uk with local SMTP id <g.00315-0@haig.cs.ucl.ac.uk>; Fri, 6 May 1994 03:57:01 +0100
Received: from terminator.rs.itd.umich.edu by bells.cs.ucl.ac.uk with Internet SMTP id <g.04036-0@bells.cs.ucl.ac.uk>; Fri, 6 May 1994 03:56:47 +0100
Received: from terminator.rs.itd.umich.edu by terminator.rs.itd.umich.edu (8.6.9/2.2) with SMTP id WAA12736; Thu, 5 May 1994 22:55:22 -0400
Message-Id: <199405060255.WAA12736@terminator.rs.itd.umich.edu>
To: pays@faugeres.inria.fr
cc: Andrew.Findlay@brunel.ac.uk, directory-group@jnt.ac.uk, osi-ds@cs.ucl.ac.uk, wg-nap@rare.nl, rapatel@theophilus.rutgers.edu
Subject: Re: New WWW - X.500 Gateway at Brunel
In-reply-to: Your message of "05 May 1994 20:47:18 +0200." <768163638.27692.0-faugeres.inria.fr*@MHS>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 05 May 1994 22:55:22 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tim Howes <tim@terminator.rs.itd.umich.edu>

> From:    pays@faugeres.inria.fr
> To:      pays@faugeres.inria.fr, Andrew.Findlay@brunel.ac.uk

> >> Nice and simple! Is  caseExact really necessary or would caseIgnore be
> >> more appropriate (remember that case is *preserved* in both syntaxes -
> >> it is only the search operation that cares about the difference).
> 
> Well... no strong opinion.
> We decided for caseExactString just because as the URL syntax
> is not a matter of ours and wanted to have (even for searches)
> the URL string as is...
> Do you all feel it will be a "plus" if we abandon the  caseExact?
> If so we are ready to change, but by now I would prefer if there is no
> good justification to stick to the caseExact...

Don't se need something less restrictive than caseExact or caseIgnore?
I'm thinking either caseExactIA5String or caseIgnoreIA5String...   -- Tim