Should tm:required have a default value?

[egekorkan]

Coming from #1400, it might be a good idea to specify a default value for tm:required in order to say that all affordances are required unless otherwise specified. We can collect opinions here

[egekorkan]

Given that this would imply changes implementations, probably for 2.0. Some other directions might be having another value type for it with values like "all", "properties/*" to have some shortcuts.

[sebastiankb]

I think, we can also express in the spec that the following convention such as:

    "tm:required": [
        "/properties",
        "/actions/fadeIn"
    ]

have to interpret, that all properties are required and all other affordances such as actions, except fadeIn, and events are optional.

[sebastiankb]

from today's TD call:

• it seems to be there is no perfect solution since there can be different use cases with different requirements (e.g., there are 100 properties, however, two of them are optional)
• we should be more clear, that required is optional. We need to update the assertion.
• at the end it is also a question of the used tooling that generates TD instances out of TMs and what are there default assumptions (e.g., in case of optional affordances)
• the group discussed 4 options:

1. no default
2. default is "all required" --> would break JSON Schema paradigm
3. default is "none required" --> as is
4. we will define "required" mandatory

• please provide your opinions on these options

[egekorkan]

not relevant anymore, closing

[JKRhb]

not relevant anymore, closing

Hmm, has this issue been kept open intentionally, or could it actually be closed then?