ADSI providers create a representation of the underlying schema by implementing the schema-management interfaces IADsClass, IADsProperty, and IADsSyntax. For example, on LDAP, IADsClass represents the attribute "objectClass" which contains values that identify every type of object known to an ldap server. NDS uses "object class". WinNT defines each object type directly, such as "Domain", "Computer", or "User". In all these cases, the IADsClass interface supplies methods to identify and manage the list of properties or attributes a class uses. Similarly, IADsProperty supplies methods to define a property as it is known to the underlying directory service. If you browse a directory service directly, you probably will not find anything corresponding to syntax objects. ADSI abstracts the syntax information as necessary and lets you use IADsSyntax to identify the syntax needed to represent an object's data.