diff options
Diffstat (limited to 'docs/Chapter8')
| -rw-r--r-- | docs/Chapter8/ves7_1spec.rst | 17 |
1 files changed, 9 insertions, 8 deletions
diff --git a/docs/Chapter8/ves7_1spec.rst b/docs/Chapter8/ves7_1spec.rst index 83829ae..2c8b933 100644 --- a/docs/Chapter8/ves7_1spec.rst +++ b/docs/Chapter8/ves7_1spec.rst @@ -115,9 +115,9 @@ the uniqueness of the eventName: {DomainAbbreviation}\_{PublisherName}\_{Description} -Each underscore-separated subfield above must start with a capital +Each underscore-separated subfield above should start with a capital letter and use camel-casing to separate words and acronyms. Acronyms -must capitalize only the first letter of the acronym. Spaces and +should capitalize only the first letter of the acronym. Spaces and underscores should not appear within any subfield. The DomainAbbreviation subfield derives from the ‘domain’ field in the @@ -362,9 +362,8 @@ an ONAP controller action, or provided manually. VES Events. The events shall only be sent to one VES Event Listener at a time. Please note: If a FQDN is used, the DNS query would return a single IP address. -* A single VES Event Listener may handle more than one type of VES event - (different domains); i.e. same VES Event Listener can receive and process - heartbeat, fault, measurement, syslog, etc. events. +* The active VES Event Listener (either the primary or secondary) will handle + all VES events regardless of domain. * **VES Credentials**: If the NF is using Basic Authentication, then the NF must support the provisioning of security and authentication parameters (HTTP username and password) in order to be able to authenticate with the @@ -647,7 +646,7 @@ Note on extensible fields: VES has explicitly defined a cpuUsage.cpuIdle field for the communication of that information. -- Keys sent through extensible fields must use camel casing to separate +- Keys sent through extensible fields should use camel casing to separate words and acronyms; only the first letter of each acronym shall be capitalized. @@ -748,8 +747,8 @@ Datatype: hashMap The hashMap datatype is an ‘associative array’, which is an unordered collection of key-value pairs of the form "key": "value", where each key -and value are strings. Keys must use camel casing to separate words and -acronyms; only the first letter of each acronym shall be capitalized. +and value are strings. Keys should use camel casing to separate words and +acronyms; only the first letter of each acronym should be capitalized. Datatype: jsonObject ++++++++++++++++++++ @@ -6213,6 +6212,8 @@ Contents. | | | - Corrected publishEventBatch call flow diagram | | | | - Changed AuthorizationHeader to Required? = NO for | | | | publishAnyEvent operation | +| | | - Relaxed various requirements related to camel | +| | | casing of values from 'must' to 'should' | +-----------+---------+-------------------------------------------------------+ .. _time_zone_abbreviations: https://en.wikipedia.org/wiki/List_of_time_zone_abbreviations |