[3.1-RC1] Add authentication protocol modeling for SoftwareService

[henrylyons]

Affected Sections: model/Service/Classes/SoftwareService.md

Feedback

Issue #1365 separates certificate-status protocols such as OCSP and CRLs from authentication protocols. However, the Service profile still has no property for describing how clients authenticate to a software service.

Suggested Change

Add an optional authentication-protocol property to SoftwareService with a corresponding vocabulary. Consider common mechanisms such as mTLS, OAuth 2.0, OpenID Connect, SAML 2.0, Kerberos, and API keys.

Notes

Follow-up to #1365 and PR #1412.

[goneall]

@henrylyons - would it be OK to target this for the 3.2 release, or do you have a need for this in the near term?