Choose which semantax to use


Use the vocabulary option to choose which set of mnemonics are recognized as semantax.


Semantax are declared within the BLUEPROCESSOR and grouped into vocabularies that align with industry standard specifications for HTML, MathML, and SVG. Custom vocabularies may also be defined for any problem domain that uses XML markup (see semantax pragma).

By default, the BLUEPROCESSOR recognizes all of the tagnames defined by the HTML, MathML, and SVG specifications. To limit the interpretation of mnemonics to just one of these, use the vocabulary option.

!option --vocabulary=html     // recognize HTML tags only
!option --vocabulary=svg // recognize SVG tags only
!option --vocabulary=mathml // recognize MathML tags only
Limiting the list of recognized mnemonics

Custom Vocabularies

If a custom vocabulary has been defined using a set of semantax options, you should enable them by specifying a custom vocabulary namespace.

!semantax .vcard #vcard
!semantax .vcard #n *parents=vcard
!semantax .vcard #photo *parents=vcard
!semantax .vcard #tel *parents=vcard
!semantax .vcard #surname *parents=n
!semantax .vcard #given *parents=n
!semantax .vcard #prefix *parents=n
!semantax .vcard #uri *parents='photo tel'
!semantax .vcard #parameters *parents='photo tel'
!semantax .vcard #mediatype *parents=parameters *implied=text
!semantax .vcard #type *parents=parameters *implied=text
!semantax .vcard #text *parents='mediatype type'

!option --vocabulary=vcard

vcard {
n {
surname Forrest
given Gump
prefix Mr.
photo {
parameters {
mediatype {
tel {
parameters {
type {
uri tel:+1-111-555-1212
Enabling a custom vocabulary

Unchecked Vocabularies

It is possible to treat a manuscript as a wide-open XML-like file, without semantax checking. This is useful when defining a formal set of semantax is too burdensome (such as with the vcard example above).

Use the unchecked value to force the BLUEPROCESSOR to interpret the leading characters of each phrase as a semantax mnemonic.

Note that with this setting implied semantax cannot be used.

!option --vocabulary=unchecked   // wide-open semantax interpretation
Enabling open-ended interpretation of semantax

syntax > options > vocabularyChoose which semantax to use

🔗 🔎