Yes, I've been checking the Verifiable Claims specs and that's from where most of my questions arise.
I don't see why you make a differentiation here about Sovrin (the ledger I assume) and Sovrin agents for this case. Wouldn't signed claims be stored on the ledger as well? Or are these meant to be somehow "private"?
In any case, my questions is more related to the functional scope of having claims that can be signed. Can I have claims signed by multiple parties? Or is it only the claim holder (or subject (or creator)) the one who can sign the claim?
Example: A trust anchor is setting up a new identity for a bank customer on the ledger (genesis claim), this trust anchor is the creator of such claim, and the holder in this case is the customer, but such claim might be signed by a bank (or even by multiple banks and/or other relevant authorities) after going through KYC verification process...
In a more general case, I as an identity owner might also store a self-attested claim about a given attribute for myself, and third parties could "sign" such claim as a form of attestation over it... Does that make any sense? Or should attestations correspond to new claims and the signature scheme for claims is designed with a totally different use case in mind?