Beckn Protocol Version 1.2.0 : Minor Version Release

[emmayank]

Summary

Beckn Open Collective presents Beckn Protocol Specification Version 1.2. This minor release contains a significantly abstracted and unified protocol specfication and recommendations from the Core Working Group. The following release note summarize the changes that have been made to the protocol since its last release version 1.1. More details will be added in subsequent minor releases.

Changelog

Full Changelog can be found here: core-v1.1.0...core-1.2-release

Reviewers

@ravi-prakash-v
@pramodkvarma
@sjthnrk
@venkatramanm

What's Changed

• Created RFC-Template.md in 372a9f2
• Updated BECKN-006-Signing-Beckn-APIs-In-HTTP-Draft-01.md in 39d21fb
• Created BECKN-010-Keyword-Definitions-for-Technical-Specifications.md in a2bf58f
• document object added in order, item and fulfillment in e6045d7
• ItemQuantity Added in Addon in cfb1660
• Support and on_support body updated in 623c9e5
• Inside Price Object, all values replace by string in 3320420
• Xinput schema updated in da5ce1c
• Payment object schema updated in 538c5a6
• ttl type made inconsistent throughout in 8ecce13
• Added mimetype in form in bea3158
• Updated Customer Object with Organization and ID property in 8edb5f4

Pull Request

1. Updating Customer and Support schema to add new properties #359
2. Search provider feature #381
3. Keyword defs #385
4. Issue Fixes #386
5. issue #392 resolved #393

Contributors

• @shenoyninad
• @bharath-ganapathy
• @ravi-prakash-v
• @venkatramanm
• @emmayank

---

This discussion was created from the release Beckn Protocol Version 1.2.0 : Minor Version Release.

[emmayank]

Dear @ravi-prakash-v , @pramodkvarma , @sjthnrk and @venkatramanm

We are thrilled to announce our plans for the upcoming release of the Beckn protocol specification, Version 1.2. The proposed changes have been outlined above, encompassing some minor but impactful adjustments. In order to facilitate a comprehensive review and ensure a smooth progression, we kindly request the collaboration of the Core Working Group.

Your expertise and insights are invaluable to the success of this endeavor. Therefore, we propose scheduling a review meeting at your earliest convenience to discuss the nuances of the 1.2 version and address any queries or suggestions you may have.

Looking forward to your participation and collective efforts in advancing the Beckn protocol.

Best regards,
@emmayank