You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: documentation/SupportingDocuments/ApiDesignConsiderations.md
+2
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,8 @@
3
3
## Introduction
4
4
The API design considerations are derived from the API usage scenarios (PR#12). The aim of the API is to hide telco specific complexity, while offering the needed capabilities. There may be different realization of the needed network capabilities, e.g. using shared network slices or even exclusive network slices.
5
5
6
+
This is an informal document, which should support the API design. The document may be updated during the API design process.
7
+
6
8
## General Considerations
7
9
The API should allow combination with other CAMARA APIs, such as QOD, Connectivity Insights / Monitoring, etc.
8
10
The API should follow the CAMARA commonalities guidelines and (potentially) align with other API designs. For example, QOD offers an endpoint for discovery of profiles and another endpoint for activation/deactivation of profiles.
0 commit comments