Use of an Array for message.order.provider.locations in Beckn Core Protocol Spec Version 0.9.4

[rajaneeshk90]

Introduction:

This discussion aims to explore the rationale behind the current design choice of utilizing an array for the message.order.provider.locations field in the beckn core protocol spec version 0.9.4. The goal is to gain a deeper understanding of the decision-making process and its implications.

Agenda:

1. Clarification of the current structure (message.order.provider.locations as an array).
2. Consideration of use cases and scenarios.
3. Discussion on the advantages of the array structure.
4. Open floor for community input and feedback.

Guidelines:

Maintain a respectful and open-minded discussion.
Focus on understanding the reasoning behind the array structure.

Context:

It is defined here: https://github.com/beckn/protocol-specifications/blob/core-0.9.4/core/v0/api/core.yaml#L1980

Discussion Points:

If we are allowing only one element in the array, we are better of with declaring it as a location object. By keeping it an array we are giving the developers and impression that they can send multiple locations in this array.

Will be happy to hear others views on it.

Thanks,
Rajaneesh