Reorganizing uri variables section

[egekorkan]

fixes #302 (the discussion is documented there)

[netlify[bot]]

✅ Deploy Preview for wot-binding-templates ready!

Name	Link
🔨 Latest commit	d3bb43b95ec4ce2d37b4bb94689365478e8aea42
🔍 Latest deploy log	https://app.netlify.com/sites/wot-binding-templates/deploys/6539337020c7100008619612
😎 Deploy Preview	https://deploy-preview-309--wot-binding-templates.netlify.app/bindings/protocols/bacnet
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[egekorkan]

Call of 18.10:

• We can use the forms for anything protocol-specific and in TD 2.0 we can have a nicer solution
• default can be used to indicate a constant value
• Example direction:

  {
  "@context": "https://www.w3.org/2022/wot/td/v1.1",
  "properties": {
      "analog1": {
          "type": "number",
          "readOnly": true,
          "forms": [{
              "op": [ "observeproperty" ],
              "href": "bacnet://5/0,1/85",
              "bacv:service": "subscribeCOVproperty",
              "bacv:covIncrement": {
                "type":"number",
                "minimum":0,
                "default":0.2
              }
          }]
      }
  }
  }

[egekorkan]

Call of 25.10:

• @lu-zero : put the vocabulary terms involving the binding protocol only in the form, so consumers unaware of the binding can still safely consume the affordance as long there are forms it can consume
• @danielpeintner: We are creating a difference for the programmers (looking at affordance for uriVariables, looking at forms for bacnet). Agree with the reasoning but the solution is still not perfect.
• @mjkoster : We should keep the separation of concerns and formalize this decision. @fennibay and @ektrah should be ok with this from the previous discussions but we can keep it open for review.

[egekorkan]

As a result of https://github.com/w3c/wot-binding-templates/issues/302#issuecomment-1812825940, we will close this PR without merging. A follow up PR should change the URI Scheme to add the two parameters but also a warning saying "TD.next will change this"