[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Sorting the NAME Attribute
- To: openldap-technical@openldap.org
- Subject: Re: Sorting the NAME Attribute
- From: Tim Gustafson <tjg@ucsc.edu>
- Date: Tue, 31 Mar 2015 17:20:41 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ucsc.edu; s=ucsc-google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=GzY8+/Y1Xck7FNrnp82Aw5Peqd5wtQpg4SWfmTeHWIc=; b=n5LJkalRhIAsIqFbTQ9G1AJMxgP9h/Ad57mGSKyuvGxh2BGPxi24lafdnjOZ7mXaaA 34rERYQQv2CdiQxAYcFdN5H8WPmRiQlA6MR6eTTDrjcF8D5R27Mrc21cWdMH48n7i3Mv xL70swC7SVnrnP0qx5bCpWHnVwo8WZZARE58o=
- In-reply-to: <CAPyBAS5RO0TkpUMBfMXPuC-5B6kn=Gg=HzDDXxeR05eka-JsaA@mail.gmail.com>
- References: <CAPyBAS5RO0TkpUMBfMXPuC-5B6kn=Gg=HzDDXxeR05eka-JsaA@mail.gmail.com>
> However, I will note, the definitions of these attributes are RFC
> defined. They have no ORDERING rule on purpose.
Just a quick follow-up on my own post:
The RFC is based on the ITU specification, which (as of ITU-T Rec.
X.520 (11/2008)) says:
6.2.1: Name: The Name attribute type is the attribute supertype from
which string attribute types typically used for naming may be formed.
name ATTRIBUTE ::= {
WITH SYNTAX UnboundedDirectoryString
EQUALITY MATCHING RULE caseIgnoreMatch
SUBSTRINGS MATCHING RULE caseIgnoreSubstringsMatch
ID id-at-name }
That certainly suggests that matching against this field should be
case-insensitive, so it follows that ordering should also be
case-insensitive.
--
Tim Gustafson
tjg@ucsc.edu
831-459-5354
Baskin Engineering, Room 313A