For every single of operation on the entities use the following templates and provide sample REST notification POST calls.
It is assumed that the Pub/Sub uses the Register and UnRegister mechanisms described in the REST Guidelines reproduced below.

Anchor
_Toc404174516 _Toc404174516

Anchor
_Toc405208294 _Toc405208294

REGISTER LISTENER POST /hub

Description :
Sets the communication endpoint address the service instance must use to deliver information about its health state, execution state, failures and metrics. Subsequent POST calls will be rejected by the service if it does not support multiple listeners. In this case DELETE /api/hub/{id} must be called before an endpoint can be created again.
Behavior :
Returns HTTP/1.1 status code 204 if the request was successful.
Returns HTTP/1.1 status code 409 if request is not successful.

Anchor
_Toc404174517 _Toc404174517

Anchor
_Toc405208295 _Toc405208295

UNREGISTER LISTENER DELETE hub/{id}

Description :
Clears the communication endpoint address that was set by creating the Hub.
Behavior :
Returns HTTP/1.1 status code 204 if the request was successful.
Returns HTTP/1.1 status code 404 if the resource is not found.

Anchor
_Toc404174518 _Toc404174518

Anchor
_Toc405208296 _Toc405208296

publish {EventTYPE} POST /listener

Description :
Provide the Event description
Behavior :
Returns HTTP/1.1 status code 201 if the service is able to set the configuration.

...

Example see TMF REST Design Guidelines.

Anchor
_Toc203490686 _Toc203490686

Anchor
_Toc225613461 _Toc225613461

Anchor
_Toc225603250 _Toc225603250

Anchor
_Toc235288526 _Toc235288526

Anchor
_Toc405208297 _Toc405208297

Release History

Anchor
_Toc405208298 _Toc405208298

Contributors to Document

...