Hi Dear tmforumWe try to model T-Shirt Size with TMF633What is T-Shirt Size:For example, we have a Service Specification which is "compute and memory".This Service has the T-Shirt Sizes:- S: 1 cpu / 128MB- M 2 cpu / 256MB- L 4 cpu / 512MB- XL 8 cpu / 1024MBWe struggle to apply this to the TMF633 open API spec.The following opportunities:- use featureSpecification as T-Shirt Size and then express cpu/memory as featureSpecCharacteristic- use specCharacteristic for expressing T-Shirt Size, then use also specCharacteristic to express cpu / memory. Express the relation between T-Shirt Size and cpu / memory with charSpecRelationship.How would you model T-Shirt Size with TMF633?
> One approach might be to have the t-shirt size at the Product level, i.e. commercial.This doesn't work, because a lot of these services are just used internally and are not directly used by a commercial offering.At the end they can be part of a commercial offering, but they are 2 to n services down the graph.If these are all Services, then "a" would be the one connected to the Commercial Offering. But I we also need to model T-Shirt Size on "b","c","d","e".
Thank you for your answer @Koen Peeters this points into the right direction.
To fulfill our requirements we would extend, the ServiceCandidate with the Characteristics.For the usability of the API I would also suggest to add the ServiceCandidates as an array to the ServiceSpecification. Since the browsing flow is mostly: I search for a Service Specification and then want to know the Candidates (T-Shirt size).@Jonathan Goldberg what is your opinion on this?
Hi.I agree with your observation Jonathan. I do not see the relevance of ServiceCandidate either. It seems to me that purpose is better fulfilled using appropriate status attributes. Is there perhaps a discussion dedicated solely to this topic ?As for the original topic and the suggestion using serviceCandidate, it works out for this particular example. But imagine a product with a complete scalable parameter from 1-1000. We do not want to create 1000 Candidates. So the answer would obviously be product and service configuration, with the needed translation in between.(?)