OptionalcanonicalCanonical order, so two documents with the same checks write the same
bytes: applicability facets in the ids.xsd sequence (entity, partOf,
classification, attribute, property, material; stable within a kind)
and ifcVersion tokens in schema order without duplicates. Both are
order-insensitive in IDS. Requirements keep their authored order, which
reports show. Default false: everything is written in the order given.
OptionalindentIndentation of one nesting level: a number of spaces (0–8) or '\t'. Default 2.
OptionalnewlineLine ending. Default '\n'.
Formatting of
writeIdsXml's output. Every option changes layout or order only, never meaning.