Non-DCTAP elements are ignored unless configured.

Columns in a CSV that are not part of the DCTAP model are not automatically passed through to text, YAML, or JSON output because unrecognized elements, in principle, bear an undefined relationship to Shapes and Statement Templates.

propertyID	Status
dcterms:creator	ignotus

Interpreted (with warnings enabled) as:

DCTAP instance
    Shape
        shapeID                  default
        Statement Template
            propertyID           dcterms:creator

WARNING [csv/header] Non-DCTAP element 'Status' not configured as extra element.

Users wishing to use columns in their CSV that are not part of the DCTAP model, for example to specify that a shape is “closed” or to specify “severity” of validation errors, can generate a configuration file (see section Initialize a config file) and list their extra column headers in the configuration file under the sections “extra_shape_elements” or “extra_statement_template_elements”. This will ensure that the extra columns will be passed through to the text, JSON, and YAML outputs.

For example, if the configuration file includes:

extra_statement_template_elements:
- status

The text output, intended as an aid in debugging, includes the extra element but marks it as “extra” with brackets:

DCTAP instance
    Shape
        shapeID                  default
        Statement Template
            propertyID           dcterms:creator
            [status]             ignotus

The JSON (or YAML) output includes the extra element “as is”:

{
    "shapes": [
        {
            "shapeID": "default",
            "statement_templates": [
                {
                    "propertyID": "dcterms:creator",
                    "status": "ignotus"
                }
            ]
        }
    ]
}