Hi Paul
You have come to the right place, and your question is perfectly appropriate.
During our work on Open API v4, we have been firming up the definition of state/status attributes, giving them fixed values using the JSON Schema enum construct. The definition of IndividualStateType that appears in the swagger means that the status of the individual can take only one of the three fixed values of IndividualStateType.
The status itself cannot be array, since only one value makes sense at any given stage in the entity lifecycle.
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.
------------------------------
Original Message:
Sent: Jan 11, 2021 12:02
From: Paul Tap
Subject: TMF632: Error in TMF632-Party-v4.0.0.swagger.json for Individual - status
Hi all,
first post, so I hope this is appropriate with respect to location and topic.
I analyzed the TMF632-Party-v4.0.0.swagger.json file and I noticed that the "status" property for "Individual is:
"status": {
"$ref": "#/definitions/IndividualStateType",
"description": "Status of the individual"
},
,where I would expect:
"status": {
"type": "array",
"items": {
"$ref": "#/definitions/IndividualStateType",
}
},
I can see that in previous versions, "status" did not have a $ref, just 3 predefined values, so this may have been missed in the change, but probably I do miss something.
Regards,
Paul Tap
------------------------------
Paul Tap
WeCity
------------------------------