Web of Things Working Group - Activity in 2025
No matches.
Past meetings
-
12 meetings.
Participants
-
1 participant joined.
-
Kazuyuki Ashimura (W3C Invited Experts) joined.
-
-
3 participants left.
-
Mahmood Afshari (W3C Invited Experts) left.
-
Elena Reshetova (Intel Corporation) left.
-
Michael Lagally (Oracle Corporation) left.
-
GitHub
w3c/wot-profile
-
3 issues opened.
-
Requirement: Clarify how the profiling mechanism will work w3c/wot-profile#488, by @benfrancis.
-
Requirement: Make it clear that WoT Profiles 2.0 is meant to work with Thing Description 2.0 w3c/wot-profile#487, by @benfrancis.
-
Comments about Profile 2.0 Use Case & Requirements w3c/wot-profile#486, by @sebastiankb.
-
-
1 issue received 2 new comments.
-
Comments about Profile 2.0 Use Case & Requirements w3c/wot-profile#486 (2 comments by @benfrancis, @TallTed)
-
-
3 pull requests opened.
-
Add Editor's Notes about open discussion around use cases & requirements w3c/wot-profile#491, by @benfrancis.
-
Clarify how the Profiling mechanism will work - closes #488 w3c/wot-profile#490, by @benfrancis.
-
Clarify that WoT Profiles 2.0 will work with Thing Description 2.0 - closes #487 w3c/wot-profile#489, by @benfrancis.
-
-
2 pull requests received 7 new comments.
-
Add Editor's Notes about open discussion around use cases & requirements w3c/wot-profile#491 (5 comments by @benfrancis, @TallTed)
-
Clarify how the Profiling mechanism will work - closes #488 w3c/wot-profile#490 (2 comments by @benfrancis, @TallTed)
-
w3c/wot-thing-description
-
2 issues opened.
-
Basic Operations on Data w3c/wot-thing-description#2169, by @egekorkan.
-
[POSSIBLE ERRATA] Wrong link and possibly text in the description field of the ontology w3c/wot-thing-description#2168, by @egekorkan.
-
-
3 issues closed.
-
should be clearer about where the definition of the HTTP Protocol Binding is w3c/wot-thing-description#791.
-
Experimenting with Specification Tooling w3c/wot-thing-description#1995.
-
Adding array for common definitions referencing w3c/wot-thing-description#2159.
-
-
8 issues received 12 new comments.
-
Review of Common Definitions Proposal w3c/wot-thing-description#2165 (5 comments by @benfrancis, @egekorkan)
-
should be clearer about where the definition of the HTTP Protocol Binding is w3c/wot-thing-description#791 (1 comment by @egekorkan)
-
Proposal: Manageable actions and data mapping using semantic annotations w3c/wot-thing-description#2166 (1 comment by @benfrancis)
-
meta operations when multiple content types exist w3c/wot-thing-description#1814 (1 comment by @benfrancis)
-
Reference to the URI Spec (RFC3986) should be replaced with IRI Spec (RFC3987) w3c/wot-thing-description#2156 (1 comment by @egekorkan)
-
-
2 pull requests opened.
-
Architecture Assertions from Ege w3c/wot-thing-description#2171, by @egekorkan.
-
Move privacy related assertions from Architecture spec (#2151 50,53) w3c/wot-thing-description#2170, by @k-toumura.
-
-
5 pull requests merged.
-
Architecture Assertions from Ege w3c/wot-thing-description#2171.
-
Move privacy related assertions from Architecture spec (#2151 50,53) w3c/wot-thing-description#2170.
-
Add security related assertions of Architecture (#2151 46, 47, 48, 49) w3c/wot-thing-description#2167.
-
Array instead of string for common definition references w3c/wot-thing-description#2163.
-
fix: syntax error in wotsec: \# w3c/wot-thing-description#2158.
-
-
5 pull requests received 13 new comments.
-
Architecture Assertions from Ege w3c/wot-thing-description#2171 (5 comments by @danielpeintner, @egekorkan, @k-toumura)
-
Add a proposal for manageable affordances and data mapping w3c/wot-thing-description#2162 (3 comments by @egekorkan, @k-toumura, @relu91)
-
Add security related assertions of Architecture (#2151 46, 47, 48, 49) w3c/wot-thing-description#2167 (3 comments by @egekorkan, @k-toumura)
-
Array instead of string for common definition references w3c/wot-thing-description#2163 (1 comment by @egekorkan)
-
w3c/wot-binding-registry
-
2 issues opened.
-
Requirements for Transitioning to Obsolete State w3c/wot-binding-registry#49, by @egekorkan.
-
Adding issue templates for all transitions w3c/wot-binding-registry#48, by @egekorkan.
-
-
1 issue closed.
-
confusing normative keyword w3c/wot-binding-registry#41.
-
-
2 issues received 2 new comments.
-
Requirements for Transitioning to Obsolete State w3c/wot-binding-registry#49 (1 comment by @egekorkan)
-
Add code of conduct for the registry submission w3c/wot-binding-registry#44 (1 comment by @egekorkan)
-
-
2 pull requests opened.
-
Issue Template for Binding Transitions w3c/wot-binding-registry#47, by @egekorkan.
-
Issue 41 Fix with Assertion w3c/wot-binding-registry#46, by @egekorkan.
-
-
2 pull requests merged.
-
Issue 41 Fix with Assertion w3c/wot-binding-registry#46.
-
Clarify JSON-LD Context impact in submission requirements w3c/wot-binding-registry#45.
-
-
3 pull requests received 4 new comments.
-
Clarify JSON-LD Context impact in submission requirements w3c/wot-binding-registry#45 (1 comment by @egekorkan)
w3c/wot-resources
-
1 pull request opened.
-
Fix `$schema` keyword with trailing space in v1 w3c/wot-resources#28, by @jviotti.
-
-
1 pull request merged.
-
Fix `$schema` keyword with trailing space in v1 w3c/wot-resources#28.
-
-
1 pull request received 1 new comment.
w3c/wot-scripting-api
-
1 issue opened.
-
TD common definition and affects on formIndex w3c/wot-scripting-api#582, by @danielpeintner.
-
-
1 issue received 6 new comments.
-
TD common definition and affects on formIndex w3c/wot-scripting-api#582 (6 comments by @danielpeintner, @egekorkan, @relu91)
-
-
1 pull request received 1 new comment.
w3c/wot-binding-templates
-
1 pull request merged.
-
docs(BACnet): remark why data link layers are left out w3c/wot-binding-templates#451.
-
-
1 pull request received 7 new comments.
-
docs(BACnet): remark why data link layers are left out w3c/wot-binding-templates#451 (7 comments by @benfrancis, @danielpeintner, @egekorkan, @fennibay)
-
TR publications
-
4 documents published.
-
Web of Things (WoT) Profiles published as a Working Draft. History of Web of Things (WoT) Profiles
-
Web of Things (WoT) Thing Description 2.0 published as a First Public Working Draft. History of Web of Things (WoT) Thing Description 2.0
-
Web of Things (WoT) Binding Templates published as a Note. History of Web of Things (WoT) Binding Templates
-
Web of Things (WoT) Binding Registry published as a Draft Registry. History of Web of Things (WoT) Binding Registry
-
Past meetings
-
11 meetings.
GitHub
w3c/wot-thing-description
-
3 issues opened.
-
Proposal: Manageable actions and data mapping using semantic annotations w3c/wot-thing-description#2166, by @benfrancis.
-
Review of Common Definitions Proposal w3c/wot-thing-description#2165, by @benfrancis.
-
Explain common definitions usage with TMs w3c/wot-thing-description#2164, by @egekorkan.
-
-
3 issues closed.
-
Fix overlaps between TD and Bindings content w3c/wot-thing-description#2006.
-
Review all uses of the terms "Binding", "Protocol Binding" and "Binding Template" w3c/wot-thing-description#2101.
-
Using the New Use Case Template and Gathering Experience w3c/wot-thing-description#2039.
-
-
7 issues received 17 new comments.
-
Review of Common Definitions Proposal w3c/wot-thing-description#2165 (6 comments by @benfrancis, @egekorkan)
-
Proposal: Manageable actions and data mapping using semantic annotations w3c/wot-thing-description#2166 (6 comments by @benfrancis, @danielpeintner, @relu91)
-
Review the set of action operations in Thing Description 2.0 w3c/wot-thing-description#2157 (1 comment by @egekorkan)
-
Fix overlaps between TD and Bindings content w3c/wot-thing-description#2006 (1 comment by @egekorkan)
-
Review all uses of the terms "Binding", "Protocol Binding" and "Binding Template" w3c/wot-thing-description#2101 (1 comment by @egekorkan)
-
-
2 pull requests opened.
-
Add security related assertions of Architecture (#2151 46, 47, 48, 49) w3c/wot-thing-description#2167, by @k-toumura.
-
Array instead of string for common definition references w3c/wot-thing-description#2163, by @egekorkan.
-
-
1 pull request merged.
-
fix prettier to version 3.0.0 w3c/wot-thing-description#2152.
-
-
3 pull requests received 35 new comments.
-
Add a proposal for manageable affordances and data mapping w3c/wot-thing-description#2162 (25 comments by @benfrancis, @danielpeintner, @egekorkan, @relu91)
-
Array instead of string for common definition references w3c/wot-thing-description#2163 (8 comments by @egekorkan, @TallTed)
-
Add security related assertions of Architecture (#2151 46, 47, 48, 49) w3c/wot-thing-description#2167 (2 comments by @egekorkan, @k-toumura)
-
w3c/wot-scripting-api
-
1 issue opened.
-
Behavior of affordances w3c/wot-scripting-api#581, by @danielpeintner.
-
-
1 issue closed.
-
Error: async iterable is now changed to async_iterable w3c/wot-scripting-api#579.
-
-
3 issues received 6 new comments.
-
Error: async iterable is now changed to async_iterable w3c/wot-scripting-api#579 (2 comments by @danielpeintner, @relu91)
-
Cover AdditionalExpectedResponses as error responses w3c/wot-scripting-api#560 (1 comment by @danielpeintner)
-
1 pull request merged.
-
Change return type of invokeAction from InteractionOutput to ActionInteractionOutput w3c/wot-scripting-api#580.
-
-
1 pull request received 1 new comment.
-
Change return type of invokeAction from InteractionOutput to ActionInteractionOutput w3c/wot-scripting-api#580 (1 comment by @danielpeintner)
-
w3c/wot-binding-registry
-
4 issues opened.
-
Add code of conduct for the registry submission w3c/wot-binding-registry#44, by @egekorkan.
-
How to organize reviews w3c/wot-binding-registry#43, by @egekorkan.
-
Adding design guidelines for resources w3c/wot-binding-registry#42, by @egekorkan.
-
confusing normative keyword w3c/wot-binding-registry#41, by @pchampin.
-
-
4 issues received 5 new comments.
-
Add code of conduct for the registry submission w3c/wot-binding-registry#44 (1 comment by @egekorkan)
-
1 pull request opened.
-
Clarify JSON-LD Context impact in submission requirements w3c/wot-binding-registry#45, by @egekorkan.
-
w3c/wot-binding-templates
-
2 issues opened.
-
WebSocket Binding w3c/wot-binding-templates#453, by @benfrancis.
-
What level of detail is acceptable for default HTTP bindings? w3c/wot-binding-templates#452, by @benfrancis.
-
-
4 issues received 9 new comments.
-
What level of detail is acceptable for default HTTP bindings? w3c/wot-binding-templates#452 (3 comments by @benfrancis, @egekorkan)
-
Should Longpolling, SSE and Websocket examples for async operations be part of the HTTP Binding? w3c/wot-binding-templates#438 (1 comment by @benfrancis)
-
1 pull request opened.
-
docs(BACnet): remark why data link layers are left out w3c/wot-binding-templates#451, by @fennibay.
-
-
1 pull request merged.
-
[WIP] Missing ReadFileRecord in Modbus binding w3c/wot-binding-templates#445.
-
-
2 pull requests received 4 new comments.
-
docs(BACnet): remark why data link layers are left out w3c/wot-binding-templates#451 (2 comments by @TallTed)
-
[WIP] Missing ReadFileRecord in Modbus binding w3c/wot-binding-templates#445 (2 comments by @egekorkan, @mahdanoura)
-
w3c/wot-profile
-
1 issue opened.
-
Use Case: Smart Home Voice Assistant w3c/wot-profile#485, by @benfrancis.
-
Lifecycle
-
1 charter extension.
-
Charter extended until 2 April 2026.
-
Past meetings
-
29 meetings.
Participants
-
1 Team contact appointed.
-
Dave Raggett became a Team contact.
-
-
1 Team contact stepped down.
-
Kazuyuki Ashimura stepped down as a Team contact.
-
-
2 participants joined.
-
Marc Riedlinger (Fraunhofer Gesellschaft) joined.
-
Roman Binkert (Siemens AG) joined.
-
-
5 participants left.
-
Zoltan Kis (Intel Corporation) left.
-
Elodie Thiéblin (Siemens AG) left.
-
Jiye Park (Siemens AG) left.
-
Fady Salama (Siemens AG) left.
-
Kazuyuki Ashimura (W3C Invited Experts) left.
-
-
1 organization joined.
-
Fraunhofer Gesellschaft joined.
-
GitHub
w3c/wot-thing-description
-
8 issues opened.
-
Redesigning Forms w3c/wot-thing-description#2161, by @egekorkan.
-
Affordance-level definition usage w3c/wot-thing-description#2160, by @egekorkan.
-
Adding array for common definitions referencing w3c/wot-thing-description#2159, by @egekorkan.
-
Review the set of action operations in Thing Description 2.0 w3c/wot-thing-description#2157, by @benfrancis.
-
Reference to the URI Spec (RFC3986) should be replaced with IRI Spec (RFC3987) w3c/wot-thing-description#2156, by @egekorkan.
-
Extending Common Definitions Proposal from CG Participants' Input w3c/wot-thing-description#2153, by @egekorkan.
-
Adding relevant Arch Assertions w3c/wot-thing-description#2151, by @egekorkan.
-
-
3 issues closed.
-
Categorizing Architecture Assertions w3c/wot-thing-description#2126.
-
Renaming Reusable Connections to Common Definitions w3c/wot-thing-description#2135.
-
4 issues received 8 new comments.
-
Reference to the URI Spec (RFC3986) should be replaced with IRI Spec (RFC3987) w3c/wot-thing-description#2156 (5 comments by @egekorkan, @ektrah, @mahdanoura)
-
Adding array for common definitions referencing w3c/wot-thing-description#2159 (1 comment by @egekorkan)
-
Extending Common Definitions Proposal from CG Participants' Input w3c/wot-thing-description#2153 (1 comment by @danielpeintner)
-
Renaming Reusable Connections to Common Definitions w3c/wot-thing-description#2135 (1 comment by @egekorkan)
-
-
5 pull requests opened.
-
Add a proposal for manageable affordances and data mapping w3c/wot-thing-description#2162, by @relu91.
-
fix: syntax error in wotsec: \# w3c/wot-thing-description#2158, by @fennibay.
-
Common Definitions Examples w3c/wot-thing-description#2154, by @egekorkan.
-
fix prettier to version 3.0.0 w3c/wot-thing-description#2152, by @egekorkan.
-
Arch assertions 10-18 w3c/wot-thing-description#2150, by @egekorkan.
-
-
8 pull requests merged.
-
Common Definitions Examples w3c/wot-thing-description#2154.
-
Arch assertions 10-18 w3c/wot-thing-description#2150.
-
Fix some minor typos for Manageable Affordances Analysis w3c/wot-thing-description#2146.
-
Renaming Initial Connection to Common Definitions w3c/wot-thing-description#2148.
-
Arch Assertion Categories w3c/wot-thing-description#2149.
-
Add categorization for TD-related Architecture assertions 37 to 45 w3c/wot-thing-description#2147.
-
Add categorization for TD-related Architecture assertions 1 to 9 w3c/wot-thing-description#2143.
-
Add categorization for TD-related Architecture assertions 19 to 27 w3c/wot-thing-description#2129.
-
-
7 pull requests received 48 new comments.
-
Common Definitions Examples w3c/wot-thing-description#2154 (17 comments by @chachamimm, @danielpeintner, @egekorkan, @lu-zero, @mahdanoura, @TallTed)
-
Add a proposal for manageable affordances and data mapping w3c/wot-thing-description#2162 (16 comments by @TallTed)
-
Arch Assertion Categories w3c/wot-thing-description#2149 (6 comments by @danielpeintner, @egekorkan)
-
fix: syntax error in wotsec: \# w3c/wot-thing-description#2158 (3 comments by @ektrah, @sebastiankb)
-
Add categorization for TD-related Architecture assertions 1 to 9 w3c/wot-thing-description#2143 (2 comments by @egekorkan)
-
Add categorization for TD-related Architecture assertions 37 to 45 w3c/wot-thing-description#2147 (1 comment by @egekorkan)
-
w3c/wot-resources
-
2 pull requests opened.
-
wot-next resources and ns repository information w3c/wot-resources#27, by @egekorkan.
-
Fixes to two links w3c/wot-resources#26, by @egekorkan.
-
-
1 pull request received 3 new comments.
w3c/wot-scripting-api
-
1 issue opened.
-
Error: async iterable is now changed to async_iterable w3c/wot-scripting-api#579, by @danielpeintner.
-
-
1 issue closed.
-
Improve section 5 w3c/wot-scripting-api#530.
-
-
4 issues received 6 new comments.
-
Error: async iterable is now changed to async_iterable w3c/wot-scripting-api#579 (2 comments by @danielpeintner, @saschanaz)
-
-
1 pull request opened.
-
Change return type of invokeAction from InteractionOutput to ActionInteractionOutput w3c/wot-scripting-api#580, by @danielpeintner.
-
-
1 pull request merged.
-
Editorial: Align with Web IDL specification w3c/wot-scripting-api#578.
-
-
1 pull request received 1 new comment.
-
Editorial: Align with Web IDL specification w3c/wot-scripting-api#578 (1 comment by @danielpeintner)
-
w3c/wot-profile
-
24 issues opened.
-
Requirement: Profiles should not conflict with each other w3c/wot-profile#475, by @benfrancis.
-
Requirement: Require conformance with the Thing Description 2.0 specification w3c/wot-profile#474, by @benfrancis.
-
Requirement: Do not describe an existing single-vendor IoT platform w3c/wot-profile#473, by @benfrancis.
-
Requirement: Do not define security schemes w3c/wot-profile#472, by @benfrancis.
-
Requirement: Do not define new discovery mechanisms w3c/wot-profile#471, by @benfrancis.
-
Requirement: Do not define data payload formats w3c/wot-profile#470, by @benfrancis.
-
Requirement: Do not define concrete protocol bindings w3c/wot-profile#469, by @benfrancis.
-
Requirement: Do not extend the WoT Thing Description Information Model w3c/wot-profile#468, by @benfrancis.
-
Requirement: Constrain Semantic Contexts w3c/wot-profile#467, by @benfrancis.
-
Requirement: Constrain Link Relation Types w3c/wot-profile#466, by @benfrancis.
-
Requirement: Constrain Discovery Mechanisms w3c/wot-profile#465, by @benfrancis.
-
Requirement: Constrain Security Schemes w3c/wot-profile#464, by @benfrancis.
-
Requirement: Constrain Payload Bindings w3c/wot-profile#463, by @benfrancis.
-
Requirement: Constrain Protocol Bindings w3c/wot-profile#462, by @benfrancis.
-
Requirement: Profile Identifier w3c/wot-profile#461, by @benfrancis.
-
Requirement: Do not allow application domain specific Profiles w3c/wot-profile#460, by @benfrancis.
-
Requirement: Keep the Number of Profiles to a Minimum w3c/wot-profile#459, by @benfrancis.
-
Requirement: Profile Registry w3c/wot-profile#458, by @benfrancis.
-
Requirement: Profiling Mechanism w3c/wot-profile#457, by @benfrancis.
-
Use Case: Smart Building Cloud Service w3c/wot-profile#456, by @benfrancis.
-
Use Case: Smart Building Hub w3c/wot-profile#455, by @benfrancis.
-
Use Case: Smart Home Device w3c/wot-profile#454, by @benfrancis.
-
Use Case: Smart Home Mobile App w3c/wot-profile#453, by @benfrancis.
-
Use Case: Smart Home Hub w3c/wot-profile#452, by @benfrancis.
-
-
23 issues closed.
-
Requirement: Do not describe an existing single-vendor IoT platform w3c/wot-profile#473.
-
Requirement: Require conformance with the Thing Description 2.0 specification w3c/wot-profile#474.
-
Requirement: Profiles should not conflict with each other w3c/wot-profile#475.
-
Requirement: Do not define new discovery mechanisms w3c/wot-profile#471.
-
Requirement: Do not define security schemes w3c/wot-profile#472.
-
Requirement: Do not extend the WoT Thing Description Information Model w3c/wot-profile#468.
-
Requirement: Do not define concrete protocol bindings w3c/wot-profile#469.
-
Requirement: Constrain Link Relation Types w3c/wot-profile#466.
-
Requirement: Constrain Semantic Contexts w3c/wot-profile#467.
-
Requirement: Constrain Discovery Mechanisms w3c/wot-profile#465.
-
Requirement: Constrain Payload Bindings w3c/wot-profile#463.
-
Requirement: Constrain Security Schemes w3c/wot-profile#464.
-
Requirement: Profile Identifier w3c/wot-profile#461.
-
Requirement: Constrain Protocol Bindings w3c/wot-profile#462.
-
Requirement: Keep the Number of Profiles to a Minimum w3c/wot-profile#459.
-
Requirement: Profile Registry w3c/wot-profile#458.
-
Requirement: Profiling Mechanism w3c/wot-profile#457.
-
Use Case: Smart Building Hub w3c/wot-profile#455.
-
Use Case: Smart Building Cloud Service w3c/wot-profile#456.
-
Use Case: Smart Home Mobile App w3c/wot-profile#453.
-
Use Case: Smart Home Device w3c/wot-profile#454.
-
Use Case: Smart Home Hub w3c/wot-profile#452.
-
How should we capture use cases & requirements for Profiles 2.0? w3c/wot-profile#448.
-
-
2 issues reopened.
-
Requirement: Do not allow application domain specific Profiles w3c/wot-profile#460, by @benfrancis.
-
Requirement: Do not define data payload formats w3c/wot-profile#470, by @benfrancis.
-
-
12 issues received 32 new comments.
-
Requirement: Do not describe an existing single-vendor IoT platform w3c/wot-profile#473 (6 comments by @benfrancis, @egekorkan, @lu-zero, @TallTed)
-
Requirement: Profiles should not conflict with each other w3c/wot-profile#475 (6 comments by @benfrancis, @egekorkan, @lu-zero, @TallTed)
-
Requirement: Do not allow application domain specific Profiles w3c/wot-profile#460 (5 comments by @benfrancis, @lu-zero)
-
Should Profiles constrain which interaction affordances and data schemas a Thing uses? w3c/wot-profile#450 (3 comments by @benfrancis, @egekorkan, @hspaay)
-
Requirement: Do not define concrete protocol bindings w3c/wot-profile#469 (1 comment by @benfrancis)
-
How should we capture use cases & requirements for Profiles 2.0? w3c/wot-profile#448 (1 comment by @benfrancis)
-
-
9 pull requests opened.
-
Remove link to missing atrisk CSS file w3c/wot-profile#484, by @benfrancis.
-
Generate static HTML of requirements document for publication of first Draft Note w3c/wot-profile#483, by @benfrancis.
-
Introduction for Use Cases & Requirements document w3c/wot-profile#482, by @benfrancis.
-
Profile Registry Entry requirements w3c/wot-profile#481, by @benfrancis.
-
Profile Registry requirements - closes #458 and #459 w3c/wot-profile#480, by @benfrancis.
-
Profiling Mechanism requirement - closes #457 w3c/wot-profile#479, by @benfrancis.
-
Smart building use cases - closes #455 and #456 w3c/wot-profile#478, by @benfrancis.
-
Smart home use cases - closes #452, #453 and #454 w3c/wot-profile#477, by @benfrancis.
-
Document structure for WoT Profiles 2.0 Use Cases & Requirements w3c/wot-profile#476, by @benfrancis.
-
-
11 pull requests merged.
-
Generate static HTML of requirements document for publication of first Draft Note w3c/wot-profile#483.
-
Remove link to missing atrisk CSS file w3c/wot-profile#484.
-
Profile Registry Entry requirements w3c/wot-profile#481.
-
Profile Registry requirements - closes #458 and #459 w3c/wot-profile#480.
-
Introduction for Use Cases & Requirements document w3c/wot-profile#482.
-
Profiling Mechanism requirement - closes #457 w3c/wot-profile#479.
-
Smart building use cases - closes #455 and #456 w3c/wot-profile#478.
-
Smart home use cases - closes #452, #453 and #454 w3c/wot-profile#477.
-
Minor typo w3c/wot-profile#449.
-
Document structure for WoT Profiles 2.0 Use Cases & Requirements w3c/wot-profile#476.
-
Move Michael McCool and Ryuichi Matsukura to former editors as requested w3c/wot-profile#451.
-
-
1 pull request closed.
-
A start on use cases and requirements for Profiles 2.0 w3c/wot-profile#417.
-
-
11 pull requests received 61 new comments.
-
Introduction for Use Cases & Requirements document w3c/wot-profile#482 (10 comments by @benfrancis, @lu-zero, @TallTed)
-
Profile Registry requirements - closes #458 and #459 w3c/wot-profile#480 (6 comments by @benfrancis, @TallTed)
-
Smart building use cases - closes #455 and #456 w3c/wot-profile#478 (6 comments by @benfrancis, @lu-zero, @TallTed)
-
Smart home use cases - closes #452, #453 and #454 w3c/wot-profile#477 (6 comments by @benfrancis, @TallTed)
-
Profiling Mechanism requirement - closes #457 w3c/wot-profile#479 (3 comments by @benfrancis, @TallTed)
-
Generate static HTML of requirements document for publication of first Draft Note w3c/wot-profile#483 (1 comment by @benfrancis)
-
A start on use cases and requirements for Profiles 2.0 w3c/wot-profile#417 (1 comment by @benfrancis)
-
Document structure for WoT Profiles 2.0 Use Cases & Requirements w3c/wot-profile#476 (1 comment by @benfrancis)
-
Move Michael McCool and Ryuichi Matsukura to former editors as requested w3c/wot-profile#451 (1 comment by @benfrancis)
w3c/wot-binding-templates
-
3 issues opened.
-
Conflicting editor/style settings ? w3c/wot-binding-templates#449, by @danielpeintner.
-
Alignment on the terms used in Binding Ontologies w3c/wot-binding-templates#448, by @egekorkan.
-
Modbus: timeout unit is not clear w3c/wot-binding-templates#447, by @egekorkan.
-
-
1 issue closed.
-
Conflicting editor/style settings ? w3c/wot-binding-templates#449.
-
-
1 issue received 1 new comment.
-
5 pull requests opened.
-
Editorconfig Fixes w3c/wot-binding-templates#450, by @egekorkan.
-
Removing S from Bindings links w3c/wot-binding-templates#446, by @egekorkan.
-
[WIP] Missing ReadFileRecord in Modbus binding w3c/wot-binding-templates#445, by @sebastiankb.
-
Adding Prettier Support w3c/wot-binding-templates#444, by @egekorkan.
-
fix(modbus): remove windows line feed in json schema w3c/wot-binding-templates#443, by @brandon1024.
-
-
5 pull requests merged.
-
Removing S from Bindings links w3c/wot-binding-templates#446.
-
Editorconfig Fixes w3c/wot-binding-templates#450.
-
Adding Prettier Support w3c/wot-binding-templates#444.
-
fix(modbus): remove windows line feed in json schema w3c/wot-binding-templates#443.
-
fix(modbus): correct small typo in default mappings section w3c/wot-binding-templates#439.
-
-
4 pull requests received 12 new comments.
-
fix(modbus): correct small typo in default mappings section w3c/wot-binding-templates#439 (4 comments by @egekorkan)
-
[WIP] Missing ReadFileRecord in Modbus binding w3c/wot-binding-templates#445 (3 comments by @danielpeintner, @mahdanoura, @sebastiankb)
-
fix(modbus): remove windows line feed in json schema w3c/wot-binding-templates#443 (2 comments by @brandon1024)
-
w3c/wot-binding-registry
-
1 pull request opened.
-
Fixing prettier version w3c/wot-binding-registry#40, by @egekorkan.
-
-
1 pull request merged.
-
Fixing prettier version w3c/wot-binding-registry#40.
-
Past meetings
-
18 meetings.
Participants
-
2 participants joined.
-
Michael McCool (W3C Invited Experts) joined.
-
Mahmood Afshari (W3C Invited Experts) joined.
-
-
1 participant left.
-
Michael McCool (W3C Invited Experts) left.
-
GitHub
w3c/wot-profile
-
3 issues opened.
-
Should Profiles constrain which interaction affordances and data schemas a Thing uses? w3c/wot-profile#450, by @benfrancis.
-
How should we capture use cases & requirements for Profiles 2.0? w3c/wot-profile#448, by @benfrancis.
-
Normative references to discontinued specs in Web of Things (WoT) Profiles w3c/wot-profile#445, by @dontcallmedom-bot.
-
-
1 issue closed.
-
Normative references to discontinued specs in Web of Things (WoT) Profiles w3c/wot-profile#445.
-
-
2 issues received 10 new comments.
-
Should Profiles constrain which interaction affordances and data schemas a Thing uses? w3c/wot-profile#450 (7 comments by @benfrancis, @egekorkan, @hspaay, @lu-zero)
-
How should we capture use cases & requirements for Profiles 2.0? w3c/wot-profile#448 (3 comments by @benfrancis, @egekorkan)
-
-
4 pull requests opened.
-
Move Michael McCool and Ryuichi Matsukura to former editors as requested w3c/wot-profile#451, by @benfrancis.
-
Minor typo w3c/wot-profile#449, by @danielpeintner.
-
Generate static HTML for Working Draft publication w3c/wot-profile#447, by @benfrancis.
-
Replace references to obsolete HTTP specification - closes #445 w3c/wot-profile#446, by @benfrancis.
-
-
3 pull requests merged.
-
Generate static HTML for Working Draft publication w3c/wot-profile#447.
-
Fixing profile vs profiles usage w3c/wot-profile#444.
-
Replace references to obsolete HTTP specification - closes #445 w3c/wot-profile#446.
-
-
1 pull request closed.
-
WIP: Provide example in the new introduction section w3c/wot-profile#334.
-
-
5 pull requests received 6 new comments.
-
Move Michael McCool and Ryuichi Matsukura to former editors as requested w3c/wot-profile#451 (1 comment by @ashimura)
-
Replace references to obsolete HTTP specification - closes #445 w3c/wot-profile#446 (1 comment by @mjkoster)
w3c/wot-thing-description
-
8 issues opened.
-
Unclear behavior around version container when TDs are generated from TMs w3c/wot-thing-description#2145, by @egekorkan.
-
Updating Appendix on contentType Usage w3c/wot-thing-description#2141, by @egekorkan.
-
Assertion Highlighting for dark and light mode w3c/wot-thing-description#2138, by @danielpeintner.
-
Prettier Action not working w3c/wot-thing-description#2136, by @danielpeintner.
-
Renaming Reusable Connections to Common Definitions w3c/wot-thing-description#2135, by @egekorkan.
-
ComboSecurityScheme referencing yet another ComboSecurityScheme w3c/wot-thing-description#2134, by @danielpeintner.
-
Ambiguous meaning of queryaction w3c/wot-thing-description#2133, by @egekorkan.
-
Creating Static Files for TD 2.0 FPWD Publication w3c/wot-thing-description#2132, by @egekorkan.
-
-
6 issues closed.
-
TD 2.0 FPWD Goals w3c/wot-thing-description#2112.
-
Creating Static Files for TD 2.0 FPWD Publication w3c/wot-thing-description#2132.
-
Prettier Action not working w3c/wot-thing-description#2136.
-
Assertion Highlighting for dark and light mode w3c/wot-thing-description#2138.
-
Consider removing section 9.3.1 Protocol Binding based on HTTP in version 1.1 w3c/wot-thing-description#1259.
-
Default Mechanisms for Bindings Vocabularies w3c/wot-thing-description#2052.
-
-
7 issues received 10 new comments.
-
ComboSecurityScheme referencing yet another ComboSecurityScheme w3c/wot-thing-description#2134 (2 comments by @egekorkan)
-
Ambiguous meaning of queryaction w3c/wot-thing-description#2133 (2 comments by @benfrancis, @hspaay)
-
Is the use of "$ref" and "definitions" allowed in TD ? w3c/wot-thing-description#307 (2 comments by @danielpeintner, @fennibay)
-
Renaming Reusable Connections to Common Definitions w3c/wot-thing-description#2135 (1 comment by @benfrancis)
-
Creating Static Files for TD 2.0 FPWD Publication w3c/wot-thing-description#2132 (1 comment by @egekorkan)
-
-
11 pull requests opened.
-
Arch Assertion Categories w3c/wot-thing-description#2149, by @egekorkan.
-
Renaming Initial Connection to Common Definitions w3c/wot-thing-description#2148, by @egekorkan.
-
Add categorization for TD-related Architecture assertions 37 to 45 w3c/wot-thing-description#2147, by @danielpeintner.
-
Fix some minor typos for Manageable Affordances Analysis w3c/wot-thing-description#2146, by @danielpeintner.
-
PR Template Fix w3c/wot-thing-description#2144, by @egekorkan.
-
Add categorization for TD-related Architecture assertions 1 to 9 w3c/wot-thing-description#2143, by @k-toumura.
-
Removing 1.1 Context Rules w3c/wot-thing-description#2142, by @egekorkan.
-
TD 2.0 FPWD Publication w3c/wot-thing-description#2140, by @egekorkan.
-
Provide 2 assertion colors depending on dark/light mode w3c/wot-thing-description#2139, by @danielpeintner.
-
Fix Prettier Problem w3c/wot-thing-description#2137, by @danielpeintner.
-
id and respec fixes w3c/wot-thing-description#2131, by @egekorkan.
-
-
10 pull requests merged.
-
Removing 1.1 Context Rules w3c/wot-thing-description#2142.
-
PR Template Fix w3c/wot-thing-description#2144.
-
Improve analysis manageable affordances document and add an initial list of user stories. w3c/wot-thing-description#2107.
-
TD 2.0 FPWD Publication w3c/wot-thing-description#2140.
-
Fix Prettier Problem w3c/wot-thing-description#2137.
-
Provide 2 assertion colors depending on dark/light mode w3c/wot-thing-description#2139.
-
id and respec fixes w3c/wot-thing-description#2131.
-
Temporary Context URL w3c/wot-thing-description#2128.
-
Change occurance of bindings registry w3c/wot-thing-description#2130.
-
Removing HTTP Binding and Adjusting Defaulting Mechanism for all Bindings w3c/wot-thing-description#2123.
-
-
10 pull requests received 52 new comments.
-
Improve analysis manageable affordances document and add an initial list of user stories. w3c/wot-thing-description#2107 (20 comments by @benfrancis, @danielpeintner, @egekorkan, @relu91, @TallTed)
-
Removing HTTP Binding and Adjusting Defaulting Mechanism for all Bindings w3c/wot-thing-description#2123 (11 comments by @egekorkan, @TallTed)
-
Add categorization for TD-related Architecture assertions 19 to 27 w3c/wot-thing-description#2129 (10 comments by @egekorkan, @JKRhb, @k-toumura, @TallTed)
-
Add categorization for TD-related Architecture assertions 1 to 9 w3c/wot-thing-description#2143 (3 comments by @egekorkan)
-
Provide 2 assertion colors depending on dark/light mode w3c/wot-thing-description#2139 (2 comments by @danielpeintner, @relu91)
-
w3c/wot-binding-registry
-
2 issues opened.
-
Creating Static Documents for Publication w3c/wot-binding-registry#36, by @egekorkan.
-
Prettier Action not working w3c/wot-binding-registry#34, by @egekorkan.
-
-
4 issues closed.
-
Creating Static Documents for Publication w3c/wot-binding-registry#36.
-
Removing Usage of X from Terminology w3c/wot-binding-registry#25.
-
Prettier Action not working w3c/wot-binding-registry#34.
-
Assertion Highighting for dark and light mode w3c/wot-binding-registry#31.
-
-
3 issues received 3 new comments.
-
5 pull requests opened.
-
Add missing space w3c/wot-binding-registry#39, by @danielpeintner.
-
Draft Registry Publication w3c/wot-binding-registry#38, by @egekorkan.
-
Removing Usage of X from Terminology w3c/wot-binding-registry#37, by @danielpeintner.
-
Fix Prettier Problem w3c/wot-binding-registry#35, by @danielpeintner.
-
Running Formatting w3c/wot-binding-registry#33, by @egekorkan.
-
-
6 pull requests merged.
-
Add missing space w3c/wot-binding-registry#39.
-
Draft Registry Publication w3c/wot-binding-registry#38.
-
Removing Usage of X from Terminology w3c/wot-binding-registry#37.
-
Fix Prettier Problem w3c/wot-binding-registry#35.
-
refactor: provide 2 assertion colors depending on dark/light mode w3c/wot-binding-registry#32.
-
Running Formatting w3c/wot-binding-registry#33.
-
-
4 pull requests received 22 new comments.
-
refactor: provide 2 assertion colors depending on dark/light mode w3c/wot-binding-registry#32 (14 comments by @danielpeintner, @egekorkan, @ektrah, @relu91)
-
Removing Usage of X from Terminology w3c/wot-binding-registry#37 (3 comments by @danielpeintner, @egekorkan)
-
w3c/wot-scripting-api
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Update README.md with tag for subfolder w3c/wot-scripting-api#577.
-
-
1 pull request received 1 new comment.
-
Editorial: Align with Web IDL specification w3c/wot-scripting-api#578 (1 comment by @danielpeintner)
-
w3c/wot-binding-templates
-
2 issues opened.
-
Modbus: Restricting quantity based on data type w3c/wot-binding-templates#441, by @egekorkan.
-
Creating Static Documents for new Group Note Publication w3c/wot-binding-templates#440, by @egekorkan.
-
-
2 issues closed.
-
Creating Static Documents for new Group Note Publication w3c/wot-binding-templates#440.
-
Adding Explanation about the future of this document w3c/wot-binding-templates#433.
-
-
1 issue received 1 new comment.
-
Creating Static Documents for new Group Note Publication w3c/wot-binding-templates#440 (1 comment by @egekorkan)
-
-
1 pull request opened.
-
New Note Publication w3c/wot-binding-templates#442, by @egekorkan.
-
-
3 pull requests merged.
-
New Note Publication w3c/wot-binding-templates#442.
-
Moving http binding related content from td spec w3c/wot-binding-templates#435.
-
Retiring the main document w3c/wot-binding-templates#434.
-
-
3 pull requests received 12 new comments.
-
fix(modbus): correct small typo in default mappings section w3c/wot-binding-templates#439 (5 comments by @brandon1024, @egekorkan, @TallTed)
-
Retiring the main document w3c/wot-binding-templates#434 (5 comments by @danielpeintner, @egekorkan, @TallTed)
-
Moving http binding related content from td spec w3c/wot-binding-templates#435 (2 comments by @egekorkan)
-
w3c/wot-discovery
-
1 issue opened.
-
Normative references to discontinued specs in Web of Things (WoT) Discovery w3c/wot-discovery#553, by @dontcallmedom-bot.
-
w3c/wot-resources
-
1 pull request merged.
-
WoT Next Resources w3c/wot-resources#25.
-
-
1 pull request received 5 new comments.
Past meetings
-
16 meetings.
GitHub
w3c/wot-thing-description
-
3 issues opened.
-
Categorizing Architecture Assertions w3c/wot-thing-description#2126, by @egekorkan.
-
Adding explanation about the difference to profiles w3c/wot-thing-description#2121, by @egekorkan.
-
Moving normative text from Architecture Specification about the TD features w3c/wot-thing-description#2120, by @egekorkan.
-
-
3 issues closed.
-
Adding explanation about the difference to profiles w3c/wot-thing-description#2121.
-
Make `contentType` optional in `ExpectedResponse` class w3c/wot-thing-description#1780.
-
Moving normative text from Architecture Specification about the TD features w3c/wot-thing-description#2120.
-
-
3 issues received 7 new comments.
-
Moving normative text from Architecture Specification about the TD features w3c/wot-thing-description#2120 (4 comments by @egekorkan, @k-toumura)
-
Adding explanation about the difference to profiles w3c/wot-thing-description#2121 (2 comments by @benfrancis, @egekorkan)
-
Default Mechanisms for Bindings Vocabularies w3c/wot-thing-description#2052 (1 comment by @egekorkan)
-
-
9 pull requests opened.
-
Change occurance of bindings registry w3c/wot-thing-description#2130, by @egekorkan.
-
Add categorization for TD-related Architecture assertions 19 to 27 w3c/wot-thing-description#2129, by @JKRhb.
-
Temporary Context URL w3c/wot-thing-description#2128, by @egekorkan.
-
Moving Sebastian and McCool to formerEditors w3c/wot-thing-description#2127, by @egekorkan.
-
Automating assertion list generation w3c/wot-thing-description#2125, by @egekorkan.
-
Add list of assertions in Architecture document w3c/wot-thing-description#2124, by @k-toumura.
-
Removing HTTP Binding and Adjusting Defaulting Mechanism for all Bindings w3c/wot-thing-description#2123, by @egekorkan.
-
Profile explanation w3c/wot-thing-description#2122, by @egekorkan.
-
Minor: remove duplication use & choose w3c/wot-thing-description#2119, by @danielpeintner.
-
-
7 pull requests merged.
-
Moving Sebastian and McCool to formerEditors w3c/wot-thing-description#2127.
-
Automating assertion list generation w3c/wot-thing-description#2125.
-
Profile explanation w3c/wot-thing-description#2122.
-
Make `contentType` optional in `ExpectedResponse` and `AdditionalExpectedResponse` classes w3c/wot-thing-description#2081.
-
Add list of assertions in Architecture document w3c/wot-thing-description#2124.
-
Minor: remove duplication use & choose w3c/wot-thing-description#2119.
-
Binding Intro Reorganization w3c/wot-thing-description#2118.
-
-
9 pull requests received 103 new comments.
-
Make `contentType` optional in `ExpectedResponse` and `AdditionalExpectedResponse` classes w3c/wot-thing-description#2081 (31 comments by @benfrancis, @egekorkan, @JKRhb, @relu91, @TallTed)
-
Removing HTTP Binding and Adjusting Defaulting Mechanism for all Bindings w3c/wot-thing-description#2123 (24 comments by @danielpeintner, @egekorkan, @TallTed)
-
Profile explanation w3c/wot-thing-description#2122 (19 comments by @benfrancis, @danielpeintner, @egekorkan, @TallTed)
-
Binding Intro Reorganization w3c/wot-thing-description#2118 (18 comments by @danielpeintner, @egekorkan)
-
Add categorization for TD-related Architecture assertions 19 to 27 w3c/wot-thing-description#2129 (5 comments by @egekorkan, @JKRhb)
-
Improve analysis manageable affordances document and add an initial list of user stories. w3c/wot-thing-description#2107 (2 comments by @egekorkan)
-
Moving Sebastian and McCool to formerEditors w3c/wot-thing-description#2127 (1 comment by @egekorkan)
-
w3c/wot-binding-templates
-
3 issues opened.
-
Should Longpolling, SSE and Websocket examples for async operations be part of the HTTP Binding? w3c/wot-binding-templates#438, by @egekorkan.
-
Should xsd:integer be allowed in Modbus? w3c/wot-binding-templates#437, by @egekorkan.
-
Modbus: Entity-based default functions w3c/wot-binding-templates#436, by @egekorkan.
-
-
2 issues received 2 new comments.
-
OPC UA Binding Document Feedback w.r.t. contentType w3c/wot-binding-templates#430 (1 comment by @barnstee)
-
Adding Explanation about the future of this document w3c/wot-binding-templates#433 (1 comment by @egekorkan)
-
-
3 pull requests opened.
-
fix(modbus): correct small typo in default mappings section w3c/wot-binding-templates#439, by @brandon1024.
-
Moving http binding related content from td spec w3c/wot-binding-templates#435, by @egekorkan.
-
Retiring the main document w3c/wot-binding-templates#434, by @egekorkan.
-
-
1 pull request merged.
-
Adapting to Registry and Binding Word Usage w3c/wot-binding-templates#432.
-
-
4 pull requests received 49 new comments.
-
fix(modbus): correct small typo in default mappings section w3c/wot-binding-templates#439 (28 comments by @brandon1024, @egekorkan, @TallTed)
-
Retiring the main document w3c/wot-binding-templates#434 (10 comments by @danielpeintner, @egekorkan)
-
Adapting to Registry and Binding Word Usage w3c/wot-binding-templates#432 (8 comments by @egekorkan, @mjkoster)
-
Moving http binding related content from td spec w3c/wot-binding-templates#435 (3 comments by @TallTed)
-
w3c/wot-resources
-
1 pull request opened.
-
WoT Next Resources w3c/wot-resources#25, by @egekorkan.
-
w3c/wot-binding-registry
-
6 issues opened.
-
Assertion Highighting for dark and light mode w3c/wot-binding-registry#31, by @danielpeintner.
-
Intro Section (https://w3c.github.io/wot-bindings-registry/#intro-section-document) rework to look nice w3c/wot-binding-registry#29, by @egekorkan.
-
Changing to WoT Binding Registry from WoT Bindings Registry w3c/wot-binding-registry#26, by @egekorkan.
-
Removing Usage of X from Terminology w3c/wot-binding-registry#25, by @egekorkan.
-
Fixing Terminology Warnings w3c/wot-binding-registry#23, by @egekorkan.
-
Registry Entries before the Registry is finalized w3c/wot-binding-registry#22, by @egekorkan.
-
-
8 issues closed.
-
First Draft Registry Plan w3c/wot-binding-registry#12.
-
Intro Section (https://w3c.github.io/wot-bindings-registry/#intro-section-document) rework to look nice w3c/wot-binding-registry#29.
-
Changing to WoT Binding Registry from WoT Bindings Registry w3c/wot-binding-registry#26.
-
Registry Entries before the Registry is finalized w3c/wot-binding-registry#22.
-
Fixing Terminology Warnings w3c/wot-binding-registry#23.
-
Creating the empty table for the bindings to go to w3c/wot-binding-registry#13.
-
Reformat the document to look good by taking over the results of refactor w3c/wot-binding-registry#14.
-
Writing the Abstract and Informative Introduction w3c/wot-binding-registry#7.
-
-
3 issues received 4 new comments.
-
Registry Entries before the Registry is finalized w3c/wot-binding-registry#22 (2 comments by @egekorkan)
-
-
11 pull requests opened.
-
refactor: provide 2 assertion colors depending on dark/light mode w3c/wot-binding-registry#32, by @danielpeintner.
-
Second intro section refactoring w3c/wot-binding-registry#30, by @egekorkan.
-
Pilot Phase Information w3c/wot-binding-registry#28, by @egekorkan.
-
Adapt documenting to remove s from bindings w3c/wot-binding-registry#27, by @egekorkan.
-
Make use of some terminology terms w3c/wot-binding-registry#24, by @danielpeintner.
-
Registry Table w3c/wot-binding-registry#21, by @egekorkan.
-
Readme Alignment w3c/wot-binding-registry#20, by @egekorkan.
-
Intro Refactor w3c/wot-binding-registry#19, by @egekorkan.
-
Delete requirements.md w3c/wot-binding-registry#18, by @egekorkan.
-
refactor: reformat document Section 6 w3c/wot-binding-registry#17, by @danielpeintner.
-
Adding Ege Korkan to editors list w3c/wot-binding-registry#16, by @egekorkan.
-
-
10 pull requests merged.
-
Second intro section refactoring w3c/wot-binding-registry#30.
-
Adapt documenting to remove s from bindings w3c/wot-binding-registry#27.
-
Pilot Phase Information w3c/wot-binding-registry#28.
-
Make use of some terminology terms w3c/wot-binding-registry#24.
-
Registry Table w3c/wot-binding-registry#21.
-
refactor: reformat document Section 6 w3c/wot-binding-registry#17.
-
Readme Alignment w3c/wot-binding-registry#20.
-
Intro Refactor w3c/wot-binding-registry#19.
-
Delete requirements.md w3c/wot-binding-registry#18.
-
Adding Ege Korkan to editors list w3c/wot-binding-registry#16.
-
-
11 pull requests received 62 new comments.
-
refactor: reformat document Section 6 w3c/wot-binding-registry#17 (35 comments by @danielpeintner, @egekorkan)
-
Make use of some terminology terms w3c/wot-binding-registry#24 (6 comments by @danielpeintner, @egekorkan)
-
Second intro section refactoring w3c/wot-binding-registry#30 (4 comments by @danielpeintner, @egekorkan)
-
refactor: provide 2 assertion colors depending on dark/light mode w3c/wot-binding-registry#32 (2 comments by @danielpeintner, @egekorkan)
-
w3c/wot-discovery
-
1 issue opened.
-
Missing input schema in createThing, retrieveThingm updatingThing action affordances w3c/wot-discovery#552, by @hspaay.
-
-
1 issue received 4 new comments.
w3c/wot-profile
-
1 issue opened.
-
British vs. American English w3c/wot-profile#442, by @danielpeintner.
-
-
1 issue closed.
-
British vs. American English w3c/wot-profile#442.
-
-
2 issues received 4 new comments.
-
Convert specification to Working Group Note and add a note about the document status w3c/wot-profile#432 (2 comments by @benfrancis, @mlagally)
-
4 pull requests opened.
-
Fixing profile vs profiles usage w3c/wot-profile#444, by @egekorkan.
-
Change words to US English - closes #442 w3c/wot-profile#443, by @benfrancis.
-
fix minor typos w3c/wot-profile#441, by @danielpeintner.
-
Fix TD 1.1 reference w3c/wot-profile#440, by @danielpeintner.
-
-
3 pull requests merged.
-
Change words to US English - closes #442 w3c/wot-profile#443.
-
Fix TD 1.1 reference w3c/wot-profile#440.
-
fix minor typos w3c/wot-profile#441.
-
-
3 pull requests received 6 new comments.
-
Change words to US English - closes #442 w3c/wot-profile#443 (2 comments by @benfrancis, @danielpeintner)
Past meetings
-
20 meetings.
Participants
-
1 participant left.
-
Kudzai Manditereza (HiveMQ) left.
-
-
1 organization left.
-
HiveMQ left.
-
GitHub
w3c/wot-binding-templates
-
2 issues opened.
-
Adding Explanation about the future of this document w3c/wot-binding-templates#433, by @egekorkan.
-
OPC UA Binding Document Feedback w.r.t. contentType w3c/wot-binding-templates#430, by @danielpeintner.
-
-
1 issue received 2 new comments.
-
OPC UA Binding Document Feedback w.r.t. contentType w3c/wot-binding-templates#430 (2 comments by @relu91, @sebastiankb)
-
-
2 pull requests opened.
-
Adapting to Registry and Binding Word Usage w3c/wot-binding-templates#432, by @egekorkan.
-
fix: update profinet schema to correct enumeratedValue and add new types w3c/wot-binding-templates#431, by @alicanipek.
-
-
3 pull requests merged.
-
fix: update profinet schema to correct enumeratedValue and add new types w3c/wot-binding-templates#431.
-
fix: model BACnet relinquish explicitly w3c/wot-binding-templates#428.
-
fix: BACnet JSON Schema syntax corrections w3c/wot-binding-templates#429.
-
-
3 pull requests received 13 new comments.
-
fix: model BACnet relinquish explicitly w3c/wot-binding-templates#428 (8 comments by @egekorkan, @fennibay, @TallTed)
-
fix: update profinet schema to correct enumeratedValue and add new types w3c/wot-binding-templates#431 (4 comments by @alicanipek, @egekorkan, @Kaz040, @relu91)
-
w3c/wot-profile
-
2 issues opened.
-
Broken link to requirements document w3c/wot-profile#434, by @benfrancis.
-
Convert specification to Working Group Note and add a note about the document status w3c/wot-profile#432, by @ashimura.
-
-
21 issues closed.
-
Clarify the behavior when a response does not have body w3c/wot-profile#360.
-
Broken link to requirements document w3c/wot-profile#434.
-
PR #364 introduced a duplicate conflicting assertion w3c/wot-profile#367.
-
How can clients verify that a device they're interacting with is compliant? w3c/wot-profile#385.
-
Make it clearer that Profiles should only progressively enhance a Thing w3c/wot-profile#403.
-
Assert that profiles should not diverge from binding template defaults w3c/wot-profile#404.
-
Issues with recent webhook subscription mechanism changes w3c/wot-profile#335.
-
Mismatch with MUST clause and examples in default language section w3c/wot-profile#373.
-
Accesibility assertions are not specific enough w3c/wot-profile#320.
-
Unclear character set constraints and non-UTF-8 html w3c/wot-profile#386.
-
Remove or re-work section 6.1.2 Links w3c/wot-profile#255.
-
Column names w3c/wot-profile#333.
-
Create sub-assertions for Keywords in the Links section w3c/wot-profile#348.
-
Multiple subscriptions from the same consumer to the same endpoint? w3c/wot-profile#388.
-
Review of HTTP Webhook Profile w3c/wot-profile#375.
-
Normative text needs to be outside of examples w3c/wot-profile#329.
-
Refine example Thing Description w3c/wot-profile#389.
-
Re-work HTTP Webhook Profile section w3c/wot-profile#423.
-
New section on Webhook message format w3c/wot-profile#258.
-
Structure of section 8.4 HTTP Webhook Profile Protocol Binding is broken w3c/wot-profile#420.
-
-
7 issues received 18 new comments.
-
Convert specification to Working Group Note and add a note about the document status w3c/wot-profile#432 (5 comments by @benfrancis, @mlagally)
-
PR #364 introduced a duplicate conflicting assertion w3c/wot-profile#367 (4 comments by @benfrancis, @egekorkan)
-
Include the "auto" security scheme to the list of supported schemes w3c/wot-profile#313 (3 comments by @benfrancis)
-
Clarify OAuth schemes - consider requiring Bearer tokens only w3c/wot-profile#347 (2 comments by @benfrancis)
-
Clarify the behavior when a response does not have body w3c/wot-profile#360 (2 comments by @benfrancis, @egekorkan)
-
Issues with recent webhook subscription mechanism changes w3c/wot-profile#335 (1 comment by @benfrancis)
-
Mismatch with MUST clause and examples in default language section w3c/wot-profile#373 (1 comment by @benfrancis)
-
-
12 pull requests opened.
-
Add a list of changes made since the 2023 Working Draft w3c/wot-profile#439, by @benfrancis.
-
Change document to Group Note and explain status of document - closes #432 w3c/wot-profile#438, by @benfrancis.
-
Clean up markup w3c/wot-profile#437, by @benfrancis.
-
Clarify behaviour when an HTTP request or response does not have a body - closes #360 w3c/wot-profile#436, by @benfrancis.
-
Fix broken link to Profile requirements - closes #434 w3c/wot-profile#435, by @benfrancis.
-
Duplicate conflicting assertion - closes #367 w3c/wot-profile#433, by @sebastiankb.
-
Profiling mechanism clarifications - closes #385, closes #403, closes #404 w3c/wot-profile#431, by @benfrancis.
-
Soften privacy and security assertions - closes #422 w3c/wot-profile#430, by @benfrancis.
-
Remove Default Language section - closes #373 w3c/wot-profile#429, by @benfrancis.
-
Replace Accessibility Constraints with Accessibility Considerations section - closes #320 w3c/wot-profile#428, by @benfrancis.
-
Re-work Links section - closes #255 w3c/wot-profile#427, by @benfrancis.
-
Re-work HTTP Webhook Profile - closes #423 w3c/wot-profile#426, by @benfrancis.
-
-
12 pull requests merged.
-
Clean up markup w3c/wot-profile#437.
-
Add a list of changes made since the 2023 Working Draft w3c/wot-profile#439.
-
Fix broken link to Profile requirements - closes #434 w3c/wot-profile#435.
-
Duplicate conflicting assertion - closes #367 w3c/wot-profile#433.
-
Profiling mechanism clarifications - closes #385, closes #403, closes #404 w3c/wot-profile#431.
-
Soften privacy and security assertions - closes #422 w3c/wot-profile#430.
-
Remove Default Language section - closes #373 w3c/wot-profile#429.
-
Re-work Links section - closes #255 w3c/wot-profile#427.
-
Re-work HTTP Webhook Profile - closes #423 w3c/wot-profile#426.
-
Common constraints section is applicable to the entire document w3c/wot-profile#424.
-
-
2 pull requests closed.
-
Change document to Group Note and explain status of document - closes #432 w3c/wot-profile#438.
-
WIP: Allow auto security scheme for other permitted security schemes w3c/wot-profile#314.
-
-
12 pull requests received 69 new comments.
-
Profiling mechanism clarifications - closes #385, closes #403, closes #404 w3c/wot-profile#431 (26 comments by @benfrancis, @egekorkan, @relu91, @TallTed)
-
Duplicate conflicting assertion - closes #367 w3c/wot-profile#433 (11 comments by @benfrancis, @egekorkan, @relu91, @TallTed)
-
Change document to Group Note and explain status of document - closes #432 w3c/wot-profile#438 (8 comments by @benfrancis, @mlagally)
-
Clarify behaviour when an HTTP request or response does not have a body - closes #360 w3c/wot-profile#436 (6 comments by @benfrancis, @relu91, @TallTed)
-
Re-work HTTP Webhook Profile - closes #423 w3c/wot-profile#426 (4 comments by @benfrancis, @lu-zero)
-
Fix broken link to Profile requirements - closes #434 w3c/wot-profile#435 (3 comments by @benfrancis, @danielpeintner)
-
WIP: Allow auto security scheme for other permitted security schemes w3c/wot-profile#314 (1 comment by @benfrancis)
-
Add a list of changes made since the 2023 Working Draft w3c/wot-profile#439 (1 comment by @benfrancis)
-
Common constraints section is applicable to the entire document w3c/wot-profile#424 (1 comment by @benfrancis)
-
w3c/wot-thing-description
-
2 issues opened.
-
Adding accesibility assertions about having title and description w3c/wot-thing-description#2116, by @egekorkan.
-
Consistent WoT, Web of Things, TD and Thing Description usage w3c/wot-thing-description#2115, by @egekorkan.
-
-
3 issues closed.
-
Unexplained value transformation or inconsistency: metric_value and metric w3c/wot-thing-description#2038.
-
Changing short name and other aspects to TD 2.0 w3c/wot-thing-description#2111.
-
ReSpec issues - 1 warning, 2 errors w3c/wot-thing-description#2110.
-
-
4 issues received 6 new comments.
-
Agreeing on meaning of authors and editors w3c/wot-thing-description#1939 (2 comments by @egekorkan)
-
Add a schema for unobserve/observe property w3c/wot-thing-description#2085 (1 comment by @benfrancis)
-
Fix overlaps between TD and Bindings content w3c/wot-thing-description#2006 (1 comment by @mjkoster)
-
-
2 pull requests opened.
-
Binding Intro Reorganization w3c/wot-thing-description#2118, by @egekorkan.
-
fix uri variable example w3c/wot-thing-description#2117, by @egekorkan.
-
-
4 pull requests merged.
-
Initial Connection Improvements w3c/wot-thing-description#2103.
-
Propose user story for XML data mapping w3c/wot-thing-description#2109.
-
fix uri variable example w3c/wot-thing-description#2117.
-
change to td 2.0 and fix broken links w3c/wot-thing-description#2113.
-
-
5 pull requests received 63 new comments.
-
Improve analysis manageable affordances document and add an initial list of user stories. w3c/wot-thing-description#2107 (13 comments by @danielpeintner, @egekorkan, @relu91, @TallTed)
-
change to td 2.0 and fix broken links w3c/wot-thing-description#2113 (5 comments by @egekorkan, @TallTed)
-
Propose user story for XML data mapping w3c/wot-thing-description#2109 (3 comments by @danielpeintner, @egekorkan)
w3c/wot-binding-registry
-
3 issues opened.
-
Preparing the Issue Template w3c/wot-binding-registry#15, by @egekorkan.
-
Reformat the document to look good by taking over the results of refactor w3c/wot-binding-registry#14, by @egekorkan.
-
Creating the empty table for the bindings to go to w3c/wot-binding-registry#13, by @egekorkan.
-
-
2 issues received 2 new comments.
-
Creating the empty table for the bindings to go to w3c/wot-binding-registry#13 (1 comment by @egekorkan)
-
w3c/wot-scripting-api
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Editorial: Align with Web IDL specification w3c/wot-scripting-api#578, by @autokagami.
-
-
1 pull request received 8 new comments.
-
Editorial: Align with Web IDL specification w3c/wot-scripting-api#578 (8 comments by @danielpeintner, @JKRhb, @relu91, @saschanaz)
-
Past meetings
-
17 meetings.
GitHub
w3c/wot-thing-description
-
5 issues opened.
-
Creating Section Introductions for FPWD w3c/wot-thing-description#2114, by @egekorkan.
-
TD 2.0 FPWD Goals w3c/wot-thing-description#2112, by @egekorkan.
-
Changing short name and other aspects to TD 2.0 w3c/wot-thing-description#2111, by @egekorkan.
-
ReSpec issues - 1 warning, 2 errors w3c/wot-thing-description#2110, by @danielpeintner.
-
Adding Who examples or defaults for User Story template w3c/wot-thing-description#2108, by @egekorkan.
-
-
6 issues received 11 new comments.
-
Optional simple-type parameters w3c/wot-thing-description#1234 (5 comments by @danielpeintner, @egekorkan, @fennibay)
-
Consider specifying an algorithm for selecting a Form w3c/wot-thing-description#2106 (2 comments by @egekorkan, @relu91)
-
Creating Section Introductions for FPWD w3c/wot-thing-description#2114 (1 comment by @danielpeintner)
-
Collecting Input for the Manageable Affordances Analysis w3c/wot-thing-description#2099 (1 comment by @relu91)
-
-
3 pull requests opened.
-
change to td 2.0 and fix broken links w3c/wot-thing-description#2113, by @egekorkan.
-
Propose user story for XML data mapping w3c/wot-thing-description#2109, by @danielpeintner.
-
Improve analysis manageable affordances document and add an initial list of user stories. w3c/wot-thing-description#2107, by @relu91.
-
-
1 pull request merged.
-
Add HTTP to the data mapping analysis w3c/wot-thing-description#2105.
-
-
5 pull requests received 30 new comments.
-
Propose user story for XML data mapping w3c/wot-thing-description#2109 (12 comments by @danielpeintner, @egekorkan, @TallTed)
-
Improve analysis manageable affordances document and add an initial list of user stories. w3c/wot-thing-description#2107 (8 comments by @danielpeintner, @egekorkan, @relu91, @TallTed)
-
w3c/wot-profile
-
3 issues opened.
-
Content Type text/event-stream may conflict with application/json w3c/wot-profile#425, by @dezell.
-
Re-work HTTP Webhook Profile section w3c/wot-profile#423, by @benfrancis.
-
Consider softening assertions in Privacy Considerations and Security Considerations sections w3c/wot-profile#422, by @benfrancis.
-
-
6 issues closed.
-
Wide review w3c/wot-profile#358.
-
Revisit section 6 title and structure w3c/wot-profile#323.
-
Requirements due diligence w3c/wot-profile#310.
-
Remove reference to security best practices document w3c/wot-profile#269.
-
how to handle multiple forms w3c/wot-profile#141.
-
Update Figure 1 to say "Basic" rather than "Baseline" w3c/wot-profile#290.
-
-
21 issues received 35 new comments.
-
Read-only events should require authentication w3c/wot-profile#384 (4 comments by @benfrancis, @egekorkan, @NalaGinrut)
-
Some assertions need splitting up into multiple assertions w3c/wot-profile#394 (2 comments by @benfrancis)
-
Additional implementers feedback of profile assertions w3c/wot-profile#306 (2 comments by @benfrancis)
-
Contradiction with the Arch spec on protocol bindings w3c/wot-profile#299 (2 comments by @benfrancis)
-
How can clients verify that a device they're interacting with is compliant? w3c/wot-profile#385 (2 comments by @benfrancis, @egekorkan)
-
Make it clearer that Profiles should only progressively enhance a Thing w3c/wot-profile#403 (2 comments by @benfrancis, @egekorkan)
-
Clarify the behavior when a response does not have body w3c/wot-profile#360 (1 comment by @benfrancis)
-
Create sub-assertions for Keywords in the Links section w3c/wot-profile#348 (1 comment by @benfrancis)
-
Include the "auto" security scheme to the list of supported schemes w3c/wot-profile#313 (1 comment by @benfrancis)
-
Consider softening assertions in Privacy Considerations and Security Considerations sections w3c/wot-profile#422 (1 comment by @egekorkan)
-
Update Figure 1 to say "Basic" rather than "Baseline" w3c/wot-profile#290 (1 comment by @benfrancis)
-
-
2 pull requests opened.
-
Common constraints section is applicable to the entire document w3c/wot-profile#424, by @danielpeintner.
-
Switch reference from wot-security-best-practices to wot-security - closes #269 w3c/wot-profile#421, by @benfrancis.
-
-
2 pull requests merged.
-
Switch reference from wot-security-best-practices to wot-security - closes #269 w3c/wot-profile#421.
-
Explicity state contentType of application/json in Forms - closes #141 w3c/wot-profile#419.
-
-
2 pull requests received 7 new comments.
-
Explicity state contentType of application/json in Forms - closes #141 w3c/wot-profile#419 (4 comments by @benfrancis, @danielpeintner)
-
Switch reference from wot-security-best-practices to wot-security - closes #269 w3c/wot-profile#421 (3 comments by @benfrancis, @egekorkan)
-
w3c/wot-binding-registry
-
1 issue opened.
-
First Draft Registry Plan w3c/wot-binding-registry#12, by @egekorkan.
-
-
1 issue closed.
-
Copying over the Requirements.md content to index.html w3c/wot-binding-registry#8.
-
-
1 issue received 1 new comment.
-
Copying over the Requirements.md content to index.html w3c/wot-binding-registry#8 (1 comment by @egekorkan)
-
-
3 pull requests opened.
-
Adding abstract w3c/wot-binding-registry#11, by @egekorkan.
-
refactor: initial setup taking over content from MD w3c/wot-binding-registry#10, by @danielpeintner.
-
Clean-up .gitignore w3c/wot-binding-registry#9, by @danielpeintner.
-
-
3 pull requests merged.
-
Adding abstract w3c/wot-binding-registry#11.
-
refactor: initial setup taking over content from MD w3c/wot-binding-registry#10.
-
Clean-up .gitignore w3c/wot-binding-registry#9.
-
-
3 pull requests received 4 new comments.
-
refactor: initial setup taking over content from MD w3c/wot-binding-registry#10 (2 comments by @danielpeintner, @egekorkan)
-
w3c/wot-binding-templates
-
1 issue received 3 new comments.
-
OPC UA Binding Document Feedback from Ege Korkan w3c/wot-binding-templates#426 (3 comments by @egekorkan, @sebastiankb)
-
-
2 pull requests opened.
-
fix: BACnet JSON Schema syntax corrections w3c/wot-binding-templates#429, by @fennibay.
-
fix: model BACnet relinquish explicitly w3c/wot-binding-templates#428, by @fennibay.
-
-
1 pull request received 7 new comments.
-
fix: model BACnet relinquish explicitly w3c/wot-binding-templates#428 (7 comments by @danielpeintner, @egekorkan, @fennibay)
-
w3c/wot-scripting-api
-
1 issue closed.
-
Extended return type of invokeAction() w3c/wot-scripting-api#555.
-
-
2 pull requests opened.
-
Update README.md with tag for subfolder w3c/wot-scripting-api#577, by @danielpeintner.
-
increase scripting version to SNAPSHOT.31 w3c/wot-scripting-api#576, by @danielpeintner.
-
-
3 pull requests merged.
-
increase scripting version to SNAPSHOT.31 w3c/wot-scripting-api#576.
-
Update README with tag w3c/wot-scripting-api#575.
-
Extended return type of invokeAction() w3c/wot-scripting-api#561.
-
-
3 pull requests received 9 new comments.
-
Extended return type of invokeAction() w3c/wot-scripting-api#561 (7 comments by @danielpeintner, @JKRhb, @relu91)
-
Past meetings
-
18 meetings.
Participants
-
1 chair stepped down.
-
Michael McCool stepped down as a chair.
-
GitHub
w3c/wot-profile
-
1 issue opened.
-
Structure of section 8.4 HTTP Webhook Profile Protocol Binding is broken w3c/wot-profile#420, by @benfrancis.
-
-
7 issues closed.
-
Webhook unsubscribe operation in diagram doesn't match protocol binding w3c/wot-profile#254.
-
Create "Structure of this document" section (1.5) w3c/wot-profile#239.
-
Rework profile overview figure w3c/wot-profile#237.
-
Security Schemes are too loose w3c/wot-profile#221.
-
Image update for HTTP baseline profile w3c/wot-profile#211.
-
Specific constraints on OAuth need to be defined w3c/wot-profile#41.
-
Recommended Security w3c/wot-profile#6.
-
-
15 issues received 22 new comments.
-
Webhook unsubscribe operation in diagram doesn't match protocol binding w3c/wot-profile#254 (2 comments by @benfrancis)
-
Consider adding an .editorconfig file for consistent formatting w3c/wot-profile#253 (2 comments by @benfrancis)
-
Action Improvements: identity /owner of an action invocation w3c/wot-profile#105 (1 comment by @benfrancis)
-
1 pull request opened.
-
Explicity state contentType of application/json in Forms - closes #141 w3c/wot-profile#419, by @benfrancis.
-
-
2 pull requests closed.
-
Cloud Events Message Format w3c/wot-profile#330.
-
WIP: Common constraints - identifiers w3c/wot-profile#271.
-
-
6 pull requests received 11 new comments.
-
WIP: Provide example in the new introduction section w3c/wot-profile#334 (6 comments by @benfrancis, @sebastiankb)
-
Explicity state contentType of application/json in Forms - closes #141 w3c/wot-profile#419 (1 comment by @benfrancis)
-
A start on use cases and requirements for Profiles 2.0 w3c/wot-profile#417 (1 comment by @benfrancis)
-
WIP: Allow auto security scheme for other permitted security schemes w3c/wot-profile#314 (1 comment by @benfrancis)
-
w3c/wot-thing-description
-
6 issues opened.
-
Consider specifying an algorithm for selecting a Form w3c/wot-thing-description#2106, by @benfrancis.
-
TMs with Initial Connection for expressing common deployments w3c/wot-thing-description#2104, by @egekorkan.
-
Clarifications for Initial Connection w3c/wot-thing-description#2102, by @egekorkan.
-
Review all uses of the terms "Binding", "Protocol Binding" and "Binding Template" w3c/wot-thing-description#2101, by @benfrancis.
-
Collecting Input for the Manageable Affordances Analysis w3c/wot-thing-description#2099, by @egekorkan.
-
Use Case vs User Story Discussion w3c/wot-thing-description#2098, by @egekorkan.
-
-
4 issues received 6 new comments.
-
Use Case vs User Story Discussion w3c/wot-thing-description#2098 (2 comments by @benfrancis, @egekorkan)
-
Consider specifying an algorithm for selecting a Form w3c/wot-thing-description#2106 (1 comment by @danielpeintner)
-
3 pull requests opened.
-
Add HTTP to the data mapping analysis w3c/wot-thing-description#2105, by @lu-zero.
-
Initial Connection Improvements w3c/wot-thing-description#2103, by @egekorkan.
-
Project management update w3c/wot-thing-description#2100, by @egekorkan.
-
-
1 pull request merged.
-
Analysis Document Template w3c/wot-thing-description#2097.
-
-
3 pull requests received 3 new comments.
w3c/wot-binding-registry
-
3 issues opened.
-
Copying over the Requirements.md content to index.html w3c/wot-binding-registry#8, by @egekorkan.
-
Writing the Abstract and Informative Introduction w3c/wot-binding-registry#7, by @egekorkan.
-
Creating Editor's Draft HTML w3c/wot-binding-registry#5, by @egekorkan.
-
-
2 issues closed.
-
Creating Editor's Draft HTML w3c/wot-binding-registry#5.
-
Adding Terminology for the Registry Mechanism w3c/wot-binding-registry#2.
-
-
2 pull requests opened.
-
Initial Document w3c/wot-binding-registry#6, by @egekorkan.
-
Terminology Improvements w3c/wot-binding-registry#4, by @egekorkan.
-
-
2 pull requests merged.
-
Initial Document w3c/wot-binding-registry#6.
-
Terminology Improvements w3c/wot-binding-registry#4.
-
-
2 pull requests received 9 new comments.
w3c/wot-architecture
-
1 issue opened.
-
Change definitions of "Binding Template" and "Protocol Binding" and add definition for "Binding Instance" w3c/wot-architecture#948, by @benfrancis.
-
w3c/wot-binding-templates
-
1 issue closed.
-
"Protocol Binding" vs. "Binding Template" w3c/wot-binding-templates#143.
-
-
1 issue received 2 new comments.
-
1 pull request merged.
-
Delete registry-requirements.md w3c/wot-binding-templates#427.
-
w3c/wot-scripting-api
-
2 issues closed.
-
Sync schemas is now outdated w3c/wot-scripting-api#571.
-
Looking into Deno w3c/wot-scripting-api#570.
-
-
6 issues received 6 new comments.
-
w3c/wot-scripting-api#572 (1 comment by @danielpeintner)
-
w3c/wot-scripting-api#573 (1 comment by @danielpeintner)
-
-
2 pull requests opened.
-
Update README with tag w3c/wot-scripting-api#575, by @danielpeintner.
-
refactor: update version for TS 12-March-2025 w3c/wot-scripting-api#574, by @danielpeintner.
-
-
1 pull request merged.
-
refactor: update version for TS 12-March-2025 w3c/wot-scripting-api#574.
-
-
1 pull request received 1 new comment.
Past meetings
-
20 meetings.
GitHub
w3c/wot-thing-description
-
3 issues opened.
-
Grouping of Things Work Item w3c/wot-thing-description#2095, by @egekorkan.
-
Collecting Analysis on Data Mapping w3c/wot-thing-description#2094, by @egekorkan.
-
Common Definitions Expansion Algorithm w3c/wot-thing-description#2093, by @egekorkan.
-
-
2 issues closed.
-
Moving ahead with the initial connection feature w3c/wot-thing-description#2089.
-
Type and schema definitions for @context are too loose w3c/wot-thing-description#2022.
-
-
3 issues received 4 new comments.
-
Moving ahead with the initial connection feature w3c/wot-thing-description#2089 (1 comment by @egekorkan)
-
4 pull requests opened.
-
Analysis Document Template w3c/wot-thing-description#2097, by @egekorkan.
-
Manageable Affordances Analysis w3c/wot-thing-description#2096, by @egekorkan.
-
fix: minor typos w3c/wot-thing-description#2092, by @danielpeintner.
-
Publication Folder Sync for Schemas w3c/wot-thing-description#2091, by @egekorkan.
-
-
5 pull requests merged.
-
Manageable Affordances Analysis w3c/wot-thing-description#2096.
-
fix: minor typos w3c/wot-thing-description#2092.
-
Initial Connection Restructuring w3c/wot-thing-description#2090.
-
Publication Folder Sync for Schemas w3c/wot-thing-description#2091.
-
fix: align JSON Schema with JSON-LD @context format w3c/wot-thing-description#2080.
-
-
6 pull requests received 25 new comments.
-
Initial Connection Restructuring w3c/wot-thing-description#2090 (8 comments by @egekorkan, @lu-zero, @TallTed)
-
Publication Folder Sync for Schemas w3c/wot-thing-description#2091 (4 comments by @danielpeintner, @egekorkan, @TallTed)
-
fix: align JSON Schema with JSON-LD @context format w3c/wot-thing-description#2080 (2 comments by @egekorkan)
-
w3c/wot-binding-templates
-
2 issues opened.
-
OPC UA Binding Document Feedback from Ege Korkan w3c/wot-binding-templates#426, by @egekorkan.
-
OPC UA binding Template Review from Kazeem w3c/wot-binding-templates#425, by @Kaz040.
-
-
4 issues closed.
-
Where should the registry live? w3c/wot-binding-templates#421.
-
Protocol Binding for OPC-UA w3c/wot-binding-templates#42.
-
Required Machine Readable Documents for Registry Entries w3c/wot-binding-templates#404.
-
Versioning of Registry Entries w3c/wot-binding-templates#400.
-
-
5 issues received 16 new comments.
-
"Protocol Binding" vs. "Binding Template" w3c/wot-binding-templates#143 (10 comments by @benfrancis, @egekorkan, @sebastiankb, @TallTed)
-
Required Machine Readable Documents for Registry Entries w3c/wot-binding-templates#404 (1 comment by @egekorkan)
-
-
3 pull requests opened.
-
Delete registry-requirements.md w3c/wot-binding-templates#427, by @egekorkan.
-
Machine readable documents requirements w3c/wot-binding-templates#424, by @egekorkan.
-
Registry versioning requirements w3c/wot-binding-templates#423, by @egekorkan.
-
-
2 pull requests merged.
-
Machine readable documents requirements w3c/wot-binding-templates#424.
-
Registry versioning requirements w3c/wot-binding-templates#423.
-
-
2 pull requests received 7 new comments.
-
Machine readable documents requirements w3c/wot-binding-templates#424 (5 comments by @egekorkan, @TallTed)
-
w3c/wot-binding-registry
-
1 pull request opened.
-
Moving the requirements document w3c/wot-binding-registry#1, by @egekorkan.
-
-
1 pull request merged.
-
Moving the requirements document w3c/wot-binding-registry#1.
-
w3c/wot-scripting-api
-
1 issue opened.
-
Sync schemas is now outdated w3c/wot-scripting-api#571, by @relu91.
-
-
1 issue received 2 new comments.
w3c/wot-resources
-
1 pull request opened.
-
Syncing Schemas w3c/wot-resources#24, by @egekorkan.
-
-
1 pull request merged.
-
Syncing Schemas w3c/wot-resources#24.
-
Past meetings
-
21 meetings.
Participants
-
1 participant joined.
-
Luca Barbato (W3C Invited Experts) joined.
-
-
1 participant left.
-
Salvador González Gerpe (Universidad Politécnica de Madrid) left.
-
GitHub
w3c/wot-binding-templates
-
3 issues opened.
-
Add link to OPC UA Binding document w3c/wot-binding-templates#422, by @danielpeintner.
-
Where should the registry live? w3c/wot-binding-templates#421, by @egekorkan.
-
Creating Use Cases from Bindings w3c/wot-binding-templates#417, by @egekorkan.
-
-
4 issues closed.
-
Registry Inclusiveness w3c/wot-binding-templates#393.
-
Handling Bindings that depend on other bindings w3c/wot-binding-templates#401.
-
Add unique labels to registry mechanism items w3c/wot-binding-templates#410.
-
Stable/Current Status Requirements w3c/wot-binding-templates#403.
-
-
5 issues received 9 new comments.
-
Required Machine Readable Documents for Registry Entries w3c/wot-binding-templates#404 (2 comments by @egekorkan)
-
Handling Bindings that depend on other bindings w3c/wot-binding-templates#401 (2 comments by @egekorkan)
-
3 pull requests opened.
-
Binding Dependencies w3c/wot-binding-templates#420, by @egekorkan.
-
Unique Item Names w3c/wot-binding-templates#419, by @egekorkan.
-
Profinet Binding Addition to Readme w3c/wot-binding-templates#416, by @egekorkan.
-
-
6 pull requests merged.
-
Binding Dependencies w3c/wot-binding-templates#420.
-
Unique Item Names w3c/wot-binding-templates#419.
-
Requiring implementation experience for bindings w3c/wot-binding-templates#414.
-
Profinet Binding Addition to Readme w3c/wot-binding-templates#416.
-
Review Comments for Registry Mechanism w3c/wot-binding-templates#413.
-
creating a PROFINET binding template file w3c/wot-binding-templates#351.
-
-
4 pull requests received 8 new comments.
-
Requiring implementation experience for bindings w3c/wot-binding-templates#414 (2 comments by @egekorkan)
w3c/wot-thing-description
-
5 issues opened.
-
Moving ahead with the initial connection feature w3c/wot-thing-description#2089, by @egekorkan.
-
Proposal: Move Forms out of the TD (TD2.0) w3c/wot-thing-description#2087, by @hspaay.
-
Add a schema for unobserve/observe property w3c/wot-thing-description#2085, by @relu91.
-
Better description for EventAffordance `subscription` and `cancellation` w3c/wot-thing-description#2084, by @relu91.
-
Identifying Types of Changes for Categorization w3c/wot-thing-description#2083, by @egekorkan.
-
-
2 issues closed.
-
json-schema vocabulary: which version? w3c/wot-thing-description#1241.
-
Webhook Event Example code examples miss "required": […] w3c/wot-thing-description#2067.
-
-
8 issues received 30 new comments.
-
Proposal: Move Forms out of the TD (TD2.0) w3c/wot-thing-description#2087 (15 comments by @benfrancis, @danielpeintner, @egekorkan, @hspaay, @lu-zero, @relu91, @sebastiankb)
-
Add a schema for unobserve/observe property w3c/wot-thing-description#2085 (3 comments by @egekorkan, @relu91)
-
Discard `controlledBy` for TD 2.0? w3c/wot-thing-description#2073 (3 comments by @lu-zero, @mahdanoura, @relu91)
-
Reconsider `id` being optional w3c/wot-thing-description#2054 (3 comments by @benfrancis, @JKRhb, @lu-zero)
-
json-ld playground Error thing definition ontology/schema w3c/wot-thing-description#2071 (2 comments by @mahdanoura, @unit9a)
-
json-schema vocabulary: which version? w3c/wot-thing-description#1241 (2 comments by @egekorkan, @ioggstream)
-
Using the New Use Case Template and Gathering Experience w3c/wot-thing-description#2039 (1 comment by @egekorkan)
-
Better description for EventAffordance `subscription` and `cancellation` w3c/wot-thing-description#2084 (1 comment by @egekorkan)
-
-
4 pull requests opened.
-
Initial Connection Restructuring w3c/wot-thing-description#2090, by @egekorkan.
-
Test PR on JSON Schema w3c/wot-thing-description#2088, by @egekorkan.
-
PR Template: Remove Checkboxes w3c/wot-thing-description#2086, by @egekorkan.
-
Profinet Binding Addition to the table w3c/wot-thing-description#2082, by @egekorkan.
-
-
5 pull requests merged.
-
Binding Mechanism Improvements w3c/wot-thing-description#2048.
-
PR Template: Remove Checkboxes w3c/wot-thing-description#2086.
-
Profinet Binding Addition to the table w3c/wot-thing-description#2082.
-
Initial Connection Feature Description w3c/wot-thing-description#2058.
-
add required property key to example w3c/wot-thing-description#2077.
-
-
1 pull request closed.
-
Test PR on JSON Schema w3c/wot-thing-description#2088.
-
-
7 pull requests received 16 new comments.
-
fix: align JSON Schema with JSON-LD @context format w3c/wot-thing-description#2080 (7 comments by @egekorkan, @TallTed)
-
Make `contentType` optional in `ExpectedResponse` and `AdditionalExpectedResponse` classes w3c/wot-thing-description#2081 (3 comments by @benfrancis, @egekorkan)
-
w3c/wot-scripting-api
-
3 issues opened.
-
Looking into Deno w3c/wot-scripting-api#570, by @danielpeintner.
-
Subscription stop misses InteractionInput ? w3c/wot-scripting-api#569, by @danielpeintner.
-
Unclear what `data` is for in `InteractionOptions` w3c/wot-scripting-api#568, by @danielpeintner.
-
-
4 issues received 5 new comments.
-
Subscription stop misses InteractionInput ? w3c/wot-scripting-api#569 (1 comment by @danielpeintner)
-
1 pull request received 1 new comment.
w3c/wot-binding-registry
-
1 issue opened.
-
Adding Terminology for the Registry Mechanism w3c/wot-binding-registry#2, by @egekorkan.
-
Past meetings
-
20 meetings.
Participants
-
1 participant left.
-
Luca Barbato (W3C Invited Experts) left.
-
-
1 organization left.
-
Luminem left.
-
GitHub
w3c/wot-scripting-api
-
2 issues opened.
-
[TD] Consequence of `contentType` being optional w3c/wot-scripting-api#567, by @danielpeintner.
-
[Use-case] WoT in the Browser w3c/wot-scripting-api#566, by @danielpeintner.
-
-
2 issues received 6 new comments.
-
[Use-case] WoT in the Browser w3c/wot-scripting-api#566 (5 comments by @benfrancis, @relu91, @zolkis)
-
-
1 pull request received 4 new comments.
-
Extended return type of invokeAction() w3c/wot-scripting-api#561 (4 comments by @danielpeintner, @relu91, @zolkis)
-
w3c/wot-binding-registry
-
1 issue opened.
-
Defining Test Report Content w3c/wot-binding-registry#3, by @egekorkan.
-
w3c/wot-binding-templates
-
13 issues opened.
-
Add unique labels to registry mechanism items w3c/wot-binding-templates#410, by @egekorkan.
-
Protocol-specific Discovery Mechanisms in Binding Documents w3c/wot-binding-templates#409, by @JKRhb.
-
Suggestion: Define a `@type` of `ActionID` in the HTTP Binding Template to help describe action queues w3c/wot-binding-templates#408, by @benfrancis.
-
How complicated can default mappings be? w3c/wot-binding-templates#407, by @benfrancis.
-
OPC UA URI Scheme w3c/wot-binding-templates#406, by @egekorkan.
-
Required Machine Readable Documents for Registry Entries w3c/wot-binding-templates#404, by @egekorkan.
-
Stable/Current Status Requirements w3c/wot-binding-templates#403, by @egekorkan.
-
Summary Document Requirements w3c/wot-binding-templates#402, by @egekorkan.
-
Handling Bindings that depend on other bindings w3c/wot-binding-templates#401, by @egekorkan.
-
Versioning of Registry Entries w3c/wot-binding-templates#400, by @egekorkan.
-
Registry Entry Field on "Access and Usage Rights" w3c/wot-binding-templates#399, by @egekorkan.
-
Handling Binding Submissions for Existing Bindings w3c/wot-binding-templates#398, by @egekorkan.
-
Template JSON Schema has required term on wrong level w3c/wot-binding-templates#397, by @danielpeintner.
-
-
4 issues closed.
-
Summary Document Requirements w3c/wot-binding-templates#402.
-
Handling Binding Submissions for Existing Bindings w3c/wot-binding-templates#398.
-
Registry Entry Field on "Access and Usage Rights" w3c/wot-binding-templates#399.
-
Template JSON Schema has required term on wrong level w3c/wot-binding-templates#397.
-
-
11 issues received 29 new comments.
-
Required Machine Readable Documents for Registry Entries w3c/wot-binding-templates#404 (4 comments by @egekorkan, @JKRhb)
-
Handling Binding Submissions for Existing Bindings w3c/wot-binding-templates#398 (4 comments by @benfrancis, @egekorkan)
-
Protocol-specific Discovery Mechanisms in Binding Documents w3c/wot-binding-templates#409 (3 comments by @benfrancis, @egekorkan, @JKRhb)
-
How complicated can default mappings be? w3c/wot-binding-templates#407 (3 comments by @benfrancis, @egekorkan)
-
Registry Entry Field on "Access and Usage Rights" w3c/wot-binding-templates#399 (2 comments by @egekorkan)
-
Add unique labels to registry mechanism items w3c/wot-binding-templates#410 (1 comment by @danielpeintner)
-
Suggestion: Define a `@type` of `ActionID` in the HTTP Binding Template to help describe action queues w3c/wot-binding-templates#408 (1 comment by @benfrancis)
-
8 pull requests opened.
-
Requiring implementation experience for bindings w3c/wot-binding-templates#414, by @relu91.
-
Review Comments for Registry Mechanism w3c/wot-binding-templates#413, by @egekorkan.
-
Adding Summary Document Requirements w3c/wot-binding-templates#412, by @egekorkan.
-
Handling Conflicting Submissions w3c/wot-binding-templates#411, by @egekorkan.
-
Moving required term one level up w3c/wot-binding-templates#405, by @egekorkan.
-
chore: normalize line endings w3c/wot-binding-templates#396, by @fennibay.
-
Fix line endings w3c/wot-binding-templates#395, by @ektrah.
-
chore: downgrade JSON Schema from 2019-09 to draft-07 w3c/wot-binding-templates#394, by @fennibay.
-
-
7 pull requests merged.
-
Adding Summary Document Requirements w3c/wot-binding-templates#412.
-
Handling Conflicting Submissions w3c/wot-binding-templates#411.
-
Registry Requirements Update w3c/wot-binding-templates#378.
-
feat: introduce cov:confirmable vocabulary term w3c/wot-binding-templates#392.
-
Fix line endings w3c/wot-binding-templates#395.
-
chore: downgrade JSON Schema from 2019-09 to draft-07 w3c/wot-binding-templates#394.
-
Moving required term one level up w3c/wot-binding-templates#405.
-
-
1 pull request closed.
-
chore: normalize line endings w3c/wot-binding-templates#396.
-
-
11 pull requests received 64 new comments.
-
chore: downgrade JSON Schema from 2019-09 to draft-07 w3c/wot-binding-templates#394 (15 comments by @danielpeintner, @egekorkan, @ektrah, @fennibay, @JKRhb)
-
Requiring implementation experience for bindings w3c/wot-binding-templates#414 (12 comments by @danielpeintner, @egekorkan, @TallTed)
-
Registry Requirements Update w3c/wot-binding-templates#378 (12 comments by @danielpeintner, @egekorkan, @JKRhb, @TallTed)
-
Adding Summary Document Requirements w3c/wot-binding-templates#412 (6 comments by @danielpeintner, @egekorkan, @TallTed)
-
feat: introduce cov:confirmable vocabulary term w3c/wot-binding-templates#392 (5 comments by @egekorkan, @ektrah, @JKRhb)
-
Handling Conflicting Submissions w3c/wot-binding-templates#411 (4 comments by @danielpeintner, @egekorkan, @TallTed)
-
creating a PROFINET binding template file w3c/wot-binding-templates#351 (2 comments by @egekorkan, @Kaz040)
-
Review Comments for Registry Mechanism w3c/wot-binding-templates#413 (2 comments by @danielpeintner, @TallTed)
-
w3c/wot-thing-description
-
2 issues opened.
-
PR Template not working w3c/wot-thing-description#2078, by @egekorkan.
-
Discard `controlledBy` for TD 2.0? w3c/wot-thing-description#2073, by @sebastiankb.
-
-
2 issues closed.
-
Typo: approache -> the … approach w3c/wot-thing-description#2066.
-
PR Template not working w3c/wot-thing-description#2078.
-
-
8 issues received 21 new comments.
-
Specify the result of `queryaction` operation w3c/wot-thing-description#2068 (10 comments by @benfrancis, @lu-zero, @TallTed)
-
Reconsider `id` being optional w3c/wot-thing-description#2054 (4 comments by @benfrancis, @egekorkan, @lu-zero)
-
Supporting complex/structured types in simple protocols w3c/wot-thing-description#1936 (1 comment by @sebastiankb)
-
Unexplained value transformation or inconsistency: metric_value and metric w3c/wot-thing-description#2038 (1 comment by @egekorkan)
-
Type and schema definitions for @context are too loose w3c/wot-thing-description#2022 (1 comment by @egekorkan)
-
-
7 pull requests opened.
-
Make `contentType` optional in `ExpectedResponse` and `AdditionalExpectedResponse` classes w3c/wot-thing-description#2081, by @JKRhb.
-
fix: align JSON Schema with JSON-LD @context format w3c/wot-thing-description#2080, by @JKRhb.
-
Moving the PR template one level up w3c/wot-thing-description#2079, by @egekorkan.
-
add required property key to example w3c/wot-thing-description#2077, by @egekorkan.
-
Modifying Prettify to make a Dry run and check for Fork w3c/wot-thing-description#2076, by @egekorkan.
-
Giving prettier job more permissions w3c/wot-thing-description#2075, by @egekorkan.
-
Testing Daniel PR w3c/wot-thing-description#2074, by @egekorkan.
-
-
4 pull requests merged.
-
fix: typo approache -> the … approach w3c/wot-thing-description#2070.
-
Moving the PR template one level up w3c/wot-thing-description#2079.
-
Modifying Prettify to make a Dry run and check for Fork w3c/wot-thing-description#2076.
-
Giving prettier job more permissions w3c/wot-thing-description#2075.
-
-
1 pull request closed.
-
Testing Daniel PR w3c/wot-thing-description#2074.
-
-
7 pull requests received 34 new comments.
-
Make `contentType` optional in `ExpectedResponse` and `AdditionalExpectedResponse` classes w3c/wot-thing-description#2081 (11 comments by @benfrancis, @egekorkan, @JKRhb)
-
fix: align JSON Schema with JSON-LD @context format w3c/wot-thing-description#2080 (7 comments by @danielpeintner, @egekorkan, @JKRhb)
-
add required property key to example w3c/wot-thing-description#2077 (6 comments by @danielpeintner, @egekorkan)
-
fix: typo approache -> the … approach w3c/wot-thing-description#2070 (4 comments by @danielpeintner, @egekorkan)
-
w3c/wot-discovery
-
2 issues opened.
-
CoAP-based TDD API w3c/wot-discovery#551, by @JKRhb.
-
Is the `@type` `ThingID` defined anywhere? w3c/wot-discovery#550, by @benfrancis.
-
-
1 issue received 1 new comment.
Past meetings
-
23 meetings.
GitHub
w3c/wot-thing-description
-
4 issues opened.
-
New JSON Schema Version will ban unknown words w3c/wot-thing-description#2072, by @egekorkan.
-
json-ld playground Error thing definition ontology/schema w3c/wot-thing-description#2071, by @unit9a.
-
URI Scheme Decision w3c/wot-thing-description#2069, by @egekorkan.
-
Specify the result of `queryaction` operation w3c/wot-thing-description#2068, by @relu91.
-
-
4 issues received 20 new comments.
-
New JSON Schema Version will ban unknown words w3c/wot-thing-description#2072 (6 comments by @benfrancis, @danielpeintner, @egekorkan, @gregsdennis, @lu-zero)
-
Specify the result of `queryaction` operation w3c/wot-thing-description#2068 (6 comments by @benfrancis, @egekorkan, @relu91, @zolkis)
-
JSON Schema breaking changes in Drafts 2019 and newer w3c/wot-thing-description#1017 (5 comments by @egekorkan, @fennibay, @handrews)
-
json-ld playground Error thing definition ontology/schema w3c/wot-thing-description#2071 (3 comments by @egekorkan, @unit9a)
-
-
1 pull request opened.
-
fix: typo approache -> the … approach w3c/wot-thing-description#2070, by @danielpeintner.
-
-
2 pull requests merged.
-
Add bacnet alarms management as an input for manageable affordances w3c/wot-thing-description#2055.
-
Some relevant information for manageable affordances work item w3c/wot-thing-description#2056.
-
-
1 pull request received 5 new comments.
-
fix: typo approache -> the … approach w3c/wot-thing-description#2070 (5 comments by @danielpeintner, @egekorkan, @TallTed)
-
w3c/wot-binding-templates
-
1 issue opened.
-
Registry Inclusiveness w3c/wot-binding-templates#393, by @egekorkan.
-
-
1 issue closed.
-
Motivate why bacv:usesService term is needed w3c/wot-binding-templates#385.
-
-
3 issues received 12 new comments.
-
Registry Inclusiveness w3c/wot-binding-templates#393 (9 comments by @benfrancis, @egekorkan, @lu-zero, @mmccool, @relu91, @sebastiankb)
-
Motivate why bacv:usesService term is needed w3c/wot-binding-templates#385 (1 comment by @egekorkan)
-
-
2 pull requests received 14 new comments.
-
feat: introduce cov:confirmable vocabulary term w3c/wot-binding-templates#392 (6 comments by @danielpeintner, @egekorkan, @TallTed)
w3c/wot-scripting-api
-
1 issue opened.
-
Align with Coding Conventions document w3c/wot-scripting-api#565, by @relu91.
-
-
1 issue received 1 new comment.
-
Should we refactor `getThingDescription` to a JS getter? w3c/wot-scripting-api#507 (1 comment by @relu91)
-
-
1 pull request received 7 new comments.
-
Extended return type of invokeAction() w3c/wot-scripting-api#561 (7 comments by @danielpeintner, @relu91, @TallTed, @zolkis)
-