IRI to URI change

[egekorkan]

Description of Changes

I am changing based on the result at #2156 (comment). However, the type is still anyUri, which is not correct (draft until that is solved?). In the meantime, I am also doing a fix to the link's href, which also mentions a form.

Related Issue

Closes #2156

Type of Change

• Normative with label

---

Preview | Diff

[egekorkan]

@TallTed @ektrah I have incorporated your feedback and added the co-authorship statements too. Thank you!

[egekorkan]

TD Call:

• @danielpeintner recommends putting a definition for absolute and relative URIs. Probably referring to URI specs
• The wording of Target URI of a submission target of a Form. It MUST be resolved with the value in the base in Thing-level. should be changed to Target URI of a submission target of a Form. The target URI MUST be resolved using the base URI at the Thing-level.
• @mahdanoura should update the toolchain repo
• Type issue: Fixes can be
  • string but adding a regex/ABNF -> not interoperable with implementations in different languages
  • string but adding (specifically RFC3986) after it
  • anyURI but adding (here it is restricted to an "ASCII URI") after it

The first 2 points will be fixed by @egekorkan . The other two, we can wait for further feedback.

[egekorkan]

TD Call:

• More time for review will be given since this

• Following enhancement

It can be found in the href member of a Form in a Thing Description.

better to say OR as a result of base + relative href

• absolute and target definitions should be separated.
• order should be base, relative, absolute, target.
• note in 5.2 to be linked in base term
• assertion under form table should mention if base exists, it must be resolved against kind of wording

[egekorkan]

locally no errors but very obvious one detected on the pipeline: