Skip to content

Commit 6eed805

Browse files
authored
Update ApiDesignConsiderations.md
As discussed during the meeting.
1 parent ac058e2 commit 6eed805

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

documentation/SupportingDocuments/ApiDesignConsiderations.md

+2
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,8 @@
33
## Introduction
44
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.
55

6+
This is an informal document, which should support the API design. The document may be updated during the API design process.
7+
68
## General Considerations
79
The API should allow combination with other CAMARA APIs, such as QOD, Connectivity Insights / Monitoring, etc.
810
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

Comments
 (0)