I have a related question on this subject which is similar to the above but a slightly different. In the example above i understand it to be looking for additional services over the top of a service existing in the inventory.
In our Case we have the following scenarios: -
Fibre Access Services
Data (broadband etc)
There can be any combination of these but this is about providing the availability for a particular address and not based on anything currently in the inventory. So i was trying to understand if the question to service qualification is 'tell me what i can have at this address'. Here the client does not have a specific ask so will not want to pre-populate multiple line items in the checkservicequalification request so how that would be most appropriately modelled in the checkservicequalification response? we could essentially have...
Request - here's my address
We actually have a lot more combinations than this but it just gives a flavour of how this becomes quite expansive and I cant really see how this link of one specification to another is meant to fit in so the caller knows that if they order a service with a broadband specification they would need to also order a service with a fibre access service (for example)
I did consider that the response could have 'lots' of serviceQualificationItem added to the response to model all of the 'top level' CFS options but then looking inside this I considered that the: -
My concern here was also that within the supportingService containers across all of the top level qualification items for example the Fibre Access Basic would be repeated many times even though it would essentially be the same information.
Hope someone might have had a similar challenge or has some thoughts on how this is best modelled