cosine.schema

开放源码的ldap系统

#
#    ub-document-title INTEGER ::= 256
#
#    ub-document-version INTEGER ::= 256
#
#    ub-favourite-drink INTEGER ::= 256
#
#    ub-host INTEGER ::= 256
#
#    ub-information INTEGER ::= 2048
#
#    ub-unique-identifier INTEGER ::= 256
#
#    ub-personal-title INTEGER ::= 256
#
#    ub-photo INTEGER ::= 250000
#
#    ub-rfc822-mailbox INTEGER ::= 256
#
#    ub-room-number INTEGER ::= 256
#
#    ub-text-or-address INTEGER ::= 256
#
#    ub-user-class INTEGER ::= 256
#
#    ub-user-identifier INTEGER ::= 256
#
#    ub-organizational-status INTEGER ::= 256
#
#    ub-janet-mailbox INTEGER ::= 256
#
#    ub-building-name INTEGER ::= 256
#
#    ub-personal-signature ::= 50000
#
#    ub-audio INTEGER ::= 250000
#

# [back to 8]
# 8.  Object Classes
#
# 8.1.  X.500 standard object classes
#
#  A number of generally useful object classes are defined in X.521, and
#  these are supported.  Refer to that document for descriptions of the
#  suggested usage of these object classes.  The ASN.1 for these object
#  classes is reproduced for completeness in Appendix C.
#
# 8.2.  X.400 standard object classes
#
#  A number of object classes defined in X.400 are supported.  Refer to
#  X.402 for descriptions of the usage of these object classes.  The
#  ASN.1 for these object classes is reproduced for completeness in
#  Appendix C.
#
# 8.3.  COSINE/Internet object classes
#
#  This section attempts to fuse together the object classes designed
#  for use in the COSINE and Internet pilot activities.  Descriptions
#  are given of the suggested usage of these object classes.  The ASN.1
#  for these object classes is also reproduced in Appendix C.
#
# 8.3.1.  Pilot Object
#
#  The PilotObject object class is used as a sub-class to allow some
#  common, useful attributes to be assigned to entries of all other
#  object classes.
#
#    pilotObject OBJECT-CLASS
#        SUBCLASS OF top
#        MAY CONTAIN {
#            info,
#            photo,
#            manager,
#            uniqueIdentifier,
#            lastModifiedTime,
#            lastModifiedBy,
#            dITRedirect,
#            audio}
#    ::= {pilotObjectClass 3}
#
objectclass ( 0.9.2342.19200300.100.4.3 NAME 'pilotObject'
	SUP top AUXILIARY
	MAY ( info $ photo $ manager $ uniqueIdentifier $
		lastModifiedTime $ lastModifiedBy $ dITRedirect $ audio )
	)

# 8.3.2.  Pilot Person
#
#  The PilotPerson object class is used as a sub-class of person, to
#  allow the use of a number of additional attributes to be assigned to
#  entries of object class person.
#
#    pilotPerson OBJECT-CLASS
#        SUBCLASS OF person
#        MAY CONTAIN {
#                    userid,
#                    textEncodedORAddress,
#                    rfc822Mailbox,
#                    favouriteDrink,
#                    roomNumber,
#                    userClass,
#                    homeTelephoneNumber,
#                    homePostalAddress,
#                    secretary,
#                    personalTitle,
#                    preferredDeliveryMethod,
#                    businessCategory,
#                    janetMailbox,
#                    otherMailbox,
#                    mobileTelephoneNumber,
#                    pagerTelephoneNumber,
#                    organizationalStatus,
#                    mailPreferenceOption,
#                    personalSignature}
#    ::= {pilotObjectClass 4}
#
objectclass ( 0.9.2342.19200300.100.4.4
	NAME ( 'pilotPerson' 'newPilotPerson' )
	SUP person STRUCTURAL
	MAY ( userid $ textEncodedORAddress $ rfc822Mailbox $
		favouriteDrink $ roomNumber $ userClass $
		homeTelephoneNumber $ homePostalAddress $ secretary $
		personalTitle $ preferredDeliveryMethod $ businessCategory $
		janetMailbox $ otherMailbox $ mobileTelephoneNumber $
		pagerTelephoneNumber $ organizationalStatus $
		mailPreferenceOption $ personalSignature )
	)

# 8.3.3.  Account
#
#  The Account object class is used to define entries representing
#  computer accounts.  The userid attribute should be used for naming
#  entries of this object class.
#
#    account OBJECT-CLASS
#        SUBCLASS OF top
#        MUST CONTAIN {
#            userid}
#        MAY CONTAIN {
#            description,
#            seeAlso,
#            localityName,
#            organizationName,
#            organizationalUnitName,
#            host}
#    ::= {pilotObjectClass 5}
#
objectclass ( 0.9.2342.19200300.100.4.5 NAME 'account'
	SUP top STRUCTURAL
	MUST userid
	MAY ( description $ seeAlso $ localityName $
		organizationName $ organizationalUnitName $ host )
	)

