Hi Rati
From my perspective it is mandatory as stated in the CP.
I checked the swagger and the serviceSpecification.id is mandatory in the POST request. It is part of the "lifecyle representation" containing the mandatory and optional attributes than must be use for entity creation request (by POST).
Note that this specification.id is not stated as mandatory in the GET response representation and this one is used to craft the uml (which is illustrative).
Hope it helps,
Ludovic
------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
------------------------------
Original Message:
Sent: Feb 02, 2021 23:35
From: Rati Mehrotra
Subject: TMF 640 v4 service specification
Hi @Ludovic Robert,
We are adopting TMF 640 v4 . The service Specification cardinality differs in the UML diagram ( mentioned optional) and conformance profile( mentioned as mandatory.). Please confirm what is correct.
Thanks,
Rati
cc: @Uma Lakshman
------------------------------
Rati Mehrotra
Telstra Corporation
------------------------------