My mental model of service.Header.Purpose was that of a collection of common attributes that all DIDComm protocols share: @id, @type, ~thread, etc. Which is why the addition of ~purpose does not make sense as it is defined by a very specific protocol.
Should the handling of ~purpose be contained within its specific protocol service package?
https://github.com/hyperledger/aries-framework-go/blob/4d6d2333de088df2e2f555065ad99f4090a0be5d/pkg/didcomm/common/service/service.go#L42-L49
My mental model of
service.Header.Purpose
was that of a collection of common attributes that all DIDComm protocols share:@id
,@type
,~thread
, etc. Which is why the addition of~purpose
does not make sense as it is defined by a very specific protocol.Should the handling of
~purpose
be contained within its specific protocol service package?