Is this a regression?
Yes
Description
There are several Swift SDK Protocol definitions that point to non-existent URIs.
Many are using the retired atalaprism.io or didcomm.atalaprism.io domains.
The invalid URIs are:
case didcommPresentation = "https://didcomm.atalaprism.io/present-proof/3.0/presentation"
case didcommRequestPresentation = "https://didcomm.atalaprism.io/present-proof/3.0/request-presentation"
case didcommProposePresentation = "https://didcomm.atalaprism.io/present-proof/3.0/propose-presentation"
case didcommconnectionRequest = "https://atalaprism.io/mercury/connections/1.0/request"
case didcommRevocationNotification = "https://atalaprism.io/revocation_notification/1.0/revoke"
case prismOnboarding = "https://atalaprism.io/did-request"
The alataprism.io baseURL redirects to the main Identus project Github.
Please provide the exception or error you saw
`atalaprism.io` URIs redirect to `https://github.com/hyperledger-identus/identus, but each of these should link to a spec somewhere no?
Please provide the environment you discovered this bug in
Swift SDK, v.7.0.0
EdgeAgentSDK > EdgeAgentSDK > EdgeAgent > Sources > Protocols > ProtocolTypes.swift
Anything else?
No response
Is this a regression?
Yes
Description
There are several Swift SDK Protocol definitions that point to non-existent URIs.
Many are using the retired
atalaprism.ioordidcomm.atalaprism.iodomains.The invalid URIs are:
case didcommPresentation = "https://didcomm.atalaprism.io/present-proof/3.0/presentation"case didcommRequestPresentation = "https://didcomm.atalaprism.io/present-proof/3.0/request-presentation"case didcommProposePresentation = "https://didcomm.atalaprism.io/present-proof/3.0/propose-presentation"case didcommconnectionRequest = "https://atalaprism.io/mercury/connections/1.0/request"case didcommRevocationNotification = "https://atalaprism.io/revocation_notification/1.0/revoke"case prismOnboarding = "https://atalaprism.io/did-request"The
alataprism.iobaseURL redirects to the main Identus project Github.Please provide the exception or error you saw
Please provide the environment you discovered this bug in
Anything else?
No response