Email or username:

Password:

Forgot your password?
Top-level
smallcircles (Humane Tech Now)

@ta180m @trwnh @caesar

Type arrays aren't explicitly mentioned in #ActivityPub spec, but they are in #ActivityStreams in a bunch of examples.

For instance "Object that is both a Place and a Location"

w3.org/TR/activitystreams-core

Or in the text stating that vCard should be used to extend an Actor.

w3.org/TR/activitystreams-core

Most elaborate example is:

w3.org/TR/activitystreams-core

Supporting a type array is spec conformant. Not supporting it is a shortcoming of the impl.

3 comments
replied to smallcircles (Humane Tech Now)

@humanetech @trwnh @caesar Ah, interesting, so it is in the spec.

In that case, the real problem is that existing AP software don't support type arrays, so if we used the solution of type arrays, we'd also have to send PRs to Mastodon and the others.

infinite love ⴳ replied to

@ta180m @humanetech @caesar the PRs should probably happen anyway, but the type array isn't strictly necessary IMO because marking a Ticket additionally as a Note doesn't really provide any additional benefit, does it? Multi-type stuff is useful mostly for multiple vocabs/contexts.

replied to infinite love ⴳ

@trwnh @humanetech @caesar Yeah, type arrays were just an alternate solution we thought of, but for now we're going to go with sending Mastodon a PR to run the conversion logic on all types instead of just the few hardcoded ones.

Go Up