Skip to content

Do not require explicit scenario definitions #285

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kleihan merged 1 commit into from
Mar 13, 2026
Merged

Do not require explicit scenario definitions #285

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 2 additions & 22 deletions repository/src/main/resources/xsd/repository.xsd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,7 @@
</xs:key>
<xs:key name="messageIdKey">
<xs:annotation>
<xs:documentation>Combination of message id and scenario ID must be unique</xs:documentation>
<xs:documentation>Combination of message id and scenario must be unique</xs:documentation>
</xs:annotation>
<xs:selector xpath="fixr:message"/>
<xs:field xpath="@id"/>
Expand Down Expand Up @@ -260,31 +260,11 @@
<xs:field xpath="@codeSet"/>
<xs:field xpath="@scenario"/>
</xs:keyref>
<!-- A scenario used in a code set definition must be a valid scenario defined in the list of scenarios -->
<xs:keyref name="codeSetScenarioKeyRef" refer="fixr:scenarioKey">
<xs:selector xpath="fixr:codeSets/fixr:codeSet"/>
<xs:field xpath="@scenario"/>
</xs:keyref>
<!-- A scenario used in a component definition must be a valid scenario defined in the list of scenarios -->
<xs:keyref name="componentScenarioKeyRef" refer="fixr:scenarioKey">
<xs:selector xpath="fixr:components/fixr:component"/>
<xs:field xpath="@scenario"/>
</xs:keyref>
<!-- A scenario used in a group definition must be a valid scenario defined in the list of scenarios -->
<xs:keyref name="groupScenarioKeyRef" refer="fixr:scenarioKey">
<xs:selector xpath="fixr:groups/fixr:group"/>
<xs:field xpath="@scenario"/>
</xs:keyref>
<!-- A scenario used in a message definition must be a valid scenario defined in the list of scenarios -->
<xs:keyref name="messageScenarioKeyRef" refer="fixr:scenarioKey">
<xs:selector xpath="fixr:messages/fixr:message"/>
<xs:field xpath="@scenario"/>
</xs:keyref>
</xs:element>
<!-- Scenario definitions -->
<xs:element name="scenarios">
<xs:annotation>
<xs:documentation>The default scenario is id='1' name='base'.</xs:documentation>
<xs:documentation>The default scenario is name='base'.</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
Expand Down
Loading