The codebase ships two overlapping Turtle export templates under develop/modules/templates/:

• ttl.ini ("Turtle (TTL)", 442 lines): rich metadata, PROV-O, VoID, Schema.org alignment heuristics, annotation-property declarations. Bare ":hasArtificialKey"-style predicate naming. Has a few template-syntax bugs (unbalanced parens in the Schema.org alignment block; "@(schema.Tables).Count" emitted mid-Turtle as a literal).

• ig_turtle_export.ini ("Turtle Export", 352 lines): more modest ontology section but adds SHACL shapes, per-table instance file, and SPARQL query examples. Uses a dedicated tmg: namespace ([url=http://casetalk.com/tmg/schema" rel="noopener]http://casetalk.com/tmg/schema[/url]#) for CaseTalk-specific predicates - much cleaner design.

Goal:

1. Merge into a single canonical Turtle/RDF export template:
   • Keep ig_turtle_export.ini's tmg: namespace design for CaseTalk predicates.
   • Fold in ttl.ini's PROV-O / VoID / annotation-property declaration blocks.
   • Keep the SHACL + SPARQL + per-table-instance outputs from ig_turtle_export.ini.
   • Fix the template-syntax bugs noted above.
   • Retire the now-duplicate template.
2. Adopt RDF 1.2 idioms in the consolidated template (Turtle is the natural vehicle - triple terms have no idiomatic RDF/XML):
   • Replace the synthetic :factExpressions / :businessRules string annotations with RDF 1.2 triple terms (<<:Customer :hasReading "Customer places Order">> :assertedBy :CaseTalk).
   • Stop hard-coding "@en"; emit the actual locale from database.Locale or table.Locale.
   • Emit rdf:dirLangString and base direction for RTL locales.

Out of scope: the OwlUnit RDF/XML conceptual-model exporter stays as-is for OTFT-level export. This ticket is about the schema-level Turtle path only.

Parent context: see 0005612 for the broader RDF 1.2 / OwlUnit audit.