Support extended types
We read in https://www.w3.org/TR/activitystreams-core/#object
When an implementation uses an extension type that overlaps with a core vocabulary type, the implementation MUST also specify the core vocabulary type.
The example given is
{
"@context": [
"https://www.w3.org/ns/activitystreams",
{
"gr": "http://purl.org/goodrelations/v1#"
}
],
"type": ["Place", "gr:Location"],
"name": "Sally's Restaurant",
"longitude": 12.34,
"latitude": 56.78,
"gr:category": "restaurants/french_restaurants"
}
The idea is if you don't support ["Place", "gr:Location"]
, you should still process the object as Place
. AFAIK we don't have implementations like this in the wild yet, but this would partly solve the problem of having to implement an increasing number of custom objects. Having a server with support for this could make it more attractive for people to use extensions of core types like this, rather than just creating new ones.