-
Notifications
You must be signed in to change notification settings - Fork 46
Open
Labels
bugTechnical mistake, inconsistency with the documentation, etc.Technical mistake, inconsistency with the documentation, etc.
Milestone
Description
With the recent: "lets make everything a restriction" there is one inconsistently introduced that must be resolved, but also appears on untouched situations.
For every restriction we have in the schema, we must assure that all attributes that have be inherited from above are added (like an extension would guarantee). I can prove that before my changes (since 8 years) this would also be an issue, seen from here:
<xsd:complexType name="AlternativeTextRefStructure">
<xsd:annotation>
<xsd:documentation>Type for a reference to an ALTERNATIVE TEXT.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="VersionOfObjectRefStructure">
<xsd:attribute name="ref" type="AlternativeTextIdType" use="required">
<xsd:annotation>
<xsd:documentation>Identifier of an ALTERNATIVE TEXT.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="nameOfRefClass" type="NameOfClassAlternativeTextRefStructure" default="AlternativeText">
<xsd:annotation>
<xsd:documentation>Automatic reference class for AlternativeTextRefStructure</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
@ue71603 can you confirm that AlternativeTextRef is missing attributes like version in the formal definition?
Metadata
Metadata
Labels
bugTechnical mistake, inconsistency with the documentation, etc.Technical mistake, inconsistency with the documentation, etc.