From 66cf324545a90ed8275cdda04eb7ade4587ee306 Mon Sep 17 00:00:00 2001 From: PatrikBuhr Date: Mon, 8 Mar 2021 12:33:17 +0100 Subject: Documentation updates Change-Id: Idbfdc085cb25835ff0c77d6d1963fece4fb0fe24 Issue-ID: CCSDK-2966 Signed-off-by: PatrikBuhr --- docs/offeredapis/offeredapis.rst | 16 ++-------------- 1 file changed, 2 insertions(+), 14 deletions(-) (limited to 'docs/offeredapis') diff --git a/docs/offeredapis/offeredapis.rst b/docs/offeredapis/offeredapis.rst index b6b2cd66..a43c0460 100644 --- a/docs/offeredapis/offeredapis.rst +++ b/docs/offeredapis/offeredapis.rst @@ -15,7 +15,7 @@ Introduction The north bound REST API of the Policy Management Service provides convenient methods to handle policies. -Global ORAN architecture +Overview ************************ Following illustration provides a global view about **ORAN** architecture, @@ -39,21 +39,9 @@ The version number (without the revision number) is held in the URI. The major version number is incremented for an incompatible change. The minor version number is incremented for a compatible change. For minor modifications of the API, version numbering must not be updated, -provided the following backward compatibility rules are respected: - -- New elements in a data type must be optional (``minOccurs=0``) -- Changes in the cardinality of an attribute in a data type must be from - mandatory to optional or from lower to greater -- New attributes defined in an element must be optional (absence of - ``use="required"``). -- If new enumerated values are included, the former ones and its meaning must - be kept. -- If new operations are added, the existing operations must be kept -- New parameters added to existing operations must be optional and existing - parameters must be kept For major modifications of the API, not backward compatible and forcing client -implementations to be changed, the version number must be updated. +implementations to be changed, the major version number must be updated. API Table -- cgit 1.2.3-korg