Open davidjwbbc opened 7 months ago
(These proposed changes affect TS 26.512 Rel-16 and Rel-17 only; the equivalent changes to the forthcoming TS 26.510 Rel-18 will be handled directly by the editor since this new specification is not yet under formal change control.)
Pushed into the next meeting cycle.
(These proposed changes affect TS 26.512 Rel-16 and Rel-17 only; the equivalent changes to the forthcoming TS 26.510 Rel-18 will be handled directly by the editor since this new specification is not yet under formal change control.)
I have now checked TS 26.510 Rel-18 and all fourteen of the properties list in the table are correctly marked as readOnly
with the exception of DynamicPolicy/enforcementMethod and DynamicPolicy/enforcementMethod which have been merged into the simpler DynamicPolicy/qosEnforcement flag in Rel-18.
Description
Issue #88 dealt with the discrepancy between Table 7.9.3.1-1 and the OpenAPI YAML in Annex C.3.8 with respect to some fields being marked as read-only, or described as being assigned by the 5GMS AF, in the Table but not marked as
readOnly: true
in the YAML. This becomes a problem with automatically generated code when the property is also a mandatory field, as the generated code will insist on the property being present in a request when it should not be present.There are several other instances of properties being marked read-only in the Tables but not marked as such in the OpenAPI YAML definitions in the Annexes.
/components/schemas/
Suggested solution
Add the
readOnly: true
flag to all YAML properties where the same property is marked as read-only in the Data model Tables or noted that it is assigned by the 5GMS AF.For types specified directly in the YAML, the addition of the
readOnly: true
will be sufficient, for example:...would become...
For properties which reference a type defined elsewhere, where the the addition of the
readOnly: true
requires that the reference be placed in anallOf
oranyOf
section, for example:...would become...
Additional context
See Issue #88 for the same change applied to the PolicyTemplates data model for TS 26.512 v17.6.0.