STIDS 2026 made one thing clear: the future of AI depends on more than larger models and larger datasets. It depends on better representations, better governance, and better conceptual clarity.

Highlights​

• Strong participation from government, industry, and academic researchers.
• Serious discussion of ontology engineering as infrastructure for AI.
• Increased attention to knowledge graphs, semantic interoperability, and data quality.
• Productive overlap with KGOIDS and related defense and intelligence communities.
• Renewed interest in NCOR as a hub for ontology best practices.

What comes next​

NCOR will continue building the infrastructure around ontology education, certification, best practices, and community coordination. STIDS 2026 was not just an event. It was a signal that this field is entering a new phase.

Most organizations think they have an interoperability problem.

They have too many systems. Too many dashboards. Too many databases. Too many teams using different words for similar things and the same words for different things. So they buy a platform, build APIs, export data, create pipelines, and declare victory when the data finally moves from one place to another.

But moving data is not the same as preserving meaning.

A spreadsheet can be exported. A JSON object can be passed through an API. A table can be replicated from one system to another. None of that guarantees that the receiving system understands what the data means.

Take something as ordinary as location.

In one system, location might mean where an object was observed. In another, where it is assigned. In another, its last known position. In another, its expected destination. In another, a region associated with responsibility, ownership, service coverage, or responsibility.

The field name is the same. The meaning is not.

Every few years, someone declares that open semantic standards are obsolete.

The argument usually sounds practical. The market has moved on. Developers prefer simpler formats. Operational platforms need speed and scale. Business users need dashboards, workflows, and applications, not formal models.

There is a grain of truth to this.

Operational platforms should not be judged only by whether they use a semantic standard as their native runtime architecture. Serious systems are layered. They combine SQL, JSON, APIs, graph stores, search indexes, workflow engines, code, and user interfaces.

No one should expect one standard to do every job.

But that does not mean open semantic standards are irrelevant. It means we need to understand what job they are supposed to do.

Open semantic standards give organizations a transparent, inspectable, machine-readable way to represent shared meaning.

Here is a simple test for any platform that claims to preserve meaning.

Give it a model and a representative dataset. Let it ingest them. Let it operate on them. Query the results. Run validations. Export everything back out.

Then compare what came out with what went in.

This is the round-trip fidelity test.

The test is not about whether the platform uses one particular internal technology. It can use tables, objects, graphs, documents, indexes, APIs, workflows, or code. Internal implementation is not the main issue.

The issue is whether the important meaning survives.

The next competitive advantage in data will not come from collecting more of it.

Most organizations already have more data than they can understand.

The advantage will come from governing meaning.

That means knowing what your important terms mean, how they relate, where definitions live, which identifiers are stable, which models are authoritative, which systems are downstream, which transformations are safe, and which assumptions are being made.

It means treating semantics as infrastructure, not afterthought.