Updating the intro to the QoS Profile.

[RandyLevensalor]

What type of PR is this?

Add one of the following kinds:

• documentation

What this PR does / why we need it:

Expands on the intro to the QoS Profile to include it's intended use.

Which issue(s) this PR fixes:

Fixes #393

Special notes for reviewers:

@tanjadegroot this should address your feedback in #383 (comment). Please review.

Changelog input

 release-note
Updated top level description of QoS Profile.

Additional documentation

This section can be blank.

docs

[benhepworth]

looks good to me

[eric-murray]

LGTM - I'll even let you get away with your spelling of behaviour!

[hdamker]

@tanjadegroot proposed in #383 (comment) for line 17:

change: communication service provider --> API provider
possibly also change: API invoker --> API consumer

She also proposed in #383 (comment) to change multiple occurrences of "network operator" with "API provider" (background is that the API consumer is requesting the service from an API provider platform which is not necessarily directly the network operator (but could be)).

[RandyLevensalor]

@tanjadegroot proposed in #383 (comment) for line 17:

change: communication service provider --> API provider
possibly also change: API invoker --> API consumer

She also proposed in #383 (comment) to change multiple occurrences of "network operator" with "API provider" (background is that the API consumer is requesting the service from an API provider platform which is not necessarily directly the network operator (but could be)).

I don't think that API provider makes sense in this context. The attributes in the QoS Profiles would be defined by the network operator or at the very least approved and supported by the network operator, regardless if someone is hosting the API on their behalf.

[jlurien]

LGTM

[hdamker]

I don't think that API provider makes sense in this context. The attributes in the QoS Profiles would be defined by the network operator or at the very least approved and supported by the network operator, regardless if someone is hosting the API on their behalf.

@RandyLevensalor I have a different view here, an API provider acting as aggregator might decide to offer only a subset or even an own defined set of profiles, which the provider is then mapping to QoS Profiles of underlying communication service provider.
But I propose that this is a different issue and PR, which I will create as sub issue of #387.