cvc-id.1

Notice! This page describes the nature of the error using a hypothetical example and not the erroneous data of the input test file. You should however be able to apply this information to your error case.

General description of the error:

The format of the error message: cvc-id.1: There is no ID/IDREF binding for IDREF ''{0}''.

Error description in schema standard: http://www.w3.org/TR/2007/WD-xmlschema11-1-20070830/#cvc-id

Possible causes for this error:

There are elements in the schema with attributes containing IDREF ("xsd:IDREF") and ID ("xsd:ID") definitions. This means that for every IDREF-type element there must be a matching ID-type element. This could possibly require access to the schema to see what elements should be matched.

An example

<amenities>
      <amenityIDREF>DG000000</amenityIDREF>
      <amenityOpenHour>14:20:0Z</amenityOpenHour>
      <amenityCloseHour>14:20:0Z</amenityCloseHour>
</amenities> 

  <amenity>
    <amenityID>ID000001</amenityID>
    <amenityType>String</amenityType>
  </amenity>
  <amenity>
    <amenityID>ID000002</amenityID>
    <amenityType>String</amenityType>
  </amenity>

Error message:

Error cvc-id.1: There is no ID/IDREF binding for IDREF 'DG000000'.

How to fix: In this example 'amenityIDREF' is of the type 'xsd:IDREF' and 'amenityID' is of the type "xsd:ID". There is no matching ID-element for IDREF-element with the value 'DG000000'. The error can be corrected by adding a new 'amenity' element and an ID-element with corresponding value.

<amenity>
<amenityID>DG000000</amenityID>
<amenityType>String</amenityType>
</amenity>

Another option is to change to value of amenityIDREF to reference to some of the existing amenityID's. Which correction is correct, depends on what you want to achieve.