Re: Schema define?

[Jim Willeke <jim@willeke.com>]

Equality
To match for equality, two values must be identical, use the same attribute
syntax, and conform to the data type of the attribute syntax. Most syntaxes
specify a match for equality. 

Ordering
To match for ordering, a syntax must be open to comparisons of less than,
equal to, and greater than. For example, 50 is less than 100, and N is greater
than B. 

Substrings
To match substrings, a syntax must be open to search and comparison patterns
that include the asterisk (*) wildcard. For example, in a syntax using substring
matching, N*V*L would match NAVAL, NAVEL, or NOVEL
-jim
gwcom wrote:

Dear all,

 

I am new to LDAP and trying to define my own schema for my needs

and I have the following questions:

For example,

        attributeType ( 2.5.4.41 NAME 'name'
                EQUALITY caseIgnoreMatch
                SUBSTR caseIgnoreSubstringsMatch
                SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} )
       

This attribute have unique oid 2.5.4.41 but my company haven't get a Unique oid

from IANA. What oids should I assign so I will not affect the system.

Do I really need to get one oid for my cmopany?

Will there be some virtual ids that won't use??

 

I read related rfcs but I still confused about EQUALITY, SUBSTR and ORDERING

Can someone explain a little bit between EQUALITY and SUBSTR

as well as ORDERING(does it for numerics)?

 

The "name" should not be crashed in attribute and objectclass, any suggested or standard

methods to make it easy to read and keep its meaning but remains unique easily?

 

Thanks

Bryan Wu