participationFees: Adding id to changed merging behavior

[jpmckinney]

Before 1.1.3, participation fees had no id field, which meant the array was merged as a whole. An id field was added in 1.1.3 #48, per the schema style guide at the time.

However, this had the effect of changing the merging behavior to the identifier merge strategy.

To restore the original behavior, we can either:

1. Remove the id field
2. Add "wholeListMerge": true
   • We would also remove the suggestion that the id field will be required in future versions, which was added more recently in response to @yolile's comment in participationFees: Add id field to array of objects #48

@duncandewhurst @yolile What is your preference?

[jpmckinney]

I double checked, and I don't think any other id fields were added to extensions at that time (grepping for \*.*add.*\bid\b).

[yolile]

@jpmckinney right now, without the id field, if you have more than one item in the participation fees array CoVe report them as duplication (even if they are different)

[jpmckinney]

Can you report that issue on the CoVE repo?

[yolile]

Already reported OpenDataServices/cove#1246 for the array of strings case, but now updated with this case too

[duncandewhurst]

I prefer 2. to keep consistency of structure (if not merging strategy) with other arrays.

Also, if anyone extended participation fees to include a property which is an array then an id field would be necessary for flattening.

[jpmckinney]

Oops, we actually already set wholeListMerge in 1.1.4. No issue here, then!