Open cjslep opened 6 years ago
I think it may be an omission from the description of "outbox". Both should probably say "reference", but perhaps the author thought it might be implied? If both are a reference (URI), then the example would make sense.
I was just as confused as @cjslep by this text.
Furthermore for followers
, following
and liked
the specification mentions that these represent 'A link to an [ActivityStreams] collection' which implies it can contain either a URI or a Link
entity.
And a bit further it mentions stream
with only the text 'A list of supplementary Collections which may be of interest.'. Is this meant to be an array of URI's?
IMHO the specification would be much clearer if the new properties of ActivityPub were more clearly explained, such as the entities and properties in ActivityStreams Vocabulary (i.e. in tabular format).
The correct type for all of these properties, inbox
, outbox
, etc. is either in-line or an URI. I agree that the language is confusing.
I think this should be documented in the Errata, with an example of inline and URI versions of inbox and outbox.
+1 making the language consistent between inbox/outbox
For
inbox
andoutbox
the specification says:A reference is implicitly understood to mean a URI that, when resolved as stated in ActivityPub, will yield an
OrderedCollection
. Thus, this says that the inbox must be a URI.However, for the outbox it specifically omits the word reference, which heavily implies the actual
OrderedCollection
must be embedded within the actor.This kind of imprecise use of language, coupled with the permissiveness of ActivityStreams, implies that Example 9 is incorrect:
Please either omit "reference" when describing the inbox, permitting implementors to inline the OrderedCollections or not, or standardize "reference" to mean inlining the actual ActivityStream data is not permitted.