Open APIs

Hi all,

I'm starting to work at TMF620 v5.0.0 and I'm now able to run the CTK. I notice some errors like non-mandatory fields being validated.

For example, I have an error in ProductSpecification if the response does not have @baseType or @schemaLocation or isBundle or productNumber (I stopped here but I believe that will be occur for every non-mandatory fields that I do not use)

Can you please clarify the behavior and confirm if this is a issue in CTK or not?

Thank you

Inside Changeme.json you can change any of the values including removing non-mandatory parameters from the payload. 

Hi all,

I'm starting to work at TMF620 v5.0.0 and I'm now able to run the CTK. I notice some errors like non-mandatory fields being validated.

For example, I have an error in ProductSpecification if the response does not have @baseType or @schemaLocation or isBundle or productNumber (I stopped here but I believe that will be occur for every non-mandatory fields that I do not use)

Can you please clarify the behavior and confirm if this is a issue in CTK or not?

Thank you

This looks to me like a CTK implementation error - the CTK is supposed to implement only mandatory fields. I'm passing this on to the CTK focal in TMF.

Inside Changeme.json you can change any of the values including removing non-mandatory parameters from the payload. 

Hi all,

I'm starting to work at TMF620 v5.0.0 and I'm now able to run the CTK. I notice some errors like non-mandatory fields being validated.

For example, I have an error in ProductSpecification if the response does not have @baseType or @schemaLocation or isBundle or productNumber (I stopped here but I believe that will be occur for every non-mandatory fields that I do not use)

Can you please clarify the behavior and confirm if this is a issue in CTK or not?

Thank you

Hi Jonathan, like Denis said this is not an error on the CTK.

All CTKs have a CHANGEME.json file, with the attributes that can be changed, this file comes with the full example payload but one may change this payload so it matched their implementation. 

Any attribute that is provided on the payload will be validated against the OAS. You will pass the CTK if you send only minimum mandatory attributes, but you will be expected to conform to the OAS on any attribute provided.

Best,

This looks to me like a CTK implementation error - the CTK is supposed to implement only mandatory fields. I'm passing this on to the CTK focal in TMF.

Inside Changeme.json you can change any of the values including removing non-mandatory parameters from the payload. 

Hi all,

I'm starting to work at TMF620 v5.0.0 and I'm now able to run the CTK. I notice some errors like non-mandatory fields being validated.

For example, I have an error in ProductSpecification if the response does not have @baseType or @schemaLocation or isBundle or productNumber (I stopped here but I believe that will be occur for every non-mandatory fields that I do not use)

Can you please clarify the behavior and confirm if this is a issue in CTK or not?

Thank you