Tag
Journal entries tagged with common alerting protocol.
A field note on two ways to preserve human-readable Common Alerting Protocol documents after Chromium removes native XSLT: HTTP content negotiation and an experimental script-loaded XSLT processor.
A follow-up note on aligning generated Flood Hub guidance CAP with a narrower authority-facing profile: clearer sender identity, authority audience text, fewer optional elements, and a two-hour freshness window.
A field note on adding Telegram as a downstream target for relayed CAP messages, with context-owned target configuration and delivery receipts visible in the operator view.
A technical note for organisations that need to receive Common Alerting Protocol alerts and relay them safely to internal systems, public feeds, and operational partners.
