FEP 7888 lays out some guidelines for use of the context as a common property between a set of objects when they can be grouped together through reply association (e.g. a reply-tree).
This proposal aims to extend these guidelines further by codifying:
context.attributedTo.The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC-2119].
A context MUST have an owner. The following are upgrades to FEP 7888 that pertain to ownership:
context MUST be resolvable.context MUST contain:
attributedTo denoting the authority/owner of that context.context.attributedTo MUST resolve to an actor (ActivityPub §4.1 Actor Objects).A resolvable context collection (see FEP f228) declares an owner by setting context.attributedTo to a resolvable URI.
{
"id": "https://cats.example.org/1/context",
"type": "OrderedCollection",
"attributedTo": "https://cats.example.org/users/cat",
"items": [...]
}
Inheritance is considered only when a new object being published has a relation (typically via inReplyTo) to another object.
There are situations where a relation exists but context is explicitly not inherited (e.g. forked topic, quote post). These situations are out of scope of this FEP.
The object MUST inherit context from the root node, if the property is present and resolvable. Otherwise the object MUST NOT publish a context.
Implementors SHOULD map that inherited context to a local identifier (if applicable) to support future use-cases/activities.
When publishing an object with a context property outside the local domain, the context owner SHOULD be addressed (to, cc, audience).
[!NOTE] If an object is at the root/top-level, then there is nothing to inherit and a new context should be generated.
When consuming an object declaring a context outside the local domain, the object’s membership MAY be verified by resolving the context directly.
[!NOTE] The remote
context’s server may not reflect the object’s membership in a timely manner due to delays in processing (i.e. network congestion, approval queues, etc.)
CC0 1.0 Universal (CC0 1.0) Public Domain Dedication
To the extent possible under law, the authors of this Fediverse Enhancement Proposal have waived all copyright and related or neighboring rights to this work.