Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Step options of type QName need to be finessed #528
Making the option type 'xs:QName' is going to be inconvenient for users:
We probably need to say that it's value is anyAtomicType. If it's a string, then we apply the rules for converting it to a qname (including the rule about colons), if it's lexically an EQName then make it into a QName that way.
Introduce new dynamic errors for attempts to use non-string values (5, 3.4, etc.) or strings that aren't lexically QNames.