remove wildcard in xpath selector to fix ValueSet validation error#224
Open
haeckerbaer wants to merge 2 commits into
Open
remove wildcard in xpath selector to fix ValueSet validation error#224haeckerbaer wants to merge 2 commits into
haeckerbaer wants to merge 2 commits into
Conversation
tim-rivett
reviewed
Jun 9, 2026
tim-rivett
left a comment
Collaborator
There was a problem hiding this comment.
This fixes the XMLSpy problem.
Has anyone got Oxygen, MS tools etc to check it doesn't cause problems in those.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As discussed and decided during SG7 meeting on 25.03.2026:
xml spy seems to throw the following error:
idc-selector-no-match:`` the selector './/siri:Values/siri:*' of identity constraint definition 'TypeOfValue_unique' doesn't match within the content model of element declaration 'ValueSet'.For identity constraints, the selector xpath must seemingly be a restricted xpath that the schema processor can statically verify against the content model. Currently the expression contains "//" (descendant-or-self axis abbreviation) and "" (wildcard element name). Some schema validators cannot prove that this selector corresponds to elements allowed by the content model of ValueSet due to the wildcard selector siri:.
Unfortunately I don't have xml spy to validate but an explicit selector should fix the error.