Open APIs

Hi Matthieu, Thank you for the clarification - that makes perfect sense. Your explanation of how POCV orchestrates the full validation flow (technical, commercial, planning, upgrade checks, etc.) is very helpful. The analogy of POCV ...

In our case, it's POCV that will do these validation. it will have a workflow to go through validations and one of them is to orchestrate TMF645 to check if it's technically feasible to activate 600 mbps at this specific fiber termination point (place ...

Hi Matthieu, Thank you for the clarification - and I fully agree that TMF645 is intentionally positioned as a capability/feasibility check, without carrying order semantics. The nuance I was trying to explore is slightly different: ...

Hi, I didn't think TMF645 keep intent implicit. I thought it just doesn't care. Its job (assuming POST Check) is just to tell you if SSpec A is technically activable (for instance at the customer's location). Would you mind to share examples ...

Hi Jiri, Regarding TMF645: The flat structure in TMF645 is by design and there is no other way. Nesting implies a containment hierarchy but in the SID: Only atomic Product Offerings have a ProductSpecification . atomic Product Offerings ...