Orie Steele
Orie Steele
@NTonani I am very open to adding additional modules to this repo, as is needed to support the work item. since its already structured as a mono repo, this is...
@nissimsan do you agree to abide by OAS 3 and treat descriptions as markdown? or are you saying we should profile down from OAS 3 and forbid markdown in descriptions?
https://swagger.io/specification/ > Throughout the specification description fields are noted as supporting CommonMark markdown formatting. Where OpenAPI tooling renders rich text it MUST support, at a minimum, markdown syntax as described...
I am a +1 for using absolute URLs and markdown.
Would love to see a small PR which adds JSON examples as a starting point.
I am excited to see this added to the universal wallet interop spec, we've been working on VP Request Spec JSON based APIs for exchanging content. I see capabilities to...
Its especially advantageous to rely on a mediator if the data is too large to pass over a browser or QR Code.
Here is a snippet from our universal wallet plugin for vp exchange: ``` it("alice notifies bob of intent to present", async () => { // request m0 = aliceWallet.createNotificationQueryRequest( "IntentToSellProductCategory"...
we're still experimenting with the interfaces, but we'll be making sure to align them in the spec here, based on feedback we receive.
ping @sudeshrshetty @dmitrizagidulin