Prepare Testfest/Plugfest - informative assertion markup - generate manual.csv

[mlagally]

This PR prepares the specification draft and provides the list of normative assertions that are to be tested and verified in the Testfest/Plugfest.

Changes:

1. Modify the normative RFC2119 markup in informative sections in the document to be informative.
2. Generate assertions.csv and manual.csv
3. Minor script modifications

---

Preview | Diff

[egekorkan]

I guess it is fine but profile testing should not be a copy paste of the TD testing in my opinion. Testing some TDs does not show any OOTBI

[sebastiankb]

In general, this looks good, but we should also consider an interop test by two independent implementations since this is an important aspect of the profile. Maybe this should be considered in the manual assertions?

[benfrancis]

Modify the normative RFC2119 markup in informative sections in the document to be informative.

I personally think it's too early to decide which parts of the specification to make informative as a strategy for allowing the specification to proceed to CR. I don't think there's yet sufficient evidence that the HTTP Basic Profile is any better supported than the HTTP SSE Profile for example.

But as long as all of the assertions are included in test reports then I suppose we can revert these changes later if necessary.

[mlagally]

Arch call on Oct. 19th.
Close without merging, this is superseeded by #296