Re: CFC: remove "the actor's namespace" from section on Object IDs in ActivityPub spec

Nope, if the a server is receiving via client to server an object that is an activity (because activities all extend from Object), and that activity has no object ID, then this language is saying one will be allocated, which would mean via C2S you could not send transient activities. I think this language would need to specifically exclude activities?

— Emelia

> On 28 Nov 2025, at 23:57, Evan Prodromou <evanp@socialwebfoundation.org> wrote:
> 
> Your comments on these two CFCs makes me think you might have switched them around.
> 
> Could you double-check that you're commenting on the correct thread?
> 
> Evan
> 
> On Fri, Nov 28, 2025 at 3:36 PM emelia <emelia@brandedcode.com <mailto:emelia@brandedcode.com>> wrote:
>> What about intentionally transient objects? (Which includes activities), per Section 3.1
>> 
>> Emelia
>> 
>>> On 28. Nov 2025, at 18:55, Evan Prodromou <evanp@socialwebfoundation.org <mailto:evanp@socialwebfoundation.org>> wrote:
>>> 
>>> 
>>> As noted in this issue, the section on object IDs in the ActivityPub spec mentions creating URLs in "the actor's namespace" without defining what that would mean:
>>> 
>>> https://github.com/w3c/activitypub/issues/443
>>> 
>>> To help with this problem, I've added the following proposed erratum:
>>> 
>>> Section 3.1, "Object identifiers", says in part that the server should create an ID "in the actor's namespace". "The actor's namespace" is not otherwise defined, making it impossible for implementers to comply. One solution is to remove this term from the sentence: However, for client to server communication, a server receiving an object posted to the outbox with no specified id SHOULD allocate an object ID and attach it to the posted object.
>>> 
>>> This is a call for consensus on adopting this erratum for ActivityPub. In the absence of objections to this change by 12 Dec 2025 AOE EOD, I will add this erratum to the Errata for ActivityPub, and make the corresponding change to the editor's draft.
>>> 
>>> To comment, please comment on issue #443 or reply in this thread.
>>> 
>>> Thanks,
>>> 
>>> Evan