-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use of "reference" with inbox
and outbox
#289
Comments
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 And a bit further it mentions 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, 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 |
I added an erratum for this:
|
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.
The text was updated successfully, but these errors were encountered: