-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why are Chapter 8 and 9 separated #630
Comments
Chapter 8 introduces the concepts in the abstract WoT system architecture. |
I think that the minimum that needs to be done is renaming building blocks to specification documents. Other comments:
I think that the amount of duplication of actual text and concepts should be reduced to make it easier to maintain, which is obviously failing given the high amount of misalignments. |
Maybe the para in 10.3 can be added to the section 10.2 which talks about WoT runtime. Scripting for me is a runtime.... |
+1 for merging, 10.2 already correctly describes how a runtime relates to the Scripting API we don't need another paragraph |
When I am updating another WoT specification and want to sync the updates with the architecture specification, it is confusing that there are two places any specification can look for: Section 8 and 9 for most, 9 and 10 for Scripting API.
If we are to have information in the architecture specification that other specifications should sync with, it should be easier for other specifications to know where to update.
The text was updated successfully, but these errors were encountered: