You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by el...@apache.org on 2018/08/30 07:46:27 UTC

svn commit: r1839642 - in /directory/site/trunk/content/api/user-guide: 4.1-schema.mdtext 4.2-schema-manager.mdtext

Author: elecharny
Date: Thu Aug 30 07:46:27 2018
New Revision: 1839642

URL: http://svn.apache.org/viewvc?rev=1839642&view=rev
Log:
Some typo fixes

Modified:
    directory/site/trunk/content/api/user-guide/4.1-schema.mdtext
    directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext

Modified: directory/site/trunk/content/api/user-guide/4.1-schema.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/4.1-schema.mdtext?rev=1839642&r1=1839641&r2=1839642&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/4.1-schema.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/4.1-schema.mdtext Thu Aug 30 07:46:27 2018
@@ -24,9 +24,9 @@ Notice: Licensed to the Apache Software
 
 # 4.1 - Schema
 
-A **Schema** is a set of elements that are used by the **LDAP Server** to describe the data that are stored. The top two elements are **ObjectClass* and **AttributeType**. An **ObjectClass** is a container, describing what an **LDAP** entry can contain, while an **AttributeType** describe each singe element stored in this container.
+A **Schema** is a set of elements that are used by the **LDAP Server** to describe the data that are stored. The top two elements are **ObjectClass** and **AttributeType**. An **ObjectClass** is a container, describing what an **LDAP** entry can contain, while an **AttributeType** describe each singe element stored in this container.
 
-The key here is that an **LDAP** entry uses **ObjectClasses** to list all the possible **AttributeTypes** that entry can contain, some of them being mandatory, some other optional.
+The key here is that an **LDAP** entry uses **ObjectClasses** to list all the possible **AttributeTypes** that an entry can contain, some of them being mandatory, some other optional.
 
 Now, there is more. We have many other **Schema Objects** that are colateral:
 

Modified: directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext?rev=1839642&r1=1839641&r2=1839642&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext Thu Aug 30 07:46:27 2018
@@ -24,7 +24,7 @@ Notice: Licensed to the Apache Software
 
 # 4.2 - Schema Manager
 
-The API and the ApacheDS server components must to keep schema elements available to interroate and use. This is done through what we call a **SchemaManager**. It hides the internal structure of the schema objects from the users.
+The API and the ApacheDS server components must to keep schema elements available to interrogate and use. This is done through what we call a **SchemaManager**. It hides the internal structure of the schema objects from the users.
 
 
 ## Contents
@@ -46,7 +46,9 @@ The API and the ApacheDS server componen
 
 The **SchemaManager** stores all the Schema elements (**[AttributeTypes (e)]()**, **[ObjectClasses (e)]()**, ... Internally, we store these elements into what is call a **Registries**.  Registries are hives where each Schema Object is stored. Each schema element has a dedicated **Registry** associated with it. Think of it as a Map which returns a reference to a specific Schema Element according to its name or OID.
 
-    Note : each Schema Element is properly defined by one of its names or OID. The OID must be unique across all schema elements, when the name can be used in different schema element (for instance, the **audio** AttributeType or ObjectClass)
+    Note : 
+    each Schema Element is properly defined by one of its names or OID. The OID must be unique across all schema elements, 
+    when the name can be used in different schema element (for instance, the **audio** AttributeType or ObjectClass)
 
 From the user point of view, the **SchemaManager** is seen as a representation of the available LDAP schema elements. It can of course be extended, or modified, by adding or removing schema elements. For historic reasons, the schema elements are gathered into what we call a **schema**. Usually, this is what you load into a **schemaManager**