angus
February 27, 2024, 7:35am
20
Cool. The only slight issue I have with it is that I agree with those who have pointed out that it seems to use target inappropriately, see
Having the target property in the object is a spec violation (because of the domain of the target property ). It is a property of Activity and not of Object. But I understand the usefulness of knowing that “an object was created to be part of a collection and should only be considered in its context”. Therefore, maybe for objects use the context property instead and keep using target only in activities?
For example:
{
"@context": "https://www.w3.org/ns/activitystreams",
"id": "http://exampl…
or
I agree, I do have multiple issues with this FEP (I’d say it’s insufficient clear in many respects, and the thing about inlining an abbreviated form of the collection object can be at odds with JSON-LD), but they do not matter very much in practice. I missed the fact that target was not a valid property for non-activity objects (and would clash with the meaning of target in activities). This is not a practical issue for this specific use case either, but that’s not great.
Nevertheless, I think…
I think context makes more sense, as @trwnh and others have advocated. I don’t really know how the FEP process works, but it seems like there’d be a decent case for substituting context for target.
cc @macgirvin
1 Like