Open OR13 opened 5 years ago
@dhh1128 @TelegramSam this is interesting ideas that shares a lot of concepts to DIDComm semantic layer. Have you seen this?
I had not seen it before. I agree that it does have a bit of overlap. Instead of using mixins/decorators, it uses reserved fieldnames. It is thus a thick base class, essentially.
The thing I would most like to emulate from it is the clarity of its documentation. Perhaps we could produce an RFC (or an auxiliary doc to the existing DIDComm or Decorators RFC) that enumerates the possibilities in a similar way.
https://github.com/cjus/umf/blob/master/umf.md
Seems like these things are similar, or rather that DIDComm is used to construct messages that are likely to be of similar format. At the very least, its worth listing similar concepts.
The main reason I link this is the clarity over HTTP vs Peer 2 Peer.
I think that kind of definition is probably buried elsewhere in hyperledger, and it should be highlighted more.
Related HN Article: https://news.ycombinator.com/item?id=17302596