DCEG & FC: FairwayAggregation requires two Fairway features

[DavidGrant-NIWC]

Multiplicity of the binding to Fairway should be 2:∞ rather than 1:∞.

[JeffWootton]

Am concerned that, where a Fairway System and associated Fairway Aggregation is split at ENC dataset boundaries such that only one instance of a Fairway feature is included in the dataset, the dataset will fail a related validation check checking for at least 2 instances of Fairway to be included in a Fairway Aggregation association.

[DavidGrant-NIWC]

Am concerned that, where a Fairway System and associated Fairway Aggregation is split at ENC dataset boundaries such that only one instance of a Fairway feature is included in the dataset, the dataset will fail a related validation check checking for at least 2 instances of Fairway to be included in a Fairway Aggregation association.

• Good point and something I hadn't considered. In that case, 1,* makes sense, but you may want to note the reasoning somewhere.
• There is still a problem because the current DCEG requires 0,1 and the FC requires 0,*.
• Also, the reference to the aggregation should be to clause 25.7 instead of 25.13