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
This unicode character U+00B7 is explicitly allowed by the XML spec as a character in a namespace prefix, but this fails to parse (that middle-dot character is the U+B7).
This problem is in the ConstructingParser, but does not exist in the regular XML loader.
Here's an XML doc that illustrates the problem:
<?xml version="1.0" encoding="UTF-8"?><!--Note that in b· that middle dot is exactly that. Unicode0xB7. --><!--This middle doc character is expressly allowed by XML1.0 syntax for namespace prefixes. --><имен:schema
xmlns:имен="http://www.w3.org/2001/XMLSchema"
xmlns:dfdl="http://www.ogf.org/dfdl/dfdl-1.0/"
xmlns:b·="http://example.com"
targetNamespace="http://example.com"><имен:include schemaLocation="xsd/built-in-formats.xsd"/><имен:annotation><имен:appinfo source="http://www.ogf.org/dfdl/"><dfdl:format ref="b·:daffodilTest1" separator="" alignment="1" alignmentUnits="bytes" lengthUnits="bytes"
trailingSkip="0" initiator="" terminator="" leadingSkip='0' textTrimKind="none" initiatedContent="no"
ignoreCase="no" representation="text" textNumberRep="standard" encoding="ASCII"/></имен:appinfo></имен:annotation><имен:simpleType name="simTyp" dfdl:lengthKind="delimited" dfdl:initiator="1:"><имен:restriction base="имен:int"/></имен:simpleType><имен:element name="one"type="b·:simTyp"/></имен:schema>
The text was updated successfully, but these errors were encountered:
@som-snytt said:
I see, when you say it's "explicitly allowed" by the spec, the spec actually says, "COLON ... and MIDDLE DOT are explicitly permitted."
This unicode character U+00B7 is explicitly allowed by the XML spec as a character in a namespace prefix, but this fails to parse (that middle-dot character is the U+B7).
This problem is in the ConstructingParser, but does not exist in the regular XML loader.
Here's an XML doc that illustrates the problem:
The text was updated successfully, but these errors were encountered: