TMF620 Product Catalog Management API User Guide has a "Characteristic-Based or Schema-Based" section. Currently we use characteristic based entities but it has some restriction specially when attributes and their value has relationship together. So we wanted to investigate on schema based characteristic. May i request you kindly share more information in this matter? As it's described very shortly on the "TMF620 Product Catalog Management API User Guide" document.Below you can find some examples which i think it's more easier to configure using JSON schema:When a product has two different storage class which each one has different storage size:Class A: [10 TB, 20 TB]Class B: [5TB, 10TB, 15TB]In order to not create two different productSpecification for above configuration, of course we can use charValue relationship in Characteristic-Based. But we found schema based chars easier. So needed more info please.