KERML — Some package-level features are mandatory

[From Vince Molnar] Package-level features do not give featuring types, and some have lower multiplicity greater than zero, meaning everything in the universe (instances of Anything), including every data value, is required to give at least that number of values to them (see KERML-56). For example, the libraries include:

Clocks::universalClock[1] {...}
Observation::defaultMonitor[1] : ChangeMonitor[1] {...}
SpatialFrames::defaultFrame : SpatialFrame[1] {...}

Might be others. This one

Occurrences::earlierFirstIncomingTransferSort: IncomingTransferSort{... }

does not give a multiplicity, I couldn't find what this means (even for expressions), tho this particular feature is supposed to have exactly one value.

Defer

The features universalClock, defaultMonitor and defaultFrame are intended to be single values that are universally available (see also resolution KERML-214 to issue KERML-56). The feature earlierFirstIncomingTransferSort has multiplicity [0..*] by default. It is used as the default for the feature Occurrence::incomingTransferSort, which also has multiplicity [0..*], so the multiplicity is appropriate.

The problem, though, is that they are not actually single values that are universally available, but features of Anything, which means that every instance in the Universe will have their own copy. There does not seem to be anything that would force the values of different instances of these features to be the same.

However, due to lack of time, the FTF is deferring further consideration of this issue to a future FTF or RTF.