Merge pull request #9 from beckn/release-v0.1.0

Release v0.1.0

README.md

@@ -1,12 +1,12 @@
-# Online Dispute Resolution Protocol
+# Dispute Resolution Protocol
 
 ## Introduction
 
 **Online Dispute Resolution (ODR)** is a mechanism to resolve disputes through the use of electronic communication technology. It often uses alternative dispute resolution (ADR) tools such as mediation, arbitration and negotiation. This mechanism not only provides citizens access to efficient and effective dispute resolution mechanisms, it also supports the formal court system by reducing the number of disputes that go to court, in turn helping address pendency in courts.
 
 ODR is a wide field. The application of ODR is not limited to disputes arising out of business to consumer (B2C) online transactions, although it seems to be particularly apt for these disputes, since it is logical to use the same medium (the internet) for the resolution of e-commerce disputes when parties are frequently located far from one another. It is believed that efficient mechanisms to resolve online disputes will impact in the development of e-commerce. However, it may be applied to a range of disputes; from interpersonal disputes including consumer to consumer disputes (C2C) or marital separation; to court disputes and even interstate conflicts.  
 
-The **Online Dispute Resolution Protocol** is an adaptation of [beckn protocol](https://github.com/beckn/protocol-specifications) that aims to unify various online dispute resolution services by implementing an interoperable API specification.
+The **Dispute Resolution Protocol Specification** (a.k.a DRoP) is an adaptation of [beckn protocol](https://github.com/beckn/protocol-specifications) that aims to unify various online dispute resolution services through an interoperable API specification.
 
 ## Release History
 

docs/1_Introduction.md

@@ -51,9 +51,9 @@ The online dispute resolution (ODR) ecosystem faces several challenges as it see
 - **Integration Issues:** Integrating ODR with existing legal and dispute resolution systems can be challenging due to differences in processes and requirements.
 - **Resistance to Change:** Traditional institutions may resist the adoption of ODR due to a lack of understanding or fear of becoming obsolete.
 
-## The ODR Protocol
+## The DRoP Specification
 
-To address some of the above challenges, the ODR community has come together to design a unified protocol for unifiying the dispute resolution ecosystem and unlock the full potential of ODR. The ODR protocol is an adaptation of Beckn Protocol that establishes a a framework to arrive at a community-owned data standard for ODR that aims to unify various online dispute resolution services by implementing an interoperable API specification. Implementing the ODR protocol will enable ecosystems/institutions seeking dispute resolution to easily discover and engage with multiple ODR service providers.
+To address some of the above challenges, the ODR community has come together to design a unified protocol for unifiying the dispute resolution ecosystem and unlock the full potential of ODR. DRoP is an adaptation of [Beckn Protocol](https://github.com/beckn/protocol-specifications) that establishes a a framework to arrive at a community-owned data standard for ODR that aims to unify various online dispute resolution services by implementing an interoperable API specification. Implementing the ODR protocol will enable ecosystems/institutions seeking dispute resolution to easily discover and engage with multiple ODR service providers.
 
 By virtue of a minimum viable standardized process/steps of communication, it eases the burden of multiple one-to-one integrations of ODR with ecosystems/institutions and also enables continuous sharing of status and updates to the respective ecosystem/institution as mutually decided.