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
The symbol attribute for AbstractState, which StandardPolymorphicStateSet inherits from, is defined as xs:anySimpleType, so presumably anything should go, including "1 and 0".
That's in contrast to StandardState, which also inherits from AbstractState but restricts the symbol attribute to StandardToken.
It seems the NeXML validator, which I think is based on running Bio::Phylo, confuses the symbol datatype restrictions.
Mmmm... the nexml validator is only partially based on Bio::Phylo, namely insofar as checking for complex referential integrity. Basic type validation is done using the schema. So if the type passes, I guess it's valid...?
The
symbol
attribute forAbstractState
, whichStandardPolymorphicStateSet
inherits from, is defined asxs:anySimpleType
, so presumably anything should go, including "1 and 0".That's in contrast to
StandardState
, which also inherits fromAbstractState
but restricts thesymbol
attribute toStandardToken
.It seems the NeXML validator, which I think is based on running Bio::Phylo, confuses the
symbol
datatype restrictions.See phenoscape/phenoscape-kb-services#149 for the original issue.
The text was updated successfully, but these errors were encountered: