From 97fc0fb0816e29eea192915b3bc7c81a86fe11f7 Mon Sep 17 00:00:00 2001 From: Vitor Pamplona Date: Thu, 4 Jan 2024 11:07:46 -0500 Subject: [PATCH] renames property to attribute for consistency --- 01.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/01.md b/01.md index 54f69149..a59d0705 100644 --- a/01.md +++ b/01.md @@ -68,7 +68,7 @@ To verify the authenticity of an event: ## Kinds -The `.kind` property specifies the meaning of an event, its tags and it is further defined in the various NIPs in this repository +The `.kind` attribute specifies the meaning of an event, its tags and it is further defined in the various NIPs in this repository Specific ranges define storage behaviors: @@ -152,15 +152,15 @@ To open and update, and close subscriptions, Clients MUST use the following form A `REQ` message may contain multiple filters which are interpreted as an OR statement: events that match any of the filters are to be returned. -Properties in each filter are a logical AND statement: all present properties must match for the filter to pass. +Attributes are a logical AND statement: all present attributes must match for the filter to pass. -Array properties (i.e. `ids`, `authors`, `kinds`, and tag filters) represent a logical OR statement. At least one of the arrays' values must match the respective field in the event to be considered a match. In the case of tag attributes such as `#e`, for which an event may have multiple values, the event and filter condition values must have at least one item in common. +Array attributes (i.e. `ids`, `authors`, `kinds`, and tag filters) represent a logical OR statement. At least one of the arrays' values must match the respective field in the event to be considered a match. In the case of tag attributes such as `#e`, for which an event may have multiple values, the event and filter condition values must have at least one item in common. The `ids`, `authors`, `#e`, and `#p` filter lists MUST contain exact 64-character lowercase hex values. -The `since` and `until` properties are used to specify the time range of events returned in the subscription. An event matches the filter if `since <= created_at <= until` holds. +The `since` and `until` attributes are used to specify the time range of events returned in the subscription. An event matches the filter if `since <= created_at <= until` holds. -The `limit` property informs the maximum number of events to return, sorted by `.created_at` desc. It operates over the previously stored events and is ignored afterward. +The `limit` attribute informs the maximum number of events to return, sorted by `.created_at` desc. It operates over the previously stored events and is ignored afterward. ### Subscription Responses