Merge pull request #614 from nigel-r-davis/develop

Pull-request for 2.6 delivery

Author: nigel-r-davis

OAS/tapi-common.yaml

@@ -15,7 +15,14 @@ info:
     \ major versions of TAPI releases.\nThe YANG model backward compatibility criteria\
     \ are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\nYANG models\
     \ included in this release may not be backward compatible with previous TAPI releases.\n\
+    - Previous revisions can now be found at https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI\
+    \ under the appropriate tag and, where relevant, fixes to those revisions can be found\
+    \ under the corresponding branches. The documentation for each significant revision is\
+    \ found at https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI-Documentation\
+    \ under the appropriate tag and, where relevant, fixes to those revisions can be found\
+    \ under the corresponding branches.\n\
     License: This module is distributed under the Apache License 2.0."
+  revision: "2025-03-31"
   version: "2.6.0"
   title: "tapi-common API"
 host: "localhost:1234"

OAS/tapi-connectivity.yaml

@@ -91,6 +91,7 @@ info:
     \ are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\nYANG models\
     \ included in this release may not be backward compatible with previous TAPI releases.\n\
     License: This module is distributed under the Apache License 2.0."
+  revision: "2025-03-31"
   version: "2.6.0"
   title: "tapi-connectivity,tapi-streaming,tapi-path-computation,tapi-notification,tapi-topology,tapi-common\
     \ API"
@@ -26868,7 +26869,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -30842,7 +30848,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -45687,7 +45698,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -52806,7 +52822,12 @@ definitions:
       validation-mechanism:
         type: "array"
         description: "Provides details of the specific validation mechanism(s) used\
-          \ to confirm the presence of an intended topological entity."
+          \ to confirm the presence of an intended topological entity.\
+          \ Validation mechanism examples include a specific discovery protocol,\
+          \ a test carried out a commissioning, information from the plan.\
+          \ There is no formal format for the string. Considering each example,\
+          \ the string could be 'discovery protocol', 'commissioning test' or\
+          \ 'plan data'."
         items:
           $ref: "#/definitions/tapi.topology.ValidationMechanism"
     description: "Validation covers the various adjacency discovery and reachability\

OAS/tapi-digital-otn.yaml

@@ -166,6 +166,7 @@ info:
     \ are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\nYANG models\
     \ included in this release may not be backward compatible with previous TAPI releases.\n\
     License: This module is distributed under the Apache License 2.0."
+  revision: "2025-03-31"
   version: "2.6.0"
   title: "tapi-common,tapi-notification,tapi-topology,tapi-dsr,tapi-digital-otn,tapi-connectivity,tapi-fm,tapi-gnmi-streaming,tapi-oam,tapi-streaming,tapi-path-computation\
     \ API"
@@ -35986,7 +35987,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -39960,7 +39966,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -65673,7 +65684,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -77711,7 +77727,12 @@ definitions:
       validation-mechanism:
         type: "array"
         description: "Provides details of the specific validation mechanism(s) used\
-          \ to confirm the presence of an intended topological entity."
+          \ to confirm the presence of an intended topological entity.\
+          \ Validation mechanism examples include a specific discovery protocol,\
+          \ a test carried out a commissioning, information from the plan.\
+          \ There is no formal format for the string. Considering each example,\
+          \ the string could be 'discovery protocol', 'commissioning test' or\
+          \ 'plan data'."
         items:
           $ref: "#/definitions/tapi.topology.ValidationMechanism"
     description: "Validation covers the various adjacency discovery and reachability\

OAS/tapi-dsr.yaml

@@ -152,6 +152,7 @@ info:
     \ are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\nYANG models\
     \ included in this release may not be backward compatible with previous TAPI releases.\n\
     License: This module is distributed under the Apache License 2.0."
+  revision: "2025-03-31"
   version: "2.6.0"
   title: "tapi-gnmi-streaming,tapi-path-computation,tapi-dsr,tapi-connectivity,tapi-notification,tapi-fm,tapi-streaming,tapi-common,tapi-topology,tapi-oam\
     \ API"
@@ -34982,7 +34983,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -38956,7 +38962,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -60041,7 +60052,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -69117,7 +69133,12 @@ definitions:
       validation-mechanism:
         type: "array"
         description: "Provides details of the specific validation mechanism(s) used\
-          \ to confirm the presence of an intended topological entity."
+          \ to confirm the presence of an intended topological entity.\
+          \ Validation mechanism examples include a specific discovery protocol,\
+          \ a test carried out a commissioning, information from the plan.\
+          \ There is no formal format for the string. Considering each example,\
+          \ the string could be 'discovery protocol', 'commissioning test' or\
+          \ 'plan data'."
         items:
           $ref: "#/definitions/tapi.topology.ValidationMechanism"
     description: "Validation covers the various adjacency discovery and reachability\

OAS/tapi-equipment.yaml

@@ -106,6 +106,7 @@ info:
     \ are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\nYANG models\
     \ included in this release may not be backward compatible with previous TAPI releases.\n\
     License: This module is distributed under the Apache License 2.0."
+  revision: "2025-03-31"
   version: "2.6.0"
   title: "tapi-topology,tapi-notification,tapi-streaming,tapi-common,tapi-equipment,tapi-connectivity,tapi-path-computation\
     \ API"
@@ -31972,7 +31973,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -35946,7 +35952,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -50841,7 +50852,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -59102,7 +59118,12 @@ definitions:
       validation-mechanism:
         type: "array"
         description: "Provides details of the specific validation mechanism(s) used\
-          \ to confirm the presence of an intended topological entity."
+          \ to confirm the presence of an intended topological entity.\
+          \ Validation mechanism examples include a specific discovery protocol,\
+          \ a test carried out a commissioning, information from the plan.\
+          \ There is no formal format for the string. Considering each example,\
+          \ the string could be 'discovery protocol', 'commissioning test' or\
+          \ 'plan data'."
         items:
           $ref: "#/definitions/tapi.topology.ValidationMechanism"
     description: "Validation covers the various adjacency discovery and reachability\

OAS/tapi-eth.yaml

@@ -151,6 +151,7 @@ info:
     \ are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\nYANG models\
     \ included in this release may not be backward compatible with previous TAPI releases.\n\
     License: This module is distributed under the Apache License 2.0."
+  revision: "2025-03-31"
   version: "2.6.0"
   title: "tapi-fm,tapi-path-computation,tapi-gnmi-streaming,tapi-connectivity,tapi-notification,tapi-topology,tapi-common,tapi-oam,tapi-streaming,tapi-eth\
     \ API"
@@ -36483,7 +36484,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -40457,7 +40463,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -66417,7 +66428,12 @@ paths:
       - "tapi-topology"
       summary: "returns tapi.topology.ValidationMechanism"
       description: "Provides details of the specific validation mechanism(s) used\
-        \ to confirm the presence of an intended topological entity."
+        \ to confirm the presence of an intended topological entity.\
+        \ Validation mechanism examples include a specific discovery protocol,\
+        \ a test carried out a commissioning, information from the plan.\
+        \ There is no formal format for the string. Considering each example,\
+        \ the string could be 'discovery protocol', 'commissioning test' or\
+        \ 'plan data'."
       parameters:
       - name: "uuid"
         in: "path"
@@ -78943,7 +78959,12 @@ definitions:
       validation-mechanism:
         type: "array"
         description: "Provides details of the specific validation mechanism(s) used\
-          \ to confirm the presence of an intended topological entity."
+          \ to confirm the presence of an intended topological entity.\
+          \ Validation mechanism examples include a specific discovery protocol,\
+          \ a test carried out a commissioning, information from the plan.\
+          \ There is no formal format for the string. Considering each example,\
+          \ the string could be 'discovery protocol', 'commissioning test' or\
+          \ 'plan data'."
         items:
           $ref: "#/definitions/tapi.topology.ValidationMechanism"
     description: "Validation covers the various adjacency discovery and reachability\

OAS/tapi-fm.yaml

@@ -61,6 +61,7 @@ info:
     \ are outlined in section 11 of <https://tools.ietf.org/html/rfc7950>.\nYANG models\
     \ included in this release may not be backward compatible with previous TAPI releases.\n\
     License: This module is distributed under the Apache License 2.0."
+  revision: "2025-03-31"
   version: "2.6.0"
   title: "tapi-streaming,tapi-fm,tapi-common,tapi-notification API"
 host: "localhost:1234"