cvc-elt.1.a: cannot find the declaration of the root

What the message literally means

In this pair the XSD declares stock in urn:example:stock. The failing XML has an unqualified stock, which belongs to no namespace. Adding the intended default namespace changes stock and its unprefixed sku child into the expanded names expected by the qualified schema.

Three common causes to check first

1. The root namespace URI differs from targetNamespace, or the XML omits the required namespace entirely. Namespace names are exact identifiers, including case and trailing punctuation.
2. The wrong schema entry point was selected. A file containing only reusable types may have no global declaration for the application’s document root.
3. The root name or vocabulary version changed. A similar-looking declaration from a different release does not establish compatibility with the incoming document.

Repair and retest

Write down the root as {namespace URI}local-name and compare it with a top-level xs:element in the loaded entry schema. Confirm that the application explicitly supplies that schema. For multi-file contracts, load the full project and select its actual root XSD. Recheck qualification of descendants after correcting the root, since elementFormDefault can expose additional mismatches.

When this is a namespace problem

This specimen is a namespace error: the only XML change adds xmlns="urn:example:stock". Declaring xmlns:xsi or adding a schemaLocation hint alone would not put stock in that namespace. Conversely, changing only the prefix while retaining the correct binding leaves the expanded name unchanged.

System.Xml.Schema: unknown root warnings versus errors

With ReportValidationWarnings enabled, the tested .NET reader returned warnings for stock and sku, with no error event. Treat that as missing schema coverage, not proof of validity. Xerces, libxml2 and XSDHub’s second engine reject this same root. The strict-wildcard guide covers a different .NET message: “is not declared”.

Complete tested XML and XSD pairs

Open either variant in the workbench, then choose Validate XML. Loading an example does not run validation or send documents; server checks require the existing permission checkbox.

These transcripts were captured on 5 November 2026 from the exact files shown below. Download all measured results and SHA-256 hashes.

<stock>
  <sku>BK-204</sku>
</stock>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:example:stock" elementFormDefault="qualified">
  <xs:element name="stock">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="sku" type="xs:string"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>
</xs:schema>

<stock xmlns="urn:example:stock">
  <sku>BK-204</sku>
</stock>

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:example:stock" elementFormDefault="qualified">
  <xs:element name="stock">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="sku" type="xs:string"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>
</xs:schema>

cvc-elt.1.a: Cannot find the declaration of element 'stock'.

No error event; warnings:
Could not find schema information for the element 'stock'.
Could not find schema information for the element 'sku'.

Element 'stock': No matching global declaration available for the validation root.

'stock' is not an element of the schema

Saxon comparison and test scope

Saxonica documents XSD processing as an Enterprise Edition feature. The Saxon rows map the named constraint, rather than presenting an invented message. The four measured rows are Xerces, .NET, the shipped workbench engine and XSDHub’s second engine.

The corrected results apply to these self-contained XSD 1.0 specimens. They do not establish business-rule acceptance for a different document or schema version.

Continue the diagnosis

• xml namespaces explained
• cvc-complex-type.2.4.c: strict wildcard, missing declaration
• xsd import include errors

All parser error codes · XML and XSD validator

Primary references

• Apache Xerces message catalogue
• Microsoft: schema validation and identity checks