Editorial methodology

Evidence before claims.

The directory is designed to distinguish what a product says, what an official source demonstrates, and what has not yet been checked.

Three evidence states

Yes

A current official source or reproducible product test supports the capability.

No

A reliable source or test establishes that the capability is not supported. An absent marketing claim is not sufficient evidence for No.

Unknown

The capability has not yet been verified. Unknown is not a negative finding.

Classification rules

• Platform is where the product runs, such as Windows, Linux, macOS, or a browser.
• Access mode describes how people use it, such as desktop, web application, command line, or editor integration.
• Runtime or host records dependencies such as Java, Eclipse, or VS Code.
• Modeling interface separates graphical, textual, and hybrid experiences.
• Tool type distinguishes semantic model editors from diagram generators and drawing tools.

Source priority

1. Current official product documentation and release notes.
2. Official standards conformance or interoperability material.
3. Reproducible testing against a named version.
4. Vendor statements, clearly labeled when independent verification is unavailable.

Corrections

Every record includes a last-checked date and source links. Vendors and users can submit a correction; all changes are reviewed before publication.