Skip to content

Commit ae94051

Browse files
NikolaiFaNikolaiFa
authored andcommitted
Clarify support for mixed SSP versions in nested SSP
1 parent 2ad515a commit ae94051

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

docs/5___ssd.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -819,6 +819,9 @@ For components that are packaged inside an SSP that contains this SSD, this is *
819819
When referencing another SSP, by default the default SSD of the SSP (i.e. `SystemStructure.ssd`) is referenced.
820820
When a non-default SSD should be selected, then the name of the non-default SSD *MUST* be given through a fragment identifier, i.e. the URI `resources/SubSSP.ssp#VariantB.ssd` would reference the `VariantB.ssd` of `SubSSP.ssp` located in the resources directory relative to this SSD.
821821

822+
{empty}[ _An SSP may contain nested SSP files that conform to different SSP versions.
823+
Tools can safely load SSP files using the latest supported version due to backward compatibility._ ]
824+
822825
When the URI is a same-document URI with a fragment identifier, for example `#other-system`, then the fragment identifier *MUST* identify a system element in this SSD document with an id attribute identical to the fragment identifier.
823826
This mechanism can be used to instantiate an embedded system definition multiple times through reference to its definition element.
824827

0 commit comments

Comments
 (0)