On 09/13/2016 01:29 AM, Leif Halvard Silli wrote:
XMLmind 7.1 claims the below document to be invalid - complaining that
the figure element breaks " [cvc-complex-type.2.4]". What XMLmind (seems
to) think to be incorrect is the lack of any other element but the
figcaption element. To put it differently, XMLmind expects figure to
contain at least one non-figcaption element.
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml";>
<head>
<title>This document is valid</title>
</head>
<body><figure id="contents"><figcaption>Innhald</figcaption></figure>
</body>
</html>
However, note that HTML5.1 says that the content model of figure is
“flow content”. And that “text” is part of “flow content”. And further,
that “Text, in the context of content models, means either nothing, or
Text nodes”. (Text defition: https://www.w3.org/TR/html51/dom.html#text )
Thus, a figure element can be totally empty (since empty/nothing is
considered to be "text") - and still be valid. And hence, the above
document is valid.
That's right.
Replaced:
---
<xs:element name="figure">
<xs:complexType mixed="true">
<!-- LIMITATION: allows to have text other than whitespace
before leading figcaption or trailing figcaption. -->
<xs:choice>
<xs:sequence>
<xs:element ref="figcaption"/>
<xs:group ref="flowContent" maxOccurs="unbounded"/>
</xs:sequence>
<xs:sequence>
<xs:group ref="flowContent" maxOccurs="unbounded"/>
<xs:element ref="figcaption" minOccurs="0"/>
</xs:sequence>
</xs:choice>
<xs:attributeGroup ref="globalAttributes"/>
</xs:complexType>
</xs:element>
---
by:
---
<xs:element name="figure">
<xs:complexType mixed="true">
<!-- LIMITATION: allows to have text other than whitespace
before leading figcaption or trailing figcaption. -->
<!-- SCHEMA VALIDATION ERROR:
figcaption violates "Unique Particle Attribution".
(May be removed by replacing second ref="flowContent"
minOccurs="0"
by ref="flowContent".) -->
<xs:choice>
<xs:sequence>
<xs:element ref="figcaption"/>
<xs:group ref="flowContent" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:sequence>
<xs:group ref="flowContent" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="figcaption" minOccurs="0"/>
</xs:sequence>
</xs:choice>
<xs:attributeGroup ref="globalAttributes"/>
</xs:complexType>
</xs:element>
---
which causes Xerces to report a schema validation error:
---
[Error] xhtml5_noscript.xsd:616:34: cos-nonambig:
"http://www.w3.org/1999/xhtml":figcaption and
"http://www.w3.org/1999/xhtml":figcaption (or elements from their
substitution group) violate "Unique Particle Attribution". During
validation against this schema, ambiguity would be created for those two
particles.
---
However, XMLmind XML Editor does *not* use Xerces to perform schema or
instance validation and does not care about "Unique Particle
Attribution". So this is no really a problem when our XHTML5 schema is
used in the context of XMLmind XML Editor.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
