Confusion about ClassOfService and *LoSCapabilities

Hi Leon.
Following is additional information and clarifications that I hope will reduce your concerns. (see text taked with [GME])

1. From the schema definition, it's very clear to me that one ClassOfService contains multiple (five exactly) LinesOfService with different capabilities.
[GME] Clarification. A ClassOfService may contain up to five different categories of service level requirements. Each category of service level requirement is represented by a zero or more corresponding ***LineOfService instances. Most likely, only DataProtectionLinesOfService will support more than instance, however the model does not enforce that.

2. From the schema definition, there is another schema called ***LoSCapabilties, and IMO it represents separate collections of LinesOfService with different types.
[GME] Each xxxLoSCapabilities instance found in StorageServices represents the ability of the service to create and support new ***LineOfService instances that each represent a specific service level requirement. All currently defined and supported ***LineOfService instances should be copied into the ***xxxLoSCapabilities /SupportedLinesOfService collection.


3. In the UserGuide docs, A use case is that StorageAdmin has access to create line of service, and it turns out to send a PATCH request to update the correspond ***LoSCapabilities.
[GME] The implementation of that ***LoSCapabilities. Should validate that the service is able to support each new or modified ***LineOfService instance added to the SupportedLinesOfService collection.


4. Another use case is that when StorageAdmin creates class of service, some new ***LinesOfServices are also inputted as the properties of new-created ClassOfService, but I didn't see any updates on ***LoSCappabilities.
[GME] The implementation is responsible for validation and making the corresponding updates to the corresponding ***xxxLoSCapabilities /SupportedLinesOfService collections.