Swignition's Options

These are the options that Swignition's web interface exposes. The command-line client has more options, which can be seen in the --help text.

Strict Microformats
When in strict mode, the page must explicitly provide well-known profile URIs for any microformats it uses (except for a handful of microformats for which there do not exist any such profiles yet). Without strict mode, microformats can be freely used without profile URIs.
Strict RDFa
When in strict mode, the page must use the XHTML+RDFa doctype if it wants to make use of RDFa. Without strict mode, RDFa can be used in any old page.
Strict eRDF
Unless you know what you're doing, you really want to keep strict mode on. When strict mode is off, Swignition will attempt to read eRDF information from pages, even if they haven't indicated that they actually contain eRDF markup — for some pages this will result in a lot of useless and meaningless data.
Strict GRDDL
When strict GRDDL is off, Swignition will follow rel=transformation links and use them to glean extra data from the page. When strict GRDDL is on, it will ignore these links unless the GRDDL profile is found — this is the correct GRDDL behaviour.
Check <head profile> for GRDDL
When this is enabled, GRDDL will fetch each profile URI on the page and inspect them for rel=profileTransformation links to use for GRDDL. For most pages, this will be very slow. Note that Swignition includes built-in parsing for most microformats, generally better than GRDDL is able to provide, so for most pages you will not need to use GRDDL anyway.
HTML5-style document outline
HTML5 contains a document outline algorithm which builds a hierarchical list of headings. Swignition is able to represent this in RDF, mostly using Dublin Core's isPartOf and title.
Parse HTTP headers
Swignition can parse HTTP response headers, using W3C HTTP Vocabulary in RDF.