add: rough way of extending contexts 3 methods

cavacado commented 1 year ago

@simboonlong here u go

netlify[bot] commented 1 year ago

Deploy Preview for ndi-tradex-poc ready!

Name	Link
Latest commit	67f2ab1c4aa7ae70c1bdb1a30fb0fb4cf3069796
Latest deploy log	https://app.netlify.com/sites/ndi-tradex-poc/deploys/6412b8bd68f4250008a35dc5
Deploy Preview	https://deploy-preview-1--ndi-tradex-poc.netlify.app
Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

simboonlong commented 1 year ago

Summary of my understanding looking at this pr:

Method 1 looks the easiest. There's "no governance" over data. We can be very flexible about what we want to define in identityVC.

Method 2 strives to have some sort of governance, expecting at least embeddedVC. We are free to use any other property say for our case, we need type later to differentiate other "third-party identity providers". But since type is a protected term in https://www.w3.org/2018/credentials/v1, we will be using a substitute term called kind instead.

Method 3 obscurity magic allow us to use type.

TradeTrust / ndi-tradex-poc