Vernacular

HTML Made Special

Default Values

Default values are commonly considered when creating APIs but too often forgotten when designing declarative formats, making them harder to use than necessary. Additionally, an important distinction often prevails in markup: whereas a method receiving an invalid argument will commonly produce an error, in markup it is often preferable to treat it as if it had been unspecified. This can lead to better decoupling between document and processor versions.

Not specifying how to default values will hurt error processing (and its cousin versioning), and lead to interoperability issues.

Imagine for instance that an author specifies the colour of an item to be #99 instead of the intended #999 because of a typo. The processor can interpret that in several ways:

Most of the above will produce different colours. And since they’ll produce different results in different implementations, there will be no interoperability. Which solution works best depends a lot on the usage scenario for the vernacular, you have to make your own mind up there. Note however that unless you are certain that there is a user at the helm to handle the error or you are encoding critical information such as steps in robotic surgery, it is unlikely that halting and catching fire is the best option.

↖︎ Back to list