Should `confidenceMethod` be renamed to `authentication`?

[msporny]

The examples in the specification currently seem to have the same properties as verification methods, as defined here: https://w3c.github.io/cid/#verification-methods

Do we want to rename confidenceMethod be to authentication, as that is more or less what the property does... or do we want to allow non-verification methods to be associated with the confidenceMethod property such that they can be transformed into verification methods, but do not start out as verification methods.

Even if we don't rename it, we should describe the relationship to authentication since they seem very close/related.

[denkeni]

+1 to authentication or authenticationMethods. It’ll be more clear that existing authentication framework could fit it.

[TallTed]

Authentication is too tied to user log in and similar.

As I remember it, confidenceMethod was supposed to be along the lines of "how was this/these property(ies) value(s) confirmed?", e.g., "how did I confirm the accuracy of the data in this VC I'm issuing?"

Yes, this might conform to a common definition of "authentication", but that literal is already overloaded in 17 directions. Let's not add an 18th.