From 4804ee387f8b48b54b4241e9950df85046167dd1 Mon Sep 17 00:00:00 2001 From: Keith Hazelton Date: Thu, 5 Nov 2020 11:23:34 -0600 Subject: [PATCH] terminology refinements --- README.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 80e02db..35ef5de 100644 --- a/README.md +++ b/README.md @@ -2,14 +2,12 @@ ## TAP Attribute Dictionary -The [TAP Attribute Dictionary](tap-core-person-schema.adoc) defines a dictionary of common -attributes used across various components of the TAP portfolio. The -normative specification of the TAP Attribute Dictionary is abstract -- it cannot be used directly. It 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 TAP Attribute Dictionary: - +The [TAP Attribute Dictionary](tap-core-person-schema.adoc) defines a large collection of +attributes used across various components of the TAP portfolio and higher education more generally. The +normative documentation of the TAP Attribute Dictionary is abstract -- it is designed to be used only when mapped to specific formats and protocols. It is +best thought of as an *attribute library* that can be drawn from to construct other documents, specifications, and software artifacts. +When discussing schema, TAP uses two terms, formatting and protocol, in quite specific ways. * **Formatting**: Mappings of the TAP Attribute Dictionary entries to a specific form, such as JSON, XML, or YAML.