Option 1: Switch Profile to non-normative section #862
Conversation
| @@ -2922,10 +2922,10 @@ <h2>Thing Model</h2> | |||
|
|
|||
| </section> | |||
|
|
|||
| <section id="wot-profiles"> | |||
| <section id="wot-profiles" class="informative"> | |||
There was a problem hiding this comment.
It is not required to add an informative reference to the profile spec, and also there's no need to make the entire section informative, since there's no normative requirement for it.
The situation is very different from the TD + binding spec case, where a normative RFC2119 assertion was enforcing to use the binding templates.
This section here does not put any normative requirements on implementers and the profile reference can remain normative.
There was a problem hiding this comment.
You are right, there is no reason to change a section to informative just to refer to non-normative references in the text. However, I think we should be aligned with the Chapter 7 structure: E.g., Binding Templates and Scripting API sections are also informative. Since Profile has published a first working draft so far, I think it makes sense for this section to be informative as well.
|
Since there are NO assertions anywhere in section 7, how about we just make the entire section informative? That way we are not calling out Profiles in particular, and we don't have to update the references - if they are in an informative section they will be informative. |
sebastiankb
changed the title
|
An alternative to this PR is to think about to make the whole chapter 7 non-normative. |
|
Arch call on Nov 2nd.: Agree to close without merging |
solves #861
Preview | Diff