Open APIs

... it looks like TMF-716 uses ResourceItem.appliedCapacity and Capacity.relatedCapacity list to store actual reserved numbers. And we have to transform these to ResourceRef-s in other APIs. Hope I'm right about that.

Where do we find TMF-716 to review? https://www.tmforum.org/?s=tmf716&post_type=product doesn't find anything.

I'm curious how resource reservations are modeled to ensure that a reserved resource is not taken by another request to allocate. That is, there is some generic notion in the model of reservations that identifies some holder of the reservation (i.e., the customer, the pending service instance, the pending resource instance). The holder of the reservation would carry a bearer token of some kind that is issued by the reservation issuer, so that others making a claim on the reserved resource without having the proper bearer token can be denied access. Then, when that reservation is redeemed --- say by providing it on a Product Order --- the resource assignment can be realized for the service instance that is now created to fulfill the order. Where are such life cycle requirements analyzed?

... it looks like TMF-716 uses ResourceItem.appliedCapacity and Capacity.relatedCapacity list to store actual reserved numbers. And we have to transform these to ResourceRef-s in other APIs. Hope I'm right about that.