This catalyst team will develop the Swagger Spec for TMF921 and a reference implementation for the endpoint
The development work on the OAS2 spec will take place directly in the TM Forum github repo for this purpose. See https://github.com/tmforum-rand/Open_API_And_Data_Model/tree/v4.0-Sprint-2020-03/apis/TMF921_Intent. (Access is restricted to members of the Open API Colloboration team in TM Forum)
#Examples (STALE! TODO: will be replaced with content from catayst space https://projects.tmforum.org/wiki/display/CIANPI/Intent+Examples)
| UC | Business | Service | Resource |
|---|---|---|---|
| Dynamic Pricing of Connectivity Services | Spot Pricing | Service Intent | Slice Intent Note Network Slices are modelled by TMF as ResourceFunctions |
| Goal | Service Order (IW) | ||
| Constraint: | SLA Preservation | ||
| Sub UseCases | ZTP (Onboarding) | ||
Tools used:
- Round Trip Convertor: https://www.easyrdf.org/converter
- Turtle to JSON-LD https://frogcat.github.io/ttl2jsonld/demo/
- https://rdf-translator.appspot.com/ http://owlgred.lumii.lv/