Specifications

Fifty-one companion specifications. The table below shows for each: namespace, enum count, DTO count, codec count, registrar class names, and direct (non-transitive) dependencies.

Totals at v4.3.0: 309 enums, 193 DTOs, 193 codecs, 56 registrars (some specs ship two), 51 specs.

Reading the table

• Enums / DTOs / Codecs — counts of files in each category for that spec. — means none.
• Registrar(s) — the class name(s) under PhpOpcua\Nodeset\<Spec>\. The directory name is always the spec name in PascalCase; the registrar class may differ. See What gets generated — naming inconsistencies.
• Depends on — direct (non-transitive) dependencies declared by the registrar's dependencyRegistrars(). Loading the spec via loadGeneratedTypes() pulls these in (and recursively their own dependencies) unless only: true is passed. See Dependency resolution.

The dependency root specs

A handful of specs sit at the root of the dependency graph — they do not depend on anything else and are pulled in by many downstream specs.

If your application loads several "downstream" specs, the cascade brings the roots in transitively. You almost never load DI explicitly — but it is in the loaded set for nearly every real deployment.

Picking specs for your deployment

Start from what the server publishes:

$client = ClientBuilder::create()->connect('opc.tcp://your-server:4840');

foreach ($client->read('i=2255')->getValue() as $idx => $uri) {
    echo "ns=$idx → $uri\n";
}

Match the URIs the server lists against the OPC Foundation's companion-spec URIs (the UA-Nodeset directory naming is a strong hint — Robotics/ → http://opcfoundation.org/UA/Robotics/). Load the registrars for those specs only.

The non-standard registrar names

For convenience, the registrar class names that do not follow <Spec>Registrar in PascalCase:

Bookmark this table; IDE autocomplete handles the rest.