updated description for date-time and removed sink credential in Subscription schema

Author: maheshc01

code/API_definitions/connectivity-insights-subscriptions.yaml

@@ -408,8 +408,6 @@ components:
             The address to which events shall be delivered using the selected
             protocol.
           example: "https://endpoint.example.com/sink"
-        sinkCredential:
-          $ref: "#/components/schemas/SinkCredential"
         types:
           description: |
             Camara Event types eligible to be delivered by this subscription.
@@ -434,13 +432,23 @@ components:
           type: string
           format: date-time
           description: Date when the event subscription will begin/began
+            It must follow [RFC 3339](https://datatracker.ietf.org/doc/html/
+            rfc3339#section-5.6) and must have time zone.
+            Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ (i.e. which
+            allows 2023-07-03T14:27:08.312+02:00 or 2023-07-03T12:27:08.312Z)
+          example: "2023-07-03T12:27:08.312Z"
         expiresAt:
           type: string
           format: date-time
           description: |
             Date when the event subscription will expire. Only provided when
             `subscriptionExpireTime` is indicated by API client or Telco
             Operator has specific policy about that.
+            It must follow [RFC 3339](https://datatracker.ietf.org/doc/html/
+            rfc3339#section-5.6) and must have time zone.
+            Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ (i.e. which allows
+            2023-07-03T14:27:08.312+02:00 or 2023-07-03T12:27:08.312Z)
+          example: "2023-07-03T12:27:08.312Z"
         status:
           type: string
           description: |-
@@ -710,10 +718,12 @@ components:
         subscriptionExpireTime:
           type: string
           format: date-time
-          example: 2023-01-17T13:18:23.682Z
           description: |
             The subscription expiration time (in date-time format) requested by
             the API consumer. Up to API project decision to keep it.
+            It must follow [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) and must have time zone.
+            Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ (i.e. which allows 2023-07-03T14:27:08.312+02:00 or 2023-07-03T12:27:08.312Z)
+          example: "2023-07-03T12:27:08.312Z"
         subscriptionMaxEvents:
           type: integer
           description: |
@@ -951,8 +961,12 @@ components:
       type: string
       format: date-time
       description: |
-        Timestamp of when the occurrence happened. Must adhere to RFC 3339.
-      example: "2018-04-05T17:31:00Z"
+        Timestamp of when the occurrence happened.
+        It must follow [RFC 3339](https://datatracker.ietf.org/doc/html/
+        rfc3339#section-5.6) and must have time zone.
+        Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ (i.e. which allows
+        2023-07-03T14:27:08.312+02:00 or 2023-07-03T12:27:08.312Z)
+      example: "2023-07-03T12:27:08.312Z"
 
     EventTypeNotification:
       type: string

code/API_definitions/connectivity-insights.yaml

@@ -173,6 +173,11 @@ components:
             current date and time is used and network data for the monitoring
             data aggregation is used to check network performance against the
             application profile defined.
+            It must follow [RFC 3339](https://datatracker.ietf.org/doc/html/
+            rfc3339#section-5.6) and must have time zone.
+            Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ (i.e. which allows
+            2023-07-03T14:27:08.312+02:00 or 2023-07-03T12:27:08.312Z)
+          example: "2023-07-03T12:27:08.312Z"
 
     NetworkQualityInsightResponse:
       type: object