update-design-doc-with-explicit-sub-scope-changes

[shilpa-padgaonkar]

What type of PR is this?

Add one of the following kinds:

• correction

What this PR does / why we need it:

Explicit subscriptions need to be transparent about the event types that they offer. Following changes are included:

• Suggests that explicit subscriptions should have a separate API file
• API name must include the keyword "subscriptions" at the end
• Suggest how scope should be represented when actions are create (subscription) and when they are delete and read (subscription)

Which issue(s) this PR fixes:

Fixes #163

Special notes for reviewers:

Changelog input

 release-note

Additional documentation

This section can be blank.

docs

[shilpa-padgaonkar]

Changed PR to draft based on subscription related discussion. Also need to await feedback & consensus on https://github.com/camaraproject/Commonalities/issues/184

[shilpa-padgaonkar]

@bigludo7 and @PedroDiez : Would be great if you could kindly review the scope related changes for explicit subscriptions documented in the design guidelines and recommend changes if needed.

[shilpa-padgaonkar]

@PedroDiez and @bigludo7 have already approved the PR, but I would need a codeowner approval to be able to merge this. @rartych is on vacation. Could either @patrice-conil or @RubenBG7 kindly approve the PR?

[bigludo7]

@shilpa-padgaonkar my colleague Patrice is also enjoying well-deserved vacation :) Hope @RubenBG7 will be able to help.

[RubenBG7]

Done @shilpa-padgaonkar