##
## schema file for OpenLDAP 2.0.x
## Schema for storing VTC student information in LDAP
## OIDs are owned by the ICT Department of HKIVE(TY).
##
## Prerequisite schemas - uid & uidNumber (nis.schema)
##
## 1.3.6.1.4.1.11400.2.1.x - attributetypes
## 1.3.6.1.4.1.11400.2.2.x - objectclasses
##
## This is taken directly from the VTC schema in ldap.vtc.edu.hk,
## and some attributes I do not clearly understand.
## Nick Urbanik <nicku@vtc.edu.hk>

attributetype ( 1.3.6.1.4.1.11400.2.1.1 NAME 'academicYear'
        DESC 'The year the student is currently enrolled, e.g., 2001'
        EQUALITY numericStringMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
        SINGLE-VALUE )

#        ORDERING numericStringOrderingMatch


# This looks like an uneccessary duplication of uid
attributetype ( 1.3.6.1.4.1.11400.2.1.2 NAME 'acOwner'
        DESC 'Students name'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

attributetype ( 1.3.6.1.4.1.11400.2.1.3 NAME 'acType'
        DESC 'Whether student or staff or...'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

# I'm not sure what Wood Road people intended by this,
# but I guess it could be input from the student...
attributetype ( 1.3.6.1.4.1.11400.2.1.4 NAME 'answer1'
        DESC 'Students first response'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

attributetype ( 1.3.6.1.4.1.11400.2.1.5 NAME 'answer2'
        DESC 'Students second response'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

attributetype ( 1.3.6.1.4.1.11400.2.1.6 NAME 'answer3'
        DESC 'Students third response'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

# Not used apparently in the public area of VTC ldap server:
attributetype ( 1.3.6.1.4.1.11400.2.1.7 NAME 'award'
        DESC 'The qualification of our alumni'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )

# Not really sure quite what they do with this:
attributetype ( 1.3.6.1.4.1.11400.2.1.8 NAME 'batchUpdateFlag'
        DESC 'Indicate that the entry has been updated.'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

attributetype ( 1.3.6.1.4.1.11400.2.1.9 NAME 'classCode'
        DESC 'The class a student is in.'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

attributetype ( 1.3.6.1.4.1.11400.2.1.10 NAME 'course'
        DESC 'The course a student is in.'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

attributetype ( 1.3.6.1.4.1.11400.2.1.11 NAME 'courseDuration'
        DESC 'How long the course lasts normally.'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

# Note that it's not 100% silly to have a department here;
# imagine if we cooperate with MIT...

attributetype ( 1.3.6.1.4.1.11400.2.1.12 NAME 'department'
        DESC 'The department a student is in.'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

attributetype ( 1.3.6.1.4.1.11400.2.1.13 NAME 'FinalYear'
        DESC 'Either T or F.'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

# No idea what this is for.
attributetype ( 1.3.6.1.4.1.11400.2.1.14 NAME 'pid'
        DESC 'No idea what this is for.'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

attributetype ( 1.3.6.1.4.1.11400.2.1.15 NAME 'registrationDate'
        DESC 'Date the student registered, e.g., 17-08-2001
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

attributetype ( 1.3.6.1.4.1.11400.2.1.16 NAME 'site'
        DESC 'locate of campus, e.g., TY, CW, ST'
        EQUALITY caseIgnoreMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
        SINGLE-VALUE )

attributetype ( 1.3.6.1.4.1.11400.2.1.17 NAME 'year'
        DESC 'In what year is the student currently enrolled, e.g., 2'
        EQUALITY numericStringMatch
        SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
        SINGLE-VALUE )

#        ORDERING numericStringOrderingMatch

objectclass ( 1.3.6.1.4.1.11400.2.2.1 NAME 'student'
        SUP Person
	MAY ( 
              academicYear $ acOwner $ acType $ answer1 $ answer2 $
	      answer3 $ award $ batchUpdateFlag $ classCode $ course
	      $ courseDuration $ department $ FinalYear $ pid $
	      registrationDate $ site $ year ) )