Web Thing Protocol Community Group - Activity in 2024
No matches.
Participants
-
2 participants joined.
-
Robert Winkler (Deutsche Telekom AG) joined.
-
Vignesh Venkatasubramanian Vaidyanathan joined.
-
-
1 organization joined.
-
Deutsche Telekom AG joined.
-
GitHub
w3c/web-thing-protocol
-
8 issues opened.
-
Requirement: Proposal (2) for standardized message envelope for requests, responses and notifications w3c/web-thing-protocol#34, by @hspaay.
-
Feedback: Action name is missing in the action status message w3c/web-thing-protocol#33, by @hspaay.
-
Feedback: Standardize the message field names (proposal 1) w3c/web-thing-protocol#32, by @hspaay.
-
Question: Do responses need to be correlated with requests? w3c/web-thing-protocol#31, by @benfrancis.
-
Requirement: Support for additonal metadata such as OpenTelemetry/TracingContext in WebSocket Messages w3c/web-thing-protocol#30, by @RobWin.
-
Requirement: Add Optional Acknowledgement for Event Subscription/Unsubscription success w3c/web-thing-protocol#29, by @RobWin.
-
Requirement: Document what happens if a Consumer tries to unsubscribe but no subscription exists w3c/web-thing-protocol#28, by @RobWin.
-
Question: What should be the response to a `readAllProperties` message? w3c/web-thing-protocol#27, by @benfrancis.
-
-
1 issue closed.
-
Strawman Proposal: Web Thing Protocol - WebSocket Sub-protocol w3c/web-thing-protocol#23.
-
-
5 issues received 10 new comments.
-
Question: Do responses need to be correlated with requests? w3c/web-thing-protocol#31 (4 comments by @benfrancis, @hspaay, @RobWin, @VigneshVSV)
-
Question: What should be the response to a `readAllProperties` message? w3c/web-thing-protocol#27 (2 comments by @hspaay, @RobWin)
-
Strawman Proposal: Web Thing Protocol - WebSocket Sub-protocol w3c/web-thing-protocol#23 (2 comments by @benfrancis, @RobWin)
-
Requirement: Add Optional Acknowledgement for Event Subscription/Unsubscription success w3c/web-thing-protocol#29 (1 comment by @hspaay)
-
Use Case: Provide web pages with access to local hardware capabilities w3c/web-thing-protocol#18 (1 comment by @RobWin)
-
-
1 pull request opened.
-
Define WebSocket Re-use w3c/web-thing-protocol#26, by @benfrancis.
-
-
1 pull request merged.
-
Define Protocol Handshake w3c/web-thing-protocol#25.
-
-
1 pull request received 5 new comments.
-
Define Protocol Handshake w3c/web-thing-protocol#25 (5 comments by @benfrancis, @egekorkan, @RobWin)
-
Reports
-
1 report published.
-
Web Thing Protocol published as a draft report.
-
Participants
-
3 participants joined.
-
Gustavo Zapico (netavanza) joined.
-
Jan Romann joined.
-
Henk Spaaij joined.
-
-
1 participant left.
-
Gustavo Zapico (netavanza) left.
-
-
1 organization joined.
-
netavanza joined.
-
GitHub
w3c/web-thing-protocol
-
1 pull request opened.
-
Define Protocol Handshake w3c/web-thing-protocol#25, by @benfrancis.
-
Participants
-
1 participant joined.
-
Habtom Kahsay Gidey joined.
-
GitHub
w3c/web-thing-protocol
-
1 pull request merged.
-
Initial Abstract, Introduction and document structure w3c/web-thing-protocol#24.
-
Participants
-
2 participants joined.
-
Cristiano Aguzzi joined.
-
John Davis joined.
-
-
1 organization joined.
-
Luminem joined.
-
GitHub
w3c/web-thing-protocol
-
1 pull request opened.
-
Initial Abstract, Introduction and document structure w3c/web-thing-protocol#24, by @benfrancis.
-
-
1 pull request received 11 new comments.
-
Initial Abstract, Introduction and document structure w3c/web-thing-protocol#24 (11 comments by @benfrancis, @egekorkan, @relu91)
-