I understand that one of the objectives of did:indy is to deprecate ATTRIB and do everything in one transaction, but hear me out..
It may take a long time until currently deployed HL Indy networks and various tools and libraries will be upgraded to support the "diddocContent" field in NYM. Until this happens, we can also allow "diddocContent" as an ATTRIB. Its contents and rules for assembly would be the same as for "diddocContent" in NYM.
A resolver would first retrieve the NYM, and if that has a "diddocContent", then it is done. Otherwise, the resolver may also attempt to retrieve the "diddocContent" from an ATTRIB, just like it may attempt to still retrieve the "endpoint" from an ATTRIB (according to this section).
This way, even older HL Indy networks could already take full advantage of new did:indy features (full control over the DID document), and at the same time upgraded HL Indy networks could do everything using a single transaction as intended by the spec. Once older HL Indy networks get upgraded, existing "endpoint" and "diddocContent" in ATTRIBs should be upgraded to "diddocContent" in NYM.
I understand that one of the objectives of did:indy is to deprecate ATTRIB and do everything in one transaction, but hear me out..
It may take a long time until currently deployed HL Indy networks and various tools and libraries will be upgraded to support the "diddocContent" field in NYM. Until this happens, we can also allow "diddocContent" as an ATTRIB. Its contents and rules for assembly would be the same as for "diddocContent" in NYM.
A resolver would first retrieve the NYM, and if that has a "diddocContent", then it is done. Otherwise, the resolver may also attempt to retrieve the "diddocContent" from an ATTRIB, just like it may attempt to still retrieve the "endpoint" from an ATTRIB (according to this section).
This way, even older HL Indy networks could already take full advantage of new did:indy features (full control over the DID document), and at the same time upgraded HL Indy networks could do everything using a single transaction as intended by the spec. Once older HL Indy networks get upgraded, existing "endpoint" and "diddocContent" in ATTRIBs should be upgraded to "diddocContent" in NYM.