-
Notifications
You must be signed in to change notification settings - Fork 8
Issues: w3c/wot-profile
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Clarifications on async actions
needs discussion
P1
Priority 1 to be discussed (e.g., next week)
Profile-2.0
#369
opened Mar 1, 2023 by
mlagally
Security - open issues
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.0
Profile-1.1
security
#359
opened Feb 1, 2023 by
mlagally
Wide review
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.0
#358
opened Feb 1, 2023 by
mlagally
Additional implementers feedback of profile assertions
help wanted
Extra attention is needed
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.0
#306
opened Oct 19, 2022 by
mlagally
Contradiction with the Arch spec on protocol bindings
by CR transition
close
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.0
#299
opened Oct 4, 2022 by
egekorkan
Discuss where Geolocation section should belong
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.1
#270
opened Aug 31, 2022 by
mlagally
Remove reference to security best practices document
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.0
security
#269
opened Aug 31, 2022 by
mlagally
New section on Webhook message format
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.0
#258
opened Aug 4, 2022 by
mlagally
Webhook unsubscribe operation in diagram doesn't match protocol binding
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.0
#254
opened Aug 3, 2022 by
benfrancis
subscribeallevents security requirements
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.1
security
#224
opened Jun 17, 2022 by
egekorkan
Security Requirements for WebHook Consumer
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.1
security
#222
opened Jun 17, 2022 by
egekorkan
Security Schemes are too loose
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.0
security
#221
opened Jun 17, 2022 by
egekorkan
List of required Security Schemes
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.1
security
#220
opened Jun 17, 2022 by
egekorkan
Image update for HTTP baseline profile
P1
Priority 1 to be discussed (e.g., next week)
Profile-1.0
#211
opened Jun 15, 2022 by
mlagally
Developer guidance
P1
Priority 1 to be discussed (e.g., next week)
requirement
#173
opened Feb 9, 2022 by
mlagally
Finite set of features and capabilities to implement by the consumer
P1
Priority 1 to be discussed (e.g., next week)
requirement
#172
opened Feb 9, 2022 by
mlagally
Validatible TDs
P1
Priority 1 to be discussed (e.g., next week)
requirement
#170
opened Feb 9, 2022 by
mlagally
Multiple profiles (mechanism)
P1
Priority 1 to be discussed (e.g., next week)
requirement
#169
opened Feb 9, 2022 by
mlagally
Ambiguities, select single choice
P1
Priority 1 to be discussed (e.g., next week)
requirement
#168
opened Feb 9, 2022 by
mlagally
Limit and reduce complexity
P1
Priority 1 to be discussed (e.g., next week)
requirement
#167
opened Feb 9, 2022 by
mlagally
Interoperability
P1
Priority 1 to be discussed (e.g., next week)
requirement
#166
opened Feb 9, 2022 by
mlagally
Profile should define a finite set of features and capabilities to implement by the consumer
needs clarification
P1
Priority 1 to be discussed (e.g., next week)
requirement
#163
opened Feb 2, 2022 by
mlagally
What should happen if Priority 1 to be discussed (e.g., next week)
Profile-1.1
writemultipleproperties
partially fails?
P1
#162
opened Jan 31, 2022 by
benfrancis
Profile requirements
P1
Priority 1 to be discussed (e.g., next week)
requirement
requirements
#156
opened Dec 14, 2021 by
mlagally
ProTip!
Find all open issues with in progress development work with linked:pr.