Replies: 3 comments
-
@Tushar-Naik @amitsaluja @abaweja @batramanuj @EkanshKr @mahoriR @mherle @NajeebMohammed @nitinmish @nikitagupta5566 @get2abhi https://github.com/orgs/ONDC-Official/teams/participants |
Beta Was this translation helpful? Give feedback.
-
Notational form is only a small cog in the whole search scheme. It is generally used by mostly front end technologies to attribute intent to a keyword that has been/is being typed. The command issued through must be parsed with search libraries, irrespective whether using BNF/CNF/CFGs etc and search query is issued to a search service. Search service internally convert the query to multiple lookups to cache and extract matching entities and return back for rendering. However, the search indexes are pretty complex set of algorithms and not all platforms will have the digital maturity to handle it at that level. My suggestion, instead of implementing search grammar on network APIs, we should simplify it through a simple tag that carries the typed keyword as root in simpler format (may be simpler implementation of BNF being more prevalent) besides some derived keywords may also mean something else. To illustrate for better understanding, lets say a buyer typed keyword1+keyword2 on free text field, then a BNF request shall look like: Name ::= “” In this case,
I hope my understanding of the problem statement is correct and coherent. |
Beta Was this translation helpful? Give feedback.
-
ONDC base protocol has the capability for free text search. To enable free text search, a generic cross-domain search grammar (BNF/CNF/?) needs to be defined and enabled. Requesting inputs from participants for help in defining this grammar.
Beta Was this translation helpful? Give feedback.
All reactions