HSON MIME Types & Usage

HSON is typically described in a <script> element in your HTML. This script is identified with a special type so that the browser will ignore it, but our code can easily access it.

Currently Sygnal's HSON processor is built into the Sygnal Attributes ( SA5 ) Data library.

Current MIME Type

We're just beginning to distinguish HSON as a distinct standard, separate from the SA5 Data library, so that it can be clearly documented, and so that the community can use the specification to write other parsers and handlers.

Currently, the most supported MIME type is the one used currently in SA5 Data, directly, which is;

sygnal/sa5-data

Migration Plans

We intend to retire sygnal/sa5-data in favor of our browser naming conventions below.

For standards consistency we're migrating to follow JSON's MIME-type naming convention patterns, such as application/hson and application/ld+json.

Our current types;

Script MIME Type	Usage
application/hson	General-purpose HSON
application/wfx+hson	Used to configure Sygnal's Webflow Chrome Extension ( aka. WFX )
application/hf+hson	Used to configure Sygnal's Hyperflow reverse proxy platform with page and site-specific settings.

MIME subtypes are a convention used to combine schema & format in the MIME type specifier. For example, JSON-LD is represented as application/ld+json.