Details
Description
There is no restriction on the String that can be used as the name for a Named. This does not seem sensible as there have already been problems in Taverna 1 and 2 with weirdly named objects. Previously, any constraints were implicitly enforced by the workbench UI. This is no longer possible.
It would be better if there were restrictions on the name e.g. that it is alphanumeric.
The scufl2 code itself and the workflow bundle serialization can cope with any kind of name (up to a reasonable size), as it is escaped where needed.
Practically though, I agree. The name of workflow bean is meant to be used somewhat similar to a variable name in programming, and so should not be a big essay or contain control characters. It is however important to upport international Unicode characters as we should not require workflows to be built in English.
It is however out of scope for SCUFL2 to restrict names based on for instance how the workflow would be serialized as SVG within the Taverna Workbench - that could be a moving target.
I am leaving this open, as a minimum characters such as "/" and "\n" should not be allowed. A maximum length of say 128 might be sensible.