beckn / beckn/protocol-specifications-v2
Clarification on Domain-Agnostic Positioning in Introduction section
Open
documentation
- Dominant language
- No language data
- Stars
- 15
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
In the first paragraph of the Introduction, Beckn Protocol is described as enabling interactions between a "buyer-side application" and a "seller-side platform" to perform "commerce transactions."
Since Beckn is positioned as a domain-agnostic protocol, the use of commerce-specific terminology in the core definition is jelling well.
Would it be worth considering more domain-neutral terminology (e.g., "participating platforms" or "network participants") to better reflect the protocol’s broader applicability?
Happy to hear thoughts from the maintainers.
Contributor guide
Assessment
This issue has not been assessed yet.