From c3b6eeaeb12a0213acb940fcdc2dd09cb66e74a8 Mon Sep 17 00:00:00 2001 From: Keith Hazelton Date: Thu, 5 Nov 2020 12:14:25 -0600 Subject: [PATCH] Update README.md --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index afd8a4d..dd1d2c8 100644 --- a/README.md +++ b/README.md @@ -16,4 +16,7 @@ When discussing schema, TAP defines two terms, formatting and protocol, in quite * **Protocols**: A formal specification defining the way two entities interoperate to accomplish a specific action. Protocols are designed to be implementable in software. -As an example, **eduPerson LDIF** would refer to the eduPerson schema expressed in the **format** defined in _RFC2849 The LDAP Data Interchange Format (LDIF) - Technical Specification_ +Example 1: "eduPerson LDIF" would refer to the eduPerson attributes expressed in the **format** defined in _RFC2849 The LDAP Data Interchange Format (LDIF) - Technical Specification_ + +Example 2: eduPerson attributes on an LDAP server can be queried by an LDAP client using the LDAP **Protocol** defined in _RFC4519 Lightweight Directory Access Protocol (LDAP) Schema for User Applications_ +