Open APIs

Hi All,

We are implementing Open APIs. In the first release, we will be sending only notification messages and CRUD operations are not implemented. But, "href" of resource is a mandatory field in resource model and hence to be sent in notification payload. As we have not implemented the GET operation on the resource, providing "href" would mislead the consumers. Hence, in this case, is it OK for notification messages for not to have the "href" field?

Thanks,

------------------------------
Kalpana HV
Colt Technology Services
------------------------------

Hi Kalpana
href is mandatory for entity messages since we assume that the messages relate to an accessible entity.

If your circumstances are such that there is no accessible entity, perhaps consider returning (for the time being) a fixed uri that always gives a 404 HTTP return status or some other appropriate 4xx status.

Hope it helps

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------

Thank you @Jonathan Goldberg. It helps.

Best regards,​

------------------------------
Kalpana HV
Colt Technology Services
------------------------------

Original Message:
Sent: Nov 01, 2020 01:10
From: Jonathan Goldberg
Subject: Whether href is always a must?

Hi Kalpana
href is mandatory for entity messages since we assume that the messages relate to an accessible entity.

If your circumstances are such that there is no accessible entity, perhaps consider returning (for the time being) a fixed uri that always gives a 404 HTTP return status or some other appropriate 4xx status.

Hope it helps

------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------