Replying to @silverpill@mitra.social
@silverpill @technical-discussion @benpate If you are going through the trouble of using your own vocabulary, why not at least make it so that namespace conflicts don't ever happen again, similarly like they do with semantics using AS Vocab now.
If you implement OfferEndorsement and I want to use it as well, but for something incompatible with your thing. Then I guess I need to invent a new less descriptive name for my thing like: NewAPServerOfferEndorsement, if you effectively reserve that name for your thing and depend on that name being unique for handling.
So I think, something like below is a better solution to the same problem, while admittedly looking worse:
fep-3447:OfferEndorsementfep-3447:AcceptEndorsementfep-3447:RejectEndorsementfep-3447:UndoEndorsement
Or
fep-3447:Offerfep-3447:Acceptfep-3447:Rejectfep-3447:Undo





