Requiring the "api" field in context object seems redundant and inhibits reuse.

[timburks]

Since the spec proposes using the x-sla field to link an SLA extension into an OpenAPI document, it seems unnecessary to also use the api field to link to the OpenAPI document from the Context Object in the SLA document. I think this would also prevent sharing of SLA documents among multiple APIs, because even if everything else was identical, different versions of the SLA document would need to exist for each referring API. Based on this, my general impression is that the api field should be eliminated, or at least made optional.

[pjmolina]

Good point @timburks !
Thanks for taking the time to reflect on it.

We can discuss it in the next SIG meting and take a decision on that. You are more than invited to join if you can.

Also, feel free to make a PR if you have the time.

Make api attribute optional.

• Why: redundant via x-sla linking mechanism.
• Pros: allows SLA reuse to different APIs. (linked by x-sla ref)
• Cons: lost bidirectional links.