From 6b8c19132d56bf8dd2d9409bb0457582c6be2a3c Mon Sep 17 00:00:00 2001 From: eslao Date: Tue, 16 Jan 2024 09:57:31 -0500 Subject: [PATCH] Remove mentions of galleries (#146) Co-authored-by: Simeon Warner --- docs/0.1/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/0.1/index.md b/docs/0.1/index.md index fee1a16..1734d78 100644 --- a/docs/0.1/index.md +++ b/docs/0.1/index.md @@ -59,7 +59,7 @@ __Previous Version:__ None ## 1. Introduction {: #introduction} -The Entity Metadata Management API is intended to establish a pattern that supports sharing changes to entities and their metadata curated by entity metadata providers with the community of entity metadata consumers (e.g. libraries, museums, galleries, archives). Use of a consistent pattern allows for the creation of software tools for producing and consuming changes in entity metadata. +The Entity Metadata Management API is intended to establish a pattern that supports sharing changes to entities and their metadata curated by entity metadata providers with the community of entity metadata consumers (e.g. libraries, museums, archives). Use of a consistent pattern allows for the creation of software tools for producing and consuming changes in entity metadata. This specification is based on the [Activity Streams 2.0 specification][org-w3c-activitystreams]. It defines a usage pattern and minor extensions specific to entity metadata management. @@ -81,7 +81,7 @@ Work that is out of scope of this API includes the recommendation or creation of ### 1.2. Use Cases {: #use-cases} -The following three use cases motivate this specification. They are drawn from workflows needed by libraries, museums, galleries, and archives. +The following three use cases motivate this specification. They are drawn from workflows needed by libraries, museums, and archives. #### 1.2.1. Change Tracking {: #change-tracking}