How can catalogs be filtered by network ?

[anandp504]

In the context of the Catalog publishing and Catalog discovery, the context.networkId might have to be modified to support an array of networks as a Provider will want to control the visibility of a Catalog across multiple networks or a Seeker might want to discover products or services across multiple networks.

Current: context.networkId is a String.
Proposal: context.networkId is an Array of Strings.

[anandp504]

This was discussed and we decided to not use the context.networkId for the Discovr service to filter out catalogs belonging to specific networks. Instead, it will be apt to to introduce the networkId as part of the /discover api Intent.filter to enforce discovery on specific networks.

[ravi-prakash-v]

@bachia

1. Is this change needed now? If so, who needs it ? @bachia please describe the specific on-ground requirement that invoked this proposal by @anandp504
2. What are the various scenarios where this filter may be used?
3. Why does this need to be a protocol change and not something that can be implemented on/in-fabric?

Assuming if this proposal meets the gating criteria for protocol change as explained here, then @anandp504,

1. Will this change affect how catalogs MAY / SHOULD be published by a Provider Node on the Fabric?
2. How does this change affect catalog syncing between DS and CS ?
3. How does this change affect discovery flow between a Consumer Node and DS?
4. Can you please describe the updated schema and flows and add it to the Discovery RFC being documented here -
   https://github.com/beckn/protocol-specifications-v2/blob/catalog-schema-changes/docs/Catalog_APIs_RFC.md

To know more about the changes management process on fabric, please read this doc. https://github.com/beckn/protocol-specifications-v2/blob/draft/GOVERNANCE.md

CC: @pramodkvarma

[pramodkvarma]

@ravi-prakash-v we should add network IDs (array) as an additional filter criteria. Please close.
@anandp504

[ravi-prakash-v]

Ok @pramodkvarma. @anandp504 please raise PR to main.

[manjudr]

@nirmay - Regarding this change request, I will make the spec changes and raise the PR to the draft branch.

[manjudr]

@nirmay I have updated the schema to support networkId as both a string and an array of strings. A bare string is still accepted for
backward compatibility so existing NPs are not impacted.

I have raised the PR to Draft Branch : beckn/protocol-specifications-v2#178