Web of Things Working Group - Activity in 2020
No matches.
Participants
-
1 participant joined.
-
Thomas Brezinski (Indeed) joined.
-
-
1 organization joined.
-
Indeed joined.
-
GitHub
w3c/wot-discovery
-
5 issues received 15 new comments.
-
Need information model for directory w3c/wot-discovery#98 (6 comments by @AndreaCimminoArriaga, @farshidtz, @mmccool)
-
Canonicalization requirements for directories w3c/wot-discovery#104 (3 comments by @AndreaCimminoArriaga, @mmccool)
-
-
2 pull requests opened.
-
Add and refer to a single validation section w3c/wot-discovery#106, by @farshidtz.
-
Updated document with federation w3c/wot-discovery#105, by @AndreaCimminoArriaga.
-
-
2 pull requests received 4 new comments.
-
Updated document with federation w3c/wot-discovery#105 (3 comments by @AndreaCimminoArriaga, @mmccool)
-
Minor fixes in search sections of directory TD w3c/wot-discovery#103 (1 comment by @AndreaCimminoArriaga)
-
w3c/wot-thing-description
-
6 issues opened.
-
Introduce a canonical TD format w3c/wot-thing-description#1023, by @mlagally.
-
From today's TD call: w3c/wot-thing-description#1022, by @sebastiankb.
-
Which is better to actuate devices, invoking ACTION or writing PROPERTY? w3c/wot-thing-description#1020, by @mryuichi.
-
Required restriction for the hierarchical defined properties w3c/wot-thing-description#1019, by @mryuichi.
-
JSON Schema breaking changes in Drafts 2019 and newer w3c/wot-thing-description#1017, by @egekorkan.
-
Example 38 is not rendered w3c/wot-thing-description#1016, by @egekorkan.
-
-
9 issues closed.
-
Complex IOT device w3c/wot-thing-description#952.
-
Rename "Thing Template" to "Thing Model" w3c/wot-thing-description#930.
-
DataSchema "Only applicable to..." w3c/wot-thing-description#1007.
-
From today's TD call: w3c/wot-thing-description#1022.
-
[question] Meaning of htv:headers in forms w3c/wot-thing-description#991.
-
Example 38 is not rendered w3c/wot-thing-description#1016.
-
[Minor] description of observable should mention unobserveproperty (besides observeproperty) w3c/wot-thing-description#950.
-
Default value for op in Property Affordance should be linked to read/writeOnly w3c/wot-thing-description#1003.
-
There is twice "5.4" in the title of Section 5.4 "Default Value Definition" w3c/wot-thing-description#1011.
-
-
35 issues received 76 new comments.
-
Modeling enumeration values semantically w3c/wot-thing-description#997 (9 comments by @egekorkan, @fennibay, @mcr, @mjkoster, @sebastiankb)
-
Error conditions for form requests w3c/wot-thing-description#303 (9 comments by @benfrancis, @egekorkan, @sebastiankb)
-
[vocabulary] Consider adding keyword to describe synchronous actions w3c/wot-thing-description#890 (6 comments by @ashimura, @egekorkan, @sebastiankb)
-
Problems translating TDs from JSON-LD 1.1 to RDF and back w3c/wot-thing-description#1015 (5 comments by @AndreaCimminoArriaga, @danielpeintner, @mmccool)
-
Introduce a canonical TD format w3c/wot-thing-description#1023 (4 comments by @danielpeintner, @sebastiankb)
-
[security] API key and PSK security schemes are not referenced or explained w3c/wot-thing-description#998 (4 comments by @egekorkan, @mmccool)
-
Which is better to actuate devices, invoking ACTION or writing PROPERTY? w3c/wot-thing-description#1020 (3 comments by @benfrancis, @danielpeintner, @sebastiankb)
-
Allow array for response in From class? w3c/wot-thing-description#617 (3 comments by @egekorkan, @sebastiankb)
-
Automate running TD rendering script w3c/wot-thing-description#883 (2 comments by @danielpeintner, @sebastiankb)
-
[DataSchema] maximum and minimum are not clear about inclusiveness w3c/wot-thing-description#1010 (2 comments by @danielpeintner, @sebastiankb)
-
TD Producer field in TD (similar to Server header field in HTTP) w3c/wot-thing-description#774 (2 comments by @sebastiankb)
-
[question] Meaning of htv:headers in forms w3c/wot-thing-description#991 (2 comments by @sebastiankb)
-
PropertyAffordance is missing InteractionAffordance properties in the published JSON-LD context w3c/wot-thing-description#894 (1 comment by @sebastiankb)
-
No mechanism to indicate the "desired" form entry w3c/wot-thing-description#877 (1 comment by @sebastiankb)
-
Add a component mechanism to support mashups w3c/wot-thing-description#958 (1 comment by @sebastiankb)
-
Required restriction for the hierarchical defined properties w3c/wot-thing-description#1019 (1 comment by @sebastiankb)
-
extend op options with observeallproperties and observemultipleproperties w3c/wot-thing-description#800 (1 comment by @sebastiankb)
-
No examples for observeproperty and unobserveproperty w3c/wot-thing-description#969 (1 comment by @sebastiankb)
-
Review resurrected Cert, Public, and PoP SecuritySchemes w3c/wot-thing-description#965 (1 comment by @mmccool)
-
JSON Schema breaking changes in Drafts 2019 and newer w3c/wot-thing-description#1017 (1 comment by @sebastiankb)
-
[question] Why is title or description necessary when titles or descriptions are present? w3c/wot-thing-description#985 (1 comment by @egekorkan)
-
There is twice "5.4" in the title of Section 5.4 "Default Value Definition" w3c/wot-thing-description#1011 (1 comment by @sebastiankb)
-
Reconsider security & securityDefinitions being mandatory w3c/wot-thing-description#757 (1 comment by @sebastiankb)
-
Single 'base' field but multiple 'forms' elements w3c/wot-thing-description#803 (1 comment by @sebastiankb)
-
Add overridable global default value(s) for mediaType w3c/wot-thing-description#204 (1 comment by @sebastiankb)
-
[ThingModel] Example of Oracle's device model (Festo) w3c/wot-thing-description#999 (1 comment by @sebastiankb)
-
-
4 pull requests opened.
-
Introduce observeAllProperties and unobserveAllProperties w3c/wot-thing-description#1025, by @sebastiankb.
-
Topics around Thing Model w3c/wot-thing-description#1024, by @sebastiankb.
-
Issue 1010 w3c/wot-thing-description#1021, by @danielpeintner.
-
fix: code brackets w3c/wot-thing-description#1018, by @danielpeintner.
-
-
4 pull requests merged.
-
fix: code brackets w3c/wot-thing-description#1018.
-
fix #950 w3c/wot-thing-description#995.
-
fix #1003 w3c/wot-thing-description#1012.
-
fix: duplicate section w3c/wot-thing-description#1013.
-
-
5 pull requests received 6 new comments.
-
Introduce observeAllProperties and unobserveAllProperties w3c/wot-thing-description#1025 (1 comment by @egekorkan)
w3c/wot-profile
-
4 issues opened.
-
Allow multiple forms for interaction affordances in Core Profile w3c/wot-profile#60, by @benfrancis.
-
Consider creating a Constrained Profile w3c/wot-profile#59, by @benfrancis.
-
Align single element array handling with the TD w3c/wot-profile#58, by @mlagally.
-
Encrypted TDs w3c/wot-profile#56, by @mlagally.
-
-
3 issues received 6 new comments.
-
Reduce or remove the constraints in section 7.2 Baseline Information Model w3c/wot-profile#10 (1 comment by @benfrancis)
-
1 pull request opened.
-
Canonical representation 2 w3c/wot-profile#57, by @mlagally.
-
w3c/wot-architecture
-
2 issues opened.
-
New terminology for the Binding document? w3c/wot-architecture#575, by @mlagally.
-
Terminology: thing description fragments w3c/wot-architecture#574, by @mlagally.
-
-
11 issues closed.
-
Post CR editorial fixes w3c/wot-architecture#350.
-
Update TD reference to PR version of TD spec w3c/wot-architecture#352.
-
validate all references w3c/wot-architecture#200.
-
Update change log to match PR transition request w3c/wot-architecture#416.
-
Possible typos w3c/wot-architecture#420.
-
Editorial issues on PR w3c/wot-architecture#437.
-
Improve integration of use case section and structure of normative sections w3c/wot-architecture#446.
-
Define terminology Thing Template w3c/wot-architecture#454.
-
Requirement document for Agriculture w3c/wot-architecture#479.
-
Consider moving requirements section to "Use Case" document w3c/wot-architecture#565.
-
Move REQUIREMENTS folder to WoT Usecases TF w3c/wot-architecture#568.
-
-
1 issue reopened.
-
Identity and Identifier should be defined terminology w3c/wot-architecture#571, by @mlagally.
-
-
15 issues received 27 new comments.
-
Terminology: thing description fragments w3c/wot-architecture#574 (5 comments by @danielpeintner, @mlagally, @relu91, @zolkis)
-
Identity and Identifier should be defined terminology w3c/wot-architecture#571 (4 comments by @mlagally, @OliverPfaff)
-
Property affordances claimed to always readable w3c/wot-architecture#412 (2 comments by @hspaay, @mlagally)
-
Lifecycle should have a balanced discussion of ownership w3c/wot-architecture#570 (2 comments by @mlagally, @OliverPfaff)
-
New terminology for the Binding document? w3c/wot-architecture#575 (2 comments by @egekorkan, @mlagally)
-
Improve integration of use case section and structure of normative sections w3c/wot-architecture#446 (1 comment by @mlagally)
-
Consider moving requirements section to "Use Case" document w3c/wot-architecture#565 (1 comment by @mlagally)
-
-
1 pull request opened.
-
moving requirements to use case reop w3c/wot-architecture#573, by @mlagally.
-
-
1 pull request merged.
-
moving requirements to use case reop w3c/wot-architecture#573.
-
w3c/wotwg
-
1 issue closed.
-
Update WG page with latest publications w3c/wotwg#9.
-
w3c/wot-security
-
1 issue opened.
-
Promoting an approach where every thing is a server is a security nightmare w3c/wot-security#197, by @hspaay.
-
-
1 issue received 1 new comment.
w3c/wot-binding-templates
-
2 issues opened.
-
writePropery and readProperty confusion w3c/wot-binding-templates#107, by @hspaay.
-
Header Information in Response or Request w3c/wot-binding-templates#106, by @sebastiankb.
-
-
1 issue closed.
-
Errors in examples w3c/wot-binding-templates#94.
-
-
1 issue received 3 new comments.
-
writePropery and readProperty confusion w3c/wot-binding-templates#107 (3 comments by @egekorkan, @hspaay)
-
-
1 pull request opened.
-
fix examples w3c/wot-binding-templates#105, by @egekorkan.
-
-
1 pull request merged.
-
fix examples w3c/wot-binding-templates#105.
-
-
2 pull requests received 3 new comments.
w3c/wot-scripting-api
-
1 issue opened.
-
Provide Task force description w3c/wot-scripting-api#285, by @danielpeintner.
-
-
2 issues received 3 new comments.
TR publications
-
5 documents published.
-
Web of Things (WoT) Architecture 1.1 published as a First Public Working Draft. History of Web of Things (WoT) Architecture 1.1
-
Web of Things (WoT) Discovery published as a First Public Working Draft. History of Web of Things (WoT) Discovery
-
Web of Things (WoT) Profile published as a First Public Working Draft. History of Web of Things (WoT) Profile
-
Web of Things (WoT) Thing Description 1.1 published as a First Public Working Draft. History of Web of Things (WoT) Thing Description 1.1
-
Web of Things (WoT) Scripting API published as a Note. History of Web of Things (WoT) Scripting API
-
GitHub
w3c/wot-discovery
-
12 issues opened.
-
Canonicalization requirements for directories w3c/wot-discovery#104, by @mmccool.
-
Review discovery support in wot-py w3c/wot-discovery#101, by @mmccool.
-
Capture requirements for JSONPath w3c/wot-discovery#100, by @mmccool.
-
Define requirements and add section for validation w3c/wot-discovery#99, by @mmccool.
-
Need information model for directory w3c/wot-discovery#98, by @mmccool.
-
How do we handle federation in SPARQL queries w3c/wot-discovery#97, by @mmccool.
-
Should security be mandatory on directories for WoT Discovery? w3c/wot-discovery#96, by @mmccool.
-
Use case: retrieving static metadata from a set of TDs w3c/wot-discovery#95, by @mmccool.
-
Consider making PATCH optional and/or removing/deferring it w3c/wot-discovery#94, by @mmccool.
-
Consider using "JSON Lines" for large TDs w3c/wot-discovery#93, by @mmccool.
-
Add evaluation features for advanced directory services w3c/wot-discovery#92, by @mmccool.
-
Clarify relationship of discovery to lifecycle w3c/wot-discovery#91, by @mmccool.
-
-
2 issues closed.
-
Consider making PATCH optional and/or removing/deferring it w3c/wot-discovery#94.
-
Feedback to Editor's Draft 29 September 2020 w3c/wot-discovery#77.
-
-
19 issues received 42 new comments.
-
Consider using "JSON Lines" for large TDs w3c/wot-discovery#93 (8 comments by @danielpeintner, @egekorkan, @farshidtz, @mmccool, @relu91)
-
Canonicalization requirements for directories w3c/wot-discovery#104 (4 comments by @AndreaCimminoArriaga, @farshidtz, @mmccool)
-
Consider making PATCH optional and/or removing/deferring it w3c/wot-discovery#94 (4 comments by @farshidtz, @mmccool, @relu91)
-
Define requirements and add section for validation w3c/wot-discovery#99 (4 comments by @egekorkan, @mmccool, @relu91)
-
Should security be mandatory on directories for WoT Discovery? w3c/wot-discovery#96 (2 comments by @benfrancis, @mmccool)
-
Clarify relationship of discovery to lifecycle w3c/wot-discovery#91 (2 comments by @mmccool, @zolkis)
-
"Thing description" for Directory should be a "Thing Model" w3c/wot-discovery#86 (2 comments by @benfrancis, @mmccool)
-
How to deal with JSON-LD fragments in query responses w3c/wot-discovery#63 (1 comment by @farshidtz)
-
Handle huge set of Thing Descriptions (pagination, streaming, etc.) w3c/wot-discovery#16 (1 comment by @mmccool)
-
Add evaluation features for advanced directory services w3c/wot-discovery#92 (1 comment by @mmccool)
-
-
2 pull requests opened.
-
Minor fixes in search sections of directory TD w3c/wot-discovery#103, by @farshidtz.
-
JSON Merge Patch (RFC7396) for partial update w3c/wot-discovery#102, by @farshidtz.
-
-
3 pull requests merged.
-
JSON Merge Patch (RFC7396) for partial update w3c/wot-discovery#102.
-
Minor fixes in search sections of directory TD w3c/wot-discovery#103.
-
Improve optional sparql assertion w3c/wot-discovery#89.
-
-
1 pull request received 1 new comment.
w3c/wot-thing-description
-
14 issues opened.
-
Problems translating TDs from JSON-LD 1.1 to RDF and back w3c/wot-thing-description#1015, by @AndreaCimminoArriaga.
-
alignment.ttl file should add the semantics of the external classes reused, at least the "type" w3c/wot-thing-description#1014, by @gatemezing.
-
There is twice "5.4" in the title of Section 5.4 "Default Value Definition" w3c/wot-thing-description#1011, by @sebastiankb.
-
[DataSchema] maximum and minimum are not clear about inclusiveness w3c/wot-thing-description#1010, by @egekorkan.
-
DataSchema "Only applicable to..." w3c/wot-thing-description#1007, by @egekorkan.
-
Undefined behavior for writeOnly and readOnly w3c/wot-thing-description#1005, by @relu91.
-
JSON Schema not rendered w3c/wot-thing-description#1004, by @relu91.
-
Default value for op in Property Affordance should be linked to read/writeOnly w3c/wot-thing-description#1003, by @egekorkan.
-
Add "reliability" to the TD w3c/wot-thing-description#1002, by @mlagally.
-
Add "precision" to data schema w3c/wot-thing-description#1001, by @mlagally.
-
[ThingModel] Example of Eclipse Vorto model w3c/wot-thing-description#1000, by @kolotu.
-
[ThingModel] Example of Oracle's device model (Festo) w3c/wot-thing-description#999, by @mlagally.
-
[security] API key and PSK security schemes are not referenced or explained w3c/wot-thing-description#998, by @egekorkan.
-
Modeling enumeration values semantically w3c/wot-thing-description#997, by @fennibay.
-
-
4 issues closed.
-
URL shortname convention for TD 1.1 w3c/wot-thing-description#990.
-
Review - Thing Description 1.1 version w3c/wot-thing-description#987.
-
JSON Schema not rendered w3c/wot-thing-description#1004.
-
Are there any OpenAPI <-> TD converters? w3c/wot-thing-description#992.
-
-
25 issues received 67 new comments.
-
Add "reliability" to the TD w3c/wot-thing-description#1002 (12 comments by @danielpeintner, @egekorkan, @mlagally, @relu91, @sebastiankb)
-
Undefined behavior for writeOnly and readOnly w3c/wot-thing-description#1005 (6 comments by @egekorkan, @handrews, @sebastiankb)
-
[ThingModel] Example of Oracle's device model (Festo) w3c/wot-thing-description#999 (6 comments by @danielpeintner, @mlagally, @sebastiankb)
-
[ThingModel] Example of Eclipse Vorto model w3c/wot-thing-description#1000 (5 comments by @egekorkan, @kolotu, @sebastiankb)
-
Modeling enumeration values semantically w3c/wot-thing-description#997 (5 comments by @egekorkan, @fennibay)
-
[question] Meaning of htv:headers in forms w3c/wot-thing-description#991 (4 comments by @egekorkan, @sebastiankb)
-
Default value for op in Property Affordance should be linked to read/writeOnly w3c/wot-thing-description#1003 (4 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
[multiLang] Should titles and descriptions be present in the TD after language negotation w3c/wot-thing-description#959 (3 comments by @egekorkan, @gatemezing, @sebastiankb)
-
[question] Why is title or description necessary when titles or descriptions are present? w3c/wot-thing-description#985 (2 comments by @egekorkan, @sebastiankb)
-
[DataSchema] maximum and minimum are not clear about inclusiveness w3c/wot-thing-description#1010 (2 comments by @danielpeintner, @egekorkan)
-
DataSchema "Only applicable to..." w3c/wot-thing-description#1007 (2 comments by @egekorkan, @sebastiankb)
-
Managing Dynamically Created Resources in TDs w3c/wot-thing-description#899 (2 comments by @egekorkan, @takuki)
-
Add a component mechanism to support mashups w3c/wot-thing-description#958 (2 comments by @benfrancis, @takuki)
-
[vocabulary] Consider adding keyword to describe synchronous actions w3c/wot-thing-description#890 (1 comment by @egekorkan)
-
[question] How to describe Philips Hue security scheme w3c/wot-thing-description#923 (1 comment by @egekorkan)
-
Evaluate geolocation terms in TD model (input from Profile TF) w3c/wot-thing-description#941 (1 comment by @mmccool)
-
There is twice "5.4" in the title of Section 5.4 "Default Value Definition" w3c/wot-thing-description#1011 (1 comment by @danielpeintner)
-
Introducing assumptions about TD instances that have no IP addresses w3c/wot-thing-description#977 (1 comment by @sebastiankb)
-
"MultiLanguage Map" is used without definition w3c/wot-thing-description#983 (1 comment by @sebastiankb)
-
Are there any OpenAPI <-> TD converters? w3c/wot-thing-description#992 (1 comment by @FilipBrinkmann)
-
-
6 pull requests opened.
-
fix: duplicate section w3c/wot-thing-description#1013, by @danielpeintner.
-
fix #1003 w3c/wot-thing-description#1012, by @egekorkan.
-
fix duplicate definition of dfn-td-processor w3c/wot-thing-description#1009, by @ashimura.
-
add new data schema terms w3c/wot-thing-description#1008, by @egekorkan.
-
feat: include JSON schema to index.html w3c/wot-thing-description#1006, by @danielpeintner.
-
add "(WoT)" to the title w3c/wot-thing-description#996, by @ashimura.
-
-
4 pull requests merged.
-
fix duplicate definition of dfn-td-processor w3c/wot-thing-description#1009.
-
feat: include JSON schema to index.html w3c/wot-thing-description#1006.
-
add new data schema terms w3c/wot-thing-description#1008.
-
add "(WoT)" to the title w3c/wot-thing-description#996.
-
-
2 pull requests received 6 new comments.
-
feat: include JSON schema to index.html w3c/wot-thing-description#1006 (4 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
w3c/wot-scripting-api
-
4 issues opened.
-
Bring back updated links to whatwg w3c/wot-scripting-api#284, by @danielpeintner.
-
Improve the Form selection algorithms w3c/wot-scripting-api#282, by @zolkis.
-
Remove ConsumedThing inheritance in ExposedThing w3c/wot-scripting-api#281, by @zolkis.
-
Make property change notifications explicit in ExposedThing w3c/wot-scripting-api#280, by @zolkis.
-
-
3 issues closed.
-
Remove ConsumedThing inheritance in ExposedThing w3c/wot-scripting-api#281.
-
Make property change notifications explicit in ExposedThing w3c/wot-scripting-api#280.
-
Improve the Form selection algorithms w3c/wot-scripting-api#282.
-
-
6 issues received 12 new comments.
-
Improve the Form selection algorithms w3c/wot-scripting-api#282 (4 comments by @danielpeintner, @relu91, @zolkis)
-
Consider to add one or more validation steps to assure TD consistency w3c/wot-scripting-api#238 (2 comments by @egekorkan, @relu91)
-
Remove ConsumedThing inheritance in ExposedThing w3c/wot-scripting-api#281 (2 comments by @danielpeintner, @zolkis)
-
Make property change notifications explicit in ExposedThing w3c/wot-scripting-api#280 (1 comment by @zolkis)
-
-
1 pull request opened.
-
Fix #280 and 281: add emitPropertyChange(), remove ConsumedThing inheritance w3c/wot-scripting-api#283, by @zolkis.
-
-
1 pull request merged.
-
Fix #280 and 281: add emitPropertyChange(), remove ConsumedThing inheritance w3c/wot-scripting-api#283.
-
-
1 pull request received 11 new comments.
-
Fix #280 and 281: add emitPropertyChange(), remove ConsumedThing inheritance w3c/wot-scripting-api#283 (11 comments by @danielpeintner, @zolkis)
-
w3c/wot-architecture
-
6 issues opened.
-
System should be defined terminology w3c/wot-architecture#572, by @mmccool.
-
Identity and Identifier should be defined terminology w3c/wot-architecture#571, by @mmccool.
-
Lifecycle should have a balanced discussion of ownership w3c/wot-architecture#570, by @mmccool.
-
Boiler plate proposal w3c/wot-architecture#569, by @mlagally.
-
Move REQUIREMENTS folder to WoT Usecases TF w3c/wot-architecture#568, by @mlagally.
-
Consider moving requirements section to "Use Case" document w3c/wot-architecture#565, by @mlagally.
-
-
3 issues received 3 new comments.
-
Identity and Identifier should be defined terminology w3c/wot-architecture#571 (1 comment by @OliverPfaff)
-
Lifecycle should have a balanced discussion of ownership w3c/wot-architecture#570 (1 comment by @OliverPfaff)
-
Consider moving requirements section to "Use Case" document w3c/wot-architecture#565 (1 comment by @mlagally)
-
-
2 pull requests opened.
-
issue 565: removing requirements section w3c/wot-architecture#567, by @mlagally.
-
use 2020 patent policy w3c/wot-architecture#566, by @ashimura.
-
-
4 pull requests merged.
-
Add candidates for UI link types w3c/wot-architecture#562.
-
Connected building requirements w3c/wot-architecture#528.
-
issue 565: removing requirements section w3c/wot-architecture#567.
-
use 2020 patent policy w3c/wot-architecture#566.
-
-
3 pull requests received 3 new comments.
w3c/wot-security
-
4 issues opened.
-
Update security and privacy considerations in Discovery w3c/wot-security#196, by @mmccool.
-
Consider specific security guidance for particular contexts w3c/wot-security#195, by @mmccool.
-
Provide guidance on use of OAuth 2 flows w3c/wot-security#194, by @mmccool.
-
Consider making order meaningful in "oneOf" combo scheme w3c/wot-security#193, by @mmccool.
-
-
10 issues received 15 new comments.
-
Review updated Lifecycle in Architecture w3c/wot-security#192 (4 comments by @mmccool, @OliverPfaff)
-
Consider specific security guidance for particular contexts w3c/wot-security#195 (1 comment by @mmccool)
-
Review security architecture of Mozilla WebThings gateway w3c/wot-security#188 (1 comment by @mmccool)
-
Consider making order meaningful in "oneOf" combo scheme w3c/wot-security#193 (1 comment by @mmccool)
-
w3c/wotwg
-
1 issue opened.
-
Update WG page with latest publications w3c/wotwg#9, by @danielpeintner.
-
w3c/wot-profile
-
1 issue opened.
-
Canonical Representation / Signing requirements w3c/wot-profile#55, by @mlagally.
-
-
1 issue received 4 new comments.
-
Canonical Representation / Signing requirements w3c/wot-profile#55 (4 comments by @mlagally, @mmccool)
-
-
2 pull requests opened.
-
Update index.html w3c/wot-profile#54, by @mlagally.
-
make the title "Web of Things (WoT) Profile" w3c/wot-profile#53, by @ashimura.
-
-
2 pull requests merged.
-
WIP: Canonical json representation w3c/wot-profile#51.
-
make the title "Web of Things (WoT) Profile" w3c/wot-profile#53.
-
-
1 pull request closed.
-
Update index.html w3c/wot-profile#54.
-
-
3 pull requests received 3 new comments.
w3c/wot-binding-templates
-
1 issue received 2 new comments.
-
How to propose a new binding + TD example w3c/wot-binding-templates#103 (2 comments by @egekorkan, @sebastiankb)
-
-
1 pull request opened.
-
WIP: Guideline to create a new protocol binding w3c/wot-binding-templates#104, by @sebastiankb.
-
-
1 pull request received 5 new comments.
-
WIP: Guideline to create a new protocol binding w3c/wot-binding-templates#104 (5 comments by @egekorkan, @relu91)
-
Participants
-
1 participant joined.
-
Jack Dickinson (Conexxus) joined.
-
-
1 participant left.
-
峰 高 (360) left.
-
-
1 organization left.
-
360 left.
-
GitHub
w3c/wot-thing-description
-
11 issues opened.
-
hasInputSchema (and probably others) compacts "type" as "@type", breaking json-schema compatibility w3c/wot-thing-description#994, by @RoboPhred.
-
Are there any OpenAPI <-> TD converters? w3c/wot-thing-description#992, by @FilipBrinkmann.
-
[question] Meaning of htv:headers in forms w3c/wot-thing-description#991, by @egekorkan.
-
URL shortname convention for TD 1.1 w3c/wot-thing-description#990, by @sebastiankb.
-
[json-schema][json-ld] Json Schema RDF context fails to round trip w3c/wot-thing-description#988, by @RoboPhred.
-
Review - Thing Description 1.1 version w3c/wot-thing-description#987, by @danielpeintner.
-
[question] Why is title or description necessary when titles or descriptions are present? w3c/wot-thing-description#985, by @egekorkan.
-
"MultiLanguage Map" is used without definition w3c/wot-thing-description#983, by @takuki.
-
Definition of contentEncoding should be of type xsd:string w3c/wot-thing-description#980, by @takuki.
-
Add hint that relation type values are collected. w3c/wot-thing-description#978, by @sebastiankb.
-
Introducing assumptions about TD instances that have no IP addresses w3c/wot-thing-description#977, by @sebastiankb.
-
-
1 issue closed.
-
[JSON-LD] Compacting property affordance for json-schema compatibility does not support the `type` property w3c/wot-thing-description#967.
-
-
22 issues received 85 new comments.
-
[question] Why is title or description necessary when titles or descriptions are present? w3c/wot-thing-description#985 (15 comments by @Citrullin, @danielpeintner, @egekorkan, @sebastiankb)
-
Introducing assumptions about TD instances that have no IP addresses w3c/wot-thing-description#977 (14 comments by @Citrullin, @danielpeintner, @egekorkan, @relu91, @sebastiankb, @zolkis)
-
Are there any OpenAPI <-> TD converters? w3c/wot-thing-description#992 (8 comments by @adriankast, @egekorkan, @relu91)
-
JSON Schema for Thing Model w3c/wot-thing-description#972 (7 comments by @danielpeintner, @egekorkan, @handrews)
-
[JSON-LD] Compacting property affordance for json-schema compatibility does not support the `type` property w3c/wot-thing-description#967 (5 comments by @BigBlueHat, @pchampin, @RoboPhred)
-
[json-schema][json-ld] Json Schema RDF context fails to round trip w3c/wot-thing-description#988 (4 comments by @pchampin, @RoboPhred, @vcharpenay)
-
Add 'minLength' and 'maxLength' to StringSchema w3c/wot-thing-description#889 (4 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
URL shortname convention for TD 1.1 w3c/wot-thing-description#990 (3 comments by @danielpeintner, @egekorkan, @mmccool)
-
Missing triple resolution in JSON-LD playground for properties forms w3c/wot-thing-description#905 (3 comments by @davidlehn, @gkellogg, @vcharpenay)
-
Automate running TD rendering script w3c/wot-thing-description#883 (3 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
TDT shall allow to define placeholders w3c/wot-thing-description#897 (2 comments by @egekorkan, @fennibay)
-
We need an OAuth2 example for TD 1.1 w3c/wot-thing-description#948 (2 comments by @egekorkan, @relu91)
-
base direction considerations [I18N] w3c/wot-thing-description#643 (2 comments by @iherman, @sebastiankb)
-
Thing Description versioning and Scripting API w3c/wot-thing-description#932 (1 comment by @sebastiankb)
-
JSON-LD 1.0 will be republished as superseded version w3c/wot-thing-description#970 (1 comment by @iherman)
-
"MultiLanguage Map" is used without definition w3c/wot-thing-description#983 (1 comment by @danielpeintner)
-
Add "multipleOf" term to NumberSchema and IntegerSchema w3c/wot-thing-description#841 (1 comment by @sebastiankb)
-
Clarify the usage of base64 encodings in DataSchema/ContentType w3c/wot-thing-description#912 (1 comment by @sebastiankb)
-
Unsubscribing and unobserving are not in default values w3c/wot-thing-description#957 (1 comment by @sebastiankb)
-
Add hint that relation type values are collected. w3c/wot-thing-description#978 (1 comment by @sebastiankb)
-
-
10 pull requests opened.
-
introduce working namespaces in TD 1.1 w3c/wot-thing-description#993, by @sebastiankb.
-
update abstract + fix bug + #987 w3c/wot-thing-description#989, by @sebastiankb.
-
fix: typos w3c/wot-thing-description#986, by @danielpeintner.
-
Repaired most respec errors. w3c/wot-thing-description#984, by @takuki.
-
Added Change Log section. w3c/wot-thing-description#982, by @takuki.
-
some hints for TD diagrams w3c/wot-thing-description#981, by @sebastiankb.
-
update author list + document status w3c/wot-thing-description#979, by @sebastiankb.
-
feat: add content type tables with data schema w3c/wot-thing-description#976, by @danielpeintner.
-
add notes and update as decided in https://github.com/w3c/wot-thing-d… w3c/wot-thing-description#975, by @danielpeintner.
-
9 pull requests merged.
-
introduce working namespaces in TD 1.1 w3c/wot-thing-description#993.
-
update abstract + fix bug + #987 w3c/wot-thing-description#989.
-
fix: typos w3c/wot-thing-description#986.
-
Repaired most respec errors. w3c/wot-thing-description#984.
-
Added Change Log section. w3c/wot-thing-description#982.
-
some hints for TD diagrams w3c/wot-thing-description#981.
-
update author list + document status w3c/wot-thing-description#979.
-
feat: add content type tables with data schema w3c/wot-thing-description#976.
-
add notes and update as decided in https://github.com/w3c/wot-thing-d… w3c/wot-thing-description#975.
-
-
2 pull requests closed.
-
[WIP] feat: add content type tables with data schema w3c/wot-thing-description#869.
-
docs: add unsubscribeevent to default list and add notes w3c/wot-thing-description#960.
-
-
8 pull requests received 21 new comments.
-
update abstract + fix bug + #987 w3c/wot-thing-description#989 (9 comments by @danielpeintner, @sebastiankb)
-
introduce working namespaces in TD 1.1 w3c/wot-thing-description#993 (5 comments by @danielpeintner, @mlagally, @sebastiankb)
-
docs: add unsubscribeevent to default list and add notes w3c/wot-thing-description#960 (2 comments by @danielpeintner)
-
[WIP] feat: add content type tables with data schema w3c/wot-thing-description#869 (1 comment by @danielpeintner)
-
feat: add content type tables with data schema w3c/wot-thing-description#976 (1 comment by @danielpeintner)
-
w3c/wot-discovery
-
10 issues opened.
-
Expand the Direct method w3c/wot-discovery#90, by @relu91.
-
Richer diff model for update notifications w3c/wot-discovery#87, by @farshidtz.
-
"Thing description" for Directory should be a "Thing Model" w3c/wot-discovery#86, by @mmccool.
-
Consider using QUIC and/or HTTP/3 w3c/wot-discovery#84, by @mmccool.
-
Consider using VC w3c/wot-discovery#83, by @mmccool.
-
Creation of OpenAPI spec from Directory TD w3c/wot-discovery#82, by @farshidtz.
-
Create semantic query examples w3c/wot-discovery#81, by @mmccool.
-
Define time-based query filter w3c/wot-discovery#80, by @mmccool.
-
Define Geospatial query filter for Directories w3c/wot-discovery#79, by @mmccool.
-
Feedback to Editor's Draft 29 September 2020 w3c/wot-discovery#77, by @wiresio.
-
-
1 issue closed.
-
Define plugfest 2020.10 scenarios for semantic discovery w3c/wot-discovery#55.
-
-
10 issues received 26 new comments.
-
"Thing description" for Directory should be a "Thing Model" w3c/wot-discovery#86 (6 comments by @egekorkan, @farshidtz, @mmccool, @relu91, @zolkis)
-
Feedback to Editor's Draft 29 September 2020 w3c/wot-discovery#77 (4 comments by @farshidtz, @mmccool, @wiresio)
-
Define plugfest 2020.10 scenarios for semantic discovery w3c/wot-discovery#55 (3 comments by @mmccool)
-
Should Directories store TD Models as well as Instances? w3c/wot-discovery#58 (1 comment by @relu91)
-
Handle huge set of Thing Descriptions (pagination, streaming, etc.) w3c/wot-discovery#16 (1 comment by @mmccool)
-
-
4 pull requests opened.
-
Improve optional sparql assertion w3c/wot-discovery#89, by @farshidtz.
-
Fix respec errors due to references w3c/wot-discovery#88, by @mmccool.
-
Pre-FPWD Fixes w3c/wot-discovery#85, by @farshidtz.
-
Remove duplicate events section and TD file w3c/wot-discovery#78, by @farshidtz.
-
-
3 pull requests merged.
-
Fix respec errors due to references w3c/wot-discovery#88.
-
Pre-FPWD Fixes w3c/wot-discovery#85.
-
Remove duplicate events section and TD file w3c/wot-discovery#78.
-
w3c/wot-scripting-api
-
4 issues opened.
-
Update references to upcoming documents w3c/wot-scripting-api#278, by @danielpeintner.
-
Modify the Changes section for publication w3c/wot-scripting-api#275, by @zolkis.
-
Add 'once' to subscription options w3c/wot-scripting-api#274, by @danielpeintner.
-
WoT network interface definition missing in Architecture w3c/wot-scripting-api#273, by @relu91.
-
-
8 issues closed.
-
Potentially insufficient error handling for emitEvent() w3c/wot-scripting-api#256.
-
WoT network interface definition missing in Architecture w3c/wot-scripting-api#273.
-
Update "Changes" section for upcoming publication w3c/wot-scripting-api#223.
-
Some intial read-through comments w3c/wot-scripting-api#230.
-
Modify the Changes section for publication w3c/wot-scripting-api#275.
-
Event handling - Issue 235 from w3c/wot w3c/wot-scripting-api#228.
-
Should we use affordance instead of interaction? w3c/wot-scripting-api#241.
-
Stale TD mitigation outdated (?) w3c/wot-scripting-api#252.
-
-
10 issues received 29 new comments.
-
Update references to upcoming documents w3c/wot-scripting-api#278 (8 comments by @danielpeintner, @relu91, @zolkis)
-
Potentially insufficient error handling for emitEvent() w3c/wot-scripting-api#256 (3 comments by @danielpeintner, @relu91)
-
WoT network interface definition missing in Architecture w3c/wot-scripting-api#273 (3 comments by @danielpeintner, @relu91, @zolkis)
-
Discovery of exposed Things on the same runtime - Issue 233 from w3c/wot w3c/wot-scripting-api#227 (1 comment by @danielpeintner)
-
-
7 pull requests opened.
-
Fix WoT network interface definition w3c/wot-scripting-api#279, by @relu91.
-
Fixes #223: update Changes section w3c/wot-scripting-api#277, by @zolkis.
-
update WOT references to latest publication URL/date w3c/wot-scripting-api#276, by @danielpeintner.
-
Add editor's note about WoT interactions vs Interaction Affordances w3c/wot-scripting-api#272, by @relu91.
-
feat: remove section about "Stale TD Security Risk" w3c/wot-scripting-api#271, by @danielpeintner.
-
Add 'once' to subscription options w3c/wot-scripting-api#270, by @zolkis.
-
Improve error handling for ExposedThing:emitEvent() w3c/wot-scripting-api#269, by @zolkis.
-
-
6 pull requests merged.
-
Fix WoT network interface definition w3c/wot-scripting-api#279.
-
Fixes #223: update Changes section w3c/wot-scripting-api#277.
-
update WOT references to latest publication URL/date w3c/wot-scripting-api#276.
-
Add editor's note about WoT interactions vs Interaction Affordances w3c/wot-scripting-api#272.
-
feat: remove section about "Stale TD Security Risk" w3c/wot-scripting-api#271.
-
Improve error handling for ExposedThing:emitEvent() w3c/wot-scripting-api#269.
-
-
2 pull requests closed.
-
Add 'once' to subscription options w3c/wot-scripting-api#270.
-
Review Comments w3c/wot-scripting-api#247.
-
-
4 pull requests received 16 new comments.
-
Add 'once' to subscription options w3c/wot-scripting-api#270 (9 comments by @danielpeintner, @relu91, @zolkis)
-
Add editor's note about WoT interactions vs Interaction Affordances w3c/wot-scripting-api#272 (4 comments by @relu91, @zolkis)
-
feat: remove section about "Stale TD Security Risk" w3c/wot-scripting-api#271 (2 comments by @ashimura, @danielpeintner)
-
Improve error handling for ExposedThing:emitEvent() w3c/wot-scripting-api#269 (1 comment by @zolkis)
-
w3c/wot-architecture
-
15 issues opened.
-
Lifecycle simplification w3c/wot-architecture#561, by @zolkis.
-
Cross reference FPWD drafts of Discovery, TD, ... w3c/wot-architecture#558, by @mlagally.
-
Introduction for discovery section (9.4) w3c/wot-architecture#557, by @mlagally.
-
Introduction for Profile section (9.2) w3c/wot-architecture#556, by @mlagally.
-
system lifecycle with registration w3c/wot-architecture#555, by @mlagally.
-
Simple system lifecycle w3c/wot-architecture#554, by @mlagally.
-
Information lifecycle w3c/wot-architecture#553, by @mlagally.
-
Lifecycle intro text w3c/wot-architecture#552, by @mlagally.
-
Introduction text to chapter 8.1 w3c/wot-architecture#551, by @mlagally.
-
add link to use case document w3c/wot-architecture#550, by @mlagally.
-
Add a link to the requirements section in the github repo w3c/wot-architecture#549, by @mlagally.
-
Align language: use case vs. application domains w3c/wot-architecture#548, by @mlagally.
-
Carry over terminology from TD spec on Thing Model w3c/wot-architecture#547, by @mlagally.
-
Revise list of co-editors w3c/wot-architecture#546, by @mlagally.
-
Annex A - Changes since last version w3c/wot-architecture#545, by @mlagally.
-
-
5 issues closed.
-
Annex A - Changes since last version w3c/wot-architecture#545.
-
Define lifecycle states + definitions+actors+security data in a table w3c/wot-architecture#476.
-
Carry over terminology from TD spec on Thing Model w3c/wot-architecture#547.
-
Add a link to the requirements section in the github repo w3c/wot-architecture#549.
-
add link to use case document w3c/wot-architecture#550.
-
-
9 issues received 9 new comments.
-
Define lifecycle states + definitions+actors+security data in a table w3c/wot-architecture#476 (1 comment by @mlagally)
-
Carry over terminology from TD spec on Thing Model w3c/wot-architecture#547 (1 comment by @mlagally)
-
Terminology: Consistenly use "Thing Model" across requirements, use cases, specs w3c/wot-architecture#534 (1 comment by @mmccool)
-
7 pull requests opened.
-
reference to 1.1 specs w3c/wot-architecture#564, by @mlagally.
-
Adding changelog w3c/wot-architecture#563, by @mlagally.
-
Add candidates for UI link types w3c/wot-architecture#562, by @relu91.
-
add links to requirements and Use Case repos and docs w3c/wot-architecture#560, by @mmccool.
-
TM definition ... w3c/wot-architecture#559, by @sebastiankb.
-
Update index.html w3c/wot-architecture#544, by @mlagally.
-
Update index.html w3c/wot-architecture#543, by @mlagally.
-
-
8 pull requests merged.
-
reference to 1.1 specs w3c/wot-architecture#564.
-
Adding changelog w3c/wot-architecture#563.
-
add links to requirements and Use Case repos and docs w3c/wot-architecture#560.
-
TM definition ... w3c/wot-architecture#559.
-
WiP: Add device lifecycle section w3c/wot-architecture#539.
-
Add Thing Model text w3c/wot-architecture#540.
-
Clean up old mentions of Thing Templates w3c/wot-architecture#541.
-
Update index.html w3c/wot-architecture#543.
-
-
2 pull requests closed.
-
WIP: Reorder Editors, Fix Respec issues w3c/wot-architecture#542.
-
Update index.html w3c/wot-architecture#544.
-
-
7 pull requests received 18 new comments.
-
Add Thing Model text w3c/wot-architecture#540 (6 comments by @danielpeintner, @mlagally, @sebastiankb)
-
w3c/wot-profile
-
9 issues opened.
-
FPWD Feedback from Cristiano w3c/wot-profile#49, by @relu91.
-
FPWD Feedback by Sebastian w3c/wot-profile#45, by @sebastiankb.
-
FPWD Feedback from Daniel w3c/wot-profile#43, by @danielpeintner.
-
Events are loosely constrained w3c/wot-profile#42, by @egekorkan.
-
Specific constraints on OAuth need to be defined w3c/wot-profile#41, by @mlagally.
-
Action affordance - check input / output type restrictions w3c/wot-profile#40, by @mlagally.
-
Select a specific JSON_SCHEMA version w3c/wot-profile#39, by @mlagally.
-
Enum simple types or permit objects? w3c/wot-profile#38, by @mlagally.
-
FPWD Feedback from Ege Korkan w3c/wot-profile#37, by @egekorkan.
-
-
7 issues received 12 new comments.
-
Term 'Core' may cause a false impression w3c/wot-profile#21 (3 comments by @draggett, @egekorkan, @sebastiankb)
-
Specific constraints on OAuth need to be defined w3c/wot-profile#41 (2 comments by @farshidtz, @relu91)
-
Action affordance - check input / output type restrictions w3c/wot-profile#40 (1 comment by @danielpeintner)
-
-
8 pull requests opened.
-
clarification on protocol bindings w3c/wot-profile#52, by @mlagally.
-
WIP: Canonical json representation w3c/wot-profile#51, by @mlagally.
-
Editors note on events / protocols w3c/wot-profile#50, by @mlagally.
-
Some text improvements w3c/wot-profile#48, by @sebastiankb.
-
Issue 45 - FPWD clarifications on profile name and figures w3c/wot-profile#47, by @mlagally.
-
Fixes to address comments from issue #43 w3c/wot-profile#46, by @mlagally.
-
Editor's note on event section w3c/wot-profile#44, by @mlagally.
-
Editorial fixes for FPWD w3c/wot-profile#36, by @mlagally.
-
-
6 pull requests merged.
-
Editors note on events / protocols w3c/wot-profile#50.
-
clarification on protocol bindings w3c/wot-profile#52.
-
Issue 45 - FPWD clarifications on profile name and figures w3c/wot-profile#47.
-
Editor's note on event section w3c/wot-profile#44.
-
Fixes to address comments from issue #43 w3c/wot-profile#46.
-
Editorial fixes for FPWD w3c/wot-profile#36.
-
-
1 pull request closed.
-
Some text improvements w3c/wot-profile#48.
-
-
7 pull requests received 31 new comments.
-
Issue 45 - FPWD clarifications on profile name and figures w3c/wot-profile#47 (8 comments by @danielpeintner, @egekorkan, @mlagally, @mmccool, @sebastiankb)
Participants
-
2 participants left.
-
Feng Zhang (Huawei) left.
-
Yongjing ZHANG (Huawei) left.
-
GitHub
w3c/wot-thing-description
-
13 issues opened.
-
Render script related issues w3c/wot-thing-description#973, by @danielpeintner.
-
JSON Schema for Thing Model w3c/wot-thing-description#972, by @sebastiankb.
-
How flexible is TD Template instantiation? w3c/wot-thing-description#971, by @devonsparks.
-
JSON-LD 1.0 will be republished as superseded version w3c/wot-thing-description#970, by @sebastiankb.
-
No examples for observeproperty and unobserveproperty w3c/wot-thing-description#969, by @egekorkan.
-
how to find the Form pair for an operation, e.g. the unsubscribe Form for a given subscribe Form w3c/wot-thing-description#968, by @zolkis.
-
[JSON-LD] Compacting property affordance for json-schema compatibility does not support the `type` property w3c/wot-thing-description#967, by @RoboPhred.
-
Create OAuth2 subclasses for each flow w3c/wot-thing-description#966, by @mmccool.
-
Review resurrected Cert, Public, and PoP SecuritySchemes w3c/wot-thing-description#965, by @mmccool.
-
How to model multiple InteractionAffordances of the same nature w3c/wot-thing-description#963, by @fennibay.
-
Use of TD Templates (Thing Models) as abstractions for consumers w3c/wot-thing-description#962, by @fennibay.
-
[multiLang] Should titles and descriptions be present in the TD after language negotation w3c/wot-thing-description#959, by @egekorkan.
-
Add a component mechanism to support mashups w3c/wot-thing-description#958, by @takuki.
-
-
2 issues closed.
-
Clarifying use of multiple security schemes in the security term w3c/wot-thing-description#901.
-
How flexible is TD Template instantiation? w3c/wot-thing-description#971.
-
-
19 issues received 60 new comments.
-
JSON Schema validation issue wr.t. "format": "iri-reference" w3c/wot-thing-description#956 (11 comments by @danielpeintner, @egekorkan, @relu91, @sebastiankb)
-
How to model multiple InteractionAffordances of the same nature w3c/wot-thing-description#963 (10 comments by @danielpeintner, @egekorkan, @fennibay, @relu91, @sebastiankb)
-
Use of TD Templates (Thing Models) as abstractions for consumers w3c/wot-thing-description#962 (8 comments by @fennibay, @relu91, @sebastiankb, @vcharpenay)
-
how to find the Form pair for an operation, e.g. the unsubscribe Form for a given subscribe Form w3c/wot-thing-description#968 (5 comments by @danielpeintner, @egekorkan, @sebastiankb, @zolkis)
-
Unsubscribing and unobserving are not in default values w3c/wot-thing-description#957 (4 comments by @egekorkan, @sebastiankb, @takuki)
-
How flexible is TD Template instantiation? w3c/wot-thing-description#971 (2 comments by @devonsparks, @egekorkan)
-
No examples for observeproperty and unobserveproperty w3c/wot-thing-description#969 (2 comments by @danielpeintner, @sebastiankb)
-
Review resurrected Cert, Public, and PoP SecuritySchemes w3c/wot-thing-description#965 (2 comments by @mmccool, @vcharpenay)
-
Clarify the usage of base64 encodings in DataSchema/ContentType w3c/wot-thing-description#912 (2 comments by @sebastiankb)
-
Add a component mechanism to support mashups w3c/wot-thing-description#958 (2 comments by @sebastiankb)
-
[question] How to describe Philips Hue security scheme w3c/wot-thing-description#923 (1 comment by @egekorkan)
-
Fields for interface generation (e.g. UI, dashboards, IDE): description, icon - Issue 263 from w3c/wot w3c/wot-thing-description#936 (1 comment by @RoboPhred)
-
[multiLang] Should titles and descriptions be present in the TD after language negotation w3c/wot-thing-description#959 (1 comment by @danielpeintner)
-
Evaluate geolocation terms in TD model (input from Profile TF) w3c/wot-thing-description#941 (1 comment by @sebastiankb)
-
[Minor] description of observable should mention unobserveproperty (besides observeproperty) w3c/wot-thing-description#950 (1 comment by @takuki)
-
-
3 pull requests opened.
-
Comment out resurrected public, cert, and pop security schemes w3c/wot-thing-description#974, by @mmccool.
-
geo location metadata w3c/wot-thing-description#961, by @sebastiankb.
-
docs: add unsubscribeevent to default list and add notes w3c/wot-thing-description#960, by @danielpeintner.
-
-
7 pull requests merged.
-
Combination security scheme w3c/wot-thing-description#944.
-
Comment out resurrected public, cert, and pop security schemes w3c/wot-thing-description#974.
-
move Thing Model (former TDT) to a main section + formalize Thing Model + introduce placeholder w3c/wot-thing-description#938.
-
WIP: Introduce minLength, maxLength, multipleOf, contentEncoding and contentMediaType in JSON Schema Ontology w3c/wot-thing-description#896.
-
geo location metadata w3c/wot-thing-description#961.
-
Updating rendering script w3c/wot-thing-description#951.
-
fix: remove wrong "," in example 17 TD snippet w3c/wot-thing-description#914.
-
-
2 pull requests closed.
-
String-meta requirement is not an assertion in TD (Issue #738) w3c/wot-thing-description#768.
-
A requirement (Can ignore BOM) is not an assertion of TD (Issue #721) w3c/wot-thing-description#766.
-
-
13 pull requests received 84 new comments.
-
move Thing Model (former TDT) to a main section + formalize Thing Model + introduce placeholder w3c/wot-thing-description#938 (31 comments by @mlagally, @mmccool, @sebastiankb)
-
geo location metadata w3c/wot-thing-description#961 (13 comments by @relu91, @sebastiankb, @vcharpenay)
-
docs: add unsubscribeevent to default list and add notes w3c/wot-thing-description#960 (11 comments by @danielpeintner, @egekorkan, @relu91, @sebastiankb, @zolkis)
-
WIP: Simplified inline security definitions w3c/wot-thing-description#945 (6 comments by @danielpeintner, @egekorkan, @relu91, @sebastiankb, @takuki)
-
Updating rendering script w3c/wot-thing-description#951 (6 comments by @mmccool, @sebastiankb, @takuki, @vcharpenay)
-
Combination security scheme w3c/wot-thing-description#944 (4 comments by @mmccool, @sebastiankb, @takuki)
-
WIP: swap securtiy and securityDefinition in context file w3c/wot-thing-description#937 (4 comments by @danielpeintner, @mmccool, @sebastiankb)
-
WIP: Add proof and proofChain sections w3c/wot-thing-description#943 (3 comments by @mmccool, @sebastiankb)
-
[WIP] feat: add content type tables with data schema w3c/wot-thing-description#869 (2 comments by @sebastiankb)
-
WIP: Introduce minLength, maxLength, multipleOf, contentEncoding and contentMediaType in JSON Schema Ontology w3c/wot-thing-description#896 (1 comment by @sebastiankb)
-
fix: remove wrong "," in example 17 TD snippet w3c/wot-thing-description#914 (1 comment by @sebastiankb)
-
String-meta requirement is not an assertion in TD (Issue #738) w3c/wot-thing-description#768 (1 comment by @takuki)
-
A requirement (Can ignore BOM) is not an assertion of TD (Issue #721) w3c/wot-thing-description#766 (1 comment by @takuki)
-
w3c/wot-scripting-api
-
1 issue opened.
-
Yet another subscription API w3c/wot-scripting-api#268, by @relu91.
-
-
6 issues closed.
-
[typescript] Use namespace instead of interface for WoT functions w3c/wot-scripting-api#215.
-
Report protocol errors that occur after subscriptions to Events and Property updates w3c/wot-scripting-api#237.
-
Consume algorithm and ConsumeThing ctor should be the same w3c/wot-scripting-api#244.
-
Check supported protocols in the validation algorithm w3c/wot-scripting-api#258.
-
Emit event algorithm should not mention Protocol bindings w3c/wot-scripting-api#251.
-
ReadHandler description is not completely correct w3c/wot-scripting-api#243.
-
-
4 issues received 14 new comments.
-
Check supported protocols in the validation algorithm w3c/wot-scripting-api#258 (7 comments by @danielpeintner, @egekorkan, @relu91, @zolkis)
-
Check data schema algorithm handle string DataSchema new fields. w3c/wot-scripting-api#242 (3 comments by @danielpeintner, @egekorkan, @relu91)
-
Potentially insufficient error handling for emitEvent() w3c/wot-scripting-api#256 (2 comments by @zolkis)
-
-
9 pull requests opened.
-
Fix typescript definition module name w3c/wot-scripting-api#267, by @relu91.
-
Fix ReSpec header with new group field w3c/wot-scripting-api#266, by @zolkis.
-
Proposal for typescript definition file w3c/wot-scripting-api#265, by @relu91.
-
Fix #237 and #256: handle subscription errors w3c/wot-scripting-api#264, by @zolkis.
-
Update README and rationale w3c/wot-scripting-api#263, by @zolkis.
-
Fix #258: improve expose() algorithm w3c/wot-scripting-api#262, by @zolkis.
-
Fix #251: improve the emitEvent() algorithm w3c/wot-scripting-api#261, by @zolkis.
-
Fix #243: make ReadHandler description more concise w3c/wot-scripting-api#260, by @zolkis.
-
Fix #244: ConsumeThing constructor and consume() should do the same w3c/wot-scripting-api#259, by @zolkis.
-
-
10 pull requests merged.
-
Fix typescript definition module name w3c/wot-scripting-api#267.
-
Proposal for typescript definition file w3c/wot-scripting-api#265.
-
Fix ReSpec header with new group field w3c/wot-scripting-api#266.
-
Fix #237 and #256: handle subscription errors w3c/wot-scripting-api#264.
-
Fix #244: ConsumeThing constructor and consume() should do the same w3c/wot-scripting-api#259.
-
Fix #258: improve expose() algorithm w3c/wot-scripting-api#262.
-
Update README and rationale w3c/wot-scripting-api#263.
-
Fix #251: improve the emitEvent() algorithm w3c/wot-scripting-api#261.
-
Fix #243: make ReadHandler description more concise w3c/wot-scripting-api#260.
-
Add more Consume Thing examples w3c/wot-scripting-api#257.
-
-
6 pull requests received 16 new comments.
-
Fix #237 and #256: handle subscription errors w3c/wot-scripting-api#264 (9 comments by @danielpeintner, @relu91, @zolkis)
-
Fix #258: improve expose() algorithm w3c/wot-scripting-api#262 (2 comments by @danielpeintner, @zolkis)
-
w3c/wot-architecture
-
4 issues opened.
-
Lifecycle section needs to take peer to peer discovery into account w3c/wot-architecture#538, by @mlagally.
-
Relationship to Project Connected Home over IP w3c/wot-architecture#536, by @jtc42.
-
Terminology: Consistenly use "Thing Model" across requirements, use cases, specs w3c/wot-architecture#534, by @mlagally.
-
Lifecycle section: Incorporate review feedback from security group w3c/wot-architecture#533, by @mlagally.
-
-
3 issues received 8 new comments.
-
Relationship to Project Connected Home over IP w3c/wot-architecture#536 (5 comments by @egekorkan, @jtc42)
-
Lifecycle section: Incorporate review feedback from security group w3c/wot-architecture#533 (2 comments by @mlagally, @mmccool)
-
-
7 pull requests opened.
-
WIP: Reorder Editors, Fix Respec issues w3c/wot-architecture#542, by @mlagally.
-
Clean up old mentions of Thing Templates w3c/wot-architecture#541, by @mmccool.
-
Add Thing Model text w3c/wot-architecture#540, by @sebastiankb.
-
WiP: Add device lifecycle section w3c/wot-architecture#539, by @zolkis.
-
System lifecycle w3c/wot-architecture#537, by @mlagally.
-
Agriculture (greenhouse horticulture) requirements w3c/wot-architecture#535, by @mryuichi.
-
extended document structure w3c/wot-architecture#532, by @mlagally.
-
-
3 pull requests merged.
-
Agriculture (greenhouse horticulture) requirements w3c/wot-architecture#535.
-
System lifecycle w3c/wot-architecture#537.
-
extended document structure w3c/wot-architecture#532.
-
-
1 pull request closed.
-
Create a new requirements from agriculture w3c/wot-architecture#505.
-
-
5 pull requests received 15 new comments.
-
Agriculture (greenhouse horticulture) requirements w3c/wot-architecture#535 (6 comments by @mlagally)
-
WiP: Add device lifecycle section w3c/wot-architecture#539 (5 comments by @k-toumura, @mmccool, @zolkis)
-
w3c/wot-discovery
-
8 issues opened.
-
Consider use of WoT Directories for discovering compute services and utilities w3c/wot-discovery#72, by @mmccool.
-
Consider using JOSE in Directory service to support object security w3c/wot-discovery#71, by @mmccool.
-
Add sequence diagrams w3c/wot-discovery#69, by @mmccool.
-
Review current directory API proposal for privacy and security w3c/wot-discovery#67, by @mmccool.
-
Consider overlap in DID and Directory functionality w3c/wot-discovery#66, by @mmccool.
-
Create typed links in DID Documents for WoT Directories w3c/wot-discovery#65, by @mmccool.
-
XPath queries of vocabulary using namespaces w3c/wot-discovery#64, by @mmccool.
-
How to deal with JSON-LD fragments in query responses w3c/wot-discovery#63, by @mmccool.
-
-
6 issues received 10 new comments.
-
9 pull requests opened.
-
Add overview figure w3c/wot-discovery#76, by @k-toumura.
-
Mark incomplete sections as editor's notes w3c/wot-discovery#75, by @mmccool.
-
Change hitach.com to hitachi.com w3c/wot-discovery#74, by @Citrullin.
-
[Editorial] remove deprecated configuration options, etc. w3c/wot-discovery#73, by @k-toumura.
-
Editorial fix w3c/wot-discovery#70, by @k-toumura.
-
Add link to latest draft in README w3c/wot-discovery#68, by @farshidtz.
-
Minor fixes in the registration api w3c/wot-discovery#62, by @farshidtz.
-
Add Partial TD term to index.html w3c/wot-discovery#61, by @farshidtz.
-
First draft of introduction mechanisms section w3c/wot-discovery#60, by @k-toumura.
-
-
11 pull requests merged.
-
Add overview figure w3c/wot-discovery#76.
-
Mark incomplete sections as editor's notes w3c/wot-discovery#75.
-
Updated index.html with search w3c/wot-discovery#47.
-
[Editorial] remove deprecated configuration options, etc. w3c/wot-discovery#73.
-
Change hitach.com to hitachi.com w3c/wot-discovery#74.
-
Editorial fix w3c/wot-discovery#70.
-
Add link to latest draft in README w3c/wot-discovery#68.
-
First draft of introduction mechanisms section w3c/wot-discovery#60.
-
Add Partial TD term to index.html w3c/wot-discovery#61.
-
Add description of the notification API w3c/wot-discovery#51.
-
Minor fixes in the registration api w3c/wot-discovery#62.
-
-
5 pull requests received 24 new comments.
-
Updated index.html with search w3c/wot-discovery#47 (14 comments by @AndreaCimminoArriaga, @farshidtz, @mmccool)
-
First draft of introduction mechanisms section w3c/wot-discovery#60 (7 comments by @farshidtz, @k-toumura, @mmccool)
-
w3c/wot-profile
-
2 issues opened.
-
Extension vocabulary for protocols w3c/wot-profile#34, by @mlagally.
-
Add a note about legal compliance w3c/wot-profile#33, by @mlagally.
-
-
2 issues received 3 new comments.
-
1 pull request opened.
-
editorial fixes: reformatting, updated respec reference w3c/wot-profile#35, by @mlagally.
-
-
1 pull request merged.
-
editorial fixes: reformatting, updated respec reference w3c/wot-profile#35.
-
w3c/wot-security
-
10 issues opened.
-
Review updated Lifecycle in Architecture w3c/wot-security#192, by @mmccool.
-
Review security architecture of Home Assistant w3c/wot-security#191, by @relu91.
-
Add explicit discussion of "Trust levels" for different consumers w3c/wot-security#190, by @mmccool.
-
Review security architecture of ThingSpeak hub w3c/wot-security#189, by @mmccool.
-
Review security architecture of Mozilla WebThings gateway w3c/wot-security#188, by @mmccool.
-
Review security architecture of OpenHAB w3c/wot-security#187, by @mmccool.
-
Discuss monitoring requirements w3c/wot-security#186, by @mmccool.
-
Consider how to support object security w3c/wot-security#185, by @mmccool.
-
Review security support in node-wot w3c/wot-security#184, by @mmccool.
-
Consider adding logging/auditing discussion w3c/wot-security#183, by @mmccool.
-
-
5 issues closed.
-
Review Lifecycle model w3c/wot-security#138.
-
Review Conexxus Security and Privacy Threat Model and Implementation Recommendations w3c/wot-security#170.
-
Review oAuth2.0 use case w3c/wot-security#177.
-
Consider OAuth2 "device" flow w3c/wot-security#173.
-
Security review of Lifecycle model and diagram w3c/wot-security#169.
-
-
11 issues received 14 new comments.
-
Review Conexxus Security and Privacy Threat Model and Implementation Recommendations w3c/wot-security#170 (2 comments by @mmccool)
-
Consider moving Thing lifecycle discussion to Architecture w3c/wot-security#65 (1 comment by @mmccool)
-
Add "Security and Privacy Considerations" to all use cases (or requirements) w3c/wot-security#168 (1 comment by @mmccool)
w3c/wot-binding-templates
-
1 issue opened.
-
How to propose a new binding + TD example w3c/wot-binding-templates#103, by @sebastiankb.
-
Participants
-
1 participant joined.
-
Martin Serrano (INSIGHT - The Centre for Data Analytics) joined.
-
-
1 participant left.
-
Hoan Quoc (INSIGHT - The Centre for Data Analytics) left.
-
-
1 organization joined.
-
Kodansha, Publishers, Ltd. joined.
-
GitHub
w3c/wot-thing-description
-
14 issues opened.
-
Unsubscribing and unobserving are not in default values w3c/wot-thing-description#957, by @egekorkan.
-
JSON Schema validation issue wr.t. "format": "iri-reference" w3c/wot-thing-description#956, by @danielpeintner.
-
Better validate "oneOf" choices w3c/wot-thing-description#955, by @mmccool.
-
Better validate/describe "variant records", eg in SecurityScheme and OAuth2 scheme w3c/wot-thing-description#954, by @mmccool.
-
For OAuth2 device flow, should we define a "device authorization" element? w3c/wot-thing-description#953, by @mmccool.
-
Complex IOT device w3c/wot-thing-description#952, by @skavan.
-
[Minor] description of observable should mention unobserveproperty (besides observeproperty) w3c/wot-thing-description#950, by @danielpeintner.
-
We need extension ontology to include implicit and password flows in OAuth2 w3c/wot-thing-description#949, by @sebastiankb.
-
We need an OAuth2 example for TD 1.1 w3c/wot-thing-description#948, by @sebastiankb.
-
New terms hardwareRevision and softwareRevision? w3c/wot-thing-description#947, by @sebastiankb.
-
New term 'serialNumber'? w3c/wot-thing-description#946, by @sebastiankb.
-
Example 35 is incorrect or has inconsistency w3c/wot-thing-description#942, by @egekorkan.
-
Evaluate geolocation terms in TD model (input from Profile TF) w3c/wot-thing-description#941, by @sebastiankb.
-
Add optional proof section to TDs w3c/wot-thing-description#940, by @mmccool.
-
-
1 issue reopened.
-
Editorial issues for consolidated TD REC updates - Errata items w3c/wot-thing-description#920, by @ashimura.
-
-
17 issues received 44 new comments.
-
Evaluate geolocation terms in TD model (input from Profile TF) w3c/wot-thing-description#941 (7 comments by @benfrancis, @egekorkan, @sebastiankb, @takuki)
-
Clarify the usage of base64 encodings in DataSchema/ContentType w3c/wot-thing-description#912 (6 comments by @egekorkan, @relu91, @sebastiankb, @takuki)
-
Clarifying use of multiple security schemes in the security term w3c/wot-thing-description#901 (5 comments by @benfrancis, @egekorkan, @farshidtz, @mmccool)
-
Unsubscribing and unobserving are not in default values w3c/wot-thing-description#957 (4 comments by @danielpeintner, @egekorkan, @zolkis)
-
JSON Schema validation issue wr.t. "format": "iri-reference" w3c/wot-thing-description#956 (4 comments by @danielpeintner, @egekorkan, @handrews)
-
Rename "Thing Template" to "Thing Model" w3c/wot-thing-description#930 (2 comments by @mmccool, @sebastiankb)
-
Example 35 is incorrect or has inconsistency w3c/wot-thing-description#942 (2 comments by @sebastiankb)
-
For OAuth2 device flow, should we define a "device authorization" element? w3c/wot-thing-description#953 (1 comment by @farshidtz)
-
Better validate/describe "variant records", eg in SecurityScheme and OAuth2 scheme w3c/wot-thing-description#954 (1 comment by @relu91)
-
New terms hardwareRevision and softwareRevision? w3c/wot-thing-description#947 (1 comment by @benfrancis)
-
Editorial issues for consolidated TD REC updates - Errata items w3c/wot-thing-description#920 (1 comment by @ashimura)
-
-
4 pull requests opened.
-
Updating rendering script w3c/wot-thing-description#951, by @vcharpenay.
-
WIP: Simplified inline security definitions w3c/wot-thing-description#945, by @mmccool.
-
Combination security scheme w3c/wot-thing-description#944, by @mmccool.
-
WIP: Add proof and proofChain sections w3c/wot-thing-description#943, by @mmccool.
-
-
1 pull request merged.
-
Update OAuth2 section w3c/wot-thing-description#927.
-
-
8 pull requests received 24 new comments.
-
Update OAuth2 section w3c/wot-thing-description#927 (8 comments by @farshidtz, @mmccool, @sebastiankb)
-
WIP: Add proof and proofChain sections w3c/wot-thing-description#943 (2 comments by @mmccool, @sebastiankb)
-
move Thing Model (former TDT) to a main section + formalize Thing Model + introduce placeholder w3c/wot-thing-description#938 (1 comment by @sebastiankb)
-
[WIP] feat: add content type tables with data schema w3c/wot-thing-description#869 (1 comment by @sebastiankb)
-
WIP: Introduce minLength, maxLength, multipleOf, contentEncoding and contentMediaType in JSON Schema Ontology w3c/wot-thing-description#896 (1 comment by @sebastiankb)
w3c/wot-scripting-api
-
15 issues opened.
-
Check supported protocols in the validation algorithm w3c/wot-scripting-api#258, by @relu91.
-
Potentially insufficient error handling for emitEvent() w3c/wot-scripting-api#256, by @jak0bw.
-
Update open issues section w3c/wot-scripting-api#253, by @relu91.
-
Stale TD mitigation outdated (?) w3c/wot-scripting-api#252, by @relu91.
-
Emit event algorithm should not mention Protocol bindings w3c/wot-scripting-api#251, by @relu91.
-
Semplify Consumed thing example w3c/wot-scripting-api#245, by @relu91.
-
Consume algorithm and ConsumeThing ctor should be the same w3c/wot-scripting-api#244, by @relu91.
-
ReadHandler description is not completely correct w3c/wot-scripting-api#243, by @relu91.
-
Check data schema algorithm handle string DataSchema new fields. w3c/wot-scripting-api#242, by @relu91.
-
Should we use affordance instead of interaction? w3c/wot-scripting-api#241, by @relu91.
-
Check data schema algorithm and strings w3c/wot-scripting-api#240, by @relu91.
-
Consider to add one or more validation steps to assure TD consistency w3c/wot-scripting-api#238, by @relu91.
-
Report protocol errors that occur after subscriptions to Events and Property updates w3c/wot-scripting-api#237, by @danielpeintner.
-
"events" > ... > "op" > "unsubscribeevent" missing on generated TD. w3c/wot-scripting-api#233, by @jak0bw.
-
Some intial read-through comments w3c/wot-scripting-api#230, by @danielpeintner.
-
-
3 issues closed.
-
Semplify Consumed thing example w3c/wot-scripting-api#245.
-
Update open issues section w3c/wot-scripting-api#253.
-
"events" > ... > "op" > "unsubscribeevent" missing on generated TD. w3c/wot-scripting-api#233.
-
-
12 issues received 58 new comments.
-
Report protocol errors that occur after subscriptions to Events and Property updates w3c/wot-scripting-api#237 (17 comments by @danielpeintner, @jak0bw, @relu91, @zolkis)
-
Some intial read-through comments w3c/wot-scripting-api#230 (11 comments by @danielpeintner, @egekorkan, @zolkis)
-
Consider to add one or more validation steps to assure TD consistency w3c/wot-scripting-api#238 (7 comments by @danielpeintner, @egekorkan, @relu91)
-
Check data schema algorithm handle string DataSchema new fields. w3c/wot-scripting-api#242 (5 comments by @danielpeintner, @egekorkan, @relu91, @zolkis)
-
Should we use affordance instead of interaction? w3c/wot-scripting-api#241 (4 comments by @danielpeintner, @egekorkan, @zolkis)
-
Semplify Consumed thing example w3c/wot-scripting-api#245 (3 comments by @danielpeintner, @relu91, @zolkis)
-
Update open issues section w3c/wot-scripting-api#253 (3 comments by @danielpeintner, @egekorkan, @zolkis)
-
Check supported protocols in the validation algorithm w3c/wot-scripting-api#258 (2 comments by @zolkis)
-
ReadHandler description is not completely correct w3c/wot-scripting-api#243 (2 comments by @egekorkan, @zolkis)
-
"events" > ... > "op" > "unsubscribeevent" missing on generated TD. w3c/wot-scripting-api#233 (2 comments by @danielpeintner, @zolkis)
-
-
15 pull requests opened.
-
Add more Consume Thing examples w3c/wot-scripting-api#257, by @relu91.
-
Update consume thing consume example w3c/wot-scripting-api#255, by @relu91.
-
Remove Open Issue section, fixing #253. w3c/wot-scripting-api#254, by @zolkis.
-
chore: updates for Chapter 6 based on PDF comments from Ege w3c/wot-scripting-api#250, by @danielpeintner.
-
example: fix/add missing bracket w3c/wot-scripting-api#249, by @danielpeintner.
-
example review file for commenting the spec w3c/wot-scripting-api#248, by @zolkis.
-
Review Comments w3c/wot-scripting-api#247, by @egekorkan.
-
Add Cristiano Aguzzi as Editor w3c/wot-scripting-api#246, by @zolkis.
-
My review feedback w3c/wot-scripting-api#239, by @relu91.
-
minor: remove duplicated as w3c/wot-scripting-api#236, by @danielpeintner.
-
feat: update typescript definitions w3c/wot-scripting-api#235, by @danielpeintner.
-
Address #230: update first chapters w3c/wot-scripting-api#234, by @zolkis.
-
Review the spec. w3c/wot-scripting-api#232, by @zolkis.
-
Minor changes on chapters 4 and 5 w3c/wot-scripting-api#231, by @relu91.
-
docs: minor typos/issues w3c/wot-scripting-api#229, by @danielpeintner.
-
-
11 pull requests merged.
-
Update consume thing consume example w3c/wot-scripting-api#255.
-
Remove Open Issue section, fixing #253. w3c/wot-scripting-api#254.
-
chore: updates for Chapter 6 based on PDF comments from Ege w3c/wot-scripting-api#250.
-
My review feedback w3c/wot-scripting-api#239.
-
example: fix/add missing bracket w3c/wot-scripting-api#249.
-
Add Cristiano Aguzzi as Editor w3c/wot-scripting-api#246.
-
Address #230: update first chapters w3c/wot-scripting-api#234.
-
feat: update typescript definitions w3c/wot-scripting-api#235.
-
minor: remove duplicated as w3c/wot-scripting-api#236.
-
Minor changes on chapters 4 and 5 w3c/wot-scripting-api#231.
-
docs: minor typos/issues w3c/wot-scripting-api#229.
-
-
2 pull requests closed.
-
example review file for commenting the spec w3c/wot-scripting-api#248.
-
Review the spec. w3c/wot-scripting-api#232.
-
-
11 pull requests received 91 new comments.
-
Minor changes on chapters 4 and 5 w3c/wot-scripting-api#231 (19 comments by @egekorkan, @relu91, @zolkis)
-
Address #230: update first chapters w3c/wot-scripting-api#234 (8 comments by @danielpeintner, @relu91, @zolkis)
-
feat: update typescript definitions w3c/wot-scripting-api#235 (5 comments by @danielpeintner, @zolkis)
-
chore: updates for Chapter 6 based on PDF comments from Ege w3c/wot-scripting-api#250 (3 comments by @danielpeintner, @zolkis)
w3c/wot-discovery
-
13 issues opened.
-
Should Directories store TD Models as well as Instances? w3c/wot-discovery#58, by @mmccool.
-
Move Requirements to Architecture w3c/wot-discovery#57, by @mmccool.
-
Reach out to JSONPath community w3c/wot-discovery#56, by @mmccool.
-
Define plugfest 2020.10 scenarios for semantic discovery w3c/wot-discovery#55, by @mmccool.
-
Need to define the discovery types and vocabulary w3c/wot-discovery#54, by @farshidtz.
-
Clarifying Introduction Mechanisms w3c/wot-discovery#53, by @k-toumura.
-
How to avoid duplicates in a directory w3c/wot-discovery#48, by @farshidtz.
-
[Directory Use Case] Add non-WoT device to smart home hub w3c/wot-discovery#46, by @benfrancis.
-
[Directory Use Case] Add web thing to smart home hub w3c/wot-discovery#45, by @benfrancis.
-
Define error responses w3c/wot-discovery#44, by @mmccool.
-
Define the WoT-Directory type somewhere (eg in new version of context, in 1.1) w3c/wot-discovery#43, by @mmccool.
-
Decide how to securely do notifications from a Directory w3c/wot-discovery#42, by @mmccool.
-
Update CSS to add syntax highlighting for normative TD content w3c/wot-discovery#41, by @mmccool.
-
-
1 issue closed.
-
Move Requirements to Architecture w3c/wot-discovery#57.
-
-
11 issues received 31 new comments.
-
Add links section to directory information model w3c/wot-discovery#34 (8 comments by @AndreaCimminoArriaga, @benfrancis, @egekorkan, @farshidtz, @relu91)
-
Clarifying Introduction Mechanisms w3c/wot-discovery#53 (4 comments by @benfrancis, @danielpeintner, @farshidtz, @k-toumura)
-
Decide how to securely do notifications from a Directory w3c/wot-discovery#42 (4 comments by @farshidtz, @mmccool)
-
Directories should notify subscribers when a TD is updated w3c/wot-discovery#28 (2 comments by @farshidtz, @relu91)
-
Immutable Thing Description IDs inside the directory w3c/wot-discovery#39 (2 comments by @benfrancis, @farshidtz)
-
Should Directories store TD Models as well as Instances? w3c/wot-discovery#58 (1 comment by @mmccool)
-
Update CSS to add syntax highlighting for normative TD content w3c/wot-discovery#41 (1 comment by @mmccool)
-
-
6 pull requests opened.
-
Remove Requirements from index.html, update requirements.md file w3c/wot-discovery#59, by @mmccool.
-
Describe error response format for directory API w3c/wot-discovery#52, by @farshidtz.
-
Add description of the notification API w3c/wot-discovery#51, by @farshidtz.
-
Add additional security schemes to directory TD w3c/wot-discovery#50, by @farshidtz.
-
Initial intro sections for Discovery document w3c/wot-discovery#49, by @mmccool.
-
Updated index.html with search w3c/wot-discovery#47, by @AndreaCimminoArriaga.
-
-
5 pull requests merged.
-
Add additional security schemes to directory TD w3c/wot-discovery#50.
-
Remove Requirements from index.html, update requirements.md file w3c/wot-discovery#59.
-
Initial intro sections for Discovery document w3c/wot-discovery#49.
-
Describe error response format for directory API w3c/wot-discovery#52.
-
Draft of registration API w3c/wot-discovery#38.
-
-
6 pull requests received 28 new comments.
-
Add additional security schemes to directory TD w3c/wot-discovery#50 (11 comments by @farshidtz, @mmccool, @relu91)
-
Initial intro sections for Discovery document w3c/wot-discovery#49 (3 comments by @mmccool, @wiresio)
-
w3c/wot-security
-
3 issues opened.
-
Consider making a WoT Security and Privacy Template w3c/wot-security#182, by @mmccool.
-
Reconsider mandatory items in OAuth2 w3c/wot-security#181, by @mmccool.
-
Review EdgeX Security Architecture and align with it w3c/wot-security#180, by @mmccool.
-
-
7 issues received 18 new comments.
-
Security review of Lifecycle model and diagram w3c/wot-security#169 (7 comments by @ereshetova, @mmccool, @OliverPfaff, @zolkis)
-
Review Conexxus Security and Privacy Threat Model and Implementation Recommendations w3c/wot-security#170 (4 comments by @ereshetova, @mmccool)
-
Add "Security and Privacy Considerations" to all use cases (or requirements) w3c/wot-security#168 (1 comment by @mmccool)
-
-
2 pull requests opened.
-
Prepare to delete Working branch - update README w3c/wot-security#179, by @mmccool.
-
Prepare to delete working branch w3c/wot-security#178, by @mmccool.
-
-
2 pull requests merged.
-
Prepare to delete Working branch - update README w3c/wot-security#179.
-
Merge Working into Master w3c/wot-security#174.
-
-
1 pull request closed.
-
Prepare to delete working branch w3c/wot-security#178.
-
-
1 pull request received 1 new comment.
w3c/wot-profile
-
5 issues opened.
-
Standardized way to indicate capabilites w3c/wot-profile#32, by @mlagally.
-
Annotate the data model with common elements w3c/wot-profile#31, by @mlagally.
-
Allow only a finite set of vocabulary extensions? w3c/wot-profile#30, by @mlagally.
-
Make units mandatory? w3c/wot-profile#29, by @mlagally.
-
Human readable documentation w3c/wot-profile#27, by @mlagally.
-
-
5 issues received 19 new comments.
-
Comments on "core" profile and scope of constraints w3c/wot-profile#25 (8 comments by @benfrancis, @draggett, @egekorkan, @sebastiankb)
-
Core/default profile should mandate HTTP support as a minimum requirement w3c/wot-profile#24 (1 comment by @egekorkan)
-
-
2 pull requests opened.
-
Update index.html w3c/wot-profile#28, by @mlagally.
-
remove non existing terms w3c/wot-profile#26, by @sebastiankb.
-
-
3 pull requests merged.
-
Update index.html w3c/wot-profile#28.
-
fix: minor bug w3c/wot-profile#23.
-
remove non existing terms w3c/wot-profile#26.
-
w3c/wot-architecture
-
2 issues opened.
-
Incorporate Discovery terminology into terminology section w3c/wot-architecture#530, by @mlagally.
-
Which branch or tag corresponds to the release version w3c/wot-architecture#529, by @liuxing3169.
-
-
1 issue closed.
-
Which branch or tag corresponds to the release version w3c/wot-architecture#529.
-
-
1 issue received 2 new comments.
-
Which branch or tag corresponds to the release version w3c/wot-architecture#529 (2 comments by @liuxing3169, @mlagally)
-
-
1 pull request opened.
-
Define Discovery requirements w3c/wot-architecture#531, by @mmccool.
-
-
1 pull request merged.
-
Define Discovery requirements w3c/wot-architecture#531.
-
-
1 pull request received 1 new comment.
w3c/wot-binding-templates
-
1 issue opened.
-
Add SSE-over-websockets as a subprotocol w3c/wot-binding-templates#102, by @mmccool.
-
-
1 issue received 2 new comments.
-
Add SSE-over-websockets as a subprotocol w3c/wot-binding-templates#102 (2 comments by @egekorkan, @mmccool)
-
-
1 pull request received 2 new comments.
Participants
-
1 participant joined.
-
Jan Šuráň (Fiserv) joined.
-
-
3 participants left.
-
Michele Blank (Siemens AG) left.
-
Joerg Heuer (Siemens AG) left.
-
Johannes Hund (Siemens AG) left.
-
-
1 organization joined.
-
Fiserv joined.
-
GitHub
w3c/wot-profile
-
6 issues opened.
-
Comments on "core" profile and scope of constraints w3c/wot-profile#25, by @mjkoster.
-
Core/default profile should mandate HTTP support as a minimum requirement w3c/wot-profile#24, by @benfrancis.
-
Term 'Core' may cause a false impression w3c/wot-profile#21, by @sebastiankb.
-
Protocol constraints - generic and per protocol level w3c/wot-profile#19, by @mlagally.
-
Profile is not exclusive w3c/wot-profile#18, by @mlagally.
-
Vocabulary not in TD context w3c/wot-profile#17, by @sebastiankb.
-
-
3 issues closed.
-
Profile is not exclusive w3c/wot-profile#18.
-
Thing Template Profile and Digital Twin Profile are bad examples w3c/wot-profile#9.
-
Split Data Model constraints and bindings w3c/wot-profile#4.
-
-
9 issues received 16 new comments.
-
Term 'Core' may cause a false impression w3c/wot-profile#21 (4 comments by @benfrancis, @danielpeintner, @sebastiankb)
-
How to support composable "Vertical" vs. "Horizontal" Profiles w3c/wot-profile#8 (2 comments by @mlagally)
-
Thing Template Profile and Digital Twin Profile are bad examples w3c/wot-profile#9 (1 comment by @mlagally)
-
-
4 pull requests opened.
-
fix: minor bug w3c/wot-profile#23, by @danielpeintner.
-
Adding conformance section w3c/wot-profile#22, by @mlagally.
-
Profile is not exclusive, removing additional profiles w3c/wot-profile#20, by @mlagally.
-
Update index.html w3c/wot-profile#16, by @mlagally.
-
-
3 pull requests merged.
-
Adding conformance section w3c/wot-profile#22.
-
Profile is not exclusive, removing additional profiles w3c/wot-profile#20.
-
Update index.html w3c/wot-profile#16.
-
-
1 pull request received 4 new comments.
-
Profile is not exclusive, removing additional profiles w3c/wot-profile#20 (4 comments by @danielpeintner, @mlagally, @sebastiankb)
-
w3c/wot-thing-description
-
11 issues opened.
-
Evaluate Technology Readinesses of Semantic/Linked Data Tool chains for Web of Things - Issue 314 from w3c/wot w3c/wot-thing-description#939, by @egekorkan.
-
Fields for interface generation (e.g. UI, dashboards, IDE): description, icon - Issue 263 from w3c/wot w3c/wot-thing-description#936, by @egekorkan.
-
Add a class field to the TD - Issue 268 from w3c/wot w3c/wot-thing-description#935, by @egekorkan.
-
streams and compound values - Issue 281 from w3c/wot w3c/wot-thing-description#934, by @egekorkan.
-
Semantics Annotations in Type Systems - Issue 115 from w3c/wot w3c/wot-thing-description#933, by @egekorkan.
-
Thing Description versioning and Scripting API w3c/wot-thing-description#932, by @relu91.
-
Content Type for Thing Model (IANA registration needed) w3c/wot-thing-description#931, by @sebastiankb.
-
Rename "Thing Template" to "Thing Model" w3c/wot-thing-description#930, by @mlagally.
-
Multiple OAuth 2.0 flows in security definitions w3c/wot-thing-description#929, by @farshidtz.
-
Add OAuth2 client and device flows w3c/wot-thing-description#926, by @mmccool.
-
Small typo regarding 5.3.1.1 w3c/wot-thing-description#925, by @erceguder.
-
-
18 issues received 47 new comments.
-
Clarifying use of multiple security schemes in the security term w3c/wot-thing-description#901 (9 comments by @egekorkan, @farshidtz, @mmccool, @relu91)
-
[question] How to describe Philips Hue security scheme w3c/wot-thing-description#923 (5 comments by @egekorkan, @mmccool, @takuki)
-
Add a class field to the TD - Issue 268 from w3c/wot w3c/wot-thing-description#935 (3 comments by @relu91, @sebastiankb)
-
Thing Description versioning and Scripting API w3c/wot-thing-description#932 (3 comments by @egekorkan, @sebastiankb)
-
Clarify the usage of base64 encodings in DataSchema/ContentType w3c/wot-thing-description#912 (3 comments by @relu91, @sebastiankb)
-
[question] How to describe apikey in query w3c/wot-thing-description#922 (3 comments by @mmccool, @sebastiankb)
-
Fields for interface generation (e.g. UI, dashboards, IDE): description, icon - Issue 263 from w3c/wot w3c/wot-thing-description#936 (2 comments by @sebastiankb)
-
TDT shall allow to define placeholders w3c/wot-thing-description#897 (2 comments by @egekorkan, @takuki)
-
Allow array for response in From class? w3c/wot-thing-description#617 (2 comments by @egekorkan, @farshidtz)
-
Multiple OAuth 2.0 flows in security definitions w3c/wot-thing-description#929 (2 comments by @farshidtz, @mmccool)
-
streams and compound values - Issue 281 from w3c/wot w3c/wot-thing-description#934 (1 comment by @sebastiankb)
-
extend op options with observeallproperties and observemultipleproperties w3c/wot-thing-description#800 (1 comment by @sebastiankb)
-
Vocabulary term "scheme" not defined when used inside securityDefinitions w3c/wot-thing-description#915 (1 comment by @takuki)
-
Editorial issues for consolidated TD REC updates - Errata items w3c/wot-thing-description#920 (1 comment by @takuki)
-
-
3 pull requests opened.
-
move Thing Model (former TDT) to a main section + formalize Thing Model + introduce placeholder w3c/wot-thing-description#938, by @sebastiankb.
-
WIP: swap securtiy and securityDefinition in context file w3c/wot-thing-description#937, by @sebastiankb.
-
Update OAuth2 section w3c/wot-thing-description#927, by @mmccool.
-
-
3 pull requests received 11 new comments.
-
Update OAuth2 section w3c/wot-thing-description#927 (8 comments by @farshidtz, @mmccool, @relu91, @takuki)
-
WIP: Introduce minLength, maxLength, multipleOf, contentEncoding and contentMediaType in JSON Schema Ontology w3c/wot-thing-description#896 (2 comments by @sebastiankb)
-
WIP: swap securtiy and securityDefinition in context file w3c/wot-thing-description#937 (1 comment by @sebastiankb)
-
w3c/wot-binding-templates
-
3 issues opened.
-
Explain BACNet related ideas w3c/wot-binding-templates#101, by @egekorkan.
-
Explain Websocket binding ideas w3c/wot-binding-templates#100, by @egekorkan.
-
CoAP RDF w3c/wot-binding-templates#97, by @sebastiankb.
-
-
2 issues received 7 new comments.
-
2 pull requests opened.
-
Presentation ROS as addition to the W3C WoT w3c/wot-binding-templates#99, by @MarcusWolfSchmidt.
-
Modbus Vocabulary w3c/wot-binding-templates#98, by @Drukob.
-
-
1 pull request merged.
-
Presentation ROS as addition to the W3C WoT w3c/wot-binding-templates#99.
-
-
2 pull requests received 5 new comments.
w3c/wot-discovery
-
4 issues opened.
-
Use cases for the discovery task - revisited - Issue 343 from w3c/wot w3c/wot-discovery#40, by @egekorkan.
-
Immutable Thing Description IDs inside the directory w3c/wot-discovery#39, by @farshidtz.
-
Including life time in TDs registration w3c/wot-discovery#37, by @AndreaCimminoArriaga.
-
Add links section to directory information model w3c/wot-discovery#34, by @mmccool.
-
-
1 issue closed.
-
Including life time in TDs registration w3c/wot-discovery#37.
-
-
4 issues received 12 new comments.
-
Add links section to directory information model w3c/wot-discovery#34 (4 comments by @benfrancis, @relu91)
-
Immutable Thing Description IDs inside the directory w3c/wot-discovery#39 (2 comments by @benfrancis, @mmccool)
-
Including life time in TDs registration w3c/wot-discovery#37 (2 comments by @AndreaCimminoArriaga, @relu91)
-
-
3 pull requests opened.
-
Draft of registration API w3c/wot-discovery#38, by @farshidtz.
-
Thing Description for LinkSmart directory w3c/wot-discovery#36, by @farshidtz.
-
Initial WoT Discovery index.html outline w3c/wot-discovery#35, by @mmccool.
-
-
4 pull requests merged.
-
Initial WoT Discovery index.html outline w3c/wot-discovery#35.
-
Add API description of Fujitsu's directory implementation. w3c/wot-discovery#33.
-
Proposal: Thing Description for Thing Directory w3c/wot-discovery#31.
-
Thing Description for LinkSmart directory w3c/wot-discovery#36.
-
-
3 pull requests received 16 new comments.
-
Initial WoT Discovery index.html outline w3c/wot-discovery#35 (10 comments by @ashimura, @benfrancis, @farshidtz, @k-toumura, @mmccool)
-
Thing Description for LinkSmart directory w3c/wot-discovery#36 (5 comments by @benfrancis, @farshidtz)
-
w3c/wot-scripting-api
-
7 issues opened.
-
Event handling - Issue 235 from w3c/wot w3c/wot-scripting-api#228, by @egekorkan.
-
Discovery of exposed Things on the same runtime - Issue 233 from w3c/wot w3c/wot-scripting-api#227, by @egekorkan.
-
ThingFilter server attribute - Issue 50 from w3c/wot w3c/wot-scripting-api#226, by @egekorkan.
-
Link the API specification to the Thing Description version w3c/wot-scripting-api#225, by @relu91.
-
Scripting API versioning w3c/wot-scripting-api#224, by @relu91.
-
Update "Changes" section for upcoming publication w3c/wot-scripting-api#223, by @danielpeintner.
-
Possible alternative design of Discovering API w3c/wot-scripting-api#222, by @relu91.
-
-
3 issues received 8 new comments.
-
Possible alternative design of Discovering API w3c/wot-scripting-api#222 (6 comments by @danielpeintner, @relu91, @zolkis)
-
ThingFilter server attribute - Issue 50 from w3c/wot w3c/wot-scripting-api#226 (1 comment by @relu91)
-
w3c/wot-architecture
-
3 issues received 3 new comments.
-
Sequence diagram for TD lookup in a directory service w3c/wot-architecture#524 (1 comment by @mlagally)
-
-
1 pull request opened.
-
Connected building requirements w3c/wot-architecture#528, by @farshidtz.
-
-
1 pull request merged.
-
Update requirements-template.md w3c/wot-architecture#525.
-
w3c/wot-security-best-practices
-
3 issues opened.
-
Update with Discovery and Directory recommendations w3c/wot-security-best-practices#7, by @mmccool.
-
Reference to draft RFC for MQTT URL scheme w3c/wot-security-best-practices#6, by @mmccool.
-
Recommended OAuth2 flows w3c/wot-security-best-practices#5, by @mmccool.
-
Participants
-
23 participants joined.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) joined.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) joined.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) joined.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) joined.
-
Ken Ogiso (Internet Research Institute, Inc.) joined.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) joined.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) joined.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) joined.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) joined.
-
Ken Ogiso (Internet Research Institute, Inc.) joined.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) joined.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) joined.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) joined.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) joined.
-
Ken Ogiso (Internet Research Institute, Inc.) joined.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) joined.
-
Shogo Iwaki (Internet Research Institute, Inc.) joined.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) joined.
-
Ken Ogiso (Internet Research Institute, Inc.) joined.
-
Shogo Iwaki (Internet Research Institute, Inc.) joined.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) joined.
-
Tetsuhiko Hirata (Hitachi, Ltd.) joined.
-
Cristiano Aguzzi (W3C Invited Experts) joined.
-
-
19 participants left.
-
Angel Retamar (Fundacion CTIC) left.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) left.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) left.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) left.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) left.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) left.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) left.
-
Ken Ogiso (Internet Research Institute, Inc.) left.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) left.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) left.
-
Ken Ogiso (Internet Research Institute, Inc.) left.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) left.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) left.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) left.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) left.
-
Shogo Iwaki (Internet Research Institute, Inc.) left.
-
Tomoaki Mizushima (Internet Research Institute, Inc.) left.
-
Hiroshi Fujiwara (Internet Research Institute, Inc.) left.
-
Ken Ogiso (Internet Research Institute, Inc.) left.
-
GitHub
w3c/wot-thing-description
-
13 issues opened.
-
[question] How to describe Philips Hue security scheme w3c/wot-thing-description#923, by @egekorkan.
-
[question] How to describe apikey in query w3c/wot-thing-description#922, by @egekorkan.
-
Differences between Mozilla & W3C Thing Description specifications w3c/wot-thing-description#921, by @benfrancis.
-
Editorial issues for consolidated TD REC updates - Errata items w3c/wot-thing-description#920, by @danielpeintner.
-
Warning by W3C validator w3c/wot-thing-description#919, by @shujikamitsuna.
-
Refer to developer documentation from a TD w3c/wot-thing-description#918, by @mlagally.
-
Ontology files return 404 w3c/wot-thing-description#917, by @egekorkan.
-
Consider defining an expiry date for a TD w3c/wot-thing-description#916, by @mlagally.
-
Vocabulary term "scheme" not defined when used inside securityDefinitions w3c/wot-thing-description#915, by @nikosft.
-
Improve the text on Action parameters (vs input) w3c/wot-thing-description#913, by @zolkis.
-
Clarify the usage of base64 encodings in DataSchema/ContentType w3c/wot-thing-description#912, by @relu91.
-
Examples for actions using URI variables should explain why not using input w3c/wot-thing-description#910, by @zolkis.
-
TD ontology minor suggestions w3c/wot-thing-description#909, by @gatemezing.
-
-
15 issues received 65 new comments.
-
Clarifying how readmultipleproperties work w3c/wot-thing-description#848 (13 comments by @benfrancis, @egekorkan, @relu91, @takuki, @zolkis)
-
Managing Dynamically Created Resources in TDs w3c/wot-thing-description#899 (9 comments by @benfrancis, @egekorkan, @mkovatsc, @mmccool, @takuki, @vcharpenay, @zolkis)
-
Consider defining an expiry date for a TD w3c/wot-thing-description#916 (7 comments by @benfrancis, @egekorkan, @farshidtz, @sebastiankb)
-
Is the use of "$ref" and "definitions" allowed in TD ? w3c/wot-thing-description#307 (5 comments by @danielpeintner, @sebastiankb)
-
Improve the text on Action parameters (vs input) w3c/wot-thing-description#913 (5 comments by @danielpeintner, @sebastiankb, @zolkis)
-
Examples for actions using URI variables should explain why not using input w3c/wot-thing-description#910 (5 comments by @danielpeintner, @egekorkan, @takuki, @zolkis)
-
Vocabulary term "scheme" not defined when used inside securityDefinitions w3c/wot-thing-description#915 (4 comments by @nikosft, @sebastiankb)
-
Need a $id for the JSON Schema w3c/wot-thing-description#674 (4 comments by @fennibay, @sebastiankb, @vcharpenay)
-
Missing default value for observable w3c/wot-thing-description#908 (4 comments by @egekorkan, @sebastiankb, @takuki, @zolkis)
-
[question] How to describe Philips Hue security scheme w3c/wot-thing-description#923 (2 comments by @egekorkan, @relu91)
-
Refer to developer documentation from a TD w3c/wot-thing-description#918 (2 comments by @mlagally, @sebastiankb)
-
Thing Model of an SDF/OneDM Example w3c/wot-thing-description#903 (2 comments by @danielpeintner, @mlagally)
-
Clarify the usage of base64 encodings in DataSchema/ContentType w3c/wot-thing-description#912 (1 comment by @zolkis)
-
Clarifying use of multiple security schemes in the security term w3c/wot-thing-description#901 (1 comment by @egekorkan)
-
-
2 pull requests opened.
-
fix: remove wrong "," in example 17 TD snippet w3c/wot-thing-description#914, by @danielpeintner.
-
Update uriVariable example (21) w3c/wot-thing-description#911, by @egekorkan.
-
-
2 pull requests merged.
-
Update uriVariable example (21) w3c/wot-thing-description#911.
-
Hypermedia Proposal 2 w3c/wot-thing-description#907.
-
-
3 pull requests received 8 new comments.
-
Update uriVariable example (21) w3c/wot-thing-description#911 (4 comments by @egekorkan, @sebastiankb, @zolkis)
-
Hypermedia Proposal 2 w3c/wot-thing-description#907 (3 comments by @egekorkan, @sebastiankb, @zolkis)
-
fix: remove wrong "," in example 17 TD snippet w3c/wot-thing-description#914 (1 comment by @sebastiankb)
-
w3c/wot-discovery
-
6 issues opened.
-
What is a Thing Directory? w3c/wot-discovery#32, by @benfrancis.
-
Define Out-of-Band Information w3c/wot-discovery#30, by @mmccool.
-
Profiles for Directories w3c/wot-discovery#29, by @mmccool.
-
Directories should notify subscribers when a TD is updated w3c/wot-discovery#28, by @mmccool.
-
GovTech - Smart City Discovery w3c/wot-discovery#26, by @mmccool.
-
[question] Are proprietary search/discovery mechanisms in scope? w3c/wot-discovery#25, by @egekorkan.
-
-
7 issues received 20 new comments.
-
Consider TTL Use cases w3c/wot-discovery#18 (10 comments by @benfrancis, @egekorkan, @farshidtz, @relu91)
-
Directories should notify subscribers when a TD is updated w3c/wot-discovery#28 (4 comments by @benfrancis, @farshidtz, @relu91, @zolkis)
-
-
3 pull requests opened.
-
Add API description of Fujitsu's directory implementation. w3c/wot-discovery#33, by @k-toumura.
-
Proposal: Thing Description for Thing Directory w3c/wot-discovery#31, by @benfrancis.
-
Presentation on Fraunhofer LinkSmart Thing Directory w3c/wot-discovery#27, by @mmccool.
-
-
1 pull request merged.
-
Presentation on Fraunhofer LinkSmart Thing Directory w3c/wot-discovery#27.
-
w3c/wot-architecture
-
3 issues opened.
-
Sequence diagram for TD lookup in a directory service w3c/wot-architecture#524, by @mlagally.
-
Sequence diagram for thing discovery w3c/wot-architecture#523, by @mlagally.
-
Identify Additional System Components w3c/wot-architecture#522, by @mlagally.
-
-
8 issues closed.
-
Update lifecycle UC: Include references to diagram and presentation w3c/wot-architecture#473.
-
Smart Grid Use Case w3c/wot-architecture#460.
-
Transportation use case w3c/wot-architecture#469.
-
Create Energy Efficiency for Smart Buildings Use Case w3c/wot-architecture#481.
-
Update Smart City use cases with Security and Privacy Considerations w3c/wot-architecture#492.
-
Update Retail Use Case with Security and Privacy Considerations w3c/wot-architecture#494.
-
Use Case for Education/Teaching w3c/wot-architecture#496.
-
Request to change the figure of "nhk-device-tv-sync.md" w3c/wot-architecture#507.
-
-
8 issues received 8 new comments.
-
Update lifecycle UC: Include references to diagram and presentation w3c/wot-architecture#473 (1 comment by @mlagally)
-
Create Energy Efficiency for Smart Buildings Use Case w3c/wot-architecture#481 (1 comment by @mlagally)
-
Update Smart City use cases with Security and Privacy Considerations w3c/wot-architecture#492 (1 comment by @mlagally)
-
Update Retail Use Case with Security and Privacy Considerations w3c/wot-architecture#494 (1 comment by @mlagally)
-
7 pull requests opened.
-
Update requirements-template.md w3c/wot-architecture#525, by @mlagally.
-
integrating before move to use-cases repo w3c/wot-architecture#521, by @mlagally.
-
Update device-lifecycle.md w3c/wot-architecture#520, by @mlagally.
-
Update lifecycle diagrams. Collect lifecycle proposals in a folder. w3c/wot-architecture#518, by @zolkis.
-
Update oauth2.0 use cases w3c/wot-architecture#517, by @relu91.
-
Created smart-campus use case w3c/wot-architecture#516, by @AndreaCimminoArriaga.
-
Update oauth2.0 use cases w3c/wot-architecture#515, by @relu91.
-
-
5 pull requests merged.
-
integrating before move to use-cases repo w3c/wot-architecture#521.
-
Update oauth2.0 use cases w3c/wot-architecture#517.
-
Created smart-campus use case w3c/wot-architecture#516.
-
Update device-lifecycle.md w3c/wot-architecture#520.
-
Update lifecycle diagrams. Collect lifecycle proposals in a folder. w3c/wot-architecture#518.
-
-
1 pull request closed.
-
Update oauth2.0 use cases w3c/wot-architecture#515.
-
-
3 pull requests received 6 new comments.
-
Created smart-campus use case w3c/wot-architecture#516 (2 comments by @AndreaCimminoArriaga, @mlagally)
-
w3c/wot-binding-templates
-
1 issue closed.
-
Review Comments: W3C Editor's Draft 23 January 2018 w3c/wot-binding-templates#21.
-
-
2 issues received 4 new comments.
-
Identifying next protocols to work w3c/wot-binding-templates#92 (3 comments by @egekorkan, @mmccool)
-
Review Comments: W3C Editor's Draft 23 January 2018 w3c/wot-binding-templates#21 (1 comment by @egekorkan)
-
w3c/wot-scripting-api
-
2 issues opened.
-
Discussion about read- write-/multipleproperties w3c/wot-scripting-api#219, by @danielpeintner.
-
Provide a convenient way to fetch a TD in simple case w3c/wot-scripting-api#216, by @zolkis.
-
-
3 issues closed.
-
[ExposedThing] Not possible to handle property observations in Scripting level w3c/wot-scripting-api#211.
-
[ExposedThing] Not possible to handle event subscriptions in Scripting level w3c/wot-scripting-api#210.
-
Fix property interaction algorithms to correctly handle Forms, contentType and DataSchema w3c/wot-scripting-api#201.
-
-
1 issue reopened.
-
[typescript] Use namespace instead of interface for WoT functions w3c/wot-scripting-api#215, by @danielpeintner.
-
-
8 issues received 24 new comments.
-
Discussion about read- write-/multipleproperties w3c/wot-scripting-api#219 (9 comments by @danielpeintner, @egekorkan, @zolkis)
-
Provide a convenient way to fetch a TD in simple case w3c/wot-scripting-api#216 (7 comments by @danielpeintner, @relu91, @zolkis)
-
[typescript] Use namespace instead of interface for WoT functions w3c/wot-scripting-api#215 (1 comment by @danielpeintner)
-
Produce() method should ignore instance specific information w3c/wot-scripting-api#156 (1 comment by @zolkis)
-
[ExposedThing] Not possible to handle property observations in Scripting level w3c/wot-scripting-api#211 (1 comment by @zolkis)
-
Fix property interaction algorithms to correctly handle Forms, contentType and DataSchema w3c/wot-scripting-api#201 (1 comment by @zolkis)
-
-
4 pull requests opened.
-
Address #200: improve text on error handling w3c/wot-scripting-api#221, by @zolkis.
-
Fix #215: make the API entry point a namespace. w3c/wot-scripting-api#220, by @zolkis.
-
Add ExposedThing property observe, unobserve and event handler support w3c/wot-scripting-api#218, by @zolkis.
-
Update draft branch w3c/wot-scripting-api#217, by @zolkis.
-
-
5 pull requests merged.
-
Address #200: improve text on error handling w3c/wot-scripting-api#221.
-
Fix #215: make the API entry point a namespace. w3c/wot-scripting-api#220.
-
Add ExposedThing property observe, unobserve and event handler support w3c/wot-scripting-api#218.
-
Update draft branch w3c/wot-scripting-api#217.
-
Add InteractionData w3c/wot-scripting-api#209.
-
-
4 pull requests received 80 new comments.
-
Add ExposedThing property observe, unobserve and event handler support w3c/wot-scripting-api#218 (66 comments by @danielpeintner, @relu91, @zolkis)
-
Fix #215: make the API entry point a namespace. w3c/wot-scripting-api#220 (4 comments by @danielpeintner, @zolkis)
-
Address #200: improve text on error handling w3c/wot-scripting-api#221 (1 comment by @danielpeintner)
-
w3c/wot-security
-
1 issue opened.
-
Review oAuth2.0 use case w3c/wot-security#177, by @relu91.
-
Participants
-
4 participants joined.
-
Kevin Olotu (W3C Invited Experts) joined.
-
Shinjiro Urata (ACCESS CO., LTD.) joined.
-
Katsuhiro Mihara (ACCESS CO., LTD.) joined.
-
Ben Francis (W3C Invited Experts) joined.
-
GitHub
w3c/wot-architecture
-
5 issues opened.
-
Create a terminology definition for "system user data" w3c/wot-architecture#508, by @mlagally.
-
Request to change the figure of "nhk-device-tv-sync.md" w3c/wot-architecture#507, by @abes-jg.
-
Use Case for Education/Teaching w3c/wot-architecture#496, by @egekorkan.
-
Update Retail Use Case with Security and Privacy Considerations w3c/wot-architecture#494, by @mmccool.
-
Update Smart City use cases with Security and Privacy Considerations w3c/wot-architecture#492, by @mmccool.
-
-
6 issues received 7 new comments.
-
Update Retail Use Case with Security and Privacy Considerations w3c/wot-architecture#494 (2 comments by @clerley, @mmccool)
-
Create a terminology definition for "system user data" w3c/wot-architecture#508 (1 comment by @mlagally)
-
Create Energy Efficiency for Smart Buildings Use Case w3c/wot-architecture#481 (1 comment by @farshidtz)
-
Update Smart City use cases with Security and Privacy Considerations w3c/wot-architecture#492 (1 comment by @mmccool)
-
-
14 pull requests opened.
-
replace figure as requested in https://github.com/w3c/wot-architecture/issues/507 w3c/wot-architecture#514, by @mlagally.
-
Add smart building use case w3c/wot-architecture#509, by @sebastiankb.
-
WoT Use Cases - Initial draft w3c/wot-architecture#506, by @mlagally.
-
Create a new requirements from agriculture w3c/wot-architecture#505, by @mryuichi.
-
Created Medical Devices use case w3c/wot-architecture#504, by @takuki.
-
Slides from arch call on 14.5. - Use case process and status w3c/wot-architecture#503, by @mlagally.
-
Add education and shared resources use case w3c/wot-architecture#502, by @egekorkan.
-
Update retail.md w3c/wot-architecture#501, by @clerley.
-
Update retail.md with Security and Privacy considerations w3c/wot-architecture#500, by @mmccool.
-
Update README.md w3c/wot-architecture#499, by @mlagally.
-
Adding profile use case w3c/wot-architecture#498, by @mlagally.
-
Use case cleanup w3c/wot-architecture#497, by @mlagally.
-
Add smart building energy efficiency use case w3c/wot-architecture#495, by @farshidtz.
-
Update smartcity-health-monitoring.md w3c/wot-architecture#491, by @mmccool.
-
-
16 pull requests merged.
-
Created Medical Devices use case w3c/wot-architecture#504.
-
replace figure as requested in https://github.com/w3c/wot-architecture/issues/507 w3c/wot-architecture#514.
-
Add smart building use case w3c/wot-architecture#509.
-
Update retail.md with Security and Privacy considerations w3c/wot-architecture#500.
-
Adding profile use case w3c/wot-architecture#498.
-
WoT Use Cases - Initial draft w3c/wot-architecture#506.
-
Slides from arch call on 14.5. - Use case process and status w3c/wot-architecture#503.
-
Add device lifecycle proposal w3c/wot-architecture#478.
-
Add education and shared resources use case w3c/wot-architecture#502.
-
Update retail.md w3c/wot-architecture#501.
-
Update README.md w3c/wot-architecture#499.
-
Add Smart Grid Use Case w3c/wot-architecture#487.
-
Add smart building energy efficiency use case w3c/wot-architecture#495.
-
Add Transportation use case w3c/wot-architecture#470.
-
Use case cleanup w3c/wot-architecture#497.
-
Update smartcity-health-monitoring.md w3c/wot-architecture#491.
-
-
7 pull requests received 23 new comments.
-
Add device lifecycle proposal w3c/wot-architecture#478 (10 comments by @clerley, @ereshetova, @mlagally, @zolkis)
-
Update retail.md with Security and Privacy considerations w3c/wot-architecture#500 (2 comments by @mmccool)
-
w3c/wot-scripting-api
-
1 issue opened.
-
[typescript] Use namespace instead of interface for WoT functions w3c/wot-scripting-api#215, by @relu91.
-
-
1 issue closed.
-
Should language and encoding be optional InteractionOptions members? w3c/wot-scripting-api#213.
-
-
4 issues received 37 new comments.
-
Fix property interaction algorithms to correctly handle Forms, contentType and DataSchema w3c/wot-scripting-api#201 (23 comments by @danielpeintner, @relu91, @zolkis)
-
Requirements from oAuth 2.0 code flow w3c/wot-scripting-api#214 (8 comments by @egekorkan, @mmccool, @relu91, @zolkis)
-
[typescript] Use namespace instead of interface for WoT functions w3c/wot-scripting-api#215 (5 comments by @danielpeintner, @egekorkan, @relu91, @zolkis)
-
Should language and encoding be optional InteractionOptions members? w3c/wot-scripting-api#213 (1 comment by @zolkis)
-
-
1 pull request received 26 new comments.
w3c/wot-thing-description
-
8 issues opened.
-
Missing default value for observable w3c/wot-thing-description#908, by @danielpeintner.
-
Make sure WoT TD and IETF RESTful architectures are consistent w3c/wot-thing-description#906, by @mmccool.
-
Missing triple resolution in JSON-LD playground for properties forms w3c/wot-thing-description#905, by @sebastiankb.
-
Introduction is missing security component w3c/wot-thing-description#904, by @egekorkan.
-
Thing Model of an SDF/OneDM Example w3c/wot-thing-description#903, by @sebastiankb.
-
Clarifying use of multiple security schemes in the security term w3c/wot-thing-description#901, by @egekorkan.
-
Link misses description w3c/wot-thing-description#900, by @danielpeintner.
-
Managing Dynamically Created Resources in TDs w3c/wot-thing-description#899, by @vcharpenay.
-
-
13 issues received 73 new comments.
-
Managing Dynamically Created Resources in TDs w3c/wot-thing-description#899 (16 comments by @benfrancis, @danielpeintner, @egekorkan, @relu91, @takuki, @vcharpenay)
-
PropertyAffordance is missing InteractionAffordance properties in the published JSON-LD context w3c/wot-thing-description#894 (10 comments by @egekorkan, @gkellogg, @pchampin, @RoboPhred, @sebastiankb, @vcharpenay)
-
Thing Model of an SDF/OneDM Example w3c/wot-thing-description#903 (9 comments by @danielpeintner, @egekorkan, @mjkoster, @sebastiankb, @takuki)
-
TDT shall allow to define placeholders w3c/wot-thing-description#897 (9 comments by @egekorkan, @sebastiankb, @takuki)
-
Link misses description w3c/wot-thing-description#900 (6 comments by @benfrancis, @egekorkan, @sebastiankb, @vcharpenay)
-
Semantic information in TDTs w3c/wot-thing-description#898 (6 comments by @kolotu, @sebastiankb, @vcharpenay)
-
How do you cancel or query the state of an action request? w3c/wot-thing-description#302 (5 comments by @egekorkan, @sebastiankb, @takuki, @vcharpenay)
-
Is the use of "$ref" and "definitions" allowed in TD ? w3c/wot-thing-description#307 (3 comments by @takuki, @vcharpenay)
-
HTTP Binding for providing historical events. w3c/wot-thing-description#892 (3 comments by @sebastiankb, @takuki)
-
Introduction is missing security component w3c/wot-thing-description#904 (2 comments by @sebastiankb, @takuki)
-
Missing triple resolution in JSON-LD playground for properties forms w3c/wot-thing-description#905 (2 comments by @dlongley, @pchampin)
-
[vocabulary] Consider adding keyword to describe synchronous actions w3c/wot-thing-description#890 (1 comment by @egekorkan)
-
-
1 pull request opened.
-
Hypermedia Proposal 2 w3c/wot-thing-description#907, by @egekorkan.
-
-
2 pull requests received 4 new comments.
-
[WIP] feat: add content type tables with data schema w3c/wot-thing-description#869 (2 comments by @egekorkan, @relu91)
-
WIP: Introduce minLength, maxLength, multipleOf, contentEncoding and contentMediaType in JSON Schema Ontology w3c/wot-thing-description#896 (2 comments by @sebastiankb)
-
w3c/wot-discovery
-
3 issues opened.
-
Consider how to sign TDs in a directory service w3c/wot-discovery#24, by @mmccool.
-
Standardizing how to describe the location of the TD w3c/wot-discovery#440, by @egekorkan.
-
Consider Role "Part of" TDs in Query Results w3c/wot-discovery#21, by @mmccool.
-
-
3 issues received 12 new comments.
-
Standardizing how to describe the location of the TD w3c/wot-discovery#440 (6 comments by @benfrancis, @egekorkan, @mmccool, @sebastiankb, @takuki)
-
Handle huge set of Thing Descriptions (pagination, streaming, etc.) w3c/wot-discovery#16 (2 comments by @mmccool, @zolkis)
-
-
2 pull requests opened.
-
Add details to design document w3c/wot-discovery#23, by @mmccool.
-
Create design.md w3c/wot-discovery#22, by @mmccool.
-
-
4 pull requests merged.
-
Add details to design document w3c/wot-discovery#23.
-
UPM Use Case about Smart Campus w3c/wot-discovery#20.
-
Create design.md w3c/wot-discovery#22.
-
Add Fujitsu's discovery work w3c/wot-discovery#19.
-
-
1 pull request received 1 new comment.
w3c/wot-security
-
3 issues opened.
-
Consider OAuth2 "device" flow w3c/wot-security#173, by @mmccool.
-
Review Conexxus Security and Privacy Threat Model and Implementation Recommendations w3c/wot-security#170, by @mmccool.
-
Security review of Lifecycle model and diagram w3c/wot-security#169, by @mlagally.
-
-
4 issues received 11 new comments.
-
Security review of Lifecycle model and diagram w3c/wot-security#169 (8 comments by @clerley, @mlagally, @zolkis)
-
Review Conexxus Security and Privacy Threat Model and Implementation Recommendations w3c/wot-security#170 (1 comment by @mmccool)
-
-
5 pull requests opened.
-
Changes for Issue #144: references/text w3c/wot-security#176, by @OliverPfaff.
-
Additions and (minor) changes for Issue #144 w3c/wot-security#175, by @OliverPfaff.
-
Merge Working into Master w3c/wot-security#174, by @mmccool.
-
Issue #144: text proposal for end-to-end security w3c/wot-security#172, by @OliverPfaff.
-
Testing only w3c/wot-security#171, by @OliverPfaff.
-
-
2 pull requests merged.
-
Changes for Issue #144: references/text w3c/wot-security#176.
-
Issue #144: text proposal for end-to-end security w3c/wot-security#172.
-
-
2 pull requests closed.
-
Additions and (minor) changes for Issue #144 w3c/wot-security#175.
-
Testing only w3c/wot-security#171.
-
-
4 pull requests received 4 new comments.
w3c/wot-binding-templates
-
1 issue opened.
-
Explaining readallproperties for MQTT w3c/wot-binding-templates#96, by @egekorkan.
-
-
1 issue reopened.
-
Create RDF representations of CoAP and MQTT vocabulary w3c/wot-binding-templates#93, by @sebastiankb.
-
-
1 issue received 2 new comments.
-
Create RDF representations of CoAP and MQTT vocabulary w3c/wot-binding-templates#93 (2 comments by @sebastiankb, @vcharpenay)
-
TR publications
-
2 documents published.
-
Web of Things (WoT) Architecture published as a Recommendation. History of Web of Things (WoT) Architecture
-
Web of Things (WoT) Thing Description published as a Recommendation. History of Web of Things (WoT) Thing Description
-
Participants
-
5 participants joined.
-
Hazel Kuok (W3C Invited Experts) joined.
-
Mike Lenox (Conexxus) joined.
-
Mike Lenox (Conexxus) joined.
-
Clerley Silveira (Conexxus) joined.
-
Farshid Tavakolizadeh (W3C Invited Experts) joined.
-
-
1 participant left.
-
Mike Lenox (Conexxus) left.
-
-
1 organization joined.
-
Data Society Alliance joined.
-
GitHub
w3c/wot-architecture
-
5 issues opened.
-
Identifiers of virtual devices w3c/wot-architecture#486, by @auslavs.
-
Create Energy Efficiency for Smart Buildings Use Case w3c/wot-architecture#481, by @mmccool.
-
Use case: Home WoT devices work according to TV programs w3c/wot-architecture#480, by @abes-jg.
-
Requirement document for Agriculture w3c/wot-architecture#479, by @mlagally.
-
Define lifecycle states + definitions+actors+security data in a table w3c/wot-architecture#476, by @mlagally.
-
-
4 issues closed.
-
Use case: Home WoT devices work according to TV programs w3c/wot-architecture#480.
-
Identifiers of virtual devices w3c/wot-architecture#486.
-
Agriculture use case w3c/wot-architecture#461.
-
Improve Use Case Template w3c/wot-architecture#462.
-
-
7 issues received 20 new comments.
-
Define lifecycle states + definitions+actors+security data in a table w3c/wot-architecture#476 (11 comments by @ereshetova, @mlagally, @mmccool, @zolkis)
-
Identifiers of virtual devices w3c/wot-architecture#486 (3 comments by @auslavs, @mlagally, @mmccool)
-
Create Energy Efficiency for Smart Buildings Use Case w3c/wot-architecture#481 (1 comment by @mmccool)
-
Update lifecycle UC: Include references to diagram and presentation w3c/wot-architecture#473 (1 comment by @mlagally)
-
-
9 pull requests opened.
-
Propose new use-case and requirement template sections for security and privacy w3c/wot-architecture#488, by @mmccool.
-
Add Smart Grid Use Case w3c/wot-architecture#487, by @wiresio.
-
Update smartcity-geolocation.md w3c/wot-architecture#485, by @mlagally.
-
Nhk device tv sync w3c/wot-architecture#484, by @mlagally.
-
Folder cleanup - removing obsolete diagrams w3c/wot-architecture#483, by @mlagally.
-
Update gps-tracker.md w3c/wot-architecture#482, by @mlagally.
-
Add device lifecycle proposal w3c/wot-architecture#478, by @zolkis.
-
Update device-lifecycle.md w3c/wot-architecture#475, by @mlagally.
-
-
6 pull requests merged.
-
Propose new use-case and requirement template sections for security and privacy w3c/wot-architecture#488.
-
Update smartcity-geolocation.md w3c/wot-architecture#485.
-
Add public health monitoring use case, update geolocation - Smart City domain w3c/wot-architecture#468.
-
Nhk device tv sync w3c/wot-architecture#484.
-
Create a use case of agriculture w3c/wot-architecture#471.
-
Update device-lifecycle.md w3c/wot-architecture#475.
-
-
3 pull requests closed.
-
Folder cleanup - removing obsolete diagrams w3c/wot-architecture#483.
-
Update gps-tracker.md w3c/wot-architecture#482.
-
Lifecycle w3c/wot-architecture#477.
-
-
6 pull requests received 50 new comments.
-
Add public health monitoring use case, update geolocation - Smart City domain w3c/wot-architecture#468 (17 comments by @mlagally, @mmccool)
-
Create a use case of agriculture w3c/wot-architecture#471 (5 comments by @mryuichi, @relu91, @zolkis)
w3c/wot-thing-description
-
7 issues opened.
-
Semantic information in TDTs w3c/wot-thing-description#898, by @kolotu.
-
TDT shall allow to define placeholders w3c/wot-thing-description#897, by @sebastiankb.
-
PropertyAffordance is missing InteractionAffordance properties in the published JSON-LD context w3c/wot-thing-description#894, by @RoboPhred.
-
Evaluate AsyncAPI w3c/wot-thing-description#893, by @egekorkan.
-
HTTP Binding for providing historical events. w3c/wot-thing-description#892, by @RoboPhred.
-
[vocabulary] Consider adding keyword to describe synchronous actions w3c/wot-thing-description#890, by @egekorkan.
-
Add 'minLength' and 'maxLength' to StringSchema w3c/wot-thing-description#889, by @RoboPhred.
-
-
1 issue closed.
-
[Editorial] Example 32 has a non functioning button w3c/wot-thing-description#842.
-
-
11 issues received 51 new comments.
-
HTTP Binding for providing historical events. w3c/wot-thing-description#892 (16 comments by @benfrancis, @egekorkan, @RoboPhred, @zolkis)
-
Add 'minLength' and 'maxLength' to StringSchema w3c/wot-thing-description#889 (8 comments by @egekorkan, @RoboPhred, @sebastiankb)
-
TDT shall allow to define placeholders w3c/wot-thing-description#897 (7 comments by @benfrancis, @egekorkan, @relu91, @sebastiankb)
-
[vocabulary] Consider adding keyword to describe synchronous actions w3c/wot-thing-description#890 (6 comments by @benfrancis, @egekorkan, @sebastiankb)
-
Describing common event subscription pattern such as subscriptionId w3c/wot-thing-description#887 (5 comments by @mlagally, @sebastiankb, @takuki)
-
[Editorial] Example 32 has a non functioning button w3c/wot-thing-description#842 (3 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
import/extend functionality in TD w3c/wot-thing-description#168 (2 comments by @kolotu, @sebastiankb)
-
PropertyAffordance is missing InteractionAffordance properties in the published JSON-LD context w3c/wot-thing-description#894 (1 comment by @RoboPhred)
-
[question][behavior][testing] Should writing to an observable property trigger new values being pushed w3c/wot-thing-description#888 (1 comment by @takuki)
-
-
3 pull requests opened.
-
WIP: Introduce minLength, maxLength, multipleOf, contentEncoding and contentMediaType in JSON Schema Ontology w3c/wot-thing-description#896, by @sebastiankb.
-
Update Readme w3c/wot-thing-description#895, by @Web-of-Things.
-
fix: issue 842 w3c/wot-thing-description#891, by @danielpeintner.
-
-
1 pull request merged.
-
fix: issue 842 w3c/wot-thing-description#891.
-
-
1 pull request closed.
-
Update Readme w3c/wot-thing-description#895.
-
-
1 pull request received 1 new comment.
w3c/wot-security
-
2 issues opened.
-
Add "Security and Privacy Considerations" to all use cases (or requirements) w3c/wot-security#168, by @mmccool.
-
Review Scripting API to ensure Security configuration is supported w3c/wot-security#167, by @mmccool.
-
-
2 issues closed.
-
Avoid "HTTP(S)"/"HTTPS" and others in this cohort w3c/wot-security#142.
-
Misleading reference [IETFACE] w3c/wot-security#146.
-
-
12 issues received 22 new comments.
-
"Thing authentication" appears fuzzy w3c/wot-security#148 (7 comments by @mlagally, @mmccool, @OliverPfaff, @zolkis)
-
Concept of "end-to-end security" w3c/wot-security#144 (4 comments by @ereshetova, @mmccool, @OliverPfaff)
-
Review Scripting API to ensure Security configuration is supported w3c/wot-security#167 (2 comments by @mmccool, @zolkis)
-
Add "Security and Privacy Considerations" to all use cases (or requirements) w3c/wot-security#168 (1 comment by @mmccool)
-
Clarify that an Update System is Necessary for Security w3c/wot-security#135 (1 comment by @mmccool)
-
-
1 pull request merged.
-
Elaborated text on end-to-end security w3c/wot-security#164.
-
w3c/wot-scripting-api
-
5 issues opened.
-
Requirements from oAuth 2.0 code flow w3c/wot-scripting-api#214, by @relu91.
-
Should language and encoding be optional InteractionOptions members? w3c/wot-scripting-api#213, by @zolkis.
-
Partial TD validation for input of produce() method w3c/wot-scripting-api#212, by @egekorkan.
-
[ExposedThing] Not possible to handle property observations in Scripting level w3c/wot-scripting-api#211, by @egekorkan.
-
[ExposedThing] Not possible to handle event subscriptions in Scripting level w3c/wot-scripting-api#210, by @egekorkan.
-
-
5 issues received 26 new comments.
-
Partial TD validation for input of produce() method w3c/wot-scripting-api#212 (9 comments by @egekorkan, @relu91, @zolkis)
-
Fix property interaction algorithms to correctly handle Forms, contentType and DataSchema w3c/wot-scripting-api#201 (7 comments by @danielpeintner, @zolkis)
-
[ExposedThing] Not possible to handle event subscriptions in Scripting level w3c/wot-scripting-api#210 (5 comments by @egekorkan, @zolkis)
-
[ExposedThing] Not possible to handle property observations in Scripting level w3c/wot-scripting-api#211 (3 comments by @zolkis)
-
Event Affordance subscription and cancellation payloads are not usable by scripting w3c/wot-scripting-api#208 (2 comments by @egekorkan, @zolkis)
-
-
1 pull request opened.
-
Add InteractionData w3c/wot-scripting-api#209, by @zolkis.
-
-
1 pull request received 9 new comments.
w3c/wot-discovery
-
3 issues opened.
-
Consider TTL Use cases w3c/wot-discovery#18, by @mmccool.
-
Compare Query and Filter approaches w3c/wot-discovery#17, by @mmccool.
-
Handle huge set of Thing Descriptions (pagination, streaming, etc.) w3c/wot-discovery#16, by @sebastiankb.
-
-
1 issue closed.
-
Possible requirement: allow discovery to return metadata in different formats w3c/wot-discovery#14.
-
-
7 issues received 16 new comments.
-
Compare Query and Filter approaches w3c/wot-discovery#17 (7 comments by @egekorkan, @mmccool, @relu91, @sebastiankb, @wiresio)
-
Handle huge set of Thing Descriptions (pagination, streaming, etc.) w3c/wot-discovery#16 (3 comments by @danielpeintner, @egekorkan, @relu91)
-
Possible requirement: allow discovery to return metadata in different formats w3c/wot-discovery#14 (2 comments by @mmccool)
-
Experimental discovery implementation using mDNS, DNS-SD and MongoDB w3c/wot-discovery#5 (1 comment by @mmccool)
-
-
3 pull requests opened.
-
UPM Use Case about Smart Campus w3c/wot-discovery#20, by @AndreaCimminoArriaga.
-
Add Fujitsu's discovery work w3c/wot-discovery#19, by @k-toumura.
-
WIP: Vorto Terminology. #7. w3c/wot-discovery#15, by @kolotu.
-
-
1 pull request merged.
-
Limit scope of use cases to metadata w3c/wot-discovery#12.
-
-
1 pull request closed.
-
WIP: Vorto Terminology. #7. w3c/wot-discovery#15.
-
-
1 pull request received 4 new comments.
w3c/wot-binding-templates
-
4 issues received 10 new comments.
-
Errors in examples w3c/wot-binding-templates#94 (5 comments by @danielpeintner, @egekorkan, @fgrape, @RoboPhred)
-
Create RDF representations of CoAP and MQTT vocabulary w3c/wot-binding-templates#93 (3 comments by @egekorkan, @mmccool, @takuki)
-
Review Comments: W3C Editor's Draft 23 January 2018 w3c/wot-binding-templates#21 (1 comment by @egekorkan)
-
-
1 pull request opened.
-
Fixes for issues #94 and #21 w3c/wot-binding-templates#95, by @egekorkan.
-
-
1 pull request merged.
-
Fixes for issues #94 and #21 w3c/wot-binding-templates#95.
-
-
1 pull request received 5 new comments.
Participants
-
1 participant joined.
-
Scott Rose (National Institute of Standards and Technology (NIST)) joined.
-
-
1 organization joined.
-
National Institute of Standards and Technology (NIST) joined.
-
GitHub
w3c/wot-discovery
-
9 issues opened.
-
Possible requirement: allow discovery to return metadata in different formats w3c/wot-discovery#14, by @mmccool.
-
Explore Eclipse Vorto Interoperability w3c/wot-discovery#13, by @mmccool.
-
Update Two-Phase architecture description w3c/wot-discovery#11, by @mmccool.
-
Reorganize Prior work w3c/wot-discovery#10, by @mmccool.
-
Create structure to organize PoCs w3c/wot-discovery#9, by @mmccool.
-
Define a concrete network API for a TD Directory service w3c/wot-discovery#8, by @mmccool.
-
Align Terminology and Semantics with Eclipse Vorto w3c/wot-discovery#7, by @mmccool.
-
Index prior work w3c/wot-discovery#6, by @mmccool.
-
Experimental discovery implementation using mDNS, DNS-SD and MongoDB w3c/wot-discovery#5, by @tksuzuki0604.
-
-
5 issues received 11 new comments.
-
Align Terminology and Semantics with Eclipse Vorto w3c/wot-discovery#7 (3 comments by @kolotu, @mjkoster, @mmccool)
-
Experimental discovery implementation using mDNS, DNS-SD and MongoDB w3c/wot-discovery#5 (3 comments by @k-toumura, @tksuzuki0604)
-
Define a concrete network API for a TD Directory service w3c/wot-discovery#8 (2 comments by @mmccool, @vcharpenay)
-
-
2 pull requests opened.
-
Limit scope of use cases to metadata w3c/wot-discovery#12, by @mmccool.
-
Restructure Use Cases w3c/wot-discovery#4, by @wiresio.
-
-
1 pull request merged.
-
Restructure Use Cases w3c/wot-discovery#4.
-
-
1 pull request received 1 new comment.
w3c/wot-thing-description
-
3 issues opened.
-
[question][behavior][testing] Should writing to an observable property trigger new values being pushed w3c/wot-thing-description#888, by @egekorkan.
-
Describing common event subscription pattern such as subscriptionId w3c/wot-thing-description#887, by @danielpeintner.
-
Efficient formats for TD w3c/wot-thing-description#885, by @takuki.
-
-
2 issues closed.
-
Giving credit to editors and contributors of the implementation report w3c/wot-thing-description#882.
-
Make a request for TD media type registration at IANA w3c/wot-thing-description#560.
-
-
8 issues received 31 new comments.
-
Describing initial connection w3c/wot-thing-description#878 (6 comments by @benfrancis, @egekorkan, @sebastiankb)
-
id field in TD Templates w3c/wot-thing-description#593 (5 comments by @mlagally, @sebastiankb, @zolkis)
-
How do you cancel or query the state of an action request? w3c/wot-thing-description#302 (5 comments by @benfrancis, @egekorkan, @sebastiankb, @takuki)
-
Giving credit to editors and contributors of the implementation report w3c/wot-thing-description#882 (5 comments by @egekorkan, @mryuichi, @takuki)
-
Describing common event subscription pattern such as subscriptionId w3c/wot-thing-description#887 (4 comments by @danielpeintner, @egekorkan, @zolkis)
-
Make a request for TD media type registration at IANA w3c/wot-thing-description#560 (2 comments by @sebastiankb)
-
-
2 pull requests opened.
-
Added appendix section "Changes from Proposed Recommendation". w3c/wot-thing-description#886, by @takuki.
-
Giving credit to editors and contributors of the implementation report. w3c/wot-thing-description#884, by @takuki.
-
-
2 pull requests merged.
-
Added appendix section "Changes from Proposed Recommendation". w3c/wot-thing-description#886.
-
Giving credit to editors and contributors of the implementation report. w3c/wot-thing-description#884.
-
-
2 pull requests received 5 new comments.
-
[WIP] feat: add content type tables with data schema w3c/wot-thing-description#869 (4 comments by @egekorkan, @handrews, @relu91, @zolkis)
-
Giving credit to editors and contributors of the implementation report. w3c/wot-thing-description#884 (1 comment by @takuki)
-
w3c/wot-security
-
2 issues opened.
-
Add integrity protection (proof section) to TDs w3c/wot-security#166, by @mmccool.
-
Re-introduce OAuth2 Security Scheme to TD w3c/wot-security#165, by @mmccool.
-
-
1 issue closed.
-
Scripting API for Discovery should Mitigate location fingerprinting w3c/wot-security#160.
-
-
5 issues received 10 new comments.
-
Scripting API for Discovery should Mitigate location fingerprinting w3c/wot-security#160 (3 comments by @mmccool)
-
Consider using DIDs to refer to public keys and authentication w3c/wot-security#161 (2 comments by @mmccool)
-
-
2 pull requests opened.
-
Elaborated text on end-to-end security w3c/wot-security#164, by @OliverPfaff.
-
Update Master to Working w3c/wot-security#163, by @mmccool.
-
-
2 pull requests merged.
-
Update Master to Working w3c/wot-security#163.
-
Working Branch Update and Repo Reorg w3c/wot-security#162.
-
-
1 pull request closed.
-
Made a text proposal for E2E security w3c/wot-security#159.
-
-
2 pull requests received 9 new comments.
w3c/wot-architecture
-
10 issues opened.
-
Review/reconcile Anima terminology with lifecycle diagram w3c/wot-architecture#474, by @mmccool.
-
Update lifecycle UC: Include references to diagram and presentation w3c/wot-architecture#473, by @mlagally.
-
Transportation use case w3c/wot-architecture#469, by @zolkis.
-
Improve Use Case Template w3c/wot-architecture#462, by @mlagally.
-
Agriculture use case w3c/wot-architecture#461, by @mlagally.
-
Smart Grid Use Case w3c/wot-architecture#460, by @mlagally.
-
Cross check terminology of stakeholders with DID w3c/wot-architecture#455, by @mlagally.
-
Define terminology Thing Template w3c/wot-architecture#454, by @mlagally.
-
Create terminology definition for "partial TD" w3c/wot-architecture#453, by @mlagally.
-
Improve integration of use case section and structure of normative sections w3c/wot-architecture#446, by @mlagally.
-
-
2 issues closed.
-
Video, Audio treatment w3c/wot-architecture#8.
-
Retail use case w3c/wot-architecture#440.
-
-
8 issues received 39 new comments.
-
Define terminology Thing Template w3c/wot-architecture#454 (27 comments by @danielpeintner, @egekorkan, @mlagally, @relu91, @sebastiankb, @zolkis)
-
Create terminology definition for "partial TD" w3c/wot-architecture#453 (4 comments by @mlagally, @sebastiankb, @zolkis)
-
Update lifecycle UC: Include references to diagram and presentation w3c/wot-architecture#473 (1 comment by @mlagally)
-
Improve integration of use case section and structure of normative sections w3c/wot-architecture#446 (1 comment by @mlagally)
-
-
12 pull requests opened.
-
Create a use case of agriculture w3c/wot-architecture#471, by @mryuichi.
-
Add Transportation use case w3c/wot-architecture#470, by @zolkis.
-
Add public health monitoring use case, update geolocation - Smart City domain w3c/wot-architecture#468, by @mmccool.
-
Update lifecycle diagram to the latest version w3c/wot-architecture#467, by @ereshetova.
-
Updating WoT lifecycle diagram with latest version w3c/wot-architecture#466, by @ereshetova.
-
Update use-case-template.md w3c/wot-architecture#464, by @mlagally.
-
Delete use-case-example.md w3c/wot-architecture#463, by @mlagally.
-
Update change log and specStatus to REC w3c/wot-architecture#451, by @mlagally.
-
fix font problems in overview diagram w3c/wot-architecture#450, by @k-toumura.
-
Updates to overview images for press release w3c/wot-architecture#449, by @mmccool.
-
Create govtech-gps-module.md w3c/wot-architecture#448, by @mlagally.
-
Create retail.md w3c/wot-architecture#447, by @mlagally.
-
-
9 pull requests merged.
-
Update lifecycle diagram to the latest version w3c/wot-architecture#467.
-
Update use-case-template.md w3c/wot-architecture#464.
-
Delete use-case-example.md w3c/wot-architecture#463.
-
Create X-Protocol Interworking.md w3c/wot-architecture#431.
-
Create govtech-gps-module.md w3c/wot-architecture#448.
-
fix font problems in overview diagram w3c/wot-architecture#450.
-
Create retail.md w3c/wot-architecture#447.
-
Updates to overview images for press release w3c/wot-architecture#449.
-
fix Figure 18 w3c/wot-architecture#445.
-
-
2 pull requests closed.
-
Updating WoT lifecycle diagram with latest version w3c/wot-architecture#466.
-
Update change log and specStatus to REC w3c/wot-architecture#451.
-
-
4 pull requests received 13 new comments.
-
Add public health monitoring use case, update geolocation - Smart City domain w3c/wot-architecture#468 (8 comments by @mlagally)
-
w3c/wot-scripting-api
-
1 issue opened.
-
Event Affordance subscription and cancellation payloads are not usable by scripting w3c/wot-scripting-api#208, by @egekorkan.
-
-
1 issue reopened.
-
Produce() method should ignore instance specific information w3c/wot-scripting-api#156, by @zolkis.
-
-
3 issues received 14 new comments.
-
Produce() method should ignore instance specific information w3c/wot-scripting-api#156 (8 comments by @danielpeintner, @egekorkan, @zolkis)
-
Event Affordance subscription and cancellation payloads are not usable by scripting w3c/wot-scripting-api#208 (3 comments by @egekorkan, @zolkis)
-
-
1 pull request opened.
-
Editorial changes w3c/wot-scripting-api#207, by @zolkis.
-
-
1 pull request merged.
-
Editorial changes w3c/wot-scripting-api#207.
-
-
1 pull request received 3 new comments.
w3c/wot-binding-templates
-
1 issue opened.
-
Errors in examples w3c/wot-binding-templates#94, by @fgrape.
-
GitHub
w3c/wot-thing-description
-
4 issues opened.
-
Automate running TD rendering script w3c/wot-thing-description#883, by @danielpeintner.
-
Giving credit to editors and contributors of the implementation report w3c/wot-thing-description#882, by @egekorkan.
-
Describing initial connection w3c/wot-thing-description#878, by @egekorkan.
-
No mechanism to indicate the "desired" form entry w3c/wot-thing-description#877, by @danielpeintner.
-
-
1 issue closed.
-
[Editorial] Implementation report uses non-static links and missing contributor w3c/wot-thing-description#851.
-
-
10 issues received 28 new comments.
-
How do you cancel or query the state of an action request? w3c/wot-thing-description#302 (7 comments by @benfrancis, @egekorkan, @mlagally, @sebastiankb, @takuki, @zolkis)
-
Describing initial connection w3c/wot-thing-description#878 (6 comments by @benfrancis, @egekorkan, @mjkoster, @sebastiankb, @zolkis)
-
Clarifying how readmultipleproperties work w3c/wot-thing-description#848 (3 comments by @egekorkan, @takuki, @zolkis)
-
Clarify read-only/write-only behavior w3c/wot-thing-description#854 (3 comments by @takuki, @zolkis)
-
No mechanism to indicate the "desired" form entry w3c/wot-thing-description#877 (3 comments by @mmccool, @takuki, @zolkis)
-
[Editorial] Implementation report uses non-static links and missing contributor w3c/wot-thing-description#851 (2 comments by @takuki)
-
[Editorial] Example 32 has a non functioning button w3c/wot-thing-description#842 (1 comment by @takuki)
-
Should it be possible to indicate whether writing a property returns set value? w3c/wot-thing-description#875 (1 comment by @takuki)
-
-
3 pull requests opened.
-
A note in section 6.4 Identification should be removed w3c/wot-thing-description#881, by @takuki.
-
provide CoAP content-format id 432 in the TD spec w3c/wot-thing-description#880, by @sebastiankb.
-
Fix typo in validation schema w3c/wot-thing-description#879, by @egekorkan.
-
-
4 pull requests merged.
-
provide CoAP content-format id 432 in the TD spec w3c/wot-thing-description#880.
-
A note in section 6.4 Identification should be removed w3c/wot-thing-description#881.
-
chore: fix ReSpec errors w3c/wot-thing-description#872.
-
Fix typo in validation schema w3c/wot-thing-description#879.
-
-
1 pull request reopened.
-
chore: fix ReSpec errors w3c/wot-thing-description#872, by @sidvishnoi.
-
-
3 pull requests received 13 new comments.
-
chore: fix ReSpec errors w3c/wot-thing-description#872 (11 comments by @ashimura, @saschanaz, @sebastiankb, @sidvishnoi, @takuki)
-
A note in section 6.4 Identification should be removed w3c/wot-thing-description#881 (1 comment by @takuki)
-
provide CoAP content-format id 432 in the TD spec w3c/wot-thing-description#880 (1 comment by @sebastiankb)
-
w3c/wot-architecture
-
2 issues opened.
-
Retail use case w3c/wot-architecture#440, by @mlagally.
-
Editorial issues on PR w3c/wot-architecture#437, by @mryuichi.
-
-
1 issue closed.
-
Digital Twin Use Case w3c/wot-architecture#426.
-
-
4 issues received 7 new comments.
-
More clearly define "Thing Authentication" w3c/wot-architecture#429 (3 comments by @mjkoster, @mlagally)
-
Give basic definition of "End-to-End Security" w3c/wot-architecture#430 (2 comments by @mjkoster, @mlagally)
-
-
6 pull requests opened.
-
fix Figure 18 w3c/wot-architecture#445, by @k-toumura.
-
Update diagram for press release w3c/wot-architecture#444, by @mlagally.
-
Presentations on DID w3c/wot-architecture#441, by @mmccool.
-
Minor editorial changes to address #1 and #2 of https://github.com/w3c/wot-architecture/issues/437 w3c/wot-architecture#439, by @mlagally.
-
Add presentation on device lifecycle models w3c/wot-architecture#434, by @zolkis.
-
Create X-Protocol Interworking.md w3c/wot-architecture#431, by @mlagally.
-
-
6 pull requests merged.
-
Update diagram for press release w3c/wot-architecture#444.
-
Presentations on DID w3c/wot-architecture#441.
-
Minor editorial changes to address #1 and #2 of https://github.com/w3c/wot-architecture/issues/437 w3c/wot-architecture#439.
-
Digital Twin Use Case + editorial cleanup w3c/wot-architecture#428.
-
Add presentation on device lifecycle models w3c/wot-architecture#434.
-
MMI Use Cases w3c/wot-architecture#424.
-
-
3 pull requests received 14 new comments.
-
Create X-Protocol Interworking.md w3c/wot-architecture#431 (11 comments by @egekorkan, @mlagally, @zolkis)
-
Minor editorial changes to address #1 and #2 of https://github.com/w3c/wot-architecture/issues/437 w3c/wot-architecture#439 (2 comments by @mlagally)
-
w3c/wot-security
-
2 issues opened.
-
Consider using DIDs to refer to public keys and authentication w3c/wot-security#161, by @mmccool.
-
Scripting API for Discovery should Mitigate location fingerprinting w3c/wot-security#160, by @mmccool.
-
-
4 issues closed.
-
Nesting security metadata in TD w3c/wot-security#56.
-
Blockchains for WoT w3c/wot-security#52.
-
Make links to the standard security terms w3c/wot-security#45.
-
-
15 issues received 20 new comments.
-
Scripting API for Discovery should Mitigate location fingerprinting w3c/wot-security#160 (2 comments by @zolkis)
-
Study more related standards & methods for authentication & authorization w3c/wot-security#54 (2 comments by @mmccool)
-
Document network reachability requirements for security schemes w3c/wot-security#55 (1 comment by @mmccool)
-
Authorization and minimizing access to TD in Things directory w3c/wot-security#53 (1 comment by @mmccool)
-
Align Security and Privacy Considerations section of Architecture CR with wot-security w3c/wot-security#35 (1 comment by @mmccool)
-
1 pull request opened.
-
Working Branch Update and Repo Reorg w3c/wot-security#162, by @mmccool.
-
-
4 pull requests merged.
-
HTTPS => HTTP-over-TLS etc. (Issue#142) w3c/wot-security#158.
-
HTTPS => HTTPS-over-TLS etc (Issue#142) w3c/wot-security#157.
-
Wording change (IETF ACE WG) w3c/wot-security#156.
-
an initial attempt on security provisioning section w3c/wot-security#150.
-
-
1 pull request closed.
-
Delete empty line (no content change; testing only) w3c/wot-security#155.
-
-
2 pull requests received 6 new comments.
w3c/wot-scripting-api
-
2 issues opened.
-
Clarify Discovery API scope w3c/wot-scripting-api#206, by @zolkis.
-
Extend API with semantic capabilities w3c/wot-scripting-api#204, by @danielpeintner.
-
-
2 issues closed.
-
setPropertyWriteHandler() gives impression that all properties will be writeable w3c/wot-scripting-api#199.
-
Define InteractionOptions for Scripting w3c/wot-scripting-api#202.
-
-
6 issues received 15 new comments.
-
Should writeProperty() return a value w3c/wot-scripting-api#193 (5 comments by @danielpeintner, @mmccool)
-
Fix property interaction algorithms to correctly handle Forms, contentType and DataSchema w3c/wot-scripting-api#201 (2 comments by @danielpeintner, @zolkis)
-
-
2 pull requests opened.
-
Returning values from writes w3c/wot-scripting-api#205, by @zolkis.
-
Fix markdown, add formIndex, explain write handlers w3c/wot-scripting-api#203, by @zolkis.
-
-
2 pull requests merged.
-
Returning values from writes w3c/wot-scripting-api#205.
-
Fix markdown, add formIndex, explain write handlers w3c/wot-scripting-api#203.
-
-
2 pull requests received 4 new comments.
-
Fix markdown, add formIndex, explain write handlers w3c/wot-scripting-api#203 (1 comment by @zolkis)
w3c/wot-discovery
-
2 issues opened.
-
Add DID to background.md w3c/wot-discovery#3, by @mmccool.
-
Privacy risk in Introduction Phase: location inferencing from list of directory services w3c/wot-discovery#2, by @mmccool.
-
-
1 pull request opened.
-
Move existing proposal from wot repo, reorganize w3c/wot-discovery#1, by @mmccool.
-
-
1 pull request merged.
-
Move existing proposal from wot repo, reorganize w3c/wot-discovery#1.
-
w3c/wot-binding-templates
-
4 issues opened.
-
Create RDF representations of CoAP and MQTT vocabulary w3c/wot-binding-templates#93, by @egekorkan.
-
Identifying next protocols to work w3c/wot-binding-templates#92, by @egekorkan.
-
Using JSON Hyper Schema w3c/wot-binding-templates#91, by @egekorkan.
-
CSS sizing properties typo? w3c/wot-binding-templates#90, by @Zurc.
-
-
8 issues closed.
-
How does a Protocol Binding represent an item which is created as a result of an interaction w3c/wot-binding-templates#15.
-
Start list of protocols and platform dialects to describe w3c/wot-binding-templates#1.
-
What are priorities for the next revision, next plugfest w3c/wot-binding-templates#41.
-
Use cases and requirements for protocol binding w3c/wot-binding-templates#3.
-
Binding for next PlugFest (Prague 2018) w3c/wot-binding-templates#13.
-
Clarifying the scope and motivation for binding templates w3c/wot-binding-templates#6.
-
Structure of protocol binding block and terminology w3c/wot-binding-templates#2.
-
CSS sizing properties typo? w3c/wot-binding-templates#90.
-
-
11 issues received 13 new comments.
-
Create RDF representations of CoAP and MQTT vocabulary w3c/wot-binding-templates#93 (1 comment by @sebastiankb)
-
How does a Protocol Binding represent an item which is created as a result of an interaction w3c/wot-binding-templates#15 (1 comment by @egekorkan)
-
Start list of protocols and platform dialects to describe w3c/wot-binding-templates#1 (1 comment by @egekorkan)
-
What are priorities for the next revision, next plugfest w3c/wot-binding-templates#41 (1 comment by @egekorkan)
-
Use cases and requirements for protocol binding w3c/wot-binding-templates#3 (1 comment by @egekorkan)
-
Clarifying the scope and motivation for binding templates w3c/wot-binding-templates#6 (1 comment by @egekorkan)
-
Structure of protocol binding block and terminology w3c/wot-binding-templates#2 (1 comment by @egekorkan)
Lifecycle
-
1 charter started.
-
Chartered until 31 January 2022.
-
TR publications
-
3 documents published.
-
Web of Things (WoT) Architecture published as a Proposed Recommendation. History of Web of Things (WoT) Architecture
-
Web of Things (WoT) Thing Description published as a Proposed Recommendation. History of Web of Things (WoT) Thing Description
-
Web of Things (WoT) Binding Templates published as a Note. History of Web of Things (WoT) Binding Templates
-
Participants
-
1 participant joined.
-
Andrea Cimmino (Universidad Politécnica de Madrid) joined.
-
-
1 participant left.
-
Fernando Serena (Universidad Politécnica de Madrid) left.
-
GitHub
w3c/wot-binding-templates
-
2 issues opened.
-
Use "Consumer/Thing" rather than "WoT Client/Server" w3c/wot-binding-templates#89, by @k-toumura.
-
Review Comments - Binding Templates - W3C Editor's Draft 22 December 2019 w3c/wot-binding-templates#87, by @danielpeintner.
-
-
4 issues closed.
-
Review Comments - Binding Templates - W3C Editor's Draft 22 December 2019 w3c/wot-binding-templates#87.
-
Use "Consumer/Thing" rather than "WoT Client/Server" w3c/wot-binding-templates#89.
-
Fixing CoAP vocabulary w3c/wot-binding-templates#81.
-
Meta-interaction is missing from section 2.3 Interaction Types w3c/wot-binding-templates#59.
-
-
7 issues received 14 new comments.
-
Review Comments - Binding Templates - W3C Editor's Draft 22 December 2019 w3c/wot-binding-templates#87 (4 comments by @egekorkan)
-
Use "Consumer/Thing" rather than "WoT Client/Server" w3c/wot-binding-templates#89 (3 comments by @egekorkan, @k-toumura)
-
Binding for next PlugFest (Prague 2018) w3c/wot-binding-templates#13 (2 comments by @egekorkan, @handrews)
-
How does a Protocol Binding represent an item which is created as a result of an interaction w3c/wot-binding-templates#15 (1 comment by @egekorkan)
-
Meta-interaction is missing from section 2.3 Interaction Types w3c/wot-binding-templates#59 (1 comment by @egekorkan)
-
-
1 pull request opened.
-
Fixes after reviews w3c/wot-binding-templates#88, by @egekorkan.
-
-
1 pull request merged.
-
Fixes after reviews w3c/wot-binding-templates#88.
-
-
1 pull request received 2 new comments.
w3c/wot-security
-
2 issues opened.
-
Review IETF MUD draft specification and consider WoT alignment w3c/wot-security#153, by @mmccool.
-
Review PING's Privacy Threat Model draft w3c/wot-security#152, by @mmccool.
-
-
2 issues closed.
-
Review Privacy Mitigations for TD ids and fingerprinting w3c/wot-security#136.
-
Align Security and Privacy Considerations section of Architecture CR with wot-security w3c/wot-security#125.
-
-
10 issues received 20 new comments.
-
Best Security Practices for Client/Server vs. PublishSubscribe Patterns w3c/wot-security#145 (3 comments by @mmccool, @OliverPfaff)
-
Align stakeholders with architecture w3c/wot-security#151 (3 comments by @ereshetova, @mmccool, @zolkis)
-
Avoid "HTTP(S)"/"HTTPS" and others in this cohort w3c/wot-security#142 (2 comments by @mmccool, @OliverPfaff)
-
Review Privacy Mitigations for TD ids and fingerprinting w3c/wot-security#136 (1 comment by @mmccool)
-
Align Security and Privacy Considerations section of Architecture CR with wot-security w3c/wot-security#125 (1 comment by @mmccool)
-
6 pull requests opened.
-
Made a text proposal for E2E security w3c/wot-security#159, by @OliverPfaff.
-
HTTPS => HTTP-over-TLS etc. (Issue#142) w3c/wot-security#158, by @OliverPfaff.
-
HTTPS => HTTPS-over-TLS etc (Issue#142) w3c/wot-security#157, by @OliverPfaff.
-
Wording change (IETF ACE WG) w3c/wot-security#156, by @OliverPfaff.
-
Delete empty line (no content change; testing only) w3c/wot-security#155, by @OliverPfaff.
-
Removed trailing empty line (testing-only) w3c/wot-security#154, by @OliverPfaff.
-
-
1 pull request closed.
-
Removed trailing empty line (testing-only) w3c/wot-security#154.
-
-
1 pull request received 1 new comment.
w3c/wot-thing-description
-
1 issue opened.
-
Should it be possible to indicate whether writing a property returns set value? w3c/wot-thing-description#875, by @danielpeintner.
-
-
1 issue closed.
-
"anchor" needs an example w3c/wot-thing-description#477.
-
-
7 issues received 18 new comments.
-
Should it be possible to indicate whether writing a property returns set value? w3c/wot-thing-description#875 (6 comments by @danielpeintner, @egekorkan, @sebastiankb, @zolkis)
-
Consider to cross reference JSON Schema definitions (external or internal) w3c/wot-thing-description#604 (4 comments by @egekorkan, @handrews)
-
How do you cancel or query the state of an action request? w3c/wot-thing-description#302 (3 comments by @vcharpenay)
-
Make a request for TD media type registration at IANA w3c/wot-thing-description#560 (1 comment by @sebastiankb)
-
Is the use of "$ref" and "definitions" allowed in TD ? w3c/wot-thing-description#307 (1 comment by @vcharpenay)
-
-
3 pull requests opened.
-
Remove `format: markdown` w3c/wot-thing-description#876, by @saschanaz.
-
Address feedback from IANA w3c/wot-thing-description#874, by @sebastiankb.
-
update eventSource reference to html w3c/wot-thing-description#873, by @sebastiankb.
-
-
2 pull requests merged.
-
Address feedback from IANA w3c/wot-thing-description#874.
-
update eventSource reference to html w3c/wot-thing-description#873.
-
-
1 pull request closed.
-
Remove `format: markdown` w3c/wot-thing-description#876.
-
-
6 pull requests received 11 new comments.
-
chore: fix ReSpec errors w3c/wot-thing-description#872 (5 comments by @saschanaz, @sidvishnoi, @takuki)
-
w3c/wot-thing-description#840 (1 comment by @takuki)
-
w3c/wot-thing-description#871 (1 comment by @takuki)
-
w3c/wot-architecture
-
4 issues opened.
-
Give basic definition of "End-to-End Security" w3c/wot-architecture#430, by @mmccool.
-
More clearly define "Thing Authentication" w3c/wot-architecture#429, by @mmccool.
-
Digital Twin Use Case w3c/wot-architecture#426, by @mlagally.
-
Possible typos w3c/wot-architecture#420, by @shujikamitsuna.
-
-
3 issues received 4 new comments.
-
[question] Is the servient a hypervisor or single application vm? w3c/wot-architecture#417 (2 comments by @mlagally, @relu91)
-
-
5 pull requests opened.
-
Digital Twin Use Case + editorial cleanup w3c/wot-architecture#428, by @mlagally.
-
MMI Use Cases w3c/wot-architecture#424, by @mmccool.
-
Adding Big Data Usecase w3c/wot-architecture#422, by @mlagally.
-
Editorial fixes for PR w3c/wot-architecture#421, by @mlagally.
-
update eventSource reference to HTML w3c/wot-architecture#419, by @mlagally.
-
-
4 pull requests merged.
-
Adding Big Data Usecase w3c/wot-architecture#422.
-
Move stakeholder terms from security doc w3c/wot-architecture#418.
-
Editorial fixes for PR w3c/wot-architecture#421.
-
update eventSource reference to HTML w3c/wot-architecture#419.
-
-
1 pull request received 1 new comment.
w3c/wot-scripting-api
-
2 issues opened.
-
Define InteractionOptions for Scripting w3c/wot-scripting-api#202, by @zolkis.
-
Fix property interaction algorithms to correctly handle Forms, contentType and DataSchema w3c/wot-scripting-api#201, by @zolkis.
-
-
1 issue closed.
-
*Soften* statements "value MUST be JSON" w3c/wot-scripting-api#198.
-
-
4 issues received 11 new comments.
-
Fix property interaction algorithms to correctly handle Forms, contentType and DataSchema w3c/wot-scripting-api#201 (4 comments by @egekorkan, @zolkis)
-
setPropertyWriteHandler() gives impression that all properties will be writeable w3c/wot-scripting-api#199 (3 comments by @egekorkan, @zolkis)
-