change `Verifiable Recognition Credential` (`VRC`) (and variants) to `Verifiable Credential for Recognition` (`VCR`? `VC4R`?) (and variants)

[TallTed]

It seems important to make these changes (which I think flow clearly and directly from the change in the document title) sooner than later, especially given the active propagation of VerifiableRecognitionCredential in various locations.

[kezike]

I suspect that this naming pattern was adopted because VC types are typically defined with Credential at the end. Examples include PermanentResidentCardCredential, OpenBadgeCredential, and AchievementCredential. This is not a hard and fast rule as far as I know, but I personally like the consistency. As for the specification name, we have a lot more freedom to choose whatever we want from a historical naming standpoint, but I favor what we currently have (as you note): Verifiable Credential for Recognition.

[TallTed]

I note that the VC types you listed do not include Verifiable -- which would make them VerifiablePermanentResidentCardCredential, VerifiableOpenBadgeCredential, and VerifiableAchievementCredential. Dropping Verifiable from VerifiableRecognitionCredential would make it the much more manageable RecognitionCredential ... but Verifiable seems key.

Lots more bike shedding awaits us!

[ottonomy]

OpenBadgeCredential, AchievementCredential, ClrCredential, EndorsementCredential (for example) are stable types defined by 1EdTech.org specs and are not open to revision to add Verifiable... prefix. I think this is just a naming convention not any sort of hard requirement. Values of types just need to be Terms or Absolute URL Strings.