I don't know if we can do this; we haven't (AFAIK) used the default attribute anywhere else in the schema because I think it would interfere with the UPDATE semantics (which allow you to leave out a value that you don't wish to set).

The prose you have written already has this effect, so I don't think it's necessary. Do you feel this is essential?

@svs explicitly requested this durring the plenary.

Understood. Have just messaged @svs, I think he's OK to leave this out as long as it's sufficiently clear in the prose.

@canterburym OK, understood. I will revert this last change.

Indeed. Let's take out default here but make the parameter mandatory in the spec and remove the "default" wording from the text, so that an LEA always has to explicitly indicate what they want. Idea behind it being "explicit is better than implicit".

Thanks both!

In fact, mandatory will not really work (or would be confusing), as this cannot be used for TS 102 232-4. Therefore, I will just revert the change and will not change the text (for the time being).