Web Thing Protocol Community Group - Activity in 2025
No matches.
GitHub
w3c/web-thing-protocol
-
1 issue opened.
-
Bug: `actionID` in the wrong place in example 42 w3c/web-thing-protocol#117, by @benfrancis.
-
-
1 issue received 6 new comments.
-
Strawman Proposal: HTTP Sub-protocol w3c/web-thing-protocol#116 (6 comments by @benfrancis, @egekorkan, @hspaay)
-
GitHub
w3c/web-thing-protocol
-
2 issues opened.
-
Strawman Proposal: HTTP Sub-protocol w3c/web-thing-protocol#116, by @benfrancis.
-
Use Case: Voice Assistant w3c/web-thing-protocol#114, by @benfrancis.
-
-
4 issues closed.
-
Accessibility Considerations w3c/web-thing-protocol#111.
-
Specify how to resume a dropped connection w3c/web-thing-protocol#69.
-
Write Security Considerations section w3c/web-thing-protocol#70.
-
Write Privacy Considerations section w3c/web-thing-protocol#71.
-
-
1 pull request opened.
-
Strawman proposal for a combined HTTP & WebSocket sub-protocol specification w3c/web-thing-protocol#115, by @benfrancis.
-
-
5 pull requests merged.
-
Strawman proposal for a combined HTTP & WebSocket sub-protocol specification w3c/web-thing-protocol#115.
-
Accessibility Considerations - closes #111 w3c/web-thing-protocol#112.
-
`lastNotificationID` feature - closes #69 w3c/web-thing-protocol#109.
-
Security Considerations - closes #70 w3c/web-thing-protocol#102.
-
Privacy Considerations - closes #71 w3c/web-thing-protocol#101.
-
-
5 pull requests received 5 new comments.
-
Strawman proposal for a combined HTTP & WebSocket sub-protocol specification w3c/web-thing-protocol#115 (1 comment by @benfrancis)
-
GitHub
w3c/web-thing-protocol
-
10 issues opened.
-
Accessibility Considerations w3c/web-thing-protocol#111, by @benfrancis.
-
Requirement: Rate Limiting w3c/web-thing-protocol#110, by @benfrancis.
-
Bug: Change in action state given as example of notification message w3c/web-thing-protocol#107, by @benfrancis.
-
Explain common deployment models w3c/web-thing-protocol#103, by @benfrancis.
-
Split operations into sections for readability w3c/web-thing-protocol#100, by @benfrancis.
-
Question: Should invokeaction always respond with an ActionStatus object w3c/web-thing-protocol#99, by @benfrancis.
-
Question: Are synchronous actions queryable and cancellable? w3c/web-thing-protocol#98, by @benfrancis.
-
Question: Should it be possible to cancel an action by name only? w3c/web-thing-protocol#97, by @benfrancis.
-
Question: Should it be possible to query an action by name only? w3c/web-thing-protocol#96, by @benfrancis.
-
Bug: Error codes should be a number w3c/web-thing-protocol#90, by @hspaay.
-
-
17 issues closed.
-
Explain common deployment models w3c/web-thing-protocol#103.
-
Split operations into sections for readability w3c/web-thing-protocol#100.
-
Bug: Change in action state given as example of notification message w3c/web-thing-protocol#107.
-
Feedback: Action name is missing in the action status message w3c/web-thing-protocol#33.
-
Requirement: Add Optional Acknowledgement for Event Subscription/Unsubscription success w3c/web-thing-protocol#29.
-
Requirement: Document what happens if a Consumer tries to unsubscribe but no subscription exists w3c/web-thing-protocol#28.
-
Question: What should be the response to a `readAllProperties` message? w3c/web-thing-protocol#27.
-
Question: How should a Consumer specify which action to query? w3c/web-thing-protocol#43.
-
Specify `queryallactions` operation w3c/web-thing-protocol#62.
-
Specify `cancelaction` operation w3c/web-thing-protocol#61.
-
Specify `queryaction` operation w3c/web-thing-protocol#60.
-
Specify `unsubscribeallevents` operation w3c/web-thing-protocol#66.
-
Specify `unsubscribeevent` operation w3c/web-thing-protocol#64.
-
Specify `subscribeallevents` operation w3c/web-thing-protocol#65.
-
Specify `subscribeevent` operation w3c/web-thing-protocol#63.
-
Bug: Error codes should be a number w3c/web-thing-protocol#90.
-
Specify `invokeaction` operation w3c/web-thing-protocol#59.
-
-
10 issues received 18 new comments.
-
Question: Are synchronous actions queryable and cancellable? w3c/web-thing-protocol#98 (5 comments by @benfrancis, @hspaay)
-
Question: How should a Consumer specify which action to query? w3c/web-thing-protocol#43 (3 comments by @benfrancis, @hspaay)
-
Feedback: Action name is missing in the action status message w3c/web-thing-protocol#33 (1 comment by @benfrancis)
-
Requirement: Add Optional Acknowledgement for Event Subscription/Unsubscription success w3c/web-thing-protocol#29 (1 comment by @benfrancis)
-
Requirement: Document what happens if a Consumer tries to unsubscribe but no subscription exists w3c/web-thing-protocol#28 (1 comment by @benfrancis)
-
Question: What should be the response to a `readAllProperties` message? w3c/web-thing-protocol#27 (1 comment by @benfrancis)
-
Question: Should invokeaction always respond with an ActionStatus object w3c/web-thing-protocol#99 (1 comment by @benfrancis)
-
Question: Should it be possible to query an action by name only? w3c/web-thing-protocol#96 (1 comment by @benfrancis)
-
-
14 pull requests opened.
-
Remove note about empty sections and text about other messages w3c/web-thing-protocol#113, by @benfrancis.
-
Accessibility Considerations - closes #111 w3c/web-thing-protocol#112, by @benfrancis.
-
`lastNotificationID` feature - closes #69 w3c/web-thing-protocol#109, by @benfrancis.
-
Remove change in action state as example of notification - closes #107 w3c/web-thing-protocol#108, by @benfrancis.
-
Split WebSocket Messages section into subsections for readability - closes #100 w3c/web-thing-protocol#106, by @benfrancis.
-
Add an example Thing Description w3c/web-thing-protocol#105, by @benfrancis.
-
Deployment Models - closes #103 w3c/web-thing-protocol#104, by @benfrancis.
-
Security Considerations - closes #70 w3c/web-thing-protocol#102, by @benfrancis.
-
Privacy Considerations - closes #71 w3c/web-thing-protocol#101, by @benfrancis.
-
Event Operations w3c/web-thing-protocol#95, by @benfrancis.
-
`queryallactions` operation - closes #62 w3c/web-thing-protocol#94, by @benfrancis.
-
`cancelaction` operation - closes #61 w3c/web-thing-protocol#93, by @benfrancis.
-
error codes should be numbers - this closes #90 w3c/web-thing-protocol#92, by @hspaay.
-
`queryaction` operation - closes #60 w3c/web-thing-protocol#91, by @benfrancis.
-
-
11 pull requests merged.
-
Remove note about empty sections and text about other messages w3c/web-thing-protocol#113.
-
Deployment Models - closes #103 w3c/web-thing-protocol#104.
-
Add an example Thing Description w3c/web-thing-protocol#105.
-
Split WebSocket Messages section into subsections for readability - closes #100 w3c/web-thing-protocol#106.
-
Remove change in action state as example of notification - closes #107 w3c/web-thing-protocol#108.
-
`queryallactions` operation - closes #62 w3c/web-thing-protocol#94.
-
`cancelaction` operation - closes #61 w3c/web-thing-protocol#93.
-
`queryaction` operation - closes #60 w3c/web-thing-protocol#91.
-
Event Operations w3c/web-thing-protocol#95.
-
`invokeaction` operation - closes #59 w3c/web-thing-protocol#89.
-
error codes should be numbers - this closes #90 w3c/web-thing-protocol#92.
-
-
12 pull requests received 33 new comments.
-
`queryallactions` operation - closes #62 w3c/web-thing-protocol#94 (6 comments by @benfrancis, @egekorkan, @hspaay)
-
Security Considerations - closes #70 w3c/web-thing-protocol#102 (2 comments by @benfrancis, @hspaay)
-
Remove note about empty sections and text about other messages w3c/web-thing-protocol#113 (1 comment by @benfrancis)
-
Split WebSocket Messages section into subsections for readability - closes #100 w3c/web-thing-protocol#106 (1 comment by @benfrancis)
-
Remove change in action state as example of notification - closes #107 w3c/web-thing-protocol#108 (1 comment by @benfrancis)
-
error codes should be numbers - this closes #90 w3c/web-thing-protocol#92 (1 comment by @benfrancis)
GitHub
w3c/web-thing-protocol
-
7 issues closed.
-
Question: How should `correlationID` be handled when event subscriptions/property observations overlap? w3c/web-thing-protocol#41.
-
Specify `unobserveallproperties` operation w3c/web-thing-protocol#58.
-
Specify `observeallproperties` w3c/web-thing-protocol#57.
-
Specify `unobserveproperty` operation w3c/web-thing-protocol#56.
-
Specify `writemultipleproperties` operation w3c/web-thing-protocol#52.
-
Specify `writeallproperties` operation w3c/web-thing-protocol#54.
-
Specify `observeproperty` operation w3c/web-thing-protocol#55.
-
-
3 issues received 39 new comments.
-
Question: How should a Consumer specify which action to query? w3c/web-thing-protocol#43 (27 comments by @benfrancis, @egekorkan, @hspaay, @relu91)
-
Question: How should `correlationID` be handled when event subscriptions/property observations overlap? w3c/web-thing-protocol#41 (7 comments by @benfrancis, @egekorkan, @hspaay, @jaller94)
-
Specify `invokeaction` operation w3c/web-thing-protocol#59 (5 comments by @benfrancis, @danielpeintner, @egekorkan, @hspaay)
-
-
4 pull requests opened.
-
`invokeaction` operation - closes #59 w3c/web-thing-protocol#89, by @benfrancis.
-
`unobserveallproperties` operation - closes #58 w3c/web-thing-protocol#88, by @benfrancis.
-
`observeallproperties` operation - closes #57 w3c/web-thing-protocol#87, by @benfrancis.
-
`unobserveproperty` operation - closes #56 w3c/web-thing-protocol#86, by @benfrancis.
-
-
6 pull requests merged.
-
`unobserveallproperties` operation - closes #58 w3c/web-thing-protocol#88.
-
`observeallproperties` operation - closes #57 w3c/web-thing-protocol#87.
-
`unobserveproperty` operation - closes #56 w3c/web-thing-protocol#86.
-
`writemultipleproperties` operation - closes #52 w3c/web-thing-protocol#84.
-
`writeallproperties` operation - closes #54 w3c/web-thing-protocol#83.
-
`observeproperty` operation - closes #55 w3c/web-thing-protocol#85.
-
-
7 pull requests received 37 new comments.
-
`unobserveproperty` operation - closes #56 w3c/web-thing-protocol#86 (9 comments by @benfrancis, @egekorkan, @hspaay)
-
`invokeaction` operation - closes #59 w3c/web-thing-protocol#89 (6 comments by @benfrancis, @egekorkan, @hspaay)
-
`writemultipleproperties` operation - closes #52 w3c/web-thing-protocol#84 (6 comments by @benfrancis, @egekorkan, @hspaay)
-
`unobserveallproperties` operation - closes #58 w3c/web-thing-protocol#88 (5 comments by @benfrancis, @egekorkan, @hspaay)
-
`observeallproperties` operation - closes #57 w3c/web-thing-protocol#87 (5 comments by @benfrancis, @egekorkan, @hspaay)
-
`observeproperty` operation - closes #55 w3c/web-thing-protocol#85 (4 comments by @benfrancis, @hspaay)
-
Participants
-
1 participant joined.
-
Boobalakrishnan Sadasivam joined.
-
GitHub
w3c/web-thing-protocol
-
2 issues closed.
-
Define error conditions for `readallproperties` operation w3c/web-thing-protocol#80.
-
Define error conditions for `readmultipleproperties` operation w3c/web-thing-protocol#79.
-
-
4 issues received 7 new comments.
-
Question: How should `correlationID` be handled when event subscriptions/property observations overlap? w3c/web-thing-protocol#41 (3 comments by @benfrancis, @hspaay, @jaller94)
-
Specify `observeproperty` operation w3c/web-thing-protocol#55 (2 comments by @benfrancis, @jaller94)
-
-
4 pull requests opened.
-
`observeproperty` operation - closes #55 w3c/web-thing-protocol#85, by @benfrancis.
-
`writemultipleproperties` operation - closes #52 w3c/web-thing-protocol#84, by @benfrancis.
-
`writeallproperties` operation - closes #54 w3c/web-thing-protocol#83, by @benfrancis.
-
Update index.html: Fix invalid error type w3c/web-thing-protocol#82, by @jaller94.
-
-
2 pull requests merged.
-
Define error conditions for `readallproperties` and `readmultipleproperties` - closes #79 and #80 w3c/web-thing-protocol#81.
-
Update index.html: Fix invalid error type w3c/web-thing-protocol#82.
-
-
2 pull requests received 11 new comments.
-
`writeallproperties` operation - closes #54 w3c/web-thing-protocol#83 (10 comments by @benfrancis, @egekorkan, @hspaay)
-
Define error conditions for `readallproperties` and `readmultipleproperties` - closes #79 and #80 w3c/web-thing-protocol#81 (1 comment by @benfrancis)
-
Participants
-
1 participant joined.
-
Alan Law (TheChineseWriter Limited) joined.
-
-
1 organization joined.
-
TheChineseWriter Limited joined.
-
GitHub
w3c/web-thing-protocol
-
2 issues opened.
-
Define error conditions for `readallproperties` operation w3c/web-thing-protocol#80, by @benfrancis.
-
Define error conditions for `readmultipleproperties` operation w3c/web-thing-protocol#79, by @benfrancis.
-
-
4 issues closed.
-
Specify `readmultipleproperites` operation w3c/web-thing-protocol#53.
-
Specify error message format w3c/web-thing-protocol#67.
-
Specify `readallproperties` operation w3c/web-thing-protocol#51.
-
Require `correlationID` in Responses if Present in Request w3c/web-thing-protocol#73.
-
-
2 issues received 6 new comments.
-
Define error conditions for `readallproperties` operation w3c/web-thing-protocol#80 (5 comments by @benfrancis, @danielpeintner, @egekorkan)
-
Question: How should `correlationID` be handled when event subscriptions/property observations overlap? w3c/web-thing-protocol#41 (1 comment by @hspaay)
-
-
1 pull request opened.
-
Define error conditions for `readallproperties` and `readmultipleproperties` - closes #79 and #80 w3c/web-thing-protocol#81, by @benfrancis.
-
-
4 pull requests merged.
-
`readmultipleproperties` operation - closes #53 w3c/web-thing-protocol#78.
-
Define error response message format - closes #67 w3c/web-thing-protocol#76.
-
`readallproperties` operation - closes #51 w3c/web-thing-protocol#77.
-
Make correlationID mandatory in response if present in request - closes #73 w3c/web-thing-protocol#75.
-
-
5 pull requests received 13 new comments.
-
Define error response message format - closes #67 w3c/web-thing-protocol#76 (5 comments by @benfrancis, @danielpeintner, @egekorkan)
-
Define error conditions for `readallproperties` and `readmultipleproperties` - closes #79 and #80 w3c/web-thing-protocol#81 (3 comments by @benfrancis, @danielpeintner, @hspaay)
-
`readallproperties` operation - closes #51 w3c/web-thing-protocol#77 (3 comments by @benfrancis, @danielpeintner)
-
`readmultipleproperties` operation - closes #53 w3c/web-thing-protocol#78 (1 comment by @benfrancis)
-
Make correlationID mandatory in response if present in request - closes #73 w3c/web-thing-protocol#75 (1 comment by @benfrancis)
-
GitHub
w3c/web-thing-protocol
-
28 issues opened.
-
Require `correlationID` in Responses if Present in Request w3c/web-thing-protocol#73, by @relu91.
-
Write Introduction section w3c/web-thing-protocol#72, by @benfrancis.
-
Write Privacy Considerations section w3c/web-thing-protocol#71, by @benfrancis.
-
Write Security Considerations section w3c/web-thing-protocol#70, by @benfrancis.
-
Specify how to resume a dropped connection w3c/web-thing-protocol#69, by @benfrancis.
-
Specify a way for a Web Thing to act as a WebSocket client w3c/web-thing-protocol#68, by @benfrancis.
-
Specify error message format w3c/web-thing-protocol#67, by @benfrancis.
-
Specify `unsubscribeallevents` operation w3c/web-thing-protocol#66, by @benfrancis.
-
Specify `subscribeallevents` operation w3c/web-thing-protocol#65, by @benfrancis.
-
Specify `unsubscribeevent` operation w3c/web-thing-protocol#64, by @benfrancis.
-
Specify `subscribeevent` operation w3c/web-thing-protocol#63, by @benfrancis.
-
Specify `queryallactions` operation w3c/web-thing-protocol#62, by @benfrancis.
-
Specify `cancelaction` operation w3c/web-thing-protocol#61, by @benfrancis.
-
Specify `queryaction` operation w3c/web-thing-protocol#60, by @benfrancis.
-
Specify `invokeaction` operation w3c/web-thing-protocol#59, by @benfrancis.
-
Specify `unobserveallproperties` operation w3c/web-thing-protocol#58, by @benfrancis.
-
Specify `observeallproperties` w3c/web-thing-protocol#57, by @benfrancis.
-
Specify `unobserveproperty` operation w3c/web-thing-protocol#56, by @benfrancis.
-
Specify `observeproperty` operation w3c/web-thing-protocol#55, by @benfrancis.
-
Specify `writeallproperties` operation w3c/web-thing-protocol#54, by @benfrancis.
-
Specify `readmultipleproperites` operation w3c/web-thing-protocol#53, by @benfrancis.
-
Specify `writemultipleproperties` operation w3c/web-thing-protocol#52, by @benfrancis.
-
Specify `readallproperties` operation w3c/web-thing-protocol#51, by @benfrancis.
-
Specify `writeproperty` operation w3c/web-thing-protocol#50, by @benfrancis.
-
Specify `readproperty` operation w3c/web-thing-protocol#49, by @benfrancis.
-
Specify common members of WebSocket messages w3c/web-thing-protocol#48, by @benfrancis.
-
Specify WebSocket Re-use w3c/web-thing-protocol#47, by @benfrancis.
-
Specify Protocol Handshake w3c/web-thing-protocol#46, by @benfrancis.
-
-
7 issues closed.
-
Specify `writeproperty` operation w3c/web-thing-protocol#50.
-
Proposal: Split `operation` and `messageType` into separate members of a message w3c/web-thing-protocol#42.
-
Write Introduction section w3c/web-thing-protocol#72.
-
Specify `readproperty` operation w3c/web-thing-protocol#49.
-
Specify common members of WebSocket messages w3c/web-thing-protocol#48.
-
Specify WebSocket Re-use w3c/web-thing-protocol#47.
-
Specify Protocol Handshake w3c/web-thing-protocol#46.
-
-
20 issues received 43 new comments.
-
Specify a way for a Web Thing to act as a WebSocket client w3c/web-thing-protocol#68 (7 comments by @benfrancis, @egekorkan, @hspaay)
-
Specify `readmultipleproperites` operation w3c/web-thing-protocol#53 (6 comments by @benfrancis, @egekorkan, @relu91)
-
Specify error message format w3c/web-thing-protocol#67 (6 comments by @benfrancis, @danielpeintner, @egekorkan, @relu91)
-
Specify `writemultipleproperties` operation w3c/web-thing-protocol#52 (2 comments by @benfrancis, @egekorkan)
-
-
6 pull requests opened.
-
`readmultipleproperties` operation - closes #53 w3c/web-thing-protocol#78, by @benfrancis.
-
`readallproperties` operation - closes #51 w3c/web-thing-protocol#77, by @benfrancis.
-
Define error response message format - closes #67 w3c/web-thing-protocol#76, by @benfrancis.
-
Make correlationID mandatory in response if present in request - closes #73 w3c/web-thing-protocol#75, by @benfrancis.
-
writeproperty message - closes #50 w3c/web-thing-protocol#74, by @benfrancis.
-
Split message type and operation - closes #42 w3c/web-thing-protocol#45, by @benfrancis.
-
-
2 pull requests merged.
-
writeproperty message - closes #50 w3c/web-thing-protocol#74.
-
Split message type and operation - closes #42 w3c/web-thing-protocol#45.
-
-
1 pull request closed.
-
writeProperty message w3c/web-thing-protocol#38.
-
-
4 pull requests received 16 new comments.
-
writeproperty message - closes #50 w3c/web-thing-protocol#74 (9 comments by @benfrancis, @egekorkan, @hspaay)
-
`readallproperties` operation - closes #51 w3c/web-thing-protocol#77 (3 comments by @benfrancis, @hspaay)
-
Split message type and operation - closes #42 w3c/web-thing-protocol#45 (3 comments by @benfrancis, @relu91)
-
Participants
-
1 participant joined.
-
David Ezell (Conexxus) joined.
-
-
1 organization joined.
-
Conexxus joined.
-
Past meetings
GitHub
w3c/web-thing-protocol
-
4 issues received 16 new comments.
-
Question: How should a Consumer specify which action to query? w3c/web-thing-protocol#43 (6 comments by @benfrancis, @hspaay)
-
Proposal: Split `operation` and `messageType` into separate members of a message w3c/web-thing-protocol#42 (6 comments by @benfrancis, @hspaay)
-
Question: How should `correlationID` be handled when event subscriptions/property observations overlap? w3c/web-thing-protocol#41 (2 comments by @benfrancis, @hspaay)
-
Question: Is there a need for `ping` and `pong` messages? w3c/web-thing-protocol#44 (2 comments by @hspaay, @relu91)
-
-
1 pull request received 4 new comments.
Participants
-
1 participant joined.
-
Victor Lu joined.
-
GitHub
w3c/web-thing-protocol
-
4 issues opened.
-
Question: Is there a need for `ping` and `pong` messages? w3c/web-thing-protocol#44, by @benfrancis.
-
Question: How should a Consumer specify which action to query? w3c/web-thing-protocol#43, by @benfrancis.
-
Proposal: Split `operation` and `messageType` into separate members of a message w3c/web-thing-protocol#42, by @benfrancis.
-
Question: How should `correlationID` be handled when event subscriptions/property observations overlap? w3c/web-thing-protocol#41, by @benfrancis.
-
-
2 issues closed.
-
Question: Do responses need to be correlated with requests? w3c/web-thing-protocol#31.
-
Question: Does every message need a `messageID`? w3c/web-thing-protocol#35.
-
-
3 issues received 6 new comments.
-
Requirement: Proposal (2) for standardized message envelope for requests, responses and notifications w3c/web-thing-protocol#34 (4 comments by @benfrancis, @hspaay)
-
Question: Do responses need to be correlated with requests? w3c/web-thing-protocol#31 (1 comment by @benfrancis)
-
Question: Does every message need a `messageID`? w3c/web-thing-protocol#35 (1 comment by @benfrancis)
-
-
1 pull request opened.
-
writeProperty message w3c/web-thing-protocol#38, by @benfrancis.
-
-
2 pull requests received 6 new comments.
Participants
-
1 participant joined.
-
daniel o joined.
-
GitHub
w3c/web-thing-protocol
-
2 issues opened.
-
proposal draft/discussion: web-thing-protocol (WoTP): json-rpc system extension w3c/web-thing-protocol#36, by @unit9a.
-
Question: Does every message need a `messageID`? w3c/web-thing-protocol#35, by @benfrancis.
-
-
9 issues received 92 new comments.
-
Requirement: Proposal (2) for standardized message envelope for requests, responses and notifications w3c/web-thing-protocol#34 (52 comments by @benfrancis, @hspaay, @RobWin, @unit9a, @VigneshVSV)
-
Question: Does every message need a `messageID`? w3c/web-thing-protocol#35 (21 comments by @benfrancis, @hspaay, @RobWin)
-
Question: Do responses need to be correlated with requests? w3c/web-thing-protocol#31 (6 comments by @benfrancis, @hspaay, @RobWin)
-
Requirement: Support for additonal metadata such as OpenTelemetry/TracingContext in WebSocket Messages w3c/web-thing-protocol#30 (4 comments by @benfrancis, @RobWin)
-
Feedback: Action name is missing in the action status message w3c/web-thing-protocol#33 (3 comments by @benfrancis, @hspaay, @RobWin)
-
Requirement: Add Optional Acknowledgement for Event Subscription/Unsubscription success w3c/web-thing-protocol#29 (3 comments by @benfrancis, @RobWin)
-
proposal draft/discussion: web-thing-protocol (WoTP): json-rpc system extension w3c/web-thing-protocol#36 (1 comment by @RobWin)
-
Feedback: Standardize the message field names (proposal 1) w3c/web-thing-protocol#32 (1 comment by @benfrancis)
-
Requirement: Document what happens if a Consumer tries to unsubscribe but no subscription exists w3c/web-thing-protocol#28 (1 comment by @benfrancis)
-
-
1 pull request opened.
-
readProperty and propertyReading messages w3c/web-thing-protocol#37, by @benfrancis.
-
-
2 pull requests merged.
-
readProperty and propertyReading messages w3c/web-thing-protocol#37.
-
Define WebSocket Re-use w3c/web-thing-protocol#26.
-
-
2 pull requests received 32 new comments.
-
readProperty and propertyReading messages w3c/web-thing-protocol#37 (31 comments by @benfrancis, @egekorkan, @hspaay, @RobWin)
-