Update namespaces according to RFC8515

[scp/oam/modeling.git] / data-model / yang / working / o-ran-sc / o-ran-ru / o-ran-sc-ru-alarms-v1.yang

diff --git a/data-model/yang/working/o-ran-sc/o-ran-ru/o-ran-sc-ru-alarms-v1.yang b/data-model/yang/working/o-ran-sc/o-ran-ru/o-ran-sc-ru-alarms-v1.yang
index c52414d..dc18c96 100644 (file)
--- a/data-model/yang/working/o-ran-sc/o-ran-ru/o-ran-sc-ru-alarms-v1.yang
+++ b/data-model/yang/working/o-ran-sc/o-ran-ru/o-ran-sc-ru-alarms-v1.yang
@@ -1,6 +1,6 @@
 module o-ran-sc-ru-alarms-v1 {
   yang-version 1.1;
-  namespace "urn:o-ran-sc:ru:alarms:1.0";
+  namespace "urn:o-ran-sc:yang:o-ran-sc-ru-alarms-v1";
   prefix osc-ru-al;
 
   import ietf-alarms {
@@ -14,7 +14,7 @@ module o-ran-sc-ru-alarms-v1 {
   description
     "This module defines the alarm identities for the O-RAN-SC Components.
 
-     Copyright 2020 the O-RAN Software Community.
+     Copyright 2021 the O-RAN Software Community.
 
      Licensed under the Apache License, Version 2.0 (the 'License');
      you may not use this file except in compliance with the License.
@@ -28,6 +28,13 @@ module o-ran-sc-ru-alarms-v1 {
      See the License for the specific language governing permissions and
      limitations under the License.";
 
+  revision 2021-03-09 {
+    description
+      "The namespace was updated according to O-RAN-SC yang guidelines.
+       The namespace must end with the full module name.";
+    reference
+      "https://jira.o-ran-sc.org/browse/OAM-168";
+  }
   revision 2020-01-18 {
     description
       "initial revision";
@@ -48,7 +55,7 @@ module o-ran-sc-ru-alarms-v1 {
       "A generic alarm which is under development and analysis,
        must not happen in production environment.
        Instructions:
-         Create an JIRA issue and provide the following intormation:
+         Create an JIRA issue and provide the following information:
          - SMO version, build number or git hash
          - O-RU version, build number or git hash
          - A procedure to reproduce the alarm.";