You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The basic GML object properties like gml:description, gml:name, gml:boundedBy should be allowed in all feature type elements like SpatialPlan, PlanOrder, PlanObject and PlanRecommendation by the used XML Schema, as they are inherited from their supertypes gml:AbstractGMLType and gml:AbstractFeatureType. However, using gml:description for example returns a schema validation error.
The reason for the error is that the code adds the generated elements gml:identifier and lud-core:objectIdentifier as the first child elements of the container element, thus moving the gml:description in the wrong place. As per the GML XML Schema, the gml:identifier element must become after any gml:description element:
.. and any gml:boundedBy and gml:location before any lud-core elements:
<complexTypename="AbstractFeatureType"abstract="true">
<annotation>
<documentation>The basic feature model is given by the gml:AbstractFeatureType.
The content model for gml:AbstractFeatureType adds two specific properties suitable for geographic features to the content model defined in gml:AbstractGMLType.
The value of the gml:boundedBy property describes an envelope that encloses the entire feature instance, and is primarily useful for supporting rapid searching for features that occur in a particular location.
The value of the gml:location property describes the extent, position or relative location of the feature.</documentation>
</annotation>
<complexContent>
<extensionbase="gml:AbstractGMLType">
<sequence>
<elementref="gml:boundedBy"minOccurs="0"/>
<elementref="gml:location"minOccurs="0"/>
</sequence>
</extension>
</complexContent>
</complexType>
The basic GML object properties like gml:description, gml:name, gml:boundedBy should be allowed in all feature type elements like SpatialPlan, PlanOrder, PlanObject and PlanRecommendation by the used XML Schema, as they are inherited from their supertypes gml:AbstractGMLType and gml:AbstractFeatureType. However, using gml:description for example returns a schema validation error.
The reason for the error is that the code adds the generated elements
gml:identifier
andlud-core:objectIdentifier
as the first child elements of the container element, thus moving the gml:description in the wrong place. As per the GML XML Schema, the gml:identifier element must become after any gml:description element:.. and any
gml:boundedBy
andgml:location
before anylud-core
elements:Snippet of the tested document:
Error:
The text was updated successfully, but these errors were encountered: