You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: eventstreams.bs
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -435,7 +435,7 @@ When using the current time in calculations, the consumer MUST take into account
435
435
The `ldes:timestampPath` points to the timestamp in the member that can be compared with the current time minus the durations.
436
436
When the `ldes:versionTimestampPath` has been set, the two version durations must be compared with this timestamp.
437
437
438
-
Historically, there are more specific types of retention policies that MUST remain supported, although their use is discouraged in favor of the retention policy design just introduced.
438
+
Historically, there are more specific types of retention policies that MUST remain supported, although their use is discouraged in favour of the retention policy design just introduced.
439
439
These retention policy types are:
440
440
1. `ldes:DurationAgoPolicy`: a time-based retention policy in which data generated before a specified duration is not retained.
441
441
2. `ldes:LatestVersionSubset`: a version subset based on the latest versions of an entity in the stream.
@@ -177,7 +177,7 @@ Point-in-time start and version window
177
177
178
178
Notes
179
179
- Changing a retention policy affects client expectations; keep the policy in sync with the actual availability of members.
180
-
- Historical, more specific policy classes (`ldes:DurationAgoPolicy`, `ldes:LatestVersionSubset`, `ldes:PointInTimePolicy`) SHOULD remain supported for backward compatibility but are discouraged in favor of `ldes:retentionPolicy` with the properties above.
180
+
- Historical, more specific policy classes (`ldes:DurationAgoPolicy`, `ldes:LatestVersionSubset`, `ldes:PointInTimePolicy`) SHOULD remain supported for backward compatibility but are discouraged in favour of `ldes:retentionPolicy` with the properties above.
@@ -100,7 +105,7 @@ If the node is not going to contain new relations leading to new members, or new
100
105
The class `ldes:EventSource` is a subclass of `dcat:Distribution`,
101
106
specialized to represent a feed that uses a chronological search tree to make a Linked Data Event Stream available in order.
102
107
103
-
An `ldes:EventSource` can only be published for LDESs that have `ldes:timestampPath` set, and thus publishes its entities in chronological order.
108
+
An `ldes:EventSource` can only be published for `ldes:EventStream` that have `ldes:timestampPath` set, and thus publishes its entities in chronological order.
0 commit comments