Allow generic override / expand of ORD information

[Fannon]

Right now, the documentation in https://github.com/cap-js/ord/blob/main/ord.md indicates two ways to add ORD information:

• Add global ord config, that is then applied to several places
• Override ORD information via Annotations on CDS Models like a Service.

This still misses some flexibility:

• It's not possible to add new ORD resources or resource types that are not supported / provided by the CAP Framework right now (e.g. Data Products or Entity Types)
• It's not possible to override something in case this is necessary

Suggestion

Add a completely generic way to provide partial ORD documents, e.g. like:

// cdsrc.json or package.json cds context
  "ord": {
    "namespace": "sap.sample",
    "description": "this is my custom description",
    "policyLevel": "sap:core:v1",
    "customOrd": "./ord/custom.ord.json" // Link to static ORD JSON file to merge in
  }

Expected behavior:

• The interface of the custom object is the same as the ORD Document interface.
• The collections (like "dataProducts" are iterated and for those resource types that CAP supports we check if they are already defined through CAP. If yes, the custom definition wins (override)"
• All content in the custom object are merged to the final ORD Document that the CAP plugin produces.

[zongqichen]

Hi @Fannon, it's a good proposal. I would suggest that renames customOrd -> customOrdContentFile, with more context.

[Fannon]

Hi @Fannon, it's a good proposal. I would suggest that renames customOrd -> customOrdContentFile, with more context.

Sounds good!