> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/data-object/do.ews.03-info.md).

# DO.EWS.03 Info

An alert is a collection of information that EWS can share with SP System to take anticipatory actions.

The **Info object** **shall** contain descriptive elements aligned with the Common Alerting Protocol (CAP) v1.2. This ensures semantic interoperability and consistent interpretation of alert messages across systems.

**Normative Reference:**\
OASIS Common Alerting Protocol (CAP) v1.2\
<https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2.html>

<table><thead><tr><th width="132.7066650390625">Attribute</th><th width="188.1612548828125">Type</th><th width="150.1409912109375">Cardinality</th><th>Description</th></tr></thead><tbody><tr><td>language</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/code-directory/cd.com.14-language_code.md">CD.COM.14: language_code</a></td><td>0...1</td><td>Unique identifier of the alert message</td></tr><tr><td>category</td><td><a data-mention href="/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/code-directory/cd.ews.01-category.md">CD.EWS.01 category</a></td><td>1...1</td><td>Hazard or event type (e.g., MET, GEO).</td></tr><tr><td>event</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>1...1</td><td>The type of the subject event of the alert message</td></tr><tr><td>reponse_type</td><td><a data-mention href="/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/code-directory/cd.ews.08-response_type.md">CD.EWS.08 response_type</a></td><td>0...1</td><td>The type of action recommended for the target audience</td></tr><tr><td>urgency</td><td><a data-mention href="/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/code-directory/cd.ews.06-urgency.md">CD.EWS.06 urgency</a></td><td>1...1</td><td>Timeframe for response (e.g., <code>Immediate</code>, <code>Expected</code>).</td></tr><tr><td>severity</td><td><a data-mention href="/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/code-directory/cd.ews.02-alert_severity.md">CD.EWS.02 alert_severity</a></td><td>1...1</td><td>Severity level (e.g., <code>Extreme</code>, <code>Severe</code>, <code>Moderate</code>, <code>Minor</code>).</td></tr><tr><td>certainty</td><td><a data-mention href="/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/code-directory/cd.ews.07-certainty.md">CD.EWS.07 certainty</a></td><td>1...1</td><td>Likelihood of occurrence (e.g., <code>Observed</code>, <code>Likely</code>, <code>Possible</code>).</td></tr><tr><td>audience</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>The text describing the intended audience of the alert message</td></tr><tr><td>effective</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string/data-formats/df.com.string.01-date_time.md">DF.COM.STRING.01 date_time</a></td><td>0...1</td><td>If this item is not included, the effective time SHALL be assumed to be the same as in &#x3C;sent>.</td></tr><tr><td>event_code</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>A system-specific code identifying the event type of the alert message</td></tr><tr><td>onset</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string/data-formats/df.com.string.01-date_time.md">DF.COM.STRING.01 date_time</a></td><td>0...1</td><td>The expected time of the beginning of the subject event of the alert message</td></tr><tr><td>expires</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string/data-formats/df.com.string.01-date_time.md">DF.COM.STRING.01 date_time</a></td><td>0...1</td><td>If this item is not provided, each recipient is free to set its own policy as to when the message is no longer in effect.</td></tr><tr><td>sender_name</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>The text naming the originator of the alert message</td></tr><tr><td>headline</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>Brief summary of the alert.</td></tr><tr><td>description</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>Detailed description of the event and its potential impact.</td></tr><tr><td>instruction</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>Recommended protective actions.</td></tr><tr><td>web</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>A full, absolute URI for an HTML page or other text resource with additional or reference information regarding this alert.</td></tr><tr><td>contact</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>The text describing the contact for follow-up and confirmation of the alert message</td></tr><tr><td>parameter</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string.md">DT.COM.02 string</a></td><td>0...1</td><td>A system-specific additional parameter associated with the alert message</td></tr><tr><td>area</td><td><a data-mention href="/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/data-object/do.ews.05-area.md">DO.EWS.05 Area</a></td><td>0...*</td><td>the area impacted by the hazard</td></tr><tr><td>resource</td><td><a data-mention href="/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/data-object/do.ews.04-resource.md">DO.EWS.04 Resource</a></td><td>0...*</td><td>to send message in different format like video, audio or image</td></tr><tr><td>created_at</td><td><a data-mention href="/standards/standards-for-interoperability-interfaces/common-standards-for-interoperability-interfaces/data/data-types-and-formats/dt.com.02-string/data-formats/df.com.string.01-date_time.md">DF.COM.STRING.01 date_time</a></td><td>0...1</td><td>The date of the creation of the alert</td></tr></tbody></table>

```json

        {
          "language": "en-US",
          "category": [
            "Met"
          ],
          "event": "Flash Flood",
          "responseType": [
            "Prepare"
          ],
          "urgency": "Immediate",
          "severity": "Severe",
          "certainty": "Likely",

          "headline": "Flash Flood Warning",
          "description": "Heavy rainfall may cause flash flooding.",
          "instruction": "Move to higher ground.",

          "effective": "2026-06-22T10:00:00Z",
          "expires": "2026-06-22T18:00:00Z",

          "area": [
            {
              "areaDesc": "Bekaa Governorate",

              "polygon": [
                "33.85,35.45 33.95,35.45 33.95,35.55 33.85,35.55 33.85,35.45"
              ],

              "geocode": [
                {
                  "valueName": "ADMIN_CODE",
                  "value": "LB-BI"
                }
              ]
            },
            {
              "areaDesc": "Baalbek District",

              "geocode": [
                {
                  "valueName": "SPMIS_DISTRICT_ID",
                  "value": "DISTRICT_101"
                }
              ]
            }
          ]
        }
      
  
```

> To note, if the SP MS is triggering an SMS or notification :&#x20;
>
> 1- Screen-Reader and Text-to-Speech (TTS) Optimization: When a Social Protection system triggers an SMS or digital notification, the text is often processed by assistive technologies. EWS must ensure that the text payloads in the Info object (DO.EWS.03) are optimized for these tools. &#x20;
>
> 2- Pronunciation & Phonetics: Avoid abbreviations. For example, instead of "Evac via HWY 9", the instruction field must read "Evacuate via Highway 9". &#x20;
>
> 3- Sequential Information: The instruction field must prioritize the most critical action in the very first sentence so screen-reader users do not have to listen to a lengthy meteorological description before learning what action to take.&#x20;

> The "web" URI must link to an accessibility-audited (WCAG 2.1/2.2 AA compliant) dashboard or resource page. &#x20;
>
> Accessible Routing: If evacuation is the "response\_type", the "instruction" or "linked web" resource must explicitly state which shelters are wheelchair accessible, which accept service animals, and where to request accessible emergency transit.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://standards.spdci.org/standards/dci-standards/early-warning-systems/wip-early-warning-systems-and-sp-system-interface/9.-ews/data/data-object/do.ews.03-info.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.