EIDO & IDX FAQ (Frequently Asked Questions): Difference between revisions

Content deleted Content added
Added links to NENA/APCO-INF-005.1 EIDD Information Document
Line 89: Line 89:
The current proposed transport draft uses Subscribe/Notify to send updated EIDOs. The mechanism includes filters that allow the recipient to control the rate of transmission. The sender can decide how often to send updates, which could be as often as every character, or as little as complete notes. The recipient can limit how often it receives EIDOs using the rate filters.
The current proposed transport draft uses Subscribe/Notify to send updated EIDOs. The mechanism includes filters that allow the recipient to control the rate of transmission. The sender can decide how often to send updates, which could be as often as every character, or as little as complete notes. The recipient can limit how often it receives EIDOs using the rate filters.


=== The APCO-NENA EIDD INF document says that an EIDD does not provide historical data. What does that mean? ===
=== The NENA-APCO EIDD INF document says that an EIDD does not provide historical data. What does that mean? ===
The EIDO specification that is being developed from the [https://www.nena.org/page/EIDD_INF NENA/APCO-INF-005.1 EIDD Information Document] indicates that the EIDO only includes the entire (not delta) CURRENT ‘state’ of the incident, as known by the sender. Historical data is stored in, and retrieved from the logging service.
The EIDO specification that is being developed from the [https://www.nena.org/page/EIDD_INF NENA/APCO-INF-005.1 EIDD Information Document] indicates that the EIDO only includes the entire (not delta) CURRENT ‘state’ of the incident, as known by the sender. Historical data is stored in, and retrieved from the logging service.