Skip to content

Commit

Permalink
Refer IGM branch from ONDC-NTS-Spec instead of Beckn Mobility Spec (#59)
Browse files Browse the repository at this point in the history
Signed-off-by: Amar Tumballi <amar@dhiway.com>
  • Loading branch information
amarts authored Mar 12, 2024
1 parent 0f73689 commit ef07a52
Show file tree
Hide file tree
Showing 317 changed files with 1,773 additions and 50,682 deletions.
3 changes: 1 addition & 2 deletions docs/.gitignore
Original file line number Diff line number Diff line change
@@ -1,3 +1,2 @@
.DS_Store
node_modules
package-lock.json
package-lock.json
8 changes: 0 additions & 8 deletions docs/.gitmodules

This file was deleted.

9 changes: 0 additions & 9 deletions docs/Committee.md

This file was deleted.

Binary file removed docs/Error-codes.xlsx
Binary file not shown.
70 changes: 1 addition & 69 deletions docs/README.md
Original file line number Diff line number Diff line change
@@ -1,72 +1,4 @@
# ONDC Mobility Specification
# Confidex's Score Specifications

These specifications are to enable ONDC Network Participants to expose or consume mobility services on ONDC.

ONDC mobility specification is an adaptation of [beckn mobility specifications](https://github.com/beckn/mobility).

These specifications will be released in multiple phases enabling different use case and enhancements.

ONDC mobility specification swagger [link](https://ondc-official.github.io/mobility-specification/)

## Latest Version

[v2.0.0](https://github.com/ONDC-Official/mobility-specification/releases/tag/v1.0.0)

## Earlier Versions

| Version | Release Date | beckn Version | Comments |
| ------- | ------------ | ---------------------------------- | ------------------------------------------------------------------ |
| v1.0.0 | 14 Jun 2023 | core - 0.9.4<br />mobility - 0.8.2 | Initial mobility specification for on-demand ride hailing use case |
| v2.0.0 | 19 Feb 2024 | core - 1.2.0 | Base version of mobility for ride hailing is completed |

## Introduction

Open Network for Digital Commerce (ONDC) is a network based on beckn open protocol and will enable local commerce across segments, such as mobility, retail etc, to be discovered and engaged by any network-enabled application.

ONDC mobility & travel aims to build a nationwide multi-modal network that provides seamless experiences, supports growth & innovation by,

* bringing together a diverse set of mobility, travel & transportation players who can engage with the open network on their own terms
* fostering collaboration, sharing & new models
* facilitating responsive policy by bringing onboard decision making authorities

In the mobility space, the intent is to enable seamless and truly multimodal transit options by bringing in diverse inventory onboard at scale that will serve the country’s population.

This would be possible in the mobility domain by making sure all mobility apps in the network are built in such a way as to enable them to communicate with each other in the same language.

## Enabled/Supported use cases on network

* On-demand Ride hailing with fix pick-up and drop locations for transport modes : Car, Autorickshaw, Motorcycle
* Auto assignment of driver on on_confirm.
* Auto assignment of driver post on_confirm.
* Soft/Hard cancellation of ride.

## Evolution

The evolution of ONDC mobility specification driven by 2 factors:

1. The beckn mobility and/or core specification evolution.
2. ONDC Network Participants recommendation and requirement for enhancing and expanding the network use cases & experience.

To know more about how the specification evolves, visit the Network GOVERNANCE document.

To follow discussions related to the mobility specification please visit the [Discussions Forum](https://github.com/ONDC-Official/mobility-specification/discussions) on GitHub

Each major release of ONDC mobility specification will be approved by ONDC mobility working group members for which are listed [here](./Committee.md)

For minor releases for bug fix and cosmetic changes ONDC would make a minor release based on internal approval process and update the committee in the next scheduled discussion.

## Contribution

### Contribution to specifications

Anyone can contribute to the specification. Please refer beckn contribution guidelines.

### Contribution to network

Anyone can contribute to the network enhancements. Contributors must follow the contribution guidelines.

Each contribution will be peer-reviewed by the ONDC mobility committee members. If approved, this contribution will be merged with the applicable versions of the specification.

#### What is Contribution to network

Addition/Modification of examples, enum, policies which are very specific to the networks scope and purview.
79 changes: 0 additions & 79 deletions docs/Usage.md

This file was deleted.

Loading

0 comments on commit ef07a52

Please sign in to comment.