Skip to content
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

Add Higher Level Goals to Scope section #52

Merged
merged 1 commit into from
Feb 21, 2023

Conversation

mmccool
Copy link
Contributor

@mmccool mmccool commented Feb 20, 2023

  • remove second half of background paragraph which was really about scope
  • add short (4-point) list of higher-level goals to start of scope section
  • add link to details document after work items (link will only work once Details cleanup #51 is merged)

Preview | Diff

<p>The Working Group has the following work items in scope:</p>
<p>During this charter, the Working Group would:</p>
<ul>
<li>Update the Architecture, Thing Description, Profile, and Discovery specifications
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

binding templates is missing here but it is not an update.

Also, I still think (as also pointed out in TAG review of Arch spec) that Arch spec should become informative.

@benfrancis
Copy link
Member

  • add link to details document after work items

Does this imply that the Working Group agrees with all of the content of this document? I don't think it has been thoroughly reviewed.

Comment on lines +210 to +211
<li>Reorganize Security Schemes and Protocol/Payload Bindings to be more modular and less specific
to HTTP.</li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reads as though protocol/payload binding (templates) are currently specific to HTTP

<p>During this charter, the Working Group would:</p>
<ul>
<li>Update the Architecture, Thing Description, Profile, and Discovery specifications
to address major issues discovered during implementation of the 1.0 and 1.1 specifications.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and add features, not just address issues

Unlike the last charter, these would not be limited to backward-compatible updates.</li>
<li>Reorganize Security Schemes and Protocol/Payload Bindings to be more modular and less specific
to HTTP.</li>
<li>Update and improve security and privacy controls.</li>
Copy link
Member

@benfrancis benfrancis Feb 21, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which work items correspond to this summary item? It's not clear to me.

@mmccool mmccool merged commit 1c3ac1c into w3c:main Feb 21, 2023
This was referenced Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants