The current schema download, which shouldn't contain pending items, still contains references to those items. Probably not an issue for systems that are using inferencing, but for non-inferencing systems that are processing the schema, it can cause a problem.

For instance, the DE-IM9 geoXXX properties are defined with ranges that include the pending GeospatialGeometry class. However, because its pending, the GeospatialGeometry class itself isn't defined in the schema. This inconsistency can cause automatic processing of the schema file to fail.

Another example is the pending CssSelectorType, which is defined as the range for cssSelector property. The CssSelectorType definition doesn't appear in the schema.

I think whatever code is being used to produce the schemas is properly ignoring the pending definitions, but not properly ignoring references to them.