-
Key: ALMAS-9
-
Legacy Issue Number: 12294
-
Status: closed
-
Source: Objective Interface Systems ( Mr. Victor Giddings)
-
Summary:
This section provides an extension mechanism for AlertData so that this data can safely be transferred to products that don't understand the extensions. The requirements that receipt of any of this data not be "dropped" etc. need to be clarified. Also, there should be the possibility for providing a "type" indication (possibly either a string or enumeration) that would allow different products to interpret different extensions.
-
Reported: ALMAS 1.0b1 — Fri, 14 Mar 2008 04:00 GMT
-
Disposition: Resolved — ALMAS 1.0
-
Disposition Summary:
Need to update Figure 6.2 and 6.2.3 AlertDataExtraAttributes attributes table:
1) add attribute "TypeOfByteData" of type int, with the description of
"Valid values for this are:
0 = string
1 = Integer8
2 = Integer16
3 = Integer32
4 = Float32
5 = Float64
6 = bytes"
2) add attribute "Description" of type string with description "Used to provide indicaton of the content e.g. "image (jpg)", "URL", "track object", ..."
Replace the last sentence of the AlertDataExtraAttributes description
'The extra attributes are configured via the ALMAS Alert definition xml PSM specified in section 7.1. If defined in the Alert definition XML provided to ALMAS, then ALMAS shall support the definition, receipt, storage and passing of this data to receivers as part of a standard implementation.' -
Updated: Fri, 6 Mar 2015 20:57 GMT
ALMAS — 2.3.2.3 AlertDataExtraAttributes
- Key: ALMAS-9
- OMG Task Force: Alerts Management Service 1.0 (ALMAS) FTF