I get the motivation for this kind of identifier. I have a project in mind that could make use of the DID format. So I was optimistic to see that thought has

I get the motivation for this kind of identifier. I have a project in mind that could make use of the DID format. So I was optimistic to see that thought has been put into it. But when I read "if value is an object... if value is a string..." (from the specification of publicKey property), I worry. Did the authors choose JSON to take advantage of loose typing as a "feature"? Is it OK for a specification to require this kind of introspection and conditional logic?