Gregory's Server@sl007 @humanetech You keep saying that as if it's possible to have someone send you an activity your software doesn't support. The whole point of having capability negotiation is to solve this very problem before it has a chance to happen.
|
5 comments
Gregory replied to smallcircles (Humane Tech Now)
@humanetech @sl007 Yeah. I use Offer{Follow} as a friend request. But I only send it to actors that have supportsFriendRequests=true. I change my UI accordingly. 
Sebastian Lasse, redaktor.me replied to Gregory
Citing the spec. again please note that MUST is written in capital letters for a purpose. 
smallcircles (Humane Tech Now) replied to Sebastian Lasse, redaktor.me
But does it say what Followers / Following means? What if I have completely different custom actor types.. Tim Berners-Lee's Semantic Web failed because there was they idea to have universal semantics that applied globally. It is very important to have closed vocabularies, imho, where the terminology only have well-defined meaning in a specific domain. This matches the idea of domain-driven design (DDD) where you have bounded contexts.
Gregory replied to smallcircles (Humane Tech Now)
@humanetech @sl007 You would technically follow the spec if you have these collections, return them as always empty, and send Reject{Follow} for any Follow you receive. |
@sl007
I agree with @grishka
Every activity has different interpretations depending on the domain it is used in. In a webshop you might have as:Offer literally meaning something that is for sale.
But Offer is already being used in other contexts.
In #forgefed an as:Note is a comment to a Ticket or Merge Request.
etc.