FEP-ef61: Portable Objects

[silverpill]

That would conflict with other uses of alsoKnownAs. I talked about this recently in adjacent topic:

@silverpill

The meaning of alsoKnownAs property is not well-defined. In my opinion, it should be used to describe different resources linked to the same entity (example: two actors representing the same person), this is how Mastodon uses it and how it is used in FEP-c390.

it shouldn’t be used to describe different identifiers of the same resource (e.g. actor ID and a corresponding acct URI), for that I’m proposing aliases property (in FEP-ef61).

The name of this property can be changed (to sameAs?), but it should be distinct from alsoKnownAs.