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 is so easy because the golang xml parsing library already resolves the namespaces for us. Probably with a preparse phase, which is technically some sort of cheating, because now we don't need to keep any state in the validator, this state is kept in the parser for us by the golang xml parser.
nsName in relaxNG only matches the namespace and not the element name, so in this case relapse will need to be able match prefixes on names. The hardest part about this would be to design the syntax and thinking about whether names should allow all types of functions and not just a very constrained subset.
Also xmlns attributes would need to be matched which is currently conveniently done as an optional attribute with any value. When namespaces are returned by the parser their name will also require a more complex and specific pattern.
The text was updated successfully, but these errors were encountered:
Adding namespaces has three problems.
This is so easy because the golang xml parsing library already resolves the namespaces for us. Probably with a preparse phase, which is technically some sort of cheating, because now we don't need to keep any state in the validator, this state is kept in the parser for us by the golang xml parser.
nsName in relaxNG only matches the namespace and not the element name, so in this case relapse will need to be able match prefixes on names. The hardest part about this would be to design the syntax and thinking about whether names should allow all types of functions and not just a very constrained subset.
Also xmlns attributes would need to be matched which is currently conveniently done as an optional attribute with any value. When namespaces are returned by the parser their name will also require a more complex and specific pattern.
The text was updated successfully, but these errors were encountered: