[Date Prev][Date Next] [Chronological] [Thread] [Top]

What's the risk for some strange usages on schema?



Hi, all:
 
I have two questions on schema definition:
 
1. In order to obtain the schema information from cn=subschema, I modify the following
   three attrbiute definitions in core.schema:
 
        attributetype ( 2.5.21.4 NAME 'matchingRules'
         EQUALITY objectIdentifierFirstComponentMatch
         SYNTAX 1.3.6.1.4.1.1466.115.121.1.30 )
 
        attributetype ( 2.5.21.5 NAME 'attributeTypes'
         EQUALITY objectIdentifierFirstComponentMatch
         SYNTAX 1.3.6.1.4.1.1466.115.121.1.3  )
 
        attributetype ( 2.5.21.6 NAME 'objectClasses'
         EQUALITY objectIdentifierFirstComponentMatch
         SYNTAX 1.3.6.1.4.1.1466.115.121.1.37 )
 
  the words "USAGE directoryOperation" for the above attributes are removed. By doing this,
  I can use Netscape Java SDK to obtain schema information, and everything works well.
  This approach is the result under many try-and-error testing. What is the risk to modify
  the above definition?
 
2. In order to store non-UTF8 code in some standard attributes, I modify the the definition of Attribute name as follows:
 
        attributetype ( 2.5.4.41 NAME 'name'
         EQUALITY caseIgnoreMatch
         SUBSTR caseIgnoreSubstringsMatch
         SYNTAX 1.3.6.1.4.1.1466.115.121.1.5{32768} )
 
    The original syntax "1.3.6.1.4.1.1466.115.121.1.15" is modified as "1.3.6.1.4.1.1466.115.121.1.5"
    to store non-UTF8 code. Also, everything seems well on any operation(add, modify,delete,search).
    What's the risk to such modification?
 
Could someone give me some idea?
 
Thank you very much!
 
SCW
 
-----------------------------------------------
Shih-Chang Wang(汪世昌)
Associate Research
Internet & Multimedia Application Tech. Lab
Telecommunication Laboratories
TEL: 886-3-4245340
FAX: 886-3-4244470