The tagdoc for <elementSpec> clearly says that the @prefix attribute has as its value 0–1 occurrences of teidata.xmlName. Makes sense, because it is defined as
The <remarks> then go on to explain that “Colons, although permitted inside the value, will cause an invalid schema to be generated.”
Two problems jump out at me:
Colons are not permitted inside the value (because teidata.xmlName is xs:NCName).
Zero occurrences of xs:NCName (i.e., prefix="") is flagged as an error, because the RELAX NG actually has attribute prefix { xsd:NCName }?, which means that the attribute is optional, but if it is present it must have a value.
(1) is just a documentation error, IMHO, to be solved here, probably by deleting the <remarks>.
(2) is likely to be a Stylesheets problem, so will probably have to make a similar ticket on that repo.
(Problem (2) is also a problem for the @prefix of <moduleSpec> and <schemaSpec> but they have avoided problem (1).)
The tagdoc for
<elementSpec>clearly says that the@prefixattribute has as its value 0–1 occurrences of teidata.xmlName. Makes sense, because it is defined asThe
<remarks>then go on to explain that “Colons, although permitted inside the value, will cause an invalid schema to be generated.”Two problems jump out at me:
prefix="") is flagged as an error, because the RELAX NG actually hasattribute prefix { xsd:NCName }?, which means that the attribute is optional, but if it is present it must have a value.(1) is just a documentation error, IMHO, to be solved here, probably by deleting the
<remarks>. (2) is likely to be a Stylesheets problem, so will probably have to make a similar ticket on that repo.(Problem (2) is also a problem for the
@prefixof<moduleSpec>and<schemaSpec>but they have avoided problem (1).)