A local Siemens API knowledge graph
2ot can derive a version-aware graph from Siemens TIA PublicAPI assemblies and documentation on the developer's own machine. The graph is tooling infrastructure, not a hosted copy of Siemens' API corpus.
Local by design
The intended workflow keeps Siemens-derived API metadata and generated graph artifacts on the developer machine where the licensed Siemens software and PublicAPI inputs are installed. 2ot can describe the graph format and tooling publicly without redistributing the proprietary API corpus or turning the website into a mirror of Siemens documentation.
Read assembly metadata without loading the Siemens assemblies into the active runtime, and merge XML documentation when it is present.
Build a compact, versioned graph package with stable metadata, hashes and an input manifest so changed API inputs can be detected.
Generate adjacent-version diffs locally to understand what changed between installed TIA PublicAPI releases.
What the graph contains
The graph normalizes assembly, type, method and documentation relationships into a compact runtime package. XML summaries, parameters, return values, exceptions and references can be merged when Siemens ships the corresponding documentation files.
Why 2ot uses it
The graph gives local tooling a structured view of the TIA engineering API across versions. That can support code generation, compatibility checks, help surfaces and integration development while keeping vendor-owned source material at the licensed workstation boundary.
The website intentionally stops at the boundary
This site documents the architecture and the capabilities of the local graph pipeline. It does not expose browsable Siemens API members, generated Siemens documentation, local graph snapshots or cross-version corpus data. Those artifacts belong in the developer's local environment and should be handled in accordance with the applicable Siemens license and EULA.