@Taimoor10 it's all easy as long as I only want my Apps to interact with each other. But for interoperability, it's important to speak the same language.
According to that doc (thx for the link), it's at least partially based on OpenID claims spec. I hope that in the future there will be convergence with projects like Hyperledger Aries,Kantara Initiative, IHAN Blueprint etc.
As I currently see it, uPort does a great job at building tooling and approachable demos.
It's not so clear to me if uPort is well integrated into standardization efforts. The space still seems to be quite fragmented.
@Taimoor10 @d10r yes, that spec is indeed based on OpenID-connect.
At the moment there is no final standard regarding credential request/replies but uPort is working towards interoperability.
This will also mean that legacy protocols will be unmaintained when that happens.
I see many potential bugs being discussed here, many without resolution.
Generally it's better to post these on github.
The uPort team, unfortunately, doesn't have the resources to man this lobby too often, leaving people without answer.
Discussions are still very welcome, of course, but if you suspect there's a bug somewhere it fits better as a github issue.
Sadly we don't have the bandwidth to maintain the full uPort stack anymore.
All of our efforts are now focused on the Veramo framework ( https://github.com/uport-project/veramo ) and the libraries that uPort has donated to the Decentralized Identity Foundation.
If you are just starting out, it would be a good idea to check out https://veramo.io instead of relying on the uport-credentials / uPort mobile combo.
It is not yet a full replacement for the uPort stack (and I'm not sure if it will ever be a 1:1 mapping there) but the goal is to provide a standards-compliant, multi-platform framework for decentralized identity and verifiable credentials that can also interoperate with other projects and efforts in this space.