Skip to content
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.

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

Clarify presence rules for scenario ID/name for references #53

Open
kleihan opened this issue Nov 27, 2023 · 0 comments
Open

Clarify presence rules for scenario ID/name for references #53

kleihan opened this issue Nov 27, 2023 · 0 comments
Assignees
Labels
SCENARIO Support for scenarios

Comments

@kleihan
Copy link
Member

kleihan commented Nov 27, 2023

Orchestra v1.1 added scenarios as top level element and added a numerical identifier. References are now possible by name and/or identifier whereby both are optional but also have a default value.

		<xs:attribute name="scenario" type="fixr:Name_t" default="base">
			<xs:annotation>
				<xs:documentation>The use case of an element, distinguished by workflow, asset class, etc.</xs:documentation>
			</xs:annotation>
		</xs:attribute>
		<xs:attribute name="scenarioId" type="fixr:id_t" default="1">
			<xs:annotation>
				<xs:documentation>Unique identifier of a scenario. Default is '1' for base scenario.</xs:documentation>
			</xs:annotation>
		</xs:attribute>

Does this mean that absence of scenario/scenarioID in a reference makes it "base"/"1"? That would require both name and ID to be present unless it is really the base scenario.

Chapter 3.5 Scenarios should be extended to clarify the referencing of scenarios.

@kleihan kleihan added this to the Orchestra v1.1RC2 milestone Nov 27, 2023
@kleihan kleihan self-assigned this Aug 9, 2024
@kleihan kleihan added SCENARIO Support for scenarios and removed question labels Aug 21, 2024
@kleihan kleihan moved this to Backlog in Orchestra v1.1 RC2 Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SCENARIO Support for scenarios
Projects
Status: No status
Development

No branches or pull requests

1 participant