# 8.3.4.  Document
#
#  The Document object class is used to define entries which represent
#  documents.
#
#    document OBJECT-CLASS
#        SUBCLASS OF top
#        MUST CONTAIN {
#            documentIdentifier}
#        MAY CONTAIN {
#            commonName,
#            description,
#            seeAlso,
#            localityName,
#            organizationName,
#            organizationalUnitName,
#            documentTitle,
#            documentVersion,
#            documentAuthor,
#            documentLocation,
#            documentPublisher}
#    ::= {pilotObjectClass 6}
#
objectclass ( 0.9.2342.19200300.100.4.6 NAME 'document'
	SUP top STRUCTURAL
	MUST documentIdentifier
	MAY ( commonName $ description $ seeAlso $ localityName $
		organizationName $ organizationalUnitName $
		documentTitle $ documentVersion $ documentAuthor $
		documentLocation $ documentPublisher )
	)

# 8.3.5.  Room
#
#  The Room object class is used to define entries representing rooms.
#  The commonName attribute should be used for naming pentries of this
#  object class.
#
#    room OBJECT-CLASS
#        SUBCLASS OF top
#        MUST CONTAIN {
#            commonName}
#        MAY CONTAIN {
#            roomNumber,
#            description,
#            seeAlso,
#            telephoneNumber}
#    ::= {pilotObjectClass 7}
#
objectclass ( 0.9.2342.19200300.100.4.7 NAME 'room'
	SUP top STRUCTURAL
	MUST commonName
	MAY ( roomNumber $ description $ seeAlso $ telephoneNumber )
	)

# 8.3.6.  Document Series
#
#  The Document Series object class is used to define an entry which
#  represents a series of documents (e.g., The Request For Comments
#  papers).
#
#    documentSeries OBJECT-CLASS
#        SUBCLASS OF top
#        MUST CONTAIN {
#            commonName}
#        MAY CONTAIN {
#            description,
#            seeAlso,
#            telephoneNumber,
#            localityName,
#            organizationName,
#            organizationalUnitName}
#    ::= {pilotObjectClass 9}
#
objectclass ( 0.9.2342.19200300.100.4.9 NAME 'documentSeries'
	SUP top STRUCTURAL
	MUST commonName
	MAY ( description $ seeAlso $ telephonenumber $
		localityName $ organizationName $ organizationalUnitName )
	)

# 8.3.7.  Domain
#
#  The Domain object class is used to define entries which represent DNS
#  or NRS domains.  The domainComponent attribute should be used for
#  naming entries of this object class.  The usage of this object class
#  is described in more detail in [3].
#
#    domain OBJECT-CLASS
#        SUBCLASS OF top
#        MUST CONTAIN {
#            domainComponent}
#        MAY CONTAIN {
#            associatedName,
#            organizationName,
#            organizationalAttributeSet}
#    ::= {pilotObjectClass 13}
#
objectclass ( 0.9.2342.19200300.100.4.13 NAME 'domain'
	SUP top STRUCTURAL
	MUST domainComponent
	MAY ( associatedName $ organizationName $ description $
		businessCategory $ seeAlso $ searchGuide $ userPassword $
		localityName $ stateOrProvinceName $ streetAddress $
		physicalDeliveryOfficeName $ postalAddress $ postalCode $
		postOfficeBox $ streetAddress $
		facsimileTelephoneNumber $ internationalISDNNumber $
		telephoneNumber $ teletexTerminalIdentifier $ telexNumber $
		preferredDeliveryMethod $ destinationIndicator $
		registeredAddress $ x121Address )
	)

# 8.3.8.  RFC822 Local Part
#
#  The RFC822 Local Part object class is used to define entries which
#  represent the local part of RFC822 mail addresses.  This treats this
#  part of an RFC822 address as a domain.  The usage of this object
#  class is described in more detail in [3].
#
#    rFC822localPart OBJECT-CLASS
#        SUBCLASS OF domain
#        MAY CONTAIN {
#            commonName,
#            surname,
#            description,
#            seeAlso,
#            telephoneNumber,
#            postalAttributeSet,
#            telecommunicationAttributeSet}
#    ::= {pilotObjectClass 14}
#
objectclass ( 0.9.2342.19200300.100.4.14 NAME 'RFC822localPart'
	SUP domain STRUCTURAL
	MAY ( commonName $ surname $ description $ seeAlso $ telephonenumber $
		physicalDeliveryOfficeName $ postalAddress $ postalCode $
		postOfficeBox $ streetAddress $
		facsimileTelephoneNumber $ internationalISDNNumber $
		telephoneNumber $ teletexTerminalIdentifier $
		telexNumber $ preferredDeliveryMethod $ destinationIndicator $
		registeredAddress $ x121Address )
	)

# 8.3.9.  DNS Domain
#
#  The DNS Domain (Domain NameServer) object class is used to define
#  entries for DNS domains.  The usage of this object class is described
#  in more detail in [3].
#
#    dNSDomain OBJECT-CLASS
#        SUBCLASS OF domain
#        MAY CONTAIN {
#            ARecord,
#            MDRecord,
#            MXRecord,
#            NSRecord,
#            SOARecord,
#            CNAMERecord}
#    ::= {pilotObjectClass 15}
#
objectclass ( 0.9.2342.19200300.100.4.15 NAME 'dNSDomain'
	SUP 'domain' STRUCTURAL
	MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ 
		SOARecord $ CNAMERecord )
	)

# 8.3.10.  Domain Related Object
#
#  The Domain Related Object object class is used to define entries
#  which represent DNS/NRS domains which are "equivalent" to an X.500
#  domain: e.g., an organisation or organisational unit.  The usage of
#  this object class is described in more detail in [3].
#
#    domainRelatedObject OBJECT-CLASS
#        SUBCLASS OF top
#        MUST CONTAIN {
#            associatedDomain}
#    ::= {pilotObjectClass 17}
#
objectclass ( 0.9.2342.19200300.100.4.17 NAME 'domainRelatedObject'
	SUP top AUXILIARY
	MUST associatedDomain )

# 8.3.11.  Friendly Country
#
#  The Friendly Country object class is used to define country entries
#  in the DIT.  The object class is used to allow friendlier naming of
#  countries than that allowed by the object class country.  The naming
#  attribute of object class country, countryName, has to be a 2 letter
#  string defined in ISO 3166.
#
#    friendlyCountry OBJECT-CLASS
#        SUBCLASS OF country
#        MUST CONTAIN {
#            friendlyCountryName}
#    ::= {pilotObjectClass 18}
#
objectclass ( 0.9.2342.19200300.100.4.18 NAME 'friendlyCountry'
	SUP country STRUCTURAL
	MUST friendlyCountryName )

# 8.3.12.  Simple Security Object
#
#  The Simple Security Object object class is used to allow an entry to
#  have a userPassword attribute when an entry's principal object
#  classes do not allow userPassword as an attribute type.
#
#    simpleSecurityObject OBJECT-CLASS
#        SUBCLASS OF top
#        MUST CONTAIN {
#            userPassword }
#    ::= {pilotObjectClass 19}
#
## (in core.schema)
## objectclass ( 0.9.2342.19200300.100.4.19 NAME 'simpleSecurityObject'
##	SUP top AUXILIARY
##	MUST userPassword )

# 8.3.13.  Pilot Organization
#
#  The PilotOrganization object class is used as a sub-class of
#  organization and organizationalUnit to allow a number of additional
#  attributes to be assigned to entries of object classes organization
#  and organizationalUnit.
#
#    pilotOrganization OBJECT-CLASS
#        SUBCLASS OF organization, organizationalUnit
#        MAY CONTAIN {
#                    buildingName}
#    ::= {pilotObjectClass 20}
#
objectclass ( 0.9.2342.19200300.100.4.20 NAME 'pilotOrganization'
	SUP ( organization $ organizationalUnit ) STRUCTURAL
	MAY buildingName )

# 8.3.14.  Pilot DSA
#
#  The PilotDSA object class is used as a sub-class of the dsa object
#  class to allow additional attributes to be assigned to entries for
#  DSAs.
#
#    pilotDSA OBJECT-CLASS
#        SUBCLASS OF dsa
#        MUST CONTAIN {
#            dSAQuality}
#    ::= {pilotObjectClass 21}
#
objectclass ( 0.9.2342.19200300.100.4.21 NAME 'pilotDSA'
	SUP dsa STRUCTURAL
	MAY dSAQuality )

# 8.3.15.  Quality Labelled Data
#
#  The Quality Labelled Data object class is used to allow the
#  assignment of the data quality attributes to subtrees in the DIT.
#
#  See [8] for more details.
#
#    qualityLabelledData OBJECT-CLASS
#        SUBCLASS OF top
#        MUST CONTAIN {
#            dSAQuality}
#        MAY CONTAIN {
#            subtreeMinimumQuality,
#            subtreeMaximumQuality}
#    ::= {pilotObjectClass 22}
objectclass ( 0.9.2342.19200300.100.4.22 NAME 'qualityLabelledData'
	SUP top AUXILIARY
	MUST dsaQuality
	MAY ( subtreeMinimumQuality $ subtreeMaximumQuality )
	)


# References
#
#    [1]  CCITT/ISO, "X.500, The Directory - overview of concepts,
#         models and services, CCITT /ISO IS 9594.
#
#    [2]  Kille, S., "The THORN and RARE X.500 Naming Architecture, in
#         University College London, Department of Computer Science
#         Research Note 89/48, May 1989.
#
#    [3]  Kille, S., "X.500 and Domains", RFC 1279, University College
#         London, November 1991.
#
#    [4]  Rose, M., "PSI/NYSERNet White Pages Pilot Project: Status
#         Report", Technical Report 90-09-10-1, published by NYSERNet
#         Inc, 1990.
#
#    [5]  Craigie, J., "UK Academic Community Directory Service Pilot
#         Project, pp. 305-310 in Computer Networks and ISDN Systems
#         17 (1989), published by North Holland.
#
#    [6]  Mockapetris, P., "Domain Names - Concepts and Facilities",
#         RFC 1034, USC/Information Sciences Institute, November 1987.
#
#    [7]  Mockapetris, P., "Domain Names - Implementation and
#         Specification, RFC 1035, USC/Information Sciences Institute,