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.

Sign up for GitHub

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

Jump to bottom

Review for redundant normative statements [TAG feedback] #816

Closed
rhiaro opened this issue Jul 25, 2022 · 2 comments
Closed

Review for redundant normative statements [TAG feedback] #816

rhiaro opened this issue Jul 25, 2022 · 2 comments
Assignees
@mmccool
Labels
by CR transition tag-needs-resolution Issue the Technical Architecture Group has raised and looks for a response on.

Comments

@rhiaro
Copy link
Member

rhiaro commented Jul 25, 2022

Some normative statements are redundant - eg. in 12.1.1 Thing Description Private Security Data Risk, "MUST ensure that only Public Security Metadata is ever stored" and "MUST ensure that no Private Security Data is included" seem to be saying the same thing from different directions.

Suggest reviewing all normative statements for this, and rephrasing where possible.

(From w3ctag/design-reviews#736)
@rhiaro rhiaro mentioned this issue Jul 25, 2022
Closed
@mlagally mlagally added tag-needs-resolution Issue the Technical Architecture Group has raised and looks for a response on. address TAG feedback and removed address TAG feedback tag-needs-resolution Issue the Technical Architecture Group has raised and looks for a response on. labels Aug 4, 2022
@w3cbot w3cbot mentioned this issue Aug 4, 2022
Open
@mlagally
Copy link
Contributor

mlagally commented Sep 1, 2022 •
edited
Loading

Discussion in Arch call on 1. Sept:
We will review all assertions and identify those that are redundant as part of the implementation report work.
These assertions will be converted to regular text.
The one that is linked in the feedback above has been already fixed.

@mlagally
Copy link
Contributor

Arch call on Oct. 13:
Review has been done.
2 follow up issues were created:
#852, #851

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mmccool mmccool

Labels
by CR transition tag-needs-resolution Issue the Technical Architecture Group has raised and looks for a response on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rhiaro @mmccool @mlagally