CAP after browser-side XSLT: representation, rendering and content negotiation
Browser XSLT removal changes human presentation, not CAP. A publisher-focused guide to rendering, HTTP negotiation and practical migration.
Project journal
Ian's notes from Alert Hub projects
Working notes from the Alert Hub codebase: CAP emergency alerting, controlled vocabularies, reporting, ingestion, interoperability, and the operational details where discussion and feedback would be useful.
Latest increments
Recent posts
Short implementation notes that connect design intent, code changes, and operational questions across the Alert Hub workspace.
Alert-hub.org data extraction with Python
A reproducible Python recipe for building a complete local copy of the Alert Hub alert archive and keeping it synchronized as an ongoing record stream.
Active Mirrors for Official CAP Feeds
A field note on the Alert Hub RSS reflector: an independently hosted mirror intended to keep official CAP alerts reachable when national network rules impede access across borders.
A Human-Readable View of Alert Hub Monthly Reports
The finalised Alert Hub monthly report can now be read and explored in the CAP Aggregator, with Markdown and JSON downloads for reuse outside the application.
Keeping CAP Alerts Readable as Browsers Retire Native XSLT
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.
Tightening the CAP Profile for Flood Hub Guidance
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.
Browse journal
Projects and themes
Projects
Tags
alert distributionandorraarchitecturearchiveauditbackendcapcommon alerting protocolcontent negotiationcontrolled vocabularycredentialsdatadata qualityelasticsearchemergency alertingfan-outfiltered alert hubfloodflood hubguidancehttpinteroperabilityjacksonjavajdk25meteoalarmmulti-channel-relayoetopen dataoperationspythonreportingresiliencersssemantic webskossnsstoragetarget deliverytelegramuxxmlxslt
Current threads
My current emphasis is interoperability: CAP, OET, controlled vocabularies, SKOS, analytics, and operational workflows that other people can inspect, question, and reuse.