[sabayon] Proposed Sabayon schema for Fedora Directory Server (FDS)

["Wilmer Jaramillo M." <wilmer fedoraproject org>]

Hi folks, please review proposed LDAP scheme for Fedora Directory
Server(FDS) based on the same schema of OpenLDAP, the rules added
correspond to the definition of "ObjectClassDescription" in RFC 2252,
remember that in some cases FDS does not publish whether an object
class is abstract, structural or auxiliary.
Changelog
- Syntax for FDS to work.
- Changed matching rules "may" by "must" in sabayonProfileName.
- Added "cn" in sabayonProfileURLObject
- Added "sup top" to sabayonProfileNameObject

The user do an LDAP search operation with a base DN set to for
retrieving the Sabayon schema used by FDS:
$ /opt/fedora-ds/shared/bin/ldapsearch -T -b "cn=schema"
'(ObjectClass=*)' | grep sabayon

Finally, the search result returned by the server would consist of the
followings entrys:
objectClasses: ( 1.3.6.1.4.1.2312.4.3.4.1 NAME 'sabayonProfile' DESC
'sabayon profile' SUP top STRUCTURAL MUST cn MAY ( sabayonProfileURL $
description ) X-ORIGIN 'user defined' )
objectClasses: ( 1.3.6.1.4.1.2312.4.3.4.2 NAME
'sabayonProfileNameObject' DESC 'contains sabayon profile name' SUP
top AUXILIARY MUST sabayonProfileName X-ORIGIN 'user defined' )
objectClasses: ( 1.3.6.1.4.1.2312.4.3.4.3 NAME
'sabayonProfileURLObject' DESC 'contains sabayon profile' SUP top
AUXILIARY MUST cn MAY sabayonProfileURL X-ORIGIN 'user defined' )
attributeTypes: ( 1.3.6.1.4.1.2312.4.3.3.1 NAME 'sabayonProfileURL'
DESC 'The URL of a sabayon profile' SUP labeledURI SYNTAX
1.3.6.1.4.1.1466.115.121.1.26 X-ORIGIN 'user defined' )
attributeTypes: ( 1.3.6.1.4.1.2312.4.3.3.2 NAME 'sabayonProfileName'
DESC 'The Name of a sabayon profile' EQUALITY caseIgnoreMatch SUBSTR
caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
X-ORIGIN 'user defined' )

-- 
Wilmer Jaramillo M.
GPG Key Fingerprint = 0666 D0D3 24CE 8935 9C24 BBF1 87DD BEA2 A4B2 1E8A

###########################################################
# 1.3.6.1.4.1.2312 dot notation
# 1.3.6.1.4.1.2312.4.3.3 attributeTypes
# 1.3.6.1.4.1.2312.4.3.4 objectClasses
###########################################################
dn: cn=schema
# These example schema can be used to integrate sabayon with ldap
# However, the ldap support in sabayon is very flexible, so you can
# choose to do your own ldap integration using a different schema
# This attribute is used to point to a sabayon profile file
# that is accessible via a (typically http) url
attributeTypes: (
  1.3.6.1.4.1.2312.4.3.3.1
  NAME 'sabayonProfileURL'
  DESC 'The URL of a sabayon profile'
  SUP labeledURI
)
# This attribute is used to store the name of a sabayon profile.
# It can refer to either a local zipfile (which will be looked up
# in /etc/desktop-profiles/$(name).zip), or it can be used to
# map to another ldap object that maps to the final profile URL
attributeTypes: (
  1.3.6.1.4.1.2312.4.3.3.2
  NAME 'sabayonProfileName'
  DESC 'The Name of a sabayon profile'
  EQUALITY caseIgnoreMatch 
  SUBSTR caseIgnoreSubstringsMatch
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 
  SINGLE-VALUE
)
# Simple example object to store profile information
# If you use this or something similar instead of a direct URL
# in your user object you get more flexibility.
objectClasses: (
  1.3.6.1.4.1.2312.4.3.4.1
  NAME 'sabayonProfile' 
  DESC 'sabayon profile' 
  SUP top
  STRUCTURAL
  MUST cn
  MAY ( sabayonProfileURL $ description )
)
# Use these to put sabayonProfileName or sabayonProfileURL
# attributes in an objetc
objectClasses: (
  1.3.6.1.4.1.2312.4.3.4.2
  NAME 'sabayonProfileNameObject'
  DESC 'contains sabayon profile name' 
  SUP top
  AUXILIARY
  MUST sabayonProfileName 
)
objectClasses: ( 
  1.3.6.1.4.1.2312.4.3.4.3  
  NAME 'sabayonProfileURLObject'
  DESC 'contains sabayon profile'
  SUP top
  AUXILIARY
  MUST cn
  MAY sabayonProfileURL  
)