The core-v2.0.0-rc branch schemas are referencing schemas in main branch

[ameetdesh]

• https://github.com/beckn/protocol-specifications-v2/blob/core-v2.0.0-rc/schema/EvChargingService/v1/attributes.yaml#L84
  - $ref: "https://raw.githubusercontent.com/beckn/protocol-specifications-new/refs/heads/main/schema/core/v2/attributes.yaml#/components/schemas/Location"
• 12 instances of referencing to main instead of tag. e.g. https://github.com/beckn/protocol-specifications-v2/blob/core-v2.0.0-rc/schema/core/v2/attributes.yaml#L26
  enum: ["https://raw.githubusercontent.com/beckn/protocol-specifications-new/refs/heads/main/schema/core/v2/context.jsonld"]

This will break if the main branch evolves, hence is fragile. Main is about to go a big refactor, and we won't want NBSL production setup (schema-validator et al) to break. Suggested fix:

• point all https://raw.githubusercontent.com/beckn/protocol-specifications-new/refs/heads/main in core and EvChargingService schemas to a tag https://github.com/beckn/protocol-specifications-v2/releases/tag/core-v2.0.0-rc1 (except maybe the changes that broke on_track behavior for NBSL. ++ @anandp504 I am green on this. You would have better perspective.)
• Ideally all references in a branch should be to an older tag or to the branch itself.

[pramodkvarma]

In any of the schemas we should NOT be referring to Github branch/release URLs. We should offer a schema hosting URL where all schemas can be housed (like /schema.beckn.io/v2/). A simple web URL under schema.beckn.io.

This is urgent and necessary because it gets messy.

@ravi-prakash-v @ameetdesh @anandp504

@ravi-prakash-v please implement this immediately. All published schemas should be housed under beckn.io URL.

[ravi-prakash-v]

Noted. This is in the pipeline. This is scheduled to be picked up after the upcoming release.

[vbabu75]

While published schemas can go to the website mentioned above by @pramodkvarma , I feel we can follow some rules to aid the developer workflow (github repo based).

1. We use relative refs in the file. So they will be branch-agnostic.
2. If we reference file in a different repo, we use tag/commit based path, so the version we are referring to does not magically change (when we use branch, we run the risk that it could)
3. For artefacts that need to be distributed, we can create a self-contained yaml without refs and host it (Both within github and outside).

[ravi-prakash-v]

This has been fixed.