- From: Evan Prodromou <evan@prodromou.name>
- Date: Wed, 28 Jun 2023 12:41:22 -0400
- To: "public-swicg@w3.org" <public-swicg@w3.org>
- Message-Id: <26BCE283-9F64-47BD-BB81-FE77816ED232@prodromou.name>
We got to 2 issues today: * #377 Signaling that some collections are managed by the server <https://github.com/w3c/activitypub/issues/377> This was resolved with a page in the Primer on server-managed collections <https://www.w3.org/wiki/ActivityPub/Primer/Server-Managed_Collections> with some guidance on when and if to use standard collection-management activities like `Add` and `Remove` to handle server-managed collections * #376 Relaxing the requirement for OrderedCollection to always be reverse-chronological? <https://github.com/w3c/activitypub/issues/376> There is a statement in the “Collections” section of ActivityPub that says that all those collections must be in reverse chronological order. Because of the wording, taken out of context, there are some people who erroneously infer that all collections used in ActivityPub, even in extensions or other vocabularies, must be in reverse chronological order. The proposed solution is to add an erratum <https://www.w3.org/wiki/ActivityPub_errata/Proposed>to make it explicit that the requirement only applies to the specified collections. Thanks to all who came! Evan > On Jun 28, 2023, at 10:40 AM, Evan Prodromou <evan@prodromou.name> wrote: > > https://meet.jit.si/moderated/c1c3c53fd2a3a78819e0cbb534848202b26b6af380c0af284edab895e35cb3c1
Received on Wednesday, 28 June 2023 16:41:37 UTC