verificationMethod property in Example 2 authentication verification relationship will cause interop issues

[kdenhartog]

Hey was just reviewing this for the purposes of the method registration and I noticed that you defined the verificationMethod reference inside the did document is different than what is most commonly done. You provided the following in Example 2:

{
        "type": "Secp256r1SignatureAuthentication2018",
        "verificationMethod": "did:bluetoqueagent:BF5pxRJP6THrUtlDdhh07hJEDKrJxkcR9m5u1xs33bhp#keys-1"
}

However verificationMethod property is not commonly structured in this way when you're intending to reference a different VM in the DID Document. The most common pattern in use is to include just the DID URL to reference to the VM in the verificationMethod property above in order to interoperably show the relationship between the authentication verification relationship and the VM.

Based on memory there's nothing illegal about the way you've structure this according to did-core but you're likely to hit interop issues when a did document relying party attempts to process this did document to get a public key out of it.