From 8947cfb2ecceae8c063511d4f5a899261d4b0f9e Mon Sep 17 00:00:00 2001 From: Keith Hazelton Date: Thu, 5 Nov 2020 10:04:09 -0600 Subject: [PATCH] modify terminology --- README.md | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index b9434f1..32629e7 100644 --- a/README.md +++ b/README.md @@ -2,23 +2,21 @@ ## TAP Core Person Schema -The [TAP Core Person Schema](tap-core-person-schema.adoc) defines a dictionary of common +The [TAP Attribute Dictiohnary](tap-core-person-schema.adoc) defines a dictionary of common attributes used across various components of the TAP portfolio. The -authoritative Core Schema is abstract -- it cannot be used directly, but is -best thought of as an *attribute library* that can be used to construct other -documents. +normative specification of the TAP Attribute Dictionary is abstract -- it cannot be used directly, but is +best thought of as an *attribute library* that can be used to construct othe documents. -The following types of documents are defined as part of the Core Schema library: +The following types of documents are defined as part of the TAP Attribute Dictionary: -* **Representations**: Mappings of the Core Schema to a specific form, such as + + +* **Formatting**: Mappings of the Core Schema to a specific form, such as JSON, XML, or YAML. * [TAP Core Person Schema: How to Create a JSON Representation](tap-core-person-schema-create-json-representation.adoc) (CS-JSON) -* **Profiles**: Selections of Core Schema attributes for a particular purpose. - * **Protocols**: A specification for implementation, based on a Representation and perhaps a Profile. Of all the Core Schema documents, only Protocols are actually implementable in software. -As an example, the **eduPerson LDAP Schema** would be a *Protocol* that -references the *eduPerson Profile* and the *LDAP Representation*. +As an example, **eduPerson LDAP** would be an LDAP **Protocol** expressed in LDAP **format**.