Resource patterns for href and maybe more

[egekorkan]

Coming from #2153 and #2176

When there are href in all affordances with the pattern properties/myPropertyName, this can be constructed based on the affordance type and the affordance name. This can be part of a form definition but not a form instance, thus reduce the copy paste effort.

Notes:

• We should be careful with the syntax to not mix it with TM placeholders since a TM can have this form definition too.
• Are there other fields in a form that can benefit from this?
• Should we go for this optimization at all? While it allows expressing this pattern and making TDs more compact, it implies more parsing effort.

[egekorkan]

TD call:

• This can be in binding defaults. This would help with the WebThing protocol issue Same href for all Forms #2182
• Can be added on top but it needs to be compatible with the templating mechanism we have.
• Can be tackled later.

[benfrancis]

This would help with the WebThing protocol issue #2182

I don't think this is necessary for the Web Thing Protocol WebSocket sub-protocol since all affordances tend to share the same href.

When there are href in all affordances with the pattern properties/myPropertyName, this can be constructed based on the affordance type and the affordance name.

Whilst we have always used this convention on the WebThings project, the URL structure is not prescribed either by the legacy Web Thing REST API or W3C WoT Profiles and I think that's a good thing.

I don't strongly oppose the idea of resource patterns but I personally wouldn't bother due to the increased parsing complexity.