Merge "Fix sonar issues in SchemaGenerator"

[aai/aai-common.git] / aai-schema / src / main / resources / aai_swagger_yaml / aai_swagger_v10.yaml

diff --git a/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml b/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml
index 1dc7075..74425ab 100644 (file)
--- a/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml
+++ b/aai-schema/src/main/resources/aai_swagger_yaml/aai_swagger_v10.yaml
@@ -1,6 +1,9 @@
 swagger: "2.0"
 info:
   description: |
+
+    [Differences versus the previous schema version](apidocs/aai_swagger_v10.diff)
+
     Copyright © 2017 AT&T Intellectual Property. All rights reserved.
 
     Licensed under the Creative Commons License, Attribution 4.0 Intl. (the "License"); you may not use this documentation except in compliance with the License.
@@ -49,19 +52,22 @@ paths:
           description: Unique identifier for physical location, e.g., CLLI
           required: true
           type: string
+          example: __PHYSICAL-LOCATION-ID__
         - name: target-pe
           in: path
           description: The Target provider edge router
           required: true
           type: string
+          example: __TARGET-PE__
         - name: availability-zone-name
           in: path
           description: Name of the availability zone
           required: true
           type: string
+          example: __AVAILABILITY-ZONE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -86,16 +92,19 @@ paths:
           description: Unique identifier for physical location, e.g., CLLI
           required: true
           type: string
+          example: __PHYSICAL-LOCATION-ID__
         - name: target-pe
           in: path
           description: The Target provider edge router
           required: true
           type: string
+          example: __TARGET-PE__
         - name: availability-zone-name
           in: path
           description: Name of the availability zone
           required: true
           type: string
+          example: __AVAILABILITY-ZONE-NAME__
   /cloud-infrastructure/complexes/complex/{physical-location-id}/ctag-pools/ctag-pool/{target-pe}/{availability-zone-name}:
     get:
       tags:
@@ -110,7 +119,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/ctag-pool"
+              $ref: "#/getDefinitions/ctag-pool"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -119,36 +128,27 @@ paths:
           description: Unique identifier for physical location, e.g., CLLI
           required: true
           type: string
+          example: __PHYSICAL-LOCATION-ID__
         - name: target-pe
           in: path
           description: The Target provider edge router
           required: true
           type: string
+          example: __TARGET-PE__
         - name: availability-zone-name
           in: path
           description: Name of the availability zone
           required: true
           type: string
-        - name: data-center-code
-          in: query
-          description: Data center code which can be an alternate way to identify a complex
-          required: false
-          type: string
-        - name: complex-name
-          in: query
-          description: Gamma complex name for LCP instance.
-          required: false
-          type: string
-        - name: identity-url
-          in: query
-          description: URL of the keystone identity service
-          required: false
-          type: string
+          example: __AVAILABILITY-ZONE-NAME__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing ctag-pool
-      description: create or update an existing ctag-pool
+      description: |
+        Create or update an existing ctag-pool.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureComplexesComplexCtagPoolsCtagPool
       consumes:
         - application/json
@@ -165,22 +165,76 @@ paths:
           description: Unique identifier for physical location, e.g., CLLI
           required: true
           type: string
+          example: __PHYSICAL-LOCATION-ID__
         - name: target-pe
           in: path
           description: The Target provider edge router
           required: true
           type: string
+          example: __TARGET-PE__
         - name: availability-zone-name
           in: path
           description: Name of the availability zone
           required: true
           type: string
+          example: __AVAILABILITY-ZONE-NAME__
         - name: body
           in: body
-          description: ctag-pool object that needs to be created or updated
+          description: ctag-pool object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplexCtagPoolsCtagPool.json)
           required: true
           schema:
             $ref: "#/definitions/ctag-pool"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing ctag-pool
+      description: |
+        Update an existing ctag-pool
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureComplexesComplexCtagPoolsCtagPool
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: physical-location-id
+          in: path
+          description: Unique identifier for physical location, e.g., CLLI
+          required: true
+          type: string
+          example: __PHYSICAL-LOCATION-ID__
+        - name: target-pe
+          in: path
+          description: The Target provider edge router
+          required: true
+          type: string
+          example: __TARGET-PE__
+        - name: availability-zone-name
+          in: path
+          description: Name of the availability zone
+          required: true
+          type: string
+          example: __AVAILABILITY-ZONE-NAME__
+        - name: body
+          in: body
+          description: ctag-pool object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/ctag-pool"
     delete:
       tags:
         - CloudInfrastructure
@@ -202,16 +256,19 @@ paths:
           description: Unique identifier for physical location, e.g., CLLI
           required: true
           type: string
+          example: __PHYSICAL-LOCATION-ID__
         - name: target-pe
           in: path
           description: The Target provider edge router
           required: true
           type: string
+          example: __TARGET-PE__
         - name: availability-zone-name
           in: path
           description: Name of the availability zone
           required: true
           type: string
+          example: __AVAILABILITY-ZONE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -231,7 +288,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/ctag-pools"
+              $ref: "#/getDefinitions/ctag-pools"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -240,19 +297,10 @@ paths:
           description: Unique identifier for physical location, e.g., CLLI
           required: true
           type: string
-        - name: data-center-code
-          in: query
-          description: Data center code which can be an alternate way to identify a complex
-          required: false
-          type: string
-        - name: complex-name
-          in: query
-          description: Gamma complex name for LCP instance.
-          required: false
-          type: string
-        - name: identity-url
+          example: __PHYSICAL-LOCATION-ID__
+        - name: availability-zone-name
           in: query
-          description: URL of the keystone identity service
+          description:
           required: false
           type: string
   /cloud-infrastructure/complexes/complex/{physical-location-id}/relationship-list/relationship:
@@ -276,9 +324,10 @@ paths:
           description: Unique identifier for physical location, e.g., CLLI
           required: true
           type: string
+          example: __PHYSICAL-LOCATION-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplex.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -303,6 +352,7 @@ paths:
           description: Unique identifier for physical location, e.g., CLLI
           required: true
           type: string
+          example: __PHYSICAL-LOCATION-ID__
   /cloud-infrastructure/complexes/complex/{physical-location-id}:
     get:
       tags:
@@ -317,7 +367,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/complex"
+              $ref: "#/getDefinitions/complex"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -326,26 +376,15 @@ paths:
           description: Unique identifier for physical location, e.g., CLLI
           required: true
           type: string
-        - name: data-center-code
-          in: query
-          description: Data center code which can be an alternate way to identify a complex
-          required: false
-          type: string
-        - name: complex-name
-          in: query
-          description: Gamma complex name for LCP instance.
-          required: false
-          type: string
-        - name: identity-url
-          in: query
-          description: URL of the keystone identity service
-          required: false
-          type: string
+          example: __PHYSICAL-LOCATION-ID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing complex
-      description: create or update an existing complex
+      description: |
+        Create or update an existing complex.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureComplexesComplex
       consumes:
         - application/json
@@ -362,12 +401,52 @@ paths:
           description: Unique identifier for physical location, e.g., CLLI
           required: true
           type: string
+          example: __PHYSICAL-LOCATION-ID__
         - name: body
           in: body
-          description: complex object that needs to be created or updated
+          description: complex object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureComplexesComplex.json)
           required: true
           schema:
             $ref: "#/definitions/complex"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing complex
+      description: |
+        Update an existing complex
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureComplexesComplex
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: physical-location-id
+          in: path
+          description: Unique identifier for physical location, e.g., CLLI
+          required: true
+          type: string
+          example: __PHYSICAL-LOCATION-ID__
+        - name: body
+          in: body
+          description: complex object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/complex"
     delete:
       tags:
         - CloudInfrastructure
@@ -389,6 +468,7 @@ paths:
           description: Unique identifier for physical location, e.g., CLLI
           required: true
           type: string
+          example: __PHYSICAL-LOCATION-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -408,9 +488,30 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/complexes"
+              $ref: "#/getDefinitions/complexes"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: physical-location-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: data-center-code
+          in: query
+          description:
+          required: false
+          type: string
+        - name: complex-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: identity-url
+          in: query
+          description:
+          required: false
+          type: string
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}/relationship-list/relationship:
     put:
       tags:
@@ -432,19 +533,22 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: volume-group-id
           in: path
           description: Unique ID of volume-group.
           required: true
           type: string
+          example: __VOLUME-GROUP-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -469,16 +573,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: volume-group-id
           in: path
           description: Unique ID of volume-group.
           required: true
           type: string
+          example: __VOLUME-GROUP-ID__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/volume-groups/volume-group/{volume-group-id}:
     get:
       tags:
@@ -493,7 +600,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/volume-group"
+              $ref: "#/getDefinitions/volume-group"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -502,46 +609,27 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: volume-group-id
           in: path
           description: Unique ID of volume-group.
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: volume-group-name
-          in: query
-          description: Name of the volume group.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this volume-group
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
+          example: __VOLUME-GROUP-ID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing volume-group
-      description: create or update an existing volume-group
+      description: |
+        Create or update an existing volume-group.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup
       consumes:
         - application/json
@@ -558,22 +646,76 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: volume-group-id
           in: path
           description: Unique ID of volume-group.
           required: true
           type: string
+          example: __VOLUME-GROUP-ID__
         - name: body
           in: body
-          description: volume-group object that needs to be created or updated
+          description: volume-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup.json)
           required: true
           schema:
             $ref: "#/definitions/volume-group"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing volume-group
+      description: |
+        Update an existing volume-group
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionVolumeGroupsVolumeGroup
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: volume-group-id
+          in: path
+          description: Unique ID of volume-group.
+          required: true
+          type: string
+          example: __VOLUME-GROUP-ID__
+        - name: body
+          in: body
+          description: volume-group object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/volume-group"
     delete:
       tags:
         - CloudInfrastructure
@@ -595,16 +737,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: volume-group-id
           in: path
           description: Unique ID of volume-group.
           required: true
           type: string
+          example: __VOLUME-GROUP-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -624,7 +769,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/volume-groups"
+              $ref: "#/getDefinitions/volume-groups"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -633,19 +778,31 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
-        - name: cloud-type
+          example: __CLOUD-REGION-ID__
+        - name: volume-group-id
           in: query
-          description: Type of the cloud (e.g., openstack)
+          description:
           required: false
           type: string
-        - name: owner-defined-type
+        - name: volume-group-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: heat-stack-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vnf-type
           in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+          description:
           required: false
           type: string
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}/relationship-list/relationship:
@@ -669,29 +826,34 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: volume-id
           in: path
           description: Unique ID of block storage volume relative to the vserver.
           required: true
           type: string
+          example: __VOLUME-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -716,26 +878,31 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: volume-id
           in: path
           description: Unique ID of block storage volume relative to the vserver.
           required: true
           type: string
+          example: __VOLUME-ID__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/volumes/volume/{volume-id}:
     get:
       tags:
@@ -750,7 +917,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/volume"
+              $ref: "#/getDefinitions/volume"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -759,70 +926,103 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: volume-id
           in: path
           description: Unique ID of block storage volume relative to the vserver.
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
+          example: __VOLUME-ID__
+    put:
+      tags:
+        - CloudInfrastructure
+      summary: create or update an existing volume
+      description: |
+        Create or update an existing volume.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
           type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
           type: string
-        - name: vserver-name
-          in: query
-          description: Name of vserver
-          required: false
+          example: __CLOUD-REGION-ID__
+        - name: tenant-id
+          in: path
+          description: Unique id relative to the cloud-region.
+          required: true
           type: string
-        - name: vserver-name2
-          in: query
-          description: Alternative name of vserver
-          required: false
+          example: __TENANT-ID__
+        - name: vserver-id
+          in: path
+          description: Unique identifier for this vserver relative to its tenant
+          required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
+          example: __VSERVER-ID__
+        - name: volume-id
+          in: path
+          description: Unique ID of block storage volume relative to the vserver.
+          required: true
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-    put:
+          example: __VOLUME-ID__
+        - name: body
+          in: body
+          description: volume object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume.json)
+          required: true
+          schema:
+            $ref: "#/definitions/volume"
+    patch:
       tags:
         - CloudInfrastructure
-      summary: create or update an existing volume
-      description: create or update an existing volume
-      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume
+      summary: update an existing volume
+      description: |
+        Update an existing volume
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverVolumesVolume
       consumes:
         - application/json
         - application/xml
@@ -838,32 +1038,37 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: volume-id
           in: path
           description: Unique ID of block storage volume relative to the vserver.
           required: true
           type: string
+          example: __VOLUME-ID__
         - name: body
           in: body
-          description: volume object that needs to be created or updated
+          description: volume object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/volume"
+            $ref: "#/patchDefinitions/volume"
     delete:
       tags:
         - CloudInfrastructure
@@ -885,26 +1090,31 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: volume-id
           in: path
           description: Unique ID of block storage volume relative to the vserver.
           required: true
           type: string
+          example: __VOLUME-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -924,7 +1134,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/volumes"
+              $ref: "#/getDefinitions/volumes"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -933,59 +1143,30 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
-          type: string
-        - name: vserver-name
-          in: query
-          description: Name of vserver
-          required: false
-          type: string
-        - name: vserver-name2
-          in: query
-          description: Alternative name of vserver
-          required: false
-          type: string
-        - name: prov-status
+          example: __VSERVER-ID__
+        - name: volume-id
           in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
+          description:
           required: false
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/relationship-list/relationship:
     put:
       tags:
@@ -1007,24 +1188,28 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -1049,21 +1234,25 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
     put:
       tags:
@@ -1085,34 +1274,40 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -1137,31 +1332,37 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -1183,39 +1384,46 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -1240,36 +1448,43 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -1284,7 +1499,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -1293,122 +1508,127 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
-          type: string
-        - name: vserver-name
-          in: query
-          description: Name of vserver
-          required: false
-          type: string
-        - name: vserver-name2
-          in: query
-          description: Alternative name of vserver
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+    put:
+      tags:
+        - CloudInfrastructure
+      summary: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
           type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __CLOUD-REGION-ID__
+        - name: tenant-id
+          in: path
+          description: Unique id relative to the cloud-region.
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __TENANT-ID__
+        - name: vserver-id
+          in: path
+          description: Unique identifier for this vserver relative to its tenant
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
+          example: __VSERVER-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
       tags:
         - CloudInfrastructure
-      summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
-      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -1424,42 +1644,49 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv4-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - CloudInfrastructure
@@ -1481,36 +1708,43 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -1537,39 +1771,46 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -1594,36 +1835,43 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -1638,7 +1886,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -1647,122 +1895,127 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
-          type: string
-        - name: vserver-name
-          in: query
-          description: Name of vserver
-          required: false
-          type: string
-        - name: vserver-name2
-          in: query
-          description: Alternative name of vserver
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+    put:
+      tags:
+        - CloudInfrastructure
+      summary: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
           type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __CLOUD-REGION-ID__
+        - name: tenant-id
+          in: path
+          description: Unique id relative to the cloud-region.
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __TENANT-ID__
+        - name: vserver-id
+          in: path
+          description: Unique identifier for this vserver relative to its tenant
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
+          example: __VSERVER-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
       tags:
         - CloudInfrastructure
-      summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
-      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
       consumes:
         - application/json
         - application/xml
@@ -1778,42 +2031,49 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv6-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - CloudInfrastructure
@@ -1835,36 +2095,43 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -1884,7 +2151,62 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlan"
+              $ref: "#/getDefinitions/vlan"
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: tenant-id
+          in: path
+          description: Unique id relative to the cloud-region.
+          required: true
+          type: string
+          example: __TENANT-ID__
+        - name: vserver-id
+          in: path
+          description: Unique identifier for this vserver relative to its tenant
+          required: true
+          type: string
+          example: __VSERVER-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+    put:
+      tags:
+        - CloudInfrastructure
+      summary: create or update an existing vlan
+      description: |
+        Create or update an existing vlan.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -1893,101 +2215,60 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
-          type: string
-        - name: vserver-name
-          in: query
-          description: Name of vserver
-          required: false
-          type: string
-        - name: vserver-name2
-          in: query
-          description: Alternative name of vserver
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
-    put:
+          example: __VLAN-INTERFACE__
+        - name: body
+          in: body
+          description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan.json)
+          required: true
+          schema:
+            $ref: "#/definitions/vlan"
+    patch:
       tags:
         - CloudInfrastructure
-      summary: create or update an existing vlan
-      description: create or update an existing vlan
-      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan
+      summary: update an existing vlan
+      description: |
+        Update an existing vlan
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceVlansVlan
       consumes:
         - application/json
         - application/xml
@@ -2003,37 +2284,43 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: vlan object that needs to be created or updated
+          description: vlan object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/vlan"
+            $ref: "#/patchDefinitions/vlan"
     delete:
       tags:
         - CloudInfrastructure
@@ -2055,31 +2342,37 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -2099,7 +2392,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlans"
+              $ref: "#/getDefinitions/vlans"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -2108,77 +2401,45 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
-          type: string
-        - name: vserver-name
-          in: query
-          description: Name of vserver
-          required: false
-          type: string
-        - name: vserver-name2
-          in: query
-          description: Alternative name of vserver
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vlan-id-inner
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: integer
+          format: int64
+        - name: vpn-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}/relationship-list/relationship:
@@ -2202,34 +2463,40 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -2254,31 +2521,37 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
     get:
       tags:
@@ -2293,7 +2566,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vf"
+              $ref: "#/getDefinitions/sriov-vf"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -2302,110 +2575,115 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
-          type: string
-        - name: vserver-name
-          in: query
-          description: Name of vserver
-          required: false
-          type: string
-        - name: vserver-name2
-          in: query
-          description: Alternative name of vserver
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
+          example: __PCI-ID__
+    put:
+      tags:
+        - CloudInfrastructure
+      summary: create or update an existing sriov-vf
+      description: |
+        Create or update an existing sriov-vf.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
           type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __CLOUD-REGION-ID__
+        - name: tenant-id
+          in: path
+          description: Unique id relative to the cloud-region.
+          required: true
           type: string
-        - name: vf-vlan-filter
-          in: query
-          description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
-          required: false
+          example: __TENANT-ID__
+        - name: vserver-id
+          in: path
+          description: Unique identifier for this vserver relative to its tenant
+          required: true
           type: string
-        - name: vf-mac-filter
-          in: query
-          description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
-          required: false
+          example: __VSERVER-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vf-vlan-strip
-          in: query
-          description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
-          required: false
-          type: boolean
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface
-          required: false
+          example: __INTERFACE-NAME__
+        - name: pci-id
+          in: path
+          description: PCI ID used to identify the sriov-vf
+          required: true
           type: string
-    put:
+          example: __PCI-ID__
+        - name: body
+          in: body
+          description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf.json)
+          required: true
+          schema:
+            $ref: "#/definitions/sriov-vf"
+    patch:
       tags:
         - CloudInfrastructure
-      summary: create or update an existing sriov-vf
-      description: create or update an existing sriov-vf
-      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf
+      summary: update an existing sriov-vf
+      description: |
+        Update an existing sriov-vf
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceSriovVfsSriovVf
       consumes:
         - application/json
         - application/xml
@@ -2421,37 +2699,43 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: sriov-vf object that needs to be created or updated
+          description: sriov-vf object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/sriov-vf"
+            $ref: "#/patchDefinitions/sriov-vf"
     delete:
       tags:
         - CloudInfrastructure
@@ -2473,31 +2757,37 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -2517,101 +2807,78 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vfs"
-        "default":
-          description: Response codes found in [response codes](https://wiki.onap.org/).
-      parameters:
-        - name: cloud-owner
-          in: path
-          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
-          required: true
-          type: string
-        - name: cloud-region-id
-          in: path
-          description: Identifier used by the vendor for the region. Second part of composite key
-          required: true
-          type: string
-        - name: tenant-id
-          in: path
-          description: Unique id relative to the cloud-region.
-          required: true
-          type: string
-        - name: vserver-id
-          in: path
-          description: Unique identifier for this vserver relative to its tenant
-          required: true
-          type: string
-        - name: interface-name
-          in: path
-          description: Name given to the interface
-          required: true
-          type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
-          type: string
-        - name: vserver-name
-          in: query
-          description: Name of vserver
-          required: false
-          type: string
-        - name: vserver-name2
-          in: query
-          description: Alternative name of vserver
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-  /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/relationship-list/relationship:
-    put:
-      tags:
-        - CloudInfrastructure
-      summary: see node definition for valid relationships
-      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceRelationshipListRelationship
-      consumes:
-        - application/json
-        - application/xml
-      produces:
-        - application/json
-        - application/xml
-      responses:
+              $ref: "#/getDefinitions/sriov-vfs"
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: tenant-id
+          in: path
+          description: Unique id relative to the cloud-region.
+          required: true
+          type: string
+          example: __TENANT-ID__
+        - name: vserver-id
+          in: path
+          description: Unique identifier for this vserver relative to its tenant
+          required: true
+          type: string
+          example: __VSERVER-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: pci-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vf-vlan-filter
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vf-mac-filter
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vf-vlan-strip
+          in: query
+          description:
+          required: false
+          type: boolean
+        - name: neutron-network-id
+          in: query
+          description:
+          required: false
+          type: string
+  /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/relationship-list/relationship:
+    put:
+      tags:
+        - CloudInfrastructure
+      summary: see node definition for valid relationships
+      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceRelationshipListRelationship
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -2620,29 +2887,34 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -2667,26 +2939,31 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -2708,34 +2985,40 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -2760,31 +3043,37 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -2799,7 +3088,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -2808,106 +3097,115 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
-          type: string
-        - name: vserver-name
-          in: query
-          description: Name of vserver
-          required: false
-          type: string
-        - name: vserver-name2
-          in: query
-          description: Alternative name of vserver
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+    put:
+      tags:
+        - CloudInfrastructure
+      summary: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
           type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __CLOUD-REGION-ID__
+        - name: tenant-id
+          in: path
+          description: Unique id relative to the cloud-region.
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __TENANT-ID__
+        - name: vserver-id
+          in: path
+          description: Unique identifier for this vserver relative to its tenant
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __VSERVER-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
       tags:
         - CloudInfrastructure
-      summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
-      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -2923,37 +3221,43 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv4-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - CloudInfrastructure
@@ -2975,31 +3279,37 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -3026,34 +3336,40 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -3078,31 +3394,37 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -3117,7 +3439,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -3126,105 +3448,45 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
-          type: string
-        - name: vserver-name
-          in: query
-          description: Name of vserver
-          required: false
-          type: string
-        - name: vserver-name2
-          in: query
-          description: Alternative name of vserver
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -3241,43 +3503,60 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
-    delete:
+    patch:
       tags:
         - CloudInfrastructure
-      summary: delete an existing l3-interface-ipv6-address-list
-      description: delete an existing l3-interface-ipv6-address-list
-      operationId: deleteCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList
       consumes:
         - application/json
         - application/xml
@@ -3293,51 +3572,56 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: resource-version
-          in: query
-          description: resource-version for concurrency
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
           required: true
-          type: string
-  /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}:
-    get:
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
+    delete:
       tags:
         - CloudInfrastructure
-      summary: returns l-interface
-      description: returns l-interface
-      operationId: getCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface
+      summary: delete an existing l3-interface-ipv6-address-list
+      description: delete an existing l3-interface-ipv6-address-list
+      operationId: deleteCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterfaceL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
       produces:
         - application/json
         - application/xml
       responses:
-        "200":
-          description: successful operation
-          schema:
-              $ref: "#/definitions/l-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -3346,84 +3630,98 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
           type: string
-        - name: vserver-name
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: resource-version
           in: query
-          description: Name of vserver
-          required: false
+          description: resource-version for concurrency
+          required: true
           type: string
-        - name: vserver-name2
-          in: query
-          description: Alternative name of vserver
-          required: false
+  /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}/l-interfaces/l-interface/{interface-name}:
+    get:
+      tags:
+        - CloudInfrastructure
+      summary: returns l-interface
+      description: returns l-interface
+      operationId: getCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "200":
+          description: successful operation
+          schema:
+              $ref: "#/getDefinitions/l-interface"
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
+          example: __CLOUD-REGION-ID__
+        - name: tenant-id
+          in: path
+          description: Unique id relative to the cloud-region.
+          required: true
           type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __TENANT-ID__
+        - name: vserver-id
+          in: path
+          description: Unique identifier for this vserver relative to its tenant
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __VSERVER-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing l-interface
-      description: create or update an existing l-interface
+      description: |
+        Create or update an existing l-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface
       consumes:
         - application/json
@@ -3440,32 +3738,100 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: l-interface object that needs to be created or updated
+          description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/l-interface"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing l-interface
+      description: |
+        Update an existing l-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserverLInterfacesLInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: tenant-id
+          in: path
+          description: Unique id relative to the cloud-region.
+          required: true
+          type: string
+          example: __TENANT-ID__
+        - name: vserver-id
+          in: path
+          description: Unique identifier for this vserver relative to its tenant
+          required: true
+          type: string
+          example: __VSERVER-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: l-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l-interface"
     delete:
       tags:
         - CloudInfrastructure
@@ -3487,26 +3853,31 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -3526,7 +3897,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interfaces"
+              $ref: "#/getDefinitions/l-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -3535,59 +3906,45 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
+          example: __VSERVER-ID__
+        - name: interface-name
           in: query
-          description: Readable name of tenant
+          description:
           required: false
           type: string
-        - name: vserver-name
+        - name: interface-id
           in: query
-          description: Name of vserver
+          description:
           required: false
           type: string
-        - name: vserver-name2
+        - name: macaddr
           in: query
-          description: Alternative name of vserver
+          description:
           required: false
           type: string
-        - name: prov-status
+        - name: network-name
           in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
+          description:
           required: false
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/vservers/vserver/{vserver-id}:
     get:
       tags:
@@ -3602,7 +3959,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vserver"
+              $ref: "#/getDefinitions/vserver"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -3611,64 +3968,33 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
-          type: string
-        - name: vserver-name
-          in: query
-          description: Name of vserver
-          required: false
-          type: string
-        - name: vserver-name2
-          in: query
-          description: Alternative name of vserver
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
+          example: __VSERVER-ID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing vserver
-      description: create or update an existing vserver
+      description: |
+        Create or update an existing vserver.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver
       consumes:
         - application/json
@@ -3685,27 +4011,88 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: body
           in: body
-          description: vserver object that needs to be created or updated
+          description: vserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver.json)
           required: true
           schema:
             $ref: "#/definitions/vserver"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing vserver
+      description: |
+        Update an existing vserver
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenantVserversVserver
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: tenant-id
+          in: path
+          description: Unique id relative to the cloud-region.
+          required: true
+          type: string
+          example: __TENANT-ID__
+        - name: vserver-id
+          in: path
+          description: Unique identifier for this vserver relative to its tenant
+          required: true
+          type: string
+          example: __VSERVER-ID__
+        - name: body
+          in: body
+          description: vserver object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vserver"
     delete:
       tags:
         - CloudInfrastructure
@@ -3727,21 +4114,25 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: vserver-id
           in: path
           description: Unique identifier for this vserver relative to its tenant
           required: true
           type: string
+          example: __VSERVER-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -3761,7 +4152,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vservers"
+              $ref: "#/getDefinitions/vservers"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -3770,31 +4161,49 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
-        - name: cloud-type
+          example: __TENANT-ID__
+        - name: vserver-id
           in: query
-          description: Type of the cloud (e.g., openstack)
+          description:
           required: false
           type: string
-        - name: owner-defined-type
+        - name: vserver-name
           in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+          description:
           required: false
           type: string
-        - name: tenant-name
+        - name: vserver-name2
+          in: query
+          description:
+          required: false
+          type: string
+        - name: prov-status
           in: query
-          description: Readable name of tenant
+          description:
           required: false
           type: string
+        - name: in-maint
+          in: query
+          description:
+          required: false
+          type: boolean
+        - name: is-closed-loop-disabled
+          in: query
+          description:
+          required: false
+          type: boolean
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}/relationship-list/relationship:
     put:
       tags:
@@ -3816,19 +4225,22 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -3853,16 +4265,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/tenants/tenant/{tenant-id}:
     get:
       tags:
@@ -3877,7 +4292,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/tenant"
+              $ref: "#/getDefinitions/tenant"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -3886,36 +4301,27 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: tenant-name
-          in: query
-          description: Readable name of tenant
-          required: false
-          type: string
+          example: __TENANT-ID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing tenant
-      description: create or update an existing tenant
+      description: |
+        Create or update an existing tenant.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenant
       consumes:
         - application/json
@@ -3932,22 +4338,76 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: body
           in: body
-          description: tenant object that needs to be created or updated
+          description: tenant object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionTenantsTenant.json)
           required: true
           schema:
             $ref: "#/definitions/tenant"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing tenant
+      description: |
+        Update an existing tenant
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionTenantsTenant
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: tenant-id
+          in: path
+          description: Unique id relative to the cloud-region.
+          required: true
+          type: string
+          example: __TENANT-ID__
+        - name: body
+          in: body
+          description: tenant object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/tenant"
     delete:
       tags:
         - CloudInfrastructure
@@ -3969,16 +4429,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: tenant-id
           in: path
           description: Unique id relative to the cloud-region.
           required: true
           type: string
+          example: __TENANT-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -3998,7 +4461,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/tenants"
+              $ref: "#/getDefinitions/tenants"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -4007,19 +4470,21 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
-        - name: cloud-type
+          example: __CLOUD-REGION-ID__
+        - name: tenant-id
           in: query
-          description: Type of the cloud (e.g., openstack)
+          description:
           required: false
           type: string
-        - name: owner-defined-type
+        - name: tenant-name
           in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+          description:
           required: false
           type: string
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}/relationship-list/relationship:
@@ -4043,19 +4508,22 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: flavor-id
           in: path
           description: Flavor id, expected to be unique across cloud-region.
           required: true
           type: string
+          example: __FLAVOR-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -4080,16 +4548,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: flavor-id
           in: path
           description: Flavor id, expected to be unique across cloud-region.
           required: true
           type: string
+          example: __FLAVOR-ID__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/flavors/flavor/{flavor-id}:
     get:
       tags:
@@ -4104,7 +4575,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/flavor"
+              $ref: "#/getDefinitions/flavor"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -4113,36 +4584,27 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: flavor-id
           in: path
           description: Flavor id, expected to be unique across cloud-region.
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: flavor-name
-          in: query
-          description: Flavor name
-          required: false
-          type: string
+          example: __FLAVOR-ID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing flavor
-      description: create or update an existing flavor
+      description: |
+        Create or update an existing flavor.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor
       consumes:
         - application/json
@@ -4159,22 +4621,76 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: flavor-id
           in: path
           description: Flavor id, expected to be unique across cloud-region.
           required: true
           type: string
+          example: __FLAVOR-ID__
         - name: body
           in: body
-          description: flavor object that needs to be created or updated
+          description: flavor object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor.json)
           required: true
           schema:
             $ref: "#/definitions/flavor"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing flavor
+      description: |
+        Update an existing flavor
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionFlavorsFlavor
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: flavor-id
+          in: path
+          description: Flavor id, expected to be unique across cloud-region.
+          required: true
+          type: string
+          example: __FLAVOR-ID__
+        - name: body
+          in: body
+          description: flavor object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/flavor"
     delete:
       tags:
         - CloudInfrastructure
@@ -4196,16 +4712,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: flavor-id
           in: path
           description: Flavor id, expected to be unique across cloud-region.
           required: true
           type: string
+          example: __FLAVOR-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -4225,7 +4744,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/flavors"
+              $ref: "#/getDefinitions/flavors"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -4234,19 +4753,21 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
-        - name: cloud-type
+          example: __CLOUD-REGION-ID__
+        - name: flavor-id
           in: query
-          description: Type of the cloud (e.g., openstack)
+          description:
           required: false
           type: string
-        - name: owner-defined-type
+        - name: flavor-name
           in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+          description:
           required: false
           type: string
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}/relationship-list/relationship:
@@ -4270,19 +4791,22 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: group-id
           in: path
           description: Group id, expected to be unique across cloud-region.
           required: true
           type: string
+          example: __GROUP-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -4307,16 +4831,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: group-id
           in: path
           description: Group id, expected to be unique across cloud-region.
           required: true
           type: string
+          example: __GROUP-ID__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/group-assignments/group-assignment/{group-id}:
     get:
       tags:
@@ -4331,7 +4858,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/group-assignment"
+              $ref: "#/getDefinitions/group-assignment"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -4340,41 +4867,27 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: group-id
           in: path
           description: Group id, expected to be unique across cloud-region.
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: group-type
-          in: query
-          description: Group type - the type of group this instance refers to
-          required: false
-          type: string
-        - name: group-name
-          in: query
-          description: Group name - name assigned to the group
-          required: false
-          type: string
+          example: __GROUP-ID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing group-assignment
-      description: create or update an existing group-assignment
+      description: |
+        Create or update an existing group-assignment.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment
       consumes:
         - application/json
@@ -4391,22 +4904,76 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: group-id
           in: path
           description: Group id, expected to be unique across cloud-region.
           required: true
           type: string
+          example: __GROUP-ID__
         - name: body
           in: body
-          description: group-assignment object that needs to be created or updated
+          description: group-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment.json)
           required: true
           schema:
             $ref: "#/definitions/group-assignment"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing group-assignment
+      description: |
+        Update an existing group-assignment
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionGroupAssignmentsGroupAssignment
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: group-id
+          in: path
+          description: Group id, expected to be unique across cloud-region.
+          required: true
+          type: string
+          example: __GROUP-ID__
+        - name: body
+          in: body
+          description: group-assignment object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/group-assignment"
     delete:
       tags:
         - CloudInfrastructure
@@ -4428,16 +4995,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: group-id
           in: path
           description: Group id, expected to be unique across cloud-region.
           required: true
           type: string
+          example: __GROUP-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -4457,7 +5027,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/group-assignments"
+              $ref: "#/getDefinitions/group-assignments"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -4466,19 +5036,26 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
-        - name: cloud-type
+          example: __CLOUD-REGION-ID__
+        - name: group-id
           in: query
-          description: Type of the cloud (e.g., openstack)
+          description:
           required: false
           type: string
-        - name: owner-defined-type
+        - name: group-type
+          in: query
+          description:
+          required: false
+          type: string
+        - name: group-name
           in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+          description:
           required: false
           type: string
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}/relationship-list/relationship:
@@ -4502,19 +5079,22 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: snapshot-id
           in: path
           description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
           required: true
           type: string
+          example: __SNAPSHOT-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -4539,16 +5119,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: snapshot-id
           in: path
           description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
           required: true
           type: string
+          example: __SNAPSHOT-ID__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots/snapshot/{snapshot-id}:
     get:
       tags:
@@ -4563,7 +5146,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/snapshot"
+              $ref: "#/getDefinitions/snapshot"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -4572,56 +5155,27 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: snapshot-id
           in: path
           description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: snapshot-name
-          in: query
-          description: Snapshot name
-          required: false
-          type: string
-        - name: application
-          in: query
-          description: The application that the image instantiates.
-          required: false
-          type: string
-        - name: application-vendor
-          in: query
-          description: The vendor of the application.
-          required: false
-          type: string
-        - name: application-version
-          in: query
-          description: The version of the application.
-          required: false
-          type: string
-        - name: prev-snapshot-id
-          in: query
-          description: This field contains the UUID of the previous snapshot (if any).
-          required: false
-          type: string
+          example: __SNAPSHOT-ID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing snapshot
-      description: create or update an existing snapshot
+      description: |
+        Create or update an existing snapshot.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot
       consumes:
         - application/json
@@ -4638,28 +5192,42 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: snapshot-id
           in: path
           description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
           required: true
           type: string
+          example: __SNAPSHOT-ID__
         - name: body
           in: body
-          description: snapshot object that needs to be created or updated
+          description: snapshot object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot.json)
           required: true
           schema:
             $ref: "#/definitions/snapshot"
-    delete:
+    patch:
       tags:
         - CloudInfrastructure
-      summary: delete an existing snapshot
-      description: delete an existing snapshot
-      operationId: deleteCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot
+      summary: update an existing snapshot
+      description: |
+        Update an existing snapshot
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot
       consumes:
         - application/json
         - application/xml
@@ -4675,102 +5243,31 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: snapshot-id
           in: path
           description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
           required: true
           type: string
-        - name: resource-version
-          in: query
-          description: resource-version for concurrency
-          required: true
-          type: string
-  /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots:
-    get:
-      tags:
-        - CloudInfrastructure
-      summary: returns snapshots
-      description: returns snapshots
-      operationId: getCloudInfrastructureCloudRegionsCloudRegionSnapshots
-      produces:
-        - application/json
-        - application/xml
-      responses:
-        "200":
-          description: successful operation
-          schema:
-              $ref: "#/definitions/snapshots"
-        "default":
-          description: Response codes found in [response codes](https://wiki.onap.org/).
-      parameters:
-        - name: cloud-owner
-          in: path
-          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
-          required: true
-          type: string
-        - name: cloud-region-id
-          in: path
-          description: Identifier used by the vendor for the region. Second part of composite key
-          required: true
-          type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-  /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/relationship-list/relationship:
-    put:
-      tags:
-        - CloudInfrastructure
-      summary: see node definition for valid relationships
-      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageRelationshipListRelationship
-      consumes:
-        - application/json
-        - application/xml
-      produces:
-        - application/json
-        - application/xml
-      responses:
-        "default":
-          description: Response codes found in [response codes](https://wiki.onap.org/).
-      parameters:
-        - name: cloud-owner
-          in: path
-          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
-          required: true
-          type: string
-        - name: cloud-region-id
-          in: path
-          description: Identifier used by the vendor for the region. Second part of composite key
-          required: true
-          type: string
-        - name: image-id
-          in: path
-          description: Image id, expected to be unique across cloud region
-          required: true
-          type: string
+          example: __SNAPSHOT-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: snapshot object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/relationship"
+            $ref: "#/patchDefinitions/snapshot"
     delete:
       tags:
         - CloudInfrastructure
-      summary: delete an existing relationship
-      description: delete an existing relationship
-      operationId: deleteCloudInfrastructureCloudRegionsCloudRegionImagesImageRelationshipListRelationship
+      summary: delete an existing snapshot
+      description: delete an existing snapshot
+      operationId: deleteCloudInfrastructureCloudRegionsCloudRegionSnapshotsSnapshot
       consumes:
         - application/json
         - application/xml
@@ -4786,23 +5283,31 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
-        - name: image-id
+          example: __CLOUD-REGION-ID__
+        - name: snapshot-id
           in: path
-          description: Image id, expected to be unique across cloud region
+          description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
           required: true
           type: string
-  /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}:
+          example: __SNAPSHOT-ID__
+        - name: resource-version
+          in: query
+          description: resource-version for concurrency
+          required: true
+          type: string
+  /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/snapshots:
     get:
       tags:
         - CloudInfrastructure
-      summary: returns metadatum
-      description: returns metadatum
-      operationId: getCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
+      summary: returns snapshots
+      description: returns snapshots
+      operationId: getCloudInfrastructureCloudRegionsCloudRegionSnapshots
       produces:
         - application/json
         - application/xml
@@ -4810,7 +5315,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/metadatum"
+              $ref: "#/getDefinitions/snapshots"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -4819,56 +5324,49 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
-        - name: image-id
-          in: path
-          description: Image id, expected to be unique across cloud region
-          required: true
-          type: string
-        - name: metaname
-          in: path
-          required: true
-          type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
+          example: __CLOUD-REGION-ID__
+        - name: snapshot-id
           in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+          description:
           required: false
           type: string
-        - name: image-name
+        - name: snapshot-name
           in: query
-          description: Image name
+          description:
           required: false
           type: string
         - name: application
           in: query
-          description: The application that the image instantiates.
+          description:
           required: false
           type: string
         - name: application-vendor
           in: query
-          description: The vendor of the application.
+          description:
           required: false
           type: string
         - name: application-version
           in: query
-          description: The version of the application.
+          description:
+          required: false
+          type: string
+        - name: prev-snapshot-id
+          in: query
+          description:
           required: false
           type: string
+  /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/relationship-list/relationship:
     put:
       tags:
         - CloudInfrastructure
-      summary: create or update an existing metadatum
-      description: create or update an existing metadatum
-      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
+      summary: see node definition for valid relationships
+      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageRelationshipListRelationship
       consumes:
         - application/json
         - application/xml
@@ -4884,26 +5382,204 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: image-id
           in: path
           description: Image id, expected to be unique across cloud region
           required: true
           type: string
+          example: __IMAGE-ID__
+        - name: body
+          in: body
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)
+          required: true
+          schema:
+            $ref: "#/definitions/relationship"
+    delete:
+      tags:
+        - CloudInfrastructure
+      summary: delete an existing relationship
+      description: delete an existing relationship
+      operationId: deleteCloudInfrastructureCloudRegionsCloudRegionImagesImageRelationshipListRelationship
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: image-id
+          in: path
+          description: Image id, expected to be unique across cloud region
+          required: true
+          type: string
+          example: __IMAGE-ID__
+  /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}/metadata/metadatum/{metaname}:
+    get:
+      tags:
+        - CloudInfrastructure
+      summary: returns metadatum
+      description: returns metadatum
+      operationId: getCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "200":
+          description: successful operation
+          schema:
+              $ref: "#/getDefinitions/metadatum"
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: image-id
+          in: path
+          description: Image id, expected to be unique across cloud region
+          required: true
+          type: string
+          example: __IMAGE-ID__
         - name: metaname
           in: path
           required: true
           type: string
+          example: __METANAME__
+    put:
+      tags:
+        - CloudInfrastructure
+      summary: create or update an existing metadatum
+      description: |
+        Create or update an existing metadatum.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: image-id
+          in: path
+          description: Image id, expected to be unique across cloud region
+          required: true
+          type: string
+          example: __IMAGE-ID__
+        - name: metaname
+          in: path
+          required: true
+          type: string
+          example: __METANAME__
         - name: body
           in: body
-          description: metadatum object that needs to be created or updated
+          description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum.json)
           required: true
           schema:
             $ref: "#/definitions/metadatum"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing metadatum
+      description: |
+        Update an existing metadatum
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionImagesImageMetadataMetadatum
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: image-id
+          in: path
+          description: Image id, expected to be unique across cloud region
+          required: true
+          type: string
+          example: __IMAGE-ID__
+        - name: metaname
+          in: path
+          required: true
+          type: string
+          example: __METANAME__
+        - name: body
+          in: body
+          description: metadatum object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/metadatum"
     delete:
       tags:
         - CloudInfrastructure
@@ -4925,20 +5601,24 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: image-id
           in: path
           description: Image id, expected to be unique across cloud region
           required: true
           type: string
+          example: __IMAGE-ID__
         - name: metaname
           in: path
           required: true
           type: string
+          example: __METANAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -4958,7 +5638,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/metadata"
+              $ref: "#/getDefinitions/metadata"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -4967,44 +5647,22 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: image-id
           in: path
           description: Image id, expected to be unique across cloud region
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: image-name
-          in: query
-          description: Image name
-          required: false
-          type: string
-        - name: application
-          in: query
-          description: The application that the image instantiates.
-          required: false
-          type: string
-        - name: application-vendor
-          in: query
-          description: The vendor of the application.
-          required: false
-          type: string
-        - name: application-version
+          example: __IMAGE-ID__
+        - name: metaname
           in: query
-          description: The version of the application.
+          description:
           required: false
           type: string
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/images/image/{image-id}:
@@ -5021,7 +5679,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/image"
+              $ref: "#/getDefinitions/image"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -5030,51 +5688,27 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: image-id
           in: path
           description: Image id, expected to be unique across cloud region
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: image-name
-          in: query
-          description: Image name
-          required: false
-          type: string
-        - name: application
-          in: query
-          description: The application that the image instantiates.
-          required: false
-          type: string
-        - name: application-vendor
-          in: query
-          description: The vendor of the application.
-          required: false
-          type: string
-        - name: application-version
-          in: query
-          description: The version of the application.
-          required: false
-          type: string
+          example: __IMAGE-ID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing image
-      description: create or update an existing image
+      description: |
+        Create or update an existing image.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionImagesImage
       consumes:
         - application/json
@@ -5091,22 +5725,76 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: image-id
           in: path
           description: Image id, expected to be unique across cloud region
           required: true
           type: string
+          example: __IMAGE-ID__
         - name: body
           in: body
-          description: image object that needs to be created or updated
+          description: image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionImagesImage.json)
           required: true
           schema:
             $ref: "#/definitions/image"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing image
+      description: |
+        Update an existing image
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionImagesImage
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: image-id
+          in: path
+          description: Image id, expected to be unique across cloud region
+          required: true
+          type: string
+          example: __IMAGE-ID__
+        - name: body
+          in: body
+          description: image object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/image"
     delete:
       tags:
         - CloudInfrastructure
@@ -5128,16 +5816,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: image-id
           in: path
           description: Image id, expected to be unique across cloud region
           required: true
           type: string
+          example: __IMAGE-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -5157,7 +5848,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/images"
+              $ref: "#/getDefinitions/images"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -5166,19 +5857,36 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
-        - name: cloud-type
+          example: __CLOUD-REGION-ID__
+        - name: image-id
           in: query
-          description: Type of the cloud (e.g., openstack)
+          description:
           required: false
           type: string
-        - name: owner-defined-type
+        - name: image-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: application
+          in: query
+          description:
+          required: false
+          type: string
+        - name: application-vendor
           in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+          description:
+          required: false
+          type: string
+        - name: application-version
+          in: query
+          description:
           required: false
           type: string
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}/relationship-list/relationship:
@@ -5202,19 +5910,22 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: switch-name
           in: path
           description: DVS switch name
           required: true
           type: string
+          example: __SWITCH-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -5239,16 +5950,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: switch-name
           in: path
           description: DVS switch name
           required: true
           type: string
+          example: __SWITCH-NAME__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/dvs-switches/dvs-switch/{switch-name}:
     get:
       tags:
@@ -5263,7 +5977,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/dvs-switch"
+              $ref: "#/getDefinitions/dvs-switch"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -5272,36 +5986,27 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: switch-name
           in: path
           description: DVS switch name
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: vcenter-url
-          in: query
-          description: URL used to reach the vcenter
-          required: false
-          type: string
+          example: __SWITCH-NAME__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing dvs-switch
-      description: create or update an existing dvs-switch
+      description: |
+        Create or update an existing dvs-switch.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch
       consumes:
         - application/json
@@ -5318,22 +6023,76 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: switch-name
           in: path
           description: DVS switch name
           required: true
           type: string
+          example: __SWITCH-NAME__
         - name: body
           in: body
-          description: dvs-switch object that needs to be created or updated
+          description: dvs-switch object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch.json)
           required: true
           schema:
             $ref: "#/definitions/dvs-switch"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing dvs-switch
+      description: |
+        Update an existing dvs-switch
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionDvsSwitchesDvsSwitch
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: switch-name
+          in: path
+          description: DVS switch name
+          required: true
+          type: string
+          example: __SWITCH-NAME__
+        - name: body
+          in: body
+          description: dvs-switch object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/dvs-switch"
     delete:
       tags:
         - CloudInfrastructure
@@ -5355,16 +6114,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: switch-name
           in: path
           description: DVS switch name
           required: true
           type: string
+          example: __SWITCH-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -5384,7 +6146,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/dvs-switches"
+              $ref: "#/getDefinitions/dvs-switches"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -5393,19 +6155,21 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
-        - name: cloud-type
+          example: __CLOUD-REGION-ID__
+        - name: switch-name
           in: query
-          description: Type of the cloud (e.g., openstack)
+          description:
           required: false
           type: string
-        - name: owner-defined-type
+        - name: vcenter-url
           in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+          description:
           required: false
           type: string
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}/relationship-list/relationship:
@@ -5429,19 +6193,22 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: network-uuid
           in: path
           description: UUID of the network. Unique across a cloud-region
           required: true
           type: string
+          example: __NETWORK-UUID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -5466,16 +6233,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: network-uuid
           in: path
           description: UUID of the network. Unique across a cloud-region
           required: true
           type: string
+          example: __NETWORK-UUID__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/oam-networks/oam-network/{network-uuid}:
     get:
       tags:
@@ -5490,7 +6260,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/oam-network"
+              $ref: "#/getDefinitions/oam-network"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -5499,42 +6269,27 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: network-uuid
           in: path
           description: UUID of the network. Unique across a cloud-region
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network.
-          required: false
-          type: string
-        - name: cvlan-tag
-          in: query
-          description: cvlan-id
-          required: false
-          type: integer
-          format: int64
+          example: __NETWORK-UUID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing oam-network
-      description: create or update an existing oam-network
+      description: |
+        Create or update an existing oam-network.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork
       consumes:
         - application/json
@@ -5551,22 +6306,76 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: network-uuid
           in: path
           description: UUID of the network. Unique across a cloud-region
           required: true
           type: string
+          example: __NETWORK-UUID__
         - name: body
           in: body
-          description: oam-network object that needs to be created or updated
+          description: oam-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork.json)
           required: true
           schema:
             $ref: "#/definitions/oam-network"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing oam-network
+      description: |
+        Update an existing oam-network
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionOamNetworksOamNetwork
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: network-uuid
+          in: path
+          description: UUID of the network. Unique across a cloud-region
+          required: true
+          type: string
+          example: __NETWORK-UUID__
+        - name: body
+          in: body
+          description: oam-network object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/oam-network"
     delete:
       tags:
         - CloudInfrastructure
@@ -5588,16 +6397,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: network-uuid
           in: path
           description: UUID of the network. Unique across a cloud-region
           required: true
           type: string
+          example: __NETWORK-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -5617,7 +6429,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/oam-networks"
+              $ref: "#/getDefinitions/oam-networks"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -5626,21 +6438,29 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
-        - name: cloud-type
+          example: __CLOUD-REGION-ID__
+        - name: network-uuid
           in: query
-          description: Type of the cloud (e.g., openstack)
+          description:
           required: false
           type: string
-        - name: owner-defined-type
+        - name: network-name
           in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+          description:
           required: false
           type: string
+        - name: cvlan-tag
+          in: query
+          description:
+          required: false
+          type: integer
+          format: int64
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}/relationship-list/relationship:
     put:
       tags:
@@ -5662,19 +6482,22 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: availability-zone-name
           in: path
           description: Name of the availability zone.  Unique across a cloud region
           required: true
           type: string
+          example: __AVAILABILITY-ZONE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -5699,16 +6522,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: availability-zone-name
           in: path
           description: Name of the availability zone.  Unique across a cloud region
           required: true
           type: string
+          example: __AVAILABILITY-ZONE-NAME__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/availability-zones/availability-zone/{availability-zone-name}:
     get:
       tags:
@@ -5723,7 +6549,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/availability-zone"
+              $ref: "#/getDefinitions/availability-zone"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -5732,31 +6558,27 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: availability-zone-name
           in: path
           description: Name of the availability zone.  Unique across a cloud region
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
+          example: __AVAILABILITY-ZONE-NAME__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing availability-zone
-      description: create or update an existing availability-zone
+      description: |
+        Create or update an existing availability-zone.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone
       consumes:
         - application/json
@@ -5773,22 +6595,76 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: availability-zone-name
           in: path
           description: Name of the availability zone.  Unique across a cloud region
           required: true
           type: string
+          example: __AVAILABILITY-ZONE-NAME__
         - name: body
           in: body
-          description: availability-zone object that needs to be created or updated
+          description: availability-zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone.json)
           required: true
           schema:
             $ref: "#/definitions/availability-zone"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing availability-zone
+      description: |
+        Update an existing availability-zone
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegionAvailabilityZonesAvailabilityZone
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: availability-zone-name
+          in: path
+          description: Name of the availability zone.  Unique across a cloud region
+          required: true
+          type: string
+          example: __AVAILABILITY-ZONE-NAME__
+        - name: body
+          in: body
+          description: availability-zone object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/availability-zone"
     delete:
       tags:
         - CloudInfrastructure
@@ -5810,16 +6686,19 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: availability-zone-name
           in: path
           description: Name of the availability zone.  Unique across a cloud region
           required: true
           type: string
+          example: __AVAILABILITY-ZONE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -5839,7 +6718,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/availability-zones"
+              $ref: "#/getDefinitions/availability-zones"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -5848,19 +6727,16 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
+          example: __CLOUD-REGION-ID__
+        - name: availability-zone-name
           in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+          description:
           required: false
           type: string
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}/relationship-list/relationship:
@@ -5884,14 +6760,16 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegion.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -5916,11 +6794,13 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
   /cloud-infrastructure/cloud-regions/cloud-region/{cloud-owner}/{cloud-region-id}:
     get:
       tags:
@@ -5935,7 +6815,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/cloud-region"
+              $ref: "#/getDefinitions/cloud-region"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -5944,26 +6824,21 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
-        - name: cloud-type
-          in: query
-          description: Type of the cloud (e.g., openstack)
-          required: false
-          type: string
-        - name: owner-defined-type
-          in: query
-          description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-          required: false
-          type: string
+          example: __CLOUD-REGION-ID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing cloud-region
-      description: create or update an existing cloud-region
+      description: |
+        Create or update an existing cloud-region.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureCloudRegionsCloudRegion
       consumes:
         - application/json
@@ -5980,17 +6855,64 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: body
           in: body
-          description: cloud-region object that needs to be created or updated
+          description: cloud-region object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureCloudRegionsCloudRegion.json)
           required: true
           schema:
             $ref: "#/definitions/cloud-region"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing cloud-region
+      description: |
+        Update an existing cloud-region
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureCloudRegionsCloudRegion
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: path
+          description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+          required: true
+          type: string
+          example: __CLOUD-OWNER__
+        - name: cloud-region-id
+          in: path
+          description: Identifier used by the vendor for the region. Second part of composite key
+          required: true
+          type: string
+          example: __CLOUD-REGION-ID__
+        - name: body
+          in: body
+          description: cloud-region object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/cloud-region"
     delete:
       tags:
         - CloudInfrastructure
@@ -6012,11 +6934,13 @@ paths:
           description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
           required: true
           type: string
+          example: __CLOUD-OWNER__
         - name: cloud-region-id
           in: path
           description: Identifier used by the vendor for the region. Second part of composite key
           required: true
           type: string
+          example: __CLOUD-REGION-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -6036,9 +6960,30 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/cloud-regions"
+              $ref: "#/getDefinitions/cloud-regions"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: cloud-owner
+          in: query
+          description:
+          required: false
+          type: string
+        - name: cloud-region-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: cloud-type
+          in: query
+          description:
+          required: false
+          type: string
+        - name: owner-defined-type
+          in: query
+          description:
+          required: false
+          type: string
   /cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}/relationship-list/relationship:
     put:
       tags:
@@ -6060,9 +7005,10 @@ paths:
           description: Unique name of network profile.
           required: true
           type: string
+          example: __NM-PROFILE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureNetworkProfilesNetworkProfile.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -6087,6 +7033,7 @@ paths:
           description: Unique name of network profile.
           required: true
           type: string
+          example: __NM-PROFILE-NAME__
   /cloud-infrastructure/network-profiles/network-profile/{nm-profile-name}:
     get:
       tags:
@@ -6101,7 +7048,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/network-profile"
+              $ref: "#/getDefinitions/network-profile"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -6110,11 +7057,15 @@ paths:
           description: Unique name of network profile.
           required: true
           type: string
+          example: __NM-PROFILE-NAME__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing network-profile
-      description: create or update an existing network-profile
+      description: |
+        Create or update an existing network-profile.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureNetworkProfilesNetworkProfile
       consumes:
         - application/json
@@ -6131,12 +7082,52 @@ paths:
           description: Unique name of network profile.
           required: true
           type: string
+          example: __NM-PROFILE-NAME__
         - name: body
           in: body
-          description: network-profile object that needs to be created or updated
+          description: network-profile object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureNetworkProfilesNetworkProfile.json)
           required: true
           schema:
             $ref: "#/definitions/network-profile"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing network-profile
+      description: |
+        Update an existing network-profile
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureNetworkProfilesNetworkProfile
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: nm-profile-name
+          in: path
+          description: Unique name of network profile.
+          required: true
+          type: string
+          example: __NM-PROFILE-NAME__
+        - name: body
+          in: body
+          description: network-profile object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/network-profile"
     delete:
       tags:
         - CloudInfrastructure
@@ -6158,6 +7149,7 @@ paths:
           description: Unique name of network profile.
           required: true
           type: string
+          example: __NM-PROFILE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -6177,9 +7169,15 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/network-profiles"
+              $ref: "#/getDefinitions/network-profiles"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: nm-profile-name
+          in: query
+          description:
+          required: false
+          type: string
   /cloud-infrastructure/pservers/pserver/{hostname}/relationship-list/relationship:
     put:
       tags:
@@ -6201,9 +7199,10 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserver.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -6228,6 +7227,7 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
   /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
     put:
       tags:
@@ -6249,14 +7249,16 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -6281,11 +7283,13 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
     put:
       tags:
@@ -6307,24 +7311,28 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -6349,21 +7357,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
   /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -6385,29 +7397,34 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -6432,26 +7449,31 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -6466,7 +7488,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -6475,97 +7497,39 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
@@ -6582,38 +7546,54 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv4-address-list"
-    delete:
+    patch:
       tags:
         - CloudInfrastructure
-      summary: delete an existing l3-interface-ipv4-address-list
-      description: delete an existing l3-interface-ipv4-address-list
-      operationId: deleteCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -6629,37 +7609,43 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: resource-version
-          in: query
-          description: resource-version for concurrency
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be updated.
           required: true
-          type: string
-  /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}/relationship-list/relationship:
-    put:
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
+    delete:
       tags:
         - CloudInfrastructure
-      summary: see node definition for valid relationships
-      operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressListRelationshipListRelationship
+      summary: delete an existing l3-interface-ipv4-address-list
+      description: delete an existing l3-interface-ipv4-address-list
+      operationId: deleteCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -6675,38 +7661,42 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
-        - name: l3-interface-ipv6-address
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: body
-          in: body
-          description: relationship object that needs to be created or updated
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: resource-version
+          in: query
+          description: resource-version for concurrency
           required: true
-          schema:
-            $ref: "#/definitions/relationship"
-    delete:
+          type: string
+  /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}/relationship-list/relationship:
+    put:
       tags:
         - CloudInfrastructure
-      summary: delete an existing relationship
-      description: delete an existing relationship
-      operationId: deleteCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressListRelationshipListRelationship
+      summary: see node definition for valid relationships
+      operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressListRelationshipListRelationship
       consumes:
         - application/json
         - application/xml
@@ -6722,26 +7712,83 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/relationship"
+    delete:
+      tags:
+        - CloudInfrastructure
+      summary: delete an existing relationship
+      description: delete an existing relationship
+      operationId: deleteCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressListRelationshipListRelationship
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -6756,7 +7803,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -6765,98 +7812,103 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+    put:
+      tags:
+        - CloudInfrastructure
+      summary: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
       tags:
         - CloudInfrastructure
-      summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
-      operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
       consumes:
         - application/json
         - application/xml
@@ -6872,32 +7924,37 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv6-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - CloudInfrastructure
@@ -6919,26 +7976,31 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -6958,7 +8020,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlan"
+              $ref: "#/getDefinitions/vlan"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -6967,76 +8029,33 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
+          example: __VLAN-INTERFACE__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing vlan
-      description: create or update an existing vlan
+      description: |
+        Create or update an existing vlan.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
       consumes:
         - application/json
@@ -7053,27 +8072,88 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: vlan object that needs to be created or updated
+          description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/vlan"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing vlan
+      description: |
+        Update an existing vlan
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: body
+          in: body
+          description: vlan object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vlan"
     delete:
       tags:
         - CloudInfrastructure
@@ -7095,21 +8175,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -7129,7 +8213,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlans"
+              $ref: "#/getDefinitions/vlans"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -7138,53 +8222,33 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vlan-id-inner
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: integer
+          format: int64
+        - name: vpn-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}/relationship-list/relationship:
@@ -7208,24 +8272,28 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -7250,21 +8318,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
   /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
     get:
       tags:
@@ -7279,7 +8351,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vf"
+              $ref: "#/getDefinitions/sriov-vf"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -7288,85 +8360,33 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vf-vlan-filter
-          in: query
-          description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
-          required: false
-          type: string
-        - name: vf-mac-filter
-          in: query
-          description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
-          required: false
-          type: string
-        - name: vf-vlan-strip
-          in: query
-          description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
-          required: false
-          type: boolean
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface
-          required: false
-          type: string
+          example: __PCI-ID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing sriov-vf
-      description: create or update an existing sriov-vf
+      description: |
+        Create or update an existing sriov-vf.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
       consumes:
         - application/json
@@ -7383,33 +8403,48 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: sriov-vf object that needs to be created or updated
+          description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/sriov-vf"
-    delete:
+    patch:
       tags:
         - CloudInfrastructure
-      summary: delete an existing sriov-vf
-      description: delete an existing sriov-vf
-      operationId: deleteCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+      summary: update an existing sriov-vf
+      description: |
+        Update an existing sriov-vf
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
       consumes:
         - application/json
         - application/xml
@@ -7425,21 +8460,71 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
+        - name: body
+          in: body
+          description: sriov-vf object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/sriov-vf"
+    delete:
+      tags:
+        - CloudInfrastructure
+      summary: delete an existing sriov-vf
+      description: delete an existing sriov-vf
+      operationId: deleteCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: pci-id
+          in: path
+          description: PCI ID used to identify the sriov-vf
+          required: true
+          type: string
+          example: __PCI-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -7459,7 +8544,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vfs"
+              $ref: "#/getDefinitions/sriov-vfs"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -7468,53 +8553,42 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
+          example: __INTERFACE-NAME__
+        - name: pci-id
           in: query
-          description: alternative pserver name
+          description:
           required: false
           type: string
-        - name: prov-status
+        - name: vf-vlan-filter
           in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
+          description:
           required: false
           type: string
-        - name: interface-id
+        - name: vf-mac-filter
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vf-vlan-strip
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: boolean
+        - name: neutron-network-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/relationship-list/relationship:
@@ -7538,19 +8612,22 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -7575,16 +8652,19 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -7606,24 +8686,28 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -7648,21 +8732,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -7677,7 +8765,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -7686,81 +8774,33 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
       consumes:
         - application/json
@@ -7777,27 +8817,88 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - CloudInfrastructure
@@ -7819,21 +8920,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -7860,24 +8965,28 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -7902,21 +9011,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -7931,7 +9044,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -7940,81 +9053,33 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -8031,27 +9096,88 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - CloudInfrastructure
@@ -8073,21 +9199,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -8107,7 +9237,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interface"
+              $ref: "#/getDefinitions/l-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -8116,60 +9246,27 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing l-interface
-      description: create or update an existing l-interface
+      description: |
+        Create or update an existing l-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface
       consumes:
         - application/json
@@ -8186,28 +9283,42 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: l-interface object that needs to be created or updated
+          description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/l-interface"
-    delete:
+    patch:
       tags:
         - CloudInfrastructure
-      summary: delete an existing l-interface
-      description: delete an existing l-interface
-      operationId: deleteCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface
+      summary: update an existing l-interface
+      description: |
+        Update an existing l-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface
       consumes:
         - application/json
         - application/xml
@@ -8223,16 +9334,59 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: l-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l-interface"
+    delete:
+      tags:
+        - CloudInfrastructure
+      summary: delete an existing l-interface
+      description: delete an existing l-interface
+      operationId: deleteCloudInfrastructurePserversPserverPInterfacesPInterfaceLInterfacesLInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -8252,7 +9406,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interfaces"
+              $ref: "#/getDefinitions/l-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -8261,33 +9415,31 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
-        - name: inv-status
+          example: __INTERFACE-NAME__
+        - name: interface-name
           in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+          description:
           required: false
           type: string
-        - name: pserver-id
+        - name: interface-id
           in: query
-          description: ID of Pserver
+          description:
           required: false
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
+        - name: macaddr
           in: query
-          description: alternative pserver name
+          description:
           required: false
           type: string
-        - name: prov-status
+        - name: network-name
           in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
+          description:
           required: false
           type: string
   /cloud-infrastructure/pservers/pserver/{hostname}/p-interfaces/p-interface/{interface-name}:
@@ -8304,7 +9456,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/p-interface"
+              $ref: "#/getDefinitions/p-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -8313,40 +9465,21 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing p-interface
-      description: create or update an existing p-interface
+      description: |
+        Create or update an existing p-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverPInterfacesPInterface
       consumes:
         - application/json
@@ -8363,17 +9496,64 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: p-interface object that needs to be created or updated
+          description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverPInterfacesPInterface.json)
           required: true
           schema:
             $ref: "#/definitions/p-interface"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing p-interface
+      description: |
+        Update an existing p-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverPInterfacesPInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: p-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/p-interface"
     delete:
       tags:
         - CloudInfrastructure
@@ -8395,11 +9575,13 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -8419,7 +9601,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/p-interfaces"
+              $ref: "#/getDefinitions/p-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -8428,23 +9610,15 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
+          example: __HOSTNAME__
+        - name: interface-name
           in: query
-          description: ID of Pserver
+          description:
           required: false
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
+        - name: prov-status
           in: query
-          description: alternative pserver name
+          description:
           required: false
           type: string
   /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/relationship-list/relationship:
@@ -8468,14 +9642,16 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -8500,11 +9676,13 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
     put:
       tags:
@@ -8526,24 +9704,28 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -8568,21 +9750,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
   /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -8604,29 +9790,34 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -8651,26 +9842,31 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -8685,7 +9881,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -8694,103 +9890,103 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+    put:
+      tags:
+        - CloudInfrastructure
+      summary: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
       tags:
         - CloudInfrastructure
-      summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
-      operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -8806,32 +10002,37 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv4-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - CloudInfrastructure
@@ -8853,26 +10054,31 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -8899,29 +10105,34 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -8946,26 +10157,31 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -8980,7 +10196,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -8989,102 +10205,39 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -9101,32 +10254,100 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - CloudInfrastructure
@@ -9148,26 +10369,31 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -9187,7 +10413,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlan"
+              $ref: "#/getDefinitions/vlan"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -9196,81 +10422,33 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
+          example: __VLAN-INTERFACE__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing vlan
-      description: create or update an existing vlan
+      description: |
+        Create or update an existing vlan.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
       consumes:
         - application/json
@@ -9287,27 +10465,88 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: vlan object that needs to be created or updated
+          description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/vlan"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing vlan
+      description: |
+        Update an existing vlan
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: body
+          in: body
+          description: vlan object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vlan"
     delete:
       tags:
         - CloudInfrastructure
@@ -9329,21 +10568,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -9363,7 +10606,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlans"
+              $ref: "#/getDefinitions/vlans"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -9372,58 +10615,33 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vlan-id-inner
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: integer
+          format: int64
+        - name: vpn-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}/relationship-list/relationship:
@@ -9447,24 +10665,28 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -9489,21 +10711,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
   /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
     get:
       tags:
@@ -9518,7 +10744,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vf"
+              $ref: "#/getDefinitions/sriov-vf"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -9527,90 +10753,33 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vf-vlan-filter
-          in: query
-          description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
-          required: false
-          type: string
-        - name: vf-mac-filter
-          in: query
-          description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
-          required: false
-          type: string
-        - name: vf-vlan-strip
-          in: query
-          description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
-          required: false
-          type: boolean
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface
-          required: false
-          type: string
+          example: __PCI-ID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing sriov-vf
-      description: create or update an existing sriov-vf
+      description: |
+        Create or update an existing sriov-vf.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
       consumes:
         - application/json
@@ -9627,27 +10796,88 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: sriov-vf object that needs to be created or updated
+          description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/sriov-vf"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing sriov-vf
+      description: |
+        Update an existing sriov-vf
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: pci-id
+          in: path
+          description: PCI ID used to identify the sriov-vf
+          required: true
+          type: string
+          example: __PCI-ID__
+        - name: body
+          in: body
+          description: sriov-vf object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/sriov-vf"
     delete:
       tags:
         - CloudInfrastructure
@@ -9669,21 +10899,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -9703,7 +10937,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vfs"
+              $ref: "#/getDefinitions/sriov-vfs"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -9712,58 +10946,42 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: pci-id
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: interface-role
+        - name: vf-vlan-filter
           in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+          description:
           required: false
           type: string
-        - name: interface-id
+        - name: vf-mac-filter
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vf-vlan-strip
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: boolean
+        - name: neutron-network-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/relationship-list/relationship:
@@ -9787,19 +11005,22 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -9824,16 +11045,19 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -9855,24 +11079,28 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -9897,21 +11125,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -9926,7 +11158,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -9935,86 +11167,33 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
       consumes:
         - application/json
@@ -10031,27 +11210,88 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - CloudInfrastructure
@@ -10073,21 +11313,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -10114,24 +11358,28 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -10156,21 +11404,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -10185,7 +11437,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -10194,86 +11446,33 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -10290,27 +11489,88 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - CloudInfrastructure
@@ -10332,21 +11592,25 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -10366,7 +11630,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interface"
+              $ref: "#/getDefinitions/l-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -10375,65 +11639,27 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing l-interface
-      description: create or update an existing l-interface
+      description: |
+        Create or update an existing l-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface
       consumes:
         - application/json
@@ -10450,22 +11676,76 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: l-interface object that needs to be created or updated
+          description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/l-interface"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing l-interface
+      description: |
+        Update an existing l-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterfaceLInterfacesLInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: l-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l-interface"
     delete:
       tags:
         - CloudInfrastructure
@@ -10487,16 +11767,19 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -10516,7 +11799,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interfaces"
+              $ref: "#/getDefinitions/l-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -10525,38 +11808,31 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
+          example: __INTERFACE-NAME__
+        - name: interface-name
           in: query
-          description: ID of Pserver
+          description:
           required: false
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
+        - name: interface-id
           in: query
-          description: alternative pserver name
+          description:
           required: false
           type: string
-        - name: interface-id
+        - name: macaddr
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: interface-role
+        - name: network-name
           in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+          description:
           required: false
           type: string
   /cloud-infrastructure/pservers/pserver/{hostname}/lag-interfaces/lag-interface/{interface-name}:
@@ -10573,7 +11849,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/lag-interface"
+              $ref: "#/getDefinitions/lag-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -10582,45 +11858,21 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing lag-interface
-      description: create or update an existing lag-interface
+      description: |
+        Create or update an existing lag-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserverLagInterfacesLagInterface
       consumes:
         - application/json
@@ -10637,17 +11889,64 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: lag-interface object that needs to be created or updated
+          description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserverLagInterfacesLagInterface.json)
           required: true
           schema:
             $ref: "#/definitions/lag-interface"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing lag-interface
+      description: |
+        Update an existing lag-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserverLagInterfacesLagInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: lag-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/lag-interface"
     delete:
       tags:
         - CloudInfrastructure
@@ -10669,11 +11968,13 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -10693,7 +11994,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/lag-interfaces"
+              $ref: "#/getDefinitions/lag-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -10702,23 +12003,20 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
-        - name: inv-status
+          example: __HOSTNAME__
+        - name: interface-name
           in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+          description:
           required: false
           type: string
-        - name: pserver-id
+        - name: interface-id
           in: query
-          description: ID of Pserver
+          description:
           required: false
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
+        - name: interface-role
           in: query
-          description: alternative pserver name
+          description:
           required: false
           type: string
   /cloud-infrastructure/pservers/pserver/{hostname}:
@@ -10735,7 +12033,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/pserver"
+              $ref: "#/getDefinitions/pserver"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -10744,30 +12042,15 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: pserver-id
-          in: query
-          description: ID of Pserver
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: pserver-name2
-          in: query
-          description: alternative pserver name
-          required: false
-          type: string
+          example: __HOSTNAME__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing pserver
-      description: create or update an existing pserver
+      description: |
+        Create or update an existing pserver.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructurePserversPserver
       consumes:
         - application/json
@@ -10784,12 +12067,52 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: body
           in: body
-          description: pserver object that needs to be created or updated
+          description: pserver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructurePserversPserver.json)
           required: true
           schema:
             $ref: "#/definitions/pserver"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing pserver
+      description: |
+        Update an existing pserver
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructurePserversPserver
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: path
+          description: Value from executing hostname on the compute node.
+          required: true
+          type: string
+          example: __HOSTNAME__
+        - name: body
+          in: body
+          description: pserver object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/pserver"
     delete:
       tags:
         - CloudInfrastructure
@@ -10811,6 +12134,7 @@ paths:
           description: Value from executing hostname on the compute node.
           required: true
           type: string
+          example: __HOSTNAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -10830,9 +12154,35 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/pservers"
+              $ref: "#/getDefinitions/pservers"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: hostname
+          in: query
+          description:
+          required: false
+          type: string
+        - name: inv-status
+          in: query
+          description:
+          required: false
+          type: string
+        - name: pserver-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: in-maint
+          in: query
+          description:
+          required: false
+          type: boolean
+        - name: pserver-name2
+          in: query
+          description:
+          required: false
+          type: string
   /cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}/relationship-list/relationship:
     put:
       tags:
@@ -10854,9 +12204,10 @@ paths:
           description: Unique ID of the vdc
           required: true
           type: string
+          example: __VDC-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -10881,6 +12232,7 @@ paths:
           description: Unique ID of the vdc
           required: true
           type: string
+          example: __VDC-ID__
   /cloud-infrastructure/virtual-data-centers/virtual-data-center/{vdc-id}:
     get:
       tags:
@@ -10895,7 +12247,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/virtual-data-center"
+              $ref: "#/getDefinitions/virtual-data-center"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -10904,16 +12256,15 @@ paths:
           description: Unique ID of the vdc
           required: true
           type: string
-        - name: vdc-name
-          in: query
-          description: Name of the virtual data center
-          required: false
-          type: string
+          example: __VDC-ID__
     put:
       tags:
         - CloudInfrastructure
       summary: create or update an existing virtual-data-center
-      description: create or update an existing virtual-data-center
+      description: |
+        Create or update an existing virtual-data-center.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateCloudInfrastructureVirtualDataCentersVirtualDataCenter
       consumes:
         - application/json
@@ -10930,12 +12281,52 @@ paths:
           description: Unique ID of the vdc
           required: true
           type: string
+          example: __VDC-ID__
         - name: body
           in: body
-          description: virtual-data-center object that needs to be created or updated
+          description: virtual-data-center object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/CloudInfrastructureVirtualDataCentersVirtualDataCenter.json)
           required: true
           schema:
             $ref: "#/definitions/virtual-data-center"
+    patch:
+      tags:
+        - CloudInfrastructure
+      summary: update an existing virtual-data-center
+      description: |
+        Update an existing virtual-data-center
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateCloudInfrastructureVirtualDataCentersVirtualDataCenter
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vdc-id
+          in: path
+          description: Unique ID of the vdc
+          required: true
+          type: string
+          example: __VDC-ID__
+        - name: body
+          in: body
+          description: virtual-data-center object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/virtual-data-center"
     delete:
       tags:
         - CloudInfrastructure
@@ -10957,6 +12348,7 @@ paths:
           description: Unique ID of the vdc
           required: true
           type: string
+          example: __VDC-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -10976,9 +12368,20 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/virtual-data-centers"
+              $ref: "#/getDefinitions/virtual-data-centers"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vdc-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vdc-name
+          in: query
+          description:
+          required: false
+          type: string
   /business/connectors/connector/{resource-instance-id}/relationship-list/relationship:
     put:
       tags:
@@ -11000,9 +12403,10 @@ paths:
           description: Unique id of resource instance.
           required: true
           type: string
+          example: __RESOURCE-INSTANCE-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessConnectorsConnector.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -11027,6 +12431,7 @@ paths:
           description: Unique id of resource instance.
           required: true
           type: string
+          example: __RESOURCE-INSTANCE-ID__
   /business/connectors/connector/{resource-instance-id}/metadata/metadatum/{metaname}:
     get:
       tags:
@@ -11041,7 +12446,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/metadatum"
+              $ref: "#/getDefinitions/metadatum"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -11050,35 +12455,20 @@ paths:
           description: Unique id of resource instance.
           required: true
           type: string
+          example: __RESOURCE-INSTANCE-ID__
         - name: metaname
           in: path
           required: true
           type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
+          example: __METANAME__
     put:
       tags:
         - Business
       summary: create or update an existing metadatum
-      description: create or update an existing metadatum
+      description: |
+        Create or update an existing metadatum.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateBusinessConnectorsConnectorMetadataMetadatum
       consumes:
         - application/json
@@ -11095,16 +12485,62 @@ paths:
           description: Unique id of resource instance.
           required: true
           type: string
+          example: __RESOURCE-INSTANCE-ID__
         - name: metaname
           in: path
           required: true
           type: string
+          example: __METANAME__
         - name: body
           in: body
-          description: metadatum object that needs to be created or updated
+          description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessConnectorsConnectorMetadataMetadatum.json)
           required: true
           schema:
             $ref: "#/definitions/metadatum"
+    patch:
+      tags:
+        - Business
+      summary: update an existing metadatum
+      description: |
+        Update an existing metadatum
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateBusinessConnectorsConnectorMetadataMetadatum
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: resource-instance-id
+          in: path
+          description: Unique id of resource instance.
+          required: true
+          type: string
+          example: __RESOURCE-INSTANCE-ID__
+        - name: metaname
+          in: path
+          required: true
+          type: string
+          example: __METANAME__
+        - name: body
+          in: body
+          description: metadatum object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/metadatum"
     delete:
       tags:
         - Business
@@ -11126,10 +12562,12 @@ paths:
           description: Unique id of resource instance.
           required: true
           type: string
+          example: __RESOURCE-INSTANCE-ID__
         - name: metaname
           in: path
           required: true
           type: string
+          example: __METANAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -11149,7 +12587,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/metadata"
+              $ref: "#/getDefinitions/metadata"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -11158,24 +12596,10 @@ paths:
           description: Unique id of resource instance.
           required: true
           type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
+          example: __RESOURCE-INSTANCE-ID__
+        - name: metaname
           in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+          description:
           required: false
           type: string
   /business/connectors/connector/{resource-instance-id}:
@@ -11192,7 +12616,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/connector"
+              $ref: "#/getDefinitions/connector"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -11201,31 +12625,15 @@ paths:
           description: Unique id of resource instance.
           required: true
           type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
+          example: __RESOURCE-INSTANCE-ID__
     put:
       tags:
         - Business
       summary: create or update an existing connector
-      description: create or update an existing connector
+      description: |
+        Create or update an existing connector.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateBusinessConnectorsConnector
       consumes:
         - application/json
@@ -11242,12 +12650,52 @@ paths:
           description: Unique id of resource instance.
           required: true
           type: string
+          example: __RESOURCE-INSTANCE-ID__
         - name: body
           in: body
-          description: connector object that needs to be created or updated
+          description: connector object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessConnectorsConnector.json)
           required: true
           schema:
             $ref: "#/definitions/connector"
+    patch:
+      tags:
+        - Business
+      summary: update an existing connector
+      description: |
+        Update an existing connector
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateBusinessConnectorsConnector
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: resource-instance-id
+          in: path
+          description: Unique id of resource instance.
+          required: true
+          type: string
+          example: __RESOURCE-INSTANCE-ID__
+        - name: body
+          in: body
+          description: connector object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/connector"
     delete:
       tags:
         - Business
@@ -11269,6 +12717,7 @@ paths:
           description: Unique id of resource instance.
           required: true
           type: string
+          example: __RESOURCE-INSTANCE-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -11288,9 +12737,35 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/connectors"
+              $ref: "#/getDefinitions/connectors"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: resource-instance-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: model-invariant-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: model-version-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: widget-model-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: widget-model-version
+          in: query
+          description:
+          required: false
+          type: string
   /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/relationship-list/relationship:
     put:
       tags:
@@ -11312,19 +12787,22 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -11349,16 +12827,19 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
   /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/metadata/metadatum/{metaname}:
     get:
       tags:
@@ -11373,7 +12854,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/metadatum"
+              $ref: "#/getDefinitions/metadatum"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -11382,70 +12863,32 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: metaname
           in: path
           required: true
           type: string
-        - name: subscriber-name
-          in: query
-          description: Subscriber name, an alternate way to retrieve a customer.
-          required: false
-          type: string
-        - name: subscriber-type
-          in: query
-          description: Subscriber type, a way to provide VID with only the INFRA customers.
-          required: false
-          type: string
-        - name: service-instance-name
-          in: query
-          description: This field will store a name assigned to the service-instance.
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: service-instance-location-id
-          in: query
-          description: An identifier that customers assign to the location where this service is being used.
-          required: false
-          type: string
-        - name: orchestration-status
-          in: query
-          description: Orchestration status of this service.
-          required: false
-          type: string
+          example: __METANAME__
     put:
       tags:
         - Business
       summary: create or update an existing metadatum
-      description: create or update an existing metadatum
+      description: |
+        Create or update an existing metadatum.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum
       consumes:
         - application/json
@@ -11462,26 +12905,86 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: metaname
           in: path
           required: true
           type: string
+          example: __METANAME__
         - name: body
           in: body
-          description: metadatum object that needs to be created or updated
+          description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum.json)
           required: true
           schema:
             $ref: "#/definitions/metadatum"
+    patch:
+      tags:
+        - Business
+      summary: update an existing metadatum
+      description: |
+        Update an existing metadatum
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceMetadataMetadatum
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: global-customer-id
+          in: path
+          description: Global customer id used across ECOMP to uniquely identify customer.
+          required: true
+          type: string
+          example: __GLOBAL-CUSTOMER-ID__
+        - name: service-type
+          in: path
+          description: Value defined by orchestration to identify this service across ECOMP.
+          required: true
+          type: string
+          example: __SERVICE-TYPE__
+        - name: service-instance-id
+          in: path
+          description: Uniquely identifies this instance of a service
+          required: true
+          type: string
+          example: __SERVICE-INSTANCE-ID__
+        - name: metaname
+          in: path
+          required: true
+          type: string
+          example: __METANAME__
+        - name: body
+          in: body
+          description: metadatum object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/metadatum"
     delete:
       tags:
         - Business
@@ -11503,20 +13006,24 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: metaname
           in: path
           required: true
           type: string
+          example: __METANAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -11536,7 +13043,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/metadata"
+              $ref: "#/getDefinitions/metadata"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -11545,59 +13052,22 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
-        - name: subscriber-name
-          in: query
-          description: Subscriber name, an alternate way to retrieve a customer.
-          required: false
-          type: string
-        - name: subscriber-type
-          in: query
-          description: Subscriber type, a way to provide VID with only the INFRA customers.
-          required: false
-          type: string
-        - name: service-instance-name
-          in: query
-          description: This field will store a name assigned to the service-instance.
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: service-instance-location-id
-          in: query
-          description: An identifier that customers assign to the location where this service is being used.
-          required: false
-          type: string
-        - name: orchestration-status
+          example: __SERVICE-INSTANCE-ID__
+        - name: metaname
           in: query
-          description: Orchestration status of this service.
+          description:
           required: false
           type: string
   /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}/relationship-list/relationship:
@@ -11621,29 +13091,34 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -11668,26 +13143,31 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
   /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/tunnel-xconnects/tunnel-xconnect/{id}:
     get:
       tags:
@@ -11702,7 +13182,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/tunnel-xconnect"
+              $ref: "#/getDefinitions/tunnel-xconnect"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -11711,97 +13191,103 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
-        - name: subscriber-name
-          in: query
-          description: Subscriber name, an alternate way to retrieve a customer.
-          required: false
-          type: string
-        - name: subscriber-type
-          in: query
-          description: Subscriber type, a way to provide VID with only the INFRA customers.
-          required: false
-          type: string
-        - name: service-instance-name
-          in: query
-          description: This field will store a name assigned to the service-instance.
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: service-instance-location-id
-          in: query
-          description: An identifier that customers assign to the location where this service is being used.
-          required: false
-          type: string
-        - name: orchestration-status
-          in: query
-          description: Orchestration status of this service.
-          required: false
+          example: __ID__
+    put:
+      tags:
+        - Business
+      summary: create or update an existing tunnel-xconnect
+      description: |
+        Create or update an existing tunnel-xconnect.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: global-customer-id
+          in: path
+          description: Global customer id used across ECOMP to uniquely identify customer.
+          required: true
           type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
+          example: __GLOBAL-CUSTOMER-ID__
+        - name: service-type
+          in: path
+          description: Value defined by orchestration to identify this service across ECOMP.
+          required: true
           type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
+          example: __SERVICE-TYPE__
+        - name: service-instance-id
+          in: path
+          description: Uniquely identifies this instance of a service
+          required: true
           type: string
-        - name: type
-          in: query
-          description: Generic description of the type of allotted resource.
-          required: false
+          example: __SERVICE-INSTANCE-ID__
+        - name: id
+          in: path
+          description: Allotted Resource id UUID assigned to this instance.
+          required: true
           type: string
-        - name: role
-          in: query
-          description: role in the network that this resource will be providing.
-          required: false
+          example: __ID__
+        - name: id
+          in: path
+          description: Allotted Resource id UUID assigned to this instance.
+          required: true
           type: string
-    put:
+          example: __ID__
+        - name: body
+          in: body
+          description: tunnel-xconnect object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect.json)
+          required: true
+          schema:
+            $ref: "#/definitions/tunnel-xconnect"
+    patch:
       tags:
         - Business
-      summary: create or update an existing tunnel-xconnect
-      description: create or update an existing tunnel-xconnect
-      operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect
+      summary: update an existing tunnel-xconnect
+      description: |
+        Update an existing tunnel-xconnect
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResourceTunnelXconnectsTunnelXconnect
       consumes:
         - application/json
         - application/xml
@@ -11817,32 +13303,37 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: body
           in: body
-          description: tunnel-xconnect object that needs to be created or updated
+          description: tunnel-xconnect object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/tunnel-xconnect"
+            $ref: "#/patchDefinitions/tunnel-xconnect"
     delete:
       tags:
         - Business
@@ -11864,26 +13355,31 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -11903,7 +13399,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/tunnel-xconnects"
+              $ref: "#/getDefinitions/tunnel-xconnects"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -11912,84 +13408,28 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
-        - name: subscriber-name
-          in: query
-          description: Subscriber name, an alternate way to retrieve a customer.
-          required: false
-          type: string
-        - name: subscriber-type
-          in: query
-          description: Subscriber type, a way to provide VID with only the INFRA customers.
-          required: false
-          type: string
-        - name: service-instance-name
-          in: query
-          description: This field will store a name assigned to the service-instance.
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: service-instance-location-id
-          in: query
-          description: An identifier that customers assign to the location where this service is being used.
-          required: false
-          type: string
-        - name: orchestration-status
-          in: query
-          description: Orchestration status of this service.
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: type
-          in: query
-          description: Generic description of the type of allotted resource.
-          required: false
-          type: string
-        - name: role
+          example: __ID__
+        - name: id
           in: query
-          description: role in the network that this resource will be providing.
+          description:
           required: false
           type: string
   /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}/relationship-list/relationship:
@@ -12013,24 +13453,28 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -12055,21 +13499,25 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
   /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}/allotted-resources/allotted-resource/{id}:
     get:
       tags:
@@ -12084,7 +13532,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/allotted-resource"
+              $ref: "#/getDefinitions/allotted-resource"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -12093,91 +13541,33 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
-        - name: subscriber-name
-          in: query
-          description: Subscriber name, an alternate way to retrieve a customer.
-          required: false
-          type: string
-        - name: subscriber-type
-          in: query
-          description: Subscriber type, a way to provide VID with only the INFRA customers.
-          required: false
-          type: string
-        - name: service-instance-name
-          in: query
-          description: This field will store a name assigned to the service-instance.
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: service-instance-location-id
-          in: query
-          description: An identifier that customers assign to the location where this service is being used.
-          required: false
-          type: string
-        - name: orchestration-status
-          in: query
-          description: Orchestration status of this service.
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: type
-          in: query
-          description: Generic description of the type of allotted resource.
-          required: false
-          type: string
-        - name: role
-          in: query
-          description: role in the network that this resource will be providing.
-          required: false
-          type: string
+          example: __ID__
     put:
       tags:
         - Business
       summary: create or update an existing allotted-resource
-      description: create or update an existing allotted-resource
+      description: |
+        Create or update an existing allotted-resource.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource
       consumes:
         - application/json
@@ -12194,27 +13584,88 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: body
           in: body
-          description: allotted-resource object that needs to be created or updated
+          description: allotted-resource object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource.json)
           required: true
           schema:
             $ref: "#/definitions/allotted-resource"
+    patch:
+      tags:
+        - Business
+      summary: update an existing allotted-resource
+      description: |
+        Update an existing allotted-resource
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstanceAllottedResourcesAllottedResource
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: global-customer-id
+          in: path
+          description: Global customer id used across ECOMP to uniquely identify customer.
+          required: true
+          type: string
+          example: __GLOBAL-CUSTOMER-ID__
+        - name: service-type
+          in: path
+          description: Value defined by orchestration to identify this service across ECOMP.
+          required: true
+          type: string
+          example: __SERVICE-TYPE__
+        - name: service-instance-id
+          in: path
+          description: Uniquely identifies this instance of a service
+          required: true
+          type: string
+          example: __SERVICE-INSTANCE-ID__
+        - name: id
+          in: path
+          description: Allotted Resource id UUID assigned to this instance.
+          required: true
+          type: string
+          example: __ID__
+        - name: body
+          in: body
+          description: allotted-resource object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/allotted-resource"
     delete:
       tags:
         - Business
@@ -12236,21 +13687,25 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: id
           in: path
           description: Allotted Resource id UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -12270,7 +13725,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/allotted-resources"
+              $ref: "#/getDefinitions/allotted-resources"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -12279,59 +13734,42 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
-        - name: subscriber-name
-          in: query
-          description: Subscriber name, an alternate way to retrieve a customer.
-          required: false
-          type: string
-        - name: subscriber-type
-          in: query
-          description: Subscriber type, a way to provide VID with only the INFRA customers.
-          required: false
-          type: string
-        - name: service-instance-name
+          example: __SERVICE-INSTANCE-ID__
+        - name: id
           in: query
-          description: This field will store a name assigned to the service-instance.
+          description:
           required: false
           type: string
         - name: model-invariant-id
           in: query
-          description: the ASDC model id for this resource or service model.
+          description:
           required: false
           type: string
         - name: model-version-id
           in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+          description:
           required: false
           type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: service-instance-location-id
+        - name: type
           in: query
-          description: An identifier that customers assign to the location where this service is being used.
+          description:
           required: false
           type: string
-        - name: orchestration-status
+        - name: role
           in: query
-          description: Orchestration status of this service.
+          description:
           required: false
           type: string
   /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/service-instances/service-instance/{service-instance-id}:
@@ -12348,7 +13786,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/service-instance"
+              $ref: "#/getDefinitions/service-instance"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -12357,66 +13795,27 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
-        - name: subscriber-name
-          in: query
-          description: Subscriber name, an alternate way to retrieve a customer.
-          required: false
-          type: string
-        - name: subscriber-type
-          in: query
-          description: Subscriber type, a way to provide VID with only the INFRA customers.
-          required: false
-          type: string
-        - name: service-instance-name
-          in: query
-          description: This field will store a name assigned to the service-instance.
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: service-instance-location-id
-          in: query
-          description: An identifier that customers assign to the location where this service is being used.
-          required: false
-          type: string
-        - name: orchestration-status
-          in: query
-          description: Orchestration status of this service.
-          required: false
-          type: string
+          example: __SERVICE-INSTANCE-ID__
     put:
       tags:
         - Business
       summary: create or update an existing service-instance
-      description: create or update an existing service-instance
+      description: |
+        Create or update an existing service-instance.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance
       consumes:
         - application/json
@@ -12433,22 +13832,76 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: body
           in: body
-          description: service-instance object that needs to be created or updated
+          description: service-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance.json)
           required: true
           schema:
             $ref: "#/definitions/service-instance"
+    patch:
+      tags:
+        - Business
+      summary: update an existing service-instance
+      description: |
+        Update an existing service-instance
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscriptionServiceInstancesServiceInstance
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: global-customer-id
+          in: path
+          description: Global customer id used across ECOMP to uniquely identify customer.
+          required: true
+          type: string
+          example: __GLOBAL-CUSTOMER-ID__
+        - name: service-type
+          in: path
+          description: Value defined by orchestration to identify this service across ECOMP.
+          required: true
+          type: string
+          example: __SERVICE-TYPE__
+        - name: service-instance-id
+          in: path
+          description: Uniquely identifies this instance of a service
+          required: true
+          type: string
+          example: __SERVICE-INSTANCE-ID__
+        - name: body
+          in: body
+          description: service-instance object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/service-instance"
     delete:
       tags:
         - Business
@@ -12470,16 +13923,19 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: service-instance-id
           in: path
           description: Uniquely identifies this instance of a service
           required: true
           type: string
+          example: __SERVICE-INSTANCE-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -12499,7 +13955,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/service-instances"
+              $ref: "#/getDefinitions/service-instances"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -12508,19 +13964,51 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
-        - name: subscriber-name
+          example: __SERVICE-TYPE__
+        - name: service-instance-id
           in: query
-          description: Subscriber name, an alternate way to retrieve a customer.
+          description:
           required: false
           type: string
-        - name: subscriber-type
+        - name: service-instance-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: model-invariant-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: model-version-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: widget-model-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: widget-model-version
+          in: query
+          description:
+          required: false
+          type: string
+        - name: service-instance-location-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: orchestration-status
           in: query
-          description: Subscriber type, a way to provide VID with only the INFRA customers.
+          description:
           required: false
           type: string
   /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}/relationship-list/relationship:
@@ -12544,14 +14032,16 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -12576,11 +14066,13 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
   /business/customers/customer/{global-customer-id}/service-subscriptions/service-subscription/{service-type}:
     get:
       tags:
@@ -12595,7 +14087,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/service-subscription"
+              $ref: "#/getDefinitions/service-subscription"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -12604,26 +14096,21 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
-        - name: subscriber-name
-          in: query
-          description: Subscriber name, an alternate way to retrieve a customer.
-          required: false
-          type: string
-        - name: subscriber-type
-          in: query
-          description: Subscriber type, a way to provide VID with only the INFRA customers.
-          required: false
-          type: string
+          example: __SERVICE-TYPE__
     put:
       tags:
         - Business
       summary: create or update an existing service-subscription
-      description: create or update an existing service-subscription
+      description: |
+        Create or update an existing service-subscription.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscription
       consumes:
         - application/json
@@ -12640,17 +14127,64 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: body
           in: body
-          description: service-subscription object that needs to be created or updated
+          description: service-subscription object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomerServiceSubscriptionsServiceSubscription.json)
           required: true
           schema:
             $ref: "#/definitions/service-subscription"
+    patch:
+      tags:
+        - Business
+      summary: update an existing service-subscription
+      description: |
+        Update an existing service-subscription
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateBusinessCustomersCustomerServiceSubscriptionsServiceSubscription
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: global-customer-id
+          in: path
+          description: Global customer id used across ECOMP to uniquely identify customer.
+          required: true
+          type: string
+          example: __GLOBAL-CUSTOMER-ID__
+        - name: service-type
+          in: path
+          description: Value defined by orchestration to identify this service across ECOMP.
+          required: true
+          type: string
+          example: __SERVICE-TYPE__
+        - name: body
+          in: body
+          description: service-subscription object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/service-subscription"
     delete:
       tags:
         - Business
@@ -12672,11 +14206,13 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: service-type
           in: path
           description: Value defined by orchestration to identify this service across ECOMP.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -12696,7 +14232,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/service-subscriptions"
+              $ref: "#/getDefinitions/service-subscriptions"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -12705,14 +14241,10 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
-        - name: subscriber-name
-          in: query
-          description: Subscriber name, an alternate way to retrieve a customer.
-          required: false
-          type: string
-        - name: subscriber-type
+          example: __GLOBAL-CUSTOMER-ID__
+        - name: service-type
           in: query
-          description: Subscriber type, a way to provide VID with only the INFRA customers.
+          description:
           required: false
           type: string
   /business/customers/customer/{global-customer-id}/relationship-list/relationship:
@@ -12736,9 +14268,10 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomer.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -12763,6 +14296,7 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
   /business/customers/customer/{global-customer-id}:
     get:
       tags:
@@ -12777,7 +14311,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/customer"
+              $ref: "#/getDefinitions/customer"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -12786,21 +14320,15 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
-        - name: subscriber-name
-          in: query
-          description: Subscriber name, an alternate way to retrieve a customer.
-          required: false
-          type: string
-        - name: subscriber-type
-          in: query
-          description: Subscriber type, a way to provide VID with only the INFRA customers.
-          required: false
-          type: string
+          example: __GLOBAL-CUSTOMER-ID__
     put:
       tags:
         - Business
       summary: create or update an existing customer
-      description: create or update an existing customer
+      description: |
+        Create or update an existing customer.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateBusinessCustomersCustomer
       consumes:
         - application/json
@@ -12817,12 +14345,52 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: body
           in: body
-          description: customer object that needs to be created or updated
+          description: customer object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/BusinessCustomersCustomer.json)
           required: true
           schema:
             $ref: "#/definitions/customer"
+    patch:
+      tags:
+        - Business
+      summary: update an existing customer
+      description: |
+        Update an existing customer
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateBusinessCustomersCustomer
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: global-customer-id
+          in: path
+          description: Global customer id used across ECOMP to uniquely identify customer.
+          required: true
+          type: string
+          example: __GLOBAL-CUSTOMER-ID__
+        - name: body
+          in: body
+          description: customer object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/customer"
     delete:
       tags:
         - Business
@@ -12844,6 +14412,7 @@ paths:
           description: Global customer id used across ECOMP to uniquely identify customer.
           required: true
           type: string
+          example: __GLOBAL-CUSTOMER-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -12863,9 +14432,25 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/customers"
+              $ref: "#/getDefinitions/customers"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: global-customer-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: subscriber-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: subscriber-type
+          in: query
+          description:
+          required: false
+          type: string
   /service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}/relationship-list/relationship:
     put:
       tags:
@@ -12887,9 +14472,10 @@ paths:
           description: Unique ID of this asset
           required: true
           type: string
+          example: __VNF-IMAGE-UUID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationVnfImagesVnfImage.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -12914,6 +14500,7 @@ paths:
           description: Unique ID of this asset
           required: true
           type: string
+          example: __VNF-IMAGE-UUID__
   /service-design-and-creation/vnf-images/vnf-image/{vnf-image-uuid}:
     get:
       tags:
@@ -12928,7 +14515,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vnf-image"
+              $ref: "#/getDefinitions/vnf-image"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -12937,26 +14524,15 @@ paths:
           description: Unique ID of this asset
           required: true
           type: string
-        - name: application
-          in: query
-          description: The application that the image instantiates.
-          required: false
-          type: string
-        - name: application-vendor
-          in: query
-          description: The vendor of the application.
-          required: false
-          type: string
-        - name: application-version
-          in: query
-          description: The version of the application.
-          required: false
-          type: string
+          example: __VNF-IMAGE-UUID__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing vnf-image
-      description: create or update an existing vnf-image
+      description: |
+        Create or update an existing vnf-image.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationVnfImagesVnfImage
       consumes:
         - application/json
@@ -12973,12 +14549,52 @@ paths:
           description: Unique ID of this asset
           required: true
           type: string
+          example: __VNF-IMAGE-UUID__
         - name: body
           in: body
-          description: vnf-image object that needs to be created or updated
+          description: vnf-image object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationVnfImagesVnfImage.json)
           required: true
           schema:
             $ref: "#/definitions/vnf-image"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing vnf-image
+      description: |
+        Update an existing vnf-image
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationVnfImagesVnfImage
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-image-uuid
+          in: path
+          description: Unique ID of this asset
+          required: true
+          type: string
+          example: __VNF-IMAGE-UUID__
+        - name: body
+          in: body
+          description: vnf-image object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vnf-image"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -13000,6 +14616,7 @@ paths:
           description: Unique ID of this asset
           required: true
           type: string
+          example: __VNF-IMAGE-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -13019,9 +14636,30 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vnf-images"
+              $ref: "#/getDefinitions/vnf-images"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-image-uuid
+          in: query
+          description:
+          required: false
+          type: string
+        - name: application
+          in: query
+          description:
+          required: false
+          type: string
+        - name: application-vendor
+          in: query
+          description:
+          required: false
+          type: string
+        - name: application-version
+          in: query
+          description:
+          required: false
+          type: string
   /service-design-and-creation/services/service/{service-id}/relationship-list/relationship:
     put:
       tags:
@@ -13043,9 +14681,10 @@ paths:
           description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
           required: true
           type: string
+          example: __SERVICE-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServicesService.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -13070,6 +14709,7 @@ paths:
           description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
           required: true
           type: string
+          example: __SERVICE-ID__
   /service-design-and-creation/services/service/{service-id}:
     get:
       tags:
@@ -13084,7 +14724,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/service"
+              $ref: "#/getDefinitions/service"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -13093,16 +14733,15 @@ paths:
           description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
           required: true
           type: string
-        - name: service-description
-          in: query
-          description: Description of the service
-          required: false
-          type: string
+          example: __SERVICE-ID__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing service
-      description: create or update an existing service
+      description: |
+        Create or update an existing service.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationServicesService
       consumes:
         - application/json
@@ -13119,12 +14758,52 @@ paths:
           description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
           required: true
           type: string
+          example: __SERVICE-ID__
         - name: body
           in: body
-          description: service object that needs to be created or updated
+          description: service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServicesService.json)
           required: true
           schema:
             $ref: "#/definitions/service"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing service
+      description: |
+        Update an existing service
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationServicesService
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: service-id
+          in: path
+          description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+          required: true
+          type: string
+          example: __SERVICE-ID__
+        - name: body
+          in: body
+          description: service object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/service"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -13146,6 +14825,7 @@ paths:
           description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
           required: true
           type: string
+          example: __SERVICE-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -13165,9 +14845,20 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/services"
+              $ref: "#/getDefinitions/services"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: service-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: service-description
+          in: query
+          description:
+          required: false
+          type: string
   /service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}/relationship-list/relationship:
     put:
       tags:
@@ -13189,14 +14880,16 @@ paths:
           description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: vnf-type
           in: path
           description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
           required: true
           type: string
+          example: __VNF-TYPE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -13221,11 +14914,13 @@ paths:
           description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: vnf-type
           in: path
           description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
           required: true
           type: string
+          example: __VNF-TYPE__
   /service-design-and-creation/service-capabilities/service-capability/{service-type}/{vnf-type}:
     get:
       tags:
@@ -13240,7 +14935,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/service-capability"
+              $ref: "#/getDefinitions/service-capability"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -13249,16 +14944,21 @@ paths:
           description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: vnf-type
           in: path
           description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
           required: true
           type: string
+          example: __VNF-TYPE__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing service-capability
-      description: create or update an existing service-capability
+      description: |
+        Create or update an existing service-capability.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationServiceCapabilitiesServiceCapability
       consumes:
         - application/json
@@ -13275,17 +14975,64 @@ paths:
           description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: vnf-type
           in: path
           description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
           required: true
           type: string
+          example: __VNF-TYPE__
         - name: body
           in: body
-          description: service-capability object that needs to be created or updated
+          description: service-capability object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationServiceCapabilitiesServiceCapability.json)
           required: true
           schema:
             $ref: "#/definitions/service-capability"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing service-capability
+      description: |
+        Update an existing service-capability
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationServiceCapabilitiesServiceCapability
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: service-type
+          in: path
+          description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+          required: true
+          type: string
+          example: __SERVICE-TYPE__
+        - name: vnf-type
+          in: path
+          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+          required: true
+          type: string
+          example: __VNF-TYPE__
+        - name: body
+          in: body
+          description: service-capability object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/service-capability"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -13307,11 +15054,13 @@ paths:
           description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
           required: true
           type: string
+          example: __SERVICE-TYPE__
         - name: vnf-type
           in: path
           description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
           required: true
           type: string
+          example: __VNF-TYPE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -13331,9 +15080,20 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/service-capabilities"
+              $ref: "#/getDefinitions/service-capabilities"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: service-type
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vnf-type
+          in: query
+          description:
+          required: false
+          type: string
   /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}/relationship-list/relationship:
     put:
       tags:
@@ -13355,30 +15115,36 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: constrained-element-set-uuid
           in: path
           required: true
           type: string
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
         - name: element-choice-set-uuid
           in: path
           required: true
           type: string
+          example: __ELEMENT-CHOICE-SET-UUID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -13403,27 +15169,33 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: constrained-element-set-uuid
           in: path
           required: true
           type: string
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
         - name: element-choice-set-uuid
           in: path
           required: true
           type: string
+          example: __ELEMENT-CHOICE-SET-UUID__
   /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/element-choice-sets/element-choice-set/{element-choice-set-uuid}:
     get:
       tags:
@@ -13438,7 +15210,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/element-choice-set"
+              $ref: "#/getDefinitions/element-choice-set"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -13447,47 +15219,41 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: constrained-element-set-uuid
           in: path
           required: true
           type: string
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
         - name: element-choice-set-uuid
           in: path
           required: true
           type: string
-        - name: model-type
-          in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
-          required: false
-          type: string
-        - name: model-name
-          in: query
-          description: Name of the model, which can change from version to version.
-          required: false
-          type: string
-        - name: model-version
-          in: query
-          description: Version
-          required: false
-          type: string
+          example: __ELEMENT-CHOICE-SET-UUID__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing element-choice-set
-      description: create or update an existing element-choice-set
+      description: |
+        Create or update an existing element-choice-set.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet
       consumes:
         - application/json
@@ -13504,33 +15270,104 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: constrained-element-set-uuid
           in: path
           required: true
           type: string
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
         - name: element-choice-set-uuid
           in: path
           required: true
           type: string
+          example: __ELEMENT-CHOICE-SET-UUID__
         - name: body
           in: body
-          description: element-choice-set object that needs to be created or updated
+          description: element-choice-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet.json)
           required: true
           schema:
             $ref: "#/definitions/element-choice-set"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing element-choice-set
+      description: |
+        Update an existing element-choice-set
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSetElementChoiceSetsElementChoiceSet
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: model-invariant-id
+          in: path
+          description: Unique identifier corresponding to the main definition of a model in ASDC
+          required: true
+          type: string
+          example: __MODEL-INVARIANT-ID__
+        - name: model-version-id
+          in: path
+          description: Unique identifier corresponding to one version of a model in ASDC
+          required: true
+          type: string
+          example: __MODEL-VERSION-ID__
+        - name: model-element-uuid
+          in: path
+          required: true
+          type: string
+          example: __MODEL-ELEMENT-UUID__
+        - name: model-constraint-uuid
+          in: path
+          required: true
+          type: string
+          example: __MODEL-CONSTRAINT-UUID__
+        - name: constrained-element-set-uuid
+          in: path
+          required: true
+          type: string
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
+        - name: element-choice-set-uuid
+          in: path
+          required: true
+          type: string
+          example: __ELEMENT-CHOICE-SET-UUID__
+        - name: body
+          in: body
+          description: element-choice-set object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/element-choice-set"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -13552,27 +15389,33 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: constrained-element-set-uuid
           in: path
           required: true
           type: string
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
         - name: element-choice-set-uuid
           in: path
           required: true
           type: string
+          example: __ELEMENT-CHOICE-SET-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -13592,7 +15435,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/element-choice-sets"
+              $ref: "#/getDefinitions/element-choice-sets"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -13601,36 +15444,31 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: constrained-element-set-uuid
           in: path
           required: true
           type: string
-        - name: model-type
-          in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
-          required: false
-          type: string
-        - name: model-name
-          in: query
-          description: Name of the model, which can change from version to version.
-          required: false
-          type: string
-        - name: model-version
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
+        - name: element-choice-set-uuid
           in: query
-          description: Version
+          description:
           required: false
           type: string
   /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}/relationship-list/relationship:
@@ -13654,26 +15492,31 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: constrained-element-set-uuid
           in: path
           required: true
           type: string
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -13698,23 +15541,28 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: constrained-element-set-uuid
           in: path
           required: true
           type: string
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
   /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}/constrained-element-sets/constrained-element-set/{constrained-element-set-uuid}:
     get:
       tags:
@@ -13729,7 +15577,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/constrained-element-set"
+              $ref: "#/getDefinitions/constrained-element-set"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -13738,43 +15586,36 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: constrained-element-set-uuid
           in: path
           required: true
           type: string
-        - name: model-type
-          in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
-          required: false
-          type: string
-        - name: model-name
-          in: query
-          description: Name of the model, which can change from version to version.
-          required: false
-          type: string
-        - name: model-version
-          in: query
-          description: Version
-          required: false
-          type: string
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing constrained-element-set
-      description: create or update an existing constrained-element-set
+      description: |
+        Create or update an existing constrained-element-set.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet
       consumes:
         - application/json
@@ -13791,29 +15632,94 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: constrained-element-set-uuid
           in: path
           required: true
           type: string
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
         - name: body
           in: body
-          description: constrained-element-set object that needs to be created or updated
+          description: constrained-element-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet.json)
           required: true
           schema:
             $ref: "#/definitions/constrained-element-set"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing constrained-element-set
+      description: |
+        Update an existing constrained-element-set
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraintConstrainedElementSetsConstrainedElementSet
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: model-invariant-id
+          in: path
+          description: Unique identifier corresponding to the main definition of a model in ASDC
+          required: true
+          type: string
+          example: __MODEL-INVARIANT-ID__
+        - name: model-version-id
+          in: path
+          description: Unique identifier corresponding to one version of a model in ASDC
+          required: true
+          type: string
+          example: __MODEL-VERSION-ID__
+        - name: model-element-uuid
+          in: path
+          required: true
+          type: string
+          example: __MODEL-ELEMENT-UUID__
+        - name: model-constraint-uuid
+          in: path
+          required: true
+          type: string
+          example: __MODEL-CONSTRAINT-UUID__
+        - name: constrained-element-set-uuid
+          in: path
+          required: true
+          type: string
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
+        - name: body
+          in: body
+          description: constrained-element-set object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/constrained-element-set"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -13835,23 +15741,28 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: constrained-element-set-uuid
           in: path
           required: true
           type: string
+          example: __CONSTRAINED-ELEMENT-SET-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -13871,7 +15782,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/constrained-element-sets"
+              $ref: "#/getDefinitions/constrained-element-sets"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -13880,32 +15791,26 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
-        - name: model-type
-          in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
-          required: false
-          type: string
-        - name: model-name
-          in: query
-          description: Name of the model, which can change from version to version.
-          required: false
-          type: string
-        - name: model-version
+          example: __MODEL-CONSTRAINT-UUID__
+        - name: constrained-element-set-uuid
           in: query
-          description: Version
+          description:
           required: false
           type: string
   /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/model-constraints/model-constraint/{model-constraint-uuid}:
@@ -13922,7 +15827,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/model-constraint"
+              $ref: "#/getDefinitions/model-constraint"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -13931,39 +15836,31 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
-        - name: model-type
-          in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
-          required: false
-          type: string
-        - name: model-name
-          in: query
-          description: Name of the model, which can change from version to version.
-          required: false
-          type: string
-        - name: model-version
-          in: query
-          description: Version
-          required: false
-          type: string
+          example: __MODEL-CONSTRAINT-UUID__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing model-constraint
-      description: create or update an existing model-constraint
+      description: |
+        Create or update an existing model-constraint.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint
       consumes:
         - application/json
@@ -13980,25 +15877,84 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: body
           in: body
-          description: model-constraint object that needs to be created or updated
+          description: model-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint.json)
           required: true
           schema:
             $ref: "#/definitions/model-constraint"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing model-constraint
+      description: |
+        Update an existing model-constraint
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElementModelConstraintsModelConstraint
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: model-invariant-id
+          in: path
+          description: Unique identifier corresponding to the main definition of a model in ASDC
+          required: true
+          type: string
+          example: __MODEL-INVARIANT-ID__
+        - name: model-version-id
+          in: path
+          description: Unique identifier corresponding to one version of a model in ASDC
+          required: true
+          type: string
+          example: __MODEL-VERSION-ID__
+        - name: model-element-uuid
+          in: path
+          required: true
+          type: string
+          example: __MODEL-ELEMENT-UUID__
+        - name: model-constraint-uuid
+          in: path
+          required: true
+          type: string
+          example: __MODEL-CONSTRAINT-UUID__
+        - name: body
+          in: body
+          description: model-constraint object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/model-constraint"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -14020,19 +15976,23 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: model-constraint-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-CONSTRAINT-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -14052,7 +16012,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/model-constraints"
+              $ref: "#/getDefinitions/model-constraints"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -14061,28 +16021,21 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
-        - name: model-type
-          in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
-          required: false
-          type: string
-        - name: model-name
-          in: query
-          description: Name of the model, which can change from version to version.
-          required: false
-          type: string
-        - name: model-version
+          example: __MODEL-ELEMENT-UUID__
+        - name: model-constraint-uuid
           in: query
-          description: Version
+          description:
           required: false
           type: string
   /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}/relationship-list/relationship:
@@ -14106,18 +16059,21 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -14142,15 +16098,18 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
   /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/model-elements/model-element/{model-element-uuid}:
     get:
       tags:
@@ -14165,7 +16124,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/model-element"
+              $ref: "#/getDefinitions/model-element"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -14174,35 +16133,26 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
-        - name: model-type
-          in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
-          required: false
-          type: string
-        - name: model-name
-          in: query
-          description: Name of the model, which can change from version to version.
-          required: false
-          type: string
-        - name: model-version
-          in: query
-          description: Version
-          required: false
-          type: string
+          example: __MODEL-ELEMENT-UUID__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing model-element
-      description: create or update an existing model-element
+      description: |
+        Create or update an existing model-element.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement
       consumes:
         - application/json
@@ -14219,21 +16169,74 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: body
           in: body
-          description: model-element object that needs to be created or updated
+          description: model-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement.json)
           required: true
           schema:
             $ref: "#/definitions/model-element"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing model-element
+      description: |
+        Update an existing model-element
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerModelElementsModelElement
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: model-invariant-id
+          in: path
+          description: Unique identifier corresponding to the main definition of a model in ASDC
+          required: true
+          type: string
+          example: __MODEL-INVARIANT-ID__
+        - name: model-version-id
+          in: path
+          description: Unique identifier corresponding to one version of a model in ASDC
+          required: true
+          type: string
+          example: __MODEL-VERSION-ID__
+        - name: model-element-uuid
+          in: path
+          required: true
+          type: string
+          example: __MODEL-ELEMENT-UUID__
+        - name: body
+          in: body
+          description: model-element object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/model-element"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -14255,15 +16258,18 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: model-element-uuid
           in: path
           required: true
           type: string
+          example: __MODEL-ELEMENT-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -14283,7 +16289,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/model-elements"
+              $ref: "#/getDefinitions/model-elements"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -14292,24 +16298,16 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
-        - name: model-type
-          in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
-          required: false
-          type: string
-        - name: model-name
-          in: query
-          description: Name of the model, which can change from version to version.
-          required: false
-          type: string
-        - name: model-version
+          example: __MODEL-VERSION-ID__
+        - name: model-element-uuid
           in: query
-          description: Version
+          description:
           required: false
           type: string
   /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/metadata/metadatum/{metaname}:
@@ -14326,7 +16324,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/metadatum"
+              $ref: "#/getDefinitions/metadatum"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -14335,35 +16333,26 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: metaname
           in: path
           required: true
           type: string
-        - name: model-type
-          in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
-          required: false
-          type: string
-        - name: model-name
-          in: query
-          description: Name of the model, which can change from version to version.
-          required: false
-          type: string
-        - name: model-version
-          in: query
-          description: Version
-          required: false
-          type: string
+          example: __METANAME__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing metadatum
-      description: create or update an existing metadatum
+      description: |
+        Create or update an existing metadatum.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum
       consumes:
         - application/json
@@ -14380,21 +16369,74 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: metaname
           in: path
           required: true
           type: string
+          example: __METANAME__
         - name: body
           in: body
-          description: metadatum object that needs to be created or updated
+          description: metadatum object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum.json)
           required: true
           schema:
             $ref: "#/definitions/metadatum"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing metadatum
+      description: |
+        Update an existing metadatum
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVerMetadataMetadatum
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: model-invariant-id
+          in: path
+          description: Unique identifier corresponding to the main definition of a model in ASDC
+          required: true
+          type: string
+          example: __MODEL-INVARIANT-ID__
+        - name: model-version-id
+          in: path
+          description: Unique identifier corresponding to one version of a model in ASDC
+          required: true
+          type: string
+          example: __MODEL-VERSION-ID__
+        - name: metaname
+          in: path
+          required: true
+          type: string
+          example: __METANAME__
+        - name: body
+          in: body
+          description: metadatum object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/metadatum"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -14416,15 +16458,18 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: metaname
           in: path
           required: true
           type: string
+          example: __METANAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -14444,7 +16489,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/metadata"
+              $ref: "#/getDefinitions/metadata"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -14453,24 +16498,16 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
-        - name: model-type
-          in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
-          required: false
-          type: string
-        - name: model-name
-          in: query
-          description: Name of the model, which can change from version to version.
-          required: false
-          type: string
-        - name: model-version
+          example: __MODEL-VERSION-ID__
+        - name: metaname
           in: query
-          description: Version
+          description:
           required: false
           type: string
   /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}/relationship-list/relationship:
@@ -14494,14 +16531,16 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVer.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -14526,11 +16565,13 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
   /service-design-and-creation/models/model/{model-invariant-id}/model-vers/model-ver/{model-version-id}:
     get:
       tags:
@@ -14545,7 +16586,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/model-ver"
+              $ref: "#/getDefinitions/model-ver"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -14554,31 +16595,21 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
-        - name: model-type
-          in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
-          required: false
-          type: string
-        - name: model-name
-          in: query
-          description: Name of the model, which can change from version to version.
-          required: false
-          type: string
-        - name: model-version
-          in: query
-          description: Version
-          required: false
-          type: string
+          example: __MODEL-VERSION-ID__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing model-ver
-      description: create or update an existing model-ver
+      description: |
+        Create or update an existing model-ver.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationModelsModelModelVersModelVer
       consumes:
         - application/json
@@ -14595,17 +16626,64 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: body
           in: body
-          description: model-ver object that needs to be created or updated
+          description: model-ver object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModelModelVersModelVer.json)
           required: true
           schema:
             $ref: "#/definitions/model-ver"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing model-ver
+      description: |
+        Update an existing model-ver
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationModelsModelModelVersModelVer
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: model-invariant-id
+          in: path
+          description: Unique identifier corresponding to the main definition of a model in ASDC
+          required: true
+          type: string
+          example: __MODEL-INVARIANT-ID__
+        - name: model-version-id
+          in: path
+          description: Unique identifier corresponding to one version of a model in ASDC
+          required: true
+          type: string
+          example: __MODEL-VERSION-ID__
+        - name: body
+          in: body
+          description: model-ver object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/model-ver"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -14627,11 +16705,13 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: model-version-id
           in: path
           description: Unique identifier corresponding to one version of a model in ASDC
           required: true
           type: string
+          example: __MODEL-VERSION-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -14651,7 +16731,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/model-vers"
+              $ref: "#/getDefinitions/model-vers"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -14660,9 +16740,20 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
-        - name: model-type
+          example: __MODEL-INVARIANT-ID__
+        - name: model-version-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: model-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: model-version
           in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
+          description:
           required: false
           type: string
   /service-design-and-creation/models/model/{model-invariant-id}/relationship-list/relationship:
@@ -14686,9 +16777,10 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModel.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -14713,6 +16805,7 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
   /service-design-and-creation/models/model/{model-invariant-id}:
     get:
       tags:
@@ -14727,7 +16820,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/model"
+              $ref: "#/getDefinitions/model"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -14736,16 +16829,15 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
-        - name: model-type
-          in: query
-          description: Type of the model, e.g., service, resource, widget, etc.
-          required: false
-          type: string
+          example: __MODEL-INVARIANT-ID__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing model
-      description: create or update an existing model
+      description: |
+        Create or update an existing model.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationModelsModel
       consumes:
         - application/json
@@ -14762,18 +16854,30 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
+          example: __MODEL-INVARIANT-ID__
         - name: body
           in: body
-          description: model object that needs to be created or updated
+          description: model object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationModelsModel.json)
           required: true
           schema:
             $ref: "#/definitions/model"
-    delete:
+    patch:
       tags:
         - ServiceDesignAndCreation
-      summary: delete an existing model
-      description: delete an existing model
-      operationId: deleteServiceDesignAndCreationModelsModel
+      summary: update an existing model
+      description: |
+        Update an existing model
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationModelsModel
       consumes:
         - application/json
         - application/xml
@@ -14789,68 +16893,19 @@ paths:
           description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
-        - name: resource-version
-          in: query
-          description: resource-version for concurrency
-          required: true
-          type: string
-  /service-design-and-creation/models:
-    get:
-      tags:
-        - ServiceDesignAndCreation
-      summary: returns models
-      description: returns models
-      operationId: getServiceDesignAndCreationModels
-      produces:
-        - application/json
-        - application/xml
-      responses:
-        "200":
-          description: successful operation
-          schema:
-              $ref: "#/definitions/models"
-        "default":
-          description: Response codes found in [response codes](https://wiki.onap.org/).
-  /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}/relationship-list/relationship:
-    put:
-      tags:
-        - ServiceDesignAndCreation
-      summary: see node definition for valid relationships
-      operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookupRelationshipListRelationship
-      consumes:
-        - application/json
-        - application/xml
-      produces:
-        - application/json
-        - application/xml
-      responses:
-        "default":
-          description: Response codes found in [response codes](https://wiki.onap.org/).
-      parameters:
-        - name: named-query-uuid
-          in: path
-          required: true
-          type: string
-        - name: named-query-element-uuid
-          in: path
-          required: true
-          type: string
-        - name: related-lookup-uuid
-          in: path
-          required: true
-          type: string
+          example: __MODEL-INVARIANT-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: model object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/relationship"
+            $ref: "#/patchDefinitions/model"
     delete:
       tags:
         - ServiceDesignAndCreation
-      summary: delete an existing relationship
-      description: delete an existing relationship
-      operationId: deleteServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookupRelationshipListRelationship
+      summary: delete an existing model
+      description: delete an existing model
+      operationId: deleteServiceDesignAndCreationModelsModel
       consumes:
         - application/json
         - application/xml
@@ -14861,25 +16916,24 @@ paths:
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
-        - name: named-query-uuid
-          in: path
-          required: true
-          type: string
-        - name: named-query-element-uuid
+        - name: model-invariant-id
           in: path
+          description: Unique identifier corresponding to the main definition of a model in ASDC
           required: true
           type: string
-        - name: related-lookup-uuid
-          in: path
+          example: __MODEL-INVARIANT-ID__
+        - name: resource-version
+          in: query
+          description: resource-version for concurrency
           required: true
           type: string
-  /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}:
+  /service-design-and-creation/models:
     get:
       tags:
         - ServiceDesignAndCreation
-      summary: returns related-lookup
-      description: returns related-lookup
-      operationId: getServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
+      summary: returns models
+      description: returns models
+      operationId: getServiceDesignAndCreationModels
       produces:
         - application/json
         - application/xml
@@ -14887,32 +16941,26 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/related-lookup"
+              $ref: "#/getDefinitions/models"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
-        - name: named-query-uuid
-          in: path
-          required: true
-          type: string
-        - name: named-query-element-uuid
-          in: path
-          required: true
-          type: string
-        - name: related-lookup-uuid
-          in: path
-          required: true
+        - name: model-invariant-id
+          in: query
+          description:
+          required: false
           type: string
-        - name: named-query-name
+        - name: model-type
           in: query
+          description:
           required: false
           type: string
+  /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}/relationship-list/relationship:
     put:
       tags:
         - ServiceDesignAndCreation
-      summary: create or update an existing related-lookup
-      description: create or update an existing related-lookup
-      operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
+      summary: see node definition for valid relationships
+      operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookupRelationshipListRelationship
       consumes:
         - application/json
         - application/xml
@@ -14927,20 +16975,175 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: named-query-element-uuid
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
         - name: related-lookup-uuid
           in: path
           required: true
           type: string
+          example: __RELATED-LOOKUP-UUID__
         - name: body
           in: body
-          description: related-lookup object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)
+          required: true
+          schema:
+            $ref: "#/definitions/relationship"
+    delete:
+      tags:
+        - ServiceDesignAndCreation
+      summary: delete an existing relationship
+      description: delete an existing relationship
+      operationId: deleteServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookupRelationshipListRelationship
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: named-query-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-UUID__
+        - name: named-query-element-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
+        - name: related-lookup-uuid
+          in: path
+          required: true
+          type: string
+          example: __RELATED-LOOKUP-UUID__
+  /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/related-lookups/related-lookup/{related-lookup-uuid}:
+    get:
+      tags:
+        - ServiceDesignAndCreation
+      summary: returns related-lookup
+      description: returns related-lookup
+      operationId: getServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "200":
+          description: successful operation
+          schema:
+              $ref: "#/getDefinitions/related-lookup"
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: named-query-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-UUID__
+        - name: named-query-element-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
+        - name: related-lookup-uuid
+          in: path
+          required: true
+          type: string
+          example: __RELATED-LOOKUP-UUID__
+    put:
+      tags:
+        - ServiceDesignAndCreation
+      summary: create or update an existing related-lookup
+      description: |
+        Create or update an existing related-lookup.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: named-query-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-UUID__
+        - name: named-query-element-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
+        - name: related-lookup-uuid
+          in: path
+          required: true
+          type: string
+          example: __RELATED-LOOKUP-UUID__
+        - name: body
+          in: body
+          description: related-lookup object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup.json)
           required: true
           schema:
             $ref: "#/definitions/related-lookup"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing related-lookup
+      description: |
+        Update an existing related-lookup
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementRelatedLookupsRelatedLookup
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: named-query-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-UUID__
+        - name: named-query-element-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
+        - name: related-lookup-uuid
+          in: path
+          required: true
+          type: string
+          example: __RELATED-LOOKUP-UUID__
+        - name: body
+          in: body
+          description: related-lookup object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/related-lookup"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -14961,14 +17164,17 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: named-query-element-uuid
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
         - name: related-lookup-uuid
           in: path
           required: true
           type: string
+          example: __RELATED-LOOKUP-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -14988,7 +17194,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/related-lookups"
+              $ref: "#/getDefinitions/related-lookups"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -14996,12 +17202,15 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: named-query-element-uuid
           in: path
           required: true
           type: string
-        - name: named-query-name
+          example: __NAMED-QUERY-ELEMENT-UUID__
+        - name: related-lookup-uuid
           in: query
+          description:
           required: false
           type: string
   /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/property-constraints/property-constraint/{property-constraint-uuid}:
@@ -15018,7 +17227,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/property-constraint"
+              $ref: "#/getDefinitions/property-constraint"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -15026,23 +17235,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: named-query-element-uuid
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
         - name: property-constraint-uuid
           in: path
           required: true
           type: string
-        - name: named-query-name
-          in: query
-          required: false
-          type: string
+          example: __PROPERTY-CONSTRAINT-UUID__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing property-constraint
-      description: create or update an existing property-constraint
+      description: |
+        Create or update an existing property-constraint.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint
       consumes:
         - application/json
@@ -15058,20 +17269,71 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: named-query-element-uuid
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
         - name: property-constraint-uuid
           in: path
           required: true
           type: string
+          example: __PROPERTY-CONSTRAINT-UUID__
         - name: body
           in: body
-          description: property-constraint object that needs to be created or updated
+          description: property-constraint object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint.json)
           required: true
           schema:
             $ref: "#/definitions/property-constraint"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing property-constraint
+      description: |
+        Update an existing property-constraint
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElementPropertyConstraintsPropertyConstraint
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: named-query-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-UUID__
+        - name: named-query-element-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
+        - name: property-constraint-uuid
+          in: path
+          required: true
+          type: string
+          example: __PROPERTY-CONSTRAINT-UUID__
+        - name: body
+          in: body
+          description: property-constraint object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/property-constraint"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -15092,14 +17354,17 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: named-query-element-uuid
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
         - name: property-constraint-uuid
           in: path
           required: true
           type: string
+          example: __PROPERTY-CONSTRAINT-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -15119,7 +17384,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/property-constraints"
+              $ref: "#/getDefinitions/property-constraints"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -15127,12 +17392,15 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: named-query-element-uuid
           in: path
           required: true
           type: string
-        - name: named-query-name
+          example: __NAMED-QUERY-ELEMENT-UUID__
+        - name: property-constraint-uuid
           in: query
+          description:
           required: false
           type: string
   /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}/relationship-list/relationship:
@@ -15155,13 +17423,15 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: named-query-element-uuid
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -15185,10 +17455,12 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: named-query-element-uuid
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
   /service-design-and-creation/named-queries/named-query/{named-query-uuid}/named-query-elements/named-query-element/{named-query-element-uuid}:
     get:
       tags:
@@ -15203,7 +17475,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/named-query-element"
+              $ref: "#/getDefinitions/named-query-element"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -15211,19 +17483,20 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: named-query-element-uuid
           in: path
           required: true
           type: string
-        - name: named-query-name
-          in: query
-          required: false
-          type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing named-query-element
-      description: create or update an existing named-query-element
+      description: |
+        Create or update an existing named-query-element.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement
       consumes:
         - application/json
@@ -15239,16 +17512,61 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: named-query-element-uuid
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
         - name: body
           in: body
-          description: named-query-element object that needs to be created or updated
+          description: named-query-element object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement.json)
           required: true
           schema:
             $ref: "#/definitions/named-query-element"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing named-query-element
+      description: |
+        Update an existing named-query-element
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQueryNamedQueryElementsNamedQueryElement
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: named-query-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-UUID__
+        - name: named-query-element-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
+        - name: body
+          in: body
+          description: named-query-element object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/named-query-element"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -15269,10 +17587,12 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: named-query-element-uuid
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-ELEMENT-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -15292,7 +17612,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/named-query-elements"
+              $ref: "#/getDefinitions/named-query-elements"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -15300,8 +17620,10 @@ paths:
           in: path
           required: true
           type: string
-        - name: named-query-name
+          example: __NAMED-QUERY-UUID__
+        - name: named-query-element-uuid
           in: query
+          description:
           required: false
           type: string
   /service-design-and-creation/named-queries/named-query/{named-query-uuid}/relationship-list/relationship:
@@ -15324,9 +17646,10 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQuery.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -15350,6 +17673,7 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
   /service-design-and-creation/named-queries/named-query/{named-query-uuid}:
     get:
       tags:
@@ -15364,7 +17688,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/named-query"
+              $ref: "#/getDefinitions/named-query"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -15372,15 +17696,15 @@ paths:
           in: path
           required: true
           type: string
-        - name: named-query-name
-          in: query
-          required: false
-          type: string
+          example: __NAMED-QUERY-UUID__
     put:
       tags:
         - ServiceDesignAndCreation
       summary: create or update an existing named-query
-      description: create or update an existing named-query
+      description: |
+        Create or update an existing named-query.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateServiceDesignAndCreationNamedQueriesNamedQuery
       consumes:
         - application/json
@@ -15396,12 +17720,51 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: body
           in: body
-          description: named-query object that needs to be created or updated
+          description: named-query object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/ServiceDesignAndCreationNamedQueriesNamedQuery.json)
           required: true
           schema:
             $ref: "#/definitions/named-query"
+    patch:
+      tags:
+        - ServiceDesignAndCreation
+      summary: update an existing named-query
+      description: |
+        Update an existing named-query
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateServiceDesignAndCreationNamedQueriesNamedQuery
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: named-query-uuid
+          in: path
+          required: true
+          type: string
+          example: __NAMED-QUERY-UUID__
+        - name: body
+          in: body
+          description: named-query object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/named-query"
     delete:
       tags:
         - ServiceDesignAndCreation
@@ -15422,6 +17785,7 @@ paths:
           in: path
           required: true
           type: string
+          example: __NAMED-QUERY-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -15441,9 +17805,20 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/named-queries"
+              $ref: "#/getDefinitions/named-queries"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: named-query-uuid
+          in: query
+          description:
+          required: false
+          type: string
+        - name: named-query-name
+          in: query
+          description:
+          required: false
+          type: string
   /network/logical-links/logical-link/{link-name}/relationship-list/relationship:
     put:
       tags:
@@ -15465,9 +17840,10 @@ paths:
           description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
           required: true
           type: string
+          example: __LINK-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLogicalLinksLogicalLink.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -15492,6 +17868,7 @@ paths:
           description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
           required: true
           type: string
+          example: __LINK-NAME__
   /network/logical-links/logical-link/{link-name}:
     get:
       tags:
@@ -15506,7 +17883,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/logical-link"
+              $ref: "#/getDefinitions/logical-link"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -15515,51 +17892,15 @@ paths:
           description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
           required: true
           type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: link-id
-          in: query
-          description: UUID of the logical-link, SDNC generates this.
-          required: false
-          type: string
-        - name: circuit-id
-          in: query
-          description: Circuit id
-          required: false
-          type: string
-        - name: purpose
-          in: query
-          description: Reason for this entity, role it is playing
-          required: false
-          type: string
+          example: __LINK-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing logical-link
-      description: create or update an existing logical-link
+      description: |
+        Create or update an existing logical-link.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkLogicalLinksLogicalLink
       consumes:
         - application/json
@@ -15576,12 +17917,52 @@ paths:
           description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
           required: true
           type: string
+          example: __LINK-NAME__
         - name: body
           in: body
-          description: logical-link object that needs to be created or updated
+          description: logical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLogicalLinksLogicalLink.json)
           required: true
           schema:
             $ref: "#/definitions/logical-link"
+    patch:
+      tags:
+        - Network
+      summary: update an existing logical-link
+      description: |
+        Update an existing logical-link
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkLogicalLinksLogicalLink
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: link-name
+          in: path
+          description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+          required: true
+          type: string
+          example: __LINK-NAME__
+        - name: body
+          in: body
+          description: logical-link object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/logical-link"
     delete:
       tags:
         - Network
@@ -15603,6 +17984,7 @@ paths:
           description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
           required: true
           type: string
+          example: __LINK-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -15622,9 +18004,55 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/logical-links"
+              $ref: "#/getDefinitions/logical-links"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: link-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: model-invariant-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: model-version-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: widget-model-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: widget-model-version
+          in: query
+          description:
+          required: false
+          type: string
+        - name: prov-status
+          in: query
+          description:
+          required: false
+          type: string
+        - name: link-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: circuit-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: purpose
+          in: query
+          description:
+          required: false
+          type: string
   /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}/relationship-list/relationship:
     put:
       tags:
@@ -15646,24 +18074,28 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: site-pair-id
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __SITE-PAIR-ID__
         - name: cos
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __COS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -15688,21 +18120,25 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: site-pair-id
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __SITE-PAIR-ID__
         - name: cos
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __COS__
   /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/classes-of-service/class-of-service/{cos}:
     get:
       tags:
@@ -15717,7 +18153,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/class-of-service"
+              $ref: "#/getDefinitions/class-of-service"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -15726,26 +18162,33 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: site-pair-id
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __SITE-PAIR-ID__
         - name: cos
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __COS__
     put:
       tags:
         - Network
       summary: create or update an existing class-of-service
-      description: create or update an existing class-of-service
+      description: |
+        Create or update an existing class-of-service.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService
       consumes:
         - application/json
@@ -15762,27 +18205,88 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: site-pair-id
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __SITE-PAIR-ID__
         - name: cos
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __COS__
         - name: body
           in: body
-          description: class-of-service object that needs to be created or updated
+          description: class-of-service object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService.json)
           required: true
           schema:
             $ref: "#/definitions/class-of-service"
+    patch:
+      tags:
+        - Network
+      summary: update an existing class-of-service
+      description: |
+        Update an existing class-of-service
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePairClassesOfServiceClassOfService
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: site-pair-set-id
+          in: path
+          description: Unique id of site pair set.
+          required: true
+          type: string
+          example: __SITE-PAIR-SET-ID__
+        - name: routing-instance-id
+          in: path
+          description: Unique id of routing instance
+          required: true
+          type: string
+          example: __ROUTING-INSTANCE-ID__
+        - name: site-pair-id
+          in: path
+          description: unique identifier of probe
+          required: true
+          type: string
+          example: __SITE-PAIR-ID__
+        - name: cos
+          in: path
+          description: unique identifier of probe
+          required: true
+          type: string
+          example: __COS__
+        - name: body
+          in: body
+          description: class-of-service object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/class-of-service"
     delete:
       tags:
         - Network
@@ -15804,21 +18308,25 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: site-pair-id
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __SITE-PAIR-ID__
         - name: cos
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __COS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -15838,7 +18346,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/classes-of-service"
+              $ref: "#/getDefinitions/classes-of-service"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -15847,16 +18355,24 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: site-pair-id
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __SITE-PAIR-ID__
+        - name: cos
+          in: query
+          description:
+          required: false
+          type: string
   /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}/relationship-list/relationship:
     put:
       tags:
@@ -15878,19 +18394,22 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: site-pair-id
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __SITE-PAIR-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -15915,16 +18434,19 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: site-pair-id
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __SITE-PAIR-ID__
   /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/site-pairs/site-pair/{site-pair-id}:
     get:
       tags:
@@ -15939,7 +18461,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/site-pair"
+              $ref: "#/getDefinitions/site-pair"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -15948,21 +18470,27 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: site-pair-id
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __SITE-PAIR-ID__
     put:
       tags:
         - Network
       summary: create or update an existing site-pair
-      description: create or update an existing site-pair
+      description: |
+        Create or update an existing site-pair.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair
       consumes:
         - application/json
@@ -15979,22 +18507,76 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: site-pair-id
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __SITE-PAIR-ID__
         - name: body
           in: body
-          description: site-pair object that needs to be created or updated
+          description: site-pair object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair.json)
           required: true
           schema:
             $ref: "#/definitions/site-pair"
+    patch:
+      tags:
+        - Network
+      summary: update an existing site-pair
+      description: |
+        Update an existing site-pair
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstanceSitePairsSitePair
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: site-pair-set-id
+          in: path
+          description: Unique id of site pair set.
+          required: true
+          type: string
+          example: __SITE-PAIR-SET-ID__
+        - name: routing-instance-id
+          in: path
+          description: Unique id of routing instance
+          required: true
+          type: string
+          example: __ROUTING-INSTANCE-ID__
+        - name: site-pair-id
+          in: path
+          description: unique identifier of probe
+          required: true
+          type: string
+          example: __SITE-PAIR-ID__
+        - name: body
+          in: body
+          description: site-pair object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/site-pair"
     delete:
       tags:
         - Network
@@ -16016,16 +18598,19 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: site-pair-id
           in: path
           description: unique identifier of probe
           required: true
           type: string
+          example: __SITE-PAIR-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -16045,7 +18630,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/site-pairs"
+              $ref: "#/getDefinitions/site-pairs"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -16054,11 +18639,18 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
+        - name: site-pair-id
+          in: query
+          description:
+          required: false
+          type: string
   /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}/relationship-list/relationship:
     put:
       tags:
@@ -16080,14 +18672,16 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -16112,11 +18706,13 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
   /network/site-pair-sets/site-pair-set/{site-pair-set-id}/routing-instances/routing-instance/{routing-instance-id}:
     get:
       tags:
@@ -16131,7 +18727,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/routing-instance"
+              $ref: "#/getDefinitions/routing-instance"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -16140,16 +18736,21 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
     put:
       tags:
         - Network
       summary: create or update an existing routing-instance
-      description: create or update an existing routing-instance
+      description: |
+        Create or update an existing routing-instance.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance
       consumes:
         - application/json
@@ -16166,17 +18767,64 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: body
           in: body
-          description: routing-instance object that needs to be created or updated
+          description: routing-instance object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance.json)
           required: true
           schema:
             $ref: "#/definitions/routing-instance"
+    patch:
+      tags:
+        - Network
+      summary: update an existing routing-instance
+      description: |
+        Update an existing routing-instance
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkSitePairSetsSitePairSetRoutingInstancesRoutingInstance
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: site-pair-set-id
+          in: path
+          description: Unique id of site pair set.
+          required: true
+          type: string
+          example: __SITE-PAIR-SET-ID__
+        - name: routing-instance-id
+          in: path
+          description: Unique id of routing instance
+          required: true
+          type: string
+          example: __ROUTING-INSTANCE-ID__
+        - name: body
+          in: body
+          description: routing-instance object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/routing-instance"
     delete:
       tags:
         - Network
@@ -16198,11 +18846,13 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: routing-instance-id
           in: path
           description: Unique id of routing instance
           required: true
           type: string
+          example: __ROUTING-INSTANCE-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -16222,7 +18872,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/routing-instances"
+              $ref: "#/getDefinitions/routing-instances"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -16231,6 +18881,12 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
+        - name: routing-instance-id
+          in: query
+          description:
+          required: false
+          type: string
   /network/site-pair-sets/site-pair-set/{site-pair-set-id}/relationship-list/relationship:
     put:
       tags:
@@ -16252,9 +18908,10 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSet.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -16279,6 +18936,7 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
   /network/site-pair-sets/site-pair-set/{site-pair-set-id}:
     get:
       tags:
@@ -16293,7 +18951,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/site-pair-set"
+              $ref: "#/getDefinitions/site-pair-set"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -16302,11 +18960,15 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
     put:
       tags:
         - Network
       summary: create or update an existing site-pair-set
-      description: create or update an existing site-pair-set
+      description: |
+        Create or update an existing site-pair-set.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkSitePairSetsSitePairSet
       consumes:
         - application/json
@@ -16323,12 +18985,52 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: body
           in: body
-          description: site-pair-set object that needs to be created or updated
+          description: site-pair-set object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkSitePairSetsSitePairSet.json)
           required: true
           schema:
             $ref: "#/definitions/site-pair-set"
+    patch:
+      tags:
+        - Network
+      summary: update an existing site-pair-set
+      description: |
+        Update an existing site-pair-set
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkSitePairSetsSitePairSet
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: site-pair-set-id
+          in: path
+          description: Unique id of site pair set.
+          required: true
+          type: string
+          example: __SITE-PAIR-SET-ID__
+        - name: body
+          in: body
+          description: site-pair-set object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/site-pair-set"
     delete:
       tags:
         - Network
@@ -16350,6 +19052,7 @@ paths:
           description: Unique id of site pair set.
           required: true
           type: string
+          example: __SITE-PAIR-SET-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -16369,9 +19072,15 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/site-pair-sets"
+              $ref: "#/getDefinitions/site-pair-sets"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: site-pair-set-id
+          in: query
+          description:
+          required: false
+          type: string
   /network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}/relationship-list/relationship:
     put:
       tags:
@@ -16393,19 +19102,22 @@ paths:
           description: VPN ID, globally unique within A&AI
           required: true
           type: string
+          example: __VPN-ID__
         - name: global-route-target
           in: path
           description: Number used to identify an RT, globally unique in the network
           required: true
           type: string
+          example: __GLOBAL-ROUTE-TARGET__
         - name: route-target-role
           in: path
           description: Role assigned to this route target
           required: true
           type: string
+          example: __ROUTE-TARGET-ROLE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBindingRouteTargetsRouteTarget.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -16430,16 +19142,19 @@ paths:
           description: VPN ID, globally unique within A&AI
           required: true
           type: string
+          example: __VPN-ID__
         - name: global-route-target
           in: path
           description: Number used to identify an RT, globally unique in the network
           required: true
           type: string
+          example: __GLOBAL-ROUTE-TARGET__
         - name: route-target-role
           in: path
           description: Role assigned to this route target
           required: true
           type: string
+          example: __ROUTE-TARGET-ROLE__
   /network/vpn-bindings/vpn-binding/{vpn-id}/route-targets/route-target/{global-route-target}/{route-target-role}:
     get:
       tags:
@@ -16454,7 +19169,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/route-target"
+              $ref: "#/getDefinitions/route-target"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -16463,31 +19178,27 @@ paths:
           description: VPN ID, globally unique within A&AI
           required: true
           type: string
+          example: __VPN-ID__
         - name: global-route-target
           in: path
           description: Number used to identify an RT, globally unique in the network
           required: true
           type: string
+          example: __GLOBAL-ROUTE-TARGET__
         - name: route-target-role
           in: path
           description: Role assigned to this route target
           required: true
           type: string
-        - name: vpn-name
-          in: query
-          description: VPN Name
-          required: false
-          type: string
-        - name: vpn-type
-          in: query
-          description: Type of the vpn, should be taken from enumerated/valid values
-          required: false
-          type: string
+          example: __ROUTE-TARGET-ROLE__
     put:
       tags:
         - Network
       summary: create or update an existing route-target
-      description: create or update an existing route-target
+      description: |
+        Create or update an existing route-target.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVpnBindingsVpnBindingRouteTargetsRouteTarget
       consumes:
         - application/json
@@ -16504,22 +19215,76 @@ paths:
           description: VPN ID, globally unique within A&AI
           required: true
           type: string
+          example: __VPN-ID__
         - name: global-route-target
           in: path
           description: Number used to identify an RT, globally unique in the network
           required: true
           type: string
+          example: __GLOBAL-ROUTE-TARGET__
         - name: route-target-role
           in: path
           description: Role assigned to this route target
           required: true
           type: string
+          example: __ROUTE-TARGET-ROLE__
         - name: body
           in: body
-          description: route-target object that needs to be created or updated
+          description: route-target object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBindingRouteTargetsRouteTarget.json)
           required: true
           schema:
             $ref: "#/definitions/route-target"
+    patch:
+      tags:
+        - Network
+      summary: update an existing route-target
+      description: |
+        Update an existing route-target
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVpnBindingsVpnBindingRouteTargetsRouteTarget
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vpn-id
+          in: path
+          description: VPN ID, globally unique within A&AI
+          required: true
+          type: string
+          example: __VPN-ID__
+        - name: global-route-target
+          in: path
+          description: Number used to identify an RT, globally unique in the network
+          required: true
+          type: string
+          example: __GLOBAL-ROUTE-TARGET__
+        - name: route-target-role
+          in: path
+          description: Role assigned to this route target
+          required: true
+          type: string
+          example: __ROUTE-TARGET-ROLE__
+        - name: body
+          in: body
+          description: route-target object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/route-target"
     delete:
       tags:
         - Network
@@ -16541,16 +19306,19 @@ paths:
           description: VPN ID, globally unique within A&AI
           required: true
           type: string
+          example: __VPN-ID__
         - name: global-route-target
           in: path
           description: Number used to identify an RT, globally unique in the network
           required: true
           type: string
+          example: __GLOBAL-ROUTE-TARGET__
         - name: route-target-role
           in: path
           description: Role assigned to this route target
           required: true
           type: string
+          example: __ROUTE-TARGET-ROLE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -16570,7 +19338,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/route-targets"
+              $ref: "#/getDefinitions/route-targets"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -16579,16 +19347,7 @@ paths:
           description: VPN ID, globally unique within A&AI
           required: true
           type: string
-        - name: vpn-name
-          in: query
-          description: VPN Name
-          required: false
-          type: string
-        - name: vpn-type
-          in: query
-          description: Type of the vpn, should be taken from enumerated/valid values
-          required: false
-          type: string
+          example: __VPN-ID__
   /network/vpn-bindings/vpn-binding/{vpn-id}/relationship-list/relationship:
     put:
       tags:
@@ -16610,9 +19369,10 @@ paths:
           description: VPN ID, globally unique within A&AI
           required: true
           type: string
+          example: __VPN-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBinding.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -16637,6 +19397,7 @@ paths:
           description: VPN ID, globally unique within A&AI
           required: true
           type: string
+          example: __VPN-ID__
   /network/vpn-bindings/vpn-binding/{vpn-id}:
     get:
       tags:
@@ -16651,7 +19412,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vpn-binding"
+              $ref: "#/getDefinitions/vpn-binding"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -16660,21 +19421,15 @@ paths:
           description: VPN ID, globally unique within A&AI
           required: true
           type: string
-        - name: vpn-name
-          in: query
-          description: VPN Name
-          required: false
-          type: string
-        - name: vpn-type
-          in: query
-          description: Type of the vpn, should be taken from enumerated/valid values
-          required: false
-          type: string
+          example: __VPN-ID__
     put:
       tags:
         - Network
       summary: create or update an existing vpn-binding
-      description: create or update an existing vpn-binding
+      description: |
+        Create or update an existing vpn-binding.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVpnBindingsVpnBinding
       consumes:
         - application/json
@@ -16691,12 +19446,52 @@ paths:
           description: VPN ID, globally unique within A&AI
           required: true
           type: string
+          example: __VPN-ID__
         - name: body
           in: body
-          description: vpn-binding object that needs to be created or updated
+          description: vpn-binding object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVpnBindingsVpnBinding.json)
           required: true
           schema:
             $ref: "#/definitions/vpn-binding"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vpn-binding
+      description: |
+        Update an existing vpn-binding
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVpnBindingsVpnBinding
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vpn-id
+          in: path
+          description: VPN ID, globally unique within A&AI
+          required: true
+          type: string
+          example: __VPN-ID__
+        - name: body
+          in: body
+          description: vpn-binding object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vpn-binding"
     delete:
       tags:
         - Network
@@ -16718,6 +19513,7 @@ paths:
           description: VPN ID, globally unique within A&AI
           required: true
           type: string
+          example: __VPN-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -16737,9 +19533,25 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vpn-bindings"
+              $ref: "#/getDefinitions/vpn-bindings"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vpn-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vpn-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vpn-type
+          in: query
+          description:
+          required: false
+          type: string
   /network/vpls-pes/vpls-pe/{equipment-name}/relationship-list/relationship:
     put:
       tags:
@@ -16760,9 +19572,10 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPe.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -16786,6 +19599,7 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
   /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
     put:
       tags:
@@ -16806,14 +19620,16 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -16837,11 +19653,13 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
     put:
       tags:
@@ -16862,24 +19680,28 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -16903,21 +19725,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
   /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -16938,29 +19764,34 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -16984,26 +19815,31 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -17018,7 +19854,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -17026,84 +19862,102 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
       tags:
         - Network
-      summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
-      operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -17118,32 +19972,37 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv4-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - Network
@@ -17164,26 +20023,31 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -17209,29 +20073,34 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -17255,26 +20124,31 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -17289,7 +20163,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -17297,84 +20171,102 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
       tags:
         - Network
-      summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
-      operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
       consumes:
         - application/json
         - application/xml
@@ -17389,32 +20281,37 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv6-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -17435,26 +20332,31 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -17474,7 +20376,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlan"
+              $ref: "#/getDefinitions/vlan"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -17482,62 +20384,33 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
+          example: __VLAN-INTERFACE__
     put:
       tags:
         - Network
       summary: create or update an existing vlan
-      description: create or update an existing vlan
+      description: |
+        Create or update an existing vlan.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
       consumes:
         - application/json
@@ -17553,27 +20426,87 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: vlan object that needs to be created or updated
+          description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/vlan"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vlan
+      description: |
+        Update an existing vlan
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: body
+          in: body
+          description: vlan object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vlan"
     delete:
       tags:
         - Network
@@ -17594,21 +20527,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -17628,7 +20565,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlans"
+              $ref: "#/getDefinitions/vlans"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -17636,39 +20573,33 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vlan-id-inner
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: integer
+          format: int64
+        - name: vpn-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}/relationship-list/relationship:
@@ -17691,24 +20622,28 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -17732,21 +20667,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
   /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
     get:
       tags:
@@ -17761,7 +20700,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vf"
+              $ref: "#/getDefinitions/sriov-vf"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -17769,71 +20708,33 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vf-vlan-filter
-          in: query
-          description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
-          required: false
-          type: string
-        - name: vf-mac-filter
-          in: query
-          description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
-          required: false
-          type: string
-        - name: vf-vlan-strip
-          in: query
-          description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
-          required: false
-          type: boolean
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface
-          required: false
-          type: string
+          example: __PCI-ID__
     put:
       tags:
         - Network
       summary: create or update an existing sriov-vf
-      description: create or update an existing sriov-vf
+      description: |
+        Create or update an existing sriov-vf.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
       consumes:
         - application/json
@@ -17849,27 +20750,87 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: sriov-vf object that needs to be created or updated
+          description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/sriov-vf"
+    patch:
+      tags:
+        - Network
+      summary: update an existing sriov-vf
+      description: |
+        Update an existing sriov-vf
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: pci-id
+          in: path
+          description: PCI ID used to identify the sriov-vf
+          required: true
+          type: string
+          example: __PCI-ID__
+        - name: body
+          in: body
+          description: sriov-vf object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/sriov-vf"
     delete:
       tags:
         - Network
@@ -17890,21 +20851,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -17924,7 +20889,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vfs"
+              $ref: "#/getDefinitions/sriov-vfs"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -17932,39 +20897,42 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: prov-status
+          example: __INTERFACE-NAME__
+        - name: pci-id
           in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+          description:
           required: false
           type: string
-        - name: prov-status
+        - name: vf-vlan-filter
           in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
+          description:
           required: false
           type: string
-        - name: interface-id
+        - name: vf-mac-filter
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vf-vlan-strip
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: boolean
+        - name: neutron-network-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/relationship-list/relationship:
@@ -17987,19 +20955,22 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -18023,16 +20994,19 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -18053,24 +21027,28 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -18094,21 +21072,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -18123,7 +21105,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -18131,67 +21113,33 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
       consumes:
         - application/json
@@ -18207,27 +21155,87 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - Network
@@ -18248,21 +21256,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -18288,24 +21300,28 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -18329,21 +21345,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -18358,7 +21378,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -18366,67 +21386,33 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -18442,27 +21428,87 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -18483,21 +21529,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -18517,7 +21567,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interface"
+              $ref: "#/getDefinitions/l-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -18525,83 +21575,117 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
+          example: __INTERFACE-NAME__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing l-interface
+      description: |
+        Create or update an existing l-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
           type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l-interface"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l-interface
+      description: |
+        Update an existing l-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
           type: string
-    put:
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: l-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l-interface"
+    delete:
       tags:
         - Network
-      summary: create or update an existing l-interface
-      description: create or update an existing l-interface
-      operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
-      consumes:
-        - application/json
-        - application/xml
-      produces:
-        - application/json
-        - application/xml
-      responses:
-        "default":
-          description: Response codes found in [response codes](https://wiki.onap.org/).
-      parameters:
-        - name: equipment-name
-          in: path
-          required: true
-          type: string
-        - name: interface-name
-          in: path
-          description: Name that identifies the physical interface
-          required: true
-          type: string
-        - name: interface-name
-          in: path
-          description: Name given to the interface
-          required: true
-          type: string
-        - name: body
-          in: body
-          description: l-interface object that needs to be created or updated
-          required: true
-          schema:
-            $ref: "#/definitions/l-interface"
-    delete:
-      tags:
-        - Network
-      summary: delete an existing l-interface
-      description: delete an existing l-interface
-      operationId: deleteNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
+      summary: delete an existing l-interface
+      description: delete an existing l-interface
+      operationId: deleteNetworkVplsPesVplsPePInterfacesPInterfaceLInterfacesLInterface
       consumes:
         - application/json
         - application/xml
@@ -18616,16 +21700,19 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -18645,7 +21732,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interfaces"
+              $ref: "#/getDefinitions/l-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -18653,19 +21740,31 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
-        - name: prov-status
+          example: __INTERFACE-NAME__
+        - name: interface-name
           in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+          description:
           required: false
           type: string
-        - name: prov-status
+        - name: interface-id
           in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
+          description:
+          required: false
+          type: string
+        - name: macaddr
+          in: query
+          description:
+          required: false
+          type: string
+        - name: network-name
+          in: query
+          description:
           required: false
           type: string
   /network/vpls-pes/vpls-pe/{equipment-name}/p-interfaces/p-interface/{interface-name}:
@@ -18682,7 +21781,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/p-interface"
+              $ref: "#/getDefinitions/p-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -18690,26 +21789,21 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing p-interface
-      description: create or update an existing p-interface
+      description: |
+        Create or update an existing p-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPePInterfacesPInterface
       consumes:
         - application/json
@@ -18725,17 +21819,63 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: p-interface object that needs to be created or updated
+          description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPePInterfacesPInterface.json)
           required: true
           schema:
             $ref: "#/definitions/p-interface"
+    patch:
+      tags:
+        - Network
+      summary: update an existing p-interface
+      description: |
+        Update an existing p-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPePInterfacesPInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: p-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/p-interface"
     delete:
       tags:
         - Network
@@ -18756,11 +21896,13 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -18780,7 +21922,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/p-interfaces"
+              $ref: "#/getDefinitions/p-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -18788,9 +21930,15 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: query
+          description:
+          required: false
+          type: string
         - name: prov-status
           in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+          description:
           required: false
           type: string
   /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/relationship-list/relationship:
@@ -18813,14 +21961,16 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -18844,11 +21994,13 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
     put:
       tags:
@@ -18869,24 +22021,28 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -18910,21 +22066,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
   /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -18945,29 +22105,34 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -18991,26 +22156,31 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -19025,7 +22195,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -19033,88 +22203,39 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
@@ -19130,38 +22251,54 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv4-address-list"
-    delete:
+    patch:
       tags:
         - Network
-      summary: delete an existing l3-interface-ipv4-address-list
-      description: delete an existing l3-interface-ipv4-address-list
-      operationId: deleteNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -19176,37 +22313,43 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: resource-version
-          in: query
-          description: resource-version for concurrency
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be updated.
           required: true
-          type: string
-  /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}/relationship-list/relationship:
-    put:
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
+    delete:
       tags:
         - Network
-      summary: see node definition for valid relationships
-      operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressListRelationshipListRelationship
+      summary: delete an existing l3-interface-ipv4-address-list
+      description: delete an existing l3-interface-ipv4-address-list
+      operationId: deleteNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -19221,38 +22364,42 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
-        - name: l3-interface-ipv6-address
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: body
-          in: body
-          description: relationship object that needs to be created or updated
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: resource-version
+          in: query
+          description: resource-version for concurrency
           required: true
-          schema:
-            $ref: "#/definitions/relationship"
-    delete:
+          type: string
+  /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}/relationship-list/relationship:
+    put:
       tags:
         - Network
-      summary: delete an existing relationship
-      description: delete an existing relationship
-      operationId: deleteNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressListRelationshipListRelationship
+      summary: see node definition for valid relationships
+      operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressListRelationshipListRelationship
       consumes:
         - application/json
         - application/xml
@@ -19267,131 +22414,43 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-  /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
-    get:
-      tags:
-        - Network
-      summary: returns l3-interface-ipv6-address-list
-      description: returns l3-interface-ipv6-address-list
-      operationId: getNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
-      produces:
-        - application/json
-        - application/xml
-      responses:
-        "200":
-          description: successful operation
-          schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
-        "default":
-          description: Response codes found in [response codes](https://wiki.onap.org/).
-      parameters:
-        - name: equipment-name
-          in: path
-          required: true
-          type: string
-        - name: interface-name
-          in: path
-          description: Name that identifies the link aggregate interface
-          required: true
-          type: string
-        - name: interface-name
-          in: path
-          description: Name given to the interface
-          required: true
-          type: string
-        - name: vlan-interface
-          in: path
-          description: String that identifies the interface
-          required: true
-          type: string
-        - name: l3-interface-ipv6-address
-          in: path
-          description: IP address
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
-    put:
+          schema:
+            $ref: "#/definitions/relationship"
+    delete:
       tags:
         - Network
-      summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
-      operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      summary: delete an existing relationship
+      description: delete an existing relationship
+      operationId: deleteNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressListRelationshipListRelationship
       consumes:
         - application/json
         - application/xml
@@ -19406,32 +22465,194 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+  /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
+    get:
+      tags:
+        - Network
+      summary: returns l3-interface-ipv6-address-list
+      description: returns l3-interface-ipv6-address-list
+      operationId: getNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "200":
+          description: successful operation
+          schema:
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -19452,26 +22673,31 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -19491,7 +22717,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlan"
+              $ref: "#/getDefinitions/vlan"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -19499,67 +22725,33 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
+          example: __VLAN-INTERFACE__
     put:
       tags:
         - Network
       summary: create or update an existing vlan
-      description: create or update an existing vlan
+      description: |
+        Create or update an existing vlan.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
       consumes:
         - application/json
@@ -19575,27 +22767,87 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: vlan object that needs to be created or updated
+          description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/vlan"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vlan
+      description: |
+        Update an existing vlan
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: body
+          in: body
+          description: vlan object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vlan"
     delete:
       tags:
         - Network
@@ -19616,21 +22868,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -19650,7 +22906,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlans"
+              $ref: "#/getDefinitions/vlans"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -19658,44 +22914,33 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vlan-id-inner
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: integer
+          format: int64
+        - name: vpn-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}/relationship-list/relationship:
@@ -19718,24 +22963,28 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -19759,21 +23008,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
   /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
     get:
       tags:
@@ -19788,7 +23041,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vf"
+              $ref: "#/getDefinitions/sriov-vf"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -19796,76 +23049,33 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vf-vlan-filter
-          in: query
-          description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
-          required: false
-          type: string
-        - name: vf-mac-filter
-          in: query
-          description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
-          required: false
-          type: string
-        - name: vf-vlan-strip
-          in: query
-          description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
-          required: false
-          type: boolean
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface
-          required: false
-          type: string
+          example: __PCI-ID__
     put:
       tags:
         - Network
       summary: create or update an existing sriov-vf
-      description: create or update an existing sriov-vf
+      description: |
+        Create or update an existing sriov-vf.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
       consumes:
         - application/json
@@ -19881,27 +23091,87 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: sriov-vf object that needs to be created or updated
+          description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/sriov-vf"
+    patch:
+      tags:
+        - Network
+      summary: update an existing sriov-vf
+      description: |
+        Update an existing sriov-vf
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: pci-id
+          in: path
+          description: PCI ID used to identify the sriov-vf
+          required: true
+          type: string
+          example: __PCI-ID__
+        - name: body
+          in: body
+          description: sriov-vf object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/sriov-vf"
     delete:
       tags:
         - Network
@@ -19922,21 +23192,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -19956,7 +23230,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vfs"
+              $ref: "#/getDefinitions/sriov-vfs"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -19964,44 +23238,42 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: pci-id
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: interface-role
+        - name: vf-vlan-filter
           in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+          description:
           required: false
           type: string
-        - name: interface-id
+        - name: vf-mac-filter
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vf-vlan-strip
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: boolean
+        - name: neutron-network-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/relationship-list/relationship:
@@ -20024,19 +23296,22 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -20060,16 +23335,19 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -20090,24 +23368,28 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -20131,21 +23413,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -20160,7 +23446,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -20168,72 +23454,33 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
       consumes:
         - application/json
@@ -20249,27 +23496,87 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - Network
@@ -20290,21 +23597,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -20330,24 +23641,28 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -20371,21 +23686,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -20400,7 +23719,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -20408,72 +23727,33 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -20489,27 +23769,87 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -20530,21 +23870,25 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -20564,7 +23908,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interface"
+              $ref: "#/getDefinitions/l-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -20572,51 +23916,27 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing l-interface
-      description: create or update an existing l-interface
+      description: |
+        Create or update an existing l-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface
       consumes:
         - application/json
@@ -20632,22 +23952,75 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: l-interface object that needs to be created or updated
+          description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/l-interface"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l-interface
+      description: |
+        Update an existing l-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterfaceLInterfacesLInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: l-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l-interface"
     delete:
       tags:
         - Network
@@ -20668,16 +24041,19 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -20697,7 +24073,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interfaces"
+              $ref: "#/getDefinitions/l-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -20705,24 +24081,31 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
-        - name: prov-status
+          example: __INTERFACE-NAME__
+        - name: interface-name
           in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+          description:
           required: false
           type: string
         - name: interface-id
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: interface-role
+        - name: macaddr
+          in: query
+          description:
+          required: false
+          type: string
+        - name: network-name
           in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+          description:
           required: false
           type: string
   /network/vpls-pes/vpls-pe/{equipment-name}/lag-interfaces/lag-interface/{interface-name}:
@@ -20739,7 +24122,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/lag-interface"
+              $ref: "#/getDefinitions/lag-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -20747,31 +24130,21 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing lag-interface
-      description: create or update an existing lag-interface
+      description: |
+        Create or update an existing lag-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPeLagInterfacesLagInterface
       consumes:
         - application/json
@@ -20787,17 +24160,63 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: lag-interface object that needs to be created or updated
+          description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPeLagInterfacesLagInterface.json)
           required: true
           schema:
             $ref: "#/definitions/lag-interface"
+    patch:
+      tags:
+        - Network
+      summary: update an existing lag-interface
+      description: |
+        Update an existing lag-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPeLagInterfacesLagInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: lag-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/lag-interface"
     delete:
       tags:
         - Network
@@ -20818,11 +24237,13 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -20842,7 +24263,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/lag-interfaces"
+              $ref: "#/getDefinitions/lag-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -20850,9 +24271,20 @@ paths:
           in: path
           required: true
           type: string
-        - name: prov-status
+          example: __EQUIPMENT-NAME__
+        - name: interface-name
           in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+          description:
+          required: false
+          type: string
+        - name: interface-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: interface-role
+          in: query
+          description:
           required: false
           type: string
   /network/vpls-pes/vpls-pe/{equipment-name}:
@@ -20869,7 +24301,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vpls-pe"
+              $ref: "#/getDefinitions/vpls-pe"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -20877,16 +24309,15 @@ paths:
           in: path
           required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
+          example: __EQUIPMENT-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing vpls-pe
-      description: create or update an existing vpls-pe
+      description: |
+        Create or update an existing vpls-pe.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVplsPesVplsPe
       consumes:
         - application/json
@@ -20902,12 +24333,51 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: body
           in: body
-          description: vpls-pe object that needs to be created or updated
+          description: vpls-pe object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVplsPesVplsPe.json)
           required: true
           schema:
             $ref: "#/definitions/vpls-pe"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vpls-pe
+      description: |
+        Update an existing vpls-pe
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVplsPesVplsPe
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: path
+          required: true
+          type: string
+          example: __EQUIPMENT-NAME__
+        - name: body
+          in: body
+          description: vpls-pe object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vpls-pe"
     delete:
       tags:
         - Network
@@ -20928,6 +24398,7 @@ paths:
           in: path
           required: true
           type: string
+          example: __EQUIPMENT-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -20947,9 +24418,20 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vpls-pes"
+              $ref: "#/getDefinitions/vpls-pes"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: equipment-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: prov-status
+          in: query
+          description:
+          required: false
+          type: string
   /network/multicast-configurations/multicast-configuration/{multicast-configuration-id}/relationship-list/relationship:
     put:
       tags:
@@ -20971,9 +24453,10 @@ paths:
           description: Unique id of multicast configuration.
           required: true
           type: string
+          example: __MULTICAST-CONFIGURATION-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkMulticastConfigurationsMulticastConfiguration.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -20998,6 +24481,7 @@ paths:
           description: Unique id of multicast configuration.
           required: true
           type: string
+          example: __MULTICAST-CONFIGURATION-ID__
   /network/multicast-configurations/multicast-configuration/{multicast-configuration-id}:
     get:
       tags:
@@ -21012,7 +24496,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/multicast-configuration"
+              $ref: "#/getDefinitions/multicast-configuration"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -21021,11 +24505,15 @@ paths:
           description: Unique id of multicast configuration.
           required: true
           type: string
+          example: __MULTICAST-CONFIGURATION-ID__
     put:
       tags:
         - Network
       summary: create or update an existing multicast-configuration
-      description: create or update an existing multicast-configuration
+      description: |
+        Create or update an existing multicast-configuration.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkMulticastConfigurationsMulticastConfiguration
       consumes:
         - application/json
@@ -21042,12 +24530,52 @@ paths:
           description: Unique id of multicast configuration.
           required: true
           type: string
+          example: __MULTICAST-CONFIGURATION-ID__
         - name: body
           in: body
-          description: multicast-configuration object that needs to be created or updated
+          description: multicast-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkMulticastConfigurationsMulticastConfiguration.json)
           required: true
           schema:
             $ref: "#/definitions/multicast-configuration"
+    patch:
+      tags:
+        - Network
+      summary: update an existing multicast-configuration
+      description: |
+        Update an existing multicast-configuration
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkMulticastConfigurationsMulticastConfiguration
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: multicast-configuration-id
+          in: path
+          description: Unique id of multicast configuration.
+          required: true
+          type: string
+          example: __MULTICAST-CONFIGURATION-ID__
+        - name: body
+          in: body
+          description: multicast-configuration object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/multicast-configuration"
     delete:
       tags:
         - Network
@@ -21069,6 +24597,7 @@ paths:
           description: Unique id of multicast configuration.
           required: true
           type: string
+          example: __MULTICAST-CONFIGURATION-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -21088,9 +24617,15 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/multicast-configurations"
+              $ref: "#/getDefinitions/multicast-configurations"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: multicast-configuration-id
+          in: query
+          description:
+          required: false
+          type: string
   /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}/relationship-list/relationship:
     put:
       tags:
@@ -21112,20 +24647,23 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-id
           in: path
           description: Unique ID of the interface
           required: true
           type: string
+          example: __INTERFACE-ID__
         - name: cvlan-tag
           in: path
           description: See mis-na-virtualization-platform.yang
           required: true
           type: integer
           format: int64
+          example: __CVLAN-TAG__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -21150,17 +24688,20 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-id
           in: path
           description: Unique ID of the interface
           required: true
           type: string
+          example: __INTERFACE-ID__
         - name: cvlan-tag
           in: path
           description: See mis-na-virtualization-platform.yang
           required: true
           type: integer
           format: int64
+          example: __CVLAN-TAG__
   /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/cvlan-tags/cvlan-tag-entry/{cvlan-tag}:
     get:
       tags:
@@ -21175,7 +24716,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/cvlan-tag-entry"
+              $ref: "#/getDefinitions/cvlan-tag-entry"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -21184,77 +24725,28 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-id
           in: path
           description: Unique ID of the interface
           required: true
           type: string
+          example: __INTERFACE-ID__
         - name: cvlan-tag
           in: path
           description: See mis-na-virtualization-platform.yang
           required: true
           type: integer
           format: int64
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: vpe-id
-          in: query
-          description: Unique ID of VPE connected to this VCE.
-          required: false
-          type: string
-        - name: port-group-id
-          in: query
-          description: Unique ID for port group in vmware
-          required: false
-          type: string
-        - name: switch-name
-          in: query
-          description: DVS or standard switch name (should be non-null for port groups associated with DVS)
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
+          example: __CVLAN-TAG__
     put:
       tags:
         - Network
       summary: create or update an existing cvlan-tag-entry
-      description: create or update an existing cvlan-tag-entry
+      description: |
+        Create or update an existing cvlan-tag-entry.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry
       consumes:
         - application/json
@@ -21271,23 +24763,78 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-id
           in: path
           description: Unique ID of the interface
           required: true
           type: string
+          example: __INTERFACE-ID__
         - name: cvlan-tag
           in: path
           description: See mis-na-virtualization-platform.yang
           required: true
           type: integer
           format: int64
+          example: __CVLAN-TAG__
         - name: body
           in: body
-          description: cvlan-tag-entry object that needs to be created or updated
+          description: cvlan-tag-entry object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry.json)
           required: true
           schema:
             $ref: "#/definitions/cvlan-tag-entry"
+    patch:
+      tags:
+        - Network
+      summary: update an existing cvlan-tag-entry
+      description: |
+        Update an existing cvlan-tag-entry
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVcesVcePortGroupsPortGroupCvlanTagsCvlanTagEntry
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-id
+          in: path
+          description: Unique ID of the interface
+          required: true
+          type: string
+          example: __INTERFACE-ID__
+        - name: cvlan-tag
+          in: path
+          description: See mis-na-virtualization-platform.yang
+          required: true
+          type: integer
+          format: int64
+          example: __CVLAN-TAG__
+        - name: body
+          in: body
+          description: cvlan-tag-entry object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/cvlan-tag-entry"
     delete:
       tags:
         - Network
@@ -21309,17 +24856,20 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-id
           in: path
           description: Unique ID of the interface
           required: true
           type: string
+          example: __INTERFACE-ID__
         - name: cvlan-tag
           in: path
           description: See mis-na-virtualization-platform.yang
           required: true
           type: integer
           format: int64
+          example: __CVLAN-TAG__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -21339,7 +24889,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/cvlan-tags"
+              $ref: "#/getDefinitions/cvlan-tags"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -21348,66 +24898,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-id
           in: path
           description: Unique ID of the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: vpe-id
-          in: query
-          description: Unique ID of VPE connected to this VCE.
-          required: false
-          type: string
-        - name: port-group-id
-          in: query
-          description: Unique ID for port group in vmware
-          required: false
-          type: string
-        - name: switch-name
-          in: query
-          description: DVS or standard switch name (should be non-null for port groups associated with DVS)
-          required: false
-          type: string
-        - name: heat-stack-id
+          example: __INTERFACE-ID__
+        - name: cvlan-tag
           in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
+          description:
           required: false
-          type: string
+          type: integer
+          format: int64
   /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}/relationship-list/relationship:
     put:
       tags:
@@ -21429,14 +24932,16 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-id
           in: path
           description: Unique ID of the interface
           required: true
           type: string
+          example: __INTERFACE-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroup.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -21461,11 +24966,13 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-id
           in: path
           description: Unique ID of the interface
           required: true
           type: string
+          example: __INTERFACE-ID__
   /network/vces/vce/{vnf-id}/port-groups/port-group/{interface-id}:
     get:
       tags:
@@ -21480,7 +24987,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/port-group"
+              $ref: "#/getDefinitions/port-group"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -21489,71 +24996,21 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-id
           in: path
           description: Unique ID of the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: vpe-id
-          in: query
-          description: Unique ID of VPE connected to this VCE.
-          required: false
-          type: string
-        - name: port-group-id
-          in: query
-          description: Unique ID for port group in vmware
-          required: false
-          type: string
-        - name: switch-name
-          in: query
-          description: DVS or standard switch name (should be non-null for port groups associated with DVS)
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
+          example: __INTERFACE-ID__
     put:
       tags:
         - Network
       summary: create or update an existing port-group
-      description: create or update an existing port-group
+      description: |
+        Create or update an existing port-group.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVcesVcePortGroupsPortGroup
       consumes:
         - application/json
@@ -21570,17 +25027,64 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-id
           in: path
           description: Unique ID of the interface
           required: true
           type: string
+          example: __INTERFACE-ID__
         - name: body
           in: body
-          description: port-group object that needs to be created or updated
+          description: port-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVcePortGroupsPortGroup.json)
           required: true
           schema:
             $ref: "#/definitions/port-group"
+    patch:
+      tags:
+        - Network
+      summary: update an existing port-group
+      description: |
+        Update an existing port-group
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVcesVcePortGroupsPortGroup
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-id
+          in: path
+          description: Unique ID of the interface
+          required: true
+          type: string
+          example: __INTERFACE-ID__
+        - name: body
+          in: body
+          description: port-group object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/port-group"
     delete:
       tags:
         - Network
@@ -21602,11 +25106,13 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-id
           in: path
           description: Unique ID of the interface
           required: true
           type: string
+          example: __INTERFACE-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -21626,7 +25132,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/port-groups"
+              $ref: "#/getDefinitions/port-groups"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -21635,44 +25141,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
+          example: __VNF-ID__
+        - name: interface-id
           in: query
-          description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+          description:
           required: false
           type: string
-        - name: regional-resource-zone
+        - name: port-group-id
           in: query
-          description: Regional way of organizing pservers, source of truth should define values
+          description:
           required: false
           type: string
-        - name: prov-status
+        - name: switch-name
           in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
+          description:
           required: false
           type: string
         - name: heat-stack-id
           in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: vpe-id
-          in: query
-          description: Unique ID of VPE connected to this VCE.
+          description:
           required: false
           type: string
   /network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}/relationship-list/relationship:
@@ -21696,19 +25183,22 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the license group the resource belongs to, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of a license resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceLicensesLicense.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -21733,16 +25223,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the license group the resource belongs to, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of a license resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
   /network/vces/vce/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}:
     get:
       tags:
@@ -21757,7 +25250,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/license"
+              $ref: "#/getDefinitions/license"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -21766,61 +25259,27 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the license group the resource belongs to, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of a license resource. 
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: vpe-id
-          in: query
-          description: Unique ID of VPE connected to this VCE.
-          required: false
-          type: string
+          example: __RESOURCE-UUID__
     put:
       tags:
         - Network
       summary: create or update an existing license
-      description: create or update an existing license
+      description: |
+        Create or update an existing license.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVcesVceLicensesLicense
       consumes:
         - application/json
@@ -21837,22 +25296,76 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the license group the resource belongs to, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of a license resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
         - name: body
           in: body
-          description: license object that needs to be created or updated
+          description: license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceLicensesLicense.json)
           required: true
           schema:
             $ref: "#/definitions/license"
+    patch:
+      tags:
+        - Network
+      summary: update an existing license
+      description: |
+        Update an existing license
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVcesVceLicensesLicense
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: group-uuid
+          in: path
+          description: Unique ID for the license group the resource belongs to, should be uuid.
+          required: true
+          type: string
+          example: __GROUP-UUID__
+        - name: resource-uuid
+          in: path
+          description: Unique ID of a license resource. 
+          required: true
+          type: string
+          example: __RESOURCE-UUID__
+        - name: body
+          in: body
+          description: license object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/license"
     delete:
       tags:
         - Network
@@ -21874,16 +25387,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the license group the resource belongs to, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of a license resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -21903,7 +25419,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/licenses"
+              $ref: "#/getDefinitions/licenses"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -21912,44 +25428,15 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
+          example: __VNF-ID__
+        - name: group-uuid
           in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
+          description:
           required: false
           type: string
-        - name: vpe-id
+        - name: resource-uuid
           in: query
-          description: Unique ID of VPE connected to this VCE.
+          description:
           required: false
           type: string
   /network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}/relationship-list/relationship:
@@ -21973,19 +25460,22 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the entitlement group the resource comes from, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of an entitlement resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceEntitlementsEntitlement.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -22010,16 +25500,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the entitlement group the resource comes from, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of an entitlement resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
   /network/vces/vce/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}:
     get:
       tags:
@@ -22034,7 +25527,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/entitlement"
+              $ref: "#/getDefinitions/entitlement"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -22043,61 +25536,27 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the entitlement group the resource comes from, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of an entitlement resource. 
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: vpe-id
-          in: query
-          description: Unique ID of VPE connected to this VCE.
-          required: false
-          type: string
+          example: __RESOURCE-UUID__
     put:
       tags:
         - Network
       summary: create or update an existing entitlement
-      description: create or update an existing entitlement
+      description: |
+        Create or update an existing entitlement.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVcesVceEntitlementsEntitlement
       consumes:
         - application/json
@@ -22114,22 +25573,76 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the entitlement group the resource comes from, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of an entitlement resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
         - name: body
           in: body
-          description: entitlement object that needs to be created or updated
+          description: entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVceEntitlementsEntitlement.json)
           required: true
           schema:
             $ref: "#/definitions/entitlement"
+    patch:
+      tags:
+        - Network
+      summary: update an existing entitlement
+      description: |
+        Update an existing entitlement
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVcesVceEntitlementsEntitlement
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: group-uuid
+          in: path
+          description: Unique ID for the entitlement group the resource comes from, should be uuid.
+          required: true
+          type: string
+          example: __GROUP-UUID__
+        - name: resource-uuid
+          in: path
+          description: Unique ID of an entitlement resource. 
+          required: true
+          type: string
+          example: __RESOURCE-UUID__
+        - name: body
+          in: body
+          description: entitlement object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/entitlement"
     delete:
       tags:
         - Network
@@ -22151,16 +25664,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the entitlement group the resource comes from, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of an entitlement resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -22180,7 +25696,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/entitlements"
+              $ref: "#/getDefinitions/entitlements"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -22189,44 +25705,15 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
+          example: __VNF-ID__
+        - name: group-uuid
           in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
+          description:
           required: false
           type: string
-        - name: vpe-id
+        - name: resource-uuid
           in: query
-          description: Unique ID of VPE connected to this VCE.
+          description:
           required: false
           type: string
   /network/vces/vce/{vnf-id}/relationship-list/relationship:
@@ -22250,9 +25737,10 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVce.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -22277,6 +25765,7 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
   /network/vces/vce/{vnf-id}:
     get:
       tags:
@@ -22291,7 +25780,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vce"
+              $ref: "#/getDefinitions/vce"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -22300,51 +25789,15 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: vpe-id
-          in: query
-          description: Unique ID of VPE connected to this VCE.
-          required: false
-          type: string
+          example: __VNF-ID__
     put:
       tags:
         - Network
       summary: create or update an existing vce
-      description: create or update an existing vce
+      description: |
+        Create or update an existing vce.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVcesVce
       consumes:
         - application/json
@@ -22361,12 +25814,52 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: body
           in: body
-          description: vce object that needs to be created or updated
+          description: vce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVcesVce.json)
           required: true
           schema:
             $ref: "#/definitions/vce"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vce
+      description: |
+        Update an existing vce
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVcesVce
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: body
+          in: body
+          description: vce object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vce"
     delete:
       tags:
         - Network
@@ -22388,6 +25881,7 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -22407,9 +25901,55 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vces"
+              $ref: "#/getDefinitions/vces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vnf-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vnf-name2
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vnf-type
+          in: query
+          description:
+          required: false
+          type: string
+        - name: service-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: regional-resource-zone
+          in: query
+          description:
+          required: false
+          type: string
+        - name: prov-status
+          in: query
+          description:
+          required: false
+          type: string
+        - name: heat-stack-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vpe-id
+          in: query
+          description:
+          required: false
+          type: string
   /network/vnfcs/vnfc/{vnfc-name}/relationship-list/relationship:
     put:
       tags:
@@ -22431,9 +25971,10 @@ paths:
           description: Unique ID of vnfc.
           required: true
           type: string
+          example: __VNFC-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVnfcsVnfc.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -22458,6 +25999,7 @@ paths:
           description: Unique ID of vnfc.
           required: true
           type: string
+          example: __VNFC-NAME__
   /network/vnfcs/vnfc/{vnfc-name}:
     get:
       tags:
@@ -22472,7 +26014,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vnfc"
+              $ref: "#/getDefinitions/vnfc"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -22481,44 +26023,15 @@ paths:
           description: Unique ID of vnfc.
           required: true
           type: string
-        - name: vnfc-function-code
-          in: query
-          description: function code
-          required: false
-          type: string
-        - name: vnfc-type
-          in: query
-          description: type
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: prov status of this vnfc
-          required: false
-          type: string
-        - name: ipaddress-v4-oam-vip
-          in: query
-          description: Oam V4 vip address of this vnfc
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: group-notation
-          in: query
-          description: Group notation of VNFC
-          required: false
-          type: string
+          example: __VNFC-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing vnfc
-      description: create or update an existing vnfc
+      description: |
+        Create or update an existing vnfc.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkVnfcsVnfc
       consumes:
         - application/json
@@ -22535,12 +26048,52 @@ paths:
           description: Unique ID of vnfc.
           required: true
           type: string
+          example: __VNFC-NAME__
         - name: body
           in: body
-          description: vnfc object that needs to be created or updated
+          description: vnfc object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkVnfcsVnfc.json)
           required: true
           schema:
             $ref: "#/definitions/vnfc"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vnfc
+      description: |
+        Update an existing vnfc
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkVnfcsVnfc
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnfc-name
+          in: path
+          description: Unique ID of vnfc.
+          required: true
+          type: string
+          example: __VNFC-NAME__
+        - name: body
+          in: body
+          description: vnfc object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vnfc"
     delete:
       tags:
         - Network
@@ -22562,6 +26115,7 @@ paths:
           description: Unique ID of vnfc.
           required: true
           type: string
+          example: __VNFC-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -22581,9 +26135,50 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vnfcs"
+              $ref: "#/getDefinitions/vnfcs"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnfc-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vnfc-function-code
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vnfc-type
+          in: query
+          description:
+          required: false
+          type: string
+        - name: prov-status
+          in: query
+          description:
+          required: false
+          type: string
+        - name: ipaddress-v4-oam-vip
+          in: query
+          description:
+          required: false
+          type: string
+        - name: in-maint
+          in: query
+          description:
+          required: false
+          type: boolean
+        - name: is-closed-loop-disabled
+          in: query
+          description:
+          required: false
+          type: boolean
+        - name: group-notation
+          in: query
+          description:
+          required: false
+          type: string
   /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}/relationship-list/relationship:
     put:
       tags:
@@ -22605,14 +26200,16 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: subnet-id
           in: path
           description: Subnet ID, should be UUID.
           required: true
           type: string
+          example: __SUBNET-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSubnetsSubnet.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -22637,11 +26234,13 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: subnet-id
           in: path
           description: Subnet ID, should be UUID.
           required: true
           type: string
+          example: __SUBNET-ID__
   /network/l3-networks/l3-network/{network-id}/subnets/subnet/{subnet-id}:
     get:
       tags:
@@ -22656,7 +26255,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/subnet"
+              $ref: "#/getDefinitions/subnet"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -22665,66 +26264,21 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: subnet-id
           in: path
           description: Subnet ID, should be UUID.
           required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network, governed by some naming convention..
-          required: false
-          type: string
-        - name: network-role
-          in: query
-          description: Role the network plans - who defines these values?
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service from ASDC.  Does not strictly map to ASDC services.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: contrail-network-fqdn
-          in: query
-          description: Contrail FQDN for the network
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: subnet-name
-          in: query
-          description: Name associated with the subnet.
-          required: false
-          type: string
+          example: __SUBNET-ID__
     put:
       tags:
         - Network
       summary: create or update an existing subnet
-      description: create or update an existing subnet
+      description: |
+        Create or update an existing subnet.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkL3NetworksL3NetworkSubnetsSubnet
       consumes:
         - application/json
@@ -22741,17 +26295,64 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: subnet-id
           in: path
           description: Subnet ID, should be UUID.
           required: true
           type: string
+          example: __SUBNET-ID__
         - name: body
           in: body
-          description: subnet object that needs to be created or updated
+          description: subnet object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSubnetsSubnet.json)
           required: true
           schema:
             $ref: "#/definitions/subnet"
+    patch:
+      tags:
+        - Network
+      summary: update an existing subnet
+      description: |
+        Update an existing subnet
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkL3NetworksL3NetworkSubnetsSubnet
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: network-id
+          in: path
+          description: Network ID, should be uuid. Unique across A&AI.
+          required: true
+          type: string
+          example: __NETWORK-ID__
+        - name: subnet-id
+          in: path
+          description: Subnet ID, should be UUID.
+          required: true
+          type: string
+          example: __SUBNET-ID__
+        - name: body
+          in: body
+          description: subnet object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/subnet"
     delete:
       tags:
         - Network
@@ -22773,11 +26374,13 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: subnet-id
           in: path
           description: Subnet ID, should be UUID.
           required: true
           type: string
+          example: __SUBNET-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -22797,7 +26400,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/subnets"
+              $ref: "#/getDefinitions/subnets"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -22806,49 +26409,15 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network, governed by some naming convention..
-          required: false
-          type: string
-        - name: network-role
-          in: query
-          description: Role the network plans - who defines these values?
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service from ASDC.  Does not strictly map to ASDC services.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: contrail-network-fqdn
-          in: query
-          description: Contrail FQDN for the network
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
+          example: __NETWORK-ID__
+        - name: subnet-id
           in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+          description:
           required: false
           type: string
-        - name: widget-model-version
+        - name: subnet-name
           in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+          description:
           required: false
           type: string
   /network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}/relationship-list/relationship:
@@ -22872,15 +26441,17 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: vlan-id-inner
           in: path
           description: id.
           required: true
           type: integer
           format: int64
+          example: __VLAN-ID-INNER__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -22905,12 +26476,14 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: vlan-id-inner
           in: path
           description: id.
           required: true
           type: integer
           format: int64
+          example: __VLAN-ID-INNER__
   /network/l3-networks/l3-network/{network-id}/ctag-assignments/ctag-assignment/{vlan-id-inner}:
     get:
       tags:
@@ -22925,7 +26498,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/ctag-assignment"
+              $ref: "#/getDefinitions/ctag-assignment"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -22934,62 +26507,22 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: vlan-id-inner
           in: path
           description: id.
           required: true
           type: integer
           format: int64
-        - name: network-name
-          in: query
-          description: Name of the network, governed by some naming convention..
-          required: false
-          type: string
-        - name: network-role
-          in: query
-          description: Role the network plans - who defines these values?
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service from ASDC.  Does not strictly map to ASDC services.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: contrail-network-fqdn
-          in: query
-          description: Contrail FQDN for the network
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
+          example: __VLAN-ID-INNER__
     put:
       tags:
         - Network
       summary: create or update an existing ctag-assignment
-      description: create or update an existing ctag-assignment
+      description: |
+        Create or update an existing ctag-assignment.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment
       consumes:
         - application/json
@@ -23006,18 +26539,66 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: vlan-id-inner
           in: path
           description: id.
           required: true
           type: integer
           format: int64
+          example: __VLAN-ID-INNER__
         - name: body
           in: body
-          description: ctag-assignment object that needs to be created or updated
+          description: ctag-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment.json)
           required: true
           schema:
             $ref: "#/definitions/ctag-assignment"
+    patch:
+      tags:
+        - Network
+      summary: update an existing ctag-assignment
+      description: |
+        Update an existing ctag-assignment
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkL3NetworksL3NetworkCtagAssignmentsCtagAssignment
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: network-id
+          in: path
+          description: Network ID, should be uuid. Unique across A&AI.
+          required: true
+          type: string
+          example: __NETWORK-ID__
+        - name: vlan-id-inner
+          in: path
+          description: id.
+          required: true
+          type: integer
+          format: int64
+          example: __VLAN-ID-INNER__
+        - name: body
+          in: body
+          description: ctag-assignment object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/ctag-assignment"
     delete:
       tags:
         - Network
@@ -23039,12 +26620,14 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: vlan-id-inner
           in: path
           description: id.
           required: true
           type: integer
           format: int64
+          example: __VLAN-ID-INNER__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -23064,7 +26647,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/ctag-assignments"
+              $ref: "#/getDefinitions/ctag-assignments"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -23073,51 +26656,13 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network, governed by some naming convention..
-          required: false
-          type: string
-        - name: network-role
-          in: query
-          description: Role the network plans - who defines these values?
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service from ASDC.  Does not strictly map to ASDC services.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: contrail-network-fqdn
-          in: query
-          description: Contrail FQDN for the network
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
+          example: __NETWORK-ID__
+        - name: vlan-id-inner
           in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+          description:
           required: false
-          type: string
+          type: integer
+          format: int64
   /network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}/relationship-list/relationship:
     put:
       tags:
@@ -23139,14 +26684,16 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: segmentation-id
           in: path
           description: Route Table Reference id, UUID assigned to this instance.
           required: true
           type: string
+          example: __SEGMENTATION-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -23171,11 +26718,13 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: segmentation-id
           in: path
           description: Route Table Reference id, UUID assigned to this instance.
           required: true
           type: string
+          example: __SEGMENTATION-ID__
   /network/l3-networks/l3-network/{network-id}/segmentation-assignments/segmentation-assignment/{segmentation-id}:
     get:
       tags:
@@ -23190,7 +26739,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/segmentation-assignment"
+              $ref: "#/getDefinitions/segmentation-assignment"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -23199,61 +26748,21 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: segmentation-id
           in: path
           description: Route Table Reference id, UUID assigned to this instance.
           required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network, governed by some naming convention..
-          required: false
-          type: string
-        - name: network-role
-          in: query
-          description: Role the network plans - who defines these values?
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service from ASDC.  Does not strictly map to ASDC services.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: contrail-network-fqdn
-          in: query
-          description: Contrail FQDN for the network
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
+          example: __SEGMENTATION-ID__
     put:
       tags:
         - Network
       summary: create or update an existing segmentation-assignment
-      description: create or update an existing segmentation-assignment
+      description: |
+        Create or update an existing segmentation-assignment.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment
       consumes:
         - application/json
@@ -23270,17 +26779,64 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: segmentation-id
           in: path
           description: Route Table Reference id, UUID assigned to this instance.
           required: true
           type: string
+          example: __SEGMENTATION-ID__
         - name: body
           in: body
-          description: segmentation-assignment object that needs to be created or updated
+          description: segmentation-assignment object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment.json)
           required: true
           schema:
             $ref: "#/definitions/segmentation-assignment"
+    patch:
+      tags:
+        - Network
+      summary: update an existing segmentation-assignment
+      description: |
+        Update an existing segmentation-assignment
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkL3NetworksL3NetworkSegmentationAssignmentsSegmentationAssignment
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: network-id
+          in: path
+          description: Network ID, should be uuid. Unique across A&AI.
+          required: true
+          type: string
+          example: __NETWORK-ID__
+        - name: segmentation-id
+          in: path
+          description: Route Table Reference id, UUID assigned to this instance.
+          required: true
+          type: string
+          example: __SEGMENTATION-ID__
+        - name: body
+          in: body
+          description: segmentation-assignment object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/segmentation-assignment"
     delete:
       tags:
         - Network
@@ -23302,11 +26858,13 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: segmentation-id
           in: path
           description: Route Table Reference id, UUID assigned to this instance.
           required: true
           type: string
+          example: __SEGMENTATION-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -23326,7 +26884,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/segmentation-assignments"
+              $ref: "#/getDefinitions/segmentation-assignments"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -23335,49 +26893,10 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network, governed by some naming convention..
-          required: false
-          type: string
-        - name: network-role
-          in: query
-          description: Role the network plans - who defines these values?
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service from ASDC.  Does not strictly map to ASDC services.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: contrail-network-fqdn
-          in: query
-          description: Contrail FQDN for the network
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
+          example: __NETWORK-ID__
+        - name: segmentation-id
           in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+          description:
           required: false
           type: string
   /network/l3-networks/l3-network/{network-id}/relationship-list/relationship:
@@ -23401,9 +26920,10 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3Network.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -23428,6 +26948,7 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
   /network/l3-networks/l3-network/{network-id}:
     get:
       tags:
@@ -23442,7 +26963,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-network"
+              $ref: "#/getDefinitions/l3-network"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -23451,56 +26972,15 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network, governed by some naming convention..
-          required: false
-          type: string
-        - name: network-role
-          in: query
-          description: Role the network plans - who defines these values?
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service from ASDC.  Does not strictly map to ASDC services.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: contrail-network-fqdn
-          in: query
-          description: Contrail FQDN for the network
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
+          example: __NETWORK-ID__
     put:
       tags:
         - Network
       summary: create or update an existing l3-network
-      description: create or update an existing l3-network
+      description: |
+        Create or update an existing l3-network.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkL3NetworksL3Network
       consumes:
         - application/json
@@ -23517,12 +26997,52 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: body
           in: body
-          description: l3-network object that needs to be created or updated
+          description: l3-network object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkL3NetworksL3Network.json)
           required: true
           schema:
             $ref: "#/definitions/l3-network"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-network
+      description: |
+        Update an existing l3-network
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkL3NetworksL3Network
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: network-id
+          in: path
+          description: Network ID, should be uuid. Unique across A&AI.
+          required: true
+          type: string
+          example: __NETWORK-ID__
+        - name: body
+          in: body
+          description: l3-network object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-network"
     delete:
       tags:
         - Network
@@ -23544,6 +27064,7 @@ paths:
           description: Network ID, should be uuid. Unique across A&AI.
           required: true
           type: string
+          example: __NETWORK-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -23563,9 +27084,60 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-networks"
+              $ref: "#/getDefinitions/l3-networks"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: network-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: network-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: network-role
+          in: query
+          description:
+          required: false
+          type: string
+        - name: service-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: heat-stack-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: contrail-network-fqdn
+          in: query
+          description:
+          required: false
+          type: string
+        - name: model-invariant-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: model-version-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: widget-model-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: widget-model-version
+          in: query
+          description:
+          required: false
+          type: string
   /network/network-policies/network-policy/{network-policy-id}/relationship-list/relationship:
     put:
       tags:
@@ -23587,9 +27159,10 @@ paths:
           description: UUID representing unique key to this instance
           required: true
           type: string
+          example: __NETWORK-POLICY-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNetworkPoliciesNetworkPolicy.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -23614,6 +27187,7 @@ paths:
           description: UUID representing unique key to this instance
           required: true
           type: string
+          example: __NETWORK-POLICY-ID__
   /network/network-policies/network-policy/{network-policy-id}:
     get:
       tags:
@@ -23628,7 +27202,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/network-policy"
+              $ref: "#/getDefinitions/network-policy"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -23637,16 +27211,15 @@ paths:
           description: UUID representing unique key to this instance
           required: true
           type: string
-        - name: network-policy-fqdn
-          in: query
-          description: Contrail FQDN for the policy
-          required: false
-          type: string
+          example: __NETWORK-POLICY-ID__
     put:
       tags:
         - Network
       summary: create or update an existing network-policy
-      description: create or update an existing network-policy
+      description: |
+        Create or update an existing network-policy.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkNetworkPoliciesNetworkPolicy
       consumes:
         - application/json
@@ -23663,12 +27236,52 @@ paths:
           description: UUID representing unique key to this instance
           required: true
           type: string
+          example: __NETWORK-POLICY-ID__
         - name: body
           in: body
-          description: network-policy object that needs to be created or updated
+          description: network-policy object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNetworkPoliciesNetworkPolicy.json)
           required: true
           schema:
             $ref: "#/definitions/network-policy"
+    patch:
+      tags:
+        - Network
+      summary: update an existing network-policy
+      description: |
+        Update an existing network-policy
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkNetworkPoliciesNetworkPolicy
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: network-policy-id
+          in: path
+          description: UUID representing unique key to this instance
+          required: true
+          type: string
+          example: __NETWORK-POLICY-ID__
+        - name: body
+          in: body
+          description: network-policy object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/network-policy"
     delete:
       tags:
         - Network
@@ -23690,6 +27303,7 @@ paths:
           description: UUID representing unique key to this instance
           required: true
           type: string
+          example: __NETWORK-POLICY-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -23709,9 +27323,20 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/network-policies"
+              $ref: "#/getDefinitions/network-policies"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: network-policy-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: network-policy-fqdn
+          in: query
+          description:
+          required: false
+          type: string
   /network/generic-vnfs/generic-vnf/{vnf-id}/relationship-list/relationship:
     put:
       tags:
@@ -23733,9 +27358,10 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnf.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -23760,6 +27386,7 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
   /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
     put:
       tags:
@@ -23781,19 +27408,22 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -23818,16 +27448,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
   /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -23849,24 +27482,28 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -23891,21 +27528,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -23920,7 +27561,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -23929,151 +27570,33 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
@@ -24090,27 +27613,88 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - Network
@@ -24132,21 +27716,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -24173,24 +27761,28 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -24215,21 +27807,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -24244,7 +27840,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -24253,151 +27849,33 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -24414,27 +27892,88 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -24456,21 +27995,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -24490,7 +28033,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlan"
+              $ref: "#/getDefinitions/vlan"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -24499,130 +28042,27 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
+          example: __VLAN-INTERFACE__
     put:
       tags:
         - Network
       summary: create or update an existing vlan
-      description: create or update an existing vlan
+      description: |
+        Create or update an existing vlan.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan
       consumes:
         - application/json
@@ -24639,22 +28079,76 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: vlan object that needs to be created or updated
+          description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/vlan"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vlan
+      description: |
+        Update an existing vlan
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceVlansVlan
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: body
+          in: body
+          description: vlan object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vlan"
     delete:
       tags:
         - Network
@@ -24676,16 +28170,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -24705,7 +28202,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlans"
+              $ref: "#/getDefinitions/vlans"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -24714,107 +28211,27 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vlan-id-inner
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: integer
+          format: int64
+        - name: vpn-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}/relationship-list/relationship:
@@ -24838,19 +28255,22 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -24875,16 +28295,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
   /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
     get:
       tags:
@@ -24899,7 +28322,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vf"
+              $ref: "#/getDefinitions/sriov-vf"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -24908,139 +28331,27 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vf-vlan-filter
-          in: query
-          description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
-          required: false
-          type: string
-        - name: vf-mac-filter
-          in: query
-          description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
-          required: false
-          type: string
-        - name: vf-vlan-strip
-          in: query
-          description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
-          required: false
-          type: boolean
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface
-          required: false
-          type: string
+          example: __PCI-ID__
     put:
       tags:
         - Network
       summary: create or update an existing sriov-vf
-      description: create or update an existing sriov-vf
+      description: |
+        Create or update an existing sriov-vf.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf
       consumes:
         - application/json
@@ -25057,22 +28368,76 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: sriov-vf object that needs to be created or updated
+          description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/sriov-vf"
+    patch:
+      tags:
+        - Network
+      summary: update an existing sriov-vf
+      description: |
+        Update an existing sriov-vf
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceSriovVfsSriovVf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: pci-id
+          in: path
+          description: PCI ID used to identify the sriov-vf
+          required: true
+          type: string
+          example: __PCI-ID__
+        - name: body
+          in: body
+          description: sriov-vf object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/sriov-vf"
     delete:
       tags:
         - Network
@@ -25094,16 +28459,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -25123,7 +28491,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vfs"
+              $ref: "#/getDefinitions/sriov-vfs"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -25132,107 +28500,36 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: vnf-name
+          example: __INTERFACE-NAME__
+        - name: pci-id
           in: query
-          description: Name of VNF.
+          description:
           required: false
           type: string
-        - name: vnf-name2
+        - name: vf-vlan-filter
           in: query
-          description: Alternate name of VNF.
+          description:
           required: false
           type: string
-        - name: vnf-type
+        - name: vf-mac-filter
           in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+          description:
           required: false
           type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
+        - name: vf-vlan-strip
           in: query
+          description:
           required: false
           type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
+        - name: neutron-network-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/relationship-list/relationship:
@@ -25256,14 +28553,16 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -25288,11 +28587,13 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -25314,19 +28615,22 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -25351,16 +28655,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -25375,7 +28682,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -25384,135 +28691,27 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList
       consumes:
         - application/json
@@ -25529,22 +28728,76 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - Network
@@ -25566,16 +28819,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -25602,19 +28858,22 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -25639,16 +28898,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/generic-vnfs/generic-vnf/{vnf-id}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -25663,7 +28925,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -25672,135 +28934,27 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -25817,22 +28971,76 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterfaceL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -25854,16 +29062,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -25883,7 +29094,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interface"
+              $ref: "#/getDefinitions/l-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -25892,114 +29103,21 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing l-interface
-      description: create or update an existing l-interface
+      description: |
+        Create or update an existing l-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfLInterfacesLInterface
       consumes:
         - application/json
@@ -26016,17 +29134,64 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: l-interface object that needs to be created or updated
+          description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/l-interface"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l-interface
+      description: |
+        Update an existing l-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLInterfacesLInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: l-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l-interface"
     delete:
       tags:
         - Network
@@ -26048,11 +29213,13 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -26072,7 +29239,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interfaces"
+              $ref: "#/getDefinitions/l-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -26081,87 +29248,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
+          example: __VNF-ID__
+        - name: interface-name
           in: query
-          description: Generic description of the type of NF
+          description:
           required: false
           type: string
-        - name: nf-function
+        - name: interface-id
           in: query
-          description: English description of Network function that the specific VNF deployment is providing
+          description:
           required: false
           type: string
-        - name: nf-role
+        - name: macaddr
           in: query
-          description: role in the network that this model will be providing
+          description:
           required: false
           type: string
-        - name: nf-naming-code
+        - name: network-name
           in: query
-          description: string assigned to this model used for naming purposes
+          description:
           required: false
           type: string
   /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/relationship-list/relationship:
@@ -26185,14 +29290,16 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -26217,11 +29324,13 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
     put:
       tags:
@@ -26243,24 +29352,28 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -26285,21 +29398,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
   /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -26321,29 +29438,34 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -26368,26 +29490,31 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -26402,7 +29529,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -26411,167 +29538,103 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
           type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
           type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
       tags:
         - Network
-      summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
-      operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -26587,32 +29650,37 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv4-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - Network
@@ -26634,26 +29702,31 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -26680,29 +29753,34 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -26727,26 +29805,31 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -26761,7 +29844,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -26770,167 +29853,103 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
       tags:
         - Network
-      summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
-      operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
       consumes:
         - application/json
         - application/xml
@@ -26946,32 +29965,37 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv6-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -26993,26 +30017,31 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -27032,7 +30061,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlan"
+              $ref: "#/getDefinitions/vlan"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -27041,145 +30070,33 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
+          example: __VLAN-INTERFACE__
     put:
       tags:
         - Network
       summary: create or update an existing vlan
-      description: create or update an existing vlan
+      description: |
+        Create or update an existing vlan.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
       consumes:
         - application/json
@@ -27196,27 +30113,88 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: vlan object that needs to be created or updated
+          description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/vlan"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vlan
+      description: |
+        Update an existing vlan
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: body
+          in: body
+          description: vlan object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vlan"
     delete:
       tags:
         - Network
@@ -27238,21 +30216,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -27272,7 +30254,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlans"
+              $ref: "#/getDefinitions/vlans"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -27281,122 +30263,33 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vlan-id-inner
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: integer
+          format: int64
+        - name: vpn-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}/relationship-list/relationship:
@@ -27420,24 +30313,28 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -27462,21 +30359,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
   /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
     get:
       tags:
@@ -27491,7 +30392,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vf"
+              $ref: "#/getDefinitions/sriov-vf"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -27500,155 +30401,91 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
+          example: __PCI-ID__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing sriov-vf
+      description: |
+        Create or update an existing sriov-vf.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
           type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
           type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vf-vlan-filter
-          in: query
-          description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
-          required: false
-          type: string
-        - name: vf-mac-filter
-          in: query
-          description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vf-vlan-strip
-          in: query
-          description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
-          required: false
-          type: boolean
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface
-          required: false
+          example: __INTERFACE-NAME__
+        - name: pci-id
+          in: path
+          description: PCI ID used to identify the sriov-vf
+          required: true
           type: string
-    put:
+          example: __PCI-ID__
+        - name: body
+          in: body
+          description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
+          required: true
+          schema:
+            $ref: "#/definitions/sriov-vf"
+    patch:
       tags:
         - Network
-      summary: create or update an existing sriov-vf
-      description: create or update an existing sriov-vf
-      operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+      summary: update an existing sriov-vf
+      description: |
+        Update an existing sriov-vf
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
       consumes:
         - application/json
         - application/xml
@@ -27664,27 +30501,31 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: sriov-vf object that needs to be created or updated
+          description: sriov-vf object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/sriov-vf"
+            $ref: "#/patchDefinitions/sriov-vf"
     delete:
       tags:
         - Network
@@ -27706,21 +30547,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -27740,7 +30585,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vfs"
+              $ref: "#/getDefinitions/sriov-vfs"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -27749,122 +30594,42 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
+          example: __INTERFACE-NAME__
+        - name: pci-id
           in: query
-          description: Regional way of organizing pservers, source of truth should define values
+          description:
           required: false
           type: string
-        - name: prov-status
+        - name: vf-vlan-filter
           in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
+          description:
           required: false
           type: string
-        - name: heat-stack-id
+        - name: vf-mac-filter
           in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
+          description:
           required: false
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
+        - name: vf-vlan-strip
           in: query
+          description:
           required: false
           type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
+        - name: neutron-network-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/relationship-list/relationship:
@@ -27888,19 +30653,22 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -27925,16 +30693,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -27956,24 +30727,28 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -27998,21 +30773,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -28027,7 +30806,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -28036,150 +30815,33 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
       consumes:
         - application/json
@@ -28196,27 +30858,88 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - Network
@@ -28238,21 +30961,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -28279,24 +31006,28 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -28321,21 +31052,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -28350,7 +31085,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -28359,150 +31094,33 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -28519,27 +31137,88 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -28561,21 +31240,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -28595,7 +31278,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interface"
+              $ref: "#/getDefinitions/l-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -28604,130 +31287,79 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
+          example: __INTERFACE-NAME__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing l-interface
+      description: |
+        Create or update an existing l-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
           type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
           type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-    put:
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l-interface"
+    patch:
       tags:
         - Network
-      summary: create or update an existing l-interface
-      description: create or update an existing l-interface
-      operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface
+      summary: update an existing l-interface
+      description: |
+        Update an existing l-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterfaceLInterfacesLInterface
       consumes:
         - application/json
         - application/xml
@@ -28743,22 +31375,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: l-interface object that needs to be created or updated
+          description: l-interface object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l-interface"
+            $ref: "#/patchDefinitions/l-interface"
     delete:
       tags:
         - Network
@@ -28780,16 +31415,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -28809,7 +31447,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interfaces"
+              $ref: "#/getDefinitions/l-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -28818,102 +31456,31 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
+          example: __INTERFACE-NAME__
+        - name: interface-name
           in: query
-          description: role in the network that this model will be providing
+          description:
           required: false
           type: string
-        - name: nf-naming-code
+        - name: interface-id
           in: query
-          description: string assigned to this model used for naming purposes
+          description:
           required: false
           type: string
-        - name: interface-id
+        - name: macaddr
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: interface-role
+        - name: network-name
           in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+          description:
           required: false
           type: string
   /network/generic-vnfs/generic-vnf/{vnf-id}/lag-interfaces/lag-interface/{interface-name}:
@@ -28930,7 +31497,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/lag-interface"
+              $ref: "#/getDefinitions/lag-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -28939,109 +31506,21 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing lag-interface
-      description: create or update an existing lag-interface
+      description: |
+        Create or update an existing lag-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterface
       consumes:
         - application/json
@@ -29058,17 +31537,64 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: lag-interface object that needs to be created or updated
+          description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLagInterfacesLagInterface.json)
           required: true
           schema:
             $ref: "#/definitions/lag-interface"
+    patch:
+      tags:
+        - Network
+      summary: update an existing lag-interface
+      description: |
+        Update an existing lag-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLagInterfacesLagInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: lag-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/lag-interface"
     delete:
       tags:
         - Network
@@ -29090,11 +31616,13 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -29114,7 +31642,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/lag-interfaces"
+              $ref: "#/getDefinitions/lag-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -29123,87 +31651,20 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
+          example: __VNF-ID__
+        - name: interface-name
           in: query
-          description: English description of Network function that the specific VNF deployment is providing
+          description:
           required: false
           type: string
-        - name: nf-role
+        - name: interface-id
           in: query
-          description: role in the network that this model will be providing
+          description:
           required: false
           type: string
-        - name: nf-naming-code
+        - name: interface-role
           in: query
-          description: string assigned to this model used for naming purposes
+          description:
           required: false
           type: string
   /network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}/relationship-list/relationship:
@@ -29227,14 +31688,16 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: vf-module-id
           in: path
           description: Unique ID of vf-module.
           required: true
           type: string
+          example: __VF-MODULE-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -29259,11 +31722,13 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: vf-module-id
           in: path
           description: Unique ID of vf-module.
           required: true
           type: string
+          example: __VF-MODULE-ID__
   /network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}:
     get:
       tags:
@@ -29278,7 +31743,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vf-module"
+              $ref: "#/getDefinitions/vf-module"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -29287,134 +31752,21 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: vf-module-id
           in: path
           description: Unique ID of vf-module.
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-        - name: vf-module-name
-          in: query
-          description: Name of vf-module
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance.
-          required: false
-          type: string
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: contrail-service-instance-fqdn
-          in: query
-          description: the Contrail unique ID for a service-instance
-          required: false
-          type: string
+          example: __VF-MODULE-ID__
     put:
       tags:
         - Network
       summary: create or update an existing vf-module
-      description: create or update an existing vf-module
+      description: |
+        Create or update an existing vf-module.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfVfModulesVfModule
       consumes:
         - application/json
@@ -29431,17 +31783,64 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: vf-module-id
           in: path
           description: Unique ID of vf-module.
           required: true
           type: string
+          example: __VF-MODULE-ID__
         - name: body
           in: body
-          description: vf-module object that needs to be created or updated
+          description: vf-module object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfVfModulesVfModule.json)
           required: true
           schema:
             $ref: "#/definitions/vf-module"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vf-module
+      description: |
+        Update an existing vf-module
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfVfModulesVfModule
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: vf-module-id
+          in: path
+          description: Unique ID of vf-module.
+          required: true
+          type: string
+          example: __VF-MODULE-ID__
+        - name: body
+          in: body
+          description: vf-module object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vf-module"
     delete:
       tags:
         - Network
@@ -29463,11 +31862,13 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: vf-module-id
           in: path
           description: Unique ID of vf-module.
           required: true
           type: string
+          example: __VF-MODULE-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -29487,7 +31888,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vf-modules"
+              $ref: "#/getDefinitions/vf-modules"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -29496,87 +31897,45 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
+          example: __VNF-ID__
+        - name: vf-module-id
           in: query
-          description: Regional way of organizing pservers, source of truth should define values
+          description:
           required: false
           type: string
-        - name: prov-status
+        - name: vf-module-name
           in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
+          description:
           required: false
           type: string
         - name: heat-stack-id
           in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
+          description:
           required: false
           type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
         - name: model-invariant-id
           in: query
-          description: the ASDC model id for this resource or service model.
+          description:
           required: false
           type: string
         - name: model-version-id
           in: query
-          description: the ASDC model version for this resource or service model.
+          description:
           required: false
           type: string
         - name: widget-model-id
           in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+          description:
           required: false
           type: string
         - name: widget-model-version
           in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
+          description:
           required: false
           type: string
-        - name: nf-naming-code
+        - name: contrail-service-instance-fqdn
           in: query
-          description: string assigned to this model used for naming purposes
+          description:
           required: false
           type: string
   /network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}/relationship-list/relationship:
@@ -29600,19 +31959,22 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the license group the resource belongs to, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of a license resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLicensesLicense.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -29637,16 +31999,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the license group the resource belongs to, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of a license resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
   /network/generic-vnfs/generic-vnf/{vnf-id}/licenses/license/{group-uuid}/{resource-uuid}:
     get:
       tags:
@@ -29661,7 +32026,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/license"
+              $ref: "#/getDefinitions/license"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -29670,105 +32035,79 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the license group the resource belongs to, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of a license resource. 
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
+          example: __RESOURCE-UUID__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing license
+      description: |
+        Create or update an existing license.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkGenericVnfsGenericVnfLicensesLicense
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
           type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
+          example: __VNF-ID__
+        - name: group-uuid
+          in: path
+          description: Unique ID for the license group the resource belongs to, should be uuid.
+          required: true
           type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
+          example: __GROUP-UUID__
+        - name: resource-uuid
+          in: path
+          description: Unique ID of a license resource. 
+          required: true
           type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
-    put:
+          example: __RESOURCE-UUID__
+        - name: body
+          in: body
+          description: license object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfLicensesLicense.json)
+          required: true
+          schema:
+            $ref: "#/definitions/license"
+    patch:
       tags:
         - Network
-      summary: create or update an existing license
-      description: create or update an existing license
-      operationId: createOrUpdateNetworkGenericVnfsGenericVnfLicensesLicense
+      summary: update an existing license
+      description: |
+        Update an existing license
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfLicensesLicense
       consumes:
         - application/json
         - application/xml
@@ -29784,22 +32123,25 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the license group the resource belongs to, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of a license resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
         - name: body
           in: body
-          description: license object that needs to be created or updated
+          description: license object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/license"
+            $ref: "#/patchDefinitions/license"
     delete:
       tags:
         - Network
@@ -29821,16 +32163,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the license group the resource belongs to, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of a license resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -29850,7 +32195,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/licenses"
+              $ref: "#/getDefinitions/licenses"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -29859,87 +32204,15 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
+          example: __VNF-ID__
+        - name: group-uuid
           in: query
-          description: role in the network that this model will be providing
+          description:
           required: false
           type: string
-        - name: nf-naming-code
+        - name: resource-uuid
           in: query
-          description: string assigned to this model used for naming purposes
+          description:
           required: false
           type: string
   /network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}/relationship-list/relationship:
@@ -29963,19 +32236,22 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the entitlement group the resource comes from, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of an entitlement resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -30000,16 +32276,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the entitlement group the resource comes from, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of an entitlement resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
   /network/generic-vnfs/generic-vnf/{vnf-id}/entitlements/entitlement/{group-uuid}/{resource-uuid}:
     get:
       tags:
@@ -30024,7 +32303,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/entitlement"
+              $ref: "#/getDefinitions/entitlement"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -30033,104 +32312,27 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the entitlement group the resource comes from, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of an entitlement resource. 
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
-          in: query
-          description: role in the network that this model will be providing
-          required: false
-          type: string
-        - name: nf-naming-code
-          in: query
-          description: string assigned to this model used for naming purposes
-          required: false
-          type: string
+          example: __RESOURCE-UUID__
     put:
       tags:
         - Network
       summary: create or update an existing entitlement
-      description: create or update an existing entitlement
+      description: |
+        Create or update an existing entitlement.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkGenericVnfsGenericVnfEntitlementsEntitlement
       consumes:
         - application/json
@@ -30147,22 +32349,76 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the entitlement group the resource comes from, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of an entitlement resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
         - name: body
           in: body
-          description: entitlement object that needs to be created or updated
+          description: entitlement object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnfEntitlementsEntitlement.json)
           required: true
           schema:
             $ref: "#/definitions/entitlement"
+    patch:
+      tags:
+        - Network
+      summary: update an existing entitlement
+      description: |
+        Update an existing entitlement
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnfEntitlementsEntitlement
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: group-uuid
+          in: path
+          description: Unique ID for the entitlement group the resource comes from, should be uuid.
+          required: true
+          type: string
+          example: __GROUP-UUID__
+        - name: resource-uuid
+          in: path
+          description: Unique ID of an entitlement resource. 
+          required: true
+          type: string
+          example: __RESOURCE-UUID__
+        - name: body
+          in: body
+          description: entitlement object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/entitlement"
     delete:
       tags:
         - Network
@@ -30184,16 +32440,19 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
         - name: group-uuid
           in: path
           description: Unique ID for the entitlement group the resource comes from, should be uuid.
           required: true
           type: string
+          example: __GROUP-UUID__
         - name: resource-uuid
           in: path
           description: Unique ID of an entitlement resource. 
           required: true
           type: string
+          example: __RESOURCE-UUID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -30213,7 +32472,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/entitlements"
+              $ref: "#/getDefinitions/entitlements"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -30222,87 +32481,15 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: service-id
-          in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-          required: false
-          type: string
-        - name: regional-resource-zone
-          in: query
-          description: Regional way of organizing pservers, source of truth should define values
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: in-maint
-          in: query
-          required: false
-          type: boolean
-        - name: is-closed-loop-disabled
-          in: query
-          required: false
-          type: boolean
-        - name: model-invariant-id
-          in: query
-          description: the ASDC model id for this resource or service model.
-          required: false
-          type: string
-        - name: model-version-id
-          in: query
-          description: the ASDC model version for this resource or service model.
-          required: false
-          type: string
-        - name: widget-model-id
-          in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-          required: false
-          type: string
-        - name: widget-model-version
-          in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-          required: false
-          type: string
-        - name: nf-type
-          in: query
-          description: Generic description of the type of NF
-          required: false
-          type: string
-        - name: nf-function
-          in: query
-          description: English description of Network function that the specific VNF deployment is providing
-          required: false
-          type: string
-        - name: nf-role
+          example: __VNF-ID__
+        - name: group-uuid
           in: query
-          description: role in the network that this model will be providing
+          description:
           required: false
           type: string
-        - name: nf-naming-code
+        - name: resource-uuid
           in: query
-          description: string assigned to this model used for naming purposes
+          description:
           required: false
           type: string
   /network/generic-vnfs/generic-vnf/{vnf-id}:
@@ -30319,7 +32506,99 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/generic-vnf"
+              $ref: "#/getDefinitions/generic-vnf"
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing generic-vnf
+      description: |
+        Create or update an existing generic-vnf.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkGenericVnfsGenericVnf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: body
+          in: body
+          description: generic-vnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkGenericVnfsGenericVnf.json)
+          required: true
+          schema:
+            $ref: "#/definitions/generic-vnf"
+    patch:
+      tags:
+        - Network
+      summary: update an existing generic-vnf
+      description: |
+        Update an existing generic-vnf
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkGenericVnfsGenericVnf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: path
+          description: Unique id of VNF.  This is unique across the graph.
+          required: true
+          type: string
+          example: __VNF-ID__
+        - name: body
+          in: body
+          description: generic-vnf object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/generic-vnf"
+    delete:
+      tags:
+        - Network
+      summary: delete an existing generic-vnf
+      description: delete an existing generic-vnf
+      operationId: deleteNetworkGenericVnfsGenericVnf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -30328,159 +32607,120 @@ paths:
           description: Unique id of VNF.  This is unique across the graph.
           required: true
           type: string
+          example: __VNF-ID__
+        - name: resource-version
+          in: query
+          description: resource-version for concurrency
+          required: true
+          type: string
+  /network/generic-vnfs:
+    get:
+      tags:
+        - Network
+      summary: returns generic-vnfs
+      description: returns generic-vnfs
+      operationId: getNetworkGenericVnfs
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "200":
+          description: successful operation
+          schema:
+              $ref: "#/getDefinitions/generic-vnfs"
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id
+          in: query
+          description:
+          required: false
+          type: string
         - name: vnf-name
           in: query
-          description: Name of VNF.
+          description:
           required: false
           type: string
         - name: vnf-name2
           in: query
-          description: Alternate name of VNF.
+          description:
           required: false
           type: string
         - name: vnf-type
           in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+          description:
           required: false
           type: string
         - name: service-id
           in: query
-          description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
+          description:
           required: false
           type: string
         - name: regional-resource-zone
           in: query
-          description: Regional way of organizing pservers, source of truth should define values
+          description:
           required: false
           type: string
         - name: prov-status
           in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
+          description:
           required: false
           type: string
         - name: heat-stack-id
           in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
+          description:
           required: false
           type: string
         - name: in-maint
           in: query
+          description:
           required: false
           type: boolean
         - name: is-closed-loop-disabled
           in: query
+          description:
           required: false
           type: boolean
         - name: model-invariant-id
           in: query
-          description: the ASDC model id for this resource or service model.
+          description:
           required: false
           type: string
         - name: model-version-id
           in: query
-          description: the ASDC model version for this resource or service model.
+          description:
           required: false
           type: string
         - name: widget-model-id
           in: query
-          description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+          description:
           required: false
           type: string
         - name: widget-model-version
           in: query
-          description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+          description:
           required: false
           type: string
         - name: nf-type
           in: query
-          description: Generic description of the type of NF
+          description:
           required: false
           type: string
         - name: nf-function
           in: query
-          description: English description of Network function that the specific VNF deployment is providing
+          description:
           required: false
           type: string
         - name: nf-role
           in: query
-          description: role in the network that this model will be providing
+          description:
           required: false
           type: string
         - name: nf-naming-code
           in: query
-          description: string assigned to this model used for naming purposes
+          description:
           required: false
           type: string
-    put:
-      tags:
-        - Network
-      summary: create or update an existing generic-vnf
-      description: create or update an existing generic-vnf
-      operationId: createOrUpdateNetworkGenericVnfsGenericVnf
-      consumes:
-        - application/json
-        - application/xml
-      produces:
-        - application/json
-        - application/xml
-      responses:
-        "default":
-          description: Response codes found in [response codes](https://wiki.onap.org/).
-      parameters:
-        - name: vnf-id
-          in: path
-          description: Unique id of VNF.  This is unique across the graph.
-          required: true
-          type: string
-        - name: body
-          in: body
-          description: generic-vnf object that needs to be created or updated
-          required: true
-          schema:
-            $ref: "#/definitions/generic-vnf"
-    delete:
-      tags:
-        - Network
-      summary: delete an existing generic-vnf
-      description: delete an existing generic-vnf
-      operationId: deleteNetworkGenericVnfsGenericVnf
-      consumes:
-        - application/json
-        - application/xml
-      produces:
-        - application/json
-        - application/xml
-      responses:
-        "default":
-          description: Response codes found in [response codes](https://wiki.onap.org/).
-      parameters:
-        - name: vnf-id
-          in: path
-          description: Unique id of VNF.  This is unique across the graph.
-          required: true
-          type: string
-        - name: resource-version
-          in: query
-          description: resource-version for concurrency
-          required: true
-          type: string
-  /network/generic-vnfs:
-    get:
-      tags:
-        - Network
-      summary: returns generic-vnfs
-      description: returns generic-vnfs
-      operationId: getNetworkGenericVnfs
-      produces:
-        - application/json
-        - application/xml
-      responses:
-        "200":
-          description: successful operation
-          schema:
-              $ref: "#/definitions/generic-vnfs"
-        "default":
-          description: Response codes found in [response codes](https://wiki.onap.org/).
   /network/lag-links/lag-link/{link-name}/relationship-list/relationship:
     put:
       tags:
@@ -30502,9 +32742,10 @@ paths:
           description: Alphabetical concatenation of lag-interface names
           required: true
           type: string
+          example: __LINK-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLagLinksLagLink.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -30529,6 +32770,7 @@ paths:
           description: Alphabetical concatenation of lag-interface names
           required: true
           type: string
+          example: __LINK-NAME__
   /network/lag-links/lag-link/{link-name}:
     get:
       tags:
@@ -30543,7 +32785,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/lag-link"
+              $ref: "#/getDefinitions/lag-link"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -30552,11 +32794,15 @@ paths:
           description: Alphabetical concatenation of lag-interface names
           required: true
           type: string
+          example: __LINK-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing lag-link
-      description: create or update an existing lag-link
+      description: |
+        Create or update an existing lag-link.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkLagLinksLagLink
       consumes:
         - application/json
@@ -30573,12 +32819,52 @@ paths:
           description: Alphabetical concatenation of lag-interface names
           required: true
           type: string
+          example: __LINK-NAME__
         - name: body
           in: body
-          description: lag-link object that needs to be created or updated
+          description: lag-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkLagLinksLagLink.json)
           required: true
           schema:
             $ref: "#/definitions/lag-link"
+    patch:
+      tags:
+        - Network
+      summary: update an existing lag-link
+      description: |
+        Update an existing lag-link
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkLagLinksLagLink
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: link-name
+          in: path
+          description: Alphabetical concatenation of lag-interface names
+          required: true
+          type: string
+          example: __LINK-NAME__
+        - name: body
+          in: body
+          description: lag-link object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/lag-link"
     delete:
       tags:
         - Network
@@ -30600,6 +32886,7 @@ paths:
           description: Alphabetical concatenation of lag-interface names
           required: true
           type: string
+          example: __LINK-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -30619,9 +32906,15 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/lag-links"
+              $ref: "#/getDefinitions/lag-links"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: link-name
+          in: query
+          description:
+          required: false
+          type: string
   /network/newvces/newvce/{vnf-id2}/relationship-list/relationship:
     put:
       tags:
@@ -30643,9 +32936,10 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvce.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -30670,6 +32964,7 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
   /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
     put:
       tags:
@@ -30691,19 +32986,22 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -30728,16 +33026,19 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
   /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -30759,24 +33060,28 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -30801,21 +33106,25 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -30830,7 +33139,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -30839,94 +33148,91 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id2
+          in: path
+          description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+          required: true
           type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
+          example: __VNF-ID2__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
       tags:
         - Network
-      summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
-      operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -30942,27 +33248,31 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv4-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - Network
@@ -30984,21 +33294,25 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -31025,24 +33339,28 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -31067,21 +33385,25 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -31096,7 +33418,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -31105,93 +33427,33 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -31208,27 +33470,88 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id2
+          in: path
+          description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+          required: true
+          type: string
+          example: __VNF-ID2__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -31250,21 +33573,25 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -31284,7 +33611,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlan"
+              $ref: "#/getDefinitions/vlan"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -31293,72 +33620,27 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
+          example: __VLAN-INTERFACE__
     put:
       tags:
         - Network
       summary: create or update an existing vlan
-      description: create or update an existing vlan
+      description: |
+        Create or update an existing vlan.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan
       consumes:
         - application/json
@@ -31375,22 +33657,76 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: vlan object that needs to be created or updated
+          description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/vlan"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vlan
+      description: |
+        Update an existing vlan
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceVlansVlan
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id2
+          in: path
+          description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+          required: true
+          type: string
+          example: __VNF-ID2__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: body
+          in: body
+          description: vlan object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vlan"
     delete:
       tags:
         - Network
@@ -31412,16 +33748,19 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -31441,7 +33780,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlans"
+              $ref: "#/getDefinitions/vlans"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -31450,49 +33789,27 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vlan-id-inner
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: integer
+          format: int64
+        - name: vpn-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}/relationship-list/relationship:
@@ -31516,19 +33833,22 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -31553,16 +33873,19 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
   /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
     get:
       tags:
@@ -31577,7 +33900,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vf"
+              $ref: "#/getDefinitions/sriov-vf"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -31586,81 +33909,27 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vf-vlan-filter
-          in: query
-          description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
-          required: false
-          type: string
-        - name: vf-mac-filter
-          in: query
-          description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
-          required: false
-          type: string
-        - name: vf-vlan-strip
-          in: query
-          description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
-          required: false
-          type: boolean
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface
-          required: false
-          type: string
+          example: __PCI-ID__
     put:
       tags:
         - Network
       summary: create or update an existing sriov-vf
-      description: create or update an existing sriov-vf
+      description: |
+        Create or update an existing sriov-vf.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf
       consumes:
         - application/json
@@ -31677,22 +33946,76 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: sriov-vf object that needs to be created or updated
+          description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/sriov-vf"
+    patch:
+      tags:
+        - Network
+      summary: update an existing sriov-vf
+      description: |
+        Update an existing sriov-vf
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceSriovVfsSriovVf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id2
+          in: path
+          description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+          required: true
+          type: string
+          example: __VNF-ID2__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: pci-id
+          in: path
+          description: PCI ID used to identify the sriov-vf
+          required: true
+          type: string
+          example: __PCI-ID__
+        - name: body
+          in: body
+          description: sriov-vf object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/sriov-vf"
     delete:
       tags:
         - Network
@@ -31714,16 +34037,19 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -31743,7 +34069,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vfs"
+              $ref: "#/getDefinitions/sriov-vfs"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -31752,49 +34078,36 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: prov-status
+          example: __INTERFACE-NAME__
+        - name: pci-id
           in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+          description:
           required: false
           type: string
-        - name: heat-stack-id
+        - name: vf-vlan-filter
           in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
+          description:
           required: false
           type: string
-        - name: interface-id
+        - name: vf-mac-filter
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vf-vlan-strip
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: boolean
+        - name: neutron-network-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/relationship-list/relationship:
@@ -31818,14 +34131,16 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -31850,11 +34165,13 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -31876,19 +34193,22 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -31913,16 +34233,19 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -31937,7 +34260,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -31946,77 +34269,27 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList
       consumes:
         - application/json
@@ -32033,22 +34306,76 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id2
+          in: path
+          description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+          required: true
+          type: string
+          example: __VNF-ID2__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - Network
@@ -32070,16 +34397,19 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -32106,19 +34436,22 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -32143,16 +34476,19 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/newvces/newvce/{vnf-id2}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -32167,7 +34503,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -32176,77 +34512,27 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -32263,22 +34549,76 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id2
+          in: path
+          description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+          required: true
+          type: string
+          example: __VNF-ID2__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -32300,16 +34640,19 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -32329,7 +34672,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interface"
+              $ref: "#/getDefinitions/l-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -32338,56 +34681,21 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing l-interface
-      description: create or update an existing l-interface
+      description: |
+        Create or update an existing l-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkNewvcesNewvceLInterfacesLInterface
       consumes:
         - application/json
@@ -32404,17 +34712,64 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: l-interface object that needs to be created or updated
+          description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/l-interface"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l-interface
+      description: |
+        Update an existing l-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkNewvcesNewvceLInterfacesLInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id2
+          in: path
+          description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+          required: true
+          type: string
+          example: __VNF-ID2__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: l-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l-interface"
     delete:
       tags:
         - Network
@@ -32436,11 +34791,13 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -32460,7 +34817,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interfaces"
+              $ref: "#/getDefinitions/l-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -32469,29 +34826,25 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
+          example: __VNF-ID2__
+        - name: interface-name
           in: query
-          description: Alternate name of VNF.
+          description:
           required: false
           type: string
-        - name: vnf-type
+        - name: interface-id
           in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+          description:
           required: false
           type: string
-        - name: prov-status
+        - name: macaddr
           in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+          description:
           required: false
           type: string
-        - name: heat-stack-id
+        - name: network-name
           in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
+          description:
           required: false
           type: string
   /network/newvces/newvce/{vnf-id2}:
@@ -32508,7 +34861,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/newvce"
+              $ref: "#/getDefinitions/newvce"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -32517,36 +34870,15 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
-        - name: vnf-name
-          in: query
-          description: Name of VNF.
-          required: false
-          type: string
-        - name: vnf-name2
-          in: query
-          description: Alternate name of VNF.
-          required: false
-          type: string
-        - name: vnf-type
-          in: query
-          description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-          required: false
-          type: string
-        - name: heat-stack-id
-          in: query
-          description: Heat stack id corresponding to this instance, managed by MSO
-          required: false
-          type: string
+          example: __VNF-ID2__
     put:
       tags:
         - Network
       summary: create or update an existing newvce
-      description: create or update an existing newvce
+      description: |
+        Create or update an existing newvce.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkNewvcesNewvce
       consumes:
         - application/json
@@ -32563,12 +34895,52 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: body
           in: body
-          description: newvce object that needs to be created or updated
+          description: newvce object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkNewvcesNewvce.json)
           required: true
           schema:
             $ref: "#/definitions/newvce"
+    patch:
+      tags:
+        - Network
+      summary: update an existing newvce
+      description: |
+        Update an existing newvce
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkNewvcesNewvce
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id2
+          in: path
+          description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+          required: true
+          type: string
+          example: __VNF-ID2__
+        - name: body
+          in: body
+          description: newvce object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/newvce"
     delete:
       tags:
         - Network
@@ -32590,6 +34962,7 @@ paths:
           description: Unique id of VNF, can't use same attribute name right now until we promote this new object
           required: true
           type: string
+          example: __VNF-ID2__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -32609,9 +34982,40 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/newvces"
+              $ref: "#/getDefinitions/newvces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: vnf-id2
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vnf-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vnf-name2
+          in: query
+          description:
+          required: false
+          type: string
+        - name: vnf-type
+          in: query
+          description:
+          required: false
+          type: string
+        - name: prov-status
+          in: query
+          description:
+          required: false
+          type: string
+        - name: heat-stack-id
+          in: query
+          description:
+          required: false
+          type: string
   /network/pnfs/pnf/{pnf-name}/relationship-list/relationship:
     put:
       tags:
@@ -32633,9 +35037,10 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnf.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -32660,6 +35065,7 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
   /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/relationship-list/relationship:
     put:
       tags:
@@ -32681,14 +35087,16 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -32713,11 +35121,13 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
     put:
       tags:
@@ -32739,24 +35149,28 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -32781,21 +35195,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
   /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -32817,29 +35235,34 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -32864,26 +35287,31 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -32898,7 +35326,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -32907,84 +35335,103 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
       tags:
         - Network
-      summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
-      operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -33000,32 +35447,37 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv4-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - Network
@@ -33047,26 +35499,31 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -33093,29 +35550,34 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -33140,26 +35602,31 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -33174,7 +35641,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -33183,84 +35650,103 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
       tags:
         - Network
-      summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
-      operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
       consumes:
         - application/json
         - application/xml
@@ -33276,32 +35762,37 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv6-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -33323,26 +35814,31 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -33362,7 +35858,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlan"
+              $ref: "#/getDefinitions/vlan"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -33371,62 +35867,33 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
+          example: __VLAN-INTERFACE__
     put:
       tags:
         - Network
       summary: create or update an existing vlan
-      description: create or update an existing vlan
+      description: |
+        Create or update an existing vlan.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
       consumes:
         - application/json
@@ -33443,27 +35910,88 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: vlan object that needs to be created or updated
+          description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/vlan"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vlan
+      description: |
+        Update an existing vlan
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceVlansVlan
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
+          type: string
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: body
+          in: body
+          description: vlan object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vlan"
     delete:
       tags:
         - Network
@@ -33485,21 +36013,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -33519,7 +36051,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlans"
+              $ref: "#/getDefinitions/vlans"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -33528,39 +36060,33 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vlan-id-inner
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: integer
+          format: int64
+        - name: vpn-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}/relationship-list/relationship:
@@ -33584,24 +36110,28 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -33626,21 +36156,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
   /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
     get:
       tags:
@@ -33655,7 +36189,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vf"
+              $ref: "#/getDefinitions/sriov-vf"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -33664,71 +36198,33 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vf-vlan-filter
-          in: query
-          description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
-          required: false
-          type: string
-        - name: vf-mac-filter
-          in: query
-          description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
-          required: false
-          type: string
-        - name: vf-vlan-strip
-          in: query
-          description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
-          required: false
-          type: boolean
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface
-          required: false
-          type: string
+          example: __PCI-ID__
     put:
       tags:
         - Network
       summary: create or update an existing sriov-vf
-      description: create or update an existing sriov-vf
+      description: |
+        Create or update an existing sriov-vf.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
       consumes:
         - application/json
@@ -33745,27 +36241,88 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: sriov-vf object that needs to be created or updated
+          description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/sriov-vf"
+    patch:
+      tags:
+        - Network
+      summary: update an existing sriov-vf
+      description: |
+        Update an existing sriov-vf
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
+          type: string
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: pci-id
+          in: path
+          description: PCI ID used to identify the sriov-vf
+          required: true
+          type: string
+          example: __PCI-ID__
+        - name: body
+          in: body
+          description: sriov-vf object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/sriov-vf"
     delete:
       tags:
         - Network
@@ -33787,21 +36344,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -33821,7 +36382,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vfs"
+              $ref: "#/getDefinitions/sriov-vfs"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -33830,39 +36391,42 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: inv-status
+          example: __INTERFACE-NAME__
+        - name: pci-id
           in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+          description:
           required: false
           type: string
-        - name: prov-status
+        - name: vf-vlan-filter
           in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
+          description:
           required: false
           type: string
-        - name: interface-id
+        - name: vf-mac-filter
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vf-vlan-strip
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: boolean
+        - name: neutron-network-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/relationship-list/relationship:
@@ -33886,19 +36450,22 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -33923,16 +36490,19 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -33954,24 +36524,28 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -33996,21 +36570,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -34025,7 +36603,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -34034,67 +36612,33 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
       consumes:
         - application/json
@@ -34111,27 +36655,88 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
+          type: string
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - Network
@@ -34153,21 +36758,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -34194,24 +36803,28 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -34236,21 +36849,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -34265,7 +36882,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -34274,68 +36891,91 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
       tags:
         - Network
-      summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
-      operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
       consumes:
         - application/json
         - application/xml
@@ -34351,27 +36991,31 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv6-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -34393,21 +37037,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -34427,7 +37075,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interface"
+              $ref: "#/getDefinitions/l-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -34436,46 +37084,27 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing l-interface
-      description: create or update an existing l-interface
+      description: |
+        Create or update an existing l-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface
       consumes:
         - application/json
@@ -34492,22 +37121,76 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: l-interface object that needs to be created or updated
+          description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/l-interface"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l-interface
+      description: |
+        Update an existing l-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfPInterfacesPInterfaceLInterfacesLInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
+          type: string
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: l-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l-interface"
     delete:
       tags:
         - Network
@@ -34529,16 +37212,19 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -34558,7 +37244,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interfaces"
+              $ref: "#/getDefinitions/l-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -34567,19 +37253,31 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
-        - name: inv-status
+          example: __INTERFACE-NAME__
+        - name: interface-name
           in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+          description:
           required: false
           type: string
-        - name: prov-status
+        - name: interface-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: macaddr
+          in: query
+          description:
+          required: false
+          type: string
+        - name: network-name
           in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
+          description:
           required: false
           type: string
   /network/pnfs/pnf/{pnf-name}/p-interfaces/p-interface/{interface-name}:
@@ -34596,7 +37294,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/p-interface"
+              $ref: "#/getDefinitions/p-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -34605,26 +37303,21 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: prov-status
-          in: query
-          description: Trigger for operational monitoring of this resource by Service Assurance systems.
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing p-interface
-      description: create or update an existing p-interface
+      description: |
+        Create or update an existing p-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnfPInterfacesPInterface
       consumes:
         - application/json
@@ -34641,17 +37334,64 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: p-interface object that needs to be created or updated
+          description: p-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfPInterfacesPInterface.json)
           required: true
           schema:
             $ref: "#/definitions/p-interface"
+    patch:
+      tags:
+        - Network
+      summary: update an existing p-interface
+      description: |
+        Update an existing p-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfPInterfacesPInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
+          type: string
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the physical interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: p-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/p-interface"
     delete:
       tags:
         - Network
@@ -34673,11 +37413,13 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the physical interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -34697,7 +37439,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/p-interfaces"
+              $ref: "#/getDefinitions/p-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -34706,9 +37448,15 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
-        - name: inv-status
+          example: __PNF-NAME__
+        - name: interface-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: prov-status
           in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+          description:
           required: false
           type: string
   /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/relationship-list/relationship:
@@ -34732,14 +37480,16 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -34764,11 +37514,13 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/relationship-list/relationship:
     put:
       tags:
@@ -34790,24 +37542,28 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -34832,21 +37588,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
   /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -34868,29 +37628,34 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -34915,26 +37680,31 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -34949,7 +37719,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -34958,89 +37728,103 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+    put:
+      tags:
+        - Network
+      summary: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
+      operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
           type: string
-    put:
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList.json)
+          required: true
+          schema:
+            $ref: "#/definitions/l3-interface-ipv4-address-list"
+    patch:
       tags:
         - Network
-      summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
-      operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -35056,32 +37840,37 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be updated.
           required: true
           schema:
-            $ref: "#/definitions/l3-interface-ipv4-address-list"
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
     delete:
       tags:
         - Network
@@ -35103,26 +37892,31 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -35149,29 +37943,34 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -35196,26 +37995,31 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -35230,7 +38034,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -35239,88 +38043,39 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -35337,38 +38092,54 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
-    delete:
+    patch:
       tags:
         - Network
-      summary: delete an existing l3-interface-ipv6-address-list
-      description: delete an existing l3-interface-ipv6-address-list
-      operationId: deleteNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
       consumes:
         - application/json
         - application/xml
@@ -35384,46 +38155,50 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: resource-version
-          in: query
-          description: resource-version for concurrency
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
           required: true
-          type: string
-  /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}:
-    get:
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
+    delete:
       tags:
         - Network
-      summary: returns vlan
-      description: returns vlan
-      operationId: getNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+      summary: delete an existing l3-interface-ipv6-address-list
+      description: delete an existing l3-interface-ipv6-address-list
+      operationId: deleteNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlanL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
       produces:
         - application/json
         - application/xml
       responses:
-        "200":
-          description: successful operation
-          schema:
-              $ref: "#/definitions/vlan"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -35432,67 +38207,86 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
+          example: __VLAN-INTERFACE__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
           type: string
-        - name: interface-role
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: resource-version
           in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
+          description: resource-version for concurrency
+          required: true
           type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
+  /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/vlans/vlan/{vlan-interface}:
+    get:
+      tags:
+        - Network
+      summary: returns vlan
+      description: returns vlan
+      operationId: getNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "200":
+          description: successful operation
+          schema:
+              $ref: "#/getDefinitions/vlan"
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
           type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
           type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
           type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: vpn-id
-          in: query
-          description: This indicates the customers VPN ID associated with this vlan
-          required: false
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
           type: string
+          example: __VLAN-INTERFACE__
     put:
       tags:
         - Network
       summary: create or update an existing vlan
-      description: create or update an existing vlan
+      description: |
+        Create or update an existing vlan.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
       consumes:
         - application/json
@@ -35509,27 +38303,88 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: body
           in: body
-          description: vlan object that needs to be created or updated
+          description: vlan object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan.json)
           required: true
           schema:
             $ref: "#/definitions/vlan"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vlan
+      description: |
+        Update an existing vlan
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceVlansVlan
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
+          type: string
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
+          in: path
+          description: String that identifies the interface
+          required: true
+          type: string
+          example: __VLAN-INTERFACE__
+        - name: body
+          in: body
+          description: vlan object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vlan"
     delete:
       tags:
         - Network
@@ -35551,21 +38406,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: vlan-interface
           in: path
           description: String that identifies the interface
           required: true
           type: string
+          example: __VLAN-INTERFACE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -35585,7 +38444,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vlans"
+              $ref: "#/getDefinitions/vlans"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -35594,44 +38453,33 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: vlan-interface
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vlan-id-inner
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: integer
+          format: int64
+        - name: vpn-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}/relationship-list/relationship:
@@ -35655,24 +38503,28 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -35697,21 +38549,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
   /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/sriov-vfs/sriov-vf/{pci-id}:
     get:
       tags:
@@ -35726,7 +38582,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vf"
+              $ref: "#/getDefinitions/sriov-vf"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -35735,76 +38591,33 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vf-vlan-filter
-          in: query
-          description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
-          required: false
-          type: string
-        - name: vf-mac-filter
-          in: query
-          description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
-          required: false
-          type: string
-        - name: vf-vlan-strip
-          in: query
-          description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
-          required: false
-          type: boolean
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface
-          required: false
-          type: string
+          example: __PCI-ID__
     put:
       tags:
         - Network
       summary: create or update an existing sriov-vf
-      description: create or update an existing sriov-vf
+      description: |
+        Create or update an existing sriov-vf.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
       consumes:
         - application/json
@@ -35821,27 +38634,88 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: body
           in: body
-          description: sriov-vf object that needs to be created or updated
+          description: sriov-vf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf.json)
           required: true
           schema:
             $ref: "#/definitions/sriov-vf"
+    patch:
+      tags:
+        - Network
+      summary: update an existing sriov-vf
+      description: |
+        Update an existing sriov-vf
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceSriovVfsSriovVf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
+          type: string
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: pci-id
+          in: path
+          description: PCI ID used to identify the sriov-vf
+          required: true
+          type: string
+          example: __PCI-ID__
+        - name: body
+          in: body
+          description: sriov-vf object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/sriov-vf"
     delete:
       tags:
         - Network
@@ -35863,21 +38737,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: pci-id
           in: path
           description: PCI ID used to identify the sriov-vf
           required: true
           type: string
+          example: __PCI-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -35897,7 +38775,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/sriov-vfs"
+              $ref: "#/getDefinitions/sriov-vfs"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -35906,44 +38784,42 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: interface-id
+          example: __INTERFACE-NAME__
+        - name: pci-id
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: interface-role
+        - name: vf-vlan-filter
           in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+          description:
           required: false
           type: string
-        - name: interface-id
+        - name: vf-mac-filter
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: macaddr
+        - name: vf-vlan-strip
           in: query
-          description: MAC address for the interface
+          description:
           required: false
-          type: string
-        - name: network-name
+          type: boolean
+        - name: neutron-network-id
           in: query
-          description: Name of the network
+          description:
           required: false
           type: string
   /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/relationship-list/relationship:
@@ -35967,19 +38843,22 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -36004,16 +38883,19 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
   /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}/relationship-list/relationship:
     put:
       tags:
@@ -36035,24 +38917,28 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -36077,21 +38963,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
   /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv4-address-list/{l3-interface-ipv4-address}:
     get:
       tags:
@@ -36106,7 +38996,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv4-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -36115,72 +39005,33 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv4-address-list
-      description: create or update an existing l3-interface-ipv4-address-list
+      description: |
+        Create or update an existing l3-interface-ipv4-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
       consumes:
         - application/json
@@ -36197,33 +39048,48 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv4-address-list object that needs to be created or updated
+          description: l3-interface-ipv4-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv4-address-list"
-    delete:
+    patch:
       tags:
         - Network
-      summary: delete an existing l3-interface-ipv4-address-list
-      description: delete an existing l3-interface-ipv4-address-list
-      operationId: deleteNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
+      summary: update an existing l3-interface-ipv4-address-list
+      description: |
+        Update an existing l3-interface-ipv4-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -36239,32 +39105,37 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv4-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: resource-version
-          in: query
-          description: resource-version for concurrency
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv4-address-list object that needs to be updated.
           required: true
-          type: string
-  /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}/relationship-list/relationship:
-    put:
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv4-address-list"
+    delete:
       tags:
         - Network
-      summary: see node definition for valid relationships
-      operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressListRelationshipListRelationship
+      summary: delete an existing l3-interface-ipv4-address-list
+      description: delete an existing l3-interface-ipv4-address-list
+      operationId: deleteNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv4AddressList
       consumes:
         - application/json
         - application/xml
@@ -36280,24 +39151,73 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv4-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV4-ADDRESS__
+        - name: resource-version
+          in: query
+          description: resource-version for concurrency
+          required: true
+          type: string
+  /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}/relationship-list/relationship:
+    put:
+      tags:
+        - Network
+      summary: see node definition for valid relationships
+      operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressListRelationshipListRelationship
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
+          type: string
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -36322,21 +39242,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
   /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}/l-interfaces/l-interface/{interface-name}/l3-interface-ipv6-address-list/{l3-interface-ipv6-address}:
     get:
       tags:
@@ -36351,7 +39275,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l3-interface-ipv6-address-list"
+              $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -36360,72 +39284,33 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
-        - name: vlan-id-inner
-          in: query
-          description: Inner VLAN tag
-          required: false
-          type: integer
-          format: int64
-        - name: neutron-network-id
-          in: query
-          description: Neutron network id of the interface that address belongs to
-          required: false
-          type: string
-        - name: neutron-subnet-id
-          in: query
-          description: Neutron id of subnet that address belongs to
-          required: false
-          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
     put:
       tags:
         - Network
       summary: create or update an existing l3-interface-ipv6-address-list
-      description: create or update an existing l3-interface-ipv6-address-list
+      description: |
+        Create or update an existing l3-interface-ipv6-address-list.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
       consumes:
         - application/json
@@ -36442,27 +39327,88 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: body
           in: body
-          description: l3-interface-ipv6-address-list object that needs to be created or updated
+          description: l3-interface-ipv6-address-list object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList.json)
           required: true
           schema:
             $ref: "#/definitions/l3-interface-ipv6-address-list"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l3-interface-ipv6-address-list
+      description: |
+        Update an existing l3-interface-ipv6-address-list
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterfaceL3InterfaceIpv6AddressList
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
+          type: string
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: l3-interface-ipv6-address
+          in: path
+          description: IP address
+          required: true
+          type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
+        - name: body
+          in: body
+          description: l3-interface-ipv6-address-list object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l3-interface-ipv6-address-list"
     delete:
       tags:
         - Network
@@ -36484,21 +39430,25 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: l3-interface-ipv6-address
           in: path
           description: IP address
           required: true
           type: string
+          example: __L3-INTERFACE-IPV6-ADDRESS__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -36518,7 +39468,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interface"
+              $ref: "#/getDefinitions/l-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -36527,51 +39477,27 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: macaddr
-          in: query
-          description: MAC address for the interface
-          required: false
-          type: string
-        - name: network-name
-          in: query
-          description: Name of the network
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing l-interface
-      description: create or update an existing l-interface
+      description: |
+        Create or update an existing l-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface
       consumes:
         - application/json
@@ -36588,22 +39514,76 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: l-interface object that needs to be created or updated
+          description: l-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface.json)
           required: true
           schema:
             $ref: "#/definitions/l-interface"
+    patch:
+      tags:
+        - Network
+      summary: update an existing l-interface
+      description: |
+        Update an existing l-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterfaceLInterfacesLInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
+          type: string
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: interface-name
+          in: path
+          description: Name given to the interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: l-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/l-interface"
     delete:
       tags:
         - Network
@@ -36625,16 +39605,19 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: interface-name
           in: path
           description: Name given to the interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -36654,7 +39637,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/l-interfaces"
+              $ref: "#/getDefinitions/l-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -36663,24 +39646,31 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
-        - name: inv-status
+          example: __INTERFACE-NAME__
+        - name: interface-name
           in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+          description:
           required: false
           type: string
         - name: interface-id
           in: query
-          description: ID of interface
+          description:
           required: false
           type: string
-        - name: interface-role
+        - name: macaddr
+          in: query
+          description:
+          required: false
+          type: string
+        - name: network-name
           in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+          description:
           required: false
           type: string
   /network/pnfs/pnf/{pnf-name}/lag-interfaces/lag-interface/{interface-name}:
@@ -36697,7 +39687,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/lag-interface"
+              $ref: "#/getDefinitions/lag-interface"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -36706,31 +39696,21 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
-        - name: interface-id
-          in: query
-          description: ID of interface
-          required: false
-          type: string
-        - name: interface-role
-          in: query
-          description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
-          required: false
-          type: string
+          example: __INTERFACE-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing lag-interface
-      description: create or update an existing lag-interface
+      description: |
+        Create or update an existing lag-interface.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnfLagInterfacesLagInterface
       consumes:
         - application/json
@@ -36747,17 +39727,64 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: body
           in: body
-          description: lag-interface object that needs to be created or updated
+          description: lag-interface object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnfLagInterfacesLagInterface.json)
           required: true
           schema:
             $ref: "#/definitions/lag-interface"
+    patch:
+      tags:
+        - Network
+      summary: update an existing lag-interface
+      description: |
+        Update an existing lag-interface
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnfLagInterfacesLagInterface
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
+          type: string
+          example: __PNF-NAME__
+        - name: interface-name
+          in: path
+          description: Name that identifies the link aggregate interface
+          required: true
+          type: string
+          example: __INTERFACE-NAME__
+        - name: body
+          in: body
+          description: lag-interface object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/lag-interface"
     delete:
       tags:
         - Network
@@ -36779,11 +39806,13 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: interface-name
           in: path
           description: Name that identifies the link aggregate interface
           required: true
           type: string
+          example: __INTERFACE-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -36803,7 +39832,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/lag-interfaces"
+              $ref: "#/getDefinitions/lag-interfaces"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -36812,9 +39841,20 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
-        - name: inv-status
+          example: __PNF-NAME__
+        - name: interface-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: interface-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: interface-role
           in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+          description:
           required: false
           type: string
   /network/pnfs/pnf/{pnf-name}:
@@ -36831,7 +39871,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/pnf"
+              $ref: "#/getDefinitions/pnf"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -36840,16 +39880,15 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
-        - name: inv-status
-          in: query
-          description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-          required: false
-          type: string
+          example: __PNF-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing pnf
-      description: create or update an existing pnf
+      description: |
+        Create or update an existing pnf.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPnfsPnf
       consumes:
         - application/json
@@ -36866,12 +39905,52 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: body
           in: body
-          description: pnf object that needs to be created or updated
+          description: pnf object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPnfsPnf.json)
           required: true
           schema:
             $ref: "#/definitions/pnf"
+    patch:
+      tags:
+        - Network
+      summary: update an existing pnf
+      description: |
+        Update an existing pnf
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPnfsPnf
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: path
+          description: unique name of Physical Network Function.
+          required: true
+          type: string
+          example: __PNF-NAME__
+        - name: body
+          in: body
+          description: pnf object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/pnf"
     delete:
       tags:
         - Network
@@ -36893,6 +39972,7 @@ paths:
           description: unique name of Physical Network Function.
           required: true
           type: string
+          example: __PNF-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -36912,9 +39992,20 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/pnfs"
+              $ref: "#/getDefinitions/pnfs"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: pnf-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: inv-status
+          in: query
+          description:
+          required: false
+          type: string
   /network/physical-links/physical-link/{link-name}/relationship-list/relationship:
     put:
       tags:
@@ -36936,9 +40027,10 @@ paths:
           description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
           required: true
           type: string
+          example: __LINK-NAME__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPhysicalLinksPhysicalLink.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -36963,6 +40055,7 @@ paths:
           description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
           required: true
           type: string
+          example: __LINK-NAME__
   /network/physical-links/physical-link/{link-name}:
     get:
       tags:
@@ -36977,7 +40070,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/physical-link"
+              $ref: "#/getDefinitions/physical-link"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -36986,16 +40079,15 @@ paths:
           description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
           required: true
           type: string
-        - name: circuit-id
-          in: query
-          description: Circuit it
-          required: false
-          type: string
+          example: __LINK-NAME__
     put:
       tags:
         - Network
       summary: create or update an existing physical-link
-      description: create or update an existing physical-link
+      description: |
+        Create or update an existing physical-link.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkPhysicalLinksPhysicalLink
       consumes:
         - application/json
@@ -37012,12 +40104,52 @@ paths:
           description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
           required: true
           type: string
+          example: __LINK-NAME__
         - name: body
           in: body
-          description: physical-link object that needs to be created or updated
+          description: physical-link object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkPhysicalLinksPhysicalLink.json)
           required: true
           schema:
             $ref: "#/definitions/physical-link"
+    patch:
+      tags:
+        - Network
+      summary: update an existing physical-link
+      description: |
+        Update an existing physical-link
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkPhysicalLinksPhysicalLink
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: link-name
+          in: path
+          description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+          required: true
+          type: string
+          example: __LINK-NAME__
+        - name: body
+          in: body
+          description: physical-link object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/physical-link"
     delete:
       tags:
         - Network
@@ -37039,6 +40171,7 @@ paths:
           description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
           required: true
           type: string
+          example: __LINK-NAME__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -37058,9 +40191,20 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/physical-links"
+              $ref: "#/getDefinitions/physical-links"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: link-name
+          in: query
+          description:
+          required: false
+          type: string
+        - name: circuit-id
+          in: query
+          description:
+          required: false
+          type: string
   /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/relationship-list/relationship:
     put:
       tags:
@@ -37082,9 +40226,10 @@ paths:
           description: UUID of this configuration
           required: true
           type: string
+          example: __IPSEC-CONFIGURATION-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfiguration.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -37109,6 +40254,7 @@ paths:
           description: UUID of this configuration
           required: true
           type: string
+          example: __IPSEC-CONFIGURATION-ID__
   /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}/relationship-list/relationship:
     put:
       tags:
@@ -37130,14 +40276,16 @@ paths:
           description: UUID of this configuration
           required: true
           type: string
+          example: __IPSEC-CONFIGURATION-ID__
         - name: vig-address-type
           in: path
           description: indicates whether the VIG is for AVPN or INTERNET
           required: true
           type: string
+          example: __VIG-ADDRESS-TYPE__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -37162,11 +40310,13 @@ paths:
           description: UUID of this configuration
           required: true
           type: string
+          example: __IPSEC-CONFIGURATION-ID__
         - name: vig-address-type
           in: path
           description: indicates whether the VIG is for AVPN or INTERNET
           required: true
           type: string
+          example: __VIG-ADDRESS-TYPE__
   /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}/vig-servers/vig-server/{vig-address-type}:
     get:
       tags:
@@ -37181,7 +40331,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vig-server"
+              $ref: "#/getDefinitions/vig-server"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -37190,16 +40340,21 @@ paths:
           description: UUID of this configuration
           required: true
           type: string
+          example: __IPSEC-CONFIGURATION-ID__
         - name: vig-address-type
           in: path
           description: indicates whether the VIG is for AVPN or INTERNET
           required: true
           type: string
+          example: __VIG-ADDRESS-TYPE__
     put:
       tags:
         - Network
       summary: create or update an existing vig-server
-      description: create or update an existing vig-server
+      description: |
+        Create or update an existing vig-server.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer
       consumes:
         - application/json
@@ -37216,17 +40371,64 @@ paths:
           description: UUID of this configuration
           required: true
           type: string
+          example: __IPSEC-CONFIGURATION-ID__
         - name: vig-address-type
           in: path
           description: indicates whether the VIG is for AVPN or INTERNET
           required: true
           type: string
+          example: __VIG-ADDRESS-TYPE__
         - name: body
           in: body
-          description: vig-server object that needs to be created or updated
+          description: vig-server object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer.json)
           required: true
           schema:
             $ref: "#/definitions/vig-server"
+    patch:
+      tags:
+        - Network
+      summary: update an existing vig-server
+      description: |
+        Update an existing vig-server
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkIpsecConfigurationsIpsecConfigurationVigServersVigServer
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: ipsec-configuration-id
+          in: path
+          description: UUID of this configuration
+          required: true
+          type: string
+          example: __IPSEC-CONFIGURATION-ID__
+        - name: vig-address-type
+          in: path
+          description: indicates whether the VIG is for AVPN or INTERNET
+          required: true
+          type: string
+          example: __VIG-ADDRESS-TYPE__
+        - name: body
+          in: body
+          description: vig-server object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/vig-server"
     delete:
       tags:
         - Network
@@ -37248,11 +40450,13 @@ paths:
           description: UUID of this configuration
           required: true
           type: string
+          example: __IPSEC-CONFIGURATION-ID__
         - name: vig-address-type
           in: path
           description: indicates whether the VIG is for AVPN or INTERNET
           required: true
           type: string
+          example: __VIG-ADDRESS-TYPE__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -37272,7 +40476,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/vig-servers"
+              $ref: "#/getDefinitions/vig-servers"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -37281,6 +40485,12 @@ paths:
           description: UUID of this configuration
           required: true
           type: string
+          example: __IPSEC-CONFIGURATION-ID__
+        - name: vig-address-type
+          in: query
+          description:
+          required: false
+          type: string
   /network/ipsec-configurations/ipsec-configuration/{ipsec-configuration-id}:
     get:
       tags:
@@ -37295,7 +40505,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/ipsec-configuration"
+              $ref: "#/getDefinitions/ipsec-configuration"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -37304,11 +40514,15 @@ paths:
           description: UUID of this configuration
           required: true
           type: string
+          example: __IPSEC-CONFIGURATION-ID__
     put:
       tags:
         - Network
       summary: create or update an existing ipsec-configuration
-      description: create or update an existing ipsec-configuration
+      description: |
+        Create or update an existing ipsec-configuration.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkIpsecConfigurationsIpsecConfiguration
       consumes:
         - application/json
@@ -37325,12 +40539,52 @@ paths:
           description: UUID of this configuration
           required: true
           type: string
+          example: __IPSEC-CONFIGURATION-ID__
         - name: body
           in: body
-          description: ipsec-configuration object that needs to be created or updated
+          description: ipsec-configuration object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkIpsecConfigurationsIpsecConfiguration.json)
           required: true
           schema:
             $ref: "#/definitions/ipsec-configuration"
+    patch:
+      tags:
+        - Network
+      summary: update an existing ipsec-configuration
+      description: |
+        Update an existing ipsec-configuration
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkIpsecConfigurationsIpsecConfiguration
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: ipsec-configuration-id
+          in: path
+          description: UUID of this configuration
+          required: true
+          type: string
+          example: __IPSEC-CONFIGURATION-ID__
+        - name: body
+          in: body
+          description: ipsec-configuration object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/ipsec-configuration"
     delete:
       tags:
         - Network
@@ -37352,6 +40606,7 @@ paths:
           description: UUID of this configuration
           required: true
           type: string
+          example: __IPSEC-CONFIGURATION-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -37371,9 +40626,15 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/ipsec-configurations"
+              $ref: "#/getDefinitions/ipsec-configurations"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: ipsec-configuration-id
+          in: query
+          description:
+          required: false
+          type: string
   /network/route-table-references/route-table-reference/{route-table-reference-id}/relationship-list/relationship:
     put:
       tags:
@@ -37395,9 +40656,10 @@ paths:
           description: Route Table Reference id, UUID assigned to this instance.
           required: true
           type: string
+          example: __ROUTE-TABLE-REFERENCE-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkRouteTableReferencesRouteTableReference.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -37422,6 +40684,7 @@ paths:
           description: Route Table Reference id, UUID assigned to this instance.
           required: true
           type: string
+          example: __ROUTE-TABLE-REFERENCE-ID__
   /network/route-table-references/route-table-reference/{route-table-reference-id}:
     get:
       tags:
@@ -37436,7 +40699,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/route-table-reference"
+              $ref: "#/getDefinitions/route-table-reference"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -37445,16 +40708,15 @@ paths:
           description: Route Table Reference id, UUID assigned to this instance.
           required: true
           type: string
-        - name: route-table-reference-fqdn
-          in: query
-          description: FQDN entry in the route table.
-          required: false
-          type: string
+          example: __ROUTE-TABLE-REFERENCE-ID__
     put:
       tags:
         - Network
       summary: create or update an existing route-table-reference
-      description: create or update an existing route-table-reference
+      description: |
+        Create or update an existing route-table-reference.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkRouteTableReferencesRouteTableReference
       consumes:
         - application/json
@@ -37471,12 +40733,52 @@ paths:
           description: Route Table Reference id, UUID assigned to this instance.
           required: true
           type: string
+          example: __ROUTE-TABLE-REFERENCE-ID__
         - name: body
           in: body
-          description: route-table-reference object that needs to be created or updated
+          description: route-table-reference object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkRouteTableReferencesRouteTableReference.json)
           required: true
           schema:
             $ref: "#/definitions/route-table-reference"
+    patch:
+      tags:
+        - Network
+      summary: update an existing route-table-reference
+      description: |
+        Update an existing route-table-reference
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkRouteTableReferencesRouteTableReference
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: route-table-reference-id
+          in: path
+          description: Route Table Reference id, UUID assigned to this instance.
+          required: true
+          type: string
+          example: __ROUTE-TABLE-REFERENCE-ID__
+        - name: body
+          in: body
+          description: route-table-reference object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/route-table-reference"
     delete:
       tags:
         - Network
@@ -37498,6 +40800,7 @@ paths:
           description: Route Table Reference id, UUID assigned to this instance.
           required: true
           type: string
+          example: __ROUTE-TABLE-REFERENCE-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -37517,9 +40820,20 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/route-table-references"
+              $ref: "#/getDefinitions/route-table-references"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: route-table-reference-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: route-table-reference-fqdn
+          in: query
+          description:
+          required: false
+          type: string
   /network/instance-groups/instance-group/{id}/relationship-list/relationship:
     put:
       tags:
@@ -37541,9 +40855,10 @@ paths:
           description: Instance Group ID, UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkInstanceGroupsInstanceGroup.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -37568,6 +40883,7 @@ paths:
           description: Instance Group ID, UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
   /network/instance-groups/instance-group/{id}:
     get:
       tags:
@@ -37582,7 +40898,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/instance-group"
+              $ref: "#/getDefinitions/instance-group"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -37591,26 +40907,15 @@ paths:
           description: Instance Group ID, UUID assigned to this instance.
           required: true
           type: string
-        - name: description
-          in: query
-          description: Descriptive text to help identify the usage of this instance-group
-          required: false
-          type: string
-        - name: type
-          in: query
-          description: Only valid value today is lower case ha for high availability
-          required: false
-          type: string
-        - name: sub-type
-          in: query
-          description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
-          required: false
-          type: string
+          example: __ID__
     put:
       tags:
         - Network
       summary: create or update an existing instance-group
-      description: create or update an existing instance-group
+      description: |
+        Create or update an existing instance-group.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkInstanceGroupsInstanceGroup
       consumes:
         - application/json
@@ -37627,12 +40932,52 @@ paths:
           description: Instance Group ID, UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: body
           in: body
-          description: instance-group object that needs to be created or updated
+          description: instance-group object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkInstanceGroupsInstanceGroup.json)
           required: true
           schema:
             $ref: "#/definitions/instance-group"
+    patch:
+      tags:
+        - Network
+      summary: update an existing instance-group
+      description: |
+        Update an existing instance-group
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkInstanceGroupsInstanceGroup
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: id
+          in: path
+          description: Instance Group ID, UUID assigned to this instance.
+          required: true
+          type: string
+          example: __ID__
+        - name: body
+          in: body
+          description: instance-group object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/instance-group"
     delete:
       tags:
         - Network
@@ -37654,6 +40999,7 @@ paths:
           description: Instance Group ID, UUID assigned to this instance.
           required: true
           type: string
+          example: __ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -37673,9 +41019,30 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/instance-groups"
+              $ref: "#/getDefinitions/instance-groups"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: description
+          in: query
+          description:
+          required: false
+          type: string
+        - name: type
+          in: query
+          description:
+          required: false
+          type: string
+        - name: sub-type
+          in: query
+          description:
+          required: false
+          type: string
   /network/zones/zone/{zone-id}/relationship-list/relationship:
     put:
       tags:
@@ -37697,9 +41064,10 @@ paths:
           description: Code assigned by AIC to the zone
           required: true
           type: string
+          example: __ZONE-ID__
         - name: body
           in: body
-          description: relationship object that needs to be created or updated
+          description: relationship object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkZonesZone.json)
           required: true
           schema:
             $ref: "#/definitions/relationship"
@@ -37724,6 +41092,7 @@ paths:
           description: Code assigned by AIC to the zone
           required: true
           type: string
+          example: __ZONE-ID__
   /network/zones/zone/{zone-id}:
     get:
       tags:
@@ -37738,7 +41107,7 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/zone"
+              $ref: "#/getDefinitions/zone"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
       parameters:
@@ -37747,21 +41116,15 @@ paths:
           description: Code assigned by AIC to the zone
           required: true
           type: string
-        - name: design-type
-          in: query
-          description: Design of zone [Medium/Large?]
-          required: false
-          type: string
-        - name: zone-context
-          in: query
-          description: Context of zone [production/test]
-          required: false
-          type: string
+          example: __ZONE-ID__
     put:
       tags:
         - Network
       summary: create or update an existing zone
-      description: create or update an existing zone
+      description: |
+        Create or update an existing zone.
+        #
+        Note! This PUT method has a corresponding PATCH method that can be used to update just a few of the fields of an existing object, rather than a full object replacement.  An example can be found in the [PATCH section] below
       operationId: createOrUpdateNetworkZonesZone
       consumes:
         - application/json
@@ -37778,12 +41141,52 @@ paths:
           description: Code assigned by AIC to the zone
           required: true
           type: string
+          example: __ZONE-ID__
         - name: body
           in: body
-          description: zone object that needs to be created or updated
+          description: zone object that needs to be created or updated. [Valid relationship examples shown here](apidocs/relations/v10/NetworkZonesZone.json)
           required: true
           schema:
             $ref: "#/definitions/zone"
+    patch:
+      tags:
+        - Network
+      summary: update an existing zone
+      description: |
+        Update an existing zone
+        #
+        Note:  Endpoints that are not devoted to object relationships support both PUT and PATCH operations.
+        The PUT operation will entirely replace an existing object.
+        The PATCH operation sends a "description of changes" for an existing object.  The entire set of changes must be applied.  An error result means no change occurs.
+        #
+        Other differences between PUT and PATCH are:
+        #
+        - For PATCH, you can send any of the values shown in sample REQUEST body.  There are no required values.
+        - For PATCH, resource-id which is a required REQUEST body element for PUT, must not be sent.
+        - PATCH cannot be used to update relationship elements; there are dedicated PUT operations for this.
+      operationId: UpdateNetworkZonesZone
+      consumes:
+        - application/json
+        - application/xml
+      produces:
+        - application/json
+        - application/xml
+      responses:
+        "default":
+          description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: zone-id
+          in: path
+          description: Code assigned by AIC to the zone
+          required: true
+          type: string
+          example: __ZONE-ID__
+        - name: body
+          in: body
+          description: zone object that needs to be updated.
+          required: true
+          schema:
+            $ref: "#/patchDefinitions/zone"
     delete:
       tags:
         - Network
@@ -37805,6 +41208,7 @@ paths:
           description: Code assigned by AIC to the zone
           required: true
           type: string
+          example: __ZONE-ID__
         - name: resource-version
           in: query
           description: resource-version for concurrency
@@ -37824,24 +41228,40 @@ paths:
         "200":
           description: successful operation
           schema:
-              $ref: "#/definitions/zones"
+              $ref: "#/getDefinitions/zones"
         "default":
           description: Response codes found in [response codes](https://wiki.onap.org/).
+      parameters:
+        - name: zone-id
+          in: query
+          description:
+          required: false
+          type: string
+        - name: design-type
+          in: query
+          description:
+          required: false
+          type: string
+        - name: zone-context
+          in: query
+          description:
+          required: false
+          type: string
 definitions:
-  search:
+  action:
     properties:
-      edge-tag-query-result:
-        type: object
-        $ref: "#/definitions/edge-tag-query-result"
-      edge-tag-query-request:
-        type: object
-        $ref: "#/definitions/edge-tag-query-request"
-      search-results:
-        type: object
-        $ref: "#/definitions/search-results"
-      sdn-zone-response:
-        type: object
-        $ref: "#/definitions/sdn-zone-response"
+      action-type:
+        type: string
+      action-data:
+        type: array
+        items:          
+          $ref: "#/definitions/action-data"
+  action-data:
+    properties:
+      property-name:
+        type: string
+      property-value:
+        type: string
   actions:
     description: |
       APIs that are more action related than REST (e.g., notify, update).
@@ -37852,103 +41272,312 @@ definitions:
       notify:
         type: object
         $ref: "#/definitions/notify"
-  relationship-data:
+  allotted-resource:
+    description: |
+      Represents a slice or partial piece of a resource that gets separately allotted
+      ###### Related Nodes
+      - TO generic-vnf( allotted-resource PartOf generic-vnf, MANY2MANY)
+      - TO instance-group( allotted-resource MemberOf instance-group, MANY2MANY)
+      - TO l3-network( allotted-resource PartOf l3-network, MANY2MANY)
+      - TO network-policy( allotted-resource Uses network-policy, ONE2ONE)
+      - TO vlan( allotted-resource PartOf vlan, MANY2MANY)
+      - TO service-instance( allotted-resource BelongsTo service-instance, MANY2ONE)(4)
+      - FROM tunnel-xconnect( tunnel-xconnect BelongsTo allotted-resource, ONE2ONE)(1)
+      - FROM service-instance( service-instance Uses allotted-resource, MANY2MANY)
+
+      -(1) IF this ALLOTTED-RESOURCE node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this ALLOTTED-RESOURCE is DELETED also
     required:
-    - relationship-key
-    - relationship-value
+    - id
     properties:
-      relationship-key:
+      id:
         type: string
-        description: A keyword provided by A&AI to indicate an attribute.
-      relationship-value:
+        description: Allotted Resource id UUID assigned to this instance.
+      description:
         type: string
-        description: Value of the attribute.
-  related-to-property:
-    properties:
-      property-key:
+        description: The descriptive information assigned to this allotted resource instance
+      selflink:
         type: string
-        description: Key part of a key/value pair
-      property-value:
+        description: Link back to more information in the controller
+      model-invariant-id:
         type: string
-        description: Value part of a key/value pair
-  relationship:
-    properties:
-      related-to:
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
         type: string
-        description: A keyword provided by A&AI to indicate type of node.
-      related-link:
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
         type: string
-        description: URL to the object in A&AI.
-      relationship-data:
+        description: the ASDC model version for this resource or service model.
+      resource-version:
+        type: string
+        description: Concurrency value
+      orchestration-status:
+        type: string
+        description: Orchestration status
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational
+      type:
+        type: string
+        description: Generic description of the type of allotted resource.
+      role:
+        type: string
+        description: role in the network that this resource will be providing.
+      tunnel-xconnects:
         type: array
-        items:          
-          $ref: "#/definitions/relationship-data"
-      related-to-property:
+        items:
+          $ref: "#/definitions/tunnel-xconnect"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+  allotted-resources:
+    description: |
+      This object is used to store slices of services being offered
+    properties:
+      allotted-resource:
         type: array
         items:          
-          $ref: "#/definitions/related-to-property"
-  relationship-list:
+          $ref: "#/definitions/allotted-resource"
+  availability-zone:
+    description: |
+      Availability zone, a collection of compute hosts/pservers
+      ###### Related Nodes
+      - TO complex( availability-zone LocatedIn complex, MANY2ONE)
+      - TO service-capability( availability-zone AppliesTo service-capability, MANY2MANY)
+      - TO cloud-region( availability-zone BelongsTo cloud-region, MANY2ONE)(4)
+      - FROM ctag-pool( ctag-pool AppliesTo availability-zone, MANY2MANY)
+      - FROM dvs-switch( dvs-switch AppliesTo availability-zone, MANY2MANY)
+      - FROM generic-vnf( generic-vnf Uses availability-zone, MANY2MANY)
+      - FROM pserver( pserver MemberOf availability-zone, MANY2ONE)
+      - FROM vce( vce Uses availability-zone, MANY2MANY)
+
+      -(4) IF this TO node is deleted, this AVAILABILITY-ZONE is DELETED also
+      -AVAILABILITY-ZONE cannot be deleted if related to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+
+    required:
+    - availability-zone-name
+    - hypervisor-type
     properties:
-      relationship:
+      availability-zone-name:
+        type: string
+        description: Name of the availability zone.  Unique across a cloud region
+      hypervisor-type:
+        type: string
+        description: Type of hypervisor.  Source of truth should define valid values.
+      operational-status:
+        type: string
+        description: State that indicates whether the availability zone should be used, etc.  Source of truth should define valid values.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+  availability-zones:
+    description: |
+      Collection of availability zones
+    properties:
+      availability-zone:
         type: array
         items:          
+          $ref: "#/definitions/availability-zone"
+  az-and-dvs-switches:
+    properties:
+      dvs-switches:
+        type: object
+        $ref: "#/definitions/dvs-switches"
+      availability-zone:
+        type: object
+        $ref: "#/definitions/availability-zone"
+  business:
+    description: |
+      Namespace for business related constructs
+    properties:
+      connectors:
+        type: array
+        items:
+          $ref: "#/definitions/connector"
+      customers:
+        type: array
+        items:
+          $ref: "#/definitions/customer"
+  class-of-service:
+    description: |
+      ###### Related Nodes
+      - TO site-pair( class-of-service BelongsTo site-pair, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this CLASS-OF-SERVICE is DELETED also
+    required:
+    - cos
+    properties:
+      cos:
+        type: string
+        description: unique identifier of probe
+      probe-id:
+        type: string
+        description: identifier of probe
+      probe-type:
+        type: string
+        description: type of probe
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
           $ref: "#/definitions/relationship"
-  ctag-pool:
+  classes-of-service:
     description: |
-      A collection of C tags (vlan tags) grouped for a specific purpose.
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      class-of-service of probe
+    properties:
+      class-of-service:
+        type: array
+        items:          
+          $ref: "#/definitions/class-of-service"
+  cloud-infrastructure:
+    description: |
+      Namespace for cloud infrastructure.
+    properties:
+      complexes:
+        type: array
+        items:
+          $ref: "#/definitions/complex"
+      cloud-regions:
+        type: array
+        items:
+          $ref: "#/definitions/cloud-region"
+      network-profiles:
+        type: array
+        items:
+          $ref: "#/definitions/network-profile"
+      pservers:
+        type: array
+        items:
+          $ref: "#/definitions/pserver"
+      virtual-data-centers:
+        type: array
+        items:
+          $ref: "#/definitions/virtual-data-center"
+  cloud-region:
+    description: |
+      cloud-region designates an installation of a cloud cluster or region or instantiation
       ###### Related Nodes
-      - TO availability-zone (Many2Many)
-      - FROM complex (is composed of ctag-pool)
-      - FROM vpls-pe
+      - TO complex( cloud-region LocatedIn complex, MANY2ONE)
+      - TO l3-network( cloud-region Uses l3-network, MANY2MANY)
+      - TO zone( cloud-region LocatedIn zone, MANY2ONE)
+      - FROM availability-zone( availability-zone BelongsTo cloud-region, MANY2ONE)(1)
+      - FROM dvs-switch( dvs-switch BelongsTo cloud-region, MANY2ONE)
+      - FROM flavor( flavor BelongsTo cloud-region, MANY2ONE)
+      - FROM group-assignment( group-assignment BelongsTo cloud-region, MANY2ONE)
+      - FROM image( image BelongsTo cloud-region, MANY2ONE)
+      - FROM oam-network( oam-network BelongsTo cloud-region, MANY2ONE)
+      - FROM snapshot( snapshot BelongsTo cloud-region, MANY2ONE)
+      - FROM tenant( tenant BelongsTo cloud-region, MANY2ONE)
+      - FROM volume-group( volume-group BelongsTo cloud-region, MANY2ONE)
+      - FROM logical-link( logical-link LocatedIn cloud-region, MANY2MANY)
+      - FROM pserver( pserver LocatedIn cloud-region, MANY2ONE)
+
+      -(1) IF this CLOUD-REGION node is deleted, this FROM node is DELETED also
+      -CLOUD-REGION cannot be deleted if related to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP
+
     required:
-    - target-pe
-    - availability-zone-name
-    - ctag-pool-purpose
+    - cloud-owner
+    - cloud-region-id
     properties:
-      target-pe:
+      cloud-owner:
         type: string
-        description: The Target provider edge router
-      availability-zone-name:
+        description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+      cloud-region-id:
         type: string
-        description: Name of the availability zone
-      ctag-pool-purpose:
+        description: Identifier used by the vendor for the region. Second part of composite key
+      cloud-type:
         type: string
-        description: Describes what the intended purpose of this pool is.
-      ctag-values:
+        description: Type of the cloud (e.g., openstack)
+      owner-defined-type:
         type: string
-        description: Comma separated list of ctags
+        description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+      cloud-region-version:
+        type: string
+        description: Software version employed at the site.  NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
+      identity-url:
+        type: string
+        description: URL of the keystone identity service
+      cloud-zone:
+        type: string
+        description: Zone where the cloud is homed.  NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+      complex-name:
+        type: string
+        description: complex name for cloud-region instance.  NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      volume-groups:
+        type: array
+        items:
+          $ref: "#/definitions/volume-group"
+      tenants:
+        type: array
+        items:
+          $ref: "#/definitions/tenant"
+      flavors:
+        type: array
+        items:
+          $ref: "#/definitions/flavor"
+      group-assignments:
+        type: array
+        items:
+          $ref: "#/definitions/group-assignment"
+      snapshots:
+        type: array
+        items:
+          $ref: "#/definitions/snapshot"
+      images:
+        type: array
+        items:
+          $ref: "#/definitions/image"
+      dvs-switches:
+        type: array
+        items:
+          $ref: "#/definitions/dvs-switch"
+      oam-networks:
+        type: array
+        items:
+          $ref: "#/definitions/oam-network"
+      availability-zones:
+        type: array
+        items:
+          $ref: "#/definitions/availability-zone"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  ctag-pools:
+  cloud-regions:
     properties:
-      ctag-pool:
+      cloud-region:
         type: array
         items:          
-          $ref: "#/definitions/ctag-pool"
+          $ref: "#/definitions/cloud-region"
   complex:
     description: |
       Collection of physical locations that can house cloud-regions.
-      ###### Default Delete Scope
-      ERROR_4_IN_EDGES_OR_CASCADE
-      ###### Related Nodes
-      - TO ctag-pool (comprises complex, Many2Many)
-      - TO l3-network (Many2Many)
-      - FROM availability-zone
-      - FROM cloud-region
-      - FROM oam-network
-      - FROM pserver
-      - FROM pnf
-      - FROM vce
-      - FROM vpls-pe
-      - FROM volume-group
-      - FROM zone
+      ###### Related Nodes
+      - TO l3-network( complex Uses l3-network, MANY2MANY)
+      - FROM availability-zone( availability-zone LocatedIn complex, MANY2ONE)
+      - FROM cloud-region( cloud-region LocatedIn complex, MANY2ONE)
+      - FROM ctag-pool( ctag-pool BelongsTo complex, MANY2ONE)(1)
+      - FROM oam-network( oam-network AppliesTo complex, MANY2MANY)
+      - FROM pnf( pnf LocatedIn complex, MANY2ONE)
+      - FROM pserver( pserver LocatedIn complex, MANY2ONE)
+      - FROM vce( vce LocatedIn complex, MANY2MANY)
+      - FROM volume-group( volume-group LocatedIn complex, MANY2ONE)
+      - FROM vpls-pe( vpls-pe LocatedIn complex, MANY2ONE)
+      - FROM zone( zone LocatedIn complex, MANY2ONE)
+
+      -(1) IF this COMPLEX node is deleted, this FROM node is DELETED also
+      -COMPLEX cannot be deleted if related to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE
+
     required:
     - physical-location-id
     - physical-location-type
@@ -38014,43 +41643,61 @@ definitions:
         type: array
         items:          
           $ref: "#/definitions/complex"
-  volume-group:
+  configuration:
     description: |
-      Persistent block-level storage.
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      Port Mirror Configuration.
       ###### Related Nodes
-      - TO complex (Many2Many)
-      - TO tenant (Many2Many)
-      - FROM cloud-region (is composed of volume-group)
-      - FROM vf-module
-      - FROM generic-vnf
+      - TO allotted-resource( configuration Uses allotted-resource, ONE2ONE)(2)
+      - TO logical-link( configuration Uses logical-link, ONE2MANY)(2)
+      - FROM metadatum( metadatum BelongsTo configuration, MANY2ONE)(1)
+      - FROM generic-vnf( generic-vnf Uses configuration, ONE2MANY)(3)
+      - FROM service-instance( service-instance Uses configuration, ONE2MANY)
+
+      -(1) IF this CONFIGURATION node is deleted, this FROM node is DELETED also
+      -(2) IF this CONFIGURATION node is deleted, this TO node is DELETED also
+      -(3) IF this FROM node is deleted, this CONFIGURATION is DELETED also
     required:
-    - volume-group-id
-    - volume-group-name
-    - vnf-type
+    - configuration-id
+    - configuration-type
+    - configuration-sub-type
+    - orchestration-status
+    - operational-status
+    - configuration-selflink
+    - model-customization-id
     properties:
-      volume-group-id:
+      configuration-id:
         type: string
-        description: Unique ID of volume-group.
-      volume-group-name:
+        description: UUID assigned to configuration.
+      management-option:
         type: string
-        description: Name of the volume group.
-      heat-stack-id:
+        description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+      configuration-name:
         type: string
-        description: Heat stack id corresponding to this volume-group
-      vnf-type:
+        description: Name of the configuration.
+      configuration-type:
         type: string
-        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+        description: port-mirroring-configuration.
+      configuration-sub-type:
+        type: string
+        description: vprobe, pprobe.
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
       orchestration-status:
         type: string
-        description: Orchestration status of this volume-group
-      model-customization-id:
+        description: Orchestration status of the configuration.
+      operational-status:
         type: string
-        description: captures the id of all the configuration used to customize the resource for the service.
-      vf-module-model-customization-id:
+        description: Indicator for whether the resource is considered operational.
+      configuration-selflink:
         type: string
-        description: helps relate the volume group to the vf-module whose components will require the volume group
+        description: URL to endpoint where AAI can get more details from SDN-GC.
+      model-customization-id:
+        type: string
+        description: id of  the configuration used to customize the resource
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
@@ -38058,499 +41705,688 @@ definitions:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  volume-groups:
+      metadata:
+        type: array
+        items:
+          $ref: "#/definitions/metadatum"
+  configurations:
     description: |
-      Collection of persistent block-level storage.
+      Collection of configurations
     properties:
-      volume-group:
+      configuration:
         type: array
         items:          
-          $ref: "#/definitions/volume-group"
-  volume:
+          $ref: "#/definitions/configuration"
+  connector:
     description: |
-      Ephemeral Block storage volume.
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      Collection of resource instances used to connect a variety of disparate inventory widgets
       ###### Related Nodes
-      - FROM vserver (is composed of volume)
+      - TO virtual-data-center( connector LocatedIn virtual-data-center, MANY2MANY)
+      - FROM metadatum( metadatum BelongsTo connector, MANY2ONE)(1)
+      - FROM service-instance( service-instance Uses connector, MANY2MANY)
+
+      -(1) IF this CONNECTOR node is deleted, this FROM node is DELETED also
     required:
-    - volume-id
-    - volume-selflink
+    - resource-instance-id
     properties:
-      volume-id:
-        type: string
-        description: Unique ID of block storage volume relative to the vserver.
-      volume-selflink:
+      resource-instance-id:
         type: string
-        description: URL to endpoint where AAI can get more details
+        description: Unique id of resource instance.
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      widget-model-id:
+        type: string
+        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+      widget-model-version:
+        type: string
+        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  volumes:
+      metadata:
+        type: array
+        items:
+          $ref: "#/definitions/metadatum"
+  connectors:
     description: |
-      Collection of ephemeral Block storage volumes.
+      Collection of resource instances used to connect a variety of disparate inventory widgets
     properties:
-      volume:
+      connector:
         type: array
         items:          
-          $ref: "#/definitions/volume"
-  l3-interface-ipv4-address-list:
+          $ref: "#/definitions/connector"
+  constrained-element-set:
     description: |
-      IPv4 Address Range
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      This is how we would capture constraints defining allowed sets of elements.
       ###### Related Nodes
-      - TO instance-group (Many2Many)
-      - TO l3-network (Many2Many)
-      - TO subnet (Many2Many)
-      - FROM l-interface (is composed of l3-interface-ipv4-address-list)
-      - FROM vlan (is composed of l3-interface-ipv4-address-list)
+      - TO model-constraint( constrained-element-set BelongsTo model-constraint, MANY2ONE)(4)
+      - TO model-element( constrained-element-set BelongsTo model-element, MANY2ONE)(4)
+      - FROM element-choice-set( element-choice-set BelongsTo constrained-element-set, MANY2ONE)(1)
+
+      -(1) IF this CONSTRAINED-ELEMENT-SET node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this CONSTRAINED-ELEMENT-SET is DELETED also
     required:
-    - l3-interface-ipv4-address
+    - constrained-element-set-uuid
+    - constraint-type
+    - check-type
     properties:
-      l3-interface-ipv4-address:
+      constrained-element-set-uuid:
         type: string
-        description: IP address
-      l3-interface-ipv4-prefix-length:
-        type: integer
-        format: int64
-        description: Prefix length, 32 for single address
-      vlan-id-inner:
-        type: integer
-        format: int64
-        description: Inner VLAN tag
-      vlan-id-outer:
-        type: integer
-        format: int64
-        description: Outer VLAN tag
-      is-floating:
-        type: boolean
-        description: Indicator of fixed or floating address
-      resource-version:
+      constraint-type:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      neutron-network-id:
+      check-type:
         type: string
-        description: Neutron network id of the interface that address belongs to
-      neutron-subnet-id:
+      resource-version:
         type: string
-        description: Neutron id of subnet that address belongs to
+      element-choice-sets:
+        type: array
+        items:
+          $ref: "#/definitions/element-choice-set"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  l3-interface-ipv6-address-list:
+  constrained-element-sets:
+    properties:
+      constrained-element-set:
+        type: array
+        items:          
+          $ref: "#/definitions/constrained-element-set"
+  ctag-assignment:
     description: |
-      IPv6 Address Range
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
       ###### Related Nodes
-      - TO instance-group (Many2Many)
-      - TO l3-network (Many2Many)
-      - TO subnet (Many2Many)
-      - FROM l-interface (is composed of l3-interface-ipv6-address-list)
-      - FROM vlan (is composed of l3-interface-ipv6-address-list)
+      - TO l3-network( ctag-assignment BelongsTo l3-network, MANY2ONE)(4)
+      - FROM service-instance( service-instance Uses ctag-assignment, ONE2MANY)
+
+      -(4) IF this TO node is deleted, this CTAG-ASSIGNMENT is DELETED also
     required:
-    - l3-interface-ipv6-address
+    - vlan-id-inner
     properties:
-      l3-interface-ipv6-address:
-        type: string
-        description: IP address
-      l3-interface-ipv6-prefix-length:
-        type: integer
-        format: int64
-        description: Prefix length, 128 for single address
       vlan-id-inner:
         type: integer
         format: int64
-        description: Inner VLAN tag
-      vlan-id-outer:
-        type: integer
-        format: int64
-        description: Outer VLAN tag
-      is-floating:
-        type: boolean
-        description: Indicator of fixed or floating address
+        description: id.
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      neutron-network-id:
-        type: string
-        description: Neutron network id of the interface that address belongs to
-      neutron-subnet-id:
-        type: string
-        description: Neutron id of subnet that address belongs to
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  vlan:
+  ctag-assignments:
+    properties:
+      ctag-assignment:
+        type: array
+        items:          
+          $ref: "#/definitions/ctag-assignment"
+  ctag-pool:
     description: |
-      Definition of vlan
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      A collection of C tags (vlan tags) grouped for a specific purpose.
       ###### Related Nodes
-      - TO l3-interface-ipv4-address-list (comprises vlan, Many2Many)
-      - TO l3-interface-ipv6-address-list (comprises vlan, Many2Many)
-      - TO multicast-configuration (Many2Many)
-      - TO logical-link (Many2Many)
-      - FROM l-interface (is composed of vlan)
-      - FROM service-instance
-      - FROM allotted-resource
+      - TO complex( ctag-pool BelongsTo complex, MANY2ONE)(4)
+      - TO availability-zone( ctag-pool AppliesTo availability-zone, MANY2MANY)
+      - FROM vpls-pe( vpls-pe Uses ctag-pool, MANY2MANY)
+
+      -(4) IF this TO node is deleted, this CTAG-POOL is DELETED also
     required:
-    - vlan-interface
-    - in-maint
+    - target-pe
+    - availability-zone-name
+    - ctag-pool-purpose
     properties:
-      vlan-interface:
+      target-pe:
         type: string
-        description: String that identifies the interface
-      vlan-id-inner:
-        type: integer
-        format: int64
-        description: Inner VLAN tag
-      vlan-id-outer:
-        type: integer
-        format: int64
-        description: Outer VLAN tag
-      resource-version:
+        description: The Target provider edge router
+      availability-zone-name:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      speed-value:
+        description: Name of the availability zone
+      ctag-pool-purpose:
         type: string
-        description: Captures the numeric part of the speed
-      speed-units:
+        description: Describes what the intended purpose of this pool is.
+      ctag-values:
         type: string
-        description: Captures the units corresponding to the speed
-      vlan-description:
+        description: Comma separated list of ctags
+      resource-version:
         type: string
-        description: Used to describe (the service associated with) the vlan
-      backdoor-connection:
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+  ctag-pools:
+    properties:
+      ctag-pool:
+        type: array
+        items:          
+          $ref: "#/definitions/ctag-pool"
+  customer:
+    description: |
+      customer identifiers to provide linkage back to BSS information.
+      ###### Related Nodes
+      - FROM service-subscription( service-subscription BelongsTo customer, MANY2ONE)(1)
+
+      -(1) IF this CUSTOMER node is deleted, this FROM node is DELETED also
+    required:
+    - global-customer-id
+    - subscriber-name
+    - subscriber-type
+    properties:
+      global-customer-id:
         type: string
-        description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
-      vpn-id:
+        description: Global customer id used across ECOMP to uniquely identify customer.
+      subscriber-name:
         type: string
-        description: This indicates the customers VPN ID associated with this vlan
-      orchestration-status:
+        description: Subscriber name, an alternate way to retrieve a customer.
+      subscriber-type:
         type: string
-        description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C.
-      in-maint:
-        type: boolean
+        description: Subscriber type, a way to provide VID with only the INFRA customers.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      service-subscriptions:
+        type: array
+        items:
+          $ref: "#/definitions/service-subscription"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-      l3-interface-ipv4-address-list:
+  customers:
+    description: |
+      Collection of customer identifiers to provide linkage back to BSS information.
+    properties:
+      customer:
         type: array
         items:          
-          $ref: "#/definitions/l3-interface-ipv4-address-list"
-      l3-interface-ipv6-address-list:
+          $ref: "#/definitions/customer"
+  cvlan-tag-entry:
+    required:
+    - cvlan-tag
+    properties:
+      cvlan-tag:
+        type: integer
+        format: int64
+        description: See mis-na-virtualization-platform.yang
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
         type: array
-        items:          
-          $ref: "#/definitions/l3-interface-ipv6-address-list"
-  vlans:
+        items:
+          $ref: "#/definitions/relationship"
+  cvlan-tags:
     properties:
-      vlan:
+      cvlan-tag-entry:
         type: array
         items:          
-          $ref: "#/definitions/vlan"
-  sriov-vf:
+          $ref: "#/definitions/cvlan-tag-entry"
+  dvs-switch:
     description: |
-      SR-IOV Virtual Function (not to be confused with virtual network function)
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      Digital virtual switch metadata, used by SDN-C to configure VCEs.  A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI. 
       ###### Related Nodes
-      - FROM l-interface (is composed of sriov-vf)
+      - TO cloud-region( dvs-switch BelongsTo cloud-region, MANY2ONE)
+      - TO availability-zone( dvs-switch AppliesTo availability-zone, MANY2MANY)
+
     required:
-    - pci-id
+    - switch-name
+    - vcenter-url
     properties:
-      pci-id:
-        type: string
-        description: PCI ID used to identify the sriov-vf
-      vf-vlan-filter:
-        type: string
-        description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
-      vf-mac-filter:
-        type: string
-        description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
-      vf-vlan-strip:
-        type: boolean
-        description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
-      vf-vlan-anti-spoof-check:
-        type: boolean
-        description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
-      vf-mac-anti-spoof-check:
-        type: boolean
-        description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
-      vf-mirrors:
+      switch-name:
         type: string
-        description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
-      vf-broadcast-allow:
-        type: boolean
-        description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
-      vf-unknown-multicast-allow:
-        type: boolean
-        description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
-      vf-unknown-unicast-allow:
-        type: boolean
-        description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
-      vf-insert-stag:
-        type: boolean
-        description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
-      vf-link-status:
+        description: DVS switch name
+      vcenter-url:
         type: string
-        description: This option is used to set the link status.  Valid values as of 1607 are on, off, and auto.
+        description: URL used to reach the vcenter
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      neutron-network-id:
-        type: string
-        description: Neutron network id of the interface
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  sriov-vfs:
+  dvs-switches:
     description: |
-      Collection of SR-IOV Virtual Functions.
+      Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
     properties:
-      sriov-vf:
+      dvs-switch:
         type: array
         items:          
-          $ref: "#/definitions/sriov-vf"
-  l-interface:
+          $ref: "#/definitions/dvs-switch"
+  edge-prop-names:
     description: |
-      Logical interfaces, e.g., a vnic.
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO instance-group (Many2Many)
-      - TO l3-interface-ipv4-address-list (comprises l-interface, Many2Many)
-      - TO l3-interface-ipv6-address-list (comprises l-interface, Many2Many)
-      - TO l-interface (comprises l-interface, One2Many)
-      - TO logical-link (Many2Many)
-      - TO vlan (comprises l-interface, Many2Many)
-      - TO sriov-vf (comprises l-interface, One2One)
-      - FROM generic-vnf (is composed of l-interface)
-      - FROM lag-interface (is composed of l-interface)
-      - FROM newvce (is composed of l-interface)
-      - FROM p-interface (is composed of l-interface)
-      - FROM vserver (is composed of l-interface)
-      - FROM l-interface (is composed of l-interface)
-    required:
-    - interface-name
-    - is-port-mirrored
-    - in-maint
+      Internal map to define the properties of an edge and interpret the map EdgeRules
     properties:
-      interface-name:
-        type: string
-        description: Name given to the interface
-      interface-role:
-        type: string
-        description: E.g., CUSTOMER, UPLINK, etc.
-      v6-wan-link-ip:
-        type: string
-        description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
-      selflink:
-        type: string
-        description: URL to endpoint where AAI can get more details
-      interface-id:
+      edgeLabel:
         type: string
-        description: ID of interface
-      macaddr:
+      direction:
         type: string
-        description: MAC address for the interface
-      network-name:
+      multiplicityRule:
         type: string
-        description: Name of the network
-      management-option:
+      isParent:
+        type: boolean
+      usesResource:
+        type: boolean
+      hasDelTarget:
+        type: boolean
+      SVC-INFRA:
+        type: boolean
+      SVC-INFRA-REV:
+        type: boolean
+  edge-tag-query-request:
+    properties:
+      edge-tag:
         type: string
-        description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
-      interface-description:
+      result-detail:
         type: string
-        description: Human friendly text regarding this interface.
-      is-port-mirrored:
-        type: boolean
-      resource-version:
+      start-node-type:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      in-maint:
-        type: boolean
-      vlans:
-        type: array
-        items:
-          $ref: "#/definitions/vlan"
-      sriov-vfs:
-        type: array
-        items:
-          $ref: "#/definitions/sriov-vf"
-      l-interfaces:
-        type: array
-        items:
-          $ref: "#/definitions/l-interface"
-      relationship-list:
+      start-node-filter:
         type: array
-        items:
-          $ref: "#/definitions/relationship"
-      l3-interface-ipv4-address-list:
+        items:          
+          $ref: "#/definitions/start-node-filter"
+      include-node-filter:
         type: array
         items:          
-          $ref: "#/definitions/l3-interface-ipv4-address-list"
-      l3-interface-ipv6-address-list:
+          $ref: "#/definitions/include-node-filter"
+      secondary-filter:
         type: array
         items:          
-          $ref: "#/definitions/l3-interface-ipv6-address-list"
-  l-interfaces:
-    description: |
-      Collection of logical interfaces.
+          $ref: "#/definitions/secondary-filter"
+  edge-tag-query-result:
     properties:
-      l-interface:
+      tagged-inventory-item-list:
         type: array
         items:          
-          $ref: "#/definitions/l-interface"
-  vserver:
+          $ref: "#/definitions/tagged-inventory-item-list"
+  element-choice-set:
     description: |
-      Virtual Servers, aka virtual machine or VM.
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO flavor (Many2One)
-      - TO image (Many2One)
-      - TO l-interface (comprises vserver, Many2Many)
-      - TO pserver (Many2One)
-      - TO volume (comprises vserver, Many2Many)
-      - TO vnfc (Many2Many)
-      - TO snapshot (One2One)
-      - TO vf-module (Many2One)
-      - FROM generic-vnf
-      - FROM tenant (is composed of vserver)
-      - FROM vce
+      This is how we would capture constraints defining allowed sets of elements.
+      ###### Related Nodes
+      - TO constrained-element-set( element-choice-set BelongsTo constrained-element-set, MANY2ONE)(4)
+      - FROM model-element( model-element BelongsTo element-choice-set, MANY2ONE)(1)
+
+      -(1) IF this ELEMENT-CHOICE-SET node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this ELEMENT-CHOICE-SET is DELETED also
     required:
-    - vserver-id
-    - vserver-name
-    - vserver-selflink
-    - in-maint
-    - is-closed-loop-disabled
+    - element-choice-set-uuid
+    - element-choice-set-name
     properties:
-      vserver-id:
-        type: string
-        description: Unique identifier for this vserver relative to its tenant
-      vserver-name:
-        type: string
-        description: Name of vserver
-      vserver-name2:
+      element-choice-set-uuid:
         type: string
-        description: Alternative name of vserver
-      prov-status:
+      element-choice-set-name:
         type: string
-        description: Trigger for operational monitoring of this resource by Service Assurance systems.
-      vserver-selflink:
+      cardinality:
         type: string
-        description: URL to endpoint where AAI can get more details
-      in-maint:
-        type: boolean
-      is-closed-loop-disabled:
-        type: boolean
       resource-version:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      volumes:
+      model-elements:
         type: array
         items:
-          $ref: "#/definitions/volume"
+          $ref: "#/definitions/model-element"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-      l-interfaces:
-        type: array
-        items:
-          $ref: "#/definitions/l-interface"
-  vservers:
-    description: |
-      Collection of virtual Servers, aka virtual machines or VMs.
+  element-choice-sets:
     properties:
-      vserver:
+      element-choice-set:
         type: array
         items:          
-          $ref: "#/definitions/vserver"
-  tenant:
+          $ref: "#/definitions/element-choice-set"
+  entitlement:
     description: |
-      Openstack tenant
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      Metadata for entitlement group.
       ###### Related Nodes
-      - TO l3-network (Many2Many)
-      - TO service-subscription (Many2Many)
-      - TO vserver (comprises tenant, One2Many)
-      - FROM cloud-region (is composed of tenant)
-      - FROM group-assignment
-      - FROM volume-group
+      - TO generic-vnf( entitlement BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO vce( entitlement BelongsTo vce, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this ENTITLEMENT is DELETED also
     required:
-    - tenant-id
-    - tenant-name
+    - group-uuid
+    - resource-uuid
     properties:
-      tenant-id:
+      group-uuid:
         type: string
-        description: Unique id relative to the cloud-region.
-      tenant-name:
+        description: Unique ID for the entitlement group the resource comes from, should be uuid.
+      resource-uuid:
         type: string
-        description: Readable name of tenant
+        description: Unique ID of an entitlement resource. 
       resource-version:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      vservers:
-        type: array
-        items:
-          $ref: "#/definitions/vserver"
+        description: Concurrency value
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  tenants:
+  entitlements:
     description: |
-      Collection of openstack tenants.
+      Entitlements, keyed by group-uuid and resource-uuid, related to license management
     properties:
-      tenant:
+      entitlement:
         type: array
         items:          
-          $ref: "#/definitions/tenant"
-  flavor:
+          $ref: "#/definitions/entitlement"
+  esr-ems:
     description: |
-      Openstack flavor.
-      ###### Default Delete Scope
-      ERROR_IF_ANY_IN_EDGES
+      Persist EMS address information used by EMS driver.
       ###### Related Nodes
-      - FROM cloud-region (is composed of flavor)
-      - FROM vserver
+      - FROM esr-system-info( esr-system-info BelongsTo esr-ems, MANY2ONE)(1)
+
+      -(1) IF this ESR-EMS node is deleted, this FROM node is DELETED also
     required:
-    - flavor-id
-    - flavor-name
-    - flavor-selflink
+    - ems-id
     properties:
-      flavor-id:
+      ems-id:
         type: string
-        description: Flavor id, expected to be unique across cloud-region.
-      flavor-name:
+        description: Unique ID of EMS.
+      resource-version:
         type: string
-        description: Flavor name
-      flavor-vcpus:
-        type: integer
-        format: int32
-        description: Number of CPUs
-      flavor-ram:
-        type: integer
-        format: int32
-        description: Amount of memory
-      flavor-disk:
-        type: integer
-        format: int32
-        description: Disk space
-      flavor-ephemeral:
-        type: integer
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      esr-system-info-list:
+        type: object
+        $ref: "#/definitions/esr-system-info-list"
+      relationship-list:
+        type: object
+        $ref: "#/definitions/relationship-list"
+  esr-ems-list:
+    properties:
+      esr-ems:
+        type: array
+        items:          
+          $ref: "#/definitions/esr-ems"
+  esr-system-info:
+    description: |
+      Persist common address information of external systems.
+      ###### Related Nodes
+      - TO esr-ems( esr-system-info BelongsTo esr-ems, MANY2ONE)(4)
+      - TO esr-vnfm( esr-system-info BelongsTo esr-vnfm, ONE2ONE)(4)
+      - TO esr-thirdparty-sdnc( esr-system-info BelongsTo esr-thirdparty-sdnc, ONE2ONE)(4)
+      - TO cloud-region( esr-system-info BelongsTo cloud-region, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this ESR-SYSTEM-INFO is DELETED also
+    required:
+    - esr-system-info-id
+    - user-name
+    - password
+    - system-type
+    properties:
+      esr-system-info-id:
+        type: string
+        description: Unique ID of esr system info.
+      system-name:
+        type: string
+        description: name of external system.
+      type:
+        type: string
+        description: type of external systems.
+      vendor:
+        type: string
+        description: vendor of external systems.
+      version:
+        type: string
+        description: version of external systems.
+      service-url:
+        type: string
+        description: url used to access external systems.
+      user-name:
+        type: string
+        description: username used to access external systems.
+      password:
+        type: string
+        description: password used to access external systems.
+      system-type:
+        type: string
+        description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+      protocol:
+        type: string
+        description: protocol of third party SDNC, for example netconf/snmp.
+      ssl-cacert:
+        type: string
+        description: ca file content if enabled ssl on auth-url.
+      ssl-insecure:
+        type: boolean
+        description: Whether to verify VIM's certificate.
+      ip-address:
+        type: string
+        description: service IP of ftp server.
+      port:
+        type: string
+        description: service port of ftp server.
+      cloud-domain:
+        type: string
+        description: domain info for authentication.
+      default-tenant:
+        type: string
+        description: default tenant of VIM.
+      passive:
+        type: boolean
+        description: ftp passive mode or not.
+      remote-path:
+        type: string
+        description: resource or performance data file path.
+      system-status:
+        type: string
+        description: the status of external system.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+  esr-system-info-list:
+    description: |
+      Collection of persistent block-level external system auth info.
+    properties:
+      esr-system-info:
+        type: array
+        items:          
+          $ref: "#/definitions/esr-system-info"
+  esr-thirdparty-sdnc:
+    description: |
+      Persist SDNC address information used by ONAP SDNC.
+      ###### Related Nodes
+      - TO pnf( esr-thirdparty-sdnc AppliesTo pnf, ONE2MANY)
+      - FROM esr-system-info( esr-system-info BelongsTo esr-thirdparty-sdnc, ONE2ONE)(1)
+
+      -(1) IF this ESR-THIRDPARTY-SDNC node is deleted, this FROM node is DELETED also
+    required:
+    - thirdparty-sdnc-id
+    properties:
+      thirdparty-sdnc-id:
+        type: string
+        description: Unique ID of SDNC.
+      location:
+        type: string
+        description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+      product-name:
+        type: string
+        description: password used to access SDNC server.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      esr-system-info-list:
+        type: object
+        $ref: "#/definitions/esr-system-info-list"
+      relationship-list:
+        type: object
+        $ref: "#/definitions/relationship-list"
+  esr-thirdparty-sdnc-list:
+    properties:
+      esr-thirdparty-sdnc:
+        type: array
+        items:          
+          $ref: "#/definitions/esr-thirdparty-sdnc"
+  esr-vnfm:
+    description: |
+      Persist VNFM address information used by VF-C.
+      ###### Related Nodes
+      - FROM esr-system-info( esr-system-info BelongsTo esr-vnfm, ONE2ONE)(1)
+
+      -(1) IF this ESR-VNFM node is deleted, this FROM node is DELETED also
+    required:
+    - vnfm-id
+    properties:
+      vnfm-id:
+        type: string
+        description: Unique ID of VNFM.
+      vim-id:
+        type: string
+        description: indecate the VIM to deploy VNF.
+      certificate-url:
+        type: string
+        description: certificate url of VNFM.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      esr-system-info-list:
+        type: object
+        $ref: "#/definitions/esr-system-info-list"
+      relationship-list:
+        type: object
+        $ref: "#/definitions/relationship-list"
+  esr-vnfm-list:
+    properties:
+      esr-vnfm:
+        type: array
+        items:          
+          $ref: "#/definitions/esr-vnfm"
+  evc:
+    description: |
+      evc object is an optional child object of the Configuration object.
+      ###### Related Nodes
+      - TO configuration( evc BelongsTo configuration, ONE2ONE)(4)
+
+      -(4) IF this TO node is deleted, this EVC is DELETED also
+    required:
+    - evc-id
+    properties:
+      evc-id:
+        type: string
+        description: Unique/key field for the evc object
+      forwarding-path-topology:
+        type: string
+        description: Point-to-Point, Multi-Point
+      cir-value:
+        type: string
+        description: Commited Information Rate
+      cir-units:
+        type: string
+        description: CIR units
+      connection-diversity-group-id:
+        type: string
+        description: Diversity Group ID
+      service-hours:
+        type: string
+        description: formerly Performance Group
+      esp-evc-circuit-id:
+        type: string
+        description: EVC Circuit ID of ESP EVC
+      esp-evc-cir-value:
+        type: string
+        description: Committed Information Rate (For ESP)
+      esp-evc-cir-units:
+        type: string
+        description: CIR units (For ESP)
+      esp-itu-code:
+        type: string
+        description: Identifies ESP
+      collector-pop-clli:
+        type: string
+        description: Collector POP CLLI (from the hostname of the access pnf)
+      inter-connect-type-ingress:
+        type: string
+        description: Interconnect type on ingress side of EVC.
+      tagmode-access-ingress:
+        type: string
+        description: tagode for collector side of EVC
+      tagmode-access-egress:
+        type: string
+        description: tagMode for network side of EVC
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+  evcs:
+    properties:
+      evc:
+        type: array
+        items:          
+          $ref: "#/definitions/evc"
+  external-system:
+    description: |
+      Namespace for external system.
+    properties:
+      esr-ems-list:
+        type: object
+        $ref: "#/definitions/esr-ems-list"
+      esr-vnfm-list:
+        type: object
+        $ref: "#/definitions/esr-vnfm-list"
+      esr-thirdparty-sdnc-list:
+        type: object
+        $ref: "#/definitions/esr-thirdparty-sdnc-list"
+  extra-properties:
+    description: |
+      Extra properties for inventory item for response list
+    properties:
+      extra-property:
+        type: array
+        items:          
+          $ref: "#/definitions/extra-property"
+  extra-property:
+    properties:
+      property-name:
+        type: string
+      property-value:
+        type: string
+  flavor:
+    description: |
+      Openstack flavor.
+      ###### Related Nodes
+      - TO cloud-region( flavor BelongsTo cloud-region, MANY2ONE)
+      - FROM vserver( vserver Uses flavor, MANY2ONE)
+
+      -FLAVOR cannot be deleted if related to VSERVER
+
+    required:
+    - flavor-id
+    - flavor-name
+    - flavor-selflink
+    properties:
+      flavor-id:
+        type: string
+        description: Flavor id, expected to be unique across cloud-region.
+      flavor-name:
+        type: string
+        description: Flavor name
+      flavor-vcpus:
+        type: integer
+        format: int32
+        description: Number of CPUs
+      flavor-ram:
+        type: integer
+        format: int32
+        description: Amount of memory
+      flavor-disk:
+        type: integer
+        format: int32
+        description: Disk space
+      flavor-ephemeral:
+        type: integer
         format: int32
         description: Amount of ephemeral disk space
       flavor-swap:
@@ -38580,15 +42416,335 @@ definitions:
         type: array
         items:          
           $ref: "#/definitions/flavor"
+  forwarder:
+    description: |
+      Entity describing a sequenced segment of forwarding path
+      ###### Related Nodes
+      - TO forwarding-path( forwarder BelongsTo forwarding-path, MANY2ONE)(4)
+      - TO l-interface( forwarder ForwardsTo l-interface, MANY2ONE)
+      - TO configuration( forwarder Uses configuration, ONE2ONE)(2)
+      - TO lag-interface( forwarder ForwardsTo lag-interface, MANY2ONE)
+      - TO p-interface( forwarder ForwardsTo p-interface, MANY2ONE)
+
+      -(2) IF this FORWARDER node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this FORWARDER is DELETED also
+    required:
+    - sequence
+    properties:
+      sequence:
+        type: integer
+        format: int32
+        description: Unique ID of this segmentation
+      forwarder-role:
+        type: string
+        description: ingress, intermediate, egress
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+  forwarder-evc:
+    description: |
+      forwarder object is an optional child object of the Configuration object.
+      ###### Related Nodes
+      - TO configuration( forwarder-evc BelongsTo configuration, ONE2ONE)(4)
+
+      -(4) IF this TO node is deleted, this FORWARDER-EVC is DELETED also
+    required:
+    - forwarder-evc-id
+    properties:
+      forwarder-evc-id:
+        type: string
+        description: Key for forwarder-evc object
+      circuit-id:
+        type: string
+        description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+      ivlan:
+        type: string
+        description: Internal VLAN.
+      svlan:
+        type: string
+        description: SVLAN value for ingress of egress forwarder.
+      cvlan:
+        type: string
+        description: CVLAN value for ingress of egress forwarder.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+  forwarder-evcs:
+    properties:
+      forwarder-evc:
+        type: array
+        items:          
+          $ref: "#/definitions/forwarder-evc"
+  forwarders:
+    properties:
+      forwarder:
+        type: array
+        items:          
+          $ref: "#/definitions/forwarder"
+  forwarding-path:
+    description: |
+      Entity that describes the sequenced forwarding path between interfaces of services or resources
+      ###### Related Nodes
+      - TO service-instance( forwarding-path AppliesTo service-instance, MANY2ONE)(4)
+      - TO configuration( forwarding-path Uses configuration, ONE2ONE)(2)
+      - FROM forwarder( forwarder BelongsTo forwarding-path, MANY2ONE)(1)
+
+      -(1) IF this FORWARDING-PATH node is deleted, this FROM node is DELETED also
+      -(2) IF this FORWARDING-PATH node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this FORWARDING-PATH is DELETED also
+    required:
+    - forwarding-path-id
+    - forwarding-path-name
+    properties:
+      forwarding-path-id:
+        type: string
+        description: Unique ID of this FP
+      forwarding-path-name:
+        type: string
+        description: Name of the FP
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+      selflink:
+        type: string
+        description: the self link for this FP
+      forwarders:
+        type: array
+        items:
+          $ref: "#/definitions/forwarder"
+  forwarding-paths:
+    properties:
+      forwarding-path:
+        type: array
+        items:          
+          $ref: "#/definitions/forwarding-path"
+  generic-vnf:
+    description: |
+      General purpose VNF
+      ###### Related Nodes
+      - TO availability-zone( generic-vnf Uses availability-zone, MANY2MANY)
+      - TO instance-group( generic-vnf MemberOf instance-group, MANY2MANY)
+      - TO ipsec-configuration( generic-vnf Uses ipsec-configuration, MANY2ONE)
+      - TO l3-network( generic-vnf Uses l3-network, MANY2MANY)
+      - TO license-key-resource( generic-vnf Uses license-key-resource, MANY2MANY)
+      - TO pserver( generic-vnf HostedOn pserver, MANY2MANY)
+      - TO vnf-image( generic-vnf Uses vnf-image, MANY2ONE)
+      - TO volume-group( generic-vnf DependsOn volume-group, ONE2MANY)
+      - TO vserver( generic-vnf HostedOn vserver, ONE2MANY)
+      - TO virtual-data-center( generic-vnf LocatedIn virtual-data-center, MANY2MANY)
+      - FROM allotted-resource( allotted-resource PartOf generic-vnf, MANY2MANY)
+      - FROM entitlement( entitlement BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM vnfc( vnfc BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM lag-interface( lag-interface BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM license( license BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM l-interface( l-interface BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM network-profile( network-profile AppliesTo generic-vnf, MANY2MANY)
+      - FROM service-instance( service-instance ComposedOf generic-vnf, ONE2MANY)
+      - FROM site-pair-set( site-pair-set AppliesTo generic-vnf, MANY2MANY)
+      - FROM vf-module( vf-module BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM logical-link( logical-link BridgedTo generic-vnf, MANY2MANY)
+
+      -(1) IF this GENERIC-VNF node is deleted, this FROM node is DELETED also
+    required:
+    - vnf-id
+    - vnf-name
+    - vnf-type
+    - in-maint
+    - is-closed-loop-disabled
+    properties:
+      vnf-id:
+        type: string
+        description: Unique id of VNF.  This is unique across the graph.
+      vnf-name:
+        type: string
+        description: Name of VNF.
+      vnf-name2:
+        type: string
+        description: Alternate name of VNF.
+      vnf-type:
+        type: string
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      service-id:
+        type: string
+        description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
+      regional-resource-zone:
+        type: string
+        description: Regional way of organizing pservers, source of truth should define values
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational.  Valid values are in-service-path and out-of-service-path.
+      license-key:
+        type: string
+        description: OBSOLETE -  do not use
+      equipment-role:
+        type: string
+        description: Client should send valid enumerated value
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, used by MSO.
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance, managed by MSO
+      mso-catalog-key:
+        type: string
+        description: Corresponds to the SDN-C catalog id used to configure this VCE
+      management-option:
+        type: string
+        description: identifier of managed by company or customer
+      ipv4-oam-address:
+        type: string
+        description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+      ipv4-loopback0-address:
+        type: string
+        description: v4 Loopback0 address
+      nm-lan-v6-address:
+        type: string
+        description: v6 Loopback address
+      management-v6-address:
+        type: string
+        description: v6 management address
+      vcpu:
+        type: integer
+        format: int64
+        description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vcpu-units:
+        type: string
+        description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vmemory:
+        type: integer
+        format: int64
+        description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vmemory-units:
+        type: string
+        description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vdisk:
+        type: integer
+        format: int64
+        description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vdisk-units:
+        type: string
+        description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only in some usecases
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true). This field (in conjunction with prov-status) is used to suppress alarms and vSCL on VNFs/VMs.
+      is-closed-loop-disabled:
+        type: boolean
+        description: used to indicate whether closed loop function is enabled on this node
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      summary-status:
+        type: string
+        description: details regarding the generic-vnf operation, PLEASE DISCONTINUE USE OF THIS FIELD.
+      encrypted-access-flag:
+        type: boolean
+        description: indicates whether generic-vnf access uses SSH
+      entitlement-assignment-group-uuid:
+        type: string
+        description: UUID of the Entitlement group used for licensing VNFs, OBSOLETE -  See child relationships.
+      entitlement-resource-uuid:
+        type: string
+        description: UUID of the specific entitlement resource.  OBSOLETE -  See child relationships.
+      license-assignment-group-uuid:
+        type: string
+        description: UUID of the license assignment group.  OBSOLETE -  See child relationships.
+      license-key-uuid:
+        type: string
+        description: UUID of the actual license resource.  OBSOLETE -  See child relationships.
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      model-customization-id:
+        type: string
+        description: captures the id of all the configuration used to customize the resource for the service.
+      widget-model-id:
+        type: string
+        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+      widget-model-version:
+        type: string
+        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+      as-number:
+        type: string
+        description: as-number of the VNF
+      regional-resource-subzone:
+        type: string
+        description: represents sub zone of the rr plane
+      nf-type:
+        type: string
+        description: Generic description of the type of NF
+      nf-function:
+        type: string
+        description: English description of Network function that the specific VNF deployment is providing
+      nf-role:
+        type: string
+        description: role in the network that this model will be providing
+      nf-naming-code:
+        type: string
+        description: string assigned to this model used for naming purposes
+      selflink:
+        type: string
+        description: Path to the controller object.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+      l-interfaces:
+        type: array
+        items:
+          $ref: "#/definitions/l-interface"
+      lag-interfaces:
+        type: array
+        items:
+          $ref: "#/definitions/lag-interface"
+      vf-modules:
+        type: array
+        items:
+          $ref: "#/definitions/vf-module"
+      licenses:
+        type: array
+        items:
+          $ref: "#/definitions/license"
+      entitlements:
+        type: array
+        items:
+          $ref: "#/definitions/entitlement"
+  generic-vnfs:
+    description: |
+      Collection of VNFs
+    properties:
+      generic-vnf:
+        type: array
+        items:          
+          $ref: "#/definitions/generic-vnf"
   group-assignment:
     description: |
       Openstack group-assignment used to store exclusivity groups (EG).
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
       ###### Related Nodes
-      - TO tenant (Many2Many)
-      - TO pserver (One2Many)
-      - FROM cloud-region (is composed of group-assignment)
+      - TO cloud-region( group-assignment BelongsTo cloud-region, MANY2ONE)
+      - FROM pserver( pserver MemberOf group-assignment, MANY2ONE)
+      - FROM tenant( tenant MemberOf group-assignment, MANY2MANY)
+
     required:
     - group-id
     - group-type
@@ -38621,47 +42777,75 @@ definitions:
         type: array
         items:          
           $ref: "#/definitions/group-assignment"
-  snapshot:
+  host-route:
     description: |
-      Openstack snapshot
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
       ###### Related Nodes
-      - FROM cloud-region (is composed of snapshot)
-      - FROM vserver
+      - TO subnet( host-route BelongsTo subnet, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this HOST-ROUTE is DELETED also
     required:
-    - snapshot-id
+    - host-route-id
+    - route-prefix
+    - next-hop
     properties:
-      snapshot-id:
-        type: string
-        description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
-      snapshot-name:
+      host-route-id:
         type: string
-        description: Snapshot name
-      snapshot-architecture:
+        description: host-route id
+      route-prefix:
         type: string
-        description: Operating system architecture
-      snapshot-os-distro:
+        description: subnet prefix
+      next-hop:
         type: string
-        description: The common name of the operating system distribution in lowercase
-      snapshot-os-version:
+        description: Could be ip-address, hostname, or service-instance
+      next-hop-type:
         type: string
-        description: The operating system version as specified by the distributor.
-      application:
+        description: Should be ip-address, hostname, or service-instance to match next-hop
+      resource-version:
         type: string
-        description: The application that the image instantiates.
-      application-vendor:
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+  host-routes:
+    properties:
+      host-route:
+        type: array
+        items:          
+          $ref: "#/definitions/host-route"
+  hpa-capabilities:
+    description: |
+      Collection of HPA Capabilities
+    properties:
+      hpa-capability:
+        type: array
+        items:          
+          $ref: "#/definitions/hpa-capability"
+  hpa-capability:
+    description: |
+      Represents a HPA capability
+      ###### Related Nodes
+      - TO flavor( hpa-capability BelongsTo flavor, MANY2ONE)
+      - TO cloud-region( hpa-capability BelongsTo cloud-region, MANY2ONE)
+      - FROM hpa-feature-attributes( hpa-feature-attributes BelongsTo hpa-capability, MANY2ONE)(1)
+
+      -(1) IF this HPA-CAPABILITY node is deleted, this FROM node is DELETED also
+    required:
+    - hpa-capability-id
+    - hpa-feature
+    properties:
+      hpa-capability-id:
         type: string
-        description: The vendor of the application.
-      application-version:
+        description: UUID to uniquely identify a HPA capability
+      hpa-feature:
         type: string
-        description: The version of the application.
-      snapshot-selflink:
+        description: Name of the HPACapability
+      hpa-version:
         type: string
-        description: URL to endpoint where AAI can get more details
-      prev-snapshot-id:
+        description: HPA schema version
+      architecture:
         type: string
-        description: This field contains the UUID of the previous snapshot (if any).
+        description: Hardware architecture
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
@@ -38669,54 +42853,44 @@ definitions:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  snapshots:
-    description: |
-      Collection of openstack snapshots
-    properties:
-      snapshot:
+      hpa-feature-attributes:
         type: array
         items:          
-          $ref: "#/definitions/snapshot"
-  metadatum:
+          $ref: "#/definitions/hpa-feature-attributes"
+  hpa-feature-attributes:
     description: |
-      Key/value pairs
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      HPA Capability Feature attributes
       ###### Related Nodes
-      - FROM image (is composed of metadatum)
-      - FROM model-ver (is composed of metadatum)
-      - FROM service-instance (is composed of metadatum)
-      - FROM connector (is composed of metadatum)
+      - TO hpa-capability( hpa-feature-attributes BelongsTo hpa-capability, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this HPA-FEATURE-ATTRIBUTES is DELETED also
     required:
-    - metaname
-    - metaval
+    - hpa-attribute-key
     properties:
-      metaname:
+      hpa-attribute-key:
         type: string
-      metaval:
+        description: name of the specific HPA attribute
+      hpa-attribute-value:
         type: string
+        description: JSON string specifying the value, unit and type of the specific HPA attribute
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-  metadata:
-    description: |
-      Collection of metadatum (key/value pairs)
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
-    properties:
-      metadatum:
+      relationship-list:
         type: array
-        items:          
-          $ref: "#/definitions/metadatum"
+        items:
+          $ref: "#/definitions/relationship"
   image:
     description: |
       Openstack image.
-      ###### Default Delete Scope
-      ERROR_4_IN_EDGES_OR_CASCADE
       ###### Related Nodes
-      - TO metadatum (comprises image, Many2Many)
-      - FROM cloud-region (is composed of image)
-      - FROM vserver
+      - TO cloud-region( image BelongsTo cloud-region, MANY2ONE)
+      - FROM metadatum( metadatum BelongsTo image, MANY2ONE)(1)
+      - FROM vserver( vserver Uses image, MANY2ONE)
+
+      -(1) IF this IMAGE node is deleted, this FROM node is DELETED also
+      -IMAGE cannot be deleted if related to VSERVER
+
     required:
     - image-id
     - image-name
@@ -38770,112 +42944,203 @@ definitions:
         type: array
         items:          
           $ref: "#/definitions/image"
-  dvs-switch:
+  include-node-filter:
+    properties:
+      include-node-type:
+        type: string
+  instance-filter:
     description: |
-      Digital virtual switch metadata, used by SDN-C to configure VCEs.  A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI. 
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      InstanceFilter for performing a named-query or model query
+  instance-filters:
+    description: |
+      InstanceFilters for performing a named-query or model query
+    properties:
+      instance-filter:
+        type: array
+        items:          
+          $ref: "#/definitions/instance-filter"
+  instance-group:
+    description: |
+      General mechanism for grouping instances
       ###### Related Nodes
-      - TO availability-zone (Many2Many)
-      - FROM cloud-region (is composed of dvs-switch)
+      - TO model( instance-group Targets model, MANY2MANY)
+      - FROM allotted-resource( allotted-resource MemberOf instance-group, MANY2MANY)
+      - FROM generic-vnf( generic-vnf MemberOf instance-group, MANY2MANY)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list MemberOf instance-group, MANY2MANY)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list MemberOf instance-group, MANY2MANY)
+      - FROM l-interface( l-interface MemberOf instance-group, MANY2MANY)
+      - FROM pnf( pnf MemberOf instance-group, MANY2MANY)
+      - FROM service-instance( service-instance MemberOf instance-group, MANY2MANY)
+
     required:
-    - switch-name
-    - vcenter-url
+    - id
+    - description
+    - type
     properties:
-      switch-name:
+      id:
         type: string
-        description: DVS switch name
-      vcenter-url:
+        description: Instance Group ID, UUID assigned to this instance.
+      description:
         type: string
-        description: URL used to reach the vcenter
+        description: Descriptive text to help identify the usage of this instance-group
+      type:
+        type: string
+        description: Only valid value today is lower case ha for high availability
+      sub-type:
+        type: string
+        description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
       resource-version:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+        description: Concurrency value
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  dvs-switches:
+  instance-groups:
     description: |
-      Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+      Collection of openstack route table references
     properties:
-      dvs-switch:
+      instance-group:
         type: array
         items:          
-          $ref: "#/definitions/dvs-switch"
-  oam-network:
-    description: |
-      OAM network, to be deprecated shortly.  Do not use for new purposes. 
-      ###### Default Delete Scope
-      ERROR_IF_ANY_IN_EDGES
-      ###### Related Nodes
-      - TO complex (Many2Many)
-      - TO service-capability (Many2Many)
-      - FROM cloud-region (is composed of oam-network)
-    required:
-    - network-uuid
-    - network-name
-    - cvlan-tag
+          $ref: "#/definitions/instance-group"
+  inventory:
     properties:
-      network-uuid:
+      search:
+        type: object
+        $ref: "#/definitions/search"
+      actions:
+        type: object
+        $ref: "#/definitions/actions"
+      cloud-infrastructure:
+        type: object
+        $ref: "#/definitions/cloud-infrastructure"
+      business:
+        type: object
+        $ref: "#/definitions/business"
+      service-design-and-creation:
+        type: object
+        $ref: "#/definitions/service-design-and-creation"
+      network:
+        type: object
+        $ref: "#/definitions/network"
+      nodes:
+        type: object
+        $ref: "#/definitions/nodes"
+  inventory-item:
+    properties:
+      inventory-item-type:
         type: string
-        description: UUID of the network. Unique across a cloud-region
-      network-name:
+      inventory-item-link:
         type: string
-        description: Name of the network.
-      cvlan-tag:
-        type: integer
-        format: int64
-        description: cvlan-id
-      ipv4-oam-gateway-address:
+      inventory-item-data:
+        type: array
+        items:          
+          $ref: "#/definitions/inventory-item-data"
+      tagged-inventory-item-list:
+        type: array
+        items:          
+          $ref: "#/definitions/tagged-inventory-item-list"
+  inventory-item-data:
+    properties:
+      property-name:
         type: string
-        description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
-      ipv4-oam-gateway-address-prefix-length:
-        type: integer
-        format: int32
-        description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
-      resource-version:
+      property-value:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-  oam-networks:
+  inventory-response-item:
     description: |
-      Collection of OAM networks, to be deprecated shortly.  Do not use for new purposes. 
+      Inventory item for response list
     properties:
-      oam-network:
+      model-name:
+        type: string
+      extra-properties:
+        type: object
+        $ref: "#/definitions/extra-properties"
+      inventory-response-items:
+        type: object
+        $ref: "#/definitions/inventory-response-items"
+  inventory-response-items:
+    description: |
+      Container for inventory items in response list
+    properties:
+      inventory-response-item:
         type: array
         items:          
-          $ref: "#/definitions/oam-network"
-  availability-zone:
+          $ref: "#/definitions/inventory-response-item"
+  ipsec-configuration:
     description: |
-      Availability zone, a collection of compute hosts/pservers
-      ###### Default Delete Scope
-      ERROR_IF_ANY_IN_EDGES
-      ###### Related Nodes
-      - TO complex (Many2Many)
-      - TO service-capability (Many2Many)
-      - FROM cloud-region (is composed of availability-zone)
-      - FROM ctag-pool
-      - FROM dvs-switch
-      - FROM generic-vnf
-      - FROM pserver
-      - FROM vce
+      IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+      ###### Related Nodes
+      - FROM generic-vnf( generic-vnf Uses ipsec-configuration, MANY2ONE)
+      - FROM vig-server( vig-server BelongsTo ipsec-configuration, MANY2ONE)(1)
+
+      -(1) IF this IPSEC-CONFIGURATION node is deleted, this FROM node is DELETED also
     required:
-    - availability-zone-name
-    - hypervisor-type
+    - ipsec-configuration-id
     properties:
-      availability-zone-name:
+      ipsec-configuration-id:
         type: string
-        description: Name of the availability zone.  Unique across a cloud region
-      hypervisor-type:
+        description: UUID of this configuration
+      requested-vig-address-type:
         type: string
-        description: Type of hypervisor.  Source of truth should define valid values.
-      operational-status:
+        description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+      requested-encryption-strength:
         type: string
-        description: State that indicates whether the availability zone should be used, etc.  Source of truth should define valid values.
+        description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+      requested-dmz-type:
+        type: string
+        description: can offer a shared DMZ or a DMZ specific to a customer
+      shared-dmz-network-address:
+        type: string
+        description: Network address of shared DMZ
+      requested-customer-name:
+        type: string
+        description: If the DMZ is a custom DMZ, this field will indicate the customer information
+      ike-version:
+        type: string
+        description: can be 1 or 2
+      ikev1-authentication:
+        type: string
+        description: Contains values like md5, sha1, sha256, sha384
+      ikev1-encryption:
+        type: string
+        description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+      ikev1-dh-group:
+        type: string
+        description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+      ikev1-am-group-id:
+        type: string
+        description: Group name defined in VIG for clients using aggressive mode
+      ikev1-am-password:
+        type: string
+        description: pre-shared key for the above group name 
+      ikev1-sa-lifetime:
+        type: string
+        description: Lifetime for IKEv1 SA
+      ipsec-authentication:
+        type: string
+        description: md5, sha1, sha256, sha384
+      ipsec-encryption:
+        type: string
+        description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+      ipsec-sa-lifetime:
+        type: string
+        description: Life time for IPSec SA
+      ipsec-pfs:
+        type: string
+        description: enable PFS or not
+      xauth-userid:
+        type: string
+        description: user ID for xAuth, sm-user, ,nmteHostName
+      xauth-user-password:
+        type: string
+        description: Encrypted using the Juniper $9$ algorithm
+      dpd-interval:
+        type: string
+        description: The time between DPD probe
+      dpd-frequency:
+        type: string
+        description: Maximum number of DPD before claiming the tunnel is down
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
@@ -38883,218 +43148,353 @@ definitions:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  availability-zones:
-    description: |
-      Collection of availability zones
+      vig-servers:
+        type: array
+        items:
+          $ref: "#/definitions/vig-server"
+  ipsec-configurations:
     properties:
-      availability-zone:
+      ipsec-configuration:
         type: array
         items:          
-          $ref: "#/definitions/availability-zone"
-  cloud-region:
+          $ref: "#/definitions/ipsec-configuration"
+  key-data:
+    properties:
+      key-name:
+        type: string
+      key-value:
+        type: string
+  l-interface:
     description: |
-      cloud-region designates an installation of a cloud cluster or region or instantiation
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
-      ###### Related Nodes
-      - TO complex (Many2One)
-      - TO l3-network (Many2Many)
-      - TO tenant (comprises cloud-region, One2Many)
-      - TO image (comprises cloud-region, One2Many)
-      - TO flavor (comprises cloud-region, One2Many)
-      - TO availability-zone (comprises cloud-region, One2Many)
-      - TO oam-network (comprises cloud-region, One2Many)
-      - TO dvs-switch (comprises cloud-region, One2Many)
-      - TO volume-group (comprises cloud-region, One2Many)
-      - TO group-assignment (comprises cloud-region, One2Many)
-      - TO snapshot (comprises cloud-region, One2Many)
-      - TO zone (Many2One)
-      - FROM pserver
-      - FROM logical-link
+      Logical interfaces, e.g., a vnic.
+      ###### Related Nodes
+      - TO generic-vnf( l-interface BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO lag-interface( l-interface BelongsTo lag-interface, MANY2ONE)(4)
+      - TO instance-group( l-interface MemberOf instance-group, MANY2MANY)
+      - TO l-interface( l-interface BelongsTo l-interface, MANY2ONE)(4)
+      - TO logical-link( l-interface LinksTo logical-link, MANY2MANY)(2)
+      - TO newvce( l-interface BelongsTo newvce, MANY2ONE)(4)
+      - TO p-interface( l-interface BindsTo p-interface, MANY2ONE)(4)
+      - TO vserver( l-interface BindsTo vserver, MANY2ONE)(4)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list BelongsTo l-interface, MANY2ONE)(1)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list BelongsTo l-interface, MANY2ONE)(1)
+      - FROM sriov-vf( sriov-vf BelongsTo l-interface, ONE2ONE)(1)
+      - FROM vlan( vlan LinksTo l-interface, MANY2ONE)(1)
+      - FROM l-interface( l-interface BelongsTo l-interface, MANY2ONE)(4)
+
+      -(1) IF this L-INTERFACE node is deleted, this FROM node is DELETED also
+      -(2) IF this L-INTERFACE node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this L-INTERFACE is DELETED also
     required:
-    - cloud-owner
-    - cloud-region-id
+    - interface-name
+    - is-port-mirrored
+    - in-maint
     properties:
-      cloud-owner:
+      interface-name:
         type: string
-        description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
-      cloud-region-id:
+        description: Name given to the interface
+      interface-role:
         type: string
-        description: Identifier used by the vendor for the region. Second part of composite key
-      cloud-type:
+        description: E.g., CUSTOMER, UPLINK, etc.
+      v6-wan-link-ip:
         type: string
-        description: Type of the cloud (e.g., openstack)
-      owner-defined-type:
+        description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+      selflink:
         type: string
-        description: Cloud-owner defined type indicator (e.g., dcp, lcp)
-      cloud-region-version:
+        description: URL to endpoint where AAI can get more details
+      interface-id:
         type: string
-        description: Software version employed at the site.  NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
-      identity-url:
+        description: ID of interface
+      macaddr:
         type: string
-        description: URL of the keystone identity service
-      cloud-zone:
+        description: MAC address for the interface
+      network-name:
         type: string
-        description: Zone where the cloud is homed.  NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
-      complex-name:
+        description: Name of the network
+      management-option:
         type: string
-        description: complex name for cloud-region instance.  NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+        description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+      interface-description:
+        type: string
+        description: Human friendly text regarding this interface.
+      is-port-mirrored:
+        type: boolean
+        description: boolean indicatating whether or not port is a mirrored.
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      volume-groups:
-        type: array
-        items:
-          $ref: "#/definitions/volume-group"
-      tenants:
-        type: array
-        items:
-          $ref: "#/definitions/tenant"
-      flavors:
-        type: array
-        items:
-          $ref: "#/definitions/flavor"
-      group-assignments:
-        type: array
-        items:
-          $ref: "#/definitions/group-assignment"
-      snapshots:
-        type: array
-        items:
-          $ref: "#/definitions/snapshot"
-      images:
-        type: array
-        items:
-          $ref: "#/definitions/image"
-      dvs-switches:
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true)
+      vlans:
         type: array
         items:
-          $ref: "#/definitions/dvs-switch"
-      oam-networks:
+          $ref: "#/definitions/vlan"
+      sriov-vfs:
         type: array
         items:
-          $ref: "#/definitions/oam-network"
-      availability-zones:
+          $ref: "#/definitions/sriov-vf"
+      l-interfaces:
         type: array
         items:
-          $ref: "#/definitions/availability-zone"
+          $ref: "#/definitions/l-interface"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  cloud-regions:
+      l3-interface-ipv4-address-list:
+        type: array
+        items:          
+          $ref: "#/definitions/l3-interface-ipv4-address-list"
+      l3-interface-ipv6-address-list:
+        type: array
+        items:          
+          $ref: "#/definitions/l3-interface-ipv6-address-list"
+  l-interfaces:
+    description: |
+      Collection of logical interfaces.
     properties:
-      cloud-region:
+      l-interface:
         type: array
         items:          
-          $ref: "#/definitions/cloud-region"
-  network-profile:
+          $ref: "#/definitions/l-interface"
+  l3-interface-ipv4-address-list:
     description: |
-      Network profile populated by SDN-GP for SNMP
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      IPv4 Address Range
       ###### Related Nodes
-      - FROM generic-vnf
+      - TO instance-group( l3-interface-ipv4-address-list MemberOf instance-group, MANY2MANY)
+      - TO l3-network( l3-interface-ipv4-address-list MemberOf l3-network, MANY2MANY)
+      - TO subnet( l3-interface-ipv4-address-list MemberOf subnet, MANY2MANY)
+      - TO l-interface( l3-interface-ipv4-address-list BelongsTo l-interface, MANY2ONE)(4)
+      - TO vlan( l3-interface-ipv4-address-list BelongsTo vlan, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this L3-INTERFACE-IPV4-ADDRESS-LIST is DELETED also
     required:
-    - nm-profile-name
+    - l3-interface-ipv4-address
     properties:
-      nm-profile-name:
-        type: string
-        description: Unique name of network profile.
-      community-string:
+      l3-interface-ipv4-address:
         type: string
-        description: Encrypted SNMP community string
+        description: IP address
+      l3-interface-ipv4-prefix-length:
+        type: integer
+        format: int64
+        description: Prefix length, 32 for single address
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      is-floating:
+        type: boolean
+        description: Indicator of fixed or floating address
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      neutron-network-id:
+        type: string
+        description: Neutron network id of the interface that address belongs to
+      neutron-subnet-id:
+        type: string
+        description: Neutron id of subnet that address belongs to
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  network-profiles:
+  l3-interface-ipv6-address-list:
     description: |
-      Collection of network profiles
+      IPv6 Address Range
+      ###### Related Nodes
+      - TO instance-group( l3-interface-ipv6-address-list MemberOf instance-group, MANY2MANY)
+      - TO l3-network( l3-interface-ipv6-address-list MemberOf l3-network, MANY2MANY)
+      - TO subnet( l3-interface-ipv6-address-list MemberOf subnet, MANY2MANY)
+      - TO l-interface( l3-interface-ipv6-address-list BelongsTo l-interface, MANY2ONE)(4)
+      - TO vlan( l3-interface-ipv6-address-list BelongsTo vlan, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this L3-INTERFACE-IPV6-ADDRESS-LIST is DELETED also
+    required:
+    - l3-interface-ipv6-address
     properties:
-      network-profile:
+      l3-interface-ipv6-address:
+        type: string
+        description: IP address
+      l3-interface-ipv6-prefix-length:
+        type: integer
+        format: int64
+        description: Prefix length, 128 for single address
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      is-floating:
+        type: boolean
+        description: Indicator of fixed or floating address
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      neutron-network-id:
+        type: string
+        description: Neutron network id of the interface that address belongs to
+      neutron-subnet-id:
+        type: string
+        description: Neutron id of subnet that address belongs to
+      relationship-list:
         type: array
-        items:          
-          $ref: "#/definitions/network-profile"
-  p-interface:
+        items:
+          $ref: "#/definitions/relationship"
+  l3-network:
     description: |
-      Physical interface (e.g., nic)
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      Generic network definition
       ###### Related Nodes
-      - TO l-interface (comprises p-interface, Many2Many)
-      - TO physical-link (Many2Many)
-      - TO logical-link (Many2One)
-      - FROM lag-interface
-      - FROM pserver (is composed of p-interface)
-      - FROM pnf (is composed of p-interface)
-      - FROM vpls-pe (is composed of p-interface)
+      - TO network-policy( l3-network Uses network-policy, MANY2MANY)
+      - TO route-table-reference( l3-network Uses route-table-reference, MANY2MANY)
+      - TO vpn-binding( l3-network Uses vpn-binding, MANY2MANY)
+      - FROM allotted-resource( allotted-resource PartOf l3-network, MANY2MANY)
+      - FROM cloud-region( cloud-region Uses l3-network, MANY2MANY)
+      - FROM complex( complex Uses l3-network, MANY2MANY)
+      - FROM generic-vnf( generic-vnf Uses l3-network, MANY2MANY)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list MemberOf l3-network, MANY2MANY)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list MemberOf l3-network, MANY2MANY)
+      - FROM ctag-assignment( ctag-assignment BelongsTo l3-network, MANY2ONE)(1)
+      - FROM segmentation-assignment( segmentation-assignment BelongsTo l3-network, MANY2ONE)(1)
+      - FROM service-instance( service-instance ComposedOf l3-network, ONE2MANY)
+      - FROM subnet( subnet BelongsTo l3-network, MANY2ONE)(1)
+      - FROM tenant( tenant Uses l3-network, MANY2MANY)
+      - FROM vf-module( vf-module DependsOn l3-network, MANY2MANY)
+
+      -(1) IF this L3-NETWORK node is deleted, this FROM node is DELETED also
     required:
-    - interface-name
-    - in-maint
+    - network-id
+    - network-name
+    - is-bound-to-vpn
+    - is-provider-network
+    - is-shared-network
+    - is-external-network
     properties:
-      interface-name:
-        type: string
-        description: Name that identifies the physical interface
-      speed-value:
+      network-id:
         type: string
-        description: Captures the numeric part of the speed
-      speed-units:
+        description: Network ID, should be uuid. Unique across A&AI.
+      network-name:
         type: string
-        description: Captures the units corresponding to the speed
-      port-description:
+        description: Name of the network, governed by some naming convention..
+      network-type:
         type: string
-        description: Nature of the services and connectivity on this port.
-      equipment-identifier:
+        description: Type of the network - who defines these values?
+      network-role:
         type: string
-        description: CLEI or other specification for p-interface hardware.
-      interface-role:
+        description: Role the network plans - who defines these values?
+      network-technology:
         type: string
-        description: Role specification for p-interface hardware.
-      interface-type:
+        description: Network technology - who defines these values?
+      neutron-network-id:
         type: string
-        description: Indicates the physical properties of the interface.
-      prov-status:
+        description: Neutron network id of this Interface
+      is-bound-to-vpn:
+        type: boolean
+        description: Set to true if bound to VPN
+      service-id:
         type: string
-        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+        description: Unique identifier of service from ASDC.  Does not strictly map to ASDC services.  SOON TO BE DEPRECATED
+      network-role-instance:
+        type: integer
+        format: int64
+        description: network role instance
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      in-maint:
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, mastered by MSO
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance, managed by MSO
+      mso-catalog-key:
+        type: string
+        description: Corresponds to the SDN-C catalog id used to configure this VCE
+      contrail-network-fqdn:
+        type: string
+        description: Contrail FQDN for the network
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      model-customization-id:
+        type: string
+        description: captures the id of all the configuration used to customize the resource for the service.
+      widget-model-id:
+        type: string
+        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+      widget-model-version:
+        type: string
+        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+      physical-network-name:
+        type: string
+        description: Name associated with the physical network.
+      is-provider-network:
         type: boolean
-      relationship-list:
+        description: boolean indicatating whether or not network is a provider network.
+      is-shared-network:
+        type: boolean
+        description: boolean indicatating whether or not network is a shared network.
+      is-external-network:
+        type: boolean
+        description: boolean indicatating whether or not network is an external network.
+      selflink:
+        type: string
+        description: Path to the controller object.
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational.
+      subnets:
         type: array
         items:
-          $ref: "#/definitions/relationship"
-      l-interfaces:
+          $ref: "#/definitions/subnet"
+      ctag-assignments:
         type: array
         items:
-          $ref: "#/definitions/l-interface"
-  p-interfaces:
-    description: |
-      Collection of physical interfaces.
+          $ref: "#/definitions/ctag-assignment"
+      segmentation-assignments:
+        type: array
+        items:
+          $ref: "#/definitions/segmentation-assignment"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+        description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding
+  l3-networks:
     properties:
-      p-interface:
+      l3-network:
         type: array
         items:          
-          $ref: "#/definitions/p-interface"
+          $ref: "#/definitions/l3-network"
   lag-interface:
     description: |
       Link aggregate interface
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO logical-link (Many2Many)
-      - TO lag-link (Many2Many)
-      - TO p-interface (Many2Many)
-      - TO l-interface (comprises lag-interface, Many2Many)
-      - FROM generic-vnf (is composed of lag-interface)
-      - FROM pserver (is composed of lag-interface)
-      - FROM pnf (is composed of lag-interface)
-      - FROM vpls-pe (is composed of lag-interface)
+      ###### Related Nodes
+      - TO generic-vnf( lag-interface BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO lag-link( lag-interface LinksTo lag-link, MANY2MANY)(2)
+      - TO logical-link( lag-interface Uses logical-link, MANY2MANY)(2)
+      - TO p-interface( lag-interface Uses p-interface, MANY2MANY)
+      - TO pnf( lag-interface BindsTo pnf, MANY2ONE)(4)
+      - TO pserver( lag-interface BindsTo pserver, MANY2ONE)(4)
+      - TO vpls-pe( lag-interface BindsTo vpls-pe, MANY2ONE)(4)
+      - FROM l-interface( l-interface BelongsTo lag-interface, MANY2ONE)(1)
+
+      -(1) IF this LAG-INTERFACE node is deleted, this FROM node is DELETED also
+      -(2) IF this LAG-INTERFACE node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this LAG-INTERFACE is DELETED also
     required:
     - interface-name
     - in-maint
@@ -39125,6 +43525,7 @@ definitions:
         description: Trigger for operational monitoring of this resource by Service Assurance systems.
       in-maint:
         type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true)
       relationship-list:
         type: array
         items:
@@ -39141,196 +43542,137 @@ definitions:
         type: array
         items:          
           $ref: "#/definitions/lag-interface"
-  pserver:
+  lag-link:
     description: |
-      Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
-      ###### Default Delete Scope
-      ERROR_4_IN_EDGES_OR_CASCADE
-      ###### Related Nodes
-      - TO complex (Many2One)
-      - TO cloud-region (Many2One)
-      - TO availability-zone (Many2One)
-      - TO lag-interface (comprises pserver, Many2Many)
-      - TO p-interface (comprises pserver, Many2Many)
-      - TO zone (Many2One)
-      - FROM generic-vnf
-      - FROM group-assignment
-      - FROM vserver
-      - FROM logical-link
+      LAG links can connect lag-interfaces
+      ###### Related Nodes
+      - FROM lag-interface( lag-interface LinksTo lag-link, MANY2MANY)(3)
+      - FROM logical-link( logical-link Uses lag-link, MANY2MANY)
+
+      -(3) IF this FROM node is deleted, this LAG-LINK is DELETED also
     required:
-    - hostname
-    - in-maint
+    - link-name
     properties:
-      hostname:
+      link-name:
         type: string
-        description: Value from executing hostname on the compute node.
-      ptnii-equip-name:
-        type: string
-        description: PTNII name
-      number-of-cpus:
-        type: integer
-        format: int32
-        description: Number of cpus
-      disk-in-gigabytes:
-        type: integer
-        format: int32
-        description: Disk size, in GBs
-      ram-in-megabytes:
-        type: integer
-        format: int32
-        description: RAM size, in MBs
-      equip-type:
-        type: string
-        description: Equipment type.  Source of truth should define valid values.
-      equip-vendor:
-        type: string
-        description: Equipment vendor.  Source of truth should define valid values.
-      equip-model:
-        type: string
-        description: Equipment model.  Source of truth should define valid values.
-      fqdn:
-        type: string
-        description: Fully-qualified domain name
-      pserver-selflink:
-        type: string
-        description: URL to endpoint where AAI can get more details
-      ipv4-oam-address:
-        type: string
-        description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device.
-      serial-number:
-        type: string
-        description: Serial number, may be queried
-      ipaddress-v4-loopback-0:
-        type: string
-        description: IPV4 Loopback 0 address
-      ipaddress-v6-loopback-0:
-        type: string
-        description: IPV6 Loopback 0 address
-      ipaddress-v4-aim:
-        type: string
-        description: IPV4 AIM address
-      ipaddress-v6-aim:
-        type: string
-        description: IPV6 AIM address
-      ipaddress-v6-oam:
-        type: string
-        description: IPV6 OAM address
-      inv-status:
-        type: string
-        description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
-      pserver-id:
-        type: string
-        description: ID of Pserver
-      internet-topology:
-        type: string
-        description: internet topology of Pserver
-      in-maint:
-        type: boolean
-      resource-version:
+        description: Alphabetical concatenation of lag-interface names
+      resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      pserver-name2:
-        type: string
-        description: alternative pserver name
-      purpose:
-        type: string
-        description: purpose of pserver
-      prov-status:
-        type: string
-        description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV]
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-      p-interfaces:
-        type: array
-        items:
-          $ref: "#/definitions/p-interface"
-      lag-interfaces:
-        type: array
-        items:
-          $ref: "#/definitions/lag-interface"
-  pservers:
+  lag-links:
     description: |
-      Collection of compute hosts.
+      Collection of link aggregation connections
     properties:
-      pserver:
+      lag-link:
         type: array
         items:          
-          $ref: "#/definitions/pserver"
-  virtual-data-center:
+          $ref: "#/definitions/lag-link"
+  license:
     description: |
-      Virtual organization of cloud infrastructure elements in a data center context
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      Metadata for license group.
       ###### Related Nodes
-      - TO generic-vnf (Many2Many)
-      - TO logical-link (Many2Many)
-      - FROM connector
+      - TO generic-vnf( license BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO vce( license BelongsTo vce, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this LICENSE is DELETED also
     required:
-    - vdc-id
-    - vdc-name
+    - group-uuid
+    - resource-uuid
     properties:
-      vdc-id:
+      group-uuid:
         type: string
-        description: Unique ID of the vdc
-      vdc-name:
+        description: Unique ID for the license group the resource belongs to, should be uuid.
+      resource-uuid:
         type: string
-        description: Name of the virtual data center
+        description: Unique ID of a license resource. 
       resource-version:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+        description: Concurrency value
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  virtual-data-centers:
+  licenses:
     description: |
-      Virtual organization of cloud infrastructure elements in a data center context
+      Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
     properties:
-      virtual-data-center:
+      license:
         type: array
         items:          
-          $ref: "#/definitions/virtual-data-center"
-  cloud-infrastructure:
+          $ref: "#/definitions/license"
+  line-of-business:
     description: |
-      Namespace for cloud infrastructure.
+      describes a line-of-business
+      ###### Related Nodes
+      - TO generic-vnf( line-of-business Uses generic-vnf, MANY2MANY)
+
+    required:
+    - line-of-business-name
     properties:
-      complexes:
-        type: array
-        items:
-          $ref: "#/definitions/complex"
-      cloud-regions:
-        type: array
-        items:
-          $ref: "#/definitions/cloud-region"
-      network-profiles:
-        type: array
-        items:
-          $ref: "#/definitions/network-profile"
-      pservers:
+      line-of-business-name:
+        type: string
+        description: Name of the line-of-business (product)
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
         type: array
         items:
-          $ref: "#/definitions/pserver"
-      virtual-data-centers:
+          $ref: "#/definitions/relationship"
+  lines-of-business:
+    description: |
+      Collection of lines-of-business
+    properties:
+      line-of-business:
         type: array
-        items:
-          $ref: "#/definitions/virtual-data-center"
-  connector:
+        items:          
+          $ref: "#/definitions/line-of-business"
+  logical-link:
     description: |
-      Collection of resource instances used to connect a variety of disparate inventory widgets
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      Logical links generally connect l-interfaces but are used to express logical connectivity between two points
       ###### Related Nodes
-      - TO virtual-data-center (Many2Many)
-      - TO metadatum (comprises connector, Many2Many)
-      - FROM service-instance
+      - TO cloud-region( logical-link LocatedIn cloud-region, MANY2MANY)
+      - TO generic-vnf( logical-link BridgedTo generic-vnf, MANY2MANY)
+      - TO lag-link( logical-link Uses lag-link, MANY2MANY)
+      - TO logical-link( logical-link Uses logical-link, MANY2MANY)
+      - TO pnf( logical-link BridgedTo pnf, MANY2MANY)
+      - TO pserver( logical-link BridgedTo pserver, MANY2MANY)
+      - TO vpn-binding( logical-link Uses vpn-binding, MANY2MANY)
+      - TO virtual-data-center( logical-link LocatedIn virtual-data-center, MANY2MANY)
+      - FROM lag-interface( lag-interface Uses logical-link, MANY2MANY)(3)
+      - FROM l-interface( l-interface LinksTo logical-link, MANY2MANY)(3)
+      - FROM p-interface( p-interface LinksTo logical-link, MANY2ONE)
+      - FROM service-instance( service-instance Uses logical-link, ONE2MANY)(3)
+      - FROM vlan( vlan Uses logical-link, MANY2MANY)(3)
+      - FROM logical-link( logical-link Uses logical-link, MANY2MANY)
+
+      -(3) IF this FROM node is deleted, this LOGICAL-LINK is DELETED also
     required:
-    - resource-instance-id
+    - link-name
+    - link-type
     properties:
-      resource-instance-id:
+      link-name:
         type: string
-        description: Unique id of resource instance.
+        description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+      link-type:
+        type: string
+        description: Type of logical link, e.g., evc
+      speed-value:
+        type: string
+        description: Captures the numeric part of the speed
+      speed-units:
+        type: string
+        description: Captures the units corresponding to the speed
+      ip-version:
+        type: string
+        description: v4, v6, or ds for dual stack
+      routing-protocol:
+        type: string
+        description: For example, static or BGP
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
@@ -39349,344 +43691,482 @@ definitions:
       widget-model-version:
         type: string
         description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+      operational-status:
+        type: string
+        description: Indication of operational status of the logical link.
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+      link-role:
+        type: string
+        description: Indication of the network use of the logical link.
+      link-name2:
+        type: string
+        description: Alias or alternate name (CLCI or D1 name).
+      link-id:
+        type: string
+        description: UUID of the logical-link, SDNC generates this.
+      circuit-id:
+        type: string
+        description: Circuit id
+      purpose:
+        type: string
+        description: Reason for this entity, role it is playing
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-      metadata:
+  logical-links:
+    description: |
+      Collection of logical connections
+    properties:
+      logical-link:
         type: array
-        items:
-          $ref: "#/definitions/metadatum"
-  connectors:
+        items:          
+          $ref: "#/definitions/logical-link"
+  metadata:
     description: |
-      Collection of resource instances used to connect a variety of disparate inventory widgets
+      Collection of metadatum (key/value pairs)
     properties:
-      connector:
+      metadatum:
         type: array
         items:          
-          $ref: "#/definitions/connector"
-  tunnel-xconnect:
+          $ref: "#/definitions/metadatum"
+  metadatum:
     description: |
-      Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      Key/value pairs
       ###### Related Nodes
-      - FROM allotted-resource (is composed of tunnel-xconnect)
+      - TO connector( metadatum BelongsTo connector, MANY2ONE)(4)
+      - TO image( metadatum BelongsTo image, MANY2ONE)(4)
+      - TO service-instance( metadatum BelongsTo service-instance, MANY2ONE)(4)
+      - TO model-ver( metadatum BelongsTo model-ver, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this METADATUM is DELETED also
     required:
-    - id
-    - bandwidth-up-wan1
-    - bandwidth-down-wan1
-    - bandwidth-up-wan2
-    - bandwidth-down-wan2
+    - metaname
+    - metaval
     properties:
-      id:
+      metaname:
         type: string
-        description: Allotted Resource id UUID assigned to this instance.
-      bandwidth-up-wan1:
+      metaval:
         type: string
-        description: The WAN uplink bandwidth for WAN1
-      bandwidth-down-wan1:
+      resource-version:
         type: string
-        description: The WAN downlink bandwidth for WAN1
-      bandwidth-up-wan2:
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+  model:
+    description: |
+      Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
+      ###### Related Nodes
+      - TO model( model-ver BelongsTo model, MANY2ONE)(1)
+      - FROM instance-group( instance-group Targets model, MANY2MANY)
+      - FROM model-ver( model-ver BelongsTo model, MANY2ONE)(1)
+      - FROM named-query( named-query AppliesTo model, ONE2MANY)
+      - FROM named-query-element( named-query-element IsA model, MANY2ONE)
+
+      -(1) IF this MODEL node is deleted, this FROM node is DELETED also
+      -MODEL cannot be deleted if related to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT
+
+    required:
+    - model-invariant-id
+    - model-type
+    properties:
+      model-invariant-id:
         type: string
-        description: The WAN uplink bandwidth for WAN2
-      bandwidth-down-wan2:
+        description: Unique identifier corresponding to the main definition of a model in ASDC
+      model-type:
         type: string
-        description: The WAN downlink bandwidth for WAN2
+        description: Type of the model, e.g., service, resource, widget, etc.
       resource-version:
         type: string
-        description: Concurrency value
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      model-vers:
+        type: array
+        items:
+          $ref: "#/definitions/model-ver"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  tunnel-xconnects:
+  model-and-named-query-search:
     description: |
-      This object is used to store the specific tunnel cross connect aspects of an allotted resource
+      ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
     properties:
-      tunnel-xconnect:
-        type: array
-        items:          
-          $ref: "#/definitions/tunnel-xconnect"
-  allotted-resource:
+      query-parameters:
+        type: object
+        $ref: "#/definitions/query-parameters"
+      instance-filters:
+        type: object
+        $ref: "#/definitions/instance-filters"
+      secondary-filts:
+        type: object
+        $ref: "#/definitions/secondary-filts"
+      top-node-type:
+        type: string
+      secondary-filter-cut-point:
+        type: string
+  model-constraint:
     description: |
-      Represents a slice or partial piece of a resource that gets separately allotted
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO generic-vnf (Many2Many)
-      - TO l3-network (Many2Many)
-      - TO instance-group (Many2Many)
-      - TO network-policy (One2One)
-      - TO vlan (Many2Many)
-      - TO tunnel-xconnect (comprises allotted-resource, One2One)
-      - FROM service-instance (is composed of allotted-resource)
-      - FROM service-instance
+      This is how we would capture constraints defining allowed sets of elements.
+      ###### Related Nodes
+      - TO model-element( model-constraint BelongsTo model-element, MANY2ONE)(4)
+      - FROM constrained-element-set( constrained-element-set BelongsTo model-constraint, MANY2ONE)(1)
+
+      -(1) IF this MODEL-CONSTRAINT node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this MODEL-CONSTRAINT is DELETED also
     required:
-    - id
+    - model-constraint-uuid
+    - constrained-element-set-uuid-to-replace
     properties:
-      id:
-        type: string
-        description: Allotted Resource id UUID assigned to this instance.
-      description:
-        type: string
-        description: The descriptive information assigned to this allotted resource instance
-      selflink:
-        type: string
-        description: Link back to more information in the controller
-      model-invariant-id:
-        type: string
-        description: the ASDC model id for this resource or service model.
-      model-version-id:
+      model-constraint-uuid:
         type: string
-        description: the ASDC model version for this resource or service model.
-      persona-model-version:
+      constrained-element-set-uuid-to-replace:
         type: string
-        description: the ASDC model version for this resource or service model.
+      constrained-element-sets:
+        type: array
+        items:
+          $ref: "#/definitions/constrained-element-set"
       resource-version:
         type: string
-        description: Concurrency value
-      orchestration-status:
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+  model-constraints:
+    properties:
+      model-constraint:
+        type: array
+        items:          
+          $ref: "#/definitions/model-constraint"
+  model-element:
+    description: |
+      Defines how other models combine to make up a higher-level model.
+      ###### Related Nodes
+      - TO element-choice-set( model-element BelongsTo element-choice-set, MANY2ONE)(4)
+      - TO model-element( model-element BelongsTo model-element, MANY2ONE)(4)
+      - TO model-ver( model-element IsA model-ver, MANY2ONE)
+      - TO model-ver( model-element BelongsTo model-ver, MANY2ONE)(4)
+      - FROM constrained-element-set( constrained-element-set BelongsTo model-element, MANY2ONE)(1)
+      - FROM model-constraint( model-constraint BelongsTo model-element, MANY2ONE)(1)
+      - FROM model-element( model-element BelongsTo model-element, MANY2ONE)(4)
+
+      -(1) IF this MODEL-ELEMENT node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this MODEL-ELEMENT is DELETED also
+    required:
+    - model-element-uuid
+    - new-data-del-flag
+    - cardinality
+    properties:
+      model-element-uuid:
         type: string
-        description: Orchestration status
-      operational-status:
+      new-data-del-flag:
         type: string
-        description: Indicator for whether the resource is considered operational
-      type:
+        description: Indicates whether this element was created as part of instantiation from this model
+      cardinality:
         type: string
-        description: Generic description of the type of allotted resource.
-      role:
+        description: How many of this type of element are required/allowed
+      linkage-points:
         type: string
-        description: role in the network that this resource will be providing.
-      tunnel-xconnects:
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      model-elements:
         type: array
         items:
-          $ref: "#/definitions/tunnel-xconnect"
+          $ref: "#/definitions/model-element"
+        description: Defines how other models combine to make up a higher-level model
+      model-constraints:
+        type: array
+        items:
+          $ref: "#/definitions/model-constraint"
+        description: Describes new constraints on this model element that are not part of that model's definition
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  allotted-resources:
-    description: |
-      This object is used to store slices of services being offered
+  model-elements:
     properties:
-      allotted-resource:
+      model-element:
         type: array
         items:          
-          $ref: "#/definitions/allotted-resource"
-  service-instance:
+          $ref: "#/definitions/model-element"
+  model-ver:
     description: |
-      Instance of a service
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO cvlan-tag (Many2Many)
-      - TO pnf (One2Many)
-      - TO connector (Many2Many)
-      - TO metadatum (comprises service-instance, Many2Many)
-      - TO logical-link (Many2Many)
-      - TO vlan (One2Many)
-      - TO service-instance (One2Many)
-      - TO ctag-assignment (One2Many)
-      - TO instance-group (Many2Many)
-      - TO allotted-resource (comprises service-instance, Many2Many)
-      - TO allotted-resource (Many2Many)
-      - FROM generic-vnf
-      - FROM l3-network
-      - FROM service-subscription (is composed of service-instance)
-      - FROM vce
-      - FROM service-instance
+      Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+      ###### Related Nodes
+      - TO model( model-ver BelongsTo model, MANY2ONE)(4)
+      - FROM model-element( model-element IsA model-ver, MANY2ONE)
+      - FROM model-element( model-element BelongsTo model-ver, MANY2ONE)(1)
+      - FROM metadatum( metadatum BelongsTo model-ver, MANY2ONE)(1)
+
+      -(1) IF this MODEL-VER node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this MODEL-VER is DELETED also
+      -MODEL-VER cannot be deleted if related to MODEL-ELEMENT
+
     required:
-    - service-instance-id
+    - model-version-id
+    - model-name
+    - model-version
     properties:
-      service-instance-id:
-        type: string
-        description: Uniquely identifies this instance of a service
-      service-instance-name:
-        type: string
-        description: This field will store a name assigned to the service-instance.
-      model-invariant-id:
-        type: string
-        description: the ASDC model id for this resource or service model.
       model-version-id:
         type: string
-        description: the ASDC model version for this resource or service model.
-      persona-model-version:
-        type: string
-        description: the ASDC model version for this resource or service model.
-      widget-model-id:
-        type: string
-        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-      widget-model-version:
-        type: string
-        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-      bandwidth-total:
-        type: string
-        description: Indicates the total bandwidth to be used for this service.
-      bandwidth-up-wan1:
-        type: string
-        description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device.
-      bandwidth-down-wan1:
-        type: string
-        description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device.
-      bandwidth-up-wan2:
-        type: string
-        description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device.
-      bandwidth-down-wan2:
+        description: Unique identifier corresponding to one version of a model in ASDC
+      model-name:
         type: string
-        description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device.
-      vhn-portal-url:
+        description: Name of the model, which can change from version to version.
+      model-version:
         type: string
-        description: URL customers will use to access the vHN Portal.
-      service-instance-location-id:
+        description: Version
+      model-description:
         type: string
-        description: An identifier that customers assign to the location where this service is being used.
+        description: Description
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      selflink:
-        type: string
-        description: Path to the controller object.
-      orchestration-status:
-        type: string
-        description: Orchestration status of this service.
-      relationship-list:
+      model-elements:
         type: array
         items:
-          $ref: "#/definitions/relationship"
+          $ref: "#/definitions/model-element"
       metadata:
         type: array
         items:
           $ref: "#/definitions/metadatum"
-      allotted-resources:
+      relationship-list:
         type: array
         items:
-          $ref: "#/definitions/allotted-resource"
-  service-instances:
+          $ref: "#/definitions/relationship"
+  model-vers:
+    properties:
+      model-ver:
+        type: array
+        items:          
+          $ref: "#/definitions/model-ver"
+  models:
     description: |
-      Collection of service instances
+      Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
     properties:
-      service-instance:
+      model:
         type: array
         items:          
-          $ref: "#/definitions/service-instance"
-  service-subscription:
+          $ref: "#/definitions/model"
+  multicast-configuration:
     description: |
-      Object that group service instances.
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
       ###### Related Nodes
-      - TO service-instance (comprises service-subscription, Many2Many)
-      - FROM customer (is composed of service-subscription)
-      - FROM tenant
+      - FROM vlan( vlan Uses multicast-configuration, MANY2MANY)
+
     required:
-    - service-type
+    - multicast-configuration-id
+    - multicast-protocol
+    - rp-type
     properties:
-      service-type:
+      multicast-configuration-id:
         type: string
-        description: Value defined by orchestration to identify this service across ECOMP.
-      temp-ub-sub-account-id:
+        description: Unique id of multicast configuration.
+      multicast-protocol:
         type: string
-        description: This property will be deleted from A&AI in the near future. Only stop gap solution.
+        description: protocol of multicast configuration
+      rp-type:
+        type: string
+        description: rp type of multicast configuration
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      service-instances:
-        type: array
-        items:
-          $ref: "#/definitions/service-instance"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  service-subscriptions:
+  multicast-configurations:
     description: |
-      Collection of objects that group service instances.
+      multicast configuration of generic-vnf ip-address
     properties:
-      service-subscription:
+      multicast-configuration:
         type: array
         items:          
-          $ref: "#/definitions/service-subscription"
-  customer:
+          $ref: "#/definitions/multicast-configuration"
+  named-queries:
+    properties:
+      named-query:
+        type: array
+        items:          
+          $ref: "#/definitions/named-query"
+  named-query:
     description: |
-      customer identifiers to provide linkage back to BSS information.
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      TBD
       ###### Related Nodes
-      - TO service-subscription (comprises customer, Many2Many)
+      - TO named-query( named-query-element BelongsTo named-query, ONE2ONE)(1)
+      - TO model( named-query AppliesTo model, ONE2MANY)
+      - FROM named-query-element( named-query-element BelongsTo named-query, ONE2ONE)(1)
+
+      -(1) IF this NAMED-QUERY node is deleted, this FROM node is DELETED also
     required:
-    - global-customer-id
-    - subscriber-name
-    - subscriber-type
+    - named-query-uuid
+    - named-query-name
+    - named-query-version
     properties:
-      global-customer-id:
+      named-query-uuid:
         type: string
-        description: Global customer id used across ECOMP to uniquely identify customer.
-      subscriber-name:
+      named-query-name:
         type: string
-        description: Subscriber name, an alternate way to retrieve a customer.
-      subscriber-type:
+      named-query-version:
+        type: string
+      required-input-param:
+        type: string
+      description:
         type: string
-        description: Subscriber type, a way to provide VID with only the INFRA customers.
       resource-version:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      service-subscriptions:
+      named-query-elements:
         type: array
         items:
-          $ref: "#/definitions/service-subscription"
+          $ref: "#/definitions/named-query-element"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  customers:
+  named-query-element:
     description: |
-      Collection of customer identifiers to provide linkage back to BSS information.
+      TBD
+      ###### Related Nodes
+      - TO named-query( named-query-element BelongsTo named-query, ONE2ONE)(4)
+      - TO model( named-query-element IsA model, MANY2ONE)
+      - TO named-query-element( named-query-element BelongsTo named-query-element, MANY2ONE)(4)
+      - FROM property-constraint( property-constraint BelongsTo named-query-element, MANY2ONE)(1)
+      - FROM related-lookup( related-lookup BelongsTo named-query-element, MANY2ONE)(1)
+      - FROM named-query-element( named-query-element BelongsTo named-query-element, MANY2ONE)(4)
+
+      -(1) IF this NAMED-QUERY-ELEMENT node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this NAMED-QUERY-ELEMENT is DELETED also
+    required:
+    - named-query-element-uuid
     properties:
-      customer:
-        type: array
-        items:          
-          $ref: "#/definitions/customer"
-  business:
-    description: |
-      Namespace for business related constructs
+      named-query-element-uuid:
+        type: string
+      property-collect-list:
+        type: string
+      resource-version:
+        type: string
+      property-limit-desc:
+        type: string
+      do-not-output:
+        type: string
+      named-query-elements:
+        type: array
+        items:
+          $ref: "#/definitions/named-query-element"
+      related-lookups:
+        type: array
+        items:
+          $ref: "#/definitions/related-lookup"
+      property-constraints:
+        type: array
+        items:
+          $ref: "#/definitions/property-constraint"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+  named-query-elements:
     properties:
-      connectors:
+      named-query-element:
+        type: array
+        items:          
+          $ref: "#/definitions/named-query-element"
+  network:
+    description: |
+      Namespace for network inventory resources.
+    properties:
+      logical-links:
         type: array
         items:
-          $ref: "#/definitions/connector"
-      customers:
+          $ref: "#/definitions/logical-link"
+      site-pair-sets:
         type: array
         items:
-          $ref: "#/definitions/customer"
-  vnf-image:
+          $ref: "#/definitions/site-pair-set"
+      vpn-bindings:
+        type: array
+        items:
+          $ref: "#/definitions/vpn-binding"
+      vpls-pes:
+        type: array
+        items:
+          $ref: "#/definitions/vpls-pe"
+      multicast-configurations:
+        type: array
+        items:
+          $ref: "#/definitions/multicast-configuration"
+      vces:
+        type: array
+        items:
+          $ref: "#/definitions/vce"
+      vnfcs:
+        type: array
+        items:
+          $ref: "#/definitions/vnfc"
+      l3-networks:
+        type: array
+        items:
+          $ref: "#/definitions/l3-network"
+      network-policies:
+        type: array
+        items:
+          $ref: "#/definitions/network-policy"
+      generic-vnfs:
+        type: array
+        items:
+          $ref: "#/definitions/generic-vnf"
+      lag-links:
+        type: array
+        items:
+          $ref: "#/definitions/lag-link"
+      newvces:
+        type: array
+        items:
+          $ref: "#/definitions/newvce"
+      pnfs:
+        type: array
+        items:
+          $ref: "#/definitions/pnf"
+      physical-links:
+        type: array
+        items:
+          $ref: "#/definitions/physical-link"
+      ipsec-configurations:
+        type: array
+        items:
+          $ref: "#/definitions/ipsec-configuration"
+      route-table-references:
+        type: array
+        items:
+          $ref: "#/definitions/route-table-reference"
+      instance-groups:
+        type: array
+        items:
+          $ref: "#/definitions/instance-group"
+      zones:
+        type: array
+        items:
+          $ref: "#/definitions/zone"
+  network-policies:
+    properties:
+      network-policy:
+        type: array
+        items:          
+          $ref: "#/definitions/network-policy"
+  network-policy:
     description: |
-      Image object that pertain to a VNF that doesn't have associated vservers.  This is a kludge.
-      ###### Default Delete Scope
-      ERROR_IF_ANY_IN_EDGES
       ###### Related Nodes
-      - FROM generic-vnf
+      - FROM allotted-resource( allotted-resource Uses network-policy, ONE2ONE)
+      - FROM l3-network( l3-network Uses network-policy, MANY2MANY)
+
     required:
-    - vnf-image-uuid
-    - application
-    - application-vendor
+    - network-policy-id
     properties:
-      vnf-image-uuid:
-        type: string
-        description: Unique ID of this asset
-      application:
-        type: string
-        description: The application that the image instantiates.
-      application-vendor:
+      network-policy-id:
         type: string
-        description: The vendor of the application.
-      application-version:
+        description: UUID representing unique key to this instance
+      network-policy-fqdn:
         type: string
-        description: The version of the application.
-      selflink:
+        description: Contrail FQDN for the policy
+      heat-stack-id:
         type: string
-        description: URL to endpoint where AAI can get more details
+        description: ID for the openStack Heat instance
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
@@ -39694,254 +44174,282 @@ definitions:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  vnf-images:
-    description: |
-      Collection of image objects that pertain to a VNF that doesn't have associated vservers.  This is a kludge.
-    properties:
-      vnf-image:
-        type: array
-        items:          
-          $ref: "#/definitions/vnf-image"
-  service:
+  network-profile:
     description: |
-      Stand-in for service model definitions.  Likely to be deprecated in favor of models from ASDC.  Does not strictly map to ASDC services.
-      ###### Default Delete Scope
-      ERROR_IF_ANY_IN_EDGES
+      Network profile populated by SDN-GP for SNMP
+      ###### Related Nodes
+      - TO generic-vnf( network-profile AppliesTo generic-vnf, MANY2MANY)
+
     required:
-    - service-id
-    - service-description
+    - nm-profile-name
     properties:
-      service-id:
-        type: string
-        description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
-      service-description:
+      nm-profile-name:
         type: string
-        description: Description of the service
-      service-selflink:
+        description: Unique name of network profile.
+      community-string:
         type: string
-        description: URL to endpoint where AAI can get more details
+        description: Encrypted SNMP community string
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      service-version:
-        type: string
-        description: service version
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  services:
+  network-profiles:
     description: |
-      Collection of service model definitions.  Likely to be deprecated in favor of models from ASDC.
+      Collection of network profiles
     properties:
-      service:
+      network-profile:
         type: array
         items:          
-          $ref: "#/definitions/service"
-  service-capability:
+          $ref: "#/definitions/network-profile"
+  newvce:
     description: |
-      Early definition of server/resource pairings, likely to be replaced by models.  No new use should be made of this.
-      ###### Default Delete Scope
-      ERROR_IF_ANY_IN_EDGES
+      This object fills in the gaps from vce that were incorporated into generic-vnf.  This object will be retired with vce.
       ###### Related Nodes
-      - FROM availability-zone
-      - FROM oam-network
+      - FROM l-interface( l-interface BelongsTo newvce, MANY2ONE)(1)
+
+      -(1) IF this NEWVCE node is deleted, this FROM node is DELETED also
     required:
-    - service-type
+    - vnf-id2
+    - vnf-name
     - vnf-type
     properties:
-      service-type:
+      vnf-id2:
         type: string
-        description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+        description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+      vnf-name:
+        type: string
+        description: Name of VNF.
+      vnf-name2:
+        type: string
+        description: Alternate name of VNF.
       vnf-type:
         type: string
         description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational
+      license-key:
+        type: string
+        description: OBSOLETE -  do not use
+      ipv4-oam-address:
+        type: string
+        description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+      equipment-role:
+        type: string
+        description: Client should send valid enumerated value.
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      ipv4-loopback0-address:
+        type: string
+        description: v4 Loopback0 address
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, mastered by MSO.
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance, managed by MSO
+      mso-catalog-key:
+        type: string
+        description: Corresponds to the SDN-C catalog id used to configure this VCE
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  service-capabilities:
+      l-interfaces:
+        type: array
+        items:
+          $ref: "#/definitions/l-interface"
+  newvces:
     description: |
-      Collection of service capabilities.
+      This object fills in the gaps from vce that were incorporated into generic-vnf.  This object will be retired with vce.
     properties:
-      service-capability:
+      newvce:
         type: array
         items:          
-          $ref: "#/definitions/service-capability"
-  element-choice-set:
-    description: |
-      This is how we would capture constraints defining allowed sets of elements.
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO model-element (comprises element-choice-set, One2Many)
-      - FROM constrained-element-set (is composed of element-choice-set)
-    required:
-    - element-choice-set-uuid
-    - element-choice-set-name
+          $ref: "#/definitions/newvce"
+  nodes:
     properties:
-      element-choice-set-uuid:
+      inventory-item-data:
+        type: array
+        items:
+          $ref: "#/definitions/inventory-item-data"
+  notification-event:
+    properties:
+      cambria.partition:
         type: string
-      element-choice-set-name:
+      notification-event-header:
+        type: object
+        $ref: "#/definitions/notification-event-header"
+  notification-event-header:
+    properties:
+      id:
         type: string
-      cardinality:
+      timestamp:
         type: string
-      resource-version:
+      source-name:
         type: string
-      model-elements:
-        type: array
-        items:
-          $ref: "#/definitions/model-element"
-      relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-  element-choice-sets:
+      domain:
+        type: string
+      sequence-number:
+        type: string
+      severity:
+        type: string
+      event-type:
+        type: string
+      version:
+        type: string
+      action:
+        type: string
+      entity-type:
+        type: string
+      top-entity-type:
+        type: string
+      entity-link:
+        type: string
+      status:
+        type: string
+  notify:
+    required:
+    - event-id
     properties:
-      element-choice-set:
+      event-id:
+        type: string
+      node-type:
+        type: string
+      event-trigger:
+        type: string
+      key-data:
         type: array
         items:          
-          $ref: "#/definitions/element-choice-set"
-  constrained-element-set:
+          $ref: "#/definitions/key-data"
+      selflink:
+        type: string
+  oam-network:
     description: |
-      This is how we would capture constraints defining allowed sets of elements.
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      OAM network, to be deprecated shortly.  Do not use for new purposes. 
       ###### Related Nodes
-      - TO element-choice-set (comprises constrained-element-set, One2Many)
-      - FROM model-element (is composed of constrained-element-set)
-      - FROM model-constraint (is composed of constrained-element-set)
+      - TO cloud-region( oam-network BelongsTo cloud-region, MANY2ONE)
+      - TO complex( oam-network AppliesTo complex, MANY2MANY)
+      - TO service-capability( oam-network AppliesTo service-capability, MANY2MANY)
+
     required:
-    - constrained-element-set-uuid
-    - constraint-type
-    - check-type
+    - network-uuid
+    - network-name
+    - cvlan-tag
     properties:
-      constrained-element-set-uuid:
+      network-uuid:
         type: string
-      constraint-type:
+        description: UUID of the network. Unique across a cloud-region
+      network-name:
         type: string
-      check-type:
+        description: Name of the network.
+      cvlan-tag:
+        type: integer
+        format: int64
+        description: cvlan-id
+      ipv4-oam-gateway-address:
         type: string
+        description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+      ipv4-oam-gateway-address-prefix-length:
+        type: integer
+        format: int32
+        description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
       resource-version:
         type: string
-      element-choice-sets:
-        type: array
-        items:
-          $ref: "#/definitions/element-choice-set"
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  constrained-element-sets:
+  oam-networks:
+    description: |
+      Collection of OAM networks, to be deprecated shortly.  Do not use for new purposes. 
     properties:
-      constrained-element-set:
+      oam-network:
         type: array
         items:          
-          $ref: "#/definitions/constrained-element-set"
-  model-constraint:
+          $ref: "#/definitions/oam-network"
+  operational-environment:
     description: |
-      This is how we would capture constraints defining allowed sets of elements.
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
       ###### Related Nodes
-      - TO constrained-element-set (comprises model-constraint, One2Many)
-      - FROM model-element (is composed of model-constraint)
+      - TO operational-environment( operational-environment Uses operational-environment, ONE2ONE)
+      - FROM operational-environment( operational-environment Uses operational-environment, ONE2ONE)
+
     required:
-    - model-constraint-uuid
-    - constrained-element-set-uuid-to-replace
+    - operational-environment-id
+    - operational-environment-name
+    - operational-environment-type
+    - operational-environment-status
+    - tenant-context
+    - workload-context
     properties:
-      model-constraint-uuid:
+      operational-environment-id:
         type: string
-      constrained-element-set-uuid-to-replace:
-        type: string
-      constrained-element-sets:
-        type: array
-        items:
-          $ref: "#/definitions/constrained-element-set"
-      resource-version:
+        description: UUID of an operational environment
+      operational-environment-name:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-  model-constraints:
-    properties:
-      model-constraint:
-        type: array
-        items:          
-          $ref: "#/definitions/model-constraint"
-  model-element:
-    description: |
-      Defines how other models combine to make up a higher-level model.
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO model-ver (Many2One)
-      - TO model-element (comprises model-element, One2Many)
-      - TO model-constraint (comprises model-element, One2Many)
-      - TO constrained-element-set (comprises model-element, One2Many)
-      - FROM model-ver (is composed of model-element)
-      - FROM element-choice-set (is composed of model-element)
-      - FROM model-element (is composed of model-element)
-    required:
-    - model-element-uuid
-    - new-data-del-flag
-    - cardinality
-    properties:
-      model-element-uuid:
+        description: Operational Environment name
+      operational-environment-type:
         type: string
-      new-data-del-flag:
+        description: Operational Environment Type.
+      operational-environment-status:
         type: string
-        description: Indicates whether this element was created as part of instantiation from this model
-      cardinality:
+        description: Status
+      tenant-context:
         type: string
-        description: How many of this type of element are required/allowed
-      linkage-points:
+        description: Tenant Context.
+      workload-context:
         type: string
+        description: Workload Context.
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      model-elements:
-        type: array
-        items:
-          $ref: "#/definitions/model-element"
-        description: Defines how other models combine to make up a higher-level model
-      model-constraints:
-        type: array
-        items:
-          $ref: "#/definitions/model-constraint"
-        description: Describes new constraints on this model element that are not part of that model's definition
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  model-elements:
+  operational-environments:
+    description: |
+      a logical partition of the cloud which allows to have multiple environments in the production AIC.
     properties:
-      model-element:
+      operational-environment:
         type: array
         items:          
-          $ref: "#/definitions/model-element"
-  model-ver:
+          $ref: "#/definitions/operational-environment"
+  overloaded-model:
     description: |
-      Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
-      ###### Default Delete Scope
-      ERROR_4_IN_EDGES_OR_CASCADE
-      ###### Related Nodes
-      - TO model-element (comprises model-ver, One2Many)
-      - TO metadatum (comprises model-ver, One2Many)
-      - FROM model (is composed of model-ver)
-      - FROM model-element
+      Allows for legacy POST of old-style and new-style models
     required:
-    - model-version-id
+    - model-invariant-id
+    - model-name-version-id
+    - model-type
     - model-name
+    - model-id
     - model-version
     properties:
-      model-version-id:
+      model-invariant-id:
+        type: string
+        description: Unique identifier corresponding to the main definition of a model in ASDC
+      model-name-version-id:
         type: string
         description: Unique identifier corresponding to one version of a model in ASDC
+      model-type:
+        type: string
+        description: Type of the model, e.g., service, resource, widget, etc.
       model-name:
         type: string
         description: Name of the model, which can change from version to version.
+      model-id:
+        type: string
+        description: Invariant unique ID which does not change from version to version
       model-version:
         type: string
         description: Version
@@ -39951,351 +44459,139 @@ definitions:
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      model-elements:
-        type: array
-        items:
-          $ref: "#/definitions/model-element"
-      metadata:
-        type: array
-        items:
-          $ref: "#/definitions/metadatum"
+      model-vers:
+        type: object
+        $ref: "#/definitions/model-vers"
       relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-  model-vers:
+        type: object
+        $ref: "#/definitions/relationship-list"
+  owning-entities:
+    description: |
+      Collection of owning-entities
     properties:
-      model-ver:
+      owning-entity:
         type: array
         items:          
-          $ref: "#/definitions/model-ver"
-  model:
+          $ref: "#/definitions/owning-entity"
+  owning-entity:
     description: |
-      Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
-      ###### Default Delete Scope
-      ERROR_4_IN_EDGES_OR_CASCADE
+      describes an owning-entity
       ###### Related Nodes
-      - TO model-ver (comprises model, One2Many)
-      - FROM named-query
-      - FROM named-query-element
-      - FROM instance-group
+      - FROM service-instance( service-instance BelongsTo owning-entity, MANY2ONE)
+
     required:
-    - model-invariant-id
-    - model-type
+    - owning-entity-id
+    - owning-entity-name
     properties:
-      model-invariant-id:
+      owning-entity-id:
         type: string
-        description: Unique identifier corresponding to the main definition of a model in ASDC
-      model-type:
+        description: UUID of an owning entity
+      owning-entity-name:
         type: string
-        description: Type of the model, e.g., service, resource, widget, etc.
+        description: Owning entity name
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      model-vers:
-        type: array
-        items:
-          $ref: "#/definitions/model-ver"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  models:
-    description: |
-      Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
-    properties:
-      model:
-        type: array
-        items:          
-          $ref: "#/definitions/model"
-  related-lookup:
+  p-interface:
     description: |
-      TBD
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      Physical interface (e.g., nic)
       ###### Related Nodes
-      - FROM named-query-element (is composed of related-lookup)
+      - TO logical-link( p-interface LinksTo logical-link, MANY2ONE)
+      - TO physical-link( p-interface LinksTo physical-link, MANY2ONE)(2)
+      - TO pnf( p-interface BindsTo pnf, MANY2ONE)(4)
+      - TO pserver( p-interface BindsTo pserver, MANY2ONE)(4)
+      - TO vpls-pe( p-interface BindsTo vpls-pe, MANY2ONE)(4)
+      - FROM lag-interface( lag-interface Uses p-interface, MANY2MANY)
+      - FROM l-interface( l-interface BindsTo p-interface, MANY2ONE)(1)
+
+      -(1) IF this P-INTERFACE node is deleted, this FROM node is DELETED also
+      -(2) IF this P-INTERFACE node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this P-INTERFACE is DELETED also
     required:
-    - related-lookup-uuid
-    - source-node-type
-    - source-node-property
-    - target-node-type
-    - target-node-property
+    - interface-name
+    - in-maint
     properties:
-      related-lookup-uuid:
+      interface-name:
         type: string
-      source-node-type:
+        description: Name that identifies the physical interface
+      speed-value:
         type: string
-      source-node-property:
+        description: Captures the numeric part of the speed
+      speed-units:
         type: string
-      target-node-type:
+        description: Captures the units corresponding to the speed
+      port-description:
         type: string
-      target-node-property:
+        description: Nature of the services and connectivity on this port.
+      equipment-identifier:
         type: string
-      property-collect-list:
+        description: CLEI or other specification for p-interface hardware.
+      interface-role:
+        type: string
+        description: Role specification for p-interface hardware.
+      interface-type:
+        type: string
+        description: Indicates the physical properties of the interface.
+      prov-status:
         type: string
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
       resource-version:
         type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true)
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  related-lookups:
+      l-interfaces:
+        type: array
+        items:
+          $ref: "#/definitions/l-interface"
+  p-interfaces:
+    description: |
+      Collection of physical interfaces.
     properties:
-      related-lookup:
+      p-interface:
         type: array
         items:          
-          $ref: "#/definitions/related-lookup"
-  property-constraint:
+          $ref: "#/definitions/p-interface"
+  physical-link:
     description: |
-      TBD
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      Collection of physical connections, typically between p-interfaces
       ###### Related Nodes
-      - FROM named-query-element (is composed of property-constraint)
-    required:
-    - property-constraint-uuid
-    - constraint-type
-    - property-name
-    - property-value
-    properties:
-      property-constraint-uuid:
-        type: string
-      constraint-type:
-        type: string
-      property-name:
-        type: string
-      property-value:
-        type: string
-      resource-version:
-        type: string
-  property-constraints:
-    properties:
-      property-constraint:
-        type: array
-        items:          
-          $ref: "#/definitions/property-constraint"
-  named-query-element:
-    description: |
-      TBD
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO named-query-element (comprises named-query-element, Many2Many)
-      - TO model (Many2One)
-      - TO property-constraint (comprises named-query-element, One2Many)
-      - TO related-lookup (comprises named-query-element, One2Many)
-      - FROM named-query (is composed of named-query-element)
-      - FROM named-query-element (is composed of named-query-element)
-    required:
-    - named-query-element-uuid
-    properties:
-      named-query-element-uuid:
-        type: string
-      property-collect-list:
-        type: string
-      resource-version:
-        type: string
-      property-limit-desc:
-        type: string
-      do-not-output:
-        type: string
-      named-query-elements:
-        type: array
-        items:
-          $ref: "#/definitions/named-query-element"
-      related-lookups:
-        type: array
-        items:
-          $ref: "#/definitions/related-lookup"
-      property-constraints:
-        type: array
-        items:
-          $ref: "#/definitions/property-constraint"
-      relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-  named-query-elements:
-    properties:
-      named-query-element:
-        type: array
-        items:          
-          $ref: "#/definitions/named-query-element"
-  named-query:
-    description: |
-      TBD
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO model (One2Many)
-      - TO named-query-element (comprises named-query, One2One)
-    required:
-    - named-query-uuid
-    - named-query-name
-    - named-query-version
-    properties:
-      named-query-uuid:
-        type: string
-      named-query-name:
-        type: string
-      named-query-version:
-        type: string
-      required-input-param:
-        type: string
-      description:
-        type: string
-      resource-version:
-        type: string
-      named-query-elements:
-        type: array
-        items:
-          $ref: "#/definitions/named-query-element"
-      relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-  named-queries:
-    properties:
-      named-query:
-        type: array
-        items:          
-          $ref: "#/definitions/named-query"
-  service-design-and-creation:
-    description: |
-      Namespace for objects managed by ASDC
-    properties:
-      vnf-images:
-        type: array
-        items:
-          $ref: "#/definitions/vnf-image"
-      services:
-        type: array
-        items:
-          $ref: "#/definitions/service"
-      service-capabilities:
-        type: array
-        items:
-          $ref: "#/definitions/service-capability"
-      models:
-        type: array
-        items:
-          $ref: "#/definitions/model"
-      named-queries:
-        type: array
-        items:
-          $ref: "#/definitions/named-query"
-  logical-link:
-    description: |
-      Logical links generally connect l-interfaces but are used to express logical connectivity between two points
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
-      ###### Related Nodes
-      - TO lag-link (Many2Many)
-      - TO pnf (Many2Many)
-      - TO logical-link (One2Many)
-      - TO generic-vnf (Many2Many)
-      - TO pserver (Many2Many)
-      - TO cloud-region (Many2Many)
-      - TO vpn-binding (Many2Many)
-      - FROM l-interface
-      - FROM lag-interface
-      - FROM p-interface
-      - FROM service-instance
-      - FROM virtual-data-center
-      - FROM vlan
-      - FROM logical-link
+      - FROM p-interface( p-interface LinksTo physical-link, MANY2ONE)(3)
+
+      -(3) IF this FROM node is deleted, this PHYSICAL-LINK is DELETED also
     required:
     - link-name
-    - link-type
     properties:
       link-name:
         type: string
-        description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
-      link-type:
-        type: string
-        description: Type of logical link, e.g., evc
+        description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
       speed-value:
         type: string
         description: Captures the numeric part of the speed
       speed-units:
         type: string
         description: Captures the units corresponding to the speed
-      ip-version:
-        type: string
-        description: v4, v6, or ds for dual stack
-      routing-protocol:
-        type: string
-        description: For example, static or BGP
-      resource-version:
-        type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      model-invariant-id:
-        type: string
-        description: the ASDC model id for this resource or service model.
-      model-version-id:
-        type: string
-        description: the ASDC model version for this resource or service model.
-      persona-model-version:
-        type: string
-        description: the ASDC model version for this resource or service model.
-      widget-model-id:
-        type: string
-        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-      widget-model-version:
-        type: string
-        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-      operational-status:
-        type: string
-        description: Indication of operational status of the logical link.
-      prov-status:
-        type: string
-        description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-      link-role:
-        type: string
-        description: Indication of the network use of the logical link.
-      link-name2:
-        type: string
-        description: Alias or alternate name (CLCI or D1 name).
-      link-id:
-        type: string
-        description: UUID of the logical-link, SDNC generates this.
       circuit-id:
         type: string
-        description: Circuit id
-      purpose:
-        type: string
-        description: Reason for this entity, role it is playing
-      relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-  logical-links:
-    description: |
-      Collection of logical connections
-    properties:
-      logical-link:
-        type: array
-        items:          
-          $ref: "#/definitions/logical-link"
-  class-of-service:
-    description: |
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
-      ###### Related Nodes
-      - FROM site-pair (is composed of class-of-service)
-    required:
-    - cos
-    properties:
-      cos:
+        description: Circuit it
+      dual-mode:
         type: string
-        description: unique identifier of probe
-      probe-id:
+        description: Dual access mode (e.g., primary, secondary
+      management-option:
         type: string
-        description: identifier of probe
-      probe-type:
+        description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+      service-provider-name:
         type: string
-        description: type of probe
+        description: Name of the service Provider on this link.
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
@@ -40303,238 +44599,124 @@ definitions:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  classes-of-service:
+  physical-links:
     description: |
-      class-of-service of probe
+      Collection of physical connections, typically between p-interfaces
     properties:
-      class-of-service:
+      physical-link:
         type: array
         items:          
-          $ref: "#/definitions/class-of-service"
-  site-pair:
+          $ref: "#/definitions/physical-link"
+  platform:
     description: |
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      describes a platform
       ###### Related Nodes
-      - TO class-of-service (comprises site-pair, Many2Many)
-      - FROM routing-instance (is composed of site-pair)
+      - TO generic-vnf( platform Uses generic-vnf, MANY2MANY)
+
     required:
-    - site-pair-id
+    - platform-name
     properties:
-      site-pair-id:
-        type: string
-        description: unique identifier of probe
-      source-ip:
-        type: string
-        description: Prefix address
-      destination-ip:
-        type: string
-        description: Prefix address
-      ip-version:
-        type: string
-        description: ip version, v4, v6
-      destination-hostname:
+      platform-name:
         type: string
-        description: Hostname of the destination equipment to which SLAs are measured against.
-      destination-equip-type:
-        type: string
-        description: The type of destinatination equipment. Could be Router, etc.
+        description: Name of the platform
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      classes-of-service:
-        type: array
-        items:
-          $ref: "#/definitions/class-of-service"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  site-pairs:
+  platforms:
     description: |
-      probe within a set
+      Collection of platforms
     properties:
-      site-pair:
+      platform:
         type: array
         items:          
-          $ref: "#/definitions/site-pair"
-  routing-instance:
+          $ref: "#/definitions/platform"
+  pnf:
     description: |
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      PNF represents a physical network function. typically equipment used in the D1 world.
       ###### Related Nodes
-      - TO site-pair (comprises routing-instance, Many2Many)
-      - FROM site-pair-set (is composed of routing-instance)
+      - TO complex( pnf LocatedIn complex, MANY2ONE)
+      - TO instance-group( pnf MemberOf instance-group, MANY2MANY)
+      - TO zone( pnf LocatedIn zone, MANY2ONE)
+      - FROM logical-link( logical-link BridgedTo pnf, MANY2MANY)
+      - FROM lag-interface( lag-interface BindsTo pnf, MANY2ONE)(1)
+      - FROM p-interface( p-interface BindsTo pnf, MANY2ONE)(1)
+      - FROM service-instance( service-instance ComposedOf pnf, ONE2MANY)
+
+      -(1) IF this PNF node is deleted, this FROM node is DELETED also
     required:
-    - routing-instance-id
+    - pnf-name
+    - in-maint
     properties:
-      routing-instance-id:
+      pnf-name:
         type: string
-        description: Unique id of routing instance
-      rpm-owner:
+        description: unique name of Physical Network Function.
+      pnf-name2:
         type: string
-        description: rpm owner
-      resource-version:
+        description: name of Physical Network Function.
+      pnf-name2-source:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      site-pairs:
-        type: array
-        items:
-          $ref: "#/definitions/site-pair"
-      relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-  routing-instances:
-    description: |
-      set of probes related to generic-vnf routing instance
-    properties:
-      routing-instance:
-        type: array
-        items:          
-          $ref: "#/definitions/routing-instance"
-  site-pair-set:
-    description: |
-      Set of instances for probes used to measure service level agreements
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO routing-instance (comprises site-pair-set, Many2Many)
-      - FROM generic-vnf
-    required:
-    - site-pair-set-id
-    properties:
-      site-pair-set-id:
+        description: source of name2
+      pnf-id:
         type: string
-        description: Unique id of site pair set.
-      resource-version:
+        description: id of pnf
+      equip-type:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      routing-instances:
-        type: array
-        items:
-          $ref: "#/definitions/routing-instance"
-      relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-  site-pair-sets:
-    description: |
-      Collection of sets of instances for probes related to generic-vnf
-    properties:
-      site-pair-set:
-        type: array
-        items:          
-          $ref: "#/definitions/site-pair-set"
-  route-target:
-    description: |
-      Route target information
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - FROM vpn-binding (is composed of route-target)
-    required:
-    - global-route-target
-    - route-target-role
-    properties:
-      global-route-target:
+        description: Equipment type.  Source of truth should define valid values.
+      equip-vendor:
         type: string
-        description: Number used to identify an RT, globally unique in the network
-      route-target-role:
+        description: Equipment vendor.  Source of truth should define valid values.
+      equip-model:
         type: string
-        description: Role assigned to this route target
-      resource-version:
+        description: Equipment model.  Source of truth should define valid values.
+      management-option:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-  route-targets:
-    description: |
-      Collection of route target information
-    properties:
-      route-target:
-        type: array
-        items:          
-          $ref: "#/definitions/route-target"
-  vpn-binding:
-    description: |
-      VPN binding
-      ###### Default Delete Scope
-      ERROR_4_IN_EDGES_OR_CASCADE
-      ###### Related Nodes
-      - TO route-target (comprises vpn-binding, One2Many)
-      - FROM l3-network
-      - FROM logical-link
-    required:
-    - vpn-id
-    - vpn-name
-    properties:
-      vpn-id:
+        description: identifier of managed by company or customer
+      ipaddress-v4-oam:
         type: string
-        description: VPN ID, globally unique within A&AI
-      vpn-name:
+        description: ipv4-oam-address with new naming convention for IP addresses
+      sw-version:
         type: string
-        description: VPN Name
-      vpn-platform:
+        description: sw-version is the version of SW for the hosted application on the PNF.
+      in-maint:
+        type: boolean
+        description: Used to indicate whether or not this object is in maintenance mode (maintenance mode = true). This field (in conjunction with prov-status) is used to suppress alarms and vSCL on VNFs/VMs.
+      frame-id:
         type: string
-        description: the platform associated with the VPN example AVPN, Mobility
-      vpn-type:
+        description: ID of the physical frame (relay rack) where pnf is installed.
+      serial-number:
         type: string
-        description: Type of the vpn, should be taken from enumerated/valid values
-      route-distinguisher:
+        description: Serial number of the device
+      ipaddress-v4-loopback-0:
         type: string
-        description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
-      resource-version:
+        description: IPV4 Loopback 0 address
+      ipaddress-v6-loopback-0:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      route-targets:
-        type: array
-        items:
-          $ref: "#/definitions/route-target"
-      relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-        description: l3-networks relate to vpn-bindings
-  vpn-bindings:
-    properties:
-      vpn-binding:
-        type: array
-        items:          
-          $ref: "#/definitions/vpn-binding"
-  vpls-pe:
-    description: |
-      VPLS Provider Edge routers.
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO complex (Many2Many)
-      - TO ctag-pool (Many2Many)
-      - TO p-interface (comprises vpls-pe, Many2Many)
-      - TO lag-interface (comprises vpls-pe, Many2Many)
-    required:
-    - equipment-name
-    properties:
-      equipment-name:
+        description: IPV6 Loopback 0 address
+      ipaddress-v4-aim:
         type: string
-      prov-status:
+        description: IPV4 AIM address
+      ipaddress-v6-aim:
         type: string
-        description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-      ipv4-oam-address:
+        description: IPV6 AIM address
+      ipaddress-v6-oam:
         type: string
-        description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
-      equipment-role:
+        description: IPV6 OAM address
+      inv-status:
         type: string
-        description: Client should send valid enumerated value, e.g., VPLS-PE.
-      vlan-id-outer:
-        type: integer
-        format: int64
-        description: Temporary location for stag to get to VCE
+        description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      prov-status:
+        type: string
+        description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV]
+      nf-role:
+        type: string
+        description: Nf Role is the role performed by this instance in the network.
       relationship-list:
         type: array
         items:
@@ -40547,78 +44729,23 @@ definitions:
         type: array
         items:
           $ref: "#/definitions/lag-interface"
-  vpls-pes:
-    description: |
-      Collection of VPLS Provider Edge routers
-    properties:
-      vpls-pe:
-        type: array
-        items:          
-          $ref: "#/definitions/vpls-pe"
-  multicast-configuration:
-    description: |
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
-      ###### Related Nodes
-      - FROM vlan
-    required:
-    - multicast-configuration-id
-    - multicast-protocol
-    - rp-type
-    properties:
-      multicast-configuration-id:
-        type: string
-        description: Unique id of multicast configuration.
-      multicast-protocol:
-        type: string
-        description: protocol of multicast configuration
-      rp-type:
-        type: string
-        description: rp type of multicast configuration
-      resource-version:
-        type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-  multicast-configurations:
+  pnfs:
     description: |
-      multicast configuration of generic-vnf ip-address
-    properties:
-      multicast-configuration:
-        type: array
-        items:          
-          $ref: "#/definitions/multicast-configuration"
-  cvlan-tag-entry:
-    required:
-    - cvlan-tag
-    properties:
-      cvlan-tag:
-        type: integer
-        format: int64
-        description: See mis-na-virtualization-platform.yang
-      resource-version:
-        type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-  cvlan-tags:
+      Collection of Physical Network Functions.
     properties:
-      cvlan-tag-entry:
+      pnf:
         type: array
         items:          
-          $ref: "#/definitions/cvlan-tag-entry"
+          $ref: "#/definitions/pnf"
   port-group:
     description: |
       Used to capture the network interfaces of this VCE
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
       ###### Related Nodes
-      - TO cvlan-tag (comprises port-group, Many2Many)
-      - FROM vce (is composed of port-group)
+      - TO vce( port-group BelongsTo vce, MANY2ONE)(4)
+      - FROM cvlan-tag( cvlan-tag BelongsTo port-group, MANY2ONE)(1)
+
+      -(1) IF this PORT-GROUP node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this PORT-GROUP is DELETED also
     required:
     - interface-id
     - orchestration-status
@@ -40670,270 +44797,358 @@ definitions:
         type: array
         items:          
           $ref: "#/definitions/port-group"
-  license:
+  project:
     description: |
-      Metadata for license group.
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      describes the project
       ###### Related Nodes
-      - FROM generic-vnf (is composed of license)
-      - FROM vce (is composed of license)
+      - TO service-instance( project Uses service-instance, ONE2MANY)
+
     required:
-    - group-uuid
-    - resource-uuid
+    - project-name
     properties:
-      group-uuid:
-        type: string
-        description: Unique ID for the license group the resource belongs to, should be uuid.
-      resource-uuid:
+      project-name:
         type: string
-        description: Unique ID of a license resource. 
+        description: Name of the project deploying a service
       resource-version:
         type: string
-        description: Concurrency value
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  licenses:
+  projects:
     description: |
-      Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+      Collection of projects
     properties:
-      license:
+      project:
         type: array
         items:          
-          $ref: "#/definitions/license"
-  entitlement:
+          $ref: "#/definitions/project"
+  properties:
     description: |
-      Metadata for entitlement group.
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
-      ###### Related Nodes
-      - FROM generic-vnf (is composed of entitlement)
-      - FROM vce (is composed of entitlement)
-    required:
-    - group-uuid
-    - resource-uuid
+      Property holder for query properties or instance properties
     properties:
-      group-uuid:
+      property-name:
         type: string
-        description: Unique ID for the entitlement group the resource comes from, should be uuid.
-      resource-uuid:
+      property-value:
         type: string
-        description: Unique ID of an entitlement resource. 
-      resource-version:
-        type: string
-        description: Concurrency value
-      relationship-list:
-        type: array
-        items:
-          $ref: "#/definitions/relationship"
-  entitlements:
+  property-constraint:
     description: |
-      Entitlements, keyed by group-uuid and resource-uuid, related to license management
+      TBD
+      ###### Related Nodes
+      - TO named-query-element( property-constraint BelongsTo named-query-element, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this PROPERTY-CONSTRAINT is DELETED also
+    required:
+    - property-constraint-uuid
+    - constraint-type
+    - property-name
+    - property-value
     properties:
-      entitlement:
+      property-constraint-uuid:
+        type: string
+      constraint-type:
+        type: string
+      property-name:
+        type: string
+      property-value:
+        type: string
+      resource-version:
+        type: string
+  property-constraints:
+    properties:
+      property-constraint:
         type: array
         items:          
-          $ref: "#/definitions/entitlement"
-  vce:
+          $ref: "#/definitions/property-constraint"
+  pserver:
     description: |
-      Virtual Customer Edge Router, used specifically for Gamma.  This object is deprecated.
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
       ###### Related Nodes
-      - TO availability-zone (Many2Many)
-      - TO complex (Many2Many)
-      - TO port-group (comprises vce, Many2Many)
-      - TO vserver (Many2Many)
-      - TO service-instance (Many2Many)
-      - TO entitlement (comprises vce, One2Many)
-      - TO license (comprises vce, One2Many)
+      - TO group-assignment( pserver MemberOf group-assignment, MANY2ONE)
+      - TO availability-zone( pserver MemberOf availability-zone, MANY2ONE)
+      - TO cloud-region( pserver LocatedIn cloud-region, MANY2ONE)
+      - TO complex( pserver LocatedIn complex, MANY2ONE)
+      - TO zone( pserver LocatedIn zone, MANY2ONE)
+      - FROM generic-vnf( generic-vnf HostedOn pserver, MANY2MANY)
+      - FROM logical-link( logical-link BridgedTo pserver, MANY2MANY)
+      - FROM lag-interface( lag-interface BindsTo pserver, MANY2ONE)(1)
+      - FROM p-interface( p-interface BindsTo pserver, MANY2ONE)(1)
+      - FROM vserver( vserver HostedOn pserver, MANY2ONE)
+
+      -(1) IF this PSERVER node is deleted, this FROM node is DELETED also
+      -PSERVER cannot be deleted if related to GENERIC-VNF,LOGICAL-LINK,VSERVER,GROUP-ASSIGNMENT
+
     required:
-    - vnf-id
-    - vnf-name
-    - vnf-type
+    - hostname
+    - in-maint
     properties:
-      vnf-id:
+      hostname:
         type: string
-        description: Unique id of VNF.  This is unique across the graph.
-      vnf-name:
+        description: Value from executing hostname on the compute node.
+      ptnii-equip-name:
         type: string
-        description: Name of VNF.
-      vnf-name2:
+        description: PTNII name
+      number-of-cpus:
+        type: integer
+        format: int32
+        description: Number of cpus
+      disk-in-gigabytes:
+        type: integer
+        format: int32
+        description: Disk size, in GBs
+      ram-in-megabytes:
+        type: integer
+        format: int32
+        description: RAM size, in MBs
+      equip-type:
         type: string
-        description: Alternate name of VNF.
-      vnf-type:
+        description: Equipment type.  Source of truth should define valid values.
+      equip-vendor:
         type: string
-        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-      service-id:
+        description: Equipment vendor.  Source of truth should define valid values.
+      equip-model:
         type: string
-        description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
-      regional-resource-zone:
+        description: Equipment model.  Source of truth should define valid values.
+      fqdn:
         type: string
-        description: Regional way of organizing pservers, source of truth should define values
-      prov-status:
+        description: Fully-qualified domain name
+      pserver-selflink:
         type: string
-        description: Trigger for operational monitoring of this resource by Service Assurance systems.
-      operational-status:
+        description: URL to endpoint where AAI can get more details
+      ipv4-oam-address:
         type: string
-        description: Indicator for whether the resource is considered operational
-      license-key:
+        description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device.
+      serial-number:
         type: string
-        description: OBSOLETE -  do not use
-      equipment-role:
+        description: Serial number, may be queried
+      ipaddress-v4-loopback-0:
         type: string
-        description: Network role being played by this VNF
-      orchestration-status:
+        description: IPV4 Loopback 0 address
+      ipaddress-v6-loopback-0:
         type: string
-        description: Orchestration status of this VNF, mastered by MSO
-      heat-stack-id:
+        description: IPV6 Loopback 0 address
+      ipaddress-v4-aim:
         type: string
-        description: Heat stack id corresponding to this instance, managed by MSO
-      mso-catalog-key:
+        description: IPV4 AIM address
+      ipaddress-v6-aim:
         type: string
-        description: Corresponds to the SDN-C catalog id used to configure this VCE
-      vpe-id:
+        description: IPV6 AIM address
+      ipaddress-v6-oam:
         type: string
-        description: Unique ID of VPE connected to this VCE.
-      v6-vce-wan-address:
+        description: IPV6 OAM address
+      inv-status:
         type: string
-        description: Valid v6 IP address for the WAN Link on this router.  Implied length of /64.
-      ipv4-oam-address:
+        description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+      pserver-id:
         type: string
-        description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+        description: ID of Pserver
+      internet-topology:
+        type: string
+        description: internet topology of Pserver
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true). This field (in conjunction with prov-status) is used to suppress alarms and vSCL on VNFs/VMs.
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      ipv4-loopback0-address:
+      pserver-name2:
         type: string
-        description: Loopback0 address
-      entitlement-resource-uuid:
+        description: alternative pserver name
+      purpose:
         type: string
-        description: OBSOLETE -  see child relationships
-      port-groups:
-        type: array
-        items:
-          $ref: "#/definitions/port-group"
-      licenses:
+        description: purpose of pserver
+      prov-status:
+        type: string
+        description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV]
+      relationship-list:
         type: array
         items:
-          $ref: "#/definitions/license"
-      entitlements:
+          $ref: "#/definitions/relationship"
+      p-interfaces:
         type: array
         items:
-          $ref: "#/definitions/entitlement"
-      relationship-list:
+          $ref: "#/definitions/p-interface"
+      lag-interfaces:
         type: array
         items:
-          $ref: "#/definitions/relationship"
-  vces:
+          $ref: "#/definitions/lag-interface"
+  pservers:
     description: |
-      Collection of Virtual Customer Edge Routers, used specifically for Gamma.  This object is deprecated.
+      Collection of compute hosts.
     properties:
-      vce:
+      pserver:
         type: array
         items:          
-          $ref: "#/definitions/vce"
-  vnfc:
+          $ref: "#/definitions/pserver"
+  query-parameters:
+    description: |
+      QueryParameters for performing a named-query or model query
+    properties:
+      named-query:
+        type: object
+        $ref: "#/definitions/named-query"
+      overloaded-model:
+        type: object
+        $ref: "#/definitions/overloaded-model"
+  related-lookup:
     description: |
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      TBD
       ###### Related Nodes
-      - FROM vserver
-      - FROM vf-module
-      - FROM generic-vnf
+      - TO named-query-element( related-lookup BelongsTo named-query-element, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this RELATED-LOOKUP is DELETED also
     required:
-    - vnfc-name
-    - vnfc-function-code
-    - vnfc-type
-    - in-maint
-    - is-closed-loop-disabled
+    - related-lookup-uuid
+    - source-node-type
+    - source-node-property
+    - target-node-type
+    - target-node-property
     properties:
-      vnfc-name:
-        type: string
-        description: Unique ID of vnfc.
-      vnfc-function-code:
+      related-lookup-uuid:
         type: string
-        description: function code
-      vnfc-type:
+      source-node-type:
         type: string
-        description: type
-      prov-status:
+      source-node-property:
         type: string
-        description: prov status of this vnfc
-      orchestration-status:
+      target-node-type:
         type: string
-        description: Orchestration status of this VNF, mastered by APP-C
-      ipaddress-v4-oam-vip:
+      target-node-property:
         type: string
-        description: Oam V4 vip address of this vnfc
-      in-maint:
-        type: boolean
-      is-closed-loop-disabled:
-        type: boolean
-      group-notation:
+      property-collect-list:
         type: string
-        description: Group notation of VNFC
       resource-version:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  vnfcs:
-    description: |
-      virtual network components associated with a vserver from application controller.
+  related-lookups:
     properties:
-      vnfc:
+      related-lookup:
         type: array
         items:          
-          $ref: "#/definitions/vnfc"
-  subnet:
-    description: |
-      ###### Default Delete Scope
-      ERROR_IF_ANY_IN_EDGES
-      ###### Related Nodes
-      - FROM l3-interface-ipv4-address-list
-      - FROM l3-interface-ipv6-address-list
-      - FROM l3-network (is composed of subnet)
+          $ref: "#/definitions/related-lookup"
+  related-to-property:
+    properties:
+      property-key:
+        type: string
+        description: Key part of a key/value pair
+      property-value:
+        type: string
+        description: Value part of a key/value pair
+  relationship:
+    properties:
+      related-to:
+        type: string
+        description: A keyword provided by A&AI to indicate type of node.
+      related-link:
+        type: string
+        description: URL to the object in A&AI.
+      relationship-data:
+        type: array
+        items:          
+          $ref: "#/definitions/relationship-data"
+  relationship-data:
     required:
-    - subnet-id
-    - dhcp-enabled
+    - relationship-key
+    - relationship-value
     properties:
-      subnet-id:
+      relationship-key:
         type: string
-        description: Subnet ID, should be UUID.
-      subnet-name:
+        description: A keyword provided by A&AI to indicate an attribute.
+      relationship-value:
         type: string
-        description: Name associated with the subnet.
-      neutron-subnet-id:
+        description: Value of the attribute.
+  relationship-list:
+    properties:
+      relationship:
+        type: array
+        items:          
+          $ref: "#/definitions/relationship"
+  reserved-prop-names:
+    description: |
+      Internal map to define some reserved properties of a vertex
+    properties:
+      last-mod-source-of-truth:
         type: string
-        description: Neutron id of this subnet
-      gateway-address:
+      aai-node-type:
         type: string
-        description: gateway ip address
-      network-start-address:
+      aai-created-ts:
+        type: integer
+        format: int64
+      aai-unique-key:
         type: string
-        description: network start address
-      cidr-mask:
+      aai-last-mod-ts:
+        type: integer
+        format: int64
+      source-of-truth:
         type: string
-        description: cidr mask
-      ip-version:
+      aai-uri:
         type: string
-        description: ip version
-      orchestration-status:
+  response-list:
+    description: |
+      Response container for the results of a named-query or model query
+    properties:
+      inventory-response-items:
+        type: object
+        $ref: "#/definitions/inventory-response-items"
+  result-data:
+    properties:
+      resource-type:
         type: string
-        description: Orchestration status of this VNF, mastered by MSO
-      dhcp-enabled:
-        type: boolean
-      dhcp-start:
+        description: The specific type of node in the A&AI graph
+      resource-link:
         type: string
-        description: the start address reserved for use by dhcp
-      dhcp-end:
+        description: The URL to the specific resource
+  route-table-reference:
+    description: |
+      Openstack route table reference.
+      ###### Related Nodes
+      - FROM l3-network( l3-network Uses route-table-reference, MANY2MANY)
+
+    required:
+    - route-table-reference-id
+    - route-table-reference-fqdn
+    properties:
+      route-table-reference-id:
         type: string
-        description: the last address reserved for use by dhcp
+        description: Route Table Reference id, UUID assigned to this instance.
+      route-table-reference-fqdn:
+        type: string
+        description: FQDN entry in the route table.
+      resource-version:
+        type: string
+        description: Concurrency value
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+  route-table-references:
+    description: |
+      Collection of openstack route table references
+    properties:
+      route-table-reference:
+        type: array
+        items:          
+          $ref: "#/definitions/route-table-reference"
+  route-target:
+    description: |
+      Route target information
+      ###### Related Nodes
+      - TO vpn-binding( route-target BelongsTo vpn-binding, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this ROUTE-TARGET is DELETED also
+    required:
+    - global-route-target
+    - route-target-role
+    properties:
+      global-route-target:
+        type: string
+        description: Number used to identify an RT, globally unique in the network
+      route-target-role:
+        type: string
+        description: Role assigned to this route target
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
@@ -40941,46 +45156,105 @@ definitions:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  subnets:
+  route-targets:
+    description: |
+      Collection of route target information
     properties:
-      subnet:
+      route-target:
         type: array
         items:          
-          $ref: "#/definitions/subnet"
-  ctag-assignment:
+          $ref: "#/definitions/route-target"
+  routing-instance:
     description: |
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
       ###### Related Nodes
-      - FROM l3-network (is composed of ctag-assignment)
-      - FROM service-instance
+      - TO site-pair-set( routing-instance BelongsTo site-pair-set, MANY2ONE)(4)
+      - FROM site-pair( site-pair BelongsTo routing-instance, MANY2ONE)(1)
+
+      -(1) IF this ROUTING-INSTANCE node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this ROUTING-INSTANCE is DELETED also
     required:
-    - vlan-id-inner
+    - routing-instance-id
     properties:
-      vlan-id-inner:
-        type: integer
-        format: int64
-        description: id.
+      routing-instance-id:
+        type: string
+        description: Unique id of routing instance
+      rpm-owner:
+        type: string
+        description: rpm owner
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      site-pairs:
+        type: array
+        items:
+          $ref: "#/definitions/site-pair"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  ctag-assignments:
+  routing-instances:
+    description: |
+      set of probes related to generic-vnf routing instance
     properties:
-      ctag-assignment:
+      routing-instance:
         type: array
         items:          
-          $ref: "#/definitions/ctag-assignment"
+          $ref: "#/definitions/routing-instance"
+  sdn-zone-response:
+    properties:
+      oam-networks:
+        type: object
+        $ref: "#/definitions/oam-networks"
+      az-and-dvs-switches:
+        type: array
+        items:          
+          $ref: "#/definitions/az-and-dvs-switches"
+  search:
+    properties:
+      edge-tag-query-result:
+        type: object
+        $ref: "#/definitions/edge-tag-query-result"
+      edge-tag-query-request:
+        type: object
+        $ref: "#/definitions/edge-tag-query-request"
+      search-results:
+        type: object
+        $ref: "#/definitions/search-results"
+      sdn-zone-response:
+        type: object
+        $ref: "#/definitions/sdn-zone-response"
+  search-results:
+    properties:
+      result-data:
+        type: array
+        items:          
+          $ref: "#/definitions/result-data"
+  secondary-filt:
+    description: |
+      SecondaryFilt for performing a named-query or model query
+  secondary-filter:
+    properties:
+      property-name:
+        type: string
+      filter-type:
+        type: string
+      property-value:
+        type: string
+  secondary-filts:
+    description: |
+      SecondaryFilts for performing a named-query or model query
+    properties:
+      secondary-filt:
+        type: array
+        items:          
+          $ref: "#/definitions/secondary-filt"
   segmentation-assignment:
     description: |
       Openstack segmentation assignment.
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
       ###### Related Nodes
-      - FROM l3-network (is composed of segmentation-assignment)
+      - TO l3-network( segmentation-assignment BelongsTo l3-network, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this SEGMENTATION-ASSIGNMENT is DELETED also
     required:
     - segmentation-id
     properties:
@@ -41002,77 +45276,123 @@ definitions:
         type: array
         items:          
           $ref: "#/definitions/segmentation-assignment"
-  l3-network:
+  service:
     description: |
-      Generic network definition
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO vpn-binding (Many2Many)
-      - TO subnet (comprises l3-network, Many2Many)
-      - TO service-instance (Many2Many)
-      - TO ctag-assignment (comprises l3-network, Many2Many)
-      - TO network-policy (Many2Many)
-      - TO segmentation-assignment (comprises l3-network, One2Many)
-      - TO route-table-reference (Many2Many)
-      - FROM cloud-region
-      - FROM complex
-      - FROM generic-vnf
-      - FROM l3-interface-ipv4-address-list
-      - FROM l3-interface-ipv6-address-list
-      - FROM tenant
-      - FROM vf-module
-      - FROM allotted-resource
+      Stand-in for service model definitions.  Likely to be deprecated in favor of models from ASDC.  Does not strictly map to ASDC services.
     required:
-    - network-id
-    - network-name
-    - is-bound-to-vpn
-    - is-provider-network
-    - is-shared-network
-    - is-external-network
+    - service-id
+    - service-description
     properties:
-      network-id:
-        type: string
-        description: Network ID, should be uuid. Unique across A&AI.
-      network-name:
-        type: string
-        description: Name of the network, governed by some naming convention..
-      network-type:
-        type: string
-        description: Type of the network - who defines these values?
-      network-role:
-        type: string
-        description: Role the network plans - who defines these values?
-      network-technology:
+      service-id:
         type: string
-        description: Network technology - who defines these values?
-      neutron-network-id:
+        description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+      service-description:
         type: string
-        description: Neutron network id of this Interface
-      is-bound-to-vpn:
-        type: boolean
-      service-id:
+        description: Description of the service
+      service-selflink:
         type: string
-        description: Unique identifier of service from ASDC.  Does not strictly map to ASDC services.  SOON TO BE DEPRECATED
-      network-role-instance:
-        type: integer
-        format: int64
-        description: network role instance
+        description: URL to endpoint where AAI can get more details
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      orchestration-status:
+      service-version:
         type: string
-        description: Orchestration status of this VNF, mastered by MSO
-      heat-stack-id:
+        description: service version
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+  service-capabilities:
+    description: |
+      Collection of service capabilities.
+    properties:
+      service-capability:
+        type: array
+        items:          
+          $ref: "#/definitions/service-capability"
+  service-capability:
+    description: |
+      Early definition of server/resource pairings, likely to be replaced by models.  No new use should be made of this.
+      ###### Related Nodes
+      - FROM availability-zone( availability-zone AppliesTo service-capability, MANY2MANY)
+      - FROM oam-network( oam-network AppliesTo service-capability, MANY2MANY)
+
+      -SERVICE-CAPABILITY cannot be deleted if related to AVAILABILITY-ZONE,OAM-NETWORK
+
+    required:
+    - service-type
+    - vnf-type
+    properties:
+      service-type:
         type: string
-        description: Heat stack id corresponding to this instance, managed by MSO
-      mso-catalog-key:
+        description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+      vnf-type:
         type: string
-        description: Corresponds to the SDN-C catalog id used to configure this VCE
-      contrail-network-fqdn:
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      resource-version:
         type: string
-        description: Contrail FQDN for the network
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+  service-design-and-creation:
+    description: |
+      Namespace for objects managed by ASDC
+    properties:
+      vnf-images:
+        type: array
+        items:
+          $ref: "#/definitions/vnf-image"
+      services:
+        type: array
+        items:
+          $ref: "#/definitions/service"
+      service-capabilities:
+        type: array
+        items:
+          $ref: "#/definitions/service-capability"
+      models:
+        type: array
+        items:
+          $ref: "#/definitions/model"
+      named-queries:
+        type: array
+        items:
+          $ref: "#/definitions/named-query"
+  service-instance:
+    description: |
+      Instance of a service
+      ###### Related Nodes
+      - TO generic-vnf( service-instance ComposedOf generic-vnf, ONE2MANY)
+      - TO l3-network( service-instance ComposedOf l3-network, ONE2MANY)
+      - TO allotted-resource( service-instance Uses allotted-resource, MANY2MANY)
+      - TO connector( service-instance Uses connector, MANY2MANY)
+      - TO ctag-assignment( service-instance Uses ctag-assignment, ONE2MANY)
+      - TO cvlan-tag( service-instance ComposedOf cvlan-tag, MANY2MANY)
+      - TO instance-group( service-instance MemberOf instance-group, MANY2MANY)
+      - TO logical-link( service-instance Uses logical-link, ONE2MANY)(2)
+      - TO pnf( service-instance ComposedOf pnf, ONE2MANY)
+      - TO service-instance( service-instance ComposedOf service-instance, ONE2MANY)
+      - TO vlan( service-instance ComposedOf vlan, ONE2MANY)
+      - TO service-subscription( service-instance BelongsTo service-subscription, MANY2ONE)(4)
+      - TO vce( service-instance ComposedOf vce, ONE2MANY)
+      - FROM allotted-resource( allotted-resource BelongsTo service-instance, MANY2ONE)(1)
+      - FROM metadatum( metadatum BelongsTo service-instance, MANY2ONE)(1)
+      - FROM service-instance( service-instance ComposedOf service-instance, ONE2MANY)
+
+      -(1) IF this SERVICE-INSTANCE node is deleted, this FROM node is DELETED also
+      -(2) IF this SERVICE-INSTANCE node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this SERVICE-INSTANCE is DELETED also
+    required:
+    - service-instance-id
+    properties:
+      service-instance-id:
+        type: string
+        description: Uniquely identifies this instance of a service
+      service-instance-name:
+        type: string
+        description: This field will store a name assigned to the service-instance.
       model-invariant-id:
         type: string
         description: the ASDC model id for this resource or service model.
@@ -41082,376 +45402,258 @@ definitions:
       persona-model-version:
         type: string
         description: the ASDC model version for this resource or service model.
-      model-customization-id:
-        type: string
-        description: captures the id of all the configuration used to customize the resource for the service.
       widget-model-id:
         type: string
         description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
       widget-model-version:
         type: string
         description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-      physical-network-name:
+      bandwidth-total:
         type: string
-        description: Name associated with the physical network.
-      is-provider-network:
-        type: boolean
-      is-shared-network:
-        type: boolean
-      is-external-network:
-        type: boolean
+        description: Indicates the total bandwidth to be used for this service.
+      bandwidth-up-wan1:
+        type: string
+        description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device.
+      bandwidth-down-wan1:
+        type: string
+        description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device.
+      bandwidth-up-wan2:
+        type: string
+        description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device.
+      bandwidth-down-wan2:
+        type: string
+        description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device.
+      vhn-portal-url:
+        type: string
+        description: URL customers will use to access the vHN Portal.
+      service-instance-location-id:
+        type: string
+        description: An identifier that customers assign to the location where this service is being used.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
       selflink:
         type: string
         description: Path to the controller object.
-      operational-status:
+      orchestration-status:
         type: string
-        description: Indicator for whether the resource is considered operational.
-      subnets:
-        type: array
-        items:
-          $ref: "#/definitions/subnet"
-      ctag-assignments:
+        description: Orchestration status of this service.
+      relationship-list:
         type: array
         items:
-          $ref: "#/definitions/ctag-assignment"
-      segmentation-assignments:
+          $ref: "#/definitions/relationship"
+      metadata:
         type: array
         items:
-          $ref: "#/definitions/segmentation-assignment"
-      relationship-list:
+          $ref: "#/definitions/metadatum"
+      allotted-resources:
         type: array
         items:
-          $ref: "#/definitions/relationship"
-        description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding
-  l3-networks:
+          $ref: "#/definitions/allotted-resource"
+  service-instances:
+    description: |
+      Collection of service instances
     properties:
-      l3-network:
+      service-instance:
         type: array
         items:          
-          $ref: "#/definitions/l3-network"
-  network-policy:
+          $ref: "#/definitions/service-instance"
+  service-subscription:
     description: |
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      Object that group service instances.
       ###### Related Nodes
-      - FROM l3-network
-      - FROM allotted-resource
+      - TO customer( service-subscription BelongsTo customer, MANY2ONE)(4)
+      - TO tenant( service-subscription Uses tenant, MANY2MANY)
+      - FROM service-instance( service-instance BelongsTo service-subscription, MANY2ONE)(1)
+
+      -(1) IF this SERVICE-SUBSCRIPTION node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this SERVICE-SUBSCRIPTION is DELETED also
     required:
-    - network-policy-id
+    - service-type
     properties:
-      network-policy-id:
-        type: string
-        description: UUID representing unique key to this instance
-      network-policy-fqdn:
+      service-type:
         type: string
-        description: Contrail FQDN for the policy
-      heat-stack-id:
+        description: Value defined by orchestration to identify this service across ECOMP.
+      temp-ub-sub-account-id:
         type: string
-        description: ID for the openStack Heat instance
+        description: This property will be deleted from A&AI in the near future. Only stop gap solution.
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      service-instances:
+        type: array
+        items:
+          $ref: "#/definitions/service-instance"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  network-policies:
+  service-subscriptions:
+    description: |
+      Collection of objects that group service instances.
     properties:
-      network-policy:
+      service-subscription:
         type: array
         items:          
-          $ref: "#/definitions/network-policy"
-  vf-module:
+          $ref: "#/definitions/service-subscription"
+  services:
+    description: |
+      Collection of service model definitions.  Likely to be deprecated in favor of models from ASDC.
+    properties:
+      service:
+        type: array
+        items:          
+          $ref: "#/definitions/service"
+  site-pair:
     description: |
-      a deployment unit of VNFCs
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
       ###### Related Nodes
-      - TO volume-group (One2One)
-      - TO l3-network (Many2Many)
-      - TO vnfc (One2Many)
-      - FROM vserver
-      - FROM generic-vnf (is composed of vf-module)
+      - TO routing-instance( site-pair BelongsTo routing-instance, MANY2ONE)(4)
+      - FROM class-of-service( class-of-service BelongsTo site-pair, MANY2ONE)(1)
+
+      -(1) IF this SITE-PAIR node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this SITE-PAIR is DELETED also
     required:
-    - vf-module-id
-    - is-base-vf-module
+    - site-pair-id
     properties:
-      vf-module-id:
-        type: string
-        description: Unique ID of vf-module.
-      vf-module-name:
-        type: string
-        description: Name of vf-module
-      heat-stack-id:
-        type: string
-        description: Heat stack id corresponding to this instance.
-      orchestration-status:
-        type: string
-        description: orchestration status of this vf-module, mastered by MSO
-      is-base-vf-module:
-        type: boolean
-      resource-version:
+      site-pair-id:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      model-invariant-id:
+        description: unique identifier of probe
+      source-ip:
         type: string
-        description: the ASDC model id for this resource or service model.
-      model-version-id:
+        description: Prefix address
+      destination-ip:
         type: string
-        description: the ASDC model version for this resource or service model.
-      persona-model-version:
+        description: Prefix address
+      ip-version:
         type: string
-        description: the ASDC model version for this resource or service model.
-      model-customization-id:
+        description: ip version, v4, v6
+      destination-hostname:
         type: string
-        description: captures the id of all the configuration used to customize the resource for the service.
-      widget-model-id:
+        description: Hostname of the destination equipment to which SLAs are measured against.
+      destination-equip-type:
         type: string
-        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-      widget-model-version:
+        description: The type of destinatination equipment. Could be Router, etc.
+      resource-version:
         type: string
-        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-      contrail-service-instance-fqdn:
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      classes-of-service:
+        type: array
+        items:
+          $ref: "#/definitions/class-of-service"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+  site-pair-set:
+    description: |
+      Set of instances for probes used to measure service level agreements
+      ###### Related Nodes
+      - TO generic-vnf( site-pair-set AppliesTo generic-vnf, MANY2MANY)
+      - FROM routing-instance( routing-instance BelongsTo site-pair-set, MANY2ONE)(1)
+
+      -(1) IF this SITE-PAIR-SET node is deleted, this FROM node is DELETED also
+    required:
+    - site-pair-set-id
+    properties:
+      site-pair-set-id:
         type: string
-        description: the Contrail unique ID for a service-instance
-      module-index:
-        type: integer
-        format: int32
-        description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit
-      selflink:
+        description: Unique id of site pair set.
+      resource-version:
         type: string
-        description: Path to the controller object.
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      routing-instances:
+        type: array
+        items:
+          $ref: "#/definitions/routing-instance"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  vf-modules:
+  site-pair-sets:
     description: |
-      Collection of vf-modules, a deployment unit of VNFCs
+      Collection of sets of instances for probes related to generic-vnf
     properties:
-      vf-module:
+      site-pair-set:
         type: array
         items:          
-          $ref: "#/definitions/vf-module"
-  generic-vnf:
+          $ref: "#/definitions/site-pair-set"
+  site-pairs:
     description: |
-      General purpose VNF
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO license-key-resource (Many2Many)
-      - TO l-interface (comprises generic-vnf, Many2Many)
-      - TO availability-zone (Many2Many)
-      - TO lag-interface (comprises generic-vnf, Many2Many)
-      - TO l3-network (Many2Many)
-      - TO pserver (Many2Many)
-      - TO vnf-image (Many2One)
-      - TO vserver (One2Many)
-      - TO service-instance (Many2Many)
-      - TO site-pair-set (Many2Many)
-      - TO network-profile (Many2Many)
-      - TO ipsec-configuration (Many2One)
-      - TO vf-module (comprises generic-vnf, One2Many)
-      - TO volume-group (One2Many)
-      - TO vnfc (One2Many)
-      - TO instance-group (Many2Many)
-      - TO entitlement (comprises generic-vnf, One2Many)
-      - TO license (comprises generic-vnf, One2Many)
-      - FROM virtual-data-center
-      - FROM logical-link
-      - FROM allotted-resource
+      probe within a set
+    properties:
+      site-pair:
+        type: array
+        items:          
+          $ref: "#/definitions/site-pair"
+  snapshot:
+    description: |
+      Openstack snapshot
+      ###### Related Nodes
+      - TO cloud-region( snapshot BelongsTo cloud-region, MANY2ONE)
+      - FROM vserver( vserver Uses snapshot, ONE2ONE)
+
     required:
-    - vnf-id
-    - vnf-name
-    - vnf-type
-    - in-maint
-    - is-closed-loop-disabled
+    - snapshot-id
     properties:
-      vnf-id:
-        type: string
-        description: Unique id of VNF.  This is unique across the graph.
-      vnf-name:
-        type: string
-        description: Name of VNF.
-      vnf-name2:
-        type: string
-        description: Alternate name of VNF.
-      vnf-type:
-        type: string
-        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-      service-id:
-        type: string
-        description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
-      regional-resource-zone:
-        type: string
-        description: Regional way of organizing pservers, source of truth should define values
-      prov-status:
-        type: string
-        description: Trigger for operational monitoring of this resource by Service Assurance systems.
-      operational-status:
-        type: string
-        description: Indicator for whether the resource is considered operational.  Valid values are in-service-path and out-of-service-path.
-      license-key:
-        type: string
-        description: OBSOLETE -  do not use
-      equipment-role:
-        type: string
-        description: Client should send valid enumerated value
-      orchestration-status:
-        type: string
-        description: Orchestration status of this VNF, used by MSO.
-      heat-stack-id:
+      snapshot-id:
         type: string
-        description: Heat stack id corresponding to this instance, managed by MSO
-      mso-catalog-key:
+        description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+      snapshot-name:
         type: string
-        description: Corresponds to the SDN-C catalog id used to configure this VCE
-      management-option:
+        description: Snapshot name
+      snapshot-architecture:
         type: string
-        description: identifier of managed by company or customer
-      ipv4-oam-address:
+        description: Operating system architecture
+      snapshot-os-distro:
         type: string
-        description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
-      ipv4-loopback0-address:
+        description: The common name of the operating system distribution in lowercase
+      snapshot-os-version:
         type: string
-        description: v4 Loopback0 address
-      nm-lan-v6-address:
+        description: The operating system version as specified by the distributor.
+      application:
         type: string
-        description: v6 Loopback address
-      management-v6-address:
+        description: The application that the image instantiates.
+      application-vendor:
         type: string
-        description: v6 management address
-      vcpu:
-        type: integer
-        format: int64
-        description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
-      vcpu-units:
+        description: The vendor of the application.
+      application-version:
         type: string
-        description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only in some usecases
-      vmemory:
-        type: integer
-        format: int64
-        description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
-      vmemory-units:
+        description: The version of the application.
+      snapshot-selflink:
         type: string
-        description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only in some usecases
-      vdisk:
-        type: integer
-        format: int64
-        description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
-      vdisk-units:
+        description: URL to endpoint where AAI can get more details
+      prev-snapshot-id:
         type: string
-        description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only in some usecases
-      in-maint:
-        type: boolean
-      is-closed-loop-disabled:
-        type: boolean
+        description: This field contains the UUID of the previous snapshot (if any).
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      summary-status:
-        type: string
-        description: details regarding the generic-vnf operation, PLEASE DISCONTINUE USE OF THIS FIELD.
-      encrypted-access-flag:
-        type: boolean
-        description: indicates whether generic-vnf access uses SSH
-      entitlement-assignment-group-uuid:
-        type: string
-        description: UUID of the Entitlement group used for licensing VNFs, OBSOLETE -  See child relationships.
-      entitlement-resource-uuid:
-        type: string
-        description: UUID of the specific entitlement resource.  OBSOLETE -  See child relationships.
-      license-assignment-group-uuid:
-        type: string
-        description: UUID of the license assignment group.  OBSOLETE -  See child relationships.
-      license-key-uuid:
-        type: string
-        description: UUID of the actual license resource.  OBSOLETE -  See child relationships.
-      model-invariant-id:
-        type: string
-        description: the ASDC model id for this resource or service model.
-      model-version-id:
-        type: string
-        description: the ASDC model version for this resource or service model.
-      persona-model-version:
-        type: string
-        description: the ASDC model version for this resource or service model.
-      model-customization-id:
-        type: string
-        description: captures the id of all the configuration used to customize the resource for the service.
-      widget-model-id:
-        type: string
-        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
-      widget-model-version:
-        type: string
-        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
-      as-number:
-        type: string
-        description: as-number of the VNF
-      regional-resource-subzone:
-        type: string
-        description: represents sub zone of the rr plane
-      nf-type:
-        type: string
-        description: Generic description of the type of NF
-      nf-function:
-        type: string
-        description: English description of Network function that the specific VNF deployment is providing
-      nf-role:
-        type: string
-        description: role in the network that this model will be providing
-      nf-naming-code:
-        type: string
-        description: string assigned to this model used for naming purposes
-      selflink:
-        type: string
-        description: Path to the controller object.
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-      l-interfaces:
-        type: array
-        items:
-          $ref: "#/definitions/l-interface"
-      lag-interfaces:
-        type: array
-        items:
-          $ref: "#/definitions/lag-interface"
-      vf-modules:
-        type: array
-        items:
-          $ref: "#/definitions/vf-module"
-      licenses:
-        type: array
-        items:
-          $ref: "#/definitions/license"
-      entitlements:
-        type: array
-        items:
-          $ref: "#/definitions/entitlement"
-  generic-vnfs:
+  snapshots:
     description: |
-      Collection of VNFs
+      Collection of openstack snapshots
     properties:
-      generic-vnf:
+      snapshot:
         type: array
         items:          
-          $ref: "#/definitions/generic-vnf"
-  lag-link:
+          $ref: "#/definitions/snapshot"
+  sriov-pf:
     description: |
-      LAG links can connect lag-interfaces
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      SR-IOV Physical Function
       ###### Related Nodes
-      - FROM lag-interface
-      - FROM logical-link
+      - TO p-interface( sriov-pf BelongsTo p-interface, ONE2ONE)(4)
+      - FROM sriov-vf( sriov-vf Uses sriov-pf, MANY2ONE)
+
+      -(4) IF this TO node is deleted, this SRIOV-PF is DELETED also
     required:
-    - link-name
+    - pf-pci-id
     properties:
-      link-name:
+      pf-pci-id:
         type: string
-        description: Alphabetical concatenation of lag-interface names
+        description: Identifier for the sriov-pf
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
@@ -41459,963 +45661,10707 @@ definitions:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  lag-links:
+  sriov-pfs:
     description: |
-      Collection of link aggregation connections
+      Collection of SR-IOV Physical Functions.
     properties:
-      lag-link:
+      sriov-pf:
         type: array
         items:          
-          $ref: "#/definitions/lag-link"
-  newvce:
+          $ref: "#/definitions/sriov-pf"
+  sriov-vf:
     description: |
-      This object fills in the gaps from vce that were incorporated into generic-vnf.  This object will be retired with vce.
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
+      SR-IOV Virtual Function (not to be confused with virtual network function)
       ###### Related Nodes
-      - TO l-interface (comprises newvce, Many2Many)
+      - TO l-interface( sriov-vf BelongsTo l-interface, ONE2ONE)(4)
+
+      -(4) IF this TO node is deleted, this SRIOV-VF is DELETED also
     required:
-    - vnf-id2
-    - vnf-name
-    - vnf-type
+    - pci-id
     properties:
-      vnf-id2:
-        type: string
-        description: Unique id of VNF, can't use same attribute name right now until we promote this new object
-      vnf-name:
-        type: string
-        description: Name of VNF.
-      vnf-name2:
-        type: string
-        description: Alternate name of VNF.
-      vnf-type:
-        type: string
-        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
-      prov-status:
+      pci-id:
         type: string
-        description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
-      operational-status:
+        description: PCI ID used to identify the sriov-vf
+      vf-vlan-filter:
         type: string
-        description: Indicator for whether the resource is considered operational
-      license-key:
+        description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+      vf-mac-filter:
         type: string
-        description: OBSOLETE -  do not use
-      ipv4-oam-address:
+        description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+      vf-vlan-strip:
+        type: boolean
+        description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+      vf-vlan-anti-spoof-check:
+        type: boolean
+        description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+      vf-mac-anti-spoof-check:
+        type: boolean
+        description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+      vf-mirrors:
         type: string
-        description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
-      equipment-role:
+        description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+      vf-broadcast-allow:
+        type: boolean
+        description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+      vf-unknown-multicast-allow:
+        type: boolean
+        description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+      vf-unknown-unicast-allow:
+        type: boolean
+        description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+      vf-insert-stag:
+        type: boolean
+        description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+      vf-link-status:
         type: string
-        description: Client should send valid enumerated value.
+        description: This option is used to set the link status.  Valid values as of 1607 are on, off, and auto.
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      ipv4-loopback0-address:
-        type: string
-        description: v4 Loopback0 address
-      orchestration-status:
-        type: string
-        description: Orchestration status of this VNF, mastered by MSO.
-      heat-stack-id:
-        type: string
-        description: Heat stack id corresponding to this instance, managed by MSO
-      mso-catalog-key:
+      neutron-network-id:
         type: string
-        description: Corresponds to the SDN-C catalog id used to configure this VCE
+        description: Neutron network id of the interface
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-      l-interfaces:
-        type: array
-        items:
-          $ref: "#/definitions/l-interface"
-  newvces:
+  sriov-vfs:
     description: |
-      This object fills in the gaps from vce that were incorporated into generic-vnf.  This object will be retired with vce.
+      Collection of SR-IOV Virtual Functions.
     properties:
-      newvce:
+      sriov-vf:
         type: array
         items:          
-          $ref: "#/definitions/newvce"
-  pnf:
+          $ref: "#/definitions/sriov-vf"
+  start-node-filter:
+    properties:
+      property-name:
+        type: string
+      property-value:
+        type: string
+  subnet:
     description: |
-      PNF represents a physical network function. typically equipment used in the D1 world.
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
       ###### Related Nodes
-      - TO p-interface (comprises pnf, Many2Many)
-      - TO lag-interface (comprises pnf, One2Many)
-      - TO complex (Many2One)
-      - TO instance-group (Many2Many)
-      - TO zone (Many2One)
-      - FROM logical-link
-      - FROM service-instance
+      - TO l3-network( subnet BelongsTo l3-network, MANY2ONE)(4)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list MemberOf subnet, MANY2MANY)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list MemberOf subnet, MANY2MANY)
+
+      -(4) IF this TO node is deleted, this SUBNET is DELETED also
+      -SUBNET cannot be deleted if related to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+
     required:
-    - pnf-name
-    - in-maint
+    - subnet-id
+    - dhcp-enabled
     properties:
-      pnf-name:
-        type: string
-        description: unique name of Physical Network Function.
-      pnf-name2:
-        type: string
-        description: name of Physical Network Function.
-      pnf-name2-source:
+      subnet-id:
         type: string
-        description: source of name2
-      pnf-id:
+        description: Subnet ID, should be UUID.
+      subnet-name:
         type: string
-        description: id of pnf
-      equip-type:
+        description: Name associated with the subnet.
+      neutron-subnet-id:
         type: string
-        description: Equipment type.  Source of truth should define valid values.
-      equip-vendor:
+        description: Neutron id of this subnet
+      gateway-address:
         type: string
-        description: Equipment vendor.  Source of truth should define valid values.
-      equip-model:
+        description: gateway ip address
+      network-start-address:
         type: string
-        description: Equipment model.  Source of truth should define valid values.
-      management-option:
+        description: network start address
+      cidr-mask:
         type: string
-        description: identifier of managed by company or customer
-      ipaddress-v4-oam:
+        description: cidr mask
+      ip-version:
         type: string
-        description: ipv4-oam-address with new naming convention for IP addresses
-      sw-version:
+        description: ip version
+      orchestration-status:
         type: string
-        description: sw-version is the version of SW for the hosted application on the PNF.
-      in-maint:
+        description: Orchestration status of this VNF, mastered by MSO
+      dhcp-enabled:
         type: boolean
-      frame-id:
-        type: string
-        description: ID of the physical frame (relay rack) where pnf is installed.
-      serial-number:
-        type: string
-        description: Serial number of the device
-      ipaddress-v4-loopback-0:
-        type: string
-        description: IPV4 Loopback 0 address
-      ipaddress-v6-loopback-0:
-        type: string
-        description: IPV6 Loopback 0 address
-      ipaddress-v4-aim:
-        type: string
-        description: IPV4 AIM address
-      ipaddress-v6-aim:
-        type: string
-        description: IPV6 AIM address
-      ipaddress-v6-oam:
+        description: dhcp enabled
+      dhcp-start:
         type: string
-        description: IPV6 OAM address
-      inv-status:
+        description: the start address reserved for use by dhcp
+      dhcp-end:
         type: string
-        description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+        description: the last address reserved for use by dhcp
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      prov-status:
-        type: string
-        description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV]
-      nf-role:
-        type: string
-        description: Nf Role is the role performed by this instance in the network.
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-      p-interfaces:
-        type: array
-        items:
-          $ref: "#/definitions/p-interface"
-      lag-interfaces:
+  subnets:
+    properties:
+      subnet:
         type: array
-        items:
-          $ref: "#/definitions/lag-interface"
-  pnfs:
-    description: |
-      Collection of Physical Network Functions.
+        items:          
+          $ref: "#/definitions/subnet"
+  tagged-inventory-item-list:
     properties:
-      pnf:
+      inventory-item:
         type: array
         items:          
-          $ref: "#/definitions/pnf"
-  physical-link:
+          $ref: "#/definitions/inventory-item"
+  tenant:
     description: |
-      Collection of physical connections, typically between p-interfaces
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      Openstack tenant
       ###### Related Nodes
-      - FROM p-interface
+      - TO cloud-region( tenant BelongsTo cloud-region, MANY2ONE)
+      - TO group-assignment( tenant MemberOf group-assignment, MANY2MANY)
+      - TO l3-network( tenant Uses l3-network, MANY2MANY)
+      - TO volume-group( tenant DependsOn volume-group, ONE2MANY)
+      - FROM service-subscription( service-subscription Uses tenant, MANY2MANY)
+      - FROM vserver( vserver BelongsTo tenant, MANY2ONE)
+
+      -TENANT cannot be deleted if related to VSERVER
+
     required:
-    - link-name
+    - tenant-id
+    - tenant-name
     properties:
-      link-name:
-        type: string
-        description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
-      speed-value:
-        type: string
-        description: Captures the numeric part of the speed
-      speed-units:
-        type: string
-        description: Captures the units corresponding to the speed
-      circuit-id:
-        type: string
-        description: Circuit it
-      dual-mode:
-        type: string
-        description: Dual access mode (e.g., primary, secondary
-      management-option:
+      tenant-id:
         type: string
-        description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
-      service-provider-name:
+        description: Unique id relative to the cloud-region.
+      tenant-name:
         type: string
-        description: Name of the service Provider on this link.
+        description: Readable name of tenant
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      vservers:
+        type: array
+        items:
+          $ref: "#/definitions/vserver"
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  physical-links:
+  tenants:
     description: |
-      Collection of physical connections, typically between p-interfaces
+      Collection of openstack tenants.
     properties:
-      physical-link:
+      tenant:
         type: array
         items:          
-          $ref: "#/definitions/physical-link"
-  vig-server:
+          $ref: "#/definitions/tenant"
+  tunnel-xconnect:
     description: |
-      vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
       ###### Related Nodes
-      - FROM ipsec-configuration (is composed of vig-server)
+      - TO allotted-resource( tunnel-xconnect BelongsTo allotted-resource, ONE2ONE)(4)
+
+      -(4) IF this TO node is deleted, this TUNNEL-XCONNECT is DELETED also
     required:
-    - vig-address-type
+    - id
+    - bandwidth-up-wan1
+    - bandwidth-down-wan1
+    - bandwidth-up-wan2
+    - bandwidth-down-wan2
     properties:
-      vig-address-type:
+      id:
         type: string
-        description: indicates whether the VIG is for AVPN or INTERNET
-      ipaddress-v4-vig:
+        description: Allotted Resource id UUID assigned to this instance.
+      bandwidth-up-wan1:
         type: string
-        description: v4 IP of the vig server
-      ipaddress-v6-vig:
+        description: The WAN uplink bandwidth for WAN1
+      bandwidth-down-wan1:
         type: string
-        description: v6 IP of the vig server
+        description: The WAN downlink bandwidth for WAN1
+      bandwidth-up-wan2:
+        type: string
+        description: The WAN uplink bandwidth for WAN2
+      bandwidth-down-wan2:
+        type: string
+        description: The WAN downlink bandwidth for WAN2
       resource-version:
         type: string
-        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+        description: Concurrency value
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  vig-servers:
+  tunnel-xconnects:
+    description: |
+      This object is used to store the specific tunnel cross connect aspects of an allotted resource
     properties:
-      vig-server:
+      tunnel-xconnect:
         type: array
         items:          
-          $ref: "#/definitions/vig-server"
-  ipsec-configuration:
+          $ref: "#/definitions/tunnel-xconnect"
+  update:
     description: |
-      IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
-      ###### Default Delete Scope
-      CASCADE_TO_CHILDREN
-      ###### Related Nodes
-      - TO vig-server (comprises ipsec-configuration, One2Many)
-      - FROM generic-vnf
+      Serves a PATCH like function.  Does not enforce concurrency control.  Clear each usage with AAI team.
     required:
-    - ipsec-configuration-id
+    - update-node-type
     properties:
-      ipsec-configuration-id:
-        type: string
-        description: UUID of this configuration
-      requested-vig-address-type:
+      update-node-type:
         type: string
-        description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
-      requested-encryption-strength:
+      update-node-key:
+        type: array
+        items:          
+          $ref: "#/definitions/update-node-key"
+      update-node-uri:
         type: string
-        description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
-      requested-dmz-type:
+      action:
+        type: array
+        items:          
+          $ref: "#/definitions/action"
+  update-node-key:
+    properties:
+      key-name:
         type: string
-        description: can offer a shared DMZ or a DMZ specific to a customer
-      shared-dmz-network-address:
+      key-value:
         type: string
-        description: Network address of shared DMZ
-      requested-customer-name:
+  vce:
+    description: |
+      Virtual Customer Edge Router, used specifically for Gamma.  This object is deprecated.
+      ###### Related Nodes
+      - TO availability-zone( vce Uses availability-zone, MANY2MANY)
+      - TO complex( vce LocatedIn complex, MANY2MANY)
+      - TO vserver( vce HostedOn vserver, ONE2MANY)
+      - FROM entitlement( entitlement BelongsTo vce, MANY2ONE)(1)
+      - FROM license( license BelongsTo vce, MANY2ONE)(1)
+      - FROM port-group( port-group BelongsTo vce, MANY2ONE)(1)
+      - FROM service-instance( service-instance ComposedOf vce, ONE2MANY)
+
+      -(1) IF this VCE node is deleted, this FROM node is DELETED also
+    required:
+    - vnf-id
+    - vnf-name
+    - vnf-type
+    properties:
+      vnf-id:
         type: string
-        description: If the DMZ is a custom DMZ, this field will indicate the customer information
-      ike-version:
+        description: Unique id of VNF.  This is unique across the graph.
+      vnf-name:
         type: string
-        description: can be 1 or 2
-      ikev1-authentication:
+        description: Name of VNF.
+      vnf-name2:
         type: string
-        description: Contains values like md5, sha1, sha256, sha384
-      ikev1-encryption:
+        description: Alternate name of VNF.
+      vnf-type:
         type: string
-        description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
-      ikev1-dh-group:
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      service-id:
         type: string
-        description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
-      ikev1-am-group-id:
+        description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+      regional-resource-zone:
         type: string
-        description: Group name defined in VIG for clients using aggressive mode
-      ikev1-am-password:
+        description: Regional way of organizing pservers, source of truth should define values
+      prov-status:
         type: string
-        description: pre-shared key for the above group name 
-      ikev1-sa-lifetime:
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+      operational-status:
         type: string
-        description: Lifetime for IKEv1 SA
-      ipsec-authentication:
+        description: Indicator for whether the resource is considered operational
+      license-key:
         type: string
-        description: md5, sha1, sha256, sha384
-      ipsec-encryption:
+        description: OBSOLETE -  do not use
+      equipment-role:
         type: string
-        description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
-      ipsec-sa-lifetime:
+        description: Network role being played by this VNF
+      orchestration-status:
         type: string
-        description: Life time for IPSec SA
-      ipsec-pfs:
+        description: Orchestration status of this VNF, mastered by MSO
+      heat-stack-id:
         type: string
-        description: enable PFS or not
-      xauth-userid:
+        description: Heat stack id corresponding to this instance, managed by MSO
+      mso-catalog-key:
         type: string
-        description: user ID for xAuth, sm-user, ,nmteHostName
-      xauth-user-password:
+        description: Corresponds to the SDN-C catalog id used to configure this VCE
+      vpe-id:
         type: string
-        description: Encrypted using the Juniper $9$ algorithm
-      dpd-interval:
+        description: Unique ID of VPE connected to this VCE.
+      v6-vce-wan-address:
         type: string
-        description: The time between DPD probe
-      dpd-frequency:
+        description: Valid v6 IP address for the WAN Link on this router.  Implied length of /64.
+      ipv4-oam-address:
         type: string
-        description: Maximum number of DPD before claiming the tunnel is down
+        description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      relationship-list:
+      ipv4-loopback0-address:
+        type: string
+        description: Loopback0 address
+      entitlement-resource-uuid:
+        type: string
+        description: OBSOLETE -  see child relationships
+      port-groups:
         type: array
         items:
-          $ref: "#/definitions/relationship"
-      vig-servers:
+          $ref: "#/definitions/port-group"
+      licenses:
         type: array
         items:
-          $ref: "#/definitions/vig-server"
-  ipsec-configurations:
+          $ref: "#/definitions/license"
+      entitlements:
+        type: array
+        items:
+          $ref: "#/definitions/entitlement"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+  vces:
+    description: |
+      Collection of Virtual Customer Edge Routers, used specifically for Gamma.  This object is deprecated.
     properties:
-      ipsec-configuration:
+      vce:
         type: array
         items:          
-          $ref: "#/definitions/ipsec-configuration"
-  route-table-reference:
+          $ref: "#/definitions/vce"
+  vf-module:
     description: |
-      Openstack route table reference.
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      a deployment unit of VNFCs
       ###### Related Nodes
-      - FROM l3-network
+      - TO generic-vnf( vf-module BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO l3-network( vf-module DependsOn l3-network, MANY2MANY)
+      - TO vnfc( vf-module Uses vnfc, ONE2MANY)
+      - TO volume-group( vf-module Uses volume-group, ONE2ONE)
+      - TO vserver( vf-module Uses vserver, ONE2MANY)
+
+      -(4) IF this TO node is deleted, this VF-MODULE is DELETED also
+      -VF-MODULE cannot be deleted if related to VNFC
+
     required:
-    - route-table-reference-id
-    - route-table-reference-fqdn
+    - vf-module-id
+    - is-base-vf-module
     properties:
-      route-table-reference-id:
+      vf-module-id:
         type: string
-        description: Route Table Reference id, UUID assigned to this instance.
-      route-table-reference-fqdn:
+        description: Unique ID of vf-module.
+      vf-module-name:
         type: string
-        description: FQDN entry in the route table.
+        description: Name of vf-module
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance.
+      orchestration-status:
+        type: string
+        description: orchestration status of this vf-module, mastered by MSO
+      is-base-vf-module:
+        type: boolean
+        description: used to indicate whether or not this object is base vf module
       resource-version:
         type: string
-        description: Concurrency value
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      model-customization-id:
+        type: string
+        description: captures the id of all the configuration used to customize the resource for the service.
+      widget-model-id:
+        type: string
+        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+      widget-model-version:
+        type: string
+        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+      contrail-service-instance-fqdn:
+        type: string
+        description: the Contrail unique ID for a service-instance
+      module-index:
+        type: integer
+        format: int32
+        description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit
+      selflink:
+        type: string
+        description: Path to the controller object.
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  route-table-references:
+  vf-modules:
     description: |
-      Collection of openstack route table references
+      Collection of vf-modules, a deployment unit of VNFCs
     properties:
-      route-table-reference:
+      vf-module:
         type: array
         items:          
-          $ref: "#/definitions/route-table-reference"
-  instance-group:
+          $ref: "#/definitions/vf-module"
+  vig-server:
     description: |
-      General mechanism for grouping instances
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
-      ###### Related Nodes
-      - TO model (Many2Many)
-      - FROM l-interface
-      - FROM l3-interface-ipv4-address-list
-      - FROM l3-interface-ipv6-address-list
-      - FROM pnf
-      - FROM allotted-resource
-      - FROM generic-vnf
-      - FROM service-instance
+      vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+      ###### Related Nodes
+      - TO ipsec-configuration( vig-server BelongsTo ipsec-configuration, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this VIG-SERVER is DELETED also
     required:
-    - id
-    - description
-    - type
+    - vig-address-type
     properties:
-      id:
-        type: string
-        description: Instance Group ID, UUID assigned to this instance.
-      description:
+      vig-address-type:
         type: string
-        description: Descriptive text to help identify the usage of this instance-group
-      type:
+        description: indicates whether the VIG is for AVPN or INTERNET
+      ipaddress-v4-vig:
         type: string
-        description: Only valid value today is lower case ha for high availability
-      sub-type:
+        description: v4 IP of the vig server
+      ipaddress-v6-vig:
         type: string
-        description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+        description: v6 IP of the vig server
       resource-version:
         type: string
-        description: Concurrency value
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  instance-groups:
-    description: |
-      Collection of openstack route table references
+  vig-servers:
     properties:
-      instance-group:
+      vig-server:
         type: array
         items:          
-          $ref: "#/definitions/instance-group"
-  zone:
+          $ref: "#/definitions/vig-server"
+  vip-ipv4-address-list:
     description: |
-      A zone is a grouping of assets in a location homing to the same connections into the CBB
-      ###### Default Delete Scope
-      THIS_NODE_ONLY
+      IPv4 Address Range
       ###### Related Nodes
-      - TO complex (Many2One)
-      - FROM cloud-region
-      - FROM pserver
-      - FROM pnf
+      - TO cloud-region( vip-ipv4-address-list BelongsTo cloud-region, MANY2ONE)
+      - TO instance-group( vip-ipv4-address-list MemberOf instance-group, MANY2MANY)
+      - TO subnet( vip-ipv4-address-list MemberOf subnet, MANY2MANY)
+      - FROM vnfc( vnfc Uses vip-ipv4-address-list, MANY2MANY)
+
     required:
-    - zone-id
-    - zone-name
-    - design-type
-    - zone-context
+    - vip-ipv4-address
     properties:
-      zone-id:
+      vip-ipv4-address:
         type: string
-        description: Code assigned by AIC to the zone
-      zone-name:
+        description: IP address
+      vip-ipv4-prefix-length:
+        type: integer
+        format: int64
+        description: Prefix length, 32 for single address
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      is-floating:
+        type: boolean
+        description: Indicator of fixed or floating address
+      resource-version:
         type: string
-        description: English name associated with the zone
-      design-type:
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      neutron-network-id:
         type: string
-        description: Design of zone [Medium/Large?]
-      zone-context:
+        description: Neutron network id of the interface that address belongs to
+      neutron-subnet-id:
         type: string
-        description: Context of zone [production/test]
-      status:
+        description: Neutron id of subnet that address belongs to
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+  vip-ipv6-address-list:
+    description: |
+      IPv6 Address Range
+      ###### Related Nodes
+      - TO cloud-region( vip-ipv6-address-list BelongsTo cloud-region, MANY2ONE)
+      - TO instance-group( vip-ipv6-address-list MemberOf instance-group, MANY2MANY)
+      - TO subnet( vip-ipv6-address-list MemberOf subnet, MANY2MANY)
+      - FROM vnfc( vnfc Uses vip-ipv6-address-list, MANY2MANY)
+
+    required:
+    - vip-ipv6-address
+    properties:
+      vip-ipv6-address:
         type: string
-        description: Status of a zone.
+        description: IP address
+      vip-ipv6-prefix-length:
+        type: integer
+        format: int64
+        description: Prefix length, 128 for single address
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      is-floating:
+        type: boolean
+        description: Indicator of fixed or floating address
       resource-version:
         type: string
-        description: Concurrency value
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      neutron-network-id:
+        type: string
+        description: Neutron network id of the interface that address belongs to
+      neutron-subnet-id:
+        type: string
+        description: Neutron id of subnet that address belongs to
       relationship-list:
         type: array
         items:
           $ref: "#/definitions/relationship"
-  zones:
+  virtual-data-center:
     description: |
-      Collection of zones
+      Virtual organization of cloud infrastructure elements in a data center context
+      ###### Related Nodes
+      - FROM connector( connector LocatedIn virtual-data-center, MANY2MANY)
+      - FROM generic-vnf( generic-vnf LocatedIn virtual-data-center, MANY2MANY)
+      - FROM logical-link( logical-link LocatedIn virtual-data-center, MANY2MANY)
+
+    required:
+    - vdc-id
+    - vdc-name
     properties:
-      zone:
+      vdc-id:
+        type: string
+        description: Unique ID of the vdc
+      vdc-name:
+        type: string
+        description: Name of the virtual data center
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
         type: array
-        items:          
-          $ref: "#/definitions/zone"
-  network:
+        items:
+          $ref: "#/definitions/relationship"
+  virtual-data-centers:
     description: |
-      Namespace for network inventory resources.
+      Virtual organization of cloud infrastructure elements in a data center context
     properties:
-      logical-links:
-        type: array
-        items:
-          $ref: "#/definitions/logical-link"
-      site-pair-sets:
+      virtual-data-center:
         type: array
-        items:
-          $ref: "#/definitions/site-pair-set"
-      vpn-bindings:
+        items:          
+          $ref: "#/definitions/virtual-data-center"
+  vlan:
+    description: |
+      Definition of vlan
+      ###### Related Nodes
+      - TO l-interface( vlan LinksTo l-interface, MANY2ONE)(4)
+      - TO logical-link( vlan Uses logical-link, MANY2MANY)(2)
+      - TO multicast-configuration( vlan Uses multicast-configuration, MANY2MANY)
+      - FROM allotted-resource( allotted-resource PartOf vlan, MANY2MANY)
+      - FROM service-instance( service-instance ComposedOf vlan, ONE2MANY)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list BelongsTo vlan, MANY2ONE)(1)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list BelongsTo vlan, MANY2ONE)(1)
+
+      -(1) IF this VLAN node is deleted, this FROM node is DELETED also
+      -(2) IF this VLAN node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this VLAN is DELETED also
+    required:
+    - vlan-interface
+    - in-maint
+    properties:
+      vlan-interface:
+        type: string
+        description: String that identifies the interface
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      speed-value:
+        type: string
+        description: Captures the numeric part of the speed
+      speed-units:
+        type: string
+        description: Captures the units corresponding to the speed
+      vlan-description:
+        type: string
+        description: Used to describe (the service associated with) the vlan
+      backdoor-connection:
+        type: string
+        description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
+      vpn-id:
+        type: string
+        description: This indicates the customers VPN ID associated with this vlan
+      orchestration-status:
+        type: string
+        description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C.
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true)
+      relationship-list:
         type: array
         items:
-          $ref: "#/definitions/vpn-binding"
-      vpls-pes:
+          $ref: "#/definitions/relationship"
+      l3-interface-ipv4-address-list:
         type: array
-        items:
-          $ref: "#/definitions/vpls-pe"
-      multicast-configurations:
+        items:          
+          $ref: "#/definitions/l3-interface-ipv4-address-list"
+      l3-interface-ipv6-address-list:
         type: array
-        items:
-          $ref: "#/definitions/multicast-configuration"
-      vces:
+        items:          
+          $ref: "#/definitions/l3-interface-ipv6-address-list"
+  vlans:
+    properties:
+      vlan:
         type: array
-        items:
-          $ref: "#/definitions/vce"
-      vnfcs:
+        items:          
+          $ref: "#/definitions/vlan"
+  vnf:
+    description: |
+      Abstract vnf class
+    required:
+    - vnf-id
+    properties:
+      vnf-id:
+        type: string
+        description: Unique id of VNF.  This is unique across the graph.
+  vnf-image:
+    description: |
+      Image object that pertain to a VNF that doesn't have associated vservers.  This is a kludge.
+      ###### Related Nodes
+      - FROM generic-vnf( generic-vnf Uses vnf-image, MANY2ONE)
+
+      -VNF-IMAGE cannot be deleted if related to GENERIC-VNF
+
+    required:
+    - vnf-image-uuid
+    - application
+    - application-vendor
+    properties:
+      vnf-image-uuid:
+        type: string
+        description: Unique ID of this asset
+      application:
+        type: string
+        description: The application that the image instantiates.
+      application-vendor:
+        type: string
+        description: The vendor of the application.
+      application-version:
+        type: string
+        description: The version of the application.
+      selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
         type: array
         items:
-          $ref: "#/definitions/vnfc"
-      l3-networks:
+          $ref: "#/definitions/relationship"
+  vnf-images:
+    description: |
+      Collection of image objects that pertain to a VNF that doesn't have associated vservers.  This is a kludge.
+    properties:
+      vnf-image:
         type: array
-        items:
-          $ref: "#/definitions/l3-network"
-      network-policies:
+        items:          
+          $ref: "#/definitions/vnf-image"
+  vnfc:
+    description: |
+      ###### Related Nodes
+      - TO generic-vnf( vnfc BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO vserver( vnfc HostedOn vserver, ONE2MANY)
+      - FROM vf-module( vf-module Uses vnfc, ONE2MANY)
+
+      -(4) IF this TO node is deleted, this VNFC is DELETED also
+    required:
+    - vnfc-name
+    - vnfc-function-code
+    - vnfc-type
+    - in-maint
+    - is-closed-loop-disabled
+    properties:
+      vnfc-name:
+        type: string
+        description: Unique ID of vnfc.
+      vnfc-function-code:
+        type: string
+        description: function code
+      vnfc-type:
+        type: string
+        description: type
+      prov-status:
+        type: string
+        description: prov status of this vnfc
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, mastered by APP-C
+      ipaddress-v4-oam-vip:
+        type: string
+        description: Oam V4 vip address of this vnfc
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true)
+      is-closed-loop-disabled:
+        type: boolean
+        description: used to indicate whether closed loop function is enabled on this node
+      group-notation:
+        type: string
+        description: Group notation of VNFC
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
         type: array
         items:
-          $ref: "#/definitions/network-policy"
-      generic-vnfs:
+          $ref: "#/definitions/relationship"
+  vnfcs:
+    description: |
+      virtual network components associated with a vserver from application controller.
+    properties:
+      vnfc:
         type: array
-        items:
-          $ref: "#/definitions/generic-vnf"
-      lag-links:
+        items:          
+          $ref: "#/definitions/vnfc"
+  volume:
+    description: |
+      Ephemeral Block storage volume.
+      ###### Related Nodes
+      - FROM vserver (PARENT of volume, vserver AttachesTo volume)(3)
+
+      -(3) IF this FROM node is deleted, this VOLUME is DELETED also
+    required:
+    - volume-id
+    - volume-selflink
+    properties:
+      volume-id:
+        type: string
+        description: Unique ID of block storage volume relative to the vserver.
+      volume-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
         type: array
         items:
-          $ref: "#/definitions/lag-link"
-      newvces:
+          $ref: "#/definitions/relationship"
+  volume-group:
+    description: |
+      Persistent block-level storage.
+      ###### Related Nodes
+      - TO cloud-region( volume-group BelongsTo cloud-region, MANY2ONE)
+      - TO complex( volume-group LocatedIn complex, MANY2ONE)
+      - FROM generic-vnf( generic-vnf DependsOn volume-group, ONE2MANY)
+      - FROM vf-module( vf-module Uses volume-group, ONE2ONE)
+      - FROM tenant( tenant DependsOn volume-group, ONE2MANY)
+
+    required:
+    - volume-group-id
+    - volume-group-name
+    - vnf-type
+    properties:
+      volume-group-id:
+        type: string
+        description: Unique ID of volume-group.
+      volume-group-name:
+        type: string
+        description: Name of the volume group.
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this volume-group
+      vnf-type:
+        type: string
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      orchestration-status:
+        type: string
+        description: Orchestration status of this volume-group
+      model-customization-id:
+        type: string
+        description: captures the id of all the configuration used to customize the resource for the service.
+      vf-module-model-customization-id:
+        type: string
+        description: helps relate the volume group to the vf-module whose components will require the volume group
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
         type: array
         items:
-          $ref: "#/definitions/newvce"
-      pnfs:
+          $ref: "#/definitions/relationship"
+  volume-groups:
+    description: |
+      Collection of persistent block-level storage.
+    properties:
+      volume-group:
         type: array
-        items:
-          $ref: "#/definitions/pnf"
-      physical-links:
+        items:          
+          $ref: "#/definitions/volume-group"
+  volumes:
+    description: |
+      Collection of ephemeral Block storage volumes.
+    properties:
+      volume:
         type: array
-        items:
-          $ref: "#/definitions/physical-link"
-      ipsec-configurations:
+        items:          
+          $ref: "#/definitions/volume"
+  vpls-pe:
+    description: |
+      VPLS Provider Edge routers.
+      ###### Related Nodes
+      - TO complex( vpls-pe LocatedIn complex, MANY2ONE)
+      - TO ctag-pool( vpls-pe Uses ctag-pool, MANY2MANY)
+      - FROM lag-interface( lag-interface BindsTo vpls-pe, MANY2ONE)(1)
+      - FROM p-interface( p-interface BindsTo vpls-pe, MANY2ONE)(1)
+
+      -(1) IF this VPLS-PE node is deleted, this FROM node is DELETED also
+    required:
+    - equipment-name
+    properties:
+      equipment-name:
+        type: string
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+      ipv4-oam-address:
+        type: string
+        description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+      equipment-role:
+        type: string
+        description: Client should send valid enumerated value, e.g., VPLS-PE.
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Temporary location for stag to get to VCE
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
         type: array
         items:
-          $ref: "#/definitions/ipsec-configuration"
-      route-table-references:
+          $ref: "#/definitions/relationship"
+      p-interfaces:
         type: array
         items:
-          $ref: "#/definitions/route-table-reference"
-      instance-groups:
+          $ref: "#/definitions/p-interface"
+      lag-interfaces:
         type: array
         items:
-          $ref: "#/definitions/instance-group"
-      zones:
+          $ref: "#/definitions/lag-interface"
+  vpls-pes:
+    description: |
+      Collection of VPLS Provider Edge routers
+    properties:
+      vpls-pe:
         type: array
-        items:
-          $ref: "#/definitions/zone"
-  inventory:
+        items:          
+          $ref: "#/definitions/vpls-pe"
+  vpn-binding:
+    description: |
+      VPN binding
+      ###### Related Nodes
+      - FROM l3-network( l3-network Uses vpn-binding, MANY2MANY)
+      - FROM logical-link( logical-link Uses vpn-binding, MANY2MANY)
+      - FROM route-target( route-target BelongsTo vpn-binding, MANY2ONE)(1)
+
+      -(1) IF this VPN-BINDING node is deleted, this FROM node is DELETED also
+      -VPN-BINDING cannot be deleted if related to L3-NETWORK,LOGICAL-LINK
+
+    required:
+    - vpn-id
+    - vpn-name
     properties:
-      search:
-        type: object
-        $ref: "#/definitions/search"
-      actions:
-        type: object
-        $ref: "#/definitions/actions"
-      cloud-infrastructure:
-        type: object
-        $ref: "#/definitions/cloud-infrastructure"
-      business:
-        type: object
-        $ref: "#/definitions/business"
-      service-design-and-creation:
-        type: object
-        $ref: "#/definitions/service-design-and-creation"
-      network:
-        type: object
-        $ref: "#/definitions/network"
-      aai-internal:
-        type: object
-        $ref: "#/definitions/aai-internal"
-      nodes:
+      vpn-id:
+        type: string
+        description: VPN ID, globally unique within A&AI
+      vpn-name:
+        type: string
+        description: VPN Name
+      vpn-platform:
+        type: string
+        description: the platform associated with the VPN example AVPN, Mobility
+      vpn-type:
+        type: string
+        description: Type of the vpn, should be taken from enumerated/valid values
+      route-distinguisher:
+        type: string
+        description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      route-targets:
         type: array
         items:
-          $ref: "#/definitions/"
-  edge-tag-query-result:
-    properties:
-      tagged-inventory-item-list:
+          $ref: "#/definitions/route-target"
+      relationship-list:
         type: array
-        items:          
-          $ref: "#/definitions/tagged-inventory-item-list"
-  tagged-inventory-item-list:
+        items:
+          $ref: "#/definitions/relationship"
+        description: l3-networks relate to vpn-bindings
+  vpn-bindings:
     properties:
-      inventory-item:
+      vpn-binding:
         type: array
         items:          
-          $ref: "#/definitions/inventory-item"
-  inventory-item:
+          $ref: "#/definitions/vpn-binding"
+  vserver:
+    description: |
+      Virtual Servers, aka virtual machine or VM.
+      ###### Related Nodes
+      - TO tenant( vserver BelongsTo tenant, MANY2ONE)
+      - TO flavor( vserver Uses flavor, MANY2ONE)
+      - TO image( vserver Uses image, MANY2ONE)
+      - TO pserver( vserver HostedOn pserver, MANY2ONE)
+      - TO snapshot( vserver Uses snapshot, ONE2ONE)
+      - TO volume (CHILD of vserver, vserver AttachesTo volume, ONE2MANY)(2)
+      - FROM generic-vnf( generic-vnf HostedOn vserver, ONE2MANY)
+      - FROM vce( vce HostedOn vserver, ONE2MANY)
+      - FROM l-interface( l-interface BindsTo vserver, MANY2ONE)(1)
+      - FROM vf-module( vf-module Uses vserver, ONE2MANY)
+      - FROM vnfc( vnfc HostedOn vserver, ONE2MANY)
+
+      -(1) IF this VSERVER node is deleted, this FROM node is DELETED also
+      -(2) IF this VSERVER node is deleted, this TO node is DELETED also
+    required:
+    - vserver-id
+    - vserver-name
+    - vserver-selflink
+    - in-maint
+    - is-closed-loop-disabled
     properties:
-      inventory-item-type:
+      vserver-id:
         type: string
-      inventory-item-link:
+        description: Unique identifier for this vserver relative to its tenant
+      vserver-name:
         type: string
-      inventory-item-data:
+        description: Name of vserver
+      vserver-name2:
+        type: string
+        description: Alternative name of vserver
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+      vserver-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      in-maint:
+        type: boolean
+        description: Used to indicate whether or not this object is in maintenance mode (maintenance mode = true). This field (in conjunction with prov-status) is used to suppress alarms and vSCL on VNFs/VMs.
+      is-closed-loop-disabled:
+        type: boolean
+        description: Used to indicate whether closed loop function is enabled on this node
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      volumes:
         type: array
-        items:          
-          $ref: "#/definitions/inventory-item-data"
-      tagged-inventory-item-list:
+        items:
+          $ref: "#/definitions/volume"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/definitions/relationship"
+      l-interfaces:
+        type: array
+        items:
+          $ref: "#/definitions/l-interface"
+  vservers:
+    description: |
+      Collection of virtual Servers, aka virtual machines or VMs.
+    properties:
+      vserver:
         type: array
         items:          
-          $ref: "#/definitions/tagged-inventory-item-list"
-  inventory-item-data:
+          $ref: "#/definitions/vserver"
+  zone:
+    description: |
+      A zone is a grouping of assets in a location homing to the same connections into the CBB
+      ###### Related Nodes
+      - TO complex( zone LocatedIn complex, MANY2ONE)
+      - FROM cloud-region( cloud-region LocatedIn zone, MANY2ONE)
+      - FROM pnf( pnf LocatedIn zone, MANY2ONE)
+      - FROM pserver( pserver LocatedIn zone, MANY2ONE)
+
+    required:
+    - zone-id
+    - zone-name
+    - design-type
+    - zone-context
     properties:
-      property-name:
+      zone-id:
         type: string
-      property-value:
+        description: Code assigned by AIC to the zone
+      zone-name:
         type: string
-  edge-tag-query-request:
-    properties:
-      edge-tag:
+        description: English name associated with the zone
+      design-type:
         type: string
-      result-detail:
+        description: Design of zone [Medium/Large?]
+      zone-context:
         type: string
-      start-node-type:
+        description: Context of zone [production/test]
+      status:
         type: string
-      start-node-filter:
+        description: Status of a zone.
+      resource-version:
+        type: string
+        description: Concurrency value
+      relationship-list:
         type: array
-        items:          
-          $ref: "#/definitions/start-node-filter"
-      include-node-filter:
+        items:
+          $ref: "#/definitions/relationship"
+  zones:
+    description: |
+      Collection of zones
+    properties:
+      zone:
         type: array
         items:          
-          $ref: "#/definitions/include-node-filter"
-      secondary-filter:
+          $ref: "#/definitions/zone"
+patchDefinitions:
+  action:
+    properties:
+      action-type:
+        type: string
+      action-data:
         type: array
         items:          
-          $ref: "#/definitions/secondary-filter"
-  start-node-filter:
+          $ref: "#/patchDefinitions/action-data"
+  action-data:
     properties:
       property-name:
         type: string
       property-value:
         type: string
-  include-node-filter:
-    properties:
-      include-node-type:
-        type: string
-  secondary-filter:
+  actions:
+    description: |
+      APIs that are more action related than REST (e.g., notify, update).
     properties:
-      property-name:
+      update:
+        type: object
+        $ref: "#/patchDefinitions/update"
+      notify:
+        type: object
+        $ref: "#/patchDefinitions/notify"
+  allotted-resource:
+    description: |
+      Represents a slice or partial piece of a resource that gets separately allotted
+      ###### Related Nodes
+      - TO generic-vnf( allotted-resource PartOf generic-vnf, MANY2MANY)
+      - TO instance-group( allotted-resource MemberOf instance-group, MANY2MANY)
+      - TO l3-network( allotted-resource PartOf l3-network, MANY2MANY)
+      - TO network-policy( allotted-resource Uses network-policy, ONE2ONE)
+      - TO vlan( allotted-resource PartOf vlan, MANY2MANY)
+      - TO service-instance( allotted-resource BelongsTo service-instance, MANY2ONE)(4)
+      - FROM tunnel-xconnect( tunnel-xconnect BelongsTo allotted-resource, ONE2ONE)(1)
+      - FROM service-instance( service-instance Uses allotted-resource, MANY2MANY)
+
+      -(1) IF this ALLOTTED-RESOURCE node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this ALLOTTED-RESOURCE is DELETED also
+    required:
+    - id
+    properties:
+      id:
         type: string
-      filter-type:
+        description: Allotted Resource id UUID assigned to this instance.
+      description:
         type: string
-      property-value:
+        description: The descriptive information assigned to this allotted resource instance
+      selflink:
         type: string
-  search-results:
+        description: Link back to more information in the controller
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+  allotted-resources:
+    description: |
+      This object is used to store slices of services being offered
     properties:
-      result-data:
+      allotted-resource:
         type: array
         items:          
-          $ref: "#/definitions/result-data"
-  result-data:
+          $ref: "#/patchDefinitions/allotted-resource"
+  availability-zone:
+    description: |
+      Availability zone, a collection of compute hosts/pservers
+      ###### Related Nodes
+      - TO complex( availability-zone LocatedIn complex, MANY2ONE)
+      - TO service-capability( availability-zone AppliesTo service-capability, MANY2MANY)
+      - TO cloud-region( availability-zone BelongsTo cloud-region, MANY2ONE)(4)
+      - FROM ctag-pool( ctag-pool AppliesTo availability-zone, MANY2MANY)
+      - FROM dvs-switch( dvs-switch AppliesTo availability-zone, MANY2MANY)
+      - FROM generic-vnf( generic-vnf Uses availability-zone, MANY2MANY)
+      - FROM pserver( pserver MemberOf availability-zone, MANY2ONE)
+      - FROM vce( vce Uses availability-zone, MANY2MANY)
+
+      -(4) IF this TO node is deleted, this AVAILABILITY-ZONE is DELETED also
+      -AVAILABILITY-ZONE cannot be deleted if related to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+
+    required:
+    - availability-zone-name
+    - hypervisor-type
     properties:
-      resource-type:
+      availability-zone-name:
         type: string
-        description: The specific type of node in the A&AI graph
-      resource-link:
+        description: Name of the availability zone.  Unique across a cloud region
+      hypervisor-type:
         type: string
-        description: The URL to the specific resource
-  sdn-zone-response:
+        description: Type of hypervisor.  Source of truth should define valid values.
+      operational-status:
+        type: string
+        description: State that indicates whether the availability zone should be used, etc.  Source of truth should define valid values.
+  availability-zones:
+    description: |
+      Collection of availability zones
     properties:
-      oam-networks:
-        type: object
-        $ref: "#/definitions/oam-networks"
-      az-and-dvs-switches:
+      availability-zone:
         type: array
         items:          
-          $ref: "#/definitions/az-and-dvs-switches"
+          $ref: "#/patchDefinitions/availability-zone"
   az-and-dvs-switches:
     properties:
       dvs-switches:
         type: object
-        $ref: "#/definitions/dvs-switches"
+        $ref: "#/patchDefinitions/dvs-switches"
       availability-zone:
         type: object
-        $ref: "#/definitions/availability-zone"
-  update:
+        $ref: "#/patchDefinitions/availability-zone"
+  business:
+    description: |
+      Namespace for business related constructs
+    properties:
+      connectors:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/connector"
+      customers:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/customer"
+  class-of-service:
+    description: |
+      ###### Related Nodes
+      - TO site-pair( class-of-service BelongsTo site-pair, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this CLASS-OF-SERVICE is DELETED also
+    required:
+    - cos
+    properties:
+      cos:
+        type: string
+        description: unique identifier of probe
+      probe-id:
+        type: string
+        description: identifier of probe
+      probe-type:
+        type: string
+        description: type of probe
+  classes-of-service:
+    description: |
+      class-of-service of probe
+    properties:
+      class-of-service:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/class-of-service"
+  cloud-infrastructure:
+    description: |
+      Namespace for cloud infrastructure.
+    properties:
+      complexes:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/complex"
+      cloud-regions:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/cloud-region"
+      network-profiles:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/network-profile"
+      pservers:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/pserver"
+      virtual-data-centers:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/virtual-data-center"
+  cloud-region:
+    description: |
+      cloud-region designates an installation of a cloud cluster or region or instantiation
+      ###### Related Nodes
+      - TO complex( cloud-region LocatedIn complex, MANY2ONE)
+      - TO l3-network( cloud-region Uses l3-network, MANY2MANY)
+      - TO zone( cloud-region LocatedIn zone, MANY2ONE)
+      - FROM availability-zone( availability-zone BelongsTo cloud-region, MANY2ONE)(1)
+      - FROM dvs-switch( dvs-switch BelongsTo cloud-region, MANY2ONE)
+      - FROM flavor( flavor BelongsTo cloud-region, MANY2ONE)
+      - FROM group-assignment( group-assignment BelongsTo cloud-region, MANY2ONE)
+      - FROM image( image BelongsTo cloud-region, MANY2ONE)
+      - FROM oam-network( oam-network BelongsTo cloud-region, MANY2ONE)
+      - FROM snapshot( snapshot BelongsTo cloud-region, MANY2ONE)
+      - FROM tenant( tenant BelongsTo cloud-region, MANY2ONE)
+      - FROM volume-group( volume-group BelongsTo cloud-region, MANY2ONE)
+      - FROM logical-link( logical-link LocatedIn cloud-region, MANY2MANY)
+      - FROM pserver( pserver LocatedIn cloud-region, MANY2ONE)
+
+      -(1) IF this CLOUD-REGION node is deleted, this FROM node is DELETED also
+      -CLOUD-REGION cannot be deleted if related to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP
+
+    required:
+    - cloud-owner
+    - cloud-region-id
+    properties:
+      cloud-owner:
+        type: string
+        description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+      cloud-region-id:
+        type: string
+        description: Identifier used by the vendor for the region. Second part of composite key
+      cloud-type:
+        type: string
+        description: Type of the cloud (e.g., openstack)
+      owner-defined-type:
+        type: string
+        description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+      cloud-region-version:
+        type: string
+        description: Software version employed at the site.  NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
+      identity-url:
+        type: string
+        description: URL of the keystone identity service
+      cloud-zone:
+        type: string
+        description: Zone where the cloud is homed.  NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+      complex-name:
+        type: string
+        description: complex name for cloud-region instance.  NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+  cloud-regions:
+    properties:
+      cloud-region:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/cloud-region"
+  complex:
+    description: |
+      Collection of physical locations that can house cloud-regions.
+      ###### Related Nodes
+      - TO l3-network( complex Uses l3-network, MANY2MANY)
+      - FROM availability-zone( availability-zone LocatedIn complex, MANY2ONE)
+      - FROM cloud-region( cloud-region LocatedIn complex, MANY2ONE)
+      - FROM ctag-pool( ctag-pool BelongsTo complex, MANY2ONE)(1)
+      - FROM oam-network( oam-network AppliesTo complex, MANY2MANY)
+      - FROM pnf( pnf LocatedIn complex, MANY2ONE)
+      - FROM pserver( pserver LocatedIn complex, MANY2ONE)
+      - FROM vce( vce LocatedIn complex, MANY2MANY)
+      - FROM volume-group( volume-group LocatedIn complex, MANY2ONE)
+      - FROM vpls-pe( vpls-pe LocatedIn complex, MANY2ONE)
+      - FROM zone( zone LocatedIn complex, MANY2ONE)
+
+      -(1) IF this COMPLEX node is deleted, this FROM node is DELETED also
+      -COMPLEX cannot be deleted if related to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE
+
+    required:
+    - physical-location-id
+    - physical-location-type
+    - street1
+    - city
+    - postal-code
+    - country
+    - region
+    properties:
+      physical-location-id:
+        type: string
+        description: Unique identifier for physical location, e.g., CLLI
+      data-center-code:
+        type: string
+        description: Data center code which can be an alternate way to identify a complex
+      complex-name:
+        type: string
+        description: Gamma complex name for LCP instance.
+      identity-url:
+        type: string
+        description: URL of the keystone identity service
+  complexes:
+    description: |
+      Collection of physical locations that can house cloud-regions.
+    properties:
+      complex:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/complex"
+  configuration:
+    description: |
+      Port Mirror Configuration.
+      ###### Related Nodes
+      - TO allotted-resource( configuration Uses allotted-resource, ONE2ONE)(2)
+      - TO logical-link( configuration Uses logical-link, ONE2MANY)(2)
+      - FROM metadatum( metadatum BelongsTo configuration, MANY2ONE)(1)
+      - FROM generic-vnf( generic-vnf Uses configuration, ONE2MANY)(3)
+      - FROM service-instance( service-instance Uses configuration, ONE2MANY)
+
+      -(1) IF this CONFIGURATION node is deleted, this FROM node is DELETED also
+      -(2) IF this CONFIGURATION node is deleted, this TO node is DELETED also
+      -(3) IF this FROM node is deleted, this CONFIGURATION is DELETED also
+    required:
+    - configuration-id
+    - configuration-type
+    - configuration-sub-type
+    - orchestration-status
+    - operational-status
+    - configuration-selflink
+    - model-customization-id
+    properties:
+      configuration-id:
+        type: string
+        description: UUID assigned to configuration.
+      management-option:
+        type: string
+        description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+      configuration-name:
+        type: string
+        description: Name of the configuration.
+      configuration-type:
+        type: string
+        description: port-mirroring-configuration.
+      configuration-sub-type:
+        type: string
+        description: vprobe, pprobe.
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      orchestration-status:
+        type: string
+        description: Orchestration status of the configuration.
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational.
+      configuration-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details from SDN-GC.
+      model-customization-id:
+        type: string
+        description: id of  the configuration used to customize the resource
+  configurations:
+    description: |
+      Collection of configurations
+    properties:
+      configuration:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/configuration"
+  connector:
+    description: |
+      Collection of resource instances used to connect a variety of disparate inventory widgets
+      ###### Related Nodes
+      - TO virtual-data-center( connector LocatedIn virtual-data-center, MANY2MANY)
+      - FROM metadatum( metadatum BelongsTo connector, MANY2ONE)(1)
+      - FROM service-instance( service-instance Uses connector, MANY2MANY)
+
+      -(1) IF this CONNECTOR node is deleted, this FROM node is DELETED also
+    required:
+    - resource-instance-id
+    properties:
+      resource-instance-id:
+        type: string
+        description: Unique id of resource instance.
+  connectors:
+    description: |
+      Collection of resource instances used to connect a variety of disparate inventory widgets
+    properties:
+      connector:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/connector"
+  constrained-element-set:
+    description: |
+      This is how we would capture constraints defining allowed sets of elements.
+      ###### Related Nodes
+      - TO model-constraint( constrained-element-set BelongsTo model-constraint, MANY2ONE)(4)
+      - TO model-element( constrained-element-set BelongsTo model-element, MANY2ONE)(4)
+      - FROM element-choice-set( element-choice-set BelongsTo constrained-element-set, MANY2ONE)(1)
+
+      -(1) IF this CONSTRAINED-ELEMENT-SET node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this CONSTRAINED-ELEMENT-SET is DELETED also
+    required:
+    - constrained-element-set-uuid
+    - constraint-type
+    - check-type
+    properties:
+      constrained-element-set-uuid:
+        type: string
+      constraint-type:
+        type: string
+      check-type:
+        type: string
+  constrained-element-sets:
+    properties:
+      constrained-element-set:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/constrained-element-set"
+  ctag-assignment:
+    description: |
+      ###### Related Nodes
+      - TO l3-network( ctag-assignment BelongsTo l3-network, MANY2ONE)(4)
+      - FROM service-instance( service-instance Uses ctag-assignment, ONE2MANY)
+
+      -(4) IF this TO node is deleted, this CTAG-ASSIGNMENT is DELETED also
+    required:
+    - vlan-id-inner
+    properties:
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: id.
+  ctag-assignments:
+    properties:
+      ctag-assignment:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/ctag-assignment"
+  ctag-pool:
+    description: |
+      A collection of C tags (vlan tags) grouped for a specific purpose.
+      ###### Related Nodes
+      - TO complex( ctag-pool BelongsTo complex, MANY2ONE)(4)
+      - TO availability-zone( ctag-pool AppliesTo availability-zone, MANY2MANY)
+      - FROM vpls-pe( vpls-pe Uses ctag-pool, MANY2MANY)
+
+      -(4) IF this TO node is deleted, this CTAG-POOL is DELETED also
+    required:
+    - target-pe
+    - availability-zone-name
+    - ctag-pool-purpose
+    properties:
+      target-pe:
+        type: string
+        description: The Target provider edge router
+      availability-zone-name:
+        type: string
+        description: Name of the availability zone
+      ctag-pool-purpose:
+        type: string
+        description: Describes what the intended purpose of this pool is.
+      ctag-values:
+        type: string
+        description: Comma separated list of ctags
+  ctag-pools:
+    properties:
+      ctag-pool:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/ctag-pool"
+  customer:
+    description: |
+      customer identifiers to provide linkage back to BSS information.
+      ###### Related Nodes
+      - FROM service-subscription( service-subscription BelongsTo customer, MANY2ONE)(1)
+
+      -(1) IF this CUSTOMER node is deleted, this FROM node is DELETED also
+    required:
+    - global-customer-id
+    - subscriber-name
+    - subscriber-type
+    properties:
+      global-customer-id:
+        type: string
+        description: Global customer id used across ECOMP to uniquely identify customer.
+      subscriber-name:
+        type: string
+        description: Subscriber name, an alternate way to retrieve a customer.
+      subscriber-type:
+        type: string
+        description: Subscriber type, a way to provide VID with only the INFRA customers.
+  customers:
+    description: |
+      Collection of customer identifiers to provide linkage back to BSS information.
+    properties:
+      customer:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/customer"
+  cvlan-tag-entry:
+    required:
+    - cvlan-tag
+    properties:
+      cvlan-tag:
+        type: integer
+        format: int64
+        description: See mis-na-virtualization-platform.yang
+  cvlan-tags:
+    properties:
+      cvlan-tag-entry:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/cvlan-tag-entry"
+  dvs-switch:
+    description: |
+      Digital virtual switch metadata, used by SDN-C to configure VCEs.  A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI. 
+      ###### Related Nodes
+      - TO cloud-region( dvs-switch BelongsTo cloud-region, MANY2ONE)
+      - TO availability-zone( dvs-switch AppliesTo availability-zone, MANY2MANY)
+
+    required:
+    - switch-name
+    - vcenter-url
+    properties:
+      switch-name:
+        type: string
+        description: DVS switch name
+      vcenter-url:
+        type: string
+        description: URL used to reach the vcenter
+  dvs-switches:
+    description: |
+      Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+    properties:
+      dvs-switch:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/dvs-switch"
+  edge-prop-names:
+    description: |
+      Internal map to define the properties of an edge and interpret the map EdgeRules
+    properties:
+      edgeLabel:
+        type: string
+      direction:
+        type: string
+      multiplicityRule:
+        type: string
+      isParent:
+        type: boolean
+      usesResource:
+        type: boolean
+      hasDelTarget:
+        type: boolean
+      SVC-INFRA:
+        type: boolean
+      SVC-INFRA-REV:
+        type: boolean
+  edge-tag-query-request:
+    properties:
+      edge-tag:
+        type: string
+      result-detail:
+        type: string
+      start-node-type:
+        type: string
+      start-node-filter:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/start-node-filter"
+      include-node-filter:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/include-node-filter"
+      secondary-filter:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/secondary-filter"
+  edge-tag-query-result:
+    properties:
+      tagged-inventory-item-list:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/tagged-inventory-item-list"
+  element-choice-set:
+    description: |
+      This is how we would capture constraints defining allowed sets of elements.
+      ###### Related Nodes
+      - TO constrained-element-set( element-choice-set BelongsTo constrained-element-set, MANY2ONE)(4)
+      - FROM model-element( model-element BelongsTo element-choice-set, MANY2ONE)(1)
+
+      -(1) IF this ELEMENT-CHOICE-SET node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this ELEMENT-CHOICE-SET is DELETED also
+    required:
+    - element-choice-set-uuid
+    - element-choice-set-name
+    properties:
+      element-choice-set-uuid:
+        type: string
+      element-choice-set-name:
+        type: string
+      cardinality:
+        type: string
+  element-choice-sets:
+    properties:
+      element-choice-set:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/element-choice-set"
+  entitlement:
+    description: |
+      Metadata for entitlement group.
+      ###### Related Nodes
+      - TO generic-vnf( entitlement BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO vce( entitlement BelongsTo vce, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this ENTITLEMENT is DELETED also
+    required:
+    - group-uuid
+    - resource-uuid
+    properties:
+      group-uuid:
+        type: string
+        description: Unique ID for the entitlement group the resource comes from, should be uuid.
+      resource-uuid:
+        type: string
+        description: Unique ID of an entitlement resource. 
+  entitlements:
+    description: |
+      Entitlements, keyed by group-uuid and resource-uuid, related to license management
+    properties:
+      entitlement:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/entitlement"
+  esr-ems:
+    description: |
+      Persist EMS address information used by EMS driver.
+      ###### Related Nodes
+      - FROM esr-system-info( esr-system-info BelongsTo esr-ems, MANY2ONE)(1)
+
+      -(1) IF this ESR-EMS node is deleted, this FROM node is DELETED also
+    required:
+    - ems-id
+    properties:
+      ems-id:
+        type: string
+        description: Unique ID of EMS.
+  esr-ems-list:
+    properties:
+      esr-ems:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/esr-ems"
+  esr-system-info:
+    description: |
+      Persist common address information of external systems.
+      ###### Related Nodes
+      - TO esr-ems( esr-system-info BelongsTo esr-ems, MANY2ONE)(4)
+      - TO esr-vnfm( esr-system-info BelongsTo esr-vnfm, ONE2ONE)(4)
+      - TO esr-thirdparty-sdnc( esr-system-info BelongsTo esr-thirdparty-sdnc, ONE2ONE)(4)
+      - TO cloud-region( esr-system-info BelongsTo cloud-region, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this ESR-SYSTEM-INFO is DELETED also
+    required:
+    - esr-system-info-id
+    - user-name
+    - password
+    - system-type
+    properties:
+      esr-system-info-id:
+        type: string
+        description: Unique ID of esr system info.
+      system-name:
+        type: string
+        description: name of external system.
+      type:
+        type: string
+        description: type of external systems.
+      vendor:
+        type: string
+        description: vendor of external systems.
+      version:
+        type: string
+        description: version of external systems.
+      service-url:
+        type: string
+        description: url used to access external systems.
+      user-name:
+        type: string
+        description: username used to access external systems.
+      password:
+        type: string
+        description: password used to access external systems.
+      system-type:
+        type: string
+        description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+      protocol:
+        type: string
+        description: protocol of third party SDNC, for example netconf/snmp.
+      ssl-cacert:
+        type: string
+        description: ca file content if enabled ssl on auth-url.
+      ssl-insecure:
+        type: boolean
+        description: Whether to verify VIM's certificate.
+      ip-address:
+        type: string
+        description: service IP of ftp server.
+      port:
+        type: string
+        description: service port of ftp server.
+      cloud-domain:
+        type: string
+        description: domain info for authentication.
+      default-tenant:
+        type: string
+        description: default tenant of VIM.
+      passive:
+        type: boolean
+        description: ftp passive mode or not.
+      remote-path:
+        type: string
+        description: resource or performance data file path.
+      system-status:
+        type: string
+        description: the status of external system.
+  esr-system-info-list:
+    description: |
+      Collection of persistent block-level external system auth info.
+    properties:
+      esr-system-info:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/esr-system-info"
+  esr-thirdparty-sdnc:
+    description: |
+      Persist SDNC address information used by ONAP SDNC.
+      ###### Related Nodes
+      - TO pnf( esr-thirdparty-sdnc AppliesTo pnf, ONE2MANY)
+      - FROM esr-system-info( esr-system-info BelongsTo esr-thirdparty-sdnc, ONE2ONE)(1)
+
+      -(1) IF this ESR-THIRDPARTY-SDNC node is deleted, this FROM node is DELETED also
+    required:
+    - thirdparty-sdnc-id
+    properties:
+      thirdparty-sdnc-id:
+        type: string
+        description: Unique ID of SDNC.
+      location:
+        type: string
+        description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+      product-name:
+        type: string
+        description: password used to access SDNC server.
+  esr-thirdparty-sdnc-list:
+    properties:
+      esr-thirdparty-sdnc:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/esr-thirdparty-sdnc"
+  esr-vnfm:
+    description: |
+      Persist VNFM address information used by VF-C.
+      ###### Related Nodes
+      - FROM esr-system-info( esr-system-info BelongsTo esr-vnfm, ONE2ONE)(1)
+
+      -(1) IF this ESR-VNFM node is deleted, this FROM node is DELETED also
+    required:
+    - vnfm-id
+    properties:
+      vnfm-id:
+        type: string
+        description: Unique ID of VNFM.
+      vim-id:
+        type: string
+        description: indecate the VIM to deploy VNF.
+      certificate-url:
+        type: string
+        description: certificate url of VNFM.
+  esr-vnfm-list:
+    properties:
+      esr-vnfm:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/esr-vnfm"
+  evc:
+    description: |
+      evc object is an optional child object of the Configuration object.
+      ###### Related Nodes
+      - TO configuration( evc BelongsTo configuration, ONE2ONE)(4)
+
+      -(4) IF this TO node is deleted, this EVC is DELETED also
+    required:
+    - evc-id
+    properties:
+      evc-id:
+        type: string
+        description: Unique/key field for the evc object
+      forwarding-path-topology:
+        type: string
+        description: Point-to-Point, Multi-Point
+      cir-value:
+        type: string
+        description: Commited Information Rate
+      cir-units:
+        type: string
+        description: CIR units
+      connection-diversity-group-id:
+        type: string
+        description: Diversity Group ID
+      service-hours:
+        type: string
+        description: formerly Performance Group
+      esp-evc-circuit-id:
+        type: string
+        description: EVC Circuit ID of ESP EVC
+      esp-evc-cir-value:
+        type: string
+        description: Committed Information Rate (For ESP)
+      esp-evc-cir-units:
+        type: string
+        description: CIR units (For ESP)
+      esp-itu-code:
+        type: string
+        description: Identifies ESP
+      collector-pop-clli:
+        type: string
+        description: Collector POP CLLI (from the hostname of the access pnf)
+      inter-connect-type-ingress:
+        type: string
+        description: Interconnect type on ingress side of EVC.
+      tagmode-access-ingress:
+        type: string
+        description: tagode for collector side of EVC
+      tagmode-access-egress:
+        type: string
+        description: tagMode for network side of EVC
+  evcs:
+    properties:
+      evc:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/evc"
+  external-system:
+    description: |
+      Namespace for external system.
+    properties:
+      esr-ems-list:
+        type: object
+        $ref: "#/patchDefinitions/esr-ems-list"
+      esr-vnfm-list:
+        type: object
+        $ref: "#/patchDefinitions/esr-vnfm-list"
+      esr-thirdparty-sdnc-list:
+        type: object
+        $ref: "#/patchDefinitions/esr-thirdparty-sdnc-list"
+  extra-properties:
+    description: |
+      Extra properties for inventory item for response list
+    properties:
+      extra-property:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/extra-property"
+  extra-property:
+    properties:
+      property-name:
+        type: string
+      property-value:
+        type: string
+  flavor:
+    description: |
+      Openstack flavor.
+      ###### Related Nodes
+      - TO cloud-region( flavor BelongsTo cloud-region, MANY2ONE)
+      - FROM vserver( vserver Uses flavor, MANY2ONE)
+
+      -FLAVOR cannot be deleted if related to VSERVER
+
+    required:
+    - flavor-id
+    - flavor-name
+    - flavor-selflink
+    properties:
+      flavor-id:
+        type: string
+        description: Flavor id, expected to be unique across cloud-region.
+      flavor-name:
+        type: string
+        description: Flavor name
+      flavor-vcpus:
+        type: integer
+        format: int32
+        description: Number of CPUs
+      flavor-ram:
+        type: integer
+        format: int32
+        description: Amount of memory
+      flavor-disk:
+        type: integer
+        format: int32
+        description: Disk space
+      flavor-ephemeral:
+        type: integer
+        format: int32
+        description: Amount of ephemeral disk space
+      flavor-swap:
+        type: string
+        description: amount of swap space allocation
+      flavor-is-public:
+        type: boolean
+        description: whether flavor is available to all users or private to the tenant it was created in.
+      flavor-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      flavor-disabled:
+        type: boolean
+        description: Boolean as to whether this flavor is no longer enabled
+  flavors:
+    description: |
+      Collection of openstack flavors.
+    properties:
+      flavor:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/flavor"
+  forwarder:
+    description: |
+      Entity describing a sequenced segment of forwarding path
+      ###### Related Nodes
+      - TO forwarding-path( forwarder BelongsTo forwarding-path, MANY2ONE)(4)
+      - TO l-interface( forwarder ForwardsTo l-interface, MANY2ONE)
+      - TO configuration( forwarder Uses configuration, ONE2ONE)(2)
+      - TO lag-interface( forwarder ForwardsTo lag-interface, MANY2ONE)
+      - TO p-interface( forwarder ForwardsTo p-interface, MANY2ONE)
+
+      -(2) IF this FORWARDER node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this FORWARDER is DELETED also
+    required:
+    - sequence
+    properties:
+      sequence:
+        type: integer
+        format: int32
+        description: Unique ID of this segmentation
+      forwarder-role:
+        type: string
+        description: ingress, intermediate, egress
+  forwarder-evc:
+    description: |
+      forwarder object is an optional child object of the Configuration object.
+      ###### Related Nodes
+      - TO configuration( forwarder-evc BelongsTo configuration, ONE2ONE)(4)
+
+      -(4) IF this TO node is deleted, this FORWARDER-EVC is DELETED also
+    required:
+    - forwarder-evc-id
+    properties:
+      forwarder-evc-id:
+        type: string
+        description: Key for forwarder-evc object
+      circuit-id:
+        type: string
+        description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+      ivlan:
+        type: string
+        description: Internal VLAN.
+      svlan:
+        type: string
+        description: SVLAN value for ingress of egress forwarder.
+      cvlan:
+        type: string
+        description: CVLAN value for ingress of egress forwarder.
+  forwarder-evcs:
+    properties:
+      forwarder-evc:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/forwarder-evc"
+  forwarders:
+    properties:
+      forwarder:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/forwarder"
+  forwarding-path:
+    description: |
+      Entity that describes the sequenced forwarding path between interfaces of services or resources
+      ###### Related Nodes
+      - TO service-instance( forwarding-path AppliesTo service-instance, MANY2ONE)(4)
+      - TO configuration( forwarding-path Uses configuration, ONE2ONE)(2)
+      - FROM forwarder( forwarder BelongsTo forwarding-path, MANY2ONE)(1)
+
+      -(1) IF this FORWARDING-PATH node is deleted, this FROM node is DELETED also
+      -(2) IF this FORWARDING-PATH node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this FORWARDING-PATH is DELETED also
+    required:
+    - forwarding-path-id
+    - forwarding-path-name
+    properties:
+      forwarding-path-id:
+        type: string
+        description: Unique ID of this FP
+      forwarding-path-name:
+        type: string
+        description: Name of the FP
+  forwarding-paths:
+    properties:
+      forwarding-path:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/forwarding-path"
+  generic-vnf:
+    description: |
+      General purpose VNF
+      ###### Related Nodes
+      - TO availability-zone( generic-vnf Uses availability-zone, MANY2MANY)
+      - TO instance-group( generic-vnf MemberOf instance-group, MANY2MANY)
+      - TO ipsec-configuration( generic-vnf Uses ipsec-configuration, MANY2ONE)
+      - TO l3-network( generic-vnf Uses l3-network, MANY2MANY)
+      - TO license-key-resource( generic-vnf Uses license-key-resource, MANY2MANY)
+      - TO pserver( generic-vnf HostedOn pserver, MANY2MANY)
+      - TO vnf-image( generic-vnf Uses vnf-image, MANY2ONE)
+      - TO volume-group( generic-vnf DependsOn volume-group, ONE2MANY)
+      - TO vserver( generic-vnf HostedOn vserver, ONE2MANY)
+      - TO virtual-data-center( generic-vnf LocatedIn virtual-data-center, MANY2MANY)
+      - FROM allotted-resource( allotted-resource PartOf generic-vnf, MANY2MANY)
+      - FROM entitlement( entitlement BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM vnfc( vnfc BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM lag-interface( lag-interface BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM license( license BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM l-interface( l-interface BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM network-profile( network-profile AppliesTo generic-vnf, MANY2MANY)
+      - FROM service-instance( service-instance ComposedOf generic-vnf, ONE2MANY)
+      - FROM site-pair-set( site-pair-set AppliesTo generic-vnf, MANY2MANY)
+      - FROM vf-module( vf-module BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM logical-link( logical-link BridgedTo generic-vnf, MANY2MANY)
+
+      -(1) IF this GENERIC-VNF node is deleted, this FROM node is DELETED also
+    required:
+    - vnf-id
+    - vnf-name
+    - vnf-type
+    - in-maint
+    - is-closed-loop-disabled
+    properties:
+      vnf-id:
+        type: string
+        description: Unique id of VNF.  This is unique across the graph.
+      vnf-name:
+        type: string
+        description: Name of VNF.
+      vnf-name2:
+        type: string
+        description: Alternate name of VNF.
+      vnf-type:
+        type: string
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      service-id:
+        type: string
+        description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
+      regional-resource-zone:
+        type: string
+        description: Regional way of organizing pservers, source of truth should define values
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational.  Valid values are in-service-path and out-of-service-path.
+      license-key:
+        type: string
+        description: OBSOLETE -  do not use
+      equipment-role:
+        type: string
+        description: Client should send valid enumerated value
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, used by MSO.
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance, managed by MSO
+      mso-catalog-key:
+        type: string
+        description: Corresponds to the SDN-C catalog id used to configure this VCE
+      management-option:
+        type: string
+        description: identifier of managed by company or customer
+      ipv4-oam-address:
+        type: string
+        description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+      ipv4-loopback0-address:
+        type: string
+        description: v4 Loopback0 address
+      nm-lan-v6-address:
+        type: string
+        description: v6 Loopback address
+      management-v6-address:
+        type: string
+        description: v6 management address
+      vcpu:
+        type: integer
+        format: int64
+        description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vcpu-units:
+        type: string
+        description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vmemory:
+        type: integer
+        format: int64
+        description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vmemory-units:
+        type: string
+        description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vdisk:
+        type: integer
+        format: int64
+        description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vdisk-units:
+        type: string
+        description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only in some usecases
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true). This field (in conjunction with prov-status) is used to suppress alarms and vSCL on VNFs/VMs.
+      is-closed-loop-disabled:
+        type: boolean
+        description: used to indicate whether closed loop function is enabled on this node
+  generic-vnfs:
+    description: |
+      Collection of VNFs
+    properties:
+      generic-vnf:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/generic-vnf"
+  group-assignment:
+    description: |
+      Openstack group-assignment used to store exclusivity groups (EG).
+      ###### Related Nodes
+      - TO cloud-region( group-assignment BelongsTo cloud-region, MANY2ONE)
+      - FROM pserver( pserver MemberOf group-assignment, MANY2ONE)
+      - FROM tenant( tenant MemberOf group-assignment, MANY2MANY)
+
+    required:
+    - group-id
+    - group-type
+    - group-name
+    properties:
+      group-id:
+        type: string
+        description: Group id, expected to be unique across cloud-region.
+      group-type:
+        type: string
+        description: Group type - the type of group this instance refers to
+      group-name:
+        type: string
+        description: Group name - name assigned to the group
+      group-description:
+        type: string
+        description: Group description - description of the group
+  group-assignments:
+    description: |
+      Collection of openstack group assignments
+    properties:
+      group-assignment:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/group-assignment"
+  host-route:
+    description: |
+      ###### Related Nodes
+      - TO subnet( host-route BelongsTo subnet, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this HOST-ROUTE is DELETED also
+    required:
+    - host-route-id
+    - route-prefix
+    - next-hop
+    properties:
+      host-route-id:
+        type: string
+        description: host-route id
+      route-prefix:
+        type: string
+        description: subnet prefix
+      next-hop:
+        type: string
+        description: Could be ip-address, hostname, or service-instance
+      next-hop-type:
+        type: string
+        description: Should be ip-address, hostname, or service-instance to match next-hop
+  host-routes:
+    properties:
+      host-route:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/host-route"
+  hpa-capabilities:
+    description: |
+      Collection of HPA Capabilities
+    properties:
+      hpa-capability:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/hpa-capability"
+  hpa-capability:
+    description: |
+      Represents a HPA capability
+      ###### Related Nodes
+      - TO flavor( hpa-capability BelongsTo flavor, MANY2ONE)
+      - TO cloud-region( hpa-capability BelongsTo cloud-region, MANY2ONE)
+      - FROM hpa-feature-attributes( hpa-feature-attributes BelongsTo hpa-capability, MANY2ONE)(1)
+
+      -(1) IF this HPA-CAPABILITY node is deleted, this FROM node is DELETED also
+    required:
+    - hpa-capability-id
+    - hpa-feature
+    properties:
+      hpa-capability-id:
+        type: string
+        description: UUID to uniquely identify a HPA capability
+      hpa-feature:
+        type: string
+        description: Name of the HPACapability
+      hpa-version:
+        type: string
+        description: HPA schema version
+      architecture:
+        type: string
+        description: Hardware architecture
+  hpa-feature-attributes:
+    description: |
+      HPA Capability Feature attributes
+      ###### Related Nodes
+      - TO hpa-capability( hpa-feature-attributes BelongsTo hpa-capability, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this HPA-FEATURE-ATTRIBUTES is DELETED also
+    required:
+    - hpa-attribute-key
+    properties:
+      hpa-attribute-key:
+        type: string
+        description: name of the specific HPA attribute
+      hpa-attribute-value:
+        type: string
+        description: JSON string specifying the value, unit and type of the specific HPA attribute
+  image:
+    description: |
+      Openstack image.
+      ###### Related Nodes
+      - TO cloud-region( image BelongsTo cloud-region, MANY2ONE)
+      - FROM metadatum( metadatum BelongsTo image, MANY2ONE)(1)
+      - FROM vserver( vserver Uses image, MANY2ONE)
+
+      -(1) IF this IMAGE node is deleted, this FROM node is DELETED also
+      -IMAGE cannot be deleted if related to VSERVER
+
+    required:
+    - image-id
+    - image-name
+    - image-os-distro
+    - image-os-version
+    - image-selflink
+    properties:
+      image-id:
+        type: string
+        description: Image id, expected to be unique across cloud region
+      image-name:
+        type: string
+        description: Image name
+      image-architecture:
+        type: string
+        description: Operating system architecture.
+      image-os-distro:
+        type: string
+        description: The common name of the operating system distribution in lowercase
+      image-os-version:
+        type: string
+        description: The operating system version as specified by the distributor.
+      application:
+        type: string
+        description: The application that the image instantiates.
+      application-vendor:
+        type: string
+        description: The vendor of the application.
+      application-version:
+        type: string
+        description: The version of the application.
+      image-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+  images:
+    description: |
+      Collectio of Openstack images.
+    properties:
+      image:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/image"
+  include-node-filter:
+    properties:
+      include-node-type:
+        type: string
+  instance-filter:
+    description: |
+      InstanceFilter for performing a named-query or model query
+  instance-filters:
+    description: |
+      InstanceFilters for performing a named-query or model query
+    properties:
+      instance-filter:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/instance-filter"
+  instance-group:
+    description: |
+      General mechanism for grouping instances
+      ###### Related Nodes
+      - TO model( instance-group Targets model, MANY2MANY)
+      - FROM allotted-resource( allotted-resource MemberOf instance-group, MANY2MANY)
+      - FROM generic-vnf( generic-vnf MemberOf instance-group, MANY2MANY)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list MemberOf instance-group, MANY2MANY)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list MemberOf instance-group, MANY2MANY)
+      - FROM l-interface( l-interface MemberOf instance-group, MANY2MANY)
+      - FROM pnf( pnf MemberOf instance-group, MANY2MANY)
+      - FROM service-instance( service-instance MemberOf instance-group, MANY2MANY)
+
+    required:
+    - id
+    - description
+    - type
+    properties:
+      id:
+        type: string
+        description: Instance Group ID, UUID assigned to this instance.
+      description:
+        type: string
+        description: Descriptive text to help identify the usage of this instance-group
+      type:
+        type: string
+        description: Only valid value today is lower case ha for high availability
+      sub-type:
+        type: string
+        description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+  instance-groups:
+    description: |
+      Collection of openstack route table references
+    properties:
+      instance-group:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/instance-group"
+  inventory:
+    properties:
+      search:
+        type: object
+        $ref: "#/patchDefinitions/search"
+      actions:
+        type: object
+        $ref: "#/patchDefinitions/actions"
+      cloud-infrastructure:
+        type: object
+        $ref: "#/patchDefinitions/cloud-infrastructure"
+      business:
+        type: object
+        $ref: "#/patchDefinitions/business"
+      service-design-and-creation:
+        type: object
+        $ref: "#/patchDefinitions/service-design-and-creation"
+      network:
+        type: object
+        $ref: "#/patchDefinitions/network"
+      nodes:
+        type: object
+        $ref: "#/patchDefinitions/nodes"
+  inventory-item:
+    properties:
+      inventory-item-type:
+        type: string
+      inventory-item-link:
+        type: string
+      inventory-item-data:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/inventory-item-data"
+      tagged-inventory-item-list:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/tagged-inventory-item-list"
+  inventory-item-data:
+    properties:
+      property-name:
+        type: string
+      property-value:
+        type: string
+  inventory-response-item:
+    description: |
+      Inventory item for response list
+    properties:
+      model-name:
+        type: string
+      extra-properties:
+        type: object
+        $ref: "#/patchDefinitions/extra-properties"
+      inventory-response-items:
+        type: object
+        $ref: "#/patchDefinitions/inventory-response-items"
+  inventory-response-items:
+    description: |
+      Container for inventory items in response list
+    properties:
+      inventory-response-item:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/inventory-response-item"
+  ipsec-configuration:
+    description: |
+      IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+      ###### Related Nodes
+      - FROM generic-vnf( generic-vnf Uses ipsec-configuration, MANY2ONE)
+      - FROM vig-server( vig-server BelongsTo ipsec-configuration, MANY2ONE)(1)
+
+      -(1) IF this IPSEC-CONFIGURATION node is deleted, this FROM node is DELETED also
+    required:
+    - ipsec-configuration-id
+    properties:
+      ipsec-configuration-id:
+        type: string
+        description: UUID of this configuration
+      requested-vig-address-type:
+        type: string
+        description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+      requested-encryption-strength:
+        type: string
+        description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+      requested-dmz-type:
+        type: string
+        description: can offer a shared DMZ or a DMZ specific to a customer
+      shared-dmz-network-address:
+        type: string
+        description: Network address of shared DMZ
+      requested-customer-name:
+        type: string
+        description: If the DMZ is a custom DMZ, this field will indicate the customer information
+      ike-version:
+        type: string
+        description: can be 1 or 2
+      ikev1-authentication:
+        type: string
+        description: Contains values like md5, sha1, sha256, sha384
+      ikev1-encryption:
+        type: string
+        description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+      ikev1-dh-group:
+        type: string
+        description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+      ikev1-am-group-id:
+        type: string
+        description: Group name defined in VIG for clients using aggressive mode
+      ikev1-am-password:
+        type: string
+        description: pre-shared key for the above group name 
+      ikev1-sa-lifetime:
+        type: string
+        description: Lifetime for IKEv1 SA
+      ipsec-authentication:
+        type: string
+        description: md5, sha1, sha256, sha384
+      ipsec-encryption:
+        type: string
+        description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+      ipsec-sa-lifetime:
+        type: string
+        description: Life time for IPSec SA
+      ipsec-pfs:
+        type: string
+        description: enable PFS or not
+      xauth-userid:
+        type: string
+        description: user ID for xAuth, sm-user, ,nmteHostName
+      xauth-user-password:
+        type: string
+        description: Encrypted using the Juniper $9$ algorithm
+      dpd-interval:
+        type: string
+        description: The time between DPD probe
+      dpd-frequency:
+        type: string
+        description: Maximum number of DPD before claiming the tunnel is down
+  ipsec-configurations:
+    properties:
+      ipsec-configuration:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/ipsec-configuration"
+  key-data:
+    properties:
+      key-name:
+        type: string
+      key-value:
+        type: string
+  l-interface:
+    description: |
+      Logical interfaces, e.g., a vnic.
+      ###### Related Nodes
+      - TO generic-vnf( l-interface BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO lag-interface( l-interface BelongsTo lag-interface, MANY2ONE)(4)
+      - TO instance-group( l-interface MemberOf instance-group, MANY2MANY)
+      - TO l-interface( l-interface BelongsTo l-interface, MANY2ONE)(4)
+      - TO logical-link( l-interface LinksTo logical-link, MANY2MANY)(2)
+      - TO newvce( l-interface BelongsTo newvce, MANY2ONE)(4)
+      - TO p-interface( l-interface BindsTo p-interface, MANY2ONE)(4)
+      - TO vserver( l-interface BindsTo vserver, MANY2ONE)(4)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list BelongsTo l-interface, MANY2ONE)(1)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list BelongsTo l-interface, MANY2ONE)(1)
+      - FROM sriov-vf( sriov-vf BelongsTo l-interface, ONE2ONE)(1)
+      - FROM vlan( vlan LinksTo l-interface, MANY2ONE)(1)
+      - FROM l-interface( l-interface BelongsTo l-interface, MANY2ONE)(4)
+
+      -(1) IF this L-INTERFACE node is deleted, this FROM node is DELETED also
+      -(2) IF this L-INTERFACE node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this L-INTERFACE is DELETED also
+    required:
+    - interface-name
+    - is-port-mirrored
+    - in-maint
+    properties:
+      interface-name:
+        type: string
+        description: Name given to the interface
+      interface-role:
+        type: string
+        description: E.g., CUSTOMER, UPLINK, etc.
+      v6-wan-link-ip:
+        type: string
+        description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+      selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      interface-id:
+        type: string
+        description: ID of interface
+      macaddr:
+        type: string
+        description: MAC address for the interface
+      network-name:
+        type: string
+        description: Name of the network
+      management-option:
+        type: string
+        description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+      interface-description:
+        type: string
+        description: Human friendly text regarding this interface.
+      is-port-mirrored:
+        type: boolean
+        description: boolean indicatating whether or not port is a mirrored.
+  l-interfaces:
+    description: |
+      Collection of logical interfaces.
+    properties:
+      l-interface:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/l-interface"
+  l3-interface-ipv4-address-list:
+    description: |
+      IPv4 Address Range
+      ###### Related Nodes
+      - TO instance-group( l3-interface-ipv4-address-list MemberOf instance-group, MANY2MANY)
+      - TO l3-network( l3-interface-ipv4-address-list MemberOf l3-network, MANY2MANY)
+      - TO subnet( l3-interface-ipv4-address-list MemberOf subnet, MANY2MANY)
+      - TO l-interface( l3-interface-ipv4-address-list BelongsTo l-interface, MANY2ONE)(4)
+      - TO vlan( l3-interface-ipv4-address-list BelongsTo vlan, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this L3-INTERFACE-IPV4-ADDRESS-LIST is DELETED also
+    required:
+    - l3-interface-ipv4-address
+    properties:
+      l3-interface-ipv4-address:
+        type: string
+        description: IP address
+      l3-interface-ipv4-prefix-length:
+        type: integer
+        format: int64
+        description: Prefix length, 32 for single address
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      is-floating:
+        type: boolean
+        description: Indicator of fixed or floating address
+  l3-interface-ipv6-address-list:
+    description: |
+      IPv6 Address Range
+      ###### Related Nodes
+      - TO instance-group( l3-interface-ipv6-address-list MemberOf instance-group, MANY2MANY)
+      - TO l3-network( l3-interface-ipv6-address-list MemberOf l3-network, MANY2MANY)
+      - TO subnet( l3-interface-ipv6-address-list MemberOf subnet, MANY2MANY)
+      - TO l-interface( l3-interface-ipv6-address-list BelongsTo l-interface, MANY2ONE)(4)
+      - TO vlan( l3-interface-ipv6-address-list BelongsTo vlan, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this L3-INTERFACE-IPV6-ADDRESS-LIST is DELETED also
+    required:
+    - l3-interface-ipv6-address
+    properties:
+      l3-interface-ipv6-address:
+        type: string
+        description: IP address
+      l3-interface-ipv6-prefix-length:
+        type: integer
+        format: int64
+        description: Prefix length, 128 for single address
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      is-floating:
+        type: boolean
+        description: Indicator of fixed or floating address
+  l3-network:
+    description: |
+      Generic network definition
+      ###### Related Nodes
+      - TO network-policy( l3-network Uses network-policy, MANY2MANY)
+      - TO route-table-reference( l3-network Uses route-table-reference, MANY2MANY)
+      - TO vpn-binding( l3-network Uses vpn-binding, MANY2MANY)
+      - FROM allotted-resource( allotted-resource PartOf l3-network, MANY2MANY)
+      - FROM cloud-region( cloud-region Uses l3-network, MANY2MANY)
+      - FROM complex( complex Uses l3-network, MANY2MANY)
+      - FROM generic-vnf( generic-vnf Uses l3-network, MANY2MANY)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list MemberOf l3-network, MANY2MANY)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list MemberOf l3-network, MANY2MANY)
+      - FROM ctag-assignment( ctag-assignment BelongsTo l3-network, MANY2ONE)(1)
+      - FROM segmentation-assignment( segmentation-assignment BelongsTo l3-network, MANY2ONE)(1)
+      - FROM service-instance( service-instance ComposedOf l3-network, ONE2MANY)
+      - FROM subnet( subnet BelongsTo l3-network, MANY2ONE)(1)
+      - FROM tenant( tenant Uses l3-network, MANY2MANY)
+      - FROM vf-module( vf-module DependsOn l3-network, MANY2MANY)
+
+      -(1) IF this L3-NETWORK node is deleted, this FROM node is DELETED also
+    required:
+    - network-id
+    - network-name
+    - is-bound-to-vpn
+    - is-provider-network
+    - is-shared-network
+    - is-external-network
+    properties:
+      network-id:
+        type: string
+        description: Network ID, should be uuid. Unique across A&AI.
+      network-name:
+        type: string
+        description: Name of the network, governed by some naming convention..
+      network-type:
+        type: string
+        description: Type of the network - who defines these values?
+      network-role:
+        type: string
+        description: Role the network plans - who defines these values?
+      network-technology:
+        type: string
+        description: Network technology - who defines these values?
+      neutron-network-id:
+        type: string
+        description: Neutron network id of this Interface
+      is-bound-to-vpn:
+        type: boolean
+        description: Set to true if bound to VPN
+      service-id:
+        type: string
+        description: Unique identifier of service from ASDC.  Does not strictly map to ASDC services.  SOON TO BE DEPRECATED
+      network-role-instance:
+        type: integer
+        format: int64
+        description: network role instance
+  l3-networks:
+    properties:
+      l3-network:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/l3-network"
+  lag-interface:
+    description: |
+      Link aggregate interface
+      ###### Related Nodes
+      - TO generic-vnf( lag-interface BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO lag-link( lag-interface LinksTo lag-link, MANY2MANY)(2)
+      - TO logical-link( lag-interface Uses logical-link, MANY2MANY)(2)
+      - TO p-interface( lag-interface Uses p-interface, MANY2MANY)
+      - TO pnf( lag-interface BindsTo pnf, MANY2ONE)(4)
+      - TO pserver( lag-interface BindsTo pserver, MANY2ONE)(4)
+      - TO vpls-pe( lag-interface BindsTo vpls-pe, MANY2ONE)(4)
+      - FROM l-interface( l-interface BelongsTo lag-interface, MANY2ONE)(1)
+
+      -(1) IF this LAG-INTERFACE node is deleted, this FROM node is DELETED also
+      -(2) IF this LAG-INTERFACE node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this LAG-INTERFACE is DELETED also
+    required:
+    - interface-name
+    - in-maint
+    properties:
+      interface-name:
+        type: string
+        description: Name that identifies the link aggregate interface
+      interface-description:
+        type: string
+        description: Human friendly text regarding this interface.
+  lag-interfaces:
+    description: |
+      Collection of link aggregate interfaces.
+    properties:
+      lag-interface:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/lag-interface"
+  lag-link:
+    description: |
+      LAG links can connect lag-interfaces
+      ###### Related Nodes
+      - FROM lag-interface( lag-interface LinksTo lag-link, MANY2MANY)(3)
+      - FROM logical-link( logical-link Uses lag-link, MANY2MANY)
+
+      -(3) IF this FROM node is deleted, this LAG-LINK is DELETED also
+    required:
+    - link-name
+    properties:
+      link-name:
+        type: string
+        description: Alphabetical concatenation of lag-interface names
+  lag-links:
+    description: |
+      Collection of link aggregation connections
+    properties:
+      lag-link:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/lag-link"
+  license:
+    description: |
+      Metadata for license group.
+      ###### Related Nodes
+      - TO generic-vnf( license BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO vce( license BelongsTo vce, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this LICENSE is DELETED also
+    required:
+    - group-uuid
+    - resource-uuid
+    properties:
+      group-uuid:
+        type: string
+        description: Unique ID for the license group the resource belongs to, should be uuid.
+      resource-uuid:
+        type: string
+        description: Unique ID of a license resource. 
+  licenses:
+    description: |
+      Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+    properties:
+      license:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/license"
+  line-of-business:
+    description: |
+      describes a line-of-business
+      ###### Related Nodes
+      - TO generic-vnf( line-of-business Uses generic-vnf, MANY2MANY)
+
+    required:
+    - line-of-business-name
+    properties:
+      line-of-business-name:
+        type: string
+        description: Name of the line-of-business (product)
+  lines-of-business:
+    description: |
+      Collection of lines-of-business
+    properties:
+      line-of-business:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/line-of-business"
+  logical-link:
+    description: |
+      Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+      ###### Related Nodes
+      - TO cloud-region( logical-link LocatedIn cloud-region, MANY2MANY)
+      - TO generic-vnf( logical-link BridgedTo generic-vnf, MANY2MANY)
+      - TO lag-link( logical-link Uses lag-link, MANY2MANY)
+      - TO logical-link( logical-link Uses logical-link, MANY2MANY)
+      - TO pnf( logical-link BridgedTo pnf, MANY2MANY)
+      - TO pserver( logical-link BridgedTo pserver, MANY2MANY)
+      - TO vpn-binding( logical-link Uses vpn-binding, MANY2MANY)
+      - TO virtual-data-center( logical-link LocatedIn virtual-data-center, MANY2MANY)
+      - FROM lag-interface( lag-interface Uses logical-link, MANY2MANY)(3)
+      - FROM l-interface( l-interface LinksTo logical-link, MANY2MANY)(3)
+      - FROM p-interface( p-interface LinksTo logical-link, MANY2ONE)
+      - FROM service-instance( service-instance Uses logical-link, ONE2MANY)(3)
+      - FROM vlan( vlan Uses logical-link, MANY2MANY)(3)
+      - FROM logical-link( logical-link Uses logical-link, MANY2MANY)
+
+      -(3) IF this FROM node is deleted, this LOGICAL-LINK is DELETED also
+    required:
+    - link-name
+    - link-type
+    properties:
+      link-name:
+        type: string
+        description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+      link-type:
+        type: string
+        description: Type of logical link, e.g., evc
+      speed-value:
+        type: string
+        description: Captures the numeric part of the speed
+      speed-units:
+        type: string
+        description: Captures the units corresponding to the speed
+      ip-version:
+        type: string
+        description: v4, v6, or ds for dual stack
+      routing-protocol:
+        type: string
+        description: For example, static or BGP
+  logical-links:
+    description: |
+      Collection of logical connections
+    properties:
+      logical-link:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/logical-link"
+  metadata:
+    description: |
+      Collection of metadatum (key/value pairs)
+    properties:
+      metadatum:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/metadatum"
+  metadatum:
+    description: |
+      Key/value pairs
+      ###### Related Nodes
+      - TO connector( metadatum BelongsTo connector, MANY2ONE)(4)
+      - TO image( metadatum BelongsTo image, MANY2ONE)(4)
+      - TO service-instance( metadatum BelongsTo service-instance, MANY2ONE)(4)
+      - TO model-ver( metadatum BelongsTo model-ver, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this METADATUM is DELETED also
+    required:
+    - metaname
+    - metaval
+    properties:
+      metaname:
+        type: string
+      metaval:
+        type: string
+  model:
+    description: |
+      Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
+      ###### Related Nodes
+      - TO model( model-ver BelongsTo model, MANY2ONE)(1)
+      - FROM instance-group( instance-group Targets model, MANY2MANY)
+      - FROM model-ver( model-ver BelongsTo model, MANY2ONE)(1)
+      - FROM named-query( named-query AppliesTo model, ONE2MANY)
+      - FROM named-query-element( named-query-element IsA model, MANY2ONE)
+
+      -(1) IF this MODEL node is deleted, this FROM node is DELETED also
+      -MODEL cannot be deleted if related to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT
+
+    required:
+    - model-invariant-id
+    - model-type
+    properties:
+      model-invariant-id:
+        type: string
+        description: Unique identifier corresponding to the main definition of a model in ASDC
+      model-type:
+        type: string
+        description: Type of the model, e.g., service, resource, widget, etc.
+  model-and-named-query-search:
+    description: |
+      ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+    properties:
+      query-parameters:
+        type: object
+        $ref: "#/patchDefinitions/query-parameters"
+      instance-filters:
+        type: object
+        $ref: "#/patchDefinitions/instance-filters"
+      secondary-filts:
+        type: object
+        $ref: "#/patchDefinitions/secondary-filts"
+      top-node-type:
+        type: string
+      secondary-filter-cut-point:
+        type: string
+  model-constraint:
+    description: |
+      This is how we would capture constraints defining allowed sets of elements.
+      ###### Related Nodes
+      - TO model-element( model-constraint BelongsTo model-element, MANY2ONE)(4)
+      - FROM constrained-element-set( constrained-element-set BelongsTo model-constraint, MANY2ONE)(1)
+
+      -(1) IF this MODEL-CONSTRAINT node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this MODEL-CONSTRAINT is DELETED also
+    required:
+    - model-constraint-uuid
+    - constrained-element-set-uuid-to-replace
+    properties:
+      model-constraint-uuid:
+        type: string
+      constrained-element-set-uuid-to-replace:
+        type: string
+      constrained-element-sets:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/constrained-element-set"
+  model-constraints:
+    properties:
+      model-constraint:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/model-constraint"
+  model-element:
+    description: |
+      Defines how other models combine to make up a higher-level model.
+      ###### Related Nodes
+      - TO element-choice-set( model-element BelongsTo element-choice-set, MANY2ONE)(4)
+      - TO model-element( model-element BelongsTo model-element, MANY2ONE)(4)
+      - TO model-ver( model-element IsA model-ver, MANY2ONE)
+      - TO model-ver( model-element BelongsTo model-ver, MANY2ONE)(4)
+      - FROM constrained-element-set( constrained-element-set BelongsTo model-element, MANY2ONE)(1)
+      - FROM model-constraint( model-constraint BelongsTo model-element, MANY2ONE)(1)
+      - FROM model-element( model-element BelongsTo model-element, MANY2ONE)(4)
+
+      -(1) IF this MODEL-ELEMENT node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this MODEL-ELEMENT is DELETED also
+    required:
+    - model-element-uuid
+    - new-data-del-flag
+    - cardinality
+    properties:
+      model-element-uuid:
+        type: string
+      new-data-del-flag:
+        type: string
+        description: Indicates whether this element was created as part of instantiation from this model
+      cardinality:
+        type: string
+        description: How many of this type of element are required/allowed
+      linkage-points:
+        type: string
+  model-elements:
+    properties:
+      model-element:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/model-element"
+  model-ver:
+    description: |
+      Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+      ###### Related Nodes
+      - TO model( model-ver BelongsTo model, MANY2ONE)(4)
+      - FROM model-element( model-element IsA model-ver, MANY2ONE)
+      - FROM model-element( model-element BelongsTo model-ver, MANY2ONE)(1)
+      - FROM metadatum( metadatum BelongsTo model-ver, MANY2ONE)(1)
+
+      -(1) IF this MODEL-VER node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this MODEL-VER is DELETED also
+      -MODEL-VER cannot be deleted if related to MODEL-ELEMENT
+
+    required:
+    - model-version-id
+    - model-name
+    - model-version
+    properties:
+      model-version-id:
+        type: string
+        description: Unique identifier corresponding to one version of a model in ASDC
+      model-name:
+        type: string
+        description: Name of the model, which can change from version to version.
+      model-version:
+        type: string
+        description: Version
+      model-description:
+        type: string
+        description: Description
+  model-vers:
+    properties:
+      model-ver:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/model-ver"
+  models:
+    description: |
+      Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+    properties:
+      model:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/model"
+  multicast-configuration:
+    description: |
+      ###### Related Nodes
+      - FROM vlan( vlan Uses multicast-configuration, MANY2MANY)
+
+    required:
+    - multicast-configuration-id
+    - multicast-protocol
+    - rp-type
+    properties:
+      multicast-configuration-id:
+        type: string
+        description: Unique id of multicast configuration.
+      multicast-protocol:
+        type: string
+        description: protocol of multicast configuration
+      rp-type:
+        type: string
+        description: rp type of multicast configuration
+  multicast-configurations:
+    description: |
+      multicast configuration of generic-vnf ip-address
+    properties:
+      multicast-configuration:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/multicast-configuration"
+  named-queries:
+    properties:
+      named-query:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/named-query"
+  named-query:
+    description: |
+      TBD
+      ###### Related Nodes
+      - TO named-query( named-query-element BelongsTo named-query, ONE2ONE)(1)
+      - TO model( named-query AppliesTo model, ONE2MANY)
+      - FROM named-query-element( named-query-element BelongsTo named-query, ONE2ONE)(1)
+
+      -(1) IF this NAMED-QUERY node is deleted, this FROM node is DELETED also
+    required:
+    - named-query-uuid
+    - named-query-name
+    - named-query-version
+    properties:
+      named-query-uuid:
+        type: string
+      named-query-name:
+        type: string
+      named-query-version:
+        type: string
+      required-input-param:
+        type: string
+      description:
+        type: string
+  named-query-element:
+    description: |
+      TBD
+      ###### Related Nodes
+      - TO named-query( named-query-element BelongsTo named-query, ONE2ONE)(4)
+      - TO model( named-query-element IsA model, MANY2ONE)
+      - TO named-query-element( named-query-element BelongsTo named-query-element, MANY2ONE)(4)
+      - FROM property-constraint( property-constraint BelongsTo named-query-element, MANY2ONE)(1)
+      - FROM related-lookup( related-lookup BelongsTo named-query-element, MANY2ONE)(1)
+      - FROM named-query-element( named-query-element BelongsTo named-query-element, MANY2ONE)(4)
+
+      -(1) IF this NAMED-QUERY-ELEMENT node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this NAMED-QUERY-ELEMENT is DELETED also
+    required:
+    - named-query-element-uuid
+    properties:
+      named-query-element-uuid:
+        type: string
+      property-collect-list:
+        type: string
+  named-query-elements:
+    properties:
+      named-query-element:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/named-query-element"
+  network:
+    description: |
+      Namespace for network inventory resources.
+    properties:
+      logical-links:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/logical-link"
+      site-pair-sets:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/site-pair-set"
+      vpn-bindings:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/vpn-binding"
+      vpls-pes:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/vpls-pe"
+      multicast-configurations:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/multicast-configuration"
+      vces:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/vce"
+      vnfcs:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/vnfc"
+      l3-networks:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/l3-network"
+      network-policies:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/network-policy"
+      generic-vnfs:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/generic-vnf"
+      lag-links:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/lag-link"
+      newvces:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/newvce"
+      pnfs:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/pnf"
+      physical-links:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/physical-link"
+      ipsec-configurations:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/ipsec-configuration"
+      route-table-references:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/route-table-reference"
+      instance-groups:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/instance-group"
+      zones:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/zone"
+  network-policies:
+    properties:
+      network-policy:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/network-policy"
+  network-policy:
+    description: |
+      ###### Related Nodes
+      - FROM allotted-resource( allotted-resource Uses network-policy, ONE2ONE)
+      - FROM l3-network( l3-network Uses network-policy, MANY2MANY)
+
+    required:
+    - network-policy-id
+    properties:
+      network-policy-id:
+        type: string
+        description: UUID representing unique key to this instance
+      network-policy-fqdn:
+        type: string
+        description: Contrail FQDN for the policy
+      heat-stack-id:
+        type: string
+        description: ID for the openStack Heat instance
+  network-profile:
+    description: |
+      Network profile populated by SDN-GP for SNMP
+      ###### Related Nodes
+      - TO generic-vnf( network-profile AppliesTo generic-vnf, MANY2MANY)
+
+    required:
+    - nm-profile-name
+    properties:
+      nm-profile-name:
+        type: string
+        description: Unique name of network profile.
+      community-string:
+        type: string
+        description: Encrypted SNMP community string
+  network-profiles:
+    description: |
+      Collection of network profiles
+    properties:
+      network-profile:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/network-profile"
+  newvce:
+    description: |
+      This object fills in the gaps from vce that were incorporated into generic-vnf.  This object will be retired with vce.
+      ###### Related Nodes
+      - FROM l-interface( l-interface BelongsTo newvce, MANY2ONE)(1)
+
+      -(1) IF this NEWVCE node is deleted, this FROM node is DELETED also
+    required:
+    - vnf-id2
+    - vnf-name
+    - vnf-type
+    properties:
+      vnf-id2:
+        type: string
+        description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+      vnf-name:
+        type: string
+        description: Name of VNF.
+      vnf-name2:
+        type: string
+        description: Alternate name of VNF.
+      vnf-type:
+        type: string
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational
+      license-key:
+        type: string
+        description: OBSOLETE -  do not use
+      ipv4-oam-address:
+        type: string
+        description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+      equipment-role:
+        type: string
+        description: Client should send valid enumerated value.
+  newvces:
+    description: |
+      This object fills in the gaps from vce that were incorporated into generic-vnf.  This object will be retired with vce.
+    properties:
+      newvce:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/newvce"
+  nodes:
+    properties:
+      inventory-item-data:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/inventory-item-data"
+  notification-event:
+    properties:
+      cambria.partition:
+        type: string
+      notification-event-header:
+        type: object
+        $ref: "#/patchDefinitions/notification-event-header"
+  notification-event-header:
+    properties:
+      id:
+        type: string
+      timestamp:
+        type: string
+      source-name:
+        type: string
+      domain:
+        type: string
+      sequence-number:
+        type: string
+      severity:
+        type: string
+      event-type:
+        type: string
+      version:
+        type: string
+      action:
+        type: string
+      entity-type:
+        type: string
+      top-entity-type:
+        type: string
+      entity-link:
+        type: string
+      status:
+        type: string
+  notify:
+    required:
+    - event-id
+    properties:
+      event-id:
+        type: string
+      node-type:
+        type: string
+      event-trigger:
+        type: string
+      key-data:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/key-data"
+      selflink:
+        type: string
+  oam-network:
+    description: |
+      OAM network, to be deprecated shortly.  Do not use for new purposes. 
+      ###### Related Nodes
+      - TO cloud-region( oam-network BelongsTo cloud-region, MANY2ONE)
+      - TO complex( oam-network AppliesTo complex, MANY2MANY)
+      - TO service-capability( oam-network AppliesTo service-capability, MANY2MANY)
+
+    required:
+    - network-uuid
+    - network-name
+    - cvlan-tag
+    properties:
+      network-uuid:
+        type: string
+        description: UUID of the network. Unique across a cloud-region
+      network-name:
+        type: string
+        description: Name of the network.
+      cvlan-tag:
+        type: integer
+        format: int64
+        description: cvlan-id
+      ipv4-oam-gateway-address:
+        type: string
+        description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+      ipv4-oam-gateway-address-prefix-length:
+        type: integer
+        format: int32
+        description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+  oam-networks:
+    description: |
+      Collection of OAM networks, to be deprecated shortly.  Do not use for new purposes. 
+    properties:
+      oam-network:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/oam-network"
+  operational-environment:
+    description: |
+      It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+      ###### Related Nodes
+      - TO operational-environment( operational-environment Uses operational-environment, ONE2ONE)
+      - FROM operational-environment( operational-environment Uses operational-environment, ONE2ONE)
+
+    required:
+    - operational-environment-id
+    - operational-environment-name
+    - operational-environment-type
+    - operational-environment-status
+    - tenant-context
+    - workload-context
+    properties:
+      operational-environment-id:
+        type: string
+        description: UUID of an operational environment
+      operational-environment-name:
+        type: string
+        description: Operational Environment name
+      operational-environment-type:
+        type: string
+        description: Operational Environment Type.
+      operational-environment-status:
+        type: string
+        description: Status
+      tenant-context:
+        type: string
+        description: Tenant Context.
+      workload-context:
+        type: string
+        description: Workload Context.
+  operational-environments:
+    description: |
+      a logical partition of the cloud which allows to have multiple environments in the production AIC.
+    properties:
+      operational-environment:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/operational-environment"
+  overloaded-model:
+    description: |
+      Allows for legacy POST of old-style and new-style models
+    required:
+    - model-invariant-id
+    - model-name-version-id
+    - model-type
+    - model-name
+    - model-id
+    - model-version
+    properties:
+      model-invariant-id:
+        type: string
+        description: Unique identifier corresponding to the main definition of a model in ASDC
+      model-name-version-id:
+        type: string
+        description: Unique identifier corresponding to one version of a model in ASDC
+      model-type:
+        type: string
+        description: Type of the model, e.g., service, resource, widget, etc.
+      model-name:
+        type: string
+        description: Name of the model, which can change from version to version.
+      model-id:
+        type: string
+        description: Invariant unique ID which does not change from version to version
+      model-version:
+        type: string
+        description: Version
+      model-description:
+        type: string
+        description: Description
+  owning-entities:
+    description: |
+      Collection of owning-entities
+    properties:
+      owning-entity:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/owning-entity"
+  owning-entity:
+    description: |
+      describes an owning-entity
+      ###### Related Nodes
+      - FROM service-instance( service-instance BelongsTo owning-entity, MANY2ONE)
+
+    required:
+    - owning-entity-id
+    - owning-entity-name
+    properties:
+      owning-entity-id:
+        type: string
+        description: UUID of an owning entity
+      owning-entity-name:
+        type: string
+        description: Owning entity name
+  p-interface:
+    description: |
+      Physical interface (e.g., nic)
+      ###### Related Nodes
+      - TO logical-link( p-interface LinksTo logical-link, MANY2ONE)
+      - TO physical-link( p-interface LinksTo physical-link, MANY2ONE)(2)
+      - TO pnf( p-interface BindsTo pnf, MANY2ONE)(4)
+      - TO pserver( p-interface BindsTo pserver, MANY2ONE)(4)
+      - TO vpls-pe( p-interface BindsTo vpls-pe, MANY2ONE)(4)
+      - FROM lag-interface( lag-interface Uses p-interface, MANY2MANY)
+      - FROM l-interface( l-interface BindsTo p-interface, MANY2ONE)(1)
+
+      -(1) IF this P-INTERFACE node is deleted, this FROM node is DELETED also
+      -(2) IF this P-INTERFACE node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this P-INTERFACE is DELETED also
+    required:
+    - interface-name
+    - in-maint
+    properties:
+      interface-name:
+        type: string
+        description: Name that identifies the physical interface
+      speed-value:
+        type: string
+        description: Captures the numeric part of the speed
+      speed-units:
+        type: string
+        description: Captures the units corresponding to the speed
+      port-description:
+        type: string
+        description: Nature of the services and connectivity on this port.
+      equipment-identifier:
+        type: string
+        description: CLEI or other specification for p-interface hardware.
+      interface-role:
+        type: string
+        description: Role specification for p-interface hardware.
+      interface-type:
+        type: string
+        description: Indicates the physical properties of the interface.
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+  p-interfaces:
+    description: |
+      Collection of physical interfaces.
+    properties:
+      p-interface:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/p-interface"
+  physical-link:
+    description: |
+      Collection of physical connections, typically between p-interfaces
+      ###### Related Nodes
+      - FROM p-interface( p-interface LinksTo physical-link, MANY2ONE)(3)
+
+      -(3) IF this FROM node is deleted, this PHYSICAL-LINK is DELETED also
+    required:
+    - link-name
+    properties:
+      link-name:
+        type: string
+        description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+      speed-value:
+        type: string
+        description: Captures the numeric part of the speed
+      speed-units:
+        type: string
+        description: Captures the units corresponding to the speed
+      circuit-id:
+        type: string
+        description: Circuit it
+      dual-mode:
+        type: string
+        description: Dual access mode (e.g., primary, secondary
+      management-option:
+        type: string
+        description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+      service-provider-name:
+        type: string
+        description: Name of the service Provider on this link.
+  physical-links:
+    description: |
+      Collection of physical connections, typically between p-interfaces
+    properties:
+      physical-link:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/physical-link"
+  platform:
+    description: |
+      describes a platform
+      ###### Related Nodes
+      - TO generic-vnf( platform Uses generic-vnf, MANY2MANY)
+
+    required:
+    - platform-name
+    properties:
+      platform-name:
+        type: string
+        description: Name of the platform
+  platforms:
+    description: |
+      Collection of platforms
+    properties:
+      platform:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/platform"
+  pnf:
+    description: |
+      PNF represents a physical network function. typically equipment used in the D1 world.
+      ###### Related Nodes
+      - TO complex( pnf LocatedIn complex, MANY2ONE)
+      - TO instance-group( pnf MemberOf instance-group, MANY2MANY)
+      - TO zone( pnf LocatedIn zone, MANY2ONE)
+      - FROM logical-link( logical-link BridgedTo pnf, MANY2MANY)
+      - FROM lag-interface( lag-interface BindsTo pnf, MANY2ONE)(1)
+      - FROM p-interface( p-interface BindsTo pnf, MANY2ONE)(1)
+      - FROM service-instance( service-instance ComposedOf pnf, ONE2MANY)
+
+      -(1) IF this PNF node is deleted, this FROM node is DELETED also
+    required:
+    - pnf-name
+    - in-maint
+    properties:
+      pnf-name:
+        type: string
+        description: unique name of Physical Network Function.
+      pnf-name2:
+        type: string
+        description: name of Physical Network Function.
+      pnf-name2-source:
+        type: string
+        description: source of name2
+      pnf-id:
+        type: string
+        description: id of pnf
+      equip-type:
+        type: string
+        description: Equipment type.  Source of truth should define valid values.
+      equip-vendor:
+        type: string
+        description: Equipment vendor.  Source of truth should define valid values.
+      equip-model:
+        type: string
+        description: Equipment model.  Source of truth should define valid values.
+      management-option:
+        type: string
+        description: identifier of managed by company or customer
+      ipaddress-v4-oam:
+        type: string
+        description: ipv4-oam-address with new naming convention for IP addresses
+      sw-version:
+        type: string
+        description: sw-version is the version of SW for the hosted application on the PNF.
+      in-maint:
+        type: boolean
+        description: Used to indicate whether or not this object is in maintenance mode (maintenance mode = true). This field (in conjunction with prov-status) is used to suppress alarms and vSCL on VNFs/VMs.
+      frame-id:
+        type: string
+        description: ID of the physical frame (relay rack) where pnf is installed.
+      serial-number:
+        type: string
+        description: Serial number of the device
+      ipaddress-v4-loopback-0:
+        type: string
+        description: IPV4 Loopback 0 address
+      ipaddress-v6-loopback-0:
+        type: string
+        description: IPV6 Loopback 0 address
+      ipaddress-v4-aim:
+        type: string
+        description: IPV4 AIM address
+      ipaddress-v6-aim:
+        type: string
+        description: IPV6 AIM address
+      ipaddress-v6-oam:
+        type: string
+        description: IPV6 OAM address
+      inv-status:
+        type: string
+        description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+  pnfs:
+    description: |
+      Collection of Physical Network Functions.
+    properties:
+      pnf:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/pnf"
+  port-group:
+    description: |
+      Used to capture the network interfaces of this VCE
+      ###### Related Nodes
+      - TO vce( port-group BelongsTo vce, MANY2ONE)(4)
+      - FROM cvlan-tag( cvlan-tag BelongsTo port-group, MANY2ONE)(1)
+
+      -(1) IF this PORT-GROUP node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this PORT-GROUP is DELETED also
+    required:
+    - interface-id
+    - orchestration-status
+    properties:
+      interface-id:
+        type: string
+        description: Unique ID of the interface
+      neutron-network-id:
+        type: string
+        description: Neutron network id of this Interface
+      neutron-network-name:
+        type: string
+        description: Neutron network name of this Interface
+      interface-role:
+        type: string
+        description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+  port-groups:
+    properties:
+      port-group:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/port-group"
+  project:
+    description: |
+      describes the project
+      ###### Related Nodes
+      - TO service-instance( project Uses service-instance, ONE2MANY)
+
+    required:
+    - project-name
+    properties:
+      project-name:
+        type: string
+        description: Name of the project deploying a service
+  projects:
+    description: |
+      Collection of projects
+    properties:
+      project:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/project"
+  properties:
+    description: |
+      Property holder for query properties or instance properties
+    properties:
+      property-name:
+        type: string
+      property-value:
+        type: string
+  property-constraint:
+    description: |
+      TBD
+      ###### Related Nodes
+      - TO named-query-element( property-constraint BelongsTo named-query-element, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this PROPERTY-CONSTRAINT is DELETED also
+    required:
+    - property-constraint-uuid
+    - constraint-type
+    - property-name
+    - property-value
+    properties:
+      property-constraint-uuid:
+        type: string
+      constraint-type:
+        type: string
+      property-name:
+        type: string
+      property-value:
+        type: string
+  property-constraints:
+    properties:
+      property-constraint:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/property-constraint"
+  pserver:
+    description: |
+      Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
+      ###### Related Nodes
+      - TO group-assignment( pserver MemberOf group-assignment, MANY2ONE)
+      - TO availability-zone( pserver MemberOf availability-zone, MANY2ONE)
+      - TO cloud-region( pserver LocatedIn cloud-region, MANY2ONE)
+      - TO complex( pserver LocatedIn complex, MANY2ONE)
+      - TO zone( pserver LocatedIn zone, MANY2ONE)
+      - FROM generic-vnf( generic-vnf HostedOn pserver, MANY2MANY)
+      - FROM logical-link( logical-link BridgedTo pserver, MANY2MANY)
+      - FROM lag-interface( lag-interface BindsTo pserver, MANY2ONE)(1)
+      - FROM p-interface( p-interface BindsTo pserver, MANY2ONE)(1)
+      - FROM vserver( vserver HostedOn pserver, MANY2ONE)
+
+      -(1) IF this PSERVER node is deleted, this FROM node is DELETED also
+      -PSERVER cannot be deleted if related to GENERIC-VNF,LOGICAL-LINK,VSERVER,GROUP-ASSIGNMENT
+
+    required:
+    - hostname
+    - in-maint
+    properties:
+      hostname:
+        type: string
+        description: Value from executing hostname on the compute node.
+      ptnii-equip-name:
+        type: string
+        description: PTNII name
+      number-of-cpus:
+        type: integer
+        format: int32
+        description: Number of cpus
+      disk-in-gigabytes:
+        type: integer
+        format: int32
+        description: Disk size, in GBs
+      ram-in-megabytes:
+        type: integer
+        format: int32
+        description: RAM size, in MBs
+      equip-type:
+        type: string
+        description: Equipment type.  Source of truth should define valid values.
+      equip-vendor:
+        type: string
+        description: Equipment vendor.  Source of truth should define valid values.
+      equip-model:
+        type: string
+        description: Equipment model.  Source of truth should define valid values.
+      fqdn:
+        type: string
+        description: Fully-qualified domain name
+      pserver-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      ipv4-oam-address:
+        type: string
+        description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device.
+      serial-number:
+        type: string
+        description: Serial number, may be queried
+      ipaddress-v4-loopback-0:
+        type: string
+        description: IPV4 Loopback 0 address
+      ipaddress-v6-loopback-0:
+        type: string
+        description: IPV6 Loopback 0 address
+      ipaddress-v4-aim:
+        type: string
+        description: IPV4 AIM address
+      ipaddress-v6-aim:
+        type: string
+        description: IPV6 AIM address
+      ipaddress-v6-oam:
+        type: string
+        description: IPV6 OAM address
+      inv-status:
+        type: string
+        description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+      pserver-id:
+        type: string
+        description: ID of Pserver
+      internet-topology:
+        type: string
+        description: internet topology of Pserver
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true). This field (in conjunction with prov-status) is used to suppress alarms and vSCL on VNFs/VMs.
+  pservers:
+    description: |
+      Collection of compute hosts.
+    properties:
+      pserver:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/pserver"
+  query-parameters:
+    description: |
+      QueryParameters for performing a named-query or model query
+    properties:
+      named-query:
+        type: object
+        $ref: "#/patchDefinitions/named-query"
+      overloaded-model:
+        type: object
+        $ref: "#/patchDefinitions/overloaded-model"
+  related-lookup:
+    description: |
+      TBD
+      ###### Related Nodes
+      - TO named-query-element( related-lookup BelongsTo named-query-element, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this RELATED-LOOKUP is DELETED also
+    required:
+    - related-lookup-uuid
+    - source-node-type
+    - source-node-property
+    - target-node-type
+    - target-node-property
+    properties:
+      related-lookup-uuid:
+        type: string
+      source-node-type:
+        type: string
+      source-node-property:
+        type: string
+      target-node-type:
+        type: string
+      target-node-property:
+        type: string
+      property-collect-list:
+        type: string
+  related-lookups:
+    properties:
+      related-lookup:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/related-lookup"
+  related-to-property:
+    properties:
+      property-key:
+        type: string
+        description: Key part of a key/value pair
+      property-value:
+        type: string
+        description: Value part of a key/value pair
+  relationship:
+    properties:
+      related-to:
+        type: string
+        description: A keyword provided by A&AI to indicate type of node.
+      related-link:
+        type: string
+        description: URL to the object in A&AI.
+      relationship-data:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/relationship-data"
+      related-to-property:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/related-to-property"
+  relationship-data:
+    required:
+    - relationship-key
+    - relationship-value
+    properties:
+      relationship-key:
+        type: string
+        description: A keyword provided by A&AI to indicate an attribute.
+      relationship-value:
+        type: string
+        description: Value of the attribute.
+  reserved-prop-names:
+    description: |
+      Internal map to define some reserved properties of a vertex
+    properties:
+      last-mod-source-of-truth:
+        type: string
+      aai-node-type:
+        type: string
+      aai-created-ts:
+        type: integer
+        format: int64
+      aai-unique-key:
+        type: string
+      aai-last-mod-ts:
+        type: integer
+        format: int64
+      source-of-truth:
+        type: string
+      aai-uri:
+        type: string
+  response-list:
+    description: |
+      Response container for the results of a named-query or model query
+    properties:
+      inventory-response-items:
+        type: object
+        $ref: "#/patchDefinitions/inventory-response-items"
+  result-data:
+    properties:
+      resource-type:
+        type: string
+        description: The specific type of node in the A&AI graph
+      resource-link:
+        type: string
+        description: The URL to the specific resource
+  route-table-reference:
+    description: |
+      Openstack route table reference.
+      ###### Related Nodes
+      - FROM l3-network( l3-network Uses route-table-reference, MANY2MANY)
+
+    required:
+    - route-table-reference-id
+    - route-table-reference-fqdn
+    properties:
+      route-table-reference-id:
+        type: string
+        description: Route Table Reference id, UUID assigned to this instance.
+      route-table-reference-fqdn:
+        type: string
+        description: FQDN entry in the route table.
+  route-table-references:
+    description: |
+      Collection of openstack route table references
+    properties:
+      route-table-reference:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/route-table-reference"
+  route-target:
+    description: |
+      Route target information
+      ###### Related Nodes
+      - TO vpn-binding( route-target BelongsTo vpn-binding, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this ROUTE-TARGET is DELETED also
+    required:
+    - global-route-target
+    - route-target-role
+    properties:
+      global-route-target:
+        type: string
+        description: Number used to identify an RT, globally unique in the network
+      route-target-role:
+        type: string
+        description: Role assigned to this route target
+  route-targets:
+    description: |
+      Collection of route target information
+    properties:
+      route-target:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/route-target"
+  routing-instance:
+    description: |
+      ###### Related Nodes
+      - TO site-pair-set( routing-instance BelongsTo site-pair-set, MANY2ONE)(4)
+      - FROM site-pair( site-pair BelongsTo routing-instance, MANY2ONE)(1)
+
+      -(1) IF this ROUTING-INSTANCE node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this ROUTING-INSTANCE is DELETED also
+    required:
+    - routing-instance-id
+    properties:
+      routing-instance-id:
+        type: string
+        description: Unique id of routing instance
+      rpm-owner:
+        type: string
+        description: rpm owner
+  routing-instances:
+    description: |
+      set of probes related to generic-vnf routing instance
+    properties:
+      routing-instance:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/routing-instance"
+  sdn-zone-response:
+    properties:
+      oam-networks:
+        type: object
+        $ref: "#/patchDefinitions/oam-networks"
+      az-and-dvs-switches:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/az-and-dvs-switches"
+  search:
+    properties:
+      edge-tag-query-result:
+        type: object
+        $ref: "#/patchDefinitions/edge-tag-query-result"
+      edge-tag-query-request:
+        type: object
+        $ref: "#/patchDefinitions/edge-tag-query-request"
+      search-results:
+        type: object
+        $ref: "#/patchDefinitions/search-results"
+      sdn-zone-response:
+        type: object
+        $ref: "#/patchDefinitions/sdn-zone-response"
+  search-results:
+    properties:
+      result-data:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/result-data"
+  secondary-filt:
+    description: |
+      SecondaryFilt for performing a named-query or model query
+  secondary-filter:
+    properties:
+      property-name:
+        type: string
+      filter-type:
+        type: string
+      property-value:
+        type: string
+  secondary-filts:
+    description: |
+      SecondaryFilts for performing a named-query or model query
+    properties:
+      secondary-filt:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/secondary-filt"
+  segmentation-assignment:
+    description: |
+      Openstack segmentation assignment.
+      ###### Related Nodes
+      - TO l3-network( segmentation-assignment BelongsTo l3-network, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this SEGMENTATION-ASSIGNMENT is DELETED also
+    required:
+    - segmentation-id
+    properties:
+      segmentation-id:
+        type: string
+        description: Route Table Reference id, UUID assigned to this instance.
+  segmentation-assignments:
+    description: |
+      Collection of openstack segmentation assignments
+    properties:
+      segmentation-assignment:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/segmentation-assignment"
+  service:
+    description: |
+      Stand-in for service model definitions.  Likely to be deprecated in favor of models from ASDC.  Does not strictly map to ASDC services.
+    required:
+    - service-id
+    - service-description
+    properties:
+      service-id:
+        type: string
+        description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+      service-description:
+        type: string
+        description: Description of the service
+      service-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+  service-capabilities:
+    description: |
+      Collection of service capabilities.
+    properties:
+      service-capability:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/service-capability"
+  service-capability:
+    description: |
+      Early definition of server/resource pairings, likely to be replaced by models.  No new use should be made of this.
+      ###### Related Nodes
+      - FROM availability-zone( availability-zone AppliesTo service-capability, MANY2MANY)
+      - FROM oam-network( oam-network AppliesTo service-capability, MANY2MANY)
+
+      -SERVICE-CAPABILITY cannot be deleted if related to AVAILABILITY-ZONE,OAM-NETWORK
+
+    required:
+    - service-type
+    - vnf-type
+    properties:
+      service-type:
+        type: string
+        description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+      vnf-type:
+        type: string
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+  service-design-and-creation:
+    description: |
+      Namespace for objects managed by ASDC
+    properties:
+      vnf-images:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/vnf-image"
+      services:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/service"
+      service-capabilities:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/service-capability"
+      models:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/model"
+      named-queries:
+        type: array
+        items:
+          $ref: "#/patchDefinitions/named-query"
+  service-instance:
+    description: |
+      Instance of a service
+      ###### Related Nodes
+      - TO generic-vnf( service-instance ComposedOf generic-vnf, ONE2MANY)
+      - TO l3-network( service-instance ComposedOf l3-network, ONE2MANY)
+      - TO allotted-resource( service-instance Uses allotted-resource, MANY2MANY)
+      - TO connector( service-instance Uses connector, MANY2MANY)
+      - TO ctag-assignment( service-instance Uses ctag-assignment, ONE2MANY)
+      - TO cvlan-tag( service-instance ComposedOf cvlan-tag, MANY2MANY)
+      - TO instance-group( service-instance MemberOf instance-group, MANY2MANY)
+      - TO logical-link( service-instance Uses logical-link, ONE2MANY)(2)
+      - TO pnf( service-instance ComposedOf pnf, ONE2MANY)
+      - TO service-instance( service-instance ComposedOf service-instance, ONE2MANY)
+      - TO vlan( service-instance ComposedOf vlan, ONE2MANY)
+      - TO service-subscription( service-instance BelongsTo service-subscription, MANY2ONE)(4)
+      - TO vce( service-instance ComposedOf vce, ONE2MANY)
+      - FROM allotted-resource( allotted-resource BelongsTo service-instance, MANY2ONE)(1)
+      - FROM metadatum( metadatum BelongsTo service-instance, MANY2ONE)(1)
+      - FROM service-instance( service-instance ComposedOf service-instance, ONE2MANY)
+
+      -(1) IF this SERVICE-INSTANCE node is deleted, this FROM node is DELETED also
+      -(2) IF this SERVICE-INSTANCE node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this SERVICE-INSTANCE is DELETED also
+    required:
+    - service-instance-id
+    properties:
+      service-instance-id:
+        type: string
+        description: Uniquely identifies this instance of a service
+      service-instance-name:
+        type: string
+        description: This field will store a name assigned to the service-instance.
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      widget-model-id:
+        type: string
+        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+      widget-model-version:
+        type: string
+        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+      bandwidth-total:
+        type: string
+        description: Indicates the total bandwidth to be used for this service.
+      bandwidth-up-wan1:
+        type: string
+        description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device.
+      bandwidth-down-wan1:
+        type: string
+        description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device.
+      bandwidth-up-wan2:
+        type: string
+        description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device.
+      bandwidth-down-wan2:
+        type: string
+        description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device.
+      vhn-portal-url:
+        type: string
+        description: URL customers will use to access the vHN Portal.
+      service-instance-location-id:
+        type: string
+        description: An identifier that customers assign to the location where this service is being used.
+  service-instances:
+    description: |
+      Collection of service instances
+    properties:
+      service-instance:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/service-instance"
+  service-subscription:
+    description: |
+      Object that group service instances.
+      ###### Related Nodes
+      - TO customer( service-subscription BelongsTo customer, MANY2ONE)(4)
+      - TO tenant( service-subscription Uses tenant, MANY2MANY)
+      - FROM service-instance( service-instance BelongsTo service-subscription, MANY2ONE)(1)
+
+      -(1) IF this SERVICE-SUBSCRIPTION node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this SERVICE-SUBSCRIPTION is DELETED also
+    required:
+    - service-type
+    properties:
+      service-type:
+        type: string
+        description: Value defined by orchestration to identify this service across ECOMP.
+      temp-ub-sub-account-id:
+        type: string
+        description: This property will be deleted from A&AI in the near future. Only stop gap solution.
+  service-subscriptions:
+    description: |
+      Collection of objects that group service instances.
+    properties:
+      service-subscription:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/service-subscription"
+  services:
+    description: |
+      Collection of service model definitions.  Likely to be deprecated in favor of models from ASDC.
+    properties:
+      service:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/service"
+  site-pair:
+    description: |
+      ###### Related Nodes
+      - TO routing-instance( site-pair BelongsTo routing-instance, MANY2ONE)(4)
+      - FROM class-of-service( class-of-service BelongsTo site-pair, MANY2ONE)(1)
+
+      -(1) IF this SITE-PAIR node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this SITE-PAIR is DELETED also
+    required:
+    - site-pair-id
+    properties:
+      site-pair-id:
+        type: string
+        description: unique identifier of probe
+      source-ip:
+        type: string
+        description: Prefix address
+      destination-ip:
+        type: string
+        description: Prefix address
+      ip-version:
+        type: string
+        description: ip version, v4, v6
+      destination-hostname:
+        type: string
+        description: Hostname of the destination equipment to which SLAs are measured against.
+      destination-equip-type:
+        type: string
+        description: The type of destinatination equipment. Could be Router, etc.
+  site-pair-set:
+    description: |
+      Set of instances for probes used to measure service level agreements
+      ###### Related Nodes
+      - TO generic-vnf( site-pair-set AppliesTo generic-vnf, MANY2MANY)
+      - FROM routing-instance( routing-instance BelongsTo site-pair-set, MANY2ONE)(1)
+
+      -(1) IF this SITE-PAIR-SET node is deleted, this FROM node is DELETED also
+    required:
+    - site-pair-set-id
+    properties:
+      site-pair-set-id:
+        type: string
+        description: Unique id of site pair set.
+  site-pair-sets:
+    description: |
+      Collection of sets of instances for probes related to generic-vnf
+    properties:
+      site-pair-set:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/site-pair-set"
+  site-pairs:
+    description: |
+      probe within a set
+    properties:
+      site-pair:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/site-pair"
+  snapshot:
+    description: |
+      Openstack snapshot
+      ###### Related Nodes
+      - TO cloud-region( snapshot BelongsTo cloud-region, MANY2ONE)
+      - FROM vserver( vserver Uses snapshot, ONE2ONE)
+
+    required:
+    - snapshot-id
+    properties:
+      snapshot-id:
+        type: string
+        description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+      snapshot-name:
+        type: string
+        description: Snapshot name
+      snapshot-architecture:
+        type: string
+        description: Operating system architecture
+      snapshot-os-distro:
+        type: string
+        description: The common name of the operating system distribution in lowercase
+      snapshot-os-version:
+        type: string
+        description: The operating system version as specified by the distributor.
+      application:
+        type: string
+        description: The application that the image instantiates.
+      application-vendor:
+        type: string
+        description: The vendor of the application.
+      application-version:
+        type: string
+        description: The version of the application.
+      snapshot-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      prev-snapshot-id:
+        type: string
+        description: This field contains the UUID of the previous snapshot (if any).
+  snapshots:
+    description: |
+      Collection of openstack snapshots
+    properties:
+      snapshot:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/snapshot"
+  sriov-pf:
+    description: |
+      SR-IOV Physical Function
+      ###### Related Nodes
+      - TO p-interface( sriov-pf BelongsTo p-interface, ONE2ONE)(4)
+      - FROM sriov-vf( sriov-vf Uses sriov-pf, MANY2ONE)
+
+      -(4) IF this TO node is deleted, this SRIOV-PF is DELETED also
+    required:
+    - pf-pci-id
+    properties:
+      pf-pci-id:
+        type: string
+        description: Identifier for the sriov-pf
+  sriov-pfs:
+    description: |
+      Collection of SR-IOV Physical Functions.
+    properties:
+      sriov-pf:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/sriov-pf"
+  sriov-vf:
+    description: |
+      SR-IOV Virtual Function (not to be confused with virtual network function)
+      ###### Related Nodes
+      - TO l-interface( sriov-vf BelongsTo l-interface, ONE2ONE)(4)
+
+      -(4) IF this TO node is deleted, this SRIOV-VF is DELETED also
+    required:
+    - pci-id
+    properties:
+      pci-id:
+        type: string
+        description: PCI ID used to identify the sriov-vf
+      vf-vlan-filter:
+        type: string
+        description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+      vf-mac-filter:
+        type: string
+        description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+      vf-vlan-strip:
+        type: boolean
+        description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+      vf-vlan-anti-spoof-check:
+        type: boolean
+        description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+      vf-mac-anti-spoof-check:
+        type: boolean
+        description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+      vf-mirrors:
+        type: string
+        description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+      vf-broadcast-allow:
+        type: boolean
+        description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+      vf-unknown-multicast-allow:
+        type: boolean
+        description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+      vf-unknown-unicast-allow:
+        type: boolean
+        description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+      vf-insert-stag:
+        type: boolean
+        description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+      vf-link-status:
+        type: string
+        description: This option is used to set the link status.  Valid values as of 1607 are on, off, and auto.
+  sriov-vfs:
+    description: |
+      Collection of SR-IOV Virtual Functions.
+    properties:
+      sriov-vf:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/sriov-vf"
+  start-node-filter:
+    properties:
+      property-name:
+        type: string
+      property-value:
+        type: string
+  subnet:
+    description: |
+      ###### Related Nodes
+      - TO l3-network( subnet BelongsTo l3-network, MANY2ONE)(4)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list MemberOf subnet, MANY2MANY)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list MemberOf subnet, MANY2MANY)
+
+      -(4) IF this TO node is deleted, this SUBNET is DELETED also
+      -SUBNET cannot be deleted if related to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+
+    required:
+    - subnet-id
+    - dhcp-enabled
+    properties:
+      subnet-id:
+        type: string
+        description: Subnet ID, should be UUID.
+      subnet-name:
+        type: string
+        description: Name associated with the subnet.
+      neutron-subnet-id:
+        type: string
+        description: Neutron id of this subnet
+      gateway-address:
+        type: string
+        description: gateway ip address
+      network-start-address:
+        type: string
+        description: network start address
+      cidr-mask:
+        type: string
+        description: cidr mask
+      ip-version:
+        type: string
+        description: ip version
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, mastered by MSO
+      dhcp-enabled:
+        type: boolean
+        description: dhcp enabled
+      dhcp-start:
+        type: string
+        description: the start address reserved for use by dhcp
+      dhcp-end:
+        type: string
+        description: the last address reserved for use by dhcp
+  subnets:
+    properties:
+      subnet:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/subnet"
+  tagged-inventory-item-list:
+    properties:
+      inventory-item:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/inventory-item"
+  tenant:
+    description: |
+      Openstack tenant
+      ###### Related Nodes
+      - TO cloud-region( tenant BelongsTo cloud-region, MANY2ONE)
+      - TO group-assignment( tenant MemberOf group-assignment, MANY2MANY)
+      - TO l3-network( tenant Uses l3-network, MANY2MANY)
+      - TO volume-group( tenant DependsOn volume-group, ONE2MANY)
+      - FROM service-subscription( service-subscription Uses tenant, MANY2MANY)
+      - FROM vserver( vserver BelongsTo tenant, MANY2ONE)
+
+      -TENANT cannot be deleted if related to VSERVER
+
+    required:
+    - tenant-id
+    - tenant-name
+    properties:
+      tenant-id:
+        type: string
+        description: Unique id relative to the cloud-region.
+      tenant-name:
+        type: string
+        description: Readable name of tenant
+  tenants:
+    description: |
+      Collection of openstack tenants.
+    properties:
+      tenant:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/tenant"
+  tunnel-xconnect:
+    description: |
+      Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
+      ###### Related Nodes
+      - TO allotted-resource( tunnel-xconnect BelongsTo allotted-resource, ONE2ONE)(4)
+
+      -(4) IF this TO node is deleted, this TUNNEL-XCONNECT is DELETED also
+    required:
+    - id
+    - bandwidth-up-wan1
+    - bandwidth-down-wan1
+    - bandwidth-up-wan2
+    - bandwidth-down-wan2
+    properties:
+      id:
+        type: string
+        description: Allotted Resource id UUID assigned to this instance.
+      bandwidth-up-wan1:
+        type: string
+        description: The WAN uplink bandwidth for WAN1
+      bandwidth-down-wan1:
+        type: string
+        description: The WAN downlink bandwidth for WAN1
+      bandwidth-up-wan2:
+        type: string
+        description: The WAN uplink bandwidth for WAN2
+      bandwidth-down-wan2:
+        type: string
+        description: The WAN downlink bandwidth for WAN2
+  tunnel-xconnects:
+    description: |
+      This object is used to store the specific tunnel cross connect aspects of an allotted resource
+    properties:
+      tunnel-xconnect:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/tunnel-xconnect"
+  update:
+    description: |
+      Serves a PATCH like function.  Does not enforce concurrency control.  Clear each usage with AAI team.
+    required:
+    - update-node-type
+    properties:
+      update-node-type:
+        type: string
+      update-node-key:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/update-node-key"
+      update-node-uri:
+        type: string
+      action:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/action"
+  update-node-key:
+    properties:
+      key-name:
+        type: string
+      key-value:
+        type: string
+  vce:
+    description: |
+      Virtual Customer Edge Router, used specifically for Gamma.  This object is deprecated.
+      ###### Related Nodes
+      - TO availability-zone( vce Uses availability-zone, MANY2MANY)
+      - TO complex( vce LocatedIn complex, MANY2MANY)
+      - TO vserver( vce HostedOn vserver, ONE2MANY)
+      - FROM entitlement( entitlement BelongsTo vce, MANY2ONE)(1)
+      - FROM license( license BelongsTo vce, MANY2ONE)(1)
+      - FROM port-group( port-group BelongsTo vce, MANY2ONE)(1)
+      - FROM service-instance( service-instance ComposedOf vce, ONE2MANY)
+
+      -(1) IF this VCE node is deleted, this FROM node is DELETED also
+    required:
+    - vnf-id
+    - vnf-name
+    - vnf-type
+    properties:
+      vnf-id:
+        type: string
+        description: Unique id of VNF.  This is unique across the graph.
+      vnf-name:
+        type: string
+        description: Name of VNF.
+      vnf-name2:
+        type: string
+        description: Alternate name of VNF.
+      vnf-type:
+        type: string
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      service-id:
+        type: string
+        description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+      regional-resource-zone:
+        type: string
+        description: Regional way of organizing pservers, source of truth should define values
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational
+      license-key:
+        type: string
+        description: OBSOLETE -  do not use
+      equipment-role:
+        type: string
+        description: Network role being played by this VNF
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, mastered by MSO
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance, managed by MSO
+      mso-catalog-key:
+        type: string
+        description: Corresponds to the SDN-C catalog id used to configure this VCE
+      vpe-id:
+        type: string
+        description: Unique ID of VPE connected to this VCE.
+      v6-vce-wan-address:
+        type: string
+        description: Valid v6 IP address for the WAN Link on this router.  Implied length of /64.
+      ipv4-oam-address:
+        type: string
+        description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+  vces:
+    description: |
+      Collection of Virtual Customer Edge Routers, used specifically for Gamma.  This object is deprecated.
+    properties:
+      vce:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/vce"
+  vf-module:
+    description: |
+      a deployment unit of VNFCs
+      ###### Related Nodes
+      - TO generic-vnf( vf-module BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO l3-network( vf-module DependsOn l3-network, MANY2MANY)
+      - TO vnfc( vf-module Uses vnfc, ONE2MANY)
+      - TO volume-group( vf-module Uses volume-group, ONE2ONE)
+      - TO vserver( vf-module Uses vserver, ONE2MANY)
+
+      -(4) IF this TO node is deleted, this VF-MODULE is DELETED also
+      -VF-MODULE cannot be deleted if related to VNFC
+
+    required:
+    - vf-module-id
+    - is-base-vf-module
+    properties:
+      vf-module-id:
+        type: string
+        description: Unique ID of vf-module.
+      vf-module-name:
+        type: string
+        description: Name of vf-module
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance.
+      orchestration-status:
+        type: string
+        description: orchestration status of this vf-module, mastered by MSO
+      is-base-vf-module:
+        type: boolean
+        description: used to indicate whether or not this object is base vf module
+  vf-modules:
+    description: |
+      Collection of vf-modules, a deployment unit of VNFCs
+    properties:
+      vf-module:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/vf-module"
+  vig-server:
+    description: |
+      vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+      ###### Related Nodes
+      - TO ipsec-configuration( vig-server BelongsTo ipsec-configuration, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this VIG-SERVER is DELETED also
+    required:
+    - vig-address-type
+    properties:
+      vig-address-type:
+        type: string
+        description: indicates whether the VIG is for AVPN or INTERNET
+      ipaddress-v4-vig:
+        type: string
+        description: v4 IP of the vig server
+      ipaddress-v6-vig:
+        type: string
+        description: v6 IP of the vig server
+  vig-servers:
+    properties:
+      vig-server:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/vig-server"
+  vip-ipv4-address-list:
+    description: |
+      IPv4 Address Range
+      ###### Related Nodes
+      - TO cloud-region( vip-ipv4-address-list BelongsTo cloud-region, MANY2ONE)
+      - TO instance-group( vip-ipv4-address-list MemberOf instance-group, MANY2MANY)
+      - TO subnet( vip-ipv4-address-list MemberOf subnet, MANY2MANY)
+      - FROM vnfc( vnfc Uses vip-ipv4-address-list, MANY2MANY)
+
+    required:
+    - vip-ipv4-address
+    properties:
+      vip-ipv4-address:
+        type: string
+        description: IP address
+      vip-ipv4-prefix-length:
+        type: integer
+        format: int64
+        description: Prefix length, 32 for single address
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      is-floating:
+        type: boolean
+        description: Indicator of fixed or floating address
+  vip-ipv6-address-list:
+    description: |
+      IPv6 Address Range
+      ###### Related Nodes
+      - TO cloud-region( vip-ipv6-address-list BelongsTo cloud-region, MANY2ONE)
+      - TO instance-group( vip-ipv6-address-list MemberOf instance-group, MANY2MANY)
+      - TO subnet( vip-ipv6-address-list MemberOf subnet, MANY2MANY)
+      - FROM vnfc( vnfc Uses vip-ipv6-address-list, MANY2MANY)
+
+    required:
+    - vip-ipv6-address
+    properties:
+      vip-ipv6-address:
+        type: string
+        description: IP address
+      vip-ipv6-prefix-length:
+        type: integer
+        format: int64
+        description: Prefix length, 128 for single address
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      is-floating:
+        type: boolean
+        description: Indicator of fixed or floating address
+  virtual-data-center:
+    description: |
+      Virtual organization of cloud infrastructure elements in a data center context
+      ###### Related Nodes
+      - FROM connector( connector LocatedIn virtual-data-center, MANY2MANY)
+      - FROM generic-vnf( generic-vnf LocatedIn virtual-data-center, MANY2MANY)
+      - FROM logical-link( logical-link LocatedIn virtual-data-center, MANY2MANY)
+
+    required:
+    - vdc-id
+    - vdc-name
+    properties:
+      vdc-id:
+        type: string
+        description: Unique ID of the vdc
+      vdc-name:
+        type: string
+        description: Name of the virtual data center
+  virtual-data-centers:
+    description: |
+      Virtual organization of cloud infrastructure elements in a data center context
+    properties:
+      virtual-data-center:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/virtual-data-center"
+  vlan:
+    description: |
+      Definition of vlan
+      ###### Related Nodes
+      - TO l-interface( vlan LinksTo l-interface, MANY2ONE)(4)
+      - TO logical-link( vlan Uses logical-link, MANY2MANY)(2)
+      - TO multicast-configuration( vlan Uses multicast-configuration, MANY2MANY)
+      - FROM allotted-resource( allotted-resource PartOf vlan, MANY2MANY)
+      - FROM service-instance( service-instance ComposedOf vlan, ONE2MANY)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list BelongsTo vlan, MANY2ONE)(1)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list BelongsTo vlan, MANY2ONE)(1)
+
+      -(1) IF this VLAN node is deleted, this FROM node is DELETED also
+      -(2) IF this VLAN node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this VLAN is DELETED also
+    required:
+    - vlan-interface
+    - in-maint
+    properties:
+      vlan-interface:
+        type: string
+        description: String that identifies the interface
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+  vlans:
+    properties:
+      vlan:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/vlan"
+  vnf:
+    description: |
+      Abstract vnf class
+    required:
+    - vnf-id
+    properties:
+      vnf-id:
+        type: string
+        description: Unique id of VNF.  This is unique across the graph.
+  vnf-image:
+    description: |
+      Image object that pertain to a VNF that doesn't have associated vservers.  This is a kludge.
+      ###### Related Nodes
+      - FROM generic-vnf( generic-vnf Uses vnf-image, MANY2ONE)
+
+      -VNF-IMAGE cannot be deleted if related to GENERIC-VNF
+
+    required:
+    - vnf-image-uuid
+    - application
+    - application-vendor
+    properties:
+      vnf-image-uuid:
+        type: string
+        description: Unique ID of this asset
+      application:
+        type: string
+        description: The application that the image instantiates.
+      application-vendor:
+        type: string
+        description: The vendor of the application.
+      application-version:
+        type: string
+        description: The version of the application.
+      selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+  vnf-images:
+    description: |
+      Collection of image objects that pertain to a VNF that doesn't have associated vservers.  This is a kludge.
+    properties:
+      vnf-image:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/vnf-image"
+  vnfc:
+    description: |
+      ###### Related Nodes
+      - TO generic-vnf( vnfc BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO vserver( vnfc HostedOn vserver, ONE2MANY)
+      - FROM vf-module( vf-module Uses vnfc, ONE2MANY)
+
+      -(4) IF this TO node is deleted, this VNFC is DELETED also
+    required:
+    - vnfc-name
+    - vnfc-function-code
+    - vnfc-type
+    - in-maint
+    - is-closed-loop-disabled
+    properties:
+      vnfc-name:
+        type: string
+        description: Unique ID of vnfc.
+      vnfc-function-code:
+        type: string
+        description: function code
+      vnfc-type:
+        type: string
+        description: type
+      prov-status:
+        type: string
+        description: prov status of this vnfc
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, mastered by APP-C
+      ipaddress-v4-oam-vip:
+        type: string
+        description: Oam V4 vip address of this vnfc
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true)
+      is-closed-loop-disabled:
+        type: boolean
+        description: used to indicate whether closed loop function is enabled on this node
+      group-notation:
+        type: string
+        description: Group notation of VNFC
+  vnfcs:
+    description: |
+      virtual network components associated with a vserver from application controller.
+    properties:
+      vnfc:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/vnfc"
+  volume:
+    description: |
+      Ephemeral Block storage volume.
+      ###### Related Nodes
+      - FROM vserver (PARENT of volume, vserver AttachesTo volume)(3)
+
+      -(3) IF this FROM node is deleted, this VOLUME is DELETED also
+    required:
+    - volume-id
+    - volume-selflink
+    properties:
+      volume-id:
+        type: string
+        description: Unique ID of block storage volume relative to the vserver.
+      volume-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+  volume-group:
+    description: |
+      Persistent block-level storage.
+      ###### Related Nodes
+      - TO cloud-region( volume-group BelongsTo cloud-region, MANY2ONE)
+      - TO complex( volume-group LocatedIn complex, MANY2ONE)
+      - FROM generic-vnf( generic-vnf DependsOn volume-group, ONE2MANY)
+      - FROM vf-module( vf-module Uses volume-group, ONE2ONE)
+      - FROM tenant( tenant DependsOn volume-group, ONE2MANY)
+
+    required:
+    - volume-group-id
+    - volume-group-name
+    - vnf-type
+    properties:
+      volume-group-id:
+        type: string
+        description: Unique ID of volume-group.
+      volume-group-name:
+        type: string
+        description: Name of the volume group.
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this volume-group
+      vnf-type:
+        type: string
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      orchestration-status:
+        type: string
+        description: Orchestration status of this volume-group
+      model-customization-id:
+        type: string
+        description: captures the id of all the configuration used to customize the resource for the service.
+      vf-module-model-customization-id:
+        type: string
+        description: helps relate the volume group to the vf-module whose components will require the volume group
+  volume-groups:
+    description: |
+      Collection of persistent block-level storage.
+    properties:
+      volume-group:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/volume-group"
+  volumes:
+    description: |
+      Collection of ephemeral Block storage volumes.
+    properties:
+      volume:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/volume"
+  vpls-pe:
+    description: |
+      VPLS Provider Edge routers.
+      ###### Related Nodes
+      - TO complex( vpls-pe LocatedIn complex, MANY2ONE)
+      - TO ctag-pool( vpls-pe Uses ctag-pool, MANY2MANY)
+      - FROM lag-interface( lag-interface BindsTo vpls-pe, MANY2ONE)(1)
+      - FROM p-interface( p-interface BindsTo vpls-pe, MANY2ONE)(1)
+
+      -(1) IF this VPLS-PE node is deleted, this FROM node is DELETED also
+    required:
+    - equipment-name
+    properties:
+      equipment-name:
+        type: string
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+      ipv4-oam-address:
+        type: string
+        description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+      equipment-role:
+        type: string
+        description: Client should send valid enumerated value, e.g., VPLS-PE.
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Temporary location for stag to get to VCE
+  vpls-pes:
+    description: |
+      Collection of VPLS Provider Edge routers
+    properties:
+      vpls-pe:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/vpls-pe"
+  vpn-binding:
+    description: |
+      VPN binding
+      ###### Related Nodes
+      - FROM l3-network( l3-network Uses vpn-binding, MANY2MANY)
+      - FROM logical-link( logical-link Uses vpn-binding, MANY2MANY)
+      - FROM route-target( route-target BelongsTo vpn-binding, MANY2ONE)(1)
+
+      -(1) IF this VPN-BINDING node is deleted, this FROM node is DELETED also
+      -VPN-BINDING cannot be deleted if related to L3-NETWORK,LOGICAL-LINK
+
+    required:
+    - vpn-id
+    - vpn-name
+    properties:
+      vpn-id:
+        type: string
+        description: VPN ID, globally unique within A&AI
+      vpn-name:
+        type: string
+        description: VPN Name
+      vpn-platform:
+        type: string
+        description: the platform associated with the VPN example AVPN, Mobility
+      vpn-type:
+        type: string
+        description: Type of the vpn, should be taken from enumerated/valid values
+      route-distinguisher:
+        type: string
+        description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
+  vpn-bindings:
+    properties:
+      vpn-binding:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/vpn-binding"
+  vserver:
+    description: |
+      Virtual Servers, aka virtual machine or VM.
+      ###### Related Nodes
+      - TO tenant( vserver BelongsTo tenant, MANY2ONE)
+      - TO flavor( vserver Uses flavor, MANY2ONE)
+      - TO image( vserver Uses image, MANY2ONE)
+      - TO pserver( vserver HostedOn pserver, MANY2ONE)
+      - TO snapshot( vserver Uses snapshot, ONE2ONE)
+      - TO volume (CHILD of vserver, vserver AttachesTo volume, ONE2MANY)(2)
+      - FROM generic-vnf( generic-vnf HostedOn vserver, ONE2MANY)
+      - FROM vce( vce HostedOn vserver, ONE2MANY)
+      - FROM l-interface( l-interface BindsTo vserver, MANY2ONE)(1)
+      - FROM vf-module( vf-module Uses vserver, ONE2MANY)
+      - FROM vnfc( vnfc HostedOn vserver, ONE2MANY)
+
+      -(1) IF this VSERVER node is deleted, this FROM node is DELETED also
+      -(2) IF this VSERVER node is deleted, this TO node is DELETED also
+    required:
+    - vserver-id
+    - vserver-name
+    - vserver-selflink
+    - in-maint
+    - is-closed-loop-disabled
+    properties:
+      vserver-id:
+        type: string
+        description: Unique identifier for this vserver relative to its tenant
+      vserver-name:
+        type: string
+        description: Name of vserver
+      vserver-name2:
+        type: string
+        description: Alternative name of vserver
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+      vserver-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      in-maint:
+        type: boolean
+        description: Used to indicate whether or not this object is in maintenance mode (maintenance mode = true). This field (in conjunction with prov-status) is used to suppress alarms and vSCL on VNFs/VMs.
+      is-closed-loop-disabled:
+        type: boolean
+        description: Used to indicate whether closed loop function is enabled on this node
+  vservers:
+    description: |
+      Collection of virtual Servers, aka virtual machines or VMs.
+    properties:
+      vserver:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/vserver"
+  zone:
+    description: |
+      A zone is a grouping of assets in a location homing to the same connections into the CBB
+      ###### Related Nodes
+      - TO complex( zone LocatedIn complex, MANY2ONE)
+      - FROM cloud-region( cloud-region LocatedIn zone, MANY2ONE)
+      - FROM pnf( pnf LocatedIn zone, MANY2ONE)
+      - FROM pserver( pserver LocatedIn zone, MANY2ONE)
+
+    required:
+    - zone-id
+    - zone-name
+    - design-type
+    - zone-context
+    properties:
+      zone-id:
+        type: string
+        description: Code assigned by AIC to the zone
+      zone-name:
+        type: string
+        description: English name associated with the zone
+      design-type:
+        type: string
+        description: Design of zone [Medium/Large?]
+      zone-context:
+        type: string
+        description: Context of zone [production/test]
+      status:
+        type: string
+        description: Status of a zone.
+  zones:
+    description: |
+      Collection of zones
+    properties:
+      zone:
+        type: array
+        items:          
+          $ref: "#/patchDefinitions/zone"
+getDefinitions:
+  action:
+    properties:
+      action-type:
+        type: string
+      action-data:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/action-data"
+  action-data:
+    properties:
+      property-name:
+        type: string
+      property-value:
+        type: string
+  actions:
+    description: |
+      APIs that are more action related than REST (e.g., notify, update).
+    properties:
+      update:
+        type: object
+        $ref: "#/getDefinitions/update"
+      notify:
+        type: object
+        $ref: "#/getDefinitions/notify"
+  allotted-resource:
+    description: |
+      Represents a slice or partial piece of a resource that gets separately allotted
+      ###### Related Nodes
+      - TO generic-vnf( allotted-resource PartOf generic-vnf, MANY2MANY)
+      - TO instance-group( allotted-resource MemberOf instance-group, MANY2MANY)
+      - TO l3-network( allotted-resource PartOf l3-network, MANY2MANY)
+      - TO network-policy( allotted-resource Uses network-policy, ONE2ONE)
+      - TO vlan( allotted-resource PartOf vlan, MANY2MANY)
+      - TO service-instance( allotted-resource BelongsTo service-instance, MANY2ONE)(4)
+      - FROM tunnel-xconnect( tunnel-xconnect BelongsTo allotted-resource, ONE2ONE)(1)
+      - FROM service-instance( service-instance Uses allotted-resource, MANY2MANY)
+
+      -(1) IF this ALLOTTED-RESOURCE node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this ALLOTTED-RESOURCE is DELETED also
+    required:
+    - id
+    properties:
+      id:
+        type: string
+        description: Allotted Resource id UUID assigned to this instance.
+      description:
+        type: string
+        description: The descriptive information assigned to this allotted resource instance
+      selflink:
+        type: string
+        description: Link back to more information in the controller
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      resource-version:
+        type: string
+        description: Concurrency value
+      orchestration-status:
+        type: string
+        description: Orchestration status
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational
+      type:
+        type: string
+        description: Generic description of the type of allotted resource.
+      role:
+        type: string
+        description: role in the network that this resource will be providing.
+      tunnel-xconnects:
+        type: array
+        items:
+          $ref: "#/getDefinitions/tunnel-xconnect"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  allotted-resources:
+    description: |
+      This object is used to store slices of services being offered
+    properties:
+      allotted-resource:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/allotted-resource"
+  availability-zone:
+    description: |
+      Availability zone, a collection of compute hosts/pservers
+      ###### Related Nodes
+      - TO complex( availability-zone LocatedIn complex, MANY2ONE)
+      - TO service-capability( availability-zone AppliesTo service-capability, MANY2MANY)
+      - TO cloud-region( availability-zone BelongsTo cloud-region, MANY2ONE)(4)
+      - FROM ctag-pool( ctag-pool AppliesTo availability-zone, MANY2MANY)
+      - FROM dvs-switch( dvs-switch AppliesTo availability-zone, MANY2MANY)
+      - FROM generic-vnf( generic-vnf Uses availability-zone, MANY2MANY)
+      - FROM pserver( pserver MemberOf availability-zone, MANY2ONE)
+      - FROM vce( vce Uses availability-zone, MANY2MANY)
+
+      -(4) IF this TO node is deleted, this AVAILABILITY-ZONE is DELETED also
+      -AVAILABILITY-ZONE cannot be deleted if related to CTAG-POOL,DVS-SWITCH,GENERIC-VNF,PSERVER,VCE
+
+    required:
+    - availability-zone-name
+    - hypervisor-type
+    properties:
+      availability-zone-name:
+        type: string
+        description: Name of the availability zone.  Unique across a cloud region
+      hypervisor-type:
+        type: string
+        description: Type of hypervisor.  Source of truth should define valid values.
+      operational-status:
+        type: string
+        description: State that indicates whether the availability zone should be used, etc.  Source of truth should define valid values.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  availability-zones:
+    description: |
+      Collection of availability zones
+    properties:
+      availability-zone:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/availability-zone"
+  az-and-dvs-switches:
+    properties:
+      dvs-switches:
+        type: object
+        $ref: "#/getDefinitions/dvs-switches"
+      availability-zone:
+        type: object
+        $ref: "#/getDefinitions/availability-zone"
+  business:
+    description: |
+      Namespace for business related constructs
+    properties:
+      connectors:
+        type: array
+        items:
+          $ref: "#/getDefinitions/connector"
+      customers:
+        type: array
+        items:
+          $ref: "#/getDefinitions/customer"
+  class-of-service:
+    description: |
+      ###### Related Nodes
+      - TO site-pair( class-of-service BelongsTo site-pair, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this CLASS-OF-SERVICE is DELETED also
+    required:
+    - cos
+    properties:
+      cos:
+        type: string
+        description: unique identifier of probe
+      probe-id:
+        type: string
+        description: identifier of probe
+      probe-type:
+        type: string
+        description: type of probe
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  classes-of-service:
+    description: |
+      class-of-service of probe
+    properties:
+      class-of-service:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/class-of-service"
+  cloud-infrastructure:
+    description: |
+      Namespace for cloud infrastructure.
+    properties:
+      complexes:
+        type: array
+        items:
+          $ref: "#/getDefinitions/complex"
+      cloud-regions:
+        type: array
+        items:
+          $ref: "#/getDefinitions/cloud-region"
+      network-profiles:
+        type: array
+        items:
+          $ref: "#/getDefinitions/network-profile"
+      pservers:
+        type: array
+        items:
+          $ref: "#/getDefinitions/pserver"
+      virtual-data-centers:
+        type: array
+        items:
+          $ref: "#/getDefinitions/virtual-data-center"
+  cloud-region:
+    description: |
+      cloud-region designates an installation of a cloud cluster or region or instantiation
+      ###### Related Nodes
+      - TO complex( cloud-region LocatedIn complex, MANY2ONE)
+      - TO l3-network( cloud-region Uses l3-network, MANY2MANY)
+      - TO zone( cloud-region LocatedIn zone, MANY2ONE)
+      - FROM availability-zone( availability-zone BelongsTo cloud-region, MANY2ONE)(1)
+      - FROM dvs-switch( dvs-switch BelongsTo cloud-region, MANY2ONE)
+      - FROM flavor( flavor BelongsTo cloud-region, MANY2ONE)
+      - FROM group-assignment( group-assignment BelongsTo cloud-region, MANY2ONE)
+      - FROM image( image BelongsTo cloud-region, MANY2ONE)
+      - FROM oam-network( oam-network BelongsTo cloud-region, MANY2ONE)
+      - FROM snapshot( snapshot BelongsTo cloud-region, MANY2ONE)
+      - FROM tenant( tenant BelongsTo cloud-region, MANY2ONE)
+      - FROM volume-group( volume-group BelongsTo cloud-region, MANY2ONE)
+      - FROM logical-link( logical-link LocatedIn cloud-region, MANY2MANY)
+      - FROM pserver( pserver LocatedIn cloud-region, MANY2ONE)
+
+      -(1) IF this CLOUD-REGION node is deleted, this FROM node is DELETED also
+      -CLOUD-REGION cannot be deleted if related to DVS-SWITCH,FLAVOR,GROUP-ASSIGNMENT,IMAGE,OAM-NETWORK,SNAPSHOT,TENANT,VOLUME-GROUP
+
+    required:
+    - cloud-owner
+    - cloud-region-id
+    properties:
+      cloud-owner:
+        type: string
+        description: Identifies the vendor and cloud name. First part of composite key should be formatted as vendor-cloudname
+      cloud-region-id:
+        type: string
+        description: Identifier used by the vendor for the region. Second part of composite key
+      cloud-type:
+        type: string
+        description: Type of the cloud (e.g., openstack)
+      owner-defined-type:
+        type: string
+        description: Cloud-owner defined type indicator (e.g., dcp, lcp)
+      cloud-region-version:
+        type: string
+        description: Software version employed at the site.  NOTE - THIS FIELD IS NOT KEPT UP TO DATE.
+      identity-url:
+        type: string
+        description: URL of the keystone identity service
+      cloud-zone:
+        type: string
+        description: Zone where the cloud is homed.  NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+      complex-name:
+        type: string
+        description: complex name for cloud-region instance.  NOTE - THIS FIELD IS NOT CORRECTLY POPULATED.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      volume-groups:
+        type: array
+        items:
+          $ref: "#/getDefinitions/volume-group"
+      tenants:
+        type: array
+        items:
+          $ref: "#/getDefinitions/tenant"
+      flavors:
+        type: array
+        items:
+          $ref: "#/getDefinitions/flavor"
+      group-assignments:
+        type: array
+        items:
+          $ref: "#/getDefinitions/group-assignment"
+      snapshots:
+        type: array
+        items:
+          $ref: "#/getDefinitions/snapshot"
+      images:
+        type: array
+        items:
+          $ref: "#/getDefinitions/image"
+      dvs-switches:
+        type: array
+        items:
+          $ref: "#/getDefinitions/dvs-switch"
+      oam-networks:
+        type: array
+        items:
+          $ref: "#/getDefinitions/oam-network"
+      availability-zones:
+        type: array
+        items:
+          $ref: "#/getDefinitions/availability-zone"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  cloud-regions:
+    properties:
+      cloud-region:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/cloud-region"
+  complex:
+    description: |
+      Collection of physical locations that can house cloud-regions.
+      ###### Related Nodes
+      - TO l3-network( complex Uses l3-network, MANY2MANY)
+      - FROM availability-zone( availability-zone LocatedIn complex, MANY2ONE)
+      - FROM cloud-region( cloud-region LocatedIn complex, MANY2ONE)
+      - FROM ctag-pool( ctag-pool BelongsTo complex, MANY2ONE)(1)
+      - FROM oam-network( oam-network AppliesTo complex, MANY2MANY)
+      - FROM pnf( pnf LocatedIn complex, MANY2ONE)
+      - FROM pserver( pserver LocatedIn complex, MANY2ONE)
+      - FROM vce( vce LocatedIn complex, MANY2MANY)
+      - FROM volume-group( volume-group LocatedIn complex, MANY2ONE)
+      - FROM vpls-pe( vpls-pe LocatedIn complex, MANY2ONE)
+      - FROM zone( zone LocatedIn complex, MANY2ONE)
+
+      -(1) IF this COMPLEX node is deleted, this FROM node is DELETED also
+      -COMPLEX cannot be deleted if related to AVAILABILITY-ZONE,CLOUD-REGION,OAM-NETWORK,PNF,PSERVER,VCE,VOLUME-GROUP,VPLS-PE,ZONE
+
+    required:
+    - physical-location-id
+    - physical-location-type
+    - street1
+    - city
+    - postal-code
+    - country
+    - region
+    properties:
+      physical-location-id:
+        type: string
+        description: Unique identifier for physical location, e.g., CLLI
+      data-center-code:
+        type: string
+        description: Data center code which can be an alternate way to identify a complex
+      complex-name:
+        type: string
+        description: Gamma complex name for LCP instance.
+      identity-url:
+        type: string
+        description: URL of the keystone identity service
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      physical-location-type:
+        type: string
+        description: Type, e.g., central office, data center.
+      street1:
+        type: string
+      street2:
+        type: string
+      city:
+        type: string
+      state:
+        type: string
+      postal-code:
+        type: string
+      country:
+        type: string
+      region:
+        type: string
+      latitude:
+        type: string
+      longitude:
+        type: string
+      elevation:
+        type: string
+      lata:
+        type: string
+      ctag-pools:
+        type: array
+        items:
+          $ref: "#/getDefinitions/ctag-pool"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  complexes:
+    description: |
+      Collection of physical locations that can house cloud-regions.
+    properties:
+      complex:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/complex"
+  configuration:
+    description: |
+      Port Mirror Configuration.
+      ###### Related Nodes
+      - TO allotted-resource( configuration Uses allotted-resource, ONE2ONE)(2)
+      - TO logical-link( configuration Uses logical-link, ONE2MANY)(2)
+      - FROM metadatum( metadatum BelongsTo configuration, MANY2ONE)(1)
+      - FROM generic-vnf( generic-vnf Uses configuration, ONE2MANY)(3)
+      - FROM service-instance( service-instance Uses configuration, ONE2MANY)
+
+      -(1) IF this CONFIGURATION node is deleted, this FROM node is DELETED also
+      -(2) IF this CONFIGURATION node is deleted, this TO node is DELETED also
+      -(3) IF this FROM node is deleted, this CONFIGURATION is DELETED also
+    required:
+    - configuration-id
+    - configuration-type
+    - configuration-sub-type
+    - orchestration-status
+    - operational-status
+    - configuration-selflink
+    - model-customization-id
+    properties:
+      configuration-id:
+        type: string
+        description: UUID assigned to configuration.
+      management-option:
+        type: string
+        description: Indicates the entity that will manage this feature. Could be an organization or the name of the application as well.
+      configuration-name:
+        type: string
+        description: Name of the configuration.
+      configuration-type:
+        type: string
+        description: port-mirroring-configuration.
+      configuration-sub-type:
+        type: string
+        description: vprobe, pprobe.
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      orchestration-status:
+        type: string
+        description: Orchestration status of the configuration.
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational.
+      configuration-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details from SDN-GC.
+      model-customization-id:
+        type: string
+        description: id of  the configuration used to customize the resource
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      metadata:
+        type: array
+        items:
+          $ref: "#/getDefinitions/metadatum"
+  configurations:
+    description: |
+      Collection of configurations
+    properties:
+      configuration:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/configuration"
+  connector:
+    description: |
+      Collection of resource instances used to connect a variety of disparate inventory widgets
+      ###### Related Nodes
+      - TO virtual-data-center( connector LocatedIn virtual-data-center, MANY2MANY)
+      - FROM metadatum( metadatum BelongsTo connector, MANY2ONE)(1)
+      - FROM service-instance( service-instance Uses connector, MANY2MANY)
+
+      -(1) IF this CONNECTOR node is deleted, this FROM node is DELETED also
+    required:
+    - resource-instance-id
+    properties:
+      resource-instance-id:
+        type: string
+        description: Unique id of resource instance.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      widget-model-id:
+        type: string
+        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+      widget-model-version:
+        type: string
+        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      metadata:
+        type: array
+        items:
+          $ref: "#/getDefinitions/metadatum"
+  connectors:
+    description: |
+      Collection of resource instances used to connect a variety of disparate inventory widgets
+    properties:
+      connector:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/connector"
+  constrained-element-set:
+    description: |
+      This is how we would capture constraints defining allowed sets of elements.
+      ###### Related Nodes
+      - TO model-constraint( constrained-element-set BelongsTo model-constraint, MANY2ONE)(4)
+      - TO model-element( constrained-element-set BelongsTo model-element, MANY2ONE)(4)
+      - FROM element-choice-set( element-choice-set BelongsTo constrained-element-set, MANY2ONE)(1)
+
+      -(1) IF this CONSTRAINED-ELEMENT-SET node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this CONSTRAINED-ELEMENT-SET is DELETED also
+    required:
+    - constrained-element-set-uuid
+    - constraint-type
+    - check-type
+    properties:
+      constrained-element-set-uuid:
+        type: string
+      constraint-type:
+        type: string
+      check-type:
+        type: string
+      resource-version:
+        type: string
+      element-choice-sets:
+        type: array
+        items:
+          $ref: "#/getDefinitions/element-choice-set"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  constrained-element-sets:
+    properties:
+      constrained-element-set:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/constrained-element-set"
+  ctag-assignment:
+    description: |
+      ###### Related Nodes
+      - TO l3-network( ctag-assignment BelongsTo l3-network, MANY2ONE)(4)
+      - FROM service-instance( service-instance Uses ctag-assignment, ONE2MANY)
+
+      -(4) IF this TO node is deleted, this CTAG-ASSIGNMENT is DELETED also
+    required:
+    - vlan-id-inner
+    properties:
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: id.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  ctag-assignments:
+    properties:
+      ctag-assignment:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/ctag-assignment"
+  ctag-pool:
+    description: |
+      A collection of C tags (vlan tags) grouped for a specific purpose.
+      ###### Related Nodes
+      - TO complex( ctag-pool BelongsTo complex, MANY2ONE)(4)
+      - TO availability-zone( ctag-pool AppliesTo availability-zone, MANY2MANY)
+      - FROM vpls-pe( vpls-pe Uses ctag-pool, MANY2MANY)
+
+      -(4) IF this TO node is deleted, this CTAG-POOL is DELETED also
+    required:
+    - target-pe
+    - availability-zone-name
+    - ctag-pool-purpose
+    properties:
+      target-pe:
+        type: string
+        description: The Target provider edge router
+      availability-zone-name:
+        type: string
+        description: Name of the availability zone
+      ctag-pool-purpose:
+        type: string
+        description: Describes what the intended purpose of this pool is.
+      ctag-values:
+        type: string
+        description: Comma separated list of ctags
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  ctag-pools:
+    properties:
+      ctag-pool:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/ctag-pool"
+  customer:
+    description: |
+      customer identifiers to provide linkage back to BSS information.
+      ###### Related Nodes
+      - FROM service-subscription( service-subscription BelongsTo customer, MANY2ONE)(1)
+
+      -(1) IF this CUSTOMER node is deleted, this FROM node is DELETED also
+    required:
+    - global-customer-id
+    - subscriber-name
+    - subscriber-type
+    properties:
+      global-customer-id:
+        type: string
+        description: Global customer id used across ECOMP to uniquely identify customer.
+      subscriber-name:
+        type: string
+        description: Subscriber name, an alternate way to retrieve a customer.
+      subscriber-type:
+        type: string
+        description: Subscriber type, a way to provide VID with only the INFRA customers.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      service-subscriptions:
+        type: array
+        items:
+          $ref: "#/getDefinitions/service-subscription"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  customers:
+    description: |
+      Collection of customer identifiers to provide linkage back to BSS information.
+    properties:
+      customer:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/customer"
+  cvlan-tag-entry:
+    required:
+    - cvlan-tag
+    properties:
+      cvlan-tag:
+        type: integer
+        format: int64
+        description: See mis-na-virtualization-platform.yang
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  cvlan-tags:
+    properties:
+      cvlan-tag-entry:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/cvlan-tag-entry"
+  dvs-switch:
+    description: |
+      Digital virtual switch metadata, used by SDN-C to configure VCEs.  A&AI needs to receive this data from the PO deployment team and administer it using the provisioningTool.sh into A&AI. 
+      ###### Related Nodes
+      - TO cloud-region( dvs-switch BelongsTo cloud-region, MANY2ONE)
+      - TO availability-zone( dvs-switch AppliesTo availability-zone, MANY2MANY)
+
+    required:
+    - switch-name
+    - vcenter-url
+    properties:
+      switch-name:
+        type: string
+        description: DVS switch name
+      vcenter-url:
+        type: string
+        description: URL used to reach the vcenter
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  dvs-switches:
+    description: |
+      Collection of digital virtual switch metadata used for vmWare VCEs and GenericVnfs.
+    properties:
+      dvs-switch:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/dvs-switch"
+  edge-prop-names:
+    description: |
+      Internal map to define the properties of an edge and interpret the map EdgeRules
+    properties:
+      edgeLabel:
+        type: string
+      direction:
+        type: string
+      multiplicityRule:
+        type: string
+      isParent:
+        type: boolean
+      usesResource:
+        type: boolean
+      hasDelTarget:
+        type: boolean
+      SVC-INFRA:
+        type: boolean
+      SVC-INFRA-REV:
+        type: boolean
+  edge-tag-query-request:
+    properties:
+      edge-tag:
+        type: string
+      result-detail:
+        type: string
+      start-node-type:
+        type: string
+      start-node-filter:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/start-node-filter"
+      include-node-filter:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/include-node-filter"
+      secondary-filter:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/secondary-filter"
+  edge-tag-query-result:
+    properties:
+      tagged-inventory-item-list:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/tagged-inventory-item-list"
+  element-choice-set:
+    description: |
+      This is how we would capture constraints defining allowed sets of elements.
+      ###### Related Nodes
+      - TO constrained-element-set( element-choice-set BelongsTo constrained-element-set, MANY2ONE)(4)
+      - FROM model-element( model-element BelongsTo element-choice-set, MANY2ONE)(1)
+
+      -(1) IF this ELEMENT-CHOICE-SET node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this ELEMENT-CHOICE-SET is DELETED also
+    required:
+    - element-choice-set-uuid
+    - element-choice-set-name
+    properties:
+      element-choice-set-uuid:
+        type: string
+      element-choice-set-name:
+        type: string
+      cardinality:
+        type: string
+      resource-version:
+        type: string
+      model-elements:
+        type: array
+        items:
+          $ref: "#/getDefinitions/model-element"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  element-choice-sets:
+    properties:
+      element-choice-set:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/element-choice-set"
+  entitlement:
+    description: |
+      Metadata for entitlement group.
+      ###### Related Nodes
+      - TO generic-vnf( entitlement BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO vce( entitlement BelongsTo vce, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this ENTITLEMENT is DELETED also
+    required:
+    - group-uuid
+    - resource-uuid
+    properties:
+      group-uuid:
+        type: string
+        description: Unique ID for the entitlement group the resource comes from, should be uuid.
+      resource-uuid:
+        type: string
+        description: Unique ID of an entitlement resource. 
+      resource-version:
+        type: string
+        description: Concurrency value
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  entitlements:
+    description: |
+      Entitlements, keyed by group-uuid and resource-uuid, related to license management
+    properties:
+      entitlement:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/entitlement"
+  esr-ems:
+    description: |
+      Persist EMS address information used by EMS driver.
+      ###### Related Nodes
+      - FROM esr-system-info( esr-system-info BelongsTo esr-ems, MANY2ONE)(1)
+
+      -(1) IF this ESR-EMS node is deleted, this FROM node is DELETED also
+    required:
+    - ems-id
+    properties:
+      ems-id:
+        type: string
+        description: Unique ID of EMS.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      esr-system-info-list:
+        type: object
+        $ref: "#/getDefinitions/esr-system-info-list"
+      relationship-list:
+        type: object
+        $ref: "#/getDefinitions/relationship-list"
+  esr-ems-list:
+    properties:
+      esr-ems:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/esr-ems"
+  esr-system-info:
+    description: |
+      Persist common address information of external systems.
+      ###### Related Nodes
+      - TO esr-ems( esr-system-info BelongsTo esr-ems, MANY2ONE)(4)
+      - TO esr-vnfm( esr-system-info BelongsTo esr-vnfm, ONE2ONE)(4)
+      - TO esr-thirdparty-sdnc( esr-system-info BelongsTo esr-thirdparty-sdnc, ONE2ONE)(4)
+      - TO cloud-region( esr-system-info BelongsTo cloud-region, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this ESR-SYSTEM-INFO is DELETED also
+    required:
+    - esr-system-info-id
+    - user-name
+    - password
+    - system-type
+    properties:
+      esr-system-info-id:
+        type: string
+        description: Unique ID of esr system info.
+      system-name:
+        type: string
+        description: name of external system.
+      type:
+        type: string
+        description: type of external systems.
+      vendor:
+        type: string
+        description: vendor of external systems.
+      version:
+        type: string
+        description: version of external systems.
+      service-url:
+        type: string
+        description: url used to access external systems.
+      user-name:
+        type: string
+        description: username used to access external systems.
+      password:
+        type: string
+        description: password used to access external systems.
+      system-type:
+        type: string
+        description: it could be vim/vnfm/thirdparty-sdnc/ems-resource/ems-performance/ems-alarm.
+      protocol:
+        type: string
+        description: protocol of third party SDNC, for example netconf/snmp.
+      ssl-cacert:
+        type: string
+        description: ca file content if enabled ssl on auth-url.
+      ssl-insecure:
+        type: boolean
+        description: Whether to verify VIM's certificate.
+      ip-address:
+        type: string
+        description: service IP of ftp server.
+      port:
+        type: string
+        description: service port of ftp server.
+      cloud-domain:
+        type: string
+        description: domain info for authentication.
+      default-tenant:
+        type: string
+        description: default tenant of VIM.
+      passive:
+        type: boolean
+        description: ftp passive mode or not.
+      remote-path:
+        type: string
+        description: resource or performance data file path.
+      system-status:
+        type: string
+        description: the status of external system.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  esr-system-info-list:
+    description: |
+      Collection of persistent block-level external system auth info.
+    properties:
+      esr-system-info:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/esr-system-info"
+  esr-thirdparty-sdnc:
+    description: |
+      Persist SDNC address information used by ONAP SDNC.
+      ###### Related Nodes
+      - TO pnf( esr-thirdparty-sdnc AppliesTo pnf, ONE2MANY)
+      - FROM esr-system-info( esr-system-info BelongsTo esr-thirdparty-sdnc, ONE2ONE)(1)
+
+      -(1) IF this ESR-THIRDPARTY-SDNC node is deleted, this FROM node is DELETED also
+    required:
+    - thirdparty-sdnc-id
+    properties:
+      thirdparty-sdnc-id:
+        type: string
+        description: Unique ID of SDNC.
+      location:
+        type: string
+        description: used for DC type to indicate the location of SDNC, such as Core or Edge.
+      product-name:
+        type: string
+        description: password used to access SDNC server.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      esr-system-info-list:
+        type: object
+        $ref: "#/getDefinitions/esr-system-info-list"
+      relationship-list:
+        type: object
+        $ref: "#/getDefinitions/relationship-list"
+  esr-thirdparty-sdnc-list:
+    properties:
+      esr-thirdparty-sdnc:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/esr-thirdparty-sdnc"
+  esr-vnfm:
+    description: |
+      Persist VNFM address information used by VF-C.
+      ###### Related Nodes
+      - FROM esr-system-info( esr-system-info BelongsTo esr-vnfm, ONE2ONE)(1)
+
+      -(1) IF this ESR-VNFM node is deleted, this FROM node is DELETED also
+    required:
+    - vnfm-id
+    properties:
+      vnfm-id:
+        type: string
+        description: Unique ID of VNFM.
+      vim-id:
+        type: string
+        description: indecate the VIM to deploy VNF.
+      certificate-url:
+        type: string
+        description: certificate url of VNFM.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      esr-system-info-list:
+        type: object
+        $ref: "#/getDefinitions/esr-system-info-list"
+      relationship-list:
+        type: object
+        $ref: "#/getDefinitions/relationship-list"
+  esr-vnfm-list:
+    properties:
+      esr-vnfm:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/esr-vnfm"
+  evc:
+    description: |
+      evc object is an optional child object of the Configuration object.
+      ###### Related Nodes
+      - TO configuration( evc BelongsTo configuration, ONE2ONE)(4)
+
+      -(4) IF this TO node is deleted, this EVC is DELETED also
+    required:
+    - evc-id
+    properties:
+      evc-id:
+        type: string
+        description: Unique/key field for the evc object
+      forwarding-path-topology:
+        type: string
+        description: Point-to-Point, Multi-Point
+      cir-value:
+        type: string
+        description: Commited Information Rate
+      cir-units:
+        type: string
+        description: CIR units
+      connection-diversity-group-id:
+        type: string
+        description: Diversity Group ID
+      service-hours:
+        type: string
+        description: formerly Performance Group
+      esp-evc-circuit-id:
+        type: string
+        description: EVC Circuit ID of ESP EVC
+      esp-evc-cir-value:
+        type: string
+        description: Committed Information Rate (For ESP)
+      esp-evc-cir-units:
+        type: string
+        description: CIR units (For ESP)
+      esp-itu-code:
+        type: string
+        description: Identifies ESP
+      collector-pop-clli:
+        type: string
+        description: Collector POP CLLI (from the hostname of the access pnf)
+      inter-connect-type-ingress:
+        type: string
+        description: Interconnect type on ingress side of EVC.
+      tagmode-access-ingress:
+        type: string
+        description: tagode for collector side of EVC
+      tagmode-access-egress:
+        type: string
+        description: tagMode for network side of EVC
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+  evcs:
+    properties:
+      evc:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/evc"
+  external-system:
+    description: |
+      Namespace for external system.
+    properties:
+      esr-ems-list:
+        type: object
+        $ref: "#/getDefinitions/esr-ems-list"
+      esr-vnfm-list:
+        type: object
+        $ref: "#/getDefinitions/esr-vnfm-list"
+      esr-thirdparty-sdnc-list:
+        type: object
+        $ref: "#/getDefinitions/esr-thirdparty-sdnc-list"
+  extra-properties:
+    description: |
+      Extra properties for inventory item for response list
+    properties:
+      extra-property:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/extra-property"
+  extra-property:
+    properties:
+      property-name:
+        type: string
+      property-value:
+        type: string
+  flavor:
+    description: |
+      Openstack flavor.
+      ###### Related Nodes
+      - TO cloud-region( flavor BelongsTo cloud-region, MANY2ONE)
+      - FROM vserver( vserver Uses flavor, MANY2ONE)
+
+      -FLAVOR cannot be deleted if related to VSERVER
+
+    required:
+    - flavor-id
+    - flavor-name
+    - flavor-selflink
+    properties:
+      flavor-id:
+        type: string
+        description: Flavor id, expected to be unique across cloud-region.
+      flavor-name:
+        type: string
+        description: Flavor name
+      flavor-vcpus:
+        type: integer
+        format: int32
+        description: Number of CPUs
+      flavor-ram:
+        type: integer
+        format: int32
+        description: Amount of memory
+      flavor-disk:
+        type: integer
+        format: int32
+        description: Disk space
+      flavor-ephemeral:
+        type: integer
+        format: int32
+        description: Amount of ephemeral disk space
+      flavor-swap:
+        type: string
+        description: amount of swap space allocation
+      flavor-is-public:
+        type: boolean
+        description: whether flavor is available to all users or private to the tenant it was created in.
+      flavor-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      flavor-disabled:
+        type: boolean
+        description: Boolean as to whether this flavor is no longer enabled
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  flavors:
+    description: |
+      Collection of openstack flavors.
+    properties:
+      flavor:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/flavor"
+  forwarder:
+    description: |
+      Entity describing a sequenced segment of forwarding path
+      ###### Related Nodes
+      - TO forwarding-path( forwarder BelongsTo forwarding-path, MANY2ONE)(4)
+      - TO l-interface( forwarder ForwardsTo l-interface, MANY2ONE)
+      - TO configuration( forwarder Uses configuration, ONE2ONE)(2)
+      - TO lag-interface( forwarder ForwardsTo lag-interface, MANY2ONE)
+      - TO p-interface( forwarder ForwardsTo p-interface, MANY2ONE)
+
+      -(2) IF this FORWARDER node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this FORWARDER is DELETED also
+    required:
+    - sequence
+    properties:
+      sequence:
+        type: integer
+        format: int32
+        description: Unique ID of this segmentation
+      forwarder-role:
+        type: string
+        description: ingress, intermediate, egress
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+  forwarder-evc:
+    description: |
+      forwarder object is an optional child object of the Configuration object.
+      ###### Related Nodes
+      - TO configuration( forwarder-evc BelongsTo configuration, ONE2ONE)(4)
+
+      -(4) IF this TO node is deleted, this FORWARDER-EVC is DELETED also
+    required:
+    - forwarder-evc-id
+    properties:
+      forwarder-evc-id:
+        type: string
+        description: Key for forwarder-evc object
+      circuit-id:
+        type: string
+        description: Circuit ID from customer/ESP/ingress end of EVC, or reference to beater circuit on gateway/network/egress end of EVC
+      ivlan:
+        type: string
+        description: Internal VLAN.
+      svlan:
+        type: string
+        description: SVLAN value for ingress of egress forwarder.
+      cvlan:
+        type: string
+        description: CVLAN value for ingress of egress forwarder.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+  forwarder-evcs:
+    properties:
+      forwarder-evc:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/forwarder-evc"
+  forwarders:
+    properties:
+      forwarder:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/forwarder"
+  forwarding-path:
+    description: |
+      Entity that describes the sequenced forwarding path between interfaces of services or resources
+      ###### Related Nodes
+      - TO service-instance( forwarding-path AppliesTo service-instance, MANY2ONE)(4)
+      - TO configuration( forwarding-path Uses configuration, ONE2ONE)(2)
+      - FROM forwarder( forwarder BelongsTo forwarding-path, MANY2ONE)(1)
+
+      -(1) IF this FORWARDING-PATH node is deleted, this FROM node is DELETED also
+      -(2) IF this FORWARDING-PATH node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this FORWARDING-PATH is DELETED also
+    required:
+    - forwarding-path-id
+    - forwarding-path-name
+    properties:
+      forwarding-path-id:
+        type: string
+        description: Unique ID of this FP
+      forwarding-path-name:
+        type: string
+        description: Name of the FP
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency. Must be empty on create, valid on update and delete.
+      selflink:
+        type: string
+        description: the self link for this FP
+      forwarders:
+        type: array
+        items:
+          $ref: "#/getDefinitions/forwarder"
+  forwarding-paths:
+    properties:
+      forwarding-path:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/forwarding-path"
+  generic-vnf:
+    description: |
+      General purpose VNF
+      ###### Related Nodes
+      - TO availability-zone( generic-vnf Uses availability-zone, MANY2MANY)
+      - TO instance-group( generic-vnf MemberOf instance-group, MANY2MANY)
+      - TO ipsec-configuration( generic-vnf Uses ipsec-configuration, MANY2ONE)
+      - TO l3-network( generic-vnf Uses l3-network, MANY2MANY)
+      - TO license-key-resource( generic-vnf Uses license-key-resource, MANY2MANY)
+      - TO pserver( generic-vnf HostedOn pserver, MANY2MANY)
+      - TO vnf-image( generic-vnf Uses vnf-image, MANY2ONE)
+      - TO volume-group( generic-vnf DependsOn volume-group, ONE2MANY)
+      - TO vserver( generic-vnf HostedOn vserver, ONE2MANY)
+      - TO virtual-data-center( generic-vnf LocatedIn virtual-data-center, MANY2MANY)
+      - FROM allotted-resource( allotted-resource PartOf generic-vnf, MANY2MANY)
+      - FROM entitlement( entitlement BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM vnfc( vnfc BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM lag-interface( lag-interface BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM license( license BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM l-interface( l-interface BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM network-profile( network-profile AppliesTo generic-vnf, MANY2MANY)
+      - FROM service-instance( service-instance ComposedOf generic-vnf, ONE2MANY)
+      - FROM site-pair-set( site-pair-set AppliesTo generic-vnf, MANY2MANY)
+      - FROM vf-module( vf-module BelongsTo generic-vnf, MANY2ONE)(1)
+      - FROM logical-link( logical-link BridgedTo generic-vnf, MANY2MANY)
+
+      -(1) IF this GENERIC-VNF node is deleted, this FROM node is DELETED also
+    required:
+    - vnf-id
+    - vnf-name
+    - vnf-type
+    - in-maint
+    - is-closed-loop-disabled
+    properties:
+      vnf-id:
+        type: string
+        description: Unique id of VNF.  This is unique across the graph.
+      vnf-name:
+        type: string
+        description: Name of VNF.
+      vnf-name2:
+        type: string
+        description: Alternate name of VNF.
+      vnf-type:
+        type: string
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      service-id:
+        type: string
+        description: Unique identifier of service, does not necessarily map to ASDC service models.  SOON TO BE DEPRECATED
+      regional-resource-zone:
+        type: string
+        description: Regional way of organizing pservers, source of truth should define values
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational.  Valid values are in-service-path and out-of-service-path.
+      license-key:
+        type: string
+        description: OBSOLETE -  do not use
+      equipment-role:
+        type: string
+        description: Client should send valid enumerated value
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, used by MSO.
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance, managed by MSO
+      mso-catalog-key:
+        type: string
+        description: Corresponds to the SDN-C catalog id used to configure this VCE
+      management-option:
+        type: string
+        description: identifier of managed by company or customer
+      ipv4-oam-address:
+        type: string
+        description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by generic-vnf.
+      ipv4-loopback0-address:
+        type: string
+        description: v4 Loopback0 address
+      nm-lan-v6-address:
+        type: string
+        description: v6 Loopback address
+      management-v6-address:
+        type: string
+        description: v6 management address
+      vcpu:
+        type: integer
+        format: int64
+        description: number of vcpus ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vcpu-units:
+        type: string
+        description: units associated with vcpu, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vmemory:
+        type: integer
+        format: int64
+        description: number of GB of memory ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vmemory-units:
+        type: string
+        description: units associated with vmemory, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vdisk:
+        type: integer
+        format: int64
+        description: number of vdisks ordered for this instance of VNF, used for VNFs with no vservers/flavors, to be used only in some usecases
+      vdisk-units:
+        type: string
+        description: units associated with vdisk, used for VNFs with no vservers/flavors, to be used only in some usecases
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true). This field (in conjunction with prov-status) is used to suppress alarms and vSCL on VNFs/VMs.
+      is-closed-loop-disabled:
+        type: boolean
+        description: used to indicate whether closed loop function is enabled on this node
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      summary-status:
+        type: string
+        description: details regarding the generic-vnf operation, PLEASE DISCONTINUE USE OF THIS FIELD.
+      encrypted-access-flag:
+        type: boolean
+        description: indicates whether generic-vnf access uses SSH
+      entitlement-assignment-group-uuid:
+        type: string
+        description: UUID of the Entitlement group used for licensing VNFs, OBSOLETE -  See child relationships.
+      entitlement-resource-uuid:
+        type: string
+        description: UUID of the specific entitlement resource.  OBSOLETE -  See child relationships.
+      license-assignment-group-uuid:
+        type: string
+        description: UUID of the license assignment group.  OBSOLETE -  See child relationships.
+      license-key-uuid:
+        type: string
+        description: UUID of the actual license resource.  OBSOLETE -  See child relationships.
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      model-customization-id:
+        type: string
+        description: captures the id of all the configuration used to customize the resource for the service.
+      widget-model-id:
+        type: string
+        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+      widget-model-version:
+        type: string
+        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+      as-number:
+        type: string
+        description: as-number of the VNF
+      regional-resource-subzone:
+        type: string
+        description: represents sub zone of the rr plane
+      nf-type:
+        type: string
+        description: Generic description of the type of NF
+      nf-function:
+        type: string
+        description: English description of Network function that the specific VNF deployment is providing
+      nf-role:
+        type: string
+        description: role in the network that this model will be providing
+      nf-naming-code:
+        type: string
+        description: string assigned to this model used for naming purposes
+      selflink:
+        type: string
+        description: Path to the controller object.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      l-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/l-interface"
+      lag-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/lag-interface"
+      vf-modules:
+        type: array
+        items:
+          $ref: "#/getDefinitions/vf-module"
+      licenses:
+        type: array
+        items:
+          $ref: "#/getDefinitions/license"
+      entitlements:
+        type: array
+        items:
+          $ref: "#/getDefinitions/entitlement"
+  generic-vnfs:
+    description: |
+      Collection of VNFs
+    properties:
+      generic-vnf:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/generic-vnf"
+  group-assignment:
+    description: |
+      Openstack group-assignment used to store exclusivity groups (EG).
+      ###### Related Nodes
+      - TO cloud-region( group-assignment BelongsTo cloud-region, MANY2ONE)
+      - FROM pserver( pserver MemberOf group-assignment, MANY2ONE)
+      - FROM tenant( tenant MemberOf group-assignment, MANY2MANY)
+
+    required:
+    - group-id
+    - group-type
+    - group-name
+    properties:
+      group-id:
+        type: string
+        description: Group id, expected to be unique across cloud-region.
+      group-type:
+        type: string
+        description: Group type - the type of group this instance refers to
+      group-name:
+        type: string
+        description: Group name - name assigned to the group
+      group-description:
+        type: string
+        description: Group description - description of the group
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  group-assignments:
+    description: |
+      Collection of openstack group assignments
+    properties:
+      group-assignment:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/group-assignment"
+  host-route:
+    description: |
+      ###### Related Nodes
+      - TO subnet( host-route BelongsTo subnet, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this HOST-ROUTE is DELETED also
+    required:
+    - host-route-id
+    - route-prefix
+    - next-hop
+    properties:
+      host-route-id:
+        type: string
+        description: host-route id
+      route-prefix:
+        type: string
+        description: subnet prefix
+      next-hop:
+        type: string
+        description: Could be ip-address, hostname, or service-instance
+      next-hop-type:
+        type: string
+        description: Should be ip-address, hostname, or service-instance to match next-hop
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  host-routes:
+    properties:
+      host-route:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/host-route"
+  hpa-capabilities:
+    description: |
+      Collection of HPA Capabilities
+    properties:
+      hpa-capability:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/hpa-capability"
+  hpa-capability:
+    description: |
+      Represents a HPA capability
+      ###### Related Nodes
+      - TO flavor( hpa-capability BelongsTo flavor, MANY2ONE)
+      - TO cloud-region( hpa-capability BelongsTo cloud-region, MANY2ONE)
+      - FROM hpa-feature-attributes( hpa-feature-attributes BelongsTo hpa-capability, MANY2ONE)(1)
+
+      -(1) IF this HPA-CAPABILITY node is deleted, this FROM node is DELETED also
+    required:
+    - hpa-capability-id
+    - hpa-feature
+    properties:
+      hpa-capability-id:
+        type: string
+        description: UUID to uniquely identify a HPA capability
+      hpa-feature:
+        type: string
+        description: Name of the HPACapability
+      hpa-version:
+        type: string
+        description: HPA schema version
+      architecture:
+        type: string
+        description: Hardware architecture
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      hpa-feature-attributes:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/hpa-feature-attributes"
+  hpa-feature-attributes:
+    description: |
+      HPA Capability Feature attributes
+      ###### Related Nodes
+      - TO hpa-capability( hpa-feature-attributes BelongsTo hpa-capability, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this HPA-FEATURE-ATTRIBUTES is DELETED also
+    required:
+    - hpa-attribute-key
+    properties:
+      hpa-attribute-key:
+        type: string
+        description: name of the specific HPA attribute
+      hpa-attribute-value:
+        type: string
+        description: JSON string specifying the value, unit and type of the specific HPA attribute
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  image:
+    description: |
+      Openstack image.
+      ###### Related Nodes
+      - TO cloud-region( image BelongsTo cloud-region, MANY2ONE)
+      - FROM metadatum( metadatum BelongsTo image, MANY2ONE)(1)
+      - FROM vserver( vserver Uses image, MANY2ONE)
+
+      -(1) IF this IMAGE node is deleted, this FROM node is DELETED also
+      -IMAGE cannot be deleted if related to VSERVER
+
+    required:
+    - image-id
+    - image-name
+    - image-os-distro
+    - image-os-version
+    - image-selflink
+    properties:
+      image-id:
+        type: string
+        description: Image id, expected to be unique across cloud region
+      image-name:
+        type: string
+        description: Image name
+      image-architecture:
+        type: string
+        description: Operating system architecture.
+      image-os-distro:
+        type: string
+        description: The common name of the operating system distribution in lowercase
+      image-os-version:
+        type: string
+        description: The operating system version as specified by the distributor.
+      application:
+        type: string
+        description: The application that the image instantiates.
+      application-vendor:
+        type: string
+        description: The vendor of the application.
+      application-version:
+        type: string
+        description: The version of the application.
+      image-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      metadata:
+        type: array
+        items:
+          $ref: "#/getDefinitions/metadatum"
+  images:
+    description: |
+      Collectio of Openstack images.
+    properties:
+      image:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/image"
+  include-node-filter:
+    properties:
+      include-node-type:
+        type: string
+  instance-filter:
+    description: |
+      InstanceFilter for performing a named-query or model query
+  instance-filters:
+    description: |
+      InstanceFilters for performing a named-query or model query
+    properties:
+      instance-filter:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/instance-filter"
+  instance-group:
+    description: |
+      General mechanism for grouping instances
+      ###### Related Nodes
+      - TO model( instance-group Targets model, MANY2MANY)
+      - FROM allotted-resource( allotted-resource MemberOf instance-group, MANY2MANY)
+      - FROM generic-vnf( generic-vnf MemberOf instance-group, MANY2MANY)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list MemberOf instance-group, MANY2MANY)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list MemberOf instance-group, MANY2MANY)
+      - FROM l-interface( l-interface MemberOf instance-group, MANY2MANY)
+      - FROM pnf( pnf MemberOf instance-group, MANY2MANY)
+      - FROM service-instance( service-instance MemberOf instance-group, MANY2MANY)
+
+    required:
+    - id
+    - description
+    - type
+    properties:
+      id:
+        type: string
+        description: Instance Group ID, UUID assigned to this instance.
+      description:
+        type: string
+        description: Descriptive text to help identify the usage of this instance-group
+      type:
+        type: string
+        description: Only valid value today is lower case ha for high availability
+      sub-type:
+        type: string
+        description: Valid values for ha type are [geo-activeactive, geo-activestandby, local-activeactive, local-activestandby]
+      resource-version:
+        type: string
+        description: Concurrency value
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  instance-groups:
+    description: |
+      Collection of openstack route table references
+    properties:
+      instance-group:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/instance-group"
+  inventory:
+    properties:
+      search:
+        type: object
+        $ref: "#/getDefinitions/search"
+      actions:
+        type: object
+        $ref: "#/getDefinitions/actions"
+      cloud-infrastructure:
+        type: object
+        $ref: "#/getDefinitions/cloud-infrastructure"
+      business:
+        type: object
+        $ref: "#/getDefinitions/business"
+      service-design-and-creation:
+        type: object
+        $ref: "#/getDefinitions/service-design-and-creation"
+      network:
+        type: object
+        $ref: "#/getDefinitions/network"
+      nodes:
+        type: object
+        $ref: "#/getDefinitions/nodes"
+  inventory-item:
+    properties:
+      inventory-item-type:
+        type: string
+      inventory-item-link:
+        type: string
+      inventory-item-data:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/inventory-item-data"
+      tagged-inventory-item-list:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/tagged-inventory-item-list"
+  inventory-item-data:
+    properties:
+      property-name:
+        type: string
+      property-value:
+        type: string
+  inventory-response-item:
+    description: |
+      Inventory item for response list
+    properties:
+      model-name:
+        type: string
+      extra-properties:
+        type: object
+        $ref: "#/getDefinitions/extra-properties"
+      inventory-response-items:
+        type: object
+        $ref: "#/getDefinitions/inventory-response-items"
+  inventory-response-items:
+    description: |
+      Container for inventory items in response list
+    properties:
+      inventory-response-item:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/inventory-response-item"
+  ipsec-configuration:
+    description: |
+      IPSec configuration node will contain various configuration data for the NMTE VNF. This node will have an edge to the generic-vnf (vnf type = TE). Starting 1607, this data will be populated by SDN-C
+      ###### Related Nodes
+      - FROM generic-vnf( generic-vnf Uses ipsec-configuration, MANY2ONE)
+      - FROM vig-server( vig-server BelongsTo ipsec-configuration, MANY2ONE)(1)
+
+      -(1) IF this IPSEC-CONFIGURATION node is deleted, this FROM node is DELETED also
+    required:
+    - ipsec-configuration-id
+    properties:
+      ipsec-configuration-id:
+        type: string
+        description: UUID of this configuration
+      requested-vig-address-type:
+        type: string
+        description: Indicate the type of VIG server like AVPN, INTERNET, BOTH
+      requested-encryption-strength:
+        type: string
+        description: Encryption values like 3des-cbc, des-cbc, aes-128-cbc, aes-192-cbc, aes-265-cbc
+      requested-dmz-type:
+        type: string
+        description: can offer a shared DMZ or a DMZ specific to a customer
+      shared-dmz-network-address:
+        type: string
+        description: Network address of shared DMZ
+      requested-customer-name:
+        type: string
+        description: If the DMZ is a custom DMZ, this field will indicate the customer information
+      ike-version:
+        type: string
+        description: can be 1 or 2
+      ikev1-authentication:
+        type: string
+        description: Contains values like md5, sha1, sha256, sha384
+      ikev1-encryption:
+        type: string
+        description: Encyption values like 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+      ikev1-dh-group:
+        type: string
+        description: Diffie-Hellman group like DH-GROUP2, DH-GROUP5, DH-GROUP14
+      ikev1-am-group-id:
+        type: string
+        description: Group name defined in VIG for clients using aggressive mode
+      ikev1-am-password:
+        type: string
+        description: pre-shared key for the above group name 
+      ikev1-sa-lifetime:
+        type: string
+        description: Lifetime for IKEv1 SA
+      ipsec-authentication:
+        type: string
+        description: md5, sha1, sha256, sha384
+      ipsec-encryption:
+        type: string
+        description: 3des-cbc, des-cbc, aes-128-cbc,?aes-192-cbc, aes-265-cbc
+      ipsec-sa-lifetime:
+        type: string
+        description: Life time for IPSec SA
+      ipsec-pfs:
+        type: string
+        description: enable PFS or not
+      xauth-userid:
+        type: string
+        description: user ID for xAuth, sm-user, ,nmteHostName
+      xauth-user-password:
+        type: string
+        description: Encrypted using the Juniper $9$ algorithm
+      dpd-interval:
+        type: string
+        description: The time between DPD probe
+      dpd-frequency:
+        type: string
+        description: Maximum number of DPD before claiming the tunnel is down
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      vig-servers:
+        type: array
+        items:
+          $ref: "#/getDefinitions/vig-server"
+  ipsec-configurations:
+    properties:
+      ipsec-configuration:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/ipsec-configuration"
+  key-data:
+    properties:
+      key-name:
+        type: string
+      key-value:
+        type: string
+  l-interface:
+    description: |
+      Logical interfaces, e.g., a vnic.
+      ###### Related Nodes
+      - TO generic-vnf( l-interface BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO lag-interface( l-interface BelongsTo lag-interface, MANY2ONE)(4)
+      - TO instance-group( l-interface MemberOf instance-group, MANY2MANY)
+      - TO l-interface( l-interface BelongsTo l-interface, MANY2ONE)(4)
+      - TO logical-link( l-interface LinksTo logical-link, MANY2MANY)(2)
+      - TO newvce( l-interface BelongsTo newvce, MANY2ONE)(4)
+      - TO p-interface( l-interface BindsTo p-interface, MANY2ONE)(4)
+      - TO vserver( l-interface BindsTo vserver, MANY2ONE)(4)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list BelongsTo l-interface, MANY2ONE)(1)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list BelongsTo l-interface, MANY2ONE)(1)
+      - FROM sriov-vf( sriov-vf BelongsTo l-interface, ONE2ONE)(1)
+      - FROM vlan( vlan LinksTo l-interface, MANY2ONE)(1)
+      - FROM l-interface( l-interface BelongsTo l-interface, MANY2ONE)(4)
+
+      -(1) IF this L-INTERFACE node is deleted, this FROM node is DELETED also
+      -(2) IF this L-INTERFACE node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this L-INTERFACE is DELETED also
+    required:
+    - interface-name
+    - is-port-mirrored
+    - in-maint
+    properties:
+      interface-name:
+        type: string
+        description: Name given to the interface
+      interface-role:
+        type: string
+        description: E.g., CUSTOMER, UPLINK, etc.
+      v6-wan-link-ip:
+        type: string
+        description: Questionably placed - v6 ip addr of this interface (is in vr-lan-interface from Mary B.
+      selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      interface-id:
+        type: string
+        description: ID of interface
+      macaddr:
+        type: string
+        description: MAC address for the interface
+      network-name:
+        type: string
+        description: Name of the network
+      management-option:
+        type: string
+        description: Whether A&AI should be managing this interface of not. Could have value like CUSTOMER
+      interface-description:
+        type: string
+        description: Human friendly text regarding this interface.
+      is-port-mirrored:
+        type: boolean
+        description: boolean indicatating whether or not port is a mirrored.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true)
+      vlans:
+        type: array
+        items:
+          $ref: "#/getDefinitions/vlan"
+      sriov-vfs:
+        type: array
+        items:
+          $ref: "#/getDefinitions/sriov-vf"
+      l-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/l-interface"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      l3-interface-ipv4-address-list:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
+      l3-interface-ipv6-address-list:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
+  l-interfaces:
+    description: |
+      Collection of logical interfaces.
+    properties:
+      l-interface:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/l-interface"
+  l3-interface-ipv4-address-list:
+    description: |
+      IPv4 Address Range
+      ###### Related Nodes
+      - TO instance-group( l3-interface-ipv4-address-list MemberOf instance-group, MANY2MANY)
+      - TO l3-network( l3-interface-ipv4-address-list MemberOf l3-network, MANY2MANY)
+      - TO subnet( l3-interface-ipv4-address-list MemberOf subnet, MANY2MANY)
+      - TO l-interface( l3-interface-ipv4-address-list BelongsTo l-interface, MANY2ONE)(4)
+      - TO vlan( l3-interface-ipv4-address-list BelongsTo vlan, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this L3-INTERFACE-IPV4-ADDRESS-LIST is DELETED also
+    required:
+    - l3-interface-ipv4-address
+    properties:
+      l3-interface-ipv4-address:
+        type: string
+        description: IP address
+      l3-interface-ipv4-prefix-length:
+        type: integer
+        format: int64
+        description: Prefix length, 32 for single address
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      is-floating:
+        type: boolean
+        description: Indicator of fixed or floating address
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      neutron-network-id:
+        type: string
+        description: Neutron network id of the interface that address belongs to
+      neutron-subnet-id:
+        type: string
+        description: Neutron id of subnet that address belongs to
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  l3-interface-ipv6-address-list:
+    description: |
+      IPv6 Address Range
+      ###### Related Nodes
+      - TO instance-group( l3-interface-ipv6-address-list MemberOf instance-group, MANY2MANY)
+      - TO l3-network( l3-interface-ipv6-address-list MemberOf l3-network, MANY2MANY)
+      - TO subnet( l3-interface-ipv6-address-list MemberOf subnet, MANY2MANY)
+      - TO l-interface( l3-interface-ipv6-address-list BelongsTo l-interface, MANY2ONE)(4)
+      - TO vlan( l3-interface-ipv6-address-list BelongsTo vlan, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this L3-INTERFACE-IPV6-ADDRESS-LIST is DELETED also
+    required:
+    - l3-interface-ipv6-address
+    properties:
+      l3-interface-ipv6-address:
+        type: string
+        description: IP address
+      l3-interface-ipv6-prefix-length:
+        type: integer
+        format: int64
+        description: Prefix length, 128 for single address
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      is-floating:
+        type: boolean
+        description: Indicator of fixed or floating address
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      neutron-network-id:
+        type: string
+        description: Neutron network id of the interface that address belongs to
+      neutron-subnet-id:
+        type: string
+        description: Neutron id of subnet that address belongs to
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  l3-network:
+    description: |
+      Generic network definition
+      ###### Related Nodes
+      - TO network-policy( l3-network Uses network-policy, MANY2MANY)
+      - TO route-table-reference( l3-network Uses route-table-reference, MANY2MANY)
+      - TO vpn-binding( l3-network Uses vpn-binding, MANY2MANY)
+      - FROM allotted-resource( allotted-resource PartOf l3-network, MANY2MANY)
+      - FROM cloud-region( cloud-region Uses l3-network, MANY2MANY)
+      - FROM complex( complex Uses l3-network, MANY2MANY)
+      - FROM generic-vnf( generic-vnf Uses l3-network, MANY2MANY)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list MemberOf l3-network, MANY2MANY)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list MemberOf l3-network, MANY2MANY)
+      - FROM ctag-assignment( ctag-assignment BelongsTo l3-network, MANY2ONE)(1)
+      - FROM segmentation-assignment( segmentation-assignment BelongsTo l3-network, MANY2ONE)(1)
+      - FROM service-instance( service-instance ComposedOf l3-network, ONE2MANY)
+      - FROM subnet( subnet BelongsTo l3-network, MANY2ONE)(1)
+      - FROM tenant( tenant Uses l3-network, MANY2MANY)
+      - FROM vf-module( vf-module DependsOn l3-network, MANY2MANY)
+
+      -(1) IF this L3-NETWORK node is deleted, this FROM node is DELETED also
+    required:
+    - network-id
+    - network-name
+    - is-bound-to-vpn
+    - is-provider-network
+    - is-shared-network
+    - is-external-network
+    properties:
+      network-id:
+        type: string
+        description: Network ID, should be uuid. Unique across A&AI.
+      network-name:
+        type: string
+        description: Name of the network, governed by some naming convention..
+      network-type:
+        type: string
+        description: Type of the network - who defines these values?
+      network-role:
+        type: string
+        description: Role the network plans - who defines these values?
+      network-technology:
+        type: string
+        description: Network technology - who defines these values?
+      neutron-network-id:
+        type: string
+        description: Neutron network id of this Interface
+      is-bound-to-vpn:
+        type: boolean
+        description: Set to true if bound to VPN
+      service-id:
+        type: string
+        description: Unique identifier of service from ASDC.  Does not strictly map to ASDC services.  SOON TO BE DEPRECATED
+      network-role-instance:
+        type: integer
+        format: int64
+        description: network role instance
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, mastered by MSO
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance, managed by MSO
+      mso-catalog-key:
+        type: string
+        description: Corresponds to the SDN-C catalog id used to configure this VCE
+      contrail-network-fqdn:
+        type: string
+        description: Contrail FQDN for the network
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      model-customization-id:
+        type: string
+        description: captures the id of all the configuration used to customize the resource for the service.
+      widget-model-id:
+        type: string
+        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+      widget-model-version:
+        type: string
+        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+      physical-network-name:
+        type: string
+        description: Name associated with the physical network.
+      is-provider-network:
+        type: boolean
+        description: boolean indicatating whether or not network is a provider network.
+      is-shared-network:
+        type: boolean
+        description: boolean indicatating whether or not network is a shared network.
+      is-external-network:
+        type: boolean
+        description: boolean indicatating whether or not network is an external network.
+      selflink:
+        type: string
+        description: Path to the controller object.
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational.
+      subnets:
+        type: array
+        items:
+          $ref: "#/getDefinitions/subnet"
+      ctag-assignments:
+        type: array
+        items:
+          $ref: "#/getDefinitions/ctag-assignment"
+      segmentation-assignments:
+        type: array
+        items:
+          $ref: "#/getDefinitions/segmentation-assignment"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+        description: Relates to tenant (or is it a child of tenant), complex, service, vpn-binding
+  l3-networks:
+    properties:
+      l3-network:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/l3-network"
+  lag-interface:
+    description: |
+      Link aggregate interface
+      ###### Related Nodes
+      - TO generic-vnf( lag-interface BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO lag-link( lag-interface LinksTo lag-link, MANY2MANY)(2)
+      - TO logical-link( lag-interface Uses logical-link, MANY2MANY)(2)
+      - TO p-interface( lag-interface Uses p-interface, MANY2MANY)
+      - TO pnf( lag-interface BindsTo pnf, MANY2ONE)(4)
+      - TO pserver( lag-interface BindsTo pserver, MANY2ONE)(4)
+      - TO vpls-pe( lag-interface BindsTo vpls-pe, MANY2ONE)(4)
+      - FROM l-interface( l-interface BelongsTo lag-interface, MANY2ONE)(1)
+
+      -(1) IF this LAG-INTERFACE node is deleted, this FROM node is DELETED also
+      -(2) IF this LAG-INTERFACE node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this LAG-INTERFACE is DELETED also
+    required:
+    - interface-name
+    - in-maint
+    properties:
+      interface-name:
+        type: string
+        description: Name that identifies the link aggregate interface
+      interface-description:
+        type: string
+        description: Human friendly text regarding this interface.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      speed-value:
+        type: string
+        description: Captures the numeric part of the speed
+      speed-units:
+        type: string
+        description: Captures the units corresponding to the speed
+      interface-id:
+        type: string
+        description: ID of interface
+      interface-role:
+        type: string
+        description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true)
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      l-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/l-interface"
+  lag-interfaces:
+    description: |
+      Collection of link aggregate interfaces.
+    properties:
+      lag-interface:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/lag-interface"
+  lag-link:
+    description: |
+      LAG links can connect lag-interfaces
+      ###### Related Nodes
+      - FROM lag-interface( lag-interface LinksTo lag-link, MANY2MANY)(3)
+      - FROM logical-link( logical-link Uses lag-link, MANY2MANY)
+
+      -(3) IF this FROM node is deleted, this LAG-LINK is DELETED also
+    required:
+    - link-name
+    properties:
+      link-name:
+        type: string
+        description: Alphabetical concatenation of lag-interface names
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  lag-links:
+    description: |
+      Collection of link aggregation connections
+    properties:
+      lag-link:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/lag-link"
+  license:
+    description: |
+      Metadata for license group.
+      ###### Related Nodes
+      - TO generic-vnf( license BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO vce( license BelongsTo vce, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this LICENSE is DELETED also
+    required:
+    - group-uuid
+    - resource-uuid
+    properties:
+      group-uuid:
+        type: string
+        description: Unique ID for the license group the resource belongs to, should be uuid.
+      resource-uuid:
+        type: string
+        description: Unique ID of a license resource. 
+      resource-version:
+        type: string
+        description: Concurrency value
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  licenses:
+    description: |
+      Licenses to be allocated across resources, keyed by group-uuid and resource-uuid, related to license management
+    properties:
+      license:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/license"
+  line-of-business:
+    description: |
+      describes a line-of-business
+      ###### Related Nodes
+      - TO generic-vnf( line-of-business Uses generic-vnf, MANY2MANY)
+
+    required:
+    - line-of-business-name
+    properties:
+      line-of-business-name:
+        type: string
+        description: Name of the line-of-business (product)
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  lines-of-business:
+    description: |
+      Collection of lines-of-business
+    properties:
+      line-of-business:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/line-of-business"
+  logical-link:
+    description: |
+      Logical links generally connect l-interfaces but are used to express logical connectivity between two points
+      ###### Related Nodes
+      - TO cloud-region( logical-link LocatedIn cloud-region, MANY2MANY)
+      - TO generic-vnf( logical-link BridgedTo generic-vnf, MANY2MANY)
+      - TO lag-link( logical-link Uses lag-link, MANY2MANY)
+      - TO logical-link( logical-link Uses logical-link, MANY2MANY)
+      - TO pnf( logical-link BridgedTo pnf, MANY2MANY)
+      - TO pserver( logical-link BridgedTo pserver, MANY2MANY)
+      - TO vpn-binding( logical-link Uses vpn-binding, MANY2MANY)
+      - TO virtual-data-center( logical-link LocatedIn virtual-data-center, MANY2MANY)
+      - FROM lag-interface( lag-interface Uses logical-link, MANY2MANY)(3)
+      - FROM l-interface( l-interface LinksTo logical-link, MANY2MANY)(3)
+      - FROM p-interface( p-interface LinksTo logical-link, MANY2ONE)
+      - FROM service-instance( service-instance Uses logical-link, ONE2MANY)(3)
+      - FROM vlan( vlan Uses logical-link, MANY2MANY)(3)
+      - FROM logical-link( logical-link Uses logical-link, MANY2MANY)
+
+      -(3) IF this FROM node is deleted, this LOGICAL-LINK is DELETED also
+    required:
+    - link-name
+    - link-type
+    properties:
+      link-name:
+        type: string
+        description: e.g., evc-name, or vnf-nameA_interface-nameA_vnf-nameZ_interface-nameZ
+      link-type:
+        type: string
+        description: Type of logical link, e.g., evc
+      speed-value:
+        type: string
+        description: Captures the numeric part of the speed
+      speed-units:
+        type: string
+        description: Captures the units corresponding to the speed
+      ip-version:
+        type: string
+        description: v4, v6, or ds for dual stack
+      routing-protocol:
+        type: string
+        description: For example, static or BGP
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      widget-model-id:
+        type: string
+        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+      widget-model-version:
+        type: string
+        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+      operational-status:
+        type: string
+        description: Indication of operational status of the logical link.
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+      link-role:
+        type: string
+        description: Indication of the network use of the logical link.
+      link-name2:
+        type: string
+        description: Alias or alternate name (CLCI or D1 name).
+      link-id:
+        type: string
+        description: UUID of the logical-link, SDNC generates this.
+      circuit-id:
+        type: string
+        description: Circuit id
+      purpose:
+        type: string
+        description: Reason for this entity, role it is playing
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  logical-links:
+    description: |
+      Collection of logical connections
+    properties:
+      logical-link:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/logical-link"
+  metadata:
+    description: |
+      Collection of metadatum (key/value pairs)
+    properties:
+      metadatum:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/metadatum"
+  metadatum:
+    description: |
+      Key/value pairs
+      ###### Related Nodes
+      - TO connector( metadatum BelongsTo connector, MANY2ONE)(4)
+      - TO image( metadatum BelongsTo image, MANY2ONE)(4)
+      - TO service-instance( metadatum BelongsTo service-instance, MANY2ONE)(4)
+      - TO model-ver( metadatum BelongsTo model-ver, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this METADATUM is DELETED also
+    required:
+    - metaname
+    - metaval
+    properties:
+      metaname:
+        type: string
+      metaval:
+        type: string
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+  model:
+    description: |
+      Subgraph definition provided by ASDC to describe an inventory asset and its connections related to ASDC models, independent of version
+      ###### Related Nodes
+      - TO model( model-ver BelongsTo model, MANY2ONE)(1)
+      - FROM instance-group( instance-group Targets model, MANY2MANY)
+      - FROM model-ver( model-ver BelongsTo model, MANY2ONE)(1)
+      - FROM named-query( named-query AppliesTo model, ONE2MANY)
+      - FROM named-query-element( named-query-element IsA model, MANY2ONE)
+
+      -(1) IF this MODEL node is deleted, this FROM node is DELETED also
+      -MODEL cannot be deleted if related to INSTANCE-GROUP,NAMED-QUERY,NAMED-QUERY-ELEMENT
+
+    required:
+    - model-invariant-id
+    - model-type
+    properties:
+      model-invariant-id:
+        type: string
+        description: Unique identifier corresponding to the main definition of a model in ASDC
+      model-type:
+        type: string
+        description: Type of the model, e.g., service, resource, widget, etc.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      model-vers:
+        type: array
+        items:
+          $ref: "#/getDefinitions/model-ver"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  model-and-named-query-search:
+    description: |
+      ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+    properties:
+      query-parameters:
+        type: object
+        $ref: "#/getDefinitions/query-parameters"
+      instance-filters:
+        type: object
+        $ref: "#/getDefinitions/instance-filters"
+      secondary-filts:
+        type: object
+        $ref: "#/getDefinitions/secondary-filts"
+      top-node-type:
+        type: string
+      secondary-filter-cut-point:
+        type: string
+  model-constraint:
+    description: |
+      This is how we would capture constraints defining allowed sets of elements.
+      ###### Related Nodes
+      - TO model-element( model-constraint BelongsTo model-element, MANY2ONE)(4)
+      - FROM constrained-element-set( constrained-element-set BelongsTo model-constraint, MANY2ONE)(1)
+
+      -(1) IF this MODEL-CONSTRAINT node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this MODEL-CONSTRAINT is DELETED also
+    required:
+    - model-constraint-uuid
+    - constrained-element-set-uuid-to-replace
+    properties:
+      model-constraint-uuid:
+        type: string
+      constrained-element-set-uuid-to-replace:
+        type: string
+      constrained-element-sets:
+        type: array
+        items:
+          $ref: "#/getDefinitions/constrained-element-set"
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+  model-constraints:
+    properties:
+      model-constraint:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/model-constraint"
+  model-element:
+    description: |
+      Defines how other models combine to make up a higher-level model.
+      ###### Related Nodes
+      - TO element-choice-set( model-element BelongsTo element-choice-set, MANY2ONE)(4)
+      - TO model-element( model-element BelongsTo model-element, MANY2ONE)(4)
+      - TO model-ver( model-element IsA model-ver, MANY2ONE)
+      - TO model-ver( model-element BelongsTo model-ver, MANY2ONE)(4)
+      - FROM constrained-element-set( constrained-element-set BelongsTo model-element, MANY2ONE)(1)
+      - FROM model-constraint( model-constraint BelongsTo model-element, MANY2ONE)(1)
+      - FROM model-element( model-element BelongsTo model-element, MANY2ONE)(4)
+
+      -(1) IF this MODEL-ELEMENT node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this MODEL-ELEMENT is DELETED also
+    required:
+    - model-element-uuid
+    - new-data-del-flag
+    - cardinality
+    properties:
+      model-element-uuid:
+        type: string
+      new-data-del-flag:
+        type: string
+        description: Indicates whether this element was created as part of instantiation from this model
+      cardinality:
+        type: string
+        description: How many of this type of element are required/allowed
+      linkage-points:
+        type: string
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      model-elements:
+        type: array
+        items:
+          $ref: "#/getDefinitions/model-element"
+        description: Defines how other models combine to make up a higher-level model
+      model-constraints:
+        type: array
+        items:
+          $ref: "#/getDefinitions/model-constraint"
+        description: Describes new constraints on this model element that are not part of that model's definition
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  model-elements:
+    properties:
+      model-element:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/model-element"
+  model-ver:
+    description: |
+      Subgraph definition provided by ASDC to describe a specific version of an inventory asset and its connections related to ASDC models
+      ###### Related Nodes
+      - TO model( model-ver BelongsTo model, MANY2ONE)(4)
+      - FROM model-element( model-element IsA model-ver, MANY2ONE)
+      - FROM model-element( model-element BelongsTo model-ver, MANY2ONE)(1)
+      - FROM metadatum( metadatum BelongsTo model-ver, MANY2ONE)(1)
+
+      -(1) IF this MODEL-VER node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this MODEL-VER is DELETED also
+      -MODEL-VER cannot be deleted if related to MODEL-ELEMENT
+
+    required:
+    - model-version-id
+    - model-name
+    - model-version
+    properties:
+      model-version-id:
+        type: string
+        description: Unique identifier corresponding to one version of a model in ASDC
+      model-name:
+        type: string
+        description: Name of the model, which can change from version to version.
+      model-version:
+        type: string
+        description: Version
+      model-description:
+        type: string
+        description: Description
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      model-elements:
+        type: array
+        items:
+          $ref: "#/getDefinitions/model-element"
+      metadata:
+        type: array
+        items:
+          $ref: "#/getDefinitions/metadatum"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  model-vers:
+    properties:
+      model-ver:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/model-ver"
+  models:
+    description: |
+      Collection of subgraph definitions provided by ASDC to describe the inventory assets and their connections related to ASDC models
+    properties:
+      model:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/model"
+  multicast-configuration:
+    description: |
+      ###### Related Nodes
+      - FROM vlan( vlan Uses multicast-configuration, MANY2MANY)
+
+    required:
+    - multicast-configuration-id
+    - multicast-protocol
+    - rp-type
+    properties:
+      multicast-configuration-id:
+        type: string
+        description: Unique id of multicast configuration.
+      multicast-protocol:
+        type: string
+        description: protocol of multicast configuration
+      rp-type:
+        type: string
+        description: rp type of multicast configuration
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  multicast-configurations:
+    description: |
+      multicast configuration of generic-vnf ip-address
+    properties:
+      multicast-configuration:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/multicast-configuration"
+  named-queries:
+    properties:
+      named-query:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/named-query"
+  named-query:
+    description: |
+      TBD
+      ###### Related Nodes
+      - TO named-query( named-query-element BelongsTo named-query, ONE2ONE)(1)
+      - TO model( named-query AppliesTo model, ONE2MANY)
+      - FROM named-query-element( named-query-element BelongsTo named-query, ONE2ONE)(1)
+
+      -(1) IF this NAMED-QUERY node is deleted, this FROM node is DELETED also
+    required:
+    - named-query-uuid
+    - named-query-name
+    - named-query-version
+    properties:
+      named-query-uuid:
+        type: string
+      named-query-name:
+        type: string
+      named-query-version:
+        type: string
+      required-input-param:
+        type: string
+      description:
+        type: string
+      resource-version:
+        type: string
+      named-query-elements:
+        type: array
+        items:
+          $ref: "#/getDefinitions/named-query-element"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  named-query-element:
+    description: |
+      TBD
+      ###### Related Nodes
+      - TO named-query( named-query-element BelongsTo named-query, ONE2ONE)(4)
+      - TO model( named-query-element IsA model, MANY2ONE)
+      - TO named-query-element( named-query-element BelongsTo named-query-element, MANY2ONE)(4)
+      - FROM property-constraint( property-constraint BelongsTo named-query-element, MANY2ONE)(1)
+      - FROM related-lookup( related-lookup BelongsTo named-query-element, MANY2ONE)(1)
+      - FROM named-query-element( named-query-element BelongsTo named-query-element, MANY2ONE)(4)
+
+      -(1) IF this NAMED-QUERY-ELEMENT node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this NAMED-QUERY-ELEMENT is DELETED also
+    required:
+    - named-query-element-uuid
+    properties:
+      named-query-element-uuid:
+        type: string
+      property-collect-list:
+        type: string
+      resource-version:
+        type: string
+      property-limit-desc:
+        type: string
+      do-not-output:
+        type: string
+      named-query-elements:
+        type: array
+        items:
+          $ref: "#/getDefinitions/named-query-element"
+      related-lookups:
+        type: array
+        items:
+          $ref: "#/getDefinitions/related-lookup"
+      property-constraints:
+        type: array
+        items:
+          $ref: "#/getDefinitions/property-constraint"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  named-query-elements:
+    properties:
+      named-query-element:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/named-query-element"
+  network:
+    description: |
+      Namespace for network inventory resources.
+    properties:
+      logical-links:
+        type: array
+        items:
+          $ref: "#/getDefinitions/logical-link"
+      site-pair-sets:
+        type: array
+        items:
+          $ref: "#/getDefinitions/site-pair-set"
+      vpn-bindings:
+        type: array
+        items:
+          $ref: "#/getDefinitions/vpn-binding"
+      vpls-pes:
+        type: array
+        items:
+          $ref: "#/getDefinitions/vpls-pe"
+      multicast-configurations:
+        type: array
+        items:
+          $ref: "#/getDefinitions/multicast-configuration"
+      vces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/vce"
+      vnfcs:
+        type: array
+        items:
+          $ref: "#/getDefinitions/vnfc"
+      l3-networks:
+        type: array
+        items:
+          $ref: "#/getDefinitions/l3-network"
+      network-policies:
+        type: array
+        items:
+          $ref: "#/getDefinitions/network-policy"
+      generic-vnfs:
+        type: array
+        items:
+          $ref: "#/getDefinitions/generic-vnf"
+      lag-links:
+        type: array
+        items:
+          $ref: "#/getDefinitions/lag-link"
+      newvces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/newvce"
+      pnfs:
+        type: array
+        items:
+          $ref: "#/getDefinitions/pnf"
+      physical-links:
+        type: array
+        items:
+          $ref: "#/getDefinitions/physical-link"
+      ipsec-configurations:
+        type: array
+        items:
+          $ref: "#/getDefinitions/ipsec-configuration"
+      route-table-references:
+        type: array
+        items:
+          $ref: "#/getDefinitions/route-table-reference"
+      instance-groups:
+        type: array
+        items:
+          $ref: "#/getDefinitions/instance-group"
+      zones:
+        type: array
+        items:
+          $ref: "#/getDefinitions/zone"
+  network-policies:
+    properties:
+      network-policy:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/network-policy"
+  network-policy:
+    description: |
+      ###### Related Nodes
+      - FROM allotted-resource( allotted-resource Uses network-policy, ONE2ONE)
+      - FROM l3-network( l3-network Uses network-policy, MANY2MANY)
+
+    required:
+    - network-policy-id
+    properties:
+      network-policy-id:
+        type: string
+        description: UUID representing unique key to this instance
+      network-policy-fqdn:
+        type: string
+        description: Contrail FQDN for the policy
+      heat-stack-id:
+        type: string
+        description: ID for the openStack Heat instance
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  network-profile:
+    description: |
+      Network profile populated by SDN-GP for SNMP
+      ###### Related Nodes
+      - TO generic-vnf( network-profile AppliesTo generic-vnf, MANY2MANY)
+
+    required:
+    - nm-profile-name
+    properties:
+      nm-profile-name:
+        type: string
+        description: Unique name of network profile.
+      community-string:
+        type: string
+        description: Encrypted SNMP community string
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  network-profiles:
+    description: |
+      Collection of network profiles
+    properties:
+      network-profile:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/network-profile"
+  newvce:
+    description: |
+      This object fills in the gaps from vce that were incorporated into generic-vnf.  This object will be retired with vce.
+      ###### Related Nodes
+      - FROM l-interface( l-interface BelongsTo newvce, MANY2ONE)(1)
+
+      -(1) IF this NEWVCE node is deleted, this FROM node is DELETED also
+    required:
+    - vnf-id2
+    - vnf-name
+    - vnf-type
+    properties:
+      vnf-id2:
+        type: string
+        description: Unique id of VNF, can't use same attribute name right now until we promote this new object
+      vnf-name:
+        type: string
+        description: Name of VNF.
+      vnf-name2:
+        type: string
+        description: Alternate name of VNF.
+      vnf-type:
+        type: string
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational
+      license-key:
+        type: string
+        description: OBSOLETE -  do not use
+      ipv4-oam-address:
+        type: string
+        description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+      equipment-role:
+        type: string
+        description: Client should send valid enumerated value.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      ipv4-loopback0-address:
+        type: string
+        description: v4 Loopback0 address
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, mastered by MSO.
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance, managed by MSO
+      mso-catalog-key:
+        type: string
+        description: Corresponds to the SDN-C catalog id used to configure this VCE
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      l-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/l-interface"
+  newvces:
+    description: |
+      This object fills in the gaps from vce that were incorporated into generic-vnf.  This object will be retired with vce.
+    properties:
+      newvce:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/newvce"
+  nodes:
+    properties:
+      inventory-item-data:
+        type: array
+        items:
+          $ref: "#/getDefinitions/inventory-item-data"
+  notification-event:
+    properties:
+      cambria.partition:
+        type: string
+      notification-event-header:
+        type: object
+        $ref: "#/getDefinitions/notification-event-header"
+  notification-event-header:
+    properties:
+      id:
+        type: string
+      timestamp:
+        type: string
+      source-name:
+        type: string
+      domain:
+        type: string
+      sequence-number:
+        type: string
+      severity:
+        type: string
+      event-type:
+        type: string
+      version:
+        type: string
+      action:
+        type: string
+      entity-type:
+        type: string
+      top-entity-type:
+        type: string
+      entity-link:
+        type: string
+      status:
+        type: string
+  notify:
+    required:
+    - event-id
+    properties:
+      event-id:
+        type: string
+      node-type:
+        type: string
+      event-trigger:
+        type: string
+      key-data:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/key-data"
+      selflink:
+        type: string
+  oam-network:
+    description: |
+      OAM network, to be deprecated shortly.  Do not use for new purposes. 
+      ###### Related Nodes
+      - TO cloud-region( oam-network BelongsTo cloud-region, MANY2ONE)
+      - TO complex( oam-network AppliesTo complex, MANY2MANY)
+      - TO service-capability( oam-network AppliesTo service-capability, MANY2MANY)
+
+    required:
+    - network-uuid
+    - network-name
+    - cvlan-tag
+    properties:
+      network-uuid:
+        type: string
+        description: UUID of the network. Unique across a cloud-region
+      network-name:
+        type: string
+        description: Name of the network.
+      cvlan-tag:
+        type: integer
+        format: int64
+        description: cvlan-id
+      ipv4-oam-gateway-address:
+        type: string
+        description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+      ipv4-oam-gateway-address-prefix-length:
+        type: integer
+        format: int32
+        description: Used for VNF firewall rule so customer cannot send customer traffic over this oam network
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  oam-networks:
+    description: |
+      Collection of OAM networks, to be deprecated shortly.  Do not use for new purposes. 
+    properties:
+      oam-network:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/oam-network"
+  operational-environment:
+    description: |
+      It is a logical partition of the cloud which allows to have multiple environments in the production AIC.
+      ###### Related Nodes
+      - TO operational-environment( operational-environment Uses operational-environment, ONE2ONE)
+      - FROM operational-environment( operational-environment Uses operational-environment, ONE2ONE)
+
+    required:
+    - operational-environment-id
+    - operational-environment-name
+    - operational-environment-type
+    - operational-environment-status
+    - tenant-context
+    - workload-context
+    properties:
+      operational-environment-id:
+        type: string
+        description: UUID of an operational environment
+      operational-environment-name:
+        type: string
+        description: Operational Environment name
+      operational-environment-type:
+        type: string
+        description: Operational Environment Type.
+      operational-environment-status:
+        type: string
+        description: Status
+      tenant-context:
+        type: string
+        description: Tenant Context.
+      workload-context:
+        type: string
+        description: Workload Context.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  operational-environments:
+    description: |
+      a logical partition of the cloud which allows to have multiple environments in the production AIC.
+    properties:
+      operational-environment:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/operational-environment"
+  overloaded-model:
+    description: |
+      Allows for legacy POST of old-style and new-style models
+    required:
+    - model-invariant-id
+    - model-name-version-id
+    - model-type
+    - model-name
+    - model-id
+    - model-version
+    properties:
+      model-invariant-id:
+        type: string
+        description: Unique identifier corresponding to the main definition of a model in ASDC
+      model-name-version-id:
+        type: string
+        description: Unique identifier corresponding to one version of a model in ASDC
+      model-type:
+        type: string
+        description: Type of the model, e.g., service, resource, widget, etc.
+      model-name:
+        type: string
+        description: Name of the model, which can change from version to version.
+      model-id:
+        type: string
+        description: Invariant unique ID which does not change from version to version
+      model-version:
+        type: string
+        description: Version
+      model-description:
+        type: string
+        description: Description
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      model-vers:
+        type: object
+        $ref: "#/getDefinitions/model-vers"
+      relationship-list:
+        type: object
+        $ref: "#/getDefinitions/relationship-list"
+  owning-entities:
+    description: |
+      Collection of owning-entities
+    properties:
+      owning-entity:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/owning-entity"
+  owning-entity:
+    description: |
+      describes an owning-entity
+      ###### Related Nodes
+      - FROM service-instance( service-instance BelongsTo owning-entity, MANY2ONE)
+
+    required:
+    - owning-entity-id
+    - owning-entity-name
+    properties:
+      owning-entity-id:
+        type: string
+        description: UUID of an owning entity
+      owning-entity-name:
+        type: string
+        description: Owning entity name
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  p-interface:
+    description: |
+      Physical interface (e.g., nic)
+      ###### Related Nodes
+      - TO logical-link( p-interface LinksTo logical-link, MANY2ONE)
+      - TO physical-link( p-interface LinksTo physical-link, MANY2ONE)(2)
+      - TO pnf( p-interface BindsTo pnf, MANY2ONE)(4)
+      - TO pserver( p-interface BindsTo pserver, MANY2ONE)(4)
+      - TO vpls-pe( p-interface BindsTo vpls-pe, MANY2ONE)(4)
+      - FROM lag-interface( lag-interface Uses p-interface, MANY2MANY)
+      - FROM l-interface( l-interface BindsTo p-interface, MANY2ONE)(1)
+
+      -(1) IF this P-INTERFACE node is deleted, this FROM node is DELETED also
+      -(2) IF this P-INTERFACE node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this P-INTERFACE is DELETED also
+    required:
+    - interface-name
+    - in-maint
+    properties:
+      interface-name:
+        type: string
+        description: Name that identifies the physical interface
+      speed-value:
+        type: string
+        description: Captures the numeric part of the speed
+      speed-units:
+        type: string
+        description: Captures the units corresponding to the speed
+      port-description:
+        type: string
+        description: Nature of the services and connectivity on this port.
+      equipment-identifier:
+        type: string
+        description: CLEI or other specification for p-interface hardware.
+      interface-role:
+        type: string
+        description: Role specification for p-interface hardware.
+      interface-type:
+        type: string
+        description: Indicates the physical properties of the interface.
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true)
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      l-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/l-interface"
+  p-interfaces:
+    description: |
+      Collection of physical interfaces.
+    properties:
+      p-interface:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/p-interface"
+  physical-link:
+    description: |
+      Collection of physical connections, typically between p-interfaces
+      ###### Related Nodes
+      - FROM p-interface( p-interface LinksTo physical-link, MANY2ONE)(3)
+
+      -(3) IF this FROM node is deleted, this PHYSICAL-LINK is DELETED also
+    required:
+    - link-name
+    properties:
+      link-name:
+        type: string
+        description: e.g., hostnameA_p-connection_nameA_hostnameZ+p_connection-nameZ
+      speed-value:
+        type: string
+        description: Captures the numeric part of the speed
+      speed-units:
+        type: string
+        description: Captures the units corresponding to the speed
+      circuit-id:
+        type: string
+        description: Circuit it
+      dual-mode:
+        type: string
+        description: Dual access mode (e.g., primary, secondary
+      management-option:
+        type: string
+        description: To provide information on who manages this circuit. A&AI or 3rd party transport provider
+      service-provider-name:
+        type: string
+        description: Name of the service Provider on this link.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  physical-links:
+    description: |
+      Collection of physical connections, typically between p-interfaces
+    properties:
+      physical-link:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/physical-link"
+  platform:
+    description: |
+      describes a platform
+      ###### Related Nodes
+      - TO generic-vnf( platform Uses generic-vnf, MANY2MANY)
+
+    required:
+    - platform-name
+    properties:
+      platform-name:
+        type: string
+        description: Name of the platform
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  platforms:
+    description: |
+      Collection of platforms
+    properties:
+      platform:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/platform"
+  pnf:
+    description: |
+      PNF represents a physical network function. typically equipment used in the D1 world.
+      ###### Related Nodes
+      - TO complex( pnf LocatedIn complex, MANY2ONE)
+      - TO instance-group( pnf MemberOf instance-group, MANY2MANY)
+      - TO zone( pnf LocatedIn zone, MANY2ONE)
+      - FROM logical-link( logical-link BridgedTo pnf, MANY2MANY)
+      - FROM lag-interface( lag-interface BindsTo pnf, MANY2ONE)(1)
+      - FROM p-interface( p-interface BindsTo pnf, MANY2ONE)(1)
+      - FROM service-instance( service-instance ComposedOf pnf, ONE2MANY)
+
+      -(1) IF this PNF node is deleted, this FROM node is DELETED also
+    required:
+    - pnf-name
+    - in-maint
+    properties:
+      pnf-name:
+        type: string
+        description: unique name of Physical Network Function.
+      pnf-name2:
+        type: string
+        description: name of Physical Network Function.
+      pnf-name2-source:
+        type: string
+        description: source of name2
+      pnf-id:
+        type: string
+        description: id of pnf
+      equip-type:
+        type: string
+        description: Equipment type.  Source of truth should define valid values.
+      equip-vendor:
+        type: string
+        description: Equipment vendor.  Source of truth should define valid values.
+      equip-model:
+        type: string
+        description: Equipment model.  Source of truth should define valid values.
+      management-option:
+        type: string
+        description: identifier of managed by company or customer
+      ipaddress-v4-oam:
+        type: string
+        description: ipv4-oam-address with new naming convention for IP addresses
+      sw-version:
+        type: string
+        description: sw-version is the version of SW for the hosted application on the PNF.
+      in-maint:
+        type: boolean
+        description: Used to indicate whether or not this object is in maintenance mode (maintenance mode = true). This field (in conjunction with prov-status) is used to suppress alarms and vSCL on VNFs/VMs.
+      frame-id:
+        type: string
+        description: ID of the physical frame (relay rack) where pnf is installed.
+      serial-number:
+        type: string
+        description: Serial number of the device
+      ipaddress-v4-loopback-0:
+        type: string
+        description: IPV4 Loopback 0 address
+      ipaddress-v6-loopback-0:
+        type: string
+        description: IPV6 Loopback 0 address
+      ipaddress-v4-aim:
+        type: string
+        description: IPV4 AIM address
+      ipaddress-v6-aim:
+        type: string
+        description: IPV6 AIM address
+      ipaddress-v6-oam:
+        type: string
+        description: IPV6 OAM address
+      inv-status:
+        type: string
+        description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      prov-status:
+        type: string
+        description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV]
+      nf-role:
+        type: string
+        description: Nf Role is the role performed by this instance in the network.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      p-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/p-interface"
+      lag-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/lag-interface"
+  pnfs:
+    description: |
+      Collection of Physical Network Functions.
+    properties:
+      pnf:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/pnf"
+  port-group:
+    description: |
+      Used to capture the network interfaces of this VCE
+      ###### Related Nodes
+      - TO vce( port-group BelongsTo vce, MANY2ONE)(4)
+      - FROM cvlan-tag( cvlan-tag BelongsTo port-group, MANY2ONE)(1)
+
+      -(1) IF this PORT-GROUP node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this PORT-GROUP is DELETED also
+    required:
+    - interface-id
+    - orchestration-status
+    properties:
+      interface-id:
+        type: string
+        description: Unique ID of the interface
+      neutron-network-id:
+        type: string
+        description: Neutron network id of this Interface
+      neutron-network-name:
+        type: string
+        description: Neutron network name of this Interface
+      interface-role:
+        type: string
+        description: Role assigned to this Interface, should use values as defined in ECOMP Yang models.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      port-group-id:
+        type: string
+        description: Unique ID for port group in vmware
+      port-group-name:
+        type: string
+        description: Likely to duplicate value of neutron network name
+      switch-name:
+        type: string
+        description: DVS or standard switch name (should be non-null for port groups associated with DVS)
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, mastered by MSO
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance, managed by MSO
+      mso-catalog-key:
+        type: string
+        description: Corresponds to the SDN-C catalog id used to configure this VCE
+      cvlan-tags:
+        type: array
+        items:
+          $ref: "#/getDefinitions/cvlan-tag-entry"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  port-groups:
+    properties:
+      port-group:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/port-group"
+  project:
+    description: |
+      describes the project
+      ###### Related Nodes
+      - TO service-instance( project Uses service-instance, ONE2MANY)
+
+    required:
+    - project-name
+    properties:
+      project-name:
+        type: string
+        description: Name of the project deploying a service
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  projects:
+    description: |
+      Collection of projects
+    properties:
+      project:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/project"
+  properties:
+    description: |
+      Property holder for query properties or instance properties
+    properties:
+      property-name:
+        type: string
+      property-value:
+        type: string
+  property-constraint:
+    description: |
+      TBD
+      ###### Related Nodes
+      - TO named-query-element( property-constraint BelongsTo named-query-element, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this PROPERTY-CONSTRAINT is DELETED also
+    required:
+    - property-constraint-uuid
+    - constraint-type
+    - property-name
+    - property-value
+    properties:
+      property-constraint-uuid:
+        type: string
+      constraint-type:
+        type: string
+      property-name:
+        type: string
+      property-value:
+        type: string
+      resource-version:
+        type: string
+  property-constraints:
+    properties:
+      property-constraint:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/property-constraint"
+  pserver:
+    description: |
+      Compute host whose hostname must be unique and must exactly match what is sent as a relationship to a vserver.
+      ###### Related Nodes
+      - TO group-assignment( pserver MemberOf group-assignment, MANY2ONE)
+      - TO availability-zone( pserver MemberOf availability-zone, MANY2ONE)
+      - TO cloud-region( pserver LocatedIn cloud-region, MANY2ONE)
+      - TO complex( pserver LocatedIn complex, MANY2ONE)
+      - TO zone( pserver LocatedIn zone, MANY2ONE)
+      - FROM generic-vnf( generic-vnf HostedOn pserver, MANY2MANY)
+      - FROM logical-link( logical-link BridgedTo pserver, MANY2MANY)
+      - FROM lag-interface( lag-interface BindsTo pserver, MANY2ONE)(1)
+      - FROM p-interface( p-interface BindsTo pserver, MANY2ONE)(1)
+      - FROM vserver( vserver HostedOn pserver, MANY2ONE)
+
+      -(1) IF this PSERVER node is deleted, this FROM node is DELETED also
+      -PSERVER cannot be deleted if related to GENERIC-VNF,LOGICAL-LINK,VSERVER,GROUP-ASSIGNMENT
+
+    required:
+    - hostname
+    - in-maint
+    properties:
+      hostname:
+        type: string
+        description: Value from executing hostname on the compute node.
+      ptnii-equip-name:
+        type: string
+        description: PTNII name
+      number-of-cpus:
+        type: integer
+        format: int32
+        description: Number of cpus
+      disk-in-gigabytes:
+        type: integer
+        format: int32
+        description: Disk size, in GBs
+      ram-in-megabytes:
+        type: integer
+        format: int32
+        description: RAM size, in MBs
+      equip-type:
+        type: string
+        description: Equipment type.  Source of truth should define valid values.
+      equip-vendor:
+        type: string
+        description: Equipment vendor.  Source of truth should define valid values.
+      equip-model:
+        type: string
+        description: Equipment model.  Source of truth should define valid values.
+      fqdn:
+        type: string
+        description: Fully-qualified domain name
+      pserver-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      ipv4-oam-address:
+        type: string
+        description: Used to configure device, also used for troubleshooting and is IP used for traps generated by device.
+      serial-number:
+        type: string
+        description: Serial number, may be queried
+      ipaddress-v4-loopback-0:
+        type: string
+        description: IPV4 Loopback 0 address
+      ipaddress-v6-loopback-0:
+        type: string
+        description: IPV6 Loopback 0 address
+      ipaddress-v4-aim:
+        type: string
+        description: IPV4 AIM address
+      ipaddress-v6-aim:
+        type: string
+        description: IPV6 AIM address
+      ipaddress-v6-oam:
+        type: string
+        description: IPV6 OAM address
+      inv-status:
+        type: string
+        description: CANOPI's inventory status.  Only set with values exactly as defined by CANOPI.
+      pserver-id:
+        type: string
+        description: ID of Pserver
+      internet-topology:
+        type: string
+        description: internet topology of Pserver
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true). This field (in conjunction with prov-status) is used to suppress alarms and vSCL on VNFs/VMs.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      pserver-name2:
+        type: string
+        description: alternative pserver name
+      purpose:
+        type: string
+        description: purpose of pserver
+      prov-status:
+        type: string
+        description: Prov Status of this device (not under canopi control) Valid values [PREPROV/NVTPROV/PROV]
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      p-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/p-interface"
+      lag-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/lag-interface"
+  pservers:
+    description: |
+      Collection of compute hosts.
+    properties:
+      pserver:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/pserver"
+  query-parameters:
+    description: |
+      QueryParameters for performing a named-query or model query
+    properties:
+      named-query:
+        type: object
+        $ref: "#/getDefinitions/named-query"
+      overloaded-model:
+        type: object
+        $ref: "#/getDefinitions/overloaded-model"
+  related-lookup:
+    description: |
+      TBD
+      ###### Related Nodes
+      - TO named-query-element( related-lookup BelongsTo named-query-element, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this RELATED-LOOKUP is DELETED also
+    required:
+    - related-lookup-uuid
+    - source-node-type
+    - source-node-property
+    - target-node-type
+    - target-node-property
+    properties:
+      related-lookup-uuid:
+        type: string
+      source-node-type:
+        type: string
+      source-node-property:
+        type: string
+      target-node-type:
+        type: string
+      target-node-property:
+        type: string
+      property-collect-list:
+        type: string
+      resource-version:
+        type: string
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  related-lookups:
+    properties:
+      related-lookup:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/related-lookup"
+  related-to-property:
+    properties:
+      property-key:
+        type: string
+        description: Key part of a key/value pair
+      property-value:
+        type: string
+        description: Value part of a key/value pair
+  relationship:
+    properties:
+      related-to:
+        type: string
+        description: A keyword provided by A&AI to indicate type of node.
+      related-link:
+        type: string
+        description: URL to the object in A&AI.
+      relationship-data:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/relationship-data"
+      related-to-property:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/related-to-property"
+  relationship-data:
+    required:
+    - relationship-key
+    - relationship-value
+    properties:
+      relationship-key:
+        type: string
+        description: A keyword provided by A&AI to indicate an attribute.
+      relationship-value:
+        type: string
+        description: Value of the attribute.
+  relationship-list:
+    properties:
+      relationship:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/relationship"
+  reserved-prop-names:
+    description: |
+      Internal map to define some reserved properties of a vertex
+    properties:
+      last-mod-source-of-truth:
+        type: string
+      aai-node-type:
+        type: string
+      aai-created-ts:
+        type: integer
+        format: int64
+      aai-unique-key:
+        type: string
+      aai-last-mod-ts:
+        type: integer
+        format: int64
+      source-of-truth:
+        type: string
+      aai-uri:
+        type: string
+  response-list:
+    description: |
+      Response container for the results of a named-query or model query
+    properties:
+      inventory-response-items:
+        type: object
+        $ref: "#/getDefinitions/inventory-response-items"
+  result-data:
+    properties:
+      resource-type:
+        type: string
+        description: The specific type of node in the A&AI graph
+      resource-link:
+        type: string
+        description: The URL to the specific resource
+  route-table-reference:
+    description: |
+      Openstack route table reference.
+      ###### Related Nodes
+      - FROM l3-network( l3-network Uses route-table-reference, MANY2MANY)
+
+    required:
+    - route-table-reference-id
+    - route-table-reference-fqdn
+    properties:
+      route-table-reference-id:
+        type: string
+        description: Route Table Reference id, UUID assigned to this instance.
+      route-table-reference-fqdn:
+        type: string
+        description: FQDN entry in the route table.
+      resource-version:
+        type: string
+        description: Concurrency value
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  route-table-references:
+    description: |
+      Collection of openstack route table references
+    properties:
+      route-table-reference:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/route-table-reference"
+  route-target:
+    description: |
+      Route target information
+      ###### Related Nodes
+      - TO vpn-binding( route-target BelongsTo vpn-binding, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this ROUTE-TARGET is DELETED also
+    required:
+    - global-route-target
+    - route-target-role
+    properties:
+      global-route-target:
+        type: string
+        description: Number used to identify an RT, globally unique in the network
+      route-target-role:
+        type: string
+        description: Role assigned to this route target
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  route-targets:
+    description: |
+      Collection of route target information
+    properties:
+      route-target:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/route-target"
+  routing-instance:
+    description: |
+      ###### Related Nodes
+      - TO site-pair-set( routing-instance BelongsTo site-pair-set, MANY2ONE)(4)
+      - FROM site-pair( site-pair BelongsTo routing-instance, MANY2ONE)(1)
+
+      -(1) IF this ROUTING-INSTANCE node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this ROUTING-INSTANCE is DELETED also
+    required:
+    - routing-instance-id
+    properties:
+      routing-instance-id:
+        type: string
+        description: Unique id of routing instance
+      rpm-owner:
+        type: string
+        description: rpm owner
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      site-pairs:
+        type: array
+        items:
+          $ref: "#/getDefinitions/site-pair"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  routing-instances:
+    description: |
+      set of probes related to generic-vnf routing instance
+    properties:
+      routing-instance:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/routing-instance"
+  sdn-zone-response:
+    properties:
+      oam-networks:
+        type: object
+        $ref: "#/getDefinitions/oam-networks"
+      az-and-dvs-switches:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/az-and-dvs-switches"
+  search:
+    properties:
+      edge-tag-query-result:
+        type: object
+        $ref: "#/getDefinitions/edge-tag-query-result"
+      edge-tag-query-request:
+        type: object
+        $ref: "#/getDefinitions/edge-tag-query-request"
+      search-results:
+        type: object
+        $ref: "#/getDefinitions/search-results"
+      sdn-zone-response:
+        type: object
+        $ref: "#/getDefinitions/sdn-zone-response"
+  search-results:
+    properties:
+      result-data:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/result-data"
+  secondary-filt:
+    description: |
+      SecondaryFilt for performing a named-query or model query
+  secondary-filter:
+    properties:
+      property-name:
+        type: string
+      filter-type:
+        type: string
+      property-value:
+        type: string
+  secondary-filts:
+    description: |
+      SecondaryFilts for performing a named-query or model query
+    properties:
+      secondary-filt:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/secondary-filt"
+  segmentation-assignment:
+    description: |
+      Openstack segmentation assignment.
+      ###### Related Nodes
+      - TO l3-network( segmentation-assignment BelongsTo l3-network, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this SEGMENTATION-ASSIGNMENT is DELETED also
+    required:
+    - segmentation-id
+    properties:
+      segmentation-id:
+        type: string
+        description: Route Table Reference id, UUID assigned to this instance.
+      resource-version:
+        type: string
+        description: Concurrency value
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  segmentation-assignments:
+    description: |
+      Collection of openstack segmentation assignments
+    properties:
+      segmentation-assignment:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/segmentation-assignment"
+  service:
+    description: |
+      Stand-in for service model definitions.  Likely to be deprecated in favor of models from ASDC.  Does not strictly map to ASDC services.
+    required:
+    - service-id
+    - service-description
+    properties:
+      service-id:
+        type: string
+        description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+      service-description:
+        type: string
+        description: Description of the service
+      service-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      service-version:
+        type: string
+        description: service version
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  service-capabilities:
+    description: |
+      Collection of service capabilities.
+    properties:
+      service-capability:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/service-capability"
+  service-capability:
+    description: |
+      Early definition of server/resource pairings, likely to be replaced by models.  No new use should be made of this.
+      ###### Related Nodes
+      - FROM availability-zone( availability-zone AppliesTo service-capability, MANY2MANY)
+      - FROM oam-network( oam-network AppliesTo service-capability, MANY2MANY)
+
+      -SERVICE-CAPABILITY cannot be deleted if related to AVAILABILITY-ZONE,OAM-NETWORK
+
+    required:
+    - service-type
+    - vnf-type
+    properties:
+      service-type:
+        type: string
+        description: This gets defined by others to provide a unique ID for the service, we accept what is sent.
+      vnf-type:
+        type: string
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  service-design-and-creation:
+    description: |
+      Namespace for objects managed by ASDC
+    properties:
+      vnf-images:
+        type: array
+        items:
+          $ref: "#/getDefinitions/vnf-image"
+      services:
+        type: array
+        items:
+          $ref: "#/getDefinitions/service"
+      service-capabilities:
+        type: array
+        items:
+          $ref: "#/getDefinitions/service-capability"
+      models:
+        type: array
+        items:
+          $ref: "#/getDefinitions/model"
+      named-queries:
+        type: array
+        items:
+          $ref: "#/getDefinitions/named-query"
+  service-instance:
+    description: |
+      Instance of a service
+      ###### Related Nodes
+      - TO generic-vnf( service-instance ComposedOf generic-vnf, ONE2MANY)
+      - TO l3-network( service-instance ComposedOf l3-network, ONE2MANY)
+      - TO allotted-resource( service-instance Uses allotted-resource, MANY2MANY)
+      - TO connector( service-instance Uses connector, MANY2MANY)
+      - TO ctag-assignment( service-instance Uses ctag-assignment, ONE2MANY)
+      - TO cvlan-tag( service-instance ComposedOf cvlan-tag, MANY2MANY)
+      - TO instance-group( service-instance MemberOf instance-group, MANY2MANY)
+      - TO logical-link( service-instance Uses logical-link, ONE2MANY)(2)
+      - TO pnf( service-instance ComposedOf pnf, ONE2MANY)
+      - TO service-instance( service-instance ComposedOf service-instance, ONE2MANY)
+      - TO vlan( service-instance ComposedOf vlan, ONE2MANY)
+      - TO service-subscription( service-instance BelongsTo service-subscription, MANY2ONE)(4)
+      - TO vce( service-instance ComposedOf vce, ONE2MANY)
+      - FROM allotted-resource( allotted-resource BelongsTo service-instance, MANY2ONE)(1)
+      - FROM metadatum( metadatum BelongsTo service-instance, MANY2ONE)(1)
+      - FROM service-instance( service-instance ComposedOf service-instance, ONE2MANY)
+
+      -(1) IF this SERVICE-INSTANCE node is deleted, this FROM node is DELETED also
+      -(2) IF this SERVICE-INSTANCE node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this SERVICE-INSTANCE is DELETED also
+    required:
+    - service-instance-id
+    properties:
+      service-instance-id:
+        type: string
+        description: Uniquely identifies this instance of a service
+      service-instance-name:
+        type: string
+        description: This field will store a name assigned to the service-instance.
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      widget-model-id:
+        type: string
+        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+      widget-model-version:
+        type: string
+        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+      bandwidth-total:
+        type: string
+        description: Indicates the total bandwidth to be used for this service.
+      bandwidth-up-wan1:
+        type: string
+        description: indicates the upstream bandwidth this service will use on the WAN1 port of the physical device.
+      bandwidth-down-wan1:
+        type: string
+        description: indicates the downstream bandwidth this service will use on the WAN1 port of the physical device.
+      bandwidth-up-wan2:
+        type: string
+        description: indicates the upstream bandwidth this service will use on the WAN2 port of the physical device.
+      bandwidth-down-wan2:
+        type: string
+        description: indicates the downstream bandwidth this service will use on the WAN2 port of the physical device.
+      vhn-portal-url:
+        type: string
+        description: URL customers will use to access the vHN Portal.
+      service-instance-location-id:
+        type: string
+        description: An identifier that customers assign to the location where this service is being used.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      selflink:
+        type: string
+        description: Path to the controller object.
+      orchestration-status:
+        type: string
+        description: Orchestration status of this service.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      metadata:
+        type: array
+        items:
+          $ref: "#/getDefinitions/metadatum"
+      allotted-resources:
+        type: array
+        items:
+          $ref: "#/getDefinitions/allotted-resource"
+  service-instances:
+    description: |
+      Collection of service instances
+    properties:
+      service-instance:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/service-instance"
+  service-subscription:
+    description: |
+      Object that group service instances.
+      ###### Related Nodes
+      - TO customer( service-subscription BelongsTo customer, MANY2ONE)(4)
+      - TO tenant( service-subscription Uses tenant, MANY2MANY)
+      - FROM service-instance( service-instance BelongsTo service-subscription, MANY2ONE)(1)
+
+      -(1) IF this SERVICE-SUBSCRIPTION node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this SERVICE-SUBSCRIPTION is DELETED also
+    required:
+    - service-type
+    properties:
+      service-type:
+        type: string
+        description: Value defined by orchestration to identify this service across ECOMP.
+      temp-ub-sub-account-id:
+        type: string
+        description: This property will be deleted from A&AI in the near future. Only stop gap solution.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      service-instances:
+        type: array
+        items:
+          $ref: "#/getDefinitions/service-instance"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  service-subscriptions:
+    description: |
+      Collection of objects that group service instances.
+    properties:
+      service-subscription:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/service-subscription"
+  services:
+    description: |
+      Collection of service model definitions.  Likely to be deprecated in favor of models from ASDC.
+    properties:
+      service:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/service"
+  site-pair:
+    description: |
+      ###### Related Nodes
+      - TO routing-instance( site-pair BelongsTo routing-instance, MANY2ONE)(4)
+      - FROM class-of-service( class-of-service BelongsTo site-pair, MANY2ONE)(1)
+
+      -(1) IF this SITE-PAIR node is deleted, this FROM node is DELETED also
+      -(4) IF this TO node is deleted, this SITE-PAIR is DELETED also
+    required:
+    - site-pair-id
+    properties:
+      site-pair-id:
+        type: string
+        description: unique identifier of probe
+      source-ip:
+        type: string
+        description: Prefix address
+      destination-ip:
+        type: string
+        description: Prefix address
+      ip-version:
+        type: string
+        description: ip version, v4, v6
+      destination-hostname:
+        type: string
+        description: Hostname of the destination equipment to which SLAs are measured against.
+      destination-equip-type:
+        type: string
+        description: The type of destinatination equipment. Could be Router, etc.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      classes-of-service:
+        type: array
+        items:
+          $ref: "#/getDefinitions/class-of-service"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  site-pair-set:
+    description: |
+      Set of instances for probes used to measure service level agreements
+      ###### Related Nodes
+      - TO generic-vnf( site-pair-set AppliesTo generic-vnf, MANY2MANY)
+      - FROM routing-instance( routing-instance BelongsTo site-pair-set, MANY2ONE)(1)
+
+      -(1) IF this SITE-PAIR-SET node is deleted, this FROM node is DELETED also
+    required:
+    - site-pair-set-id
+    properties:
+      site-pair-set-id:
+        type: string
+        description: Unique id of site pair set.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      routing-instances:
+        type: array
+        items:
+          $ref: "#/getDefinitions/routing-instance"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  site-pair-sets:
+    description: |
+      Collection of sets of instances for probes related to generic-vnf
+    properties:
+      site-pair-set:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/site-pair-set"
+  site-pairs:
+    description: |
+      probe within a set
+    properties:
+      site-pair:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/site-pair"
+  snapshot:
+    description: |
+      Openstack snapshot
+      ###### Related Nodes
+      - TO cloud-region( snapshot BelongsTo cloud-region, MANY2ONE)
+      - FROM vserver( vserver Uses snapshot, ONE2ONE)
+
+    required:
+    - snapshot-id
+    properties:
+      snapshot-id:
+        type: string
+        description: Snapshot id, this is the key UUID assoc associated in glance with the snapshots.
+      snapshot-name:
+        type: string
+        description: Snapshot name
+      snapshot-architecture:
+        type: string
+        description: Operating system architecture
+      snapshot-os-distro:
+        type: string
+        description: The common name of the operating system distribution in lowercase
+      snapshot-os-version:
+        type: string
+        description: The operating system version as specified by the distributor.
+      application:
+        type: string
+        description: The application that the image instantiates.
+      application-vendor:
+        type: string
+        description: The vendor of the application.
+      application-version:
+        type: string
+        description: The version of the application.
+      snapshot-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      prev-snapshot-id:
+        type: string
+        description: This field contains the UUID of the previous snapshot (if any).
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  snapshots:
+    description: |
+      Collection of openstack snapshots
+    properties:
+      snapshot:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/snapshot"
+  sriov-pf:
+    description: |
+      SR-IOV Physical Function
+      ###### Related Nodes
+      - TO p-interface( sriov-pf BelongsTo p-interface, ONE2ONE)(4)
+      - FROM sriov-vf( sriov-vf Uses sriov-pf, MANY2ONE)
+
+      -(4) IF this TO node is deleted, this SRIOV-PF is DELETED also
+    required:
+    - pf-pci-id
+    properties:
+      pf-pci-id:
+        type: string
+        description: Identifier for the sriov-pf
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  sriov-pfs:
+    description: |
+      Collection of SR-IOV Physical Functions.
+    properties:
+      sriov-pf:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/sriov-pf"
+  sriov-vf:
+    description: |
+      SR-IOV Virtual Function (not to be confused with virtual network function)
+      ###### Related Nodes
+      - TO l-interface( sriov-vf BelongsTo l-interface, ONE2ONE)(4)
+
+      -(4) IF this TO node is deleted, this SRIOV-VF is DELETED also
+    required:
+    - pci-id
+    properties:
+      pci-id:
+        type: string
+        description: PCI ID used to identify the sriov-vf
+      vf-vlan-filter:
+        type: string
+        description: This metadata provides option to specify list of VLAN filters applied on VF to pass the traffic to VM.
+      vf-mac-filter:
+        type: string
+        description: When MAC filters are specified, VF-agent service configures VFs to do MAC level filtering before the traffic is passed to VM.
+      vf-vlan-strip:
+        type: boolean
+        description: When this field is set to true, VF will configured to strip the outer TAG before the traffic is passed to VM.
+      vf-vlan-anti-spoof-check:
+        type: boolean
+        description: This option ensures anti VLAN spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+      vf-mac-anti-spoof-check:
+        type: boolean
+        description: This option ensures anti MAC spoof checks are done at the VF level to comply with security. The disable check will also be honored per the VNF needs for trusted VMs.
+      vf-mirrors:
+        type: string
+        description: This option defines the set of Mirror objects which essentially mirrors the traffic from source to set of collector VNF Ports.
+      vf-broadcast-allow:
+        type: boolean
+        description: This option, if set to true, sets the VF in promiscuous mode and allows all broadcast traffic to reach the VM
+      vf-unknown-multicast-allow:
+        type: boolean
+        description: This option, if set to true, sets the VF in promiscuous mode and allows unknown multicast traffic to reach the VM
+      vf-unknown-unicast-allow:
+        type: boolean
+        description: This option, if set to true, sets the VF in promiscuous mode and allows unknown unicast traffic to reach the VM
+      vf-insert-stag:
+        type: boolean
+        description: This option, if set to true, instructs to insert outer tag after traffic comes out of VM.
+      vf-link-status:
+        type: string
+        description: This option is used to set the link status.  Valid values as of 1607 are on, off, and auto.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      neutron-network-id:
+        type: string
+        description: Neutron network id of the interface
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  sriov-vfs:
+    description: |
+      Collection of SR-IOV Virtual Functions.
+    properties:
+      sriov-vf:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/sriov-vf"
+  start-node-filter:
+    properties:
+      property-name:
+        type: string
+      property-value:
+        type: string
+  subnet:
+    description: |
+      ###### Related Nodes
+      - TO l3-network( subnet BelongsTo l3-network, MANY2ONE)(4)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list MemberOf subnet, MANY2MANY)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list MemberOf subnet, MANY2MANY)
+
+      -(4) IF this TO node is deleted, this SUBNET is DELETED also
+      -SUBNET cannot be deleted if related to L3-INTERFACE-IPV4-ADDRESS-LIST,L3-INTERFACE-IPV6-ADDRESS-LIST
+
+    required:
+    - subnet-id
+    - dhcp-enabled
+    properties:
+      subnet-id:
+        type: string
+        description: Subnet ID, should be UUID.
+      subnet-name:
+        type: string
+        description: Name associated with the subnet.
+      neutron-subnet-id:
+        type: string
+        description: Neutron id of this subnet
+      gateway-address:
+        type: string
+        description: gateway ip address
+      network-start-address:
+        type: string
+        description: network start address
+      cidr-mask:
+        type: string
+        description: cidr mask
+      ip-version:
+        type: string
+        description: ip version
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, mastered by MSO
+      dhcp-enabled:
+        type: boolean
+        description: dhcp enabled
+      dhcp-start:
+        type: string
+        description: the start address reserved for use by dhcp
+      dhcp-end:
+        type: string
+        description: the last address reserved for use by dhcp
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  subnets:
+    properties:
+      subnet:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/subnet"
+  tagged-inventory-item-list:
+    properties:
+      inventory-item:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/inventory-item"
+  tenant:
+    description: |
+      Openstack tenant
+      ###### Related Nodes
+      - TO cloud-region( tenant BelongsTo cloud-region, MANY2ONE)
+      - TO group-assignment( tenant MemberOf group-assignment, MANY2MANY)
+      - TO l3-network( tenant Uses l3-network, MANY2MANY)
+      - TO volume-group( tenant DependsOn volume-group, ONE2MANY)
+      - FROM service-subscription( service-subscription Uses tenant, MANY2MANY)
+      - FROM vserver( vserver BelongsTo tenant, MANY2ONE)
+
+      -TENANT cannot be deleted if related to VSERVER
+
+    required:
+    - tenant-id
+    - tenant-name
+    properties:
+      tenant-id:
+        type: string
+        description: Unique id relative to the cloud-region.
+      tenant-name:
+        type: string
+        description: Readable name of tenant
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      vservers:
+        type: array
+        items:
+          $ref: "#/getDefinitions/vserver"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  tenants:
+    description: |
+      Collection of openstack tenants.
+    properties:
+      tenant:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/tenant"
+  tunnel-xconnect:
+    description: |
+      Represents the specifics of a tunnel cross connect piece of a resource that gets separately allotted
+      ###### Related Nodes
+      - TO allotted-resource( tunnel-xconnect BelongsTo allotted-resource, ONE2ONE)(4)
+
+      -(4) IF this TO node is deleted, this TUNNEL-XCONNECT is DELETED also
+    required:
+    - id
+    - bandwidth-up-wan1
+    - bandwidth-down-wan1
+    - bandwidth-up-wan2
+    - bandwidth-down-wan2
+    properties:
+      id:
+        type: string
+        description: Allotted Resource id UUID assigned to this instance.
+      bandwidth-up-wan1:
+        type: string
+        description: The WAN uplink bandwidth for WAN1
+      bandwidth-down-wan1:
+        type: string
+        description: The WAN downlink bandwidth for WAN1
+      bandwidth-up-wan2:
+        type: string
+        description: The WAN uplink bandwidth for WAN2
+      bandwidth-down-wan2:
+        type: string
+        description: The WAN downlink bandwidth for WAN2
+      resource-version:
+        type: string
+        description: Concurrency value
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  tunnel-xconnects:
+    description: |
+      This object is used to store the specific tunnel cross connect aspects of an allotted resource
+    properties:
+      tunnel-xconnect:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/tunnel-xconnect"
+  update:
+    description: |
+      Serves a PATCH like function.  Does not enforce concurrency control.  Clear each usage with AAI team.
+    required:
+    - update-node-type
+    properties:
+      update-node-type:
+        type: string
+      update-node-key:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/update-node-key"
+      update-node-uri:
+        type: string
+      action:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/action"
+  update-node-key:
+    properties:
+      key-name:
+        type: string
+      key-value:
+        type: string
+  vce:
+    description: |
+      Virtual Customer Edge Router, used specifically for Gamma.  This object is deprecated.
+      ###### Related Nodes
+      - TO availability-zone( vce Uses availability-zone, MANY2MANY)
+      - TO complex( vce LocatedIn complex, MANY2MANY)
+      - TO vserver( vce HostedOn vserver, ONE2MANY)
+      - FROM entitlement( entitlement BelongsTo vce, MANY2ONE)(1)
+      - FROM license( license BelongsTo vce, MANY2ONE)(1)
+      - FROM port-group( port-group BelongsTo vce, MANY2ONE)(1)
+      - FROM service-instance( service-instance ComposedOf vce, ONE2MANY)
+
+      -(1) IF this VCE node is deleted, this FROM node is DELETED also
+    required:
+    - vnf-id
+    - vnf-name
+    - vnf-type
+    properties:
+      vnf-id:
+        type: string
+        description: Unique id of VNF.  This is unique across the graph.
+      vnf-name:
+        type: string
+        description: Name of VNF.
+      vnf-name2:
+        type: string
+        description: Alternate name of VNF.
+      vnf-type:
+        type: string
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      service-id:
+        type: string
+        description: Unique identifier of service, does not strictly map to ASDC services, SOON TO BE DEPRECATED.
+      regional-resource-zone:
+        type: string
+        description: Regional way of organizing pservers, source of truth should define values
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+      operational-status:
+        type: string
+        description: Indicator for whether the resource is considered operational
+      license-key:
+        type: string
+        description: OBSOLETE -  do not use
+      equipment-role:
+        type: string
+        description: Network role being played by this VNF
+      orchestration-status:
+        type: string
+        description: Orchestration status of this VNF, mastered by MSO
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance, managed by MSO
+      mso-catalog-key:
+        type: string
+        description: Corresponds to the SDN-C catalog id used to configure this VCE
+      vpe-id:
+        type: string
+        description: Unique ID of VPE connected to this VCE.
+      v6-vce-wan-address:
+        type: string
+        description: Valid v6 IP address for the WAN Link on this router.  Implied length of /64.
+      ipv4-oam-address:
+        type: string
+        description: Address tail-f uses to configure vce, also used for troubleshooting and is IP used for traps generated by VCE.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      ipv4-loopback0-address:
+        type: string
+        description: Loopback0 address
+      entitlement-resource-uuid:
+        type: string
+        description: OBSOLETE -  see child relationships
+      port-groups:
+        type: array
+        items:
+          $ref: "#/getDefinitions/port-group"
+      licenses:
+        type: array
+        items:
+          $ref: "#/getDefinitions/license"
+      entitlements:
+        type: array
+        items:
+          $ref: "#/getDefinitions/entitlement"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  vces:
+    description: |
+      Collection of Virtual Customer Edge Routers, used specifically for Gamma.  This object is deprecated.
+    properties:
+      vce:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/vce"
+  vf-module:
+    description: |
+      a deployment unit of VNFCs
+      ###### Related Nodes
+      - TO generic-vnf( vf-module BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO l3-network( vf-module DependsOn l3-network, MANY2MANY)
+      - TO vnfc( vf-module Uses vnfc, ONE2MANY)
+      - TO volume-group( vf-module Uses volume-group, ONE2ONE)
+      - TO vserver( vf-module Uses vserver, ONE2MANY)
+
+      -(4) IF this TO node is deleted, this VF-MODULE is DELETED also
+      -VF-MODULE cannot be deleted if related to VNFC
+
+    required:
+    - vf-module-id
+    - is-base-vf-module
+    properties:
+      vf-module-id:
+        type: string
+        description: Unique ID of vf-module.
+      vf-module-name:
+        type: string
+        description: Name of vf-module
+      heat-stack-id:
+        type: string
+        description: Heat stack id corresponding to this instance.
+      orchestration-status:
+        type: string
+        description: orchestration status of this vf-module, mastered by MSO
+      is-base-vf-module:
+        type: boolean
+        description: used to indicate whether or not this object is base vf module
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      model-invariant-id:
+        type: string
+        description: the ASDC model id for this resource or service model.
+      model-version-id:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      persona-model-version:
+        type: string
+        description: the ASDC model version for this resource or service model.
+      model-customization-id:
+        type: string
+        description: captures the id of all the configuration used to customize the resource for the service.
+      widget-model-id:
+        type: string
+        description: the ASDC data dictionary widget model. This maps directly to the A&AI widget.
+      widget-model-version:
+        type: string
+        description: the ASDC data dictionary version of the widget model.This maps directly to the A&AI version of the widget.
+      contrail-service-instance-fqdn:
+        type: string
+        description: the Contrail unique ID for a service-instance
+      module-index:
+        type: integer
+        format: int32
+        description: the index will track the number of modules of a given type that have been deployed in a VNF, starting with 0, and always choosing the lowest available digit
+      selflink:
+        type: string
+        description: Path to the controller object.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  vf-modules:
+    description: |
+      Collection of vf-modules, a deployment unit of VNFCs
+    properties:
+      vf-module:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/vf-module"
+  vig-server:
+    description: |
+      vig-server contains information about a vig server used for IPSec-configuration. Populated by SDN-C from 1607
+      ###### Related Nodes
+      - TO ipsec-configuration( vig-server BelongsTo ipsec-configuration, MANY2ONE)(4)
+
+      -(4) IF this TO node is deleted, this VIG-SERVER is DELETED also
+    required:
+    - vig-address-type
+    properties:
+      vig-address-type:
+        type: string
+        description: indicates whether the VIG is for AVPN or INTERNET
+      ipaddress-v4-vig:
+        type: string
+        description: v4 IP of the vig server
+      ipaddress-v6-vig:
+        type: string
+        description: v6 IP of the vig server
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  vig-servers:
+    properties:
+      vig-server:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/vig-server"
+  vip-ipv4-address-list:
+    description: |
+      IPv4 Address Range
+      ###### Related Nodes
+      - TO cloud-region( vip-ipv4-address-list BelongsTo cloud-region, MANY2ONE)
+      - TO instance-group( vip-ipv4-address-list MemberOf instance-group, MANY2MANY)
+      - TO subnet( vip-ipv4-address-list MemberOf subnet, MANY2MANY)
+      - FROM vnfc( vnfc Uses vip-ipv4-address-list, MANY2MANY)
+
+    required:
+    - vip-ipv4-address
+    properties:
+      vip-ipv4-address:
+        type: string
+        description: IP address
+      vip-ipv4-prefix-length:
+        type: integer
+        format: int64
+        description: Prefix length, 32 for single address
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      is-floating:
+        type: boolean
+        description: Indicator of fixed or floating address
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      neutron-network-id:
+        type: string
+        description: Neutron network id of the interface that address belongs to
+      neutron-subnet-id:
+        type: string
+        description: Neutron id of subnet that address belongs to
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  vip-ipv6-address-list:
+    description: |
+      IPv6 Address Range
+      ###### Related Nodes
+      - TO cloud-region( vip-ipv6-address-list BelongsTo cloud-region, MANY2ONE)
+      - TO instance-group( vip-ipv6-address-list MemberOf instance-group, MANY2MANY)
+      - TO subnet( vip-ipv6-address-list MemberOf subnet, MANY2MANY)
+      - FROM vnfc( vnfc Uses vip-ipv6-address-list, MANY2MANY)
+
+    required:
+    - vip-ipv6-address
+    properties:
+      vip-ipv6-address:
+        type: string
+        description: IP address
+      vip-ipv6-prefix-length:
+        type: integer
+        format: int64
+        description: Prefix length, 128 for single address
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      is-floating:
+        type: boolean
+        description: Indicator of fixed or floating address
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      neutron-network-id:
+        type: string
+        description: Neutron network id of the interface that address belongs to
+      neutron-subnet-id:
+        type: string
+        description: Neutron id of subnet that address belongs to
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  virtual-data-center:
+    description: |
+      Virtual organization of cloud infrastructure elements in a data center context
+      ###### Related Nodes
+      - FROM connector( connector LocatedIn virtual-data-center, MANY2MANY)
+      - FROM generic-vnf( generic-vnf LocatedIn virtual-data-center, MANY2MANY)
+      - FROM logical-link( logical-link LocatedIn virtual-data-center, MANY2MANY)
+
+    required:
+    - vdc-id
+    - vdc-name
+    properties:
+      vdc-id:
+        type: string
+        description: Unique ID of the vdc
+      vdc-name:
+        type: string
+        description: Name of the virtual data center
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  virtual-data-centers:
+    description: |
+      Virtual organization of cloud infrastructure elements in a data center context
+    properties:
+      virtual-data-center:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/virtual-data-center"
+  vlan:
     description: |
-      Serves a PATCH like function.  Does not enforce concurrency control.  Clear each usage with AAI team.
+      Definition of vlan
+      ###### Related Nodes
+      - TO l-interface( vlan LinksTo l-interface, MANY2ONE)(4)
+      - TO logical-link( vlan Uses logical-link, MANY2MANY)(2)
+      - TO multicast-configuration( vlan Uses multicast-configuration, MANY2MANY)
+      - FROM allotted-resource( allotted-resource PartOf vlan, MANY2MANY)
+      - FROM service-instance( service-instance ComposedOf vlan, ONE2MANY)
+      - FROM l3-interface-ipv4-address-list( l3-interface-ipv4-address-list BelongsTo vlan, MANY2ONE)(1)
+      - FROM l3-interface-ipv6-address-list( l3-interface-ipv6-address-list BelongsTo vlan, MANY2ONE)(1)
+
+      -(1) IF this VLAN node is deleted, this FROM node is DELETED also
+      -(2) IF this VLAN node is deleted, this TO node is DELETED also
+      -(4) IF this TO node is deleted, this VLAN is DELETED also
     required:
-    - update-node-type
+    - vlan-interface
+    - in-maint
     properties:
-      update-node-type:
+      vlan-interface:
         type: string
-      update-node-key:
+        description: String that identifies the interface
+      vlan-id-inner:
+        type: integer
+        format: int64
+        description: Inner VLAN tag
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Outer VLAN tag
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      speed-value:
+        type: string
+        description: Captures the numeric part of the speed
+      speed-units:
+        type: string
+        description: Captures the units corresponding to the speed
+      vlan-description:
+        type: string
+        description: Used to describe (the service associated with) the vlan
+      backdoor-connection:
+        type: string
+        description: Whether customer is going to use this VLAN for backdoor connection to another customer premise device.
+      vpn-id:
+        type: string
+        description: This indicates the customers VPN ID associated with this vlan
+      orchestration-status:
+        type: string
+        description: Status of a vnf's vlan interface, on which the customer circuit resides, mastered by SDN-C.
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true)
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      l3-interface-ipv4-address-list:
         type: array
         items:          
-          $ref: "#/definitions/update-node-key"
-      update-node-uri:
-        type: string
-      action:
+          $ref: "#/getDefinitions/l3-interface-ipv4-address-list"
+      l3-interface-ipv6-address-list:
         type: array
         items:          
-          $ref: "#/definitions/action"
-  action:
+          $ref: "#/getDefinitions/l3-interface-ipv6-address-list"
+  vlans:
     properties:
-      action-type:
-        type: string
-      action-data:
+      vlan:
         type: array
         items:          
-          $ref: "#/definitions/action-data"
-  action-data:
-    properties:
-      property-name:
-        type: string
-      property-value:
-        type: string
-  update-node-key:
+          $ref: "#/getDefinitions/vlan"
+  vnf:
+    description: |
+      Abstract vnf class
+    required:
+    - vnf-id
     properties:
-      key-name:
-        type: string
-      key-value:
+      vnf-id:
         type: string
-  notify:
+        description: Unique id of VNF.  This is unique across the graph.
+  vnf-image:
+    description: |
+      Image object that pertain to a VNF that doesn't have associated vservers.  This is a kludge.
+      ###### Related Nodes
+      - FROM generic-vnf( generic-vnf Uses vnf-image, MANY2ONE)
+
+      -VNF-IMAGE cannot be deleted if related to GENERIC-VNF
+
     required:
-    - event-id
+    - vnf-image-uuid
+    - application
+    - application-vendor
     properties:
-      event-id:
+      vnf-image-uuid:
         type: string
-      node-type:
+        description: Unique ID of this asset
+      application:
         type: string
-      event-trigger:
+        description: The application that the image instantiates.
+      application-vendor:
         type: string
-      key-data:
-        type: array
-        items:          
-          $ref: "#/definitions/key-data"
-      selflink:
+        description: The vendor of the application.
+      application-version:
         type: string
-  key-data:
-    properties:
-      key-name:
+        description: The version of the application.
+      selflink:
         type: string
-      key-value:
+        description: URL to endpoint where AAI can get more details
+      resource-version:
         type: string
-  notification-event:
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  vnf-images:
+    description: |
+      Collection of image objects that pertain to a VNF that doesn't have associated vservers.  This is a kludge.
     properties:
-      cambria.partition:
-        type: string
-      notification-event-header:
-        type: object
-        $ref: "#/definitions/notification-event-header"
-  notification-event-header:
+      vnf-image:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/vnf-image"
+  vnfc:
+    description: |
+      ###### Related Nodes
+      - TO generic-vnf( vnfc BelongsTo generic-vnf, MANY2ONE)(4)
+      - TO vserver( vnfc HostedOn vserver, ONE2MANY)
+      - FROM vf-module( vf-module Uses vnfc, ONE2MANY)
+
+      -(4) IF this TO node is deleted, this VNFC is DELETED also
+    required:
+    - vnfc-name
+    - vnfc-function-code
+    - vnfc-type
+    - in-maint
+    - is-closed-loop-disabled
     properties:
-      id:
-        type: string
-      timestamp:
-        type: string
-      source-name:
+      vnfc-name:
         type: string
-      domain:
+        description: Unique ID of vnfc.
+      vnfc-function-code:
         type: string
-      sequence-number:
+        description: function code
+      vnfc-type:
         type: string
-      severity:
+        description: type
+      prov-status:
         type: string
-      event-type:
+        description: prov status of this vnfc
+      orchestration-status:
         type: string
-      version:
+        description: Orchestration status of this VNF, mastered by APP-C
+      ipaddress-v4-oam-vip:
         type: string
-      action:
+        description: Oam V4 vip address of this vnfc
+      in-maint:
+        type: boolean
+        description: used to indicate whether or not this object is in maintenance mode (maintenance mode = true)
+      is-closed-loop-disabled:
+        type: boolean
+        description: used to indicate whether closed loop function is enabled on this node
+      group-notation:
         type: string
-      entity-type:
+        description: Group notation of VNFC
+      resource-version:
         type: string
-      top-entity-type:
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  vnfcs:
+    description: |
+      virtual network components associated with a vserver from application controller.
+    properties:
+      vnfc:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/vnfc"
+  volume:
+    description: |
+      Ephemeral Block storage volume.
+      ###### Related Nodes
+      - FROM vserver (PARENT of volume, vserver AttachesTo volume)(3)
+
+      -(3) IF this FROM node is deleted, this VOLUME is DELETED also
+    required:
+    - volume-id
+    - volume-selflink
+    properties:
+      volume-id:
         type: string
-      entity-link:
+        description: Unique ID of block storage volume relative to the vserver.
+      volume-selflink:
         type: string
-      status:
+        description: URL to endpoint where AAI can get more details
+      resource-version:
         type: string
-  reserved-prop-names:
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  volume-group:
     description: |
-      Internal map to define some reserved properties of a vertex
+      Persistent block-level storage.
+      ###### Related Nodes
+      - TO cloud-region( volume-group BelongsTo cloud-region, MANY2ONE)
+      - TO complex( volume-group LocatedIn complex, MANY2ONE)
+      - FROM generic-vnf( generic-vnf DependsOn volume-group, ONE2MANY)
+      - FROM vf-module( vf-module Uses volume-group, ONE2ONE)
+      - FROM tenant( tenant DependsOn volume-group, ONE2MANY)
+
+    required:
+    - volume-group-id
+    - volume-group-name
+    - vnf-type
     properties:
-      last-mod-source-of-truth:
+      volume-group-id:
         type: string
-      aai-node-type:
+        description: Unique ID of volume-group.
+      volume-group-name:
         type: string
-      aai-created-ts:
-        type: integer
-        format: int64
-      aai-unique-key:
+        description: Name of the volume group.
+      heat-stack-id:
         type: string
-      aai-last-mod-ts:
-        type: integer
-        format: int64
-      source-of-truth:
+        description: Heat stack id corresponding to this volume-group
+      vnf-type:
         type: string
-      aai-uri:
+        description: String capturing type of vnf, that was intended to identify the ASDC resource.  This field has been overloaded in service-specific ways and clients should expect changes to occur in the future to this field as ECOMP matures.
+      orchestration-status:
         type: string
-  edge-prop-names:
-    description: |
-      Internal map to define the properties of an edge and interpret the map EdgeRules
-    properties:
-      edgeLabel:
+        description: Orchestration status of this volume-group
+      model-customization-id:
         type: string
-      direction:
+        description: captures the id of all the configuration used to customize the resource for the service.
+      vf-module-model-customization-id:
         type: string
-      multiplicityRule:
+        description: helps relate the volume group to the vf-module whose components will require the volume group
+      resource-version:
         type: string
-      isParent:
-        type: boolean
-      usesResource:
-        type: boolean
-      hasDelTarget:
-        type: boolean
-      SVC-INFRA:
-        type: boolean
-      SVC-INFRA-REV:
-        type: boolean
-  model-and-named-query-search:
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  volume-groups:
     description: |
-      ModelAndNamedQuerySearch holds query-parameters and instance-properties for performing a named-query or model query
+      Collection of persistent block-level storage.
     properties:
-      query-parameters:
-        type: object
-        $ref: "#/definitions/query-parameters"
-      instance-filters:
-        type: object
-        $ref: "#/definitions/instance-filters"
-      secondary-filts:
-        type: object
-        $ref: "#/definitions/secondary-filts"
-      top-node-type:
-        type: string
-      secondary-filter-cut-point:
-        type: string
-  query-parameters:
+      volume-group:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/volume-group"
+  volumes:
     description: |
-      QueryParameters for performing a named-query or model query
+      Collection of ephemeral Block storage volumes.
     properties:
-      named-query:
-        type: object
-        $ref: "#/definitions/named-query"
-      overloaded-model:
-        type: object
-        $ref: "#/definitions/overloaded-model"
-  overloaded-model:
+      volume:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/volume"
+  vpls-pe:
     description: |
-      Allows for legacy POST of old-style and new-style models
+      VPLS Provider Edge routers.
+      ###### Related Nodes
+      - TO complex( vpls-pe LocatedIn complex, MANY2ONE)
+      - TO ctag-pool( vpls-pe Uses ctag-pool, MANY2MANY)
+      - FROM lag-interface( lag-interface BindsTo vpls-pe, MANY2ONE)(1)
+      - FROM p-interface( p-interface BindsTo vpls-pe, MANY2ONE)(1)
+
+      -(1) IF this VPLS-PE node is deleted, this FROM node is DELETED also
     required:
-    - model-invariant-id
-    - model-name-version-id
-    - model-type
-    - model-name
-    - model-id
-    - model-version
+    - equipment-name
     properties:
-      model-invariant-id:
-        type: string
-        description: Unique identifier corresponding to the main definition of a model in ASDC
-      model-name-version-id:
-        type: string
-        description: Unique identifier corresponding to one version of a model in ASDC
-      model-type:
-        type: string
-        description: Type of the model, e.g., service, resource, widget, etc.
-      model-name:
+      equipment-name:
         type: string
-        description: Name of the model, which can change from version to version.
-      model-id:
+      prov-status:
         type: string
-        description: Invariant unique ID which does not change from version to version
-      model-version:
+        description: Trigger for operational monitoring of this VNF by BAU Service Assurance systems.
+      ipv4-oam-address:
         type: string
-        description: Version
-      model-description:
+        description: Address tail-f uses to configure generic-vnf, also used for troubleshooting and is IP used for traps generated by GenericVnf (v4-loopback0-ip-address).
+      equipment-role:
         type: string
-        description: Description
+        description: Client should send valid enumerated value, e.g., VPLS-PE.
+      vlan-id-outer:
+        type: integer
+        format: int64
+        description: Temporary location for stag to get to VCE
       resource-version:
         type: string
         description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
-      model-vers:
-        type: object
-        $ref: "#/definitions/model-vers"
       relationship-list:
-        type: object
-        $ref: "#/definitions/relationship-list"
-  instance-filters:
-    description: |
-      InstanceFilters for performing a named-query or model query
-    properties:
-      instance-filter:
         type: array
-        items:          
-          $ref: "#/definitions/instance-filter"
-  instance-filter:
-    description: |
-      InstanceFilter for performing a named-query or model query
-  secondary-filts:
+        items:
+          $ref: "#/getDefinitions/relationship"
+      p-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/p-interface"
+      lag-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/lag-interface"
+  vpls-pes:
     description: |
-      SecondaryFilts for performing a named-query or model query
+      Collection of VPLS Provider Edge routers
     properties:
-      secondary-filt:
+      vpls-pe:
         type: array
         items:          
-          $ref: "#/definitions/secondary-filt"
-  secondary-filt:
-    description: |
-      SecondaryFilt for performing a named-query or model query
-  properties:
+          $ref: "#/getDefinitions/vpls-pe"
+  vpn-binding:
     description: |
-      Property holder for query properties or instance properties
+      VPN binding
+      ###### Related Nodes
+      - FROM l3-network( l3-network Uses vpn-binding, MANY2MANY)
+      - FROM logical-link( logical-link Uses vpn-binding, MANY2MANY)
+      - FROM route-target( route-target BelongsTo vpn-binding, MANY2ONE)(1)
+
+      -(1) IF this VPN-BINDING node is deleted, this FROM node is DELETED also
+      -VPN-BINDING cannot be deleted if related to L3-NETWORK,LOGICAL-LINK
+
+    required:
+    - vpn-id
+    - vpn-name
     properties:
-      property-name:
+      vpn-id:
         type: string
-      property-value:
+        description: VPN ID, globally unique within A&AI
+      vpn-name:
         type: string
-  response-list:
-    description: |
-      Response container for the results of a named-query or model query
-    properties:
-      inventory-response-items:
-        type: object
-        $ref: "#/definitions/inventory-response-items"
-  inventory-response-items:
-    description: |
-      Container for inventory items in response list
+        description: VPN Name
+      vpn-platform:
+        type: string
+        description: the platform associated with the VPN example AVPN, Mobility
+      vpn-type:
+        type: string
+        description: Type of the vpn, should be taken from enumerated/valid values
+      route-distinguisher:
+        type: string
+        description: Used to distinguish the distinct VPN routes of separate customers who connect to the provider in an MPLS network.
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      route-targets:
+        type: array
+        items:
+          $ref: "#/getDefinitions/route-target"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+        description: l3-networks relate to vpn-bindings
+  vpn-bindings:
     properties:
-      inventory-response-item:
+      vpn-binding:
         type: array
         items:          
-          $ref: "#/definitions/inventory-response-item"
-  inventory-response-item:
+          $ref: "#/getDefinitions/vpn-binding"
+  vserver:
     description: |
-      Inventory item for response list
+      Virtual Servers, aka virtual machine or VM.
+      ###### Related Nodes
+      - TO tenant( vserver BelongsTo tenant, MANY2ONE)
+      - TO flavor( vserver Uses flavor, MANY2ONE)
+      - TO image( vserver Uses image, MANY2ONE)
+      - TO pserver( vserver HostedOn pserver, MANY2ONE)
+      - TO snapshot( vserver Uses snapshot, ONE2ONE)
+      - TO volume (CHILD of vserver, vserver AttachesTo volume, ONE2MANY)(2)
+      - FROM generic-vnf( generic-vnf HostedOn vserver, ONE2MANY)
+      - FROM vce( vce HostedOn vserver, ONE2MANY)
+      - FROM l-interface( l-interface BindsTo vserver, MANY2ONE)(1)
+      - FROM vf-module( vf-module Uses vserver, ONE2MANY)
+      - FROM vnfc( vnfc HostedOn vserver, ONE2MANY)
+
+      -(1) IF this VSERVER node is deleted, this FROM node is DELETED also
+      -(2) IF this VSERVER node is deleted, this TO node is DELETED also
+    required:
+    - vserver-id
+    - vserver-name
+    - vserver-selflink
+    - in-maint
+    - is-closed-loop-disabled
     properties:
-      model-name:
+      vserver-id:
         type: string
-      extra-properties:
-        type: object
-        $ref: "#/definitions/extra-properties"
-      inventory-response-items:
-        type: object
-        $ref: "#/definitions/inventory-response-items"
-  extra-properties:
+        description: Unique identifier for this vserver relative to its tenant
+      vserver-name:
+        type: string
+        description: Name of vserver
+      vserver-name2:
+        type: string
+        description: Alternative name of vserver
+      prov-status:
+        type: string
+        description: Trigger for operational monitoring of this resource by Service Assurance systems.
+      vserver-selflink:
+        type: string
+        description: URL to endpoint where AAI can get more details
+      in-maint:
+        type: boolean
+        description: Used to indicate whether or not this object is in maintenance mode (maintenance mode = true). This field (in conjunction with prov-status) is used to suppress alarms and vSCL on VNFs/VMs.
+      is-closed-loop-disabled:
+        type: boolean
+        description: Used to indicate whether closed loop function is enabled on this node
+      resource-version:
+        type: string
+        description: Used for optimistic concurrency.  Must be empty on create, valid on update and delete.
+      volumes:
+        type: array
+        items:
+          $ref: "#/getDefinitions/volume"
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+      l-interfaces:
+        type: array
+        items:
+          $ref: "#/getDefinitions/l-interface"
+  vservers:
     description: |
-      Extra properties for inventory item for response list
+      Collection of virtual Servers, aka virtual machines or VMs.
     properties:
-      extra-property:
+      vserver:
         type: array
         items:          
-          $ref: "#/definitions/extra-property"
-  extra-property:
+          $ref: "#/getDefinitions/vserver"
+  zone:
+    description: |
+      A zone is a grouping of assets in a location homing to the same connections into the CBB
+      ###### Related Nodes
+      - TO complex( zone LocatedIn complex, MANY2ONE)
+      - FROM cloud-region( cloud-region LocatedIn zone, MANY2ONE)
+      - FROM pnf( pnf LocatedIn zone, MANY2ONE)
+      - FROM pserver( pserver LocatedIn zone, MANY2ONE)
+
+    required:
+    - zone-id
+    - zone-name
+    - design-type
+    - zone-context
     properties:
-      property-name:
+      zone-id:
         type: string
-      property-value:
+        description: Code assigned by AIC to the zone
+      zone-name:
         type: string
-  vnf:
+        description: English name associated with the zone
+      design-type:
+        type: string
+        description: Design of zone [Medium/Large?]
+      zone-context:
+        type: string
+        description: Context of zone [production/test]
+      status:
+        type: string
+        description: Status of a zone.
+      resource-version:
+        type: string
+        description: Concurrency value
+      relationship-list:
+        type: array
+        items:
+          $ref: "#/getDefinitions/relationship"
+  zones:
     description: |
-      Abstract vnf class
-    required:
-    - vnf-id
+      Collection of zones
     properties:
-      vnf-id:
-        type: string
-        description: Unique id of VNF.  This is unique across the graph.
+      zone:
+        type: array
+        items:          
+          $ref: "#/getDefinitions/zone"