René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Put all UI related parameter options in metadata","articleBody":"In the current spec all UI related options of computation template parameters are in the [json object](https://github.com/VirtualProgrammingLab/documentation/blob/viplab3.0-json/docs/viplab3.0/computation_template.md#json-object-parameter). Like the in the rest of the spec all ui related stuff should be placed in a metadata sub property, so it's simply to filter these options in the websocket-api and keep the websocket api independen of any new added option.\r\n\r\nOnly the validation should not be in the metadata of the parameter, because it's used by the websocket-api to validate the user input. The `validation` property of the parameter should not be a string but rather an object which contains all the validation settings, that are currently spread across  the parameter object.\r\n\r\nI don't understand the difference between `oneof` and `anyof`.\r\n\r\nIt's not defined how a \"numeric value\" is defined for range. Because to check the range the \"number\" needs to be parsed. Which formats are allowed, int, float, \".\" or \",\" as separator? We should keep this validation on the server side simple, so we have not to deal with programming language specific formats.","author":{"url":"https://github.com/Legion2","@type":"Person","name":"Legion2"},"datePublished":"2020-05-09T21:52:31.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/3/documentation/issues/3"}