While troubleshooting some failures of the import-export verification tool to verify RDF graphs produced with and without binaries exported, differences were discovered in the syntax of the turtle that the import-export tool writes to disk.
When binaries are included, the turtle appears to conform to RDF 1.0 rules, where all the literals (including strings) are explicitly typed. Presumably this is coming more or less directly from Fedora. When binaries are not included, however, the tool is filtering some triples out of the graph, and appears to write turtle that conforms to the more relaxed RDF 1.1 rules, where untyped literals can be assumed to be of type xsd:string and "true" and "false" are assumed to be Booleans when untyped, among other differences.
While these differences might be semantically insignificant (at least to RDF 1.1 parsers – but not to RDF 1.0), and could in theory be something that the verification tool were expected to handle, it seems like a good practice for the import/export tool to produce syntactically consistent turtle no matter which options are chosen.
Here are examples of the turtle written to disk by import/export with binaries:
and with no binaries:
See also: https://www.w3.org/TR/rdf11-new/