issue while importing XSD

By | May 18, 2018

If you are trying to work with XSD you may encounter following errors

  • Namespace ‘’ is not available to be referenced in this schema.
  • Imported schema for namespace ‘’ was not resolved.

This error means that either you need to declare the namespace “” within XSD or the xml.xsd file in which this namespace is declared is not available.

If you need to declare the namespace, add the following line within xsd as a first child within <xsd:schema> tag

<xsd:import namespace="" schemaLocation="xml.xsd" />

Also the directory in which you have your xsd file, you need to have xml.xsd file available. Create xml.xsd file within the same directory and add following code in it.

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="" targetNamespace="" xml:lang="en">
      <xs:documentation>See and for information about this namespace.</xs:documentation>
      <xs:documentation>This schema defines attributes and an attribute group
suitable for use by
schemas wishing to allow xml:base, xml:lang or xml:space attributes
on elements they define.

To enable this, such a schema must import this schema
for the XML namespace, e.g. as follows:
<schema . . .>
. . .
<import namespace=""

Subsequently, qualified reference to any of the attributes
or the group defined below will have the desired effect, e.g.

<type . . .>
. . .
<attributeGroup ref="xml:specialAttrs"/>

will define a type which will schema-validate an instance
element with any of those attributes</xs:documentation>
      <xs:documentation>In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
At the date of issue it can also be found at
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML Schema
itself. In other words, if the XML Schema namespace changes, the version
of this document at will change
accordingly; the version at will not change.</xs:documentation>
   <xs:attribute name="lang" type="xs:language">
         <xs:documentation>In due course, we should install the relevant ISO 2- and 3-letter
codes as the enumerated possible values . . .</xs:documentation>
   <xs:attribute default="preserve" name="space">
         <xs:restriction base="xs:NCName">
            <xs:enumeration value="default" />
            <xs:enumeration value="preserve" />
   <xs:attribute name="base" type="xs:anyURI">
         <xs:documentation>See for
information about this attribute.</xs:documentation>
   <xs:attributeGroup name="specialAttrs">
      <xs:attribute ref="xml:base" />
      <xs:attribute ref="xml:lang" />
      <xs:attribute ref="xml:space" />
Vishal Monpara is a full stack Solution Developer/Architect with 12 years of experience primarily using Microsoft stack. He is currently working in Retail industry and moving 1’s and 0’s from geographically dispersed hard disks to geographically dispersed user leveraging geographically dispersed team members.

Leave a Reply

Your email address will not be published. Required fields are marked *