Formats, Profiles, and Translators

A filename is only the start of an interoperability question. This category explains how representation families, schemas, profiles, extensions, encodings, containers, versions, and translator implementations affect the information a receiver can interpret.

Overview

Use these articles before treating a support-table entry or file extension as a compatibility conclusion. First identify the representation and the job it must support. Then identify the precise scope inside that representation, confirm the direction and release of the product support, and account for the mapping work a translator performs.

A file may be syntactically valid while its external resources, layers, or package relationships are unavailable to the receiver. Those conditions can prevent the receiver from interpreting the intended data. Representation mechanics help you ask what must travel with the primary file; they do not replace validation of assembly dependencies, visual assets, or acceptance criteria.

Articles

Read the articles in this order:

1. Format, schema, profile, encoding, and extension defines the identifiers hidden behind a file label.
2. Native, neutral, and derived representations compares representation families by the next job and the information that must survive.
3. Schemas, application protocols, model views, and extensions explains the scope inside a nominally familiar format.
4. Read, write, import, and export shows how to interpret directional, release-bound support statements.
5. What a CAD translator actually has to do describes implemented mapping and its possible limits.
6. Containers, packages, and external resources helps determine whether “send the file” is enough.
7. USDZ package layout and resolver constraints gives a concrete checklist for package layout, path resolution, and receiver context.
8. Choosing an IFC serialization compares IFC-SPF, ifcXML, IFCZIP, and other listed formats by status and format-level trade-offs.
9. AutoCAD DWG version compatibility and downgrade effects shows the release ranges Autodesk lists and selected changes that can occur when saving an older format.
10. PCB fabrication representations separates layer images, job metadata, drill/rout data, and structured PCB manufacturing descriptions.
11. CAD assemblies to robot descriptions explains what URDF and SDFormat describe, what a CAD export declaration leaves open, and which package and receiver checks remain.

What this category does not establish

The existence of a format or profile does not prove that a particular application implements it, that a translator preserves a specific information layer, or that a received result is useful for the downstream task. Use geometry and topology, product structure and references, editability, and the portal’s validation content for those questions.