Web of Things Working Group - Activity in 2019
No matches.
Lifecycle
-
1 charter extension.
-
Charter extended until 31 January 2020.
-
GitHub
w3c/wot-thing-description
-
4 issues opened.
-
Update ontology files on github.io and w3.org w3c/wot-thing-description#868, by @vcharpenay.
-
Test updated JSON Schema with at-risk items removed w3c/wot-thing-description#858, by @mmccool.
-
Figures need to remove at-risk items for PR w3c/wot-thing-description#857, by @mmccool.
-
Clarify read-only/write-only behavior w3c/wot-thing-description#854, by @mlagally.
-
-
12 issues closed.
-
Update ontology files on github.io and w3.org w3c/wot-thing-description#868.
-
rules and test suite for conversion between JSON schema and RDF w3c/wot-thing-description#804.
-
Move MQTT (and CoAP) example to Protocol Binding Templates document w3c/wot-thing-description#786.
-
(Minor) CR2 Release Candidate comments w3c/wot-thing-description#833.
-
Figures need to remove at-risk items for PR w3c/wot-thing-description#857.
-
Test updated JSON Schema with at-risk items removed w3c/wot-thing-description#858.
-
Explainer: Mention alternative rejected solutions w3c/wot-thing-description#788.
-
Handle at risk features before publishing as proposed rec w3c/wot-thing-description#789.
-
Reference to semantic processing w3c/wot-thing-description#846.
-
Clarifying default bindings for all op values w3c/wot-thing-description#843.
-
Clarify read/writeXproperties in case readOnly or writeOnly properties w3c/wot-thing-description#845.
-
[question] Protocol bindings for read/writeXproperties w3c/wot-thing-description#844.
-
-
20 issues received 62 new comments.
-
Update ontology files on github.io and w3.org w3c/wot-thing-description#868 (8 comments by @ashimura, @mmccool, @vcharpenay)
-
[Editorial] Example 32 has a non functioning button w3c/wot-thing-description#842 (7 comments by @ashimura, @danielpeintner, @mmccool, @sebastiankb, @vcharpenay)
-
Make a request for TD media type registration at IANA w3c/wot-thing-description#560 (5 comments by @ektrah, @mmccool, @plehegar, @sebastiankb)
-
rules and test suite for conversion between JSON schema and RDF w3c/wot-thing-description#804 (5 comments by @mmccool, @rob-metalinkage, @sebastiankb, @vcharpenay)
-
Move MQTT (and CoAP) example to Protocol Binding Templates document w3c/wot-thing-description#786 (5 comments by @egekorkan, @sebastiankb)
-
Test updated JSON Schema with at-risk items removed w3c/wot-thing-description#858 (4 comments by @egekorkan, @sebastiankb)
-
Clarifying how readmultipleproperties work w3c/wot-thing-description#848 (4 comments by @egekorkan, @sebastiankb)
-
Figures need to remove at-risk items for PR w3c/wot-thing-description#857 (3 comments by @sebastiankb, @vcharpenay)
-
[At-Risk] Implementations of OAuth2SecurityScheme needed w3c/wot-thing-description#730 (2 comments by @sebastiankb)
-
Handle at risk features before publishing as proposed rec w3c/wot-thing-description#789 (2 comments by @sebastiankb)
-
Improve Explainer with User-Oriented Use Cases w3c/wot-thing-description#805 (2 comments by @sebastiankb)
-
Clarifying default bindings for all op values w3c/wot-thing-description#843 (2 comments by @egekorkan, @sebastiankb)
-
Clarify read/writeXproperties in case readOnly or writeOnly properties w3c/wot-thing-description#845 (2 comments by @mlagally, @sebastiankb)
-
[question] Protocol bindings for read/writeXproperties w3c/wot-thing-description#844 (2 comments by @egekorkan, @sebastiankb)
-
[Editorial] Implementation report uses non-static links and missing contributor w3c/wot-thing-description#851 (2 comments by @egekorkan, @sebastiankb)
-
Explainer: Mention alternative rejected solutions w3c/wot-thing-description#788 (1 comment by @sebastiankb)
-
Clarify InteractionAffordance::contentType vs DataSchema::type w3c/wot-thing-description#839 (1 comment by @sebastiankb)
-
-
15 pull requests opened.
-
chore: fix ReSpec errors w3c/wot-thing-description#872, by @sidvishnoi.
-
Updated Change Log section for transition to Proposed Recommendation. w3c/wot-thing-description#870, by @takuki.
-
[WIP] feat: add content type tables with data schema w3c/wot-thing-description#869, by @danielpeintner.
-
WIP: Fix #839: Clarify DataSchema vs contentType w3c/wot-thing-description#867, by @zolkis.
-
[Editorial] Update URL of Node Generator repository in Implementation Report w3c/wot-thing-description#866, by @k-toumura.
-
rename brighness to illuminance w3c/wot-thing-description#865, by @sebastiankb.
-
update uri to iri w3c/wot-thing-description#864, by @egekorkan.
-
update validation schema w3c/wot-thing-description#863, by @egekorkan.
-
update mqtt coap example w3c/wot-thing-description#862, by @sebastiankb.
-
Change Dereferencing to Fetch in Privacy considerations section w3c/wot-thing-description#861, by @mmccool.
-
Change OAuth2 flow to use "e.g." instead of "one of" w3c/wot-thing-description#860, by @mmccool.
-
Update UML images to remove at-risk security schemes w3c/wot-thing-description#859, by @mmccool.
-
Remove at-risk features and update implementation report for PR transition w3c/wot-thing-description#856, by @mmccool.
-
provide a related work in explainer w3c/wot-thing-description#855, by @sebastiankb.
-
Explanations for meta interactions w3c/wot-thing-description#853, by @egekorkan.
-
-
14 pull requests merged.
-
Updated Change Log section for transition to Proposed Recommendation. w3c/wot-thing-description#870.
-
[Editorial] Update URL of Node Generator repository in Implementation Report w3c/wot-thing-description#866.
-
WIP: Updated RDF vocabularies w3c/wot-thing-description#744.
-
rename brighness to illuminance w3c/wot-thing-description#865.
-
update uri to iri w3c/wot-thing-description#864.
-
update validation schema w3c/wot-thing-description#863.
-
Change Dereferencing to Fetch in Privacy considerations section w3c/wot-thing-description#861.
-
update mqtt coap example w3c/wot-thing-description#862.
-
Change OAuth2 flow to use "e.g." instead of "one of" w3c/wot-thing-description#860.
-
Update UML images to remove at-risk security schemes w3c/wot-thing-description#859.
-
Remove at-risk features and update implementation report for PR transition w3c/wot-thing-description#856.
-
References to semantic processing made consistent (for issue #846) w3c/wot-thing-description#852.
-
Explanations for meta interactions w3c/wot-thing-description#853.
-
provide a related work in explainer w3c/wot-thing-description#855.
-
-
1 pull request closed.
-
WIP: Fix #839: Clarify DataSchema vs contentType w3c/wot-thing-description#867.
-
-
12 pull requests received 25 new comments.
-
Explanations for meta interactions w3c/wot-thing-description#853 (6 comments by @egekorkan, @sebastiankb)
-
Remove at-risk features and update implementation report for PR transition w3c/wot-thing-description#856 (4 comments by @mmccool, @sebastiankb)
-
WIP: Fix #839: Clarify DataSchema vs contentType w3c/wot-thing-description#867 (3 comments by @mmccool, @zolkis)
-
References to semantic processing made consistent (for issue #846) w3c/wot-thing-description#852 (2 comments by @sebastiankb)
-
[WIP] feat: add content type tables with data schema w3c/wot-thing-description#869 (1 comment by @danielpeintner)
-
Change Dereferencing to Fetch in Privacy considerations section w3c/wot-thing-description#861 (1 comment by @sebastiankb)
-
Change OAuth2 flow to use "e.g." instead of "one of" w3c/wot-thing-description#860 (1 comment by @sebastiankb)
-
Update UML images to remove at-risk security schemes w3c/wot-thing-description#859 (1 comment by @sebastiankb)
-
w3c/wot-binding-templates
-
5 issues opened.
-
[MQTT]: Request Response w3c/wot-binding-templates#86, by @egekorkan.
-
[MQTT]: Events with retain w3c/wot-binding-templates#85, by @egekorkan.
-
[MQTT]: Readable but non observable properties w3c/wot-binding-templates#84, by @egekorkan.
-
[MQTT]: Retain true for properties w3c/wot-binding-templates#83, by @egekorkan.
-
Fixing CoAP vocabulary w3c/wot-binding-templates#81, by @egekorkan.
-
-
7 issues closed.
-
observeOnly properties w3c/wot-binding-templates#78.
-
Align Vocabulary tables with TD spec w3c/wot-binding-templates#73.
-
Introduction section structure and content w3c/wot-binding-templates#62.
-
Inputs for MQTT Binding w3c/wot-binding-templates#46.
-
MQTT Vocabulary needs better terms w3c/wot-binding-templates#72.
-
MQTT Vocabulary Option values are unsigned int w3c/wot-binding-templates#74.
-
RDF-compliant inputData/outputData modeling w3c/wot-binding-templates#23.
-
-
10 issues received 12 new comments.
-
Is a binding template specification necessary? w3c/wot-binding-templates#28 (1 comment by @Citrullin)
-
[MQTT]: Readable but non observable properties w3c/wot-binding-templates#84 (1 comment by @egekorkan)
-
MQTT Binding: Describing connection to the broker w3c/wot-binding-templates#14 (1 comment by @egekorkan)
-
1 pull request opened.
-
improve CoAP vocabulary to address #81 w3c/wot-binding-templates#82, by @egekorkan.
-
-
1 pull request merged.
-
improve CoAP vocabulary to address #81 w3c/wot-binding-templates#82.
-
-
1 pull request received 22 new comments.
-
improve CoAP vocabulary to address #81 w3c/wot-binding-templates#82 (22 comments by @egekorkan, @ektrah, @vcharpenay)
-
w3c/wot-architecture
-
2 issues opened.
-
[question] Is the servient a hypervisor or single application vm? w3c/wot-architecture#417, by @relu91.
-
Update change log to match PR transition request w3c/wot-architecture#416, by @mmccool.
-
-
5 issues received 7 new comments.
-
Property affordances claimed to always readable w3c/wot-architecture#412 (3 comments by @egekorkan, @mlagally)
-
[question] Is the servient a hypervisor or single application vm? w3c/wot-architecture#417 (1 comment by @zolkis)
-
-
3 pull requests opened.
-
Move stakeholder terms from security doc w3c/wot-architecture#418, by @ereshetova.
-
PR version w3c/wot-architecture#415, by @mlagally.
-
Moving text and figure on lifecycle from security doc to architecture w3c/wot-architecture#414, by @ereshetova.
-
-
2 pull requests merged.
-
PR version w3c/wot-architecture#415.
-
Moving text and figure on lifecycle from security doc to architecture w3c/wot-architecture#414.
-
-
1 pull request closed.
-
Moving text and figure on lifecycle from security doc to architecture w3c/wot-architecture#413.
-
-
2 pull requests received 5 new comments.
-
Moving text and figure on lifecycle from security doc to architecture w3c/wot-architecture#413 (3 comments by @ereshetova, @mlagally)
-
Moving text and figure on lifecycle from security doc to architecture w3c/wot-architecture#414 (2 comments by @ereshetova, @mlagally)
-
w3c/wot-scripting-api
-
1 issue opened.
-
Error Handling w3c/wot-scripting-api#200, by @danielpeintner.
-
-
2 issues received 5 new comments.
w3c/wot-security
-
1 issue opened.
-
Align stakeholders with architecture w3c/wot-security#151, by @mlagally.
-
-
7 issues received 8 new comments.
-
Consider moving Thing lifecycle discussion to Architecture w3c/wot-security#65 (1 comment by @mmccool)
-
1 pull request received 1 new comment.
TR publications
-
3 documents published.
-
Web of Things (WoT) Architecture published as a Candidate Recommendation Snapshot. History of Web of Things (WoT) Architecture
-
Web of Things (WoT) Thing Description published as a Candidate Recommendation Snapshot. History of Web of Things (WoT) Thing Description
-
Participants
-
1 participant left.
-
Michael Koster (W3C Invited Experts) left.
-
GitHub
w3c/wot-thing-description
-
8 issues opened.
-
[Editorial] Implementation report uses non-static links and missing contributor w3c/wot-thing-description#851, by @egekorkan.
-
Clarifying how readmultipleproperties work w3c/wot-thing-description#848, by @egekorkan.
-
Reference to semantic processing w3c/wot-thing-description#846, by @takuki.
-
Clarify read/writeXproperties in case readOnly or writeOnly properties w3c/wot-thing-description#845, by @egekorkan.
-
[question] Protocol bindings for read/writeXproperties w3c/wot-thing-description#844, by @egekorkan.
-
Clarifying default bindings for all op values w3c/wot-thing-description#843, by @egekorkan.
-
[Editorial] Example 32 has a non functioning button w3c/wot-thing-description#842, by @egekorkan.
-
Add "multipleOf" term to NumberSchema and IntegerSchema w3c/wot-thing-description#841, by @ToruKawaguchi.
-
-
1 issue closed.
-
Move Transformation to RDF (now removed from TD) to TD ontology document w3c/wot-thing-description#787.
-
-
1 issue reopened.
-
(Minor) CR2 Release Candidate comments w3c/wot-thing-description#833, by @danielpeintner.
-
-
11 issues received 33 new comments.
-
Clarify InteractionAffordance::contentType vs DataSchema::type w3c/wot-thing-description#839 (11 comments by @danielpeintner, @egekorkan, @takuki, @zolkis)
-
Add "multipleOf" term to NumberSchema and IntegerSchema w3c/wot-thing-description#841 (4 comments by @egekorkan, @takuki, @ToruKawaguchi)
-
Make a request for TD media type registration at IANA w3c/wot-thing-description#560 (3 comments by @takuki)
-
[question] Protocol bindings for read/writeXproperties w3c/wot-thing-description#844 (3 comments by @egekorkan, @sebastiankb)
-
(Minor) CR2 Release Candidate comments w3c/wot-thing-description#833 (3 comments by @danielpeintner, @mjkoster, @takuki)
-
Clarifying default bindings for all op values w3c/wot-thing-description#843 (2 comments by @sebastiankb)
-
[Editorial] Example 32 has a non functioning button w3c/wot-thing-description#842 (2 comments by @ashimura, @sebastiankb)
-
Clarify read/writeXproperties in case readOnly or writeOnly properties w3c/wot-thing-description#845 (2 comments by @egekorkan, @sebastiankb)
-
extend op options with observeallproperties and observemultipleproperties w3c/wot-thing-description#800 (1 comment by @egekorkan)
-
Move Transformation to RDF (now removed from TD) to TD ontology document w3c/wot-thing-description#787 (1 comment by @takuki)
-
-
4 pull requests opened.
-
References to semantic processing made consistent (for issue #846) w3c/wot-thing-description#852, by @takuki.
-
Fix link of GraphViz w3c/wot-thing-description#850, by @vvenv.
-
fix indent w3c/wot-thing-description#849, by @vvenv.
-
For issue #839 (content type vs data schema) w3c/wot-thing-description#847, by @takuki.
-
-
4 pull requests merged.
-
For issue #839 (content type vs data schema) w3c/wot-thing-description#847.
-
Fix link of GraphViz w3c/wot-thing-description#850.
-
fix indent w3c/wot-thing-description#849.
-
fix: resolves remaining issues in 833 w3c/wot-thing-description#838.
-
-
4 pull requests received 9 new comments.
-
For issue #839 (content type vs data schema) w3c/wot-thing-description#847 (4 comments by @danielpeintner, @sebastiankb, @zolkis)
-
References to semantic processing made consistent (for issue #846) w3c/wot-thing-description#852 (1 comment by @vcharpenay)
-
w3c/wot-security
-
10 issues opened.
-
Add SDO (Secure Device Onboard) Reference w3c/wot-security#149, by @mmccool.
-
"Thing authentication" appears fuzzy w3c/wot-security#148, by @OliverPfaff.
-
Discuss IETF Anima w3c/wot-security#147, by @OliverPfaff.
-
Misleading reference [IETFACE] w3c/wot-security#146, by @OliverPfaff.
-
Best Security Practices for Client/Server vs. PublishSubscribe Patterns w3c/wot-security#145, by @OliverPfaff.
-
Concept of "end-to-end security" w3c/wot-security#144, by @OliverPfaff.
-
Definition of the notion "Privacy" w3c/wot-security#143, by @OliverPfaff.
-
Avoid "HTTP(S)"/"HTTPS" and others in this cohort w3c/wot-security#142, by @OliverPfaff.
-
Describe Proxy as a special case of Intermediary w3c/wot-security#141, by @mmccool.
-
Update Privacy section in guidelines document with new risks w3c/wot-security#140, by @mmccool.
-
-
1 issue closed.
-
Update Definitions of Security and Privacy in Architecture Document w3c/wot-security#134.
-
-
8 issues received 13 new comments.
-
"Thing authentication" appears fuzzy w3c/wot-security#148 (3 comments by @ereshetova, @mmccool, @OliverPfaff)
-
Best Security Practices for Client/Server vs. PublishSubscribe Patterns w3c/wot-security#145 (2 comments by @ereshetova, @mmccool)
-
Update Definitions of Security and Privacy in Architecture Document w3c/wot-security#134 (1 comment by @mmccool)
-
-
2 pull requests opened.
-
an initial attempt on security provisioning section w3c/wot-security#150, by @ereshetova.
-
Add Change Log for Third (and Second) Release w3c/wot-security#139, by @mmccool.
-
-
1 pull request merged.
-
Add Change Log for Third (and Second) Release w3c/wot-security#139.
-
-
1 pull request closed.
-
Change "Local and Remote Proxy" to "Local and Remote Intermediary" w3c/wot-security#137.
-
-
2 pull requests received 3 new comments.
-
Change "Local and Remote Proxy" to "Local and Remote Intermediary" w3c/wot-security#137 (2 comments by @mmccool)
-
w3c/wot-architecture
-
1 issue opened.
-
Property affordances claimed to always readable w3c/wot-architecture#412, by @egekorkan.
-
-
1 pull request opened.
-
Moving text and figure on lifecycle from security doc to architecture w3c/wot-architecture#413, by @ereshetova.
-
-
1 pull request received 1 new comment.
-
Moving text and figure on lifecycle from security doc to architecture w3c/wot-architecture#413 (1 comment by @ereshetova)
-
w3c/wot-binding-templates
-
5 issues received 5 new comments.
-
MQTT Vocabulary Option values are unsigned int w3c/wot-binding-templates#74 (1 comment by @egekorkan)
-
1 pull request opened.
-
improve vocabulary w3c/wot-binding-templates#80, by @egekorkan.
-
-
2 pull requests merged.
-
improve vocabulary w3c/wot-binding-templates#80.
-
Multiple Contributions w3c/wot-binding-templates#79.
-
-
1 pull request received 2 new comments.
w3c/wot-scripting-api
-
1 issue opened.
-
setPropertyWriteHandler() gives impression that all properties will be writeable w3c/wot-scripting-api#199, by @egekorkan.
-
-
2 issues closed.
-
WIP: Implementation experience while realizing new API in node-wot w3c/wot-scripting-api#180.
-
handlers for unobserving property/event missing w3c/wot-scripting-api#183.
-
w3c/wot-profile
-
3 issues received 7 new comments.
-
single profile or smart home + industrial profile w3c/wot-profile#12 (4 comments by @benfrancis, @zolkis)
-
How to support composable "Vertical" vs. "Horizontal" Profiles w3c/wot-profile#8 (2 comments by @benfrancis, @zolkis)
-
TR publications
-
1 document published.
-
Web of Things (WoT) Scripting API published as a Working Draft. History of Web of Things (WoT) Scripting API
-
Participants
-
3 organizations left.
-
Blockstream left.
-
EVRYTHNG left.
-
HTML5 Converged Technology Forum left.
-
GitHub
w3c/wot-profile
-
3 issues received 4 new comments.
-
How to support composable "Vertical" vs. "Horizontal" Profiles w3c/wot-profile#8 (1 comment by @mlagally)
-
1 pull request opened.
-
renames, restructuring w3c/wot-profile#15, by @mlagally.
-
-
1 pull request merged.
-
renames, restructuring w3c/wot-profile#15.
-
w3c/wot-architecture
-
7 issues opened.
-
Section 3. Terminology to be informative w3c/wot-architecture#402, by @ashimura.
-
update change log for CR2 w3c/wot-architecture#401, by @mlagally.
-
Add short mention of ID privacy risk to Architecture Security and Privacy Considerations w3c/wot-architecture#398, by @mmccool.
-
Add definitions of security data/metadata to terminology w3c/wot-architecture#393, by @mlagally.
-
Rename chapter headings as described in https://github.com/w3c/wot-architecture/issues/390 w3c/wot-architecture#392, by @mlagally.
-
Add introduction section as described in https://github.com/w3c/wot-architecture/issues/390 w3c/wot-architecture#391, by @mlagally.
-
Document lacks sufficient detail to understand how privacy-sensitive information flows through the system w3c/wot-architecture#390, by @pes10k.
-
-
14 issues closed.
-
Section 3. Terminology to be informative w3c/wot-architecture#402.
-
TAG interoperability concerns w3c/wot-architecture#371.
-
Add short mention of ID privacy risk to Architecture Security and Privacy Considerations w3c/wot-architecture#398.
-
define "Private security (meta)data" w3c/wot-architecture#380.
-
Add introduction section as described in https://github.com/w3c/wot-architecture/issues/390 w3c/wot-architecture#391.
-
Rename chapter headings as described in https://github.com/w3c/wot-architecture/issues/390 w3c/wot-architecture#392.
-
Add definitions of security data/metadata to terminology w3c/wot-architecture#393.
-
update change log for CR2 w3c/wot-architecture#401.
-
General TL;DR problem w3c/wot-architecture#366.
-
Address TAG and Security review feedback w3c/wot-architecture#351.
-
Update Wikipedia page on WoT w3c/wot-architecture#207.
-
Data Schema should be briefly explained in Architecture Document w3c/wot-architecture#382.
-
Update Figures 25 + 27-29 to call out private security data and public security metadata w3c/wot-architecture#386.
-
-
1 issue reopened.
-
Update TD reference to PR version of TD spec w3c/wot-architecture#352, by @mlagally.
-
-
13 issues received 16 new comments.
-
Document lacks sufficient detail to understand how privacy-sensitive information flows through the system w3c/wot-architecture#390 (3 comments by @mlagally)
-
Need deployment example for Cloud Server with Client devices w3c/wot-architecture#208 (1 comment by @mlagally)
-
Add short mention of ID privacy risk to Architecture Security and Privacy Considerations w3c/wot-architecture#398 (1 comment by @mlagally)
-
Add introduction section as described in https://github.com/w3c/wot-architecture/issues/390 w3c/wot-architecture#391 (1 comment by @mlagally)
-
Add definitions of security data/metadata to terminology w3c/wot-architecture#393 (1 comment by @mlagally)
-
-
15 pull requests opened.
-
initial structure and templates for use cases and requirements w3c/wot-architecture#411, by @mlagally.
-
initial structure and templates for use cases and requirements w3c/wot-architecture#408, by @mlagally.
-
Details about reference changes to the change log. w3c/wot-architecture#407, by @mlagally.
-
Additional explanation for RFC2046 w3c/wot-architecture#406, by @mlagally.
-
Bring CR2-request branch up to date with master w3c/wot-architecture#405, by @mmccool.
-
Make terminology informative - Update w3c/wot-architecture#404, by @mmccool.
-
make terminology section informative w3c/wot-architecture#403, by @ashimura.
-
Privacy risks patch 2 w3c/wot-architecture#400, by @mmccool.
-
Add privacy paragraph to "Deployment" section w3c/wot-architecture#399, by @mmccool.
-
Refactoring and rewriting abstract and introduction w3c/wot-architecture#397, by @mmccool.
-
Update index.html - Add security data/metadata defns w3c/wot-architecture#396, by @mmccool.
-
Update index.html - Introduction w3c/wot-architecture#395, by @mlagally.
-
Update index.html - rename section headings w3c/wot-architecture#394, by @mlagally.
-
-
16 pull requests merged.
-
initial structure and templates for use cases and requirements w3c/wot-architecture#411.
-
cleanup w3c/wot-architecture#410.
-
minor w3c/wot-architecture#409.
-
initial structure and templates for use cases and requirements w3c/wot-architecture#408.
-
Details about reference changes to the change log. w3c/wot-architecture#407.
-
Bring CR2-request branch up to date with master w3c/wot-architecture#405.
-
Make terminology informative - Update w3c/wot-architecture#404.
-
make terminology section informative w3c/wot-architecture#403.
-
Refactoring and rewriting abstract and introduction w3c/wot-architecture#397.
-
Update index.html - Add security data/metadata defns w3c/wot-architecture#396.
-
Add privacy paragraph to "Deployment" section w3c/wot-architecture#399.
-
Privacy risks patch 2 w3c/wot-architecture#400.
-
Update index.html - rename section headings w3c/wot-architecture#394.
-
Update index.html - Introduction w3c/wot-architecture#395.
-
Update Figures 25 + 27-29 w3c/wot-architecture#388.
-
[Editorial] Add and update SVG files w3c/wot-architecture#389.
-
-
1 pull request closed.
-
Additional explanation for RFC2046 w3c/wot-architecture#406.
-
-
5 pull requests received 20 new comments.
-
Update index.html - Add security data/metadata defns w3c/wot-architecture#396 (10 comments by @mlagally, @mmccool)
-
Refactoring and rewriting abstract and introduction w3c/wot-architecture#397 (4 comments by @mlagally, @mmccool)
-
make terminology section informative w3c/wot-architecture#403 (3 comments by @ashimura, @mlagally, @mmccool)
-
w3c/wot-thing-description
-
4 issues opened.
-
Clarify InteractionAffordance::contentType vs DataSchema::type w3c/wot-thing-description#839, by @zolkis.
-
(Minor) CR2 Release Candidate comments w3c/wot-thing-description#833, by @danielpeintner.
-
Update Change Log w3c/wot-thing-description#829, by @takuki.
-
Update Privacy Risks and Mitigations that reference IDs w3c/wot-thing-description#824, by @mmccool.
-
-
15 issues closed.
-
Update Change Log w3c/wot-thing-description#829.
-
Implementation report uses the words client and server w3c/wot-thing-description#815.
-
Update Privacy Risks and Mitigations that reference IDs w3c/wot-thing-description#824.
-
Reasoning is missing why Example 29 design is considered a good practice w3c/wot-thing-description#813.
-
Question: difference between operation types writeallproperties vs. writemultipleproperties w3c/wot-thing-description#799.
-
[Testing] Implementations of Digest QoP sub-feature needed w3c/wot-thing-description#739.
-
[question] How to describe observeOnly properties? w3c/wot-thing-description#810.
-
[Editorial] inline JSON is formatted like normal text w3c/wot-thing-description#468.
-
[Editorial] DataSchema subclass order is not consistent w3c/wot-thing-description#467.
-
i18n checklist for Handling base direction for strings w3c/wot-thing-description#585.
-
Thing Description Serialization and BOM [I18N] w3c/wot-thing-description#640.
-
Retrieve raw JSON data for context namespaces w3c/wot-thing-description#790.
-
Testing "type = array of X" assertions w3c/wot-thing-description#388.
-
server-data-schema and server-data-schema-extras are contradictory (for a first time reader) w3c/wot-thing-description#807.
-
Rename Thing Template to Thing Description Template / TD Template w3c/wot-thing-description#801.
-
-
28 issues received 63 new comments.
-
Implementation report uses the words client and server w3c/wot-thing-description#815 (8 comments by @egekorkan, @mmccool, @sebastiankb)
-
Allow "security" to include both SecurityScheme objects and declared identifiers w3c/wot-thing-description#300 (6 comments by @mmccool, @sebastiankb, @vcharpenay)
-
(Minor) CR2 Release Candidate comments w3c/wot-thing-description#833 (5 comments by @danielpeintner, @mmccool, @sebastiankb)
-
should be clearer about where the definition of the HTTP Protocol Binding is w3c/wot-thing-description#791 (4 comments by @benfrancis, @egekorkan, @mmccool, @sebastiankb)
-
[At-Risk] Implementations of OAuth2SecurityScheme needed w3c/wot-thing-description#730 (4 comments by @mmccool)
-
Reasoning is missing why Example 29 design is considered a good practice w3c/wot-thing-description#813 (3 comments by @sebastiankb, @vcharpenay)
-
Bringing back PoP Security Scheme w3c/wot-thing-description#731 (3 comments by @mmccool, @sebastiankb)
-
make privacy mitigations mandatory w3c/wot-thing-description#794 (3 comments by @mmccool, @sebastiankb)
-
Clarify InteractionAffordance::contentType vs DataSchema::type w3c/wot-thing-description#839 (2 comments by @egekorkan, @zolkis)
-
Move Transformation to RDF (now removed from TD) to TD ontology document w3c/wot-thing-description#787 (2 comments by @takuki, @vcharpenay)
-
Handle at risk features before publishing as proposed rec w3c/wot-thing-description#789 (2 comments by @mmccool, @sebastiankb)
-
JSON Schema/Hyper-Schema compatibility goals? w3c/wot-thing-description#115 (2 comments by @handrews, @sebastiankb)
-
[Editorial] inline JSON is formatted like normal text w3c/wot-thing-description#468 (2 comments by @egekorkan, @sebastiankb)
-
[Editorial] DataSchema subclass order is not consistent w3c/wot-thing-description#467 (2 comments by @egekorkan, @vcharpenay)
-
Update Privacy Risks and Mitigations that reference IDs w3c/wot-thing-description#824 (1 comment by @sebastiankb)
-
Question: difference between operation types writeallproperties vs. writemultipleproperties w3c/wot-thing-description#799 (1 comment by @sebastiankb)
-
[Testing] Implementations of Digest QoP sub-feature needed w3c/wot-thing-description#739 (1 comment by @mmccool)
-
No "with default values" checkbox for Appendix A examples w3c/wot-thing-description#715 (1 comment by @sebastiankb)
-
Move MQTT (and CoAP) example to Protocol Binding Templates document w3c/wot-thing-description#786 (1 comment by @sebastiankb)
-
[question] How to describe observeOnly properties? w3c/wot-thing-description#810 (1 comment by @egekorkan)
-
Make a request for TD media type registration at IANA w3c/wot-thing-description#560 (1 comment by @sebastiankb)
-
i18n checklist for Handling base direction for strings w3c/wot-thing-description#585 (1 comment by @sebastiankb)
-
Thing Description Serialization and BOM [I18N] w3c/wot-thing-description#640 (1 comment by @sebastiankb)
-
Retrieve raw JSON data for context namespaces w3c/wot-thing-description#790 (1 comment by @vcharpenay)
-
EventAffordance - unclear alignment of Data Schemas with response messages w3c/wot-thing-description#817 (1 comment by @sebastiankb)
-
Rename Thing Template to Thing Description Template / TD Template w3c/wot-thing-description#801 (1 comment by @sebastiankb)
-
-
16 pull requests opened.
-
fix: resolves remaining issues in 833 w3c/wot-thing-description#838, by @danielpeintner.
-
Fix CR2 request to include missing assertion w3c/wot-thing-description#837, by @mmccool.
-
List td-writeall-consumer as at-risk w3c/wot-thing-description#836, by @mmccool.
-
Minor At-risk fixes and IR updates w3c/wot-thing-description#835, by @mmccool.
-
Update CR2 Request with Master w3c/wot-thing-description#834, by @mmccool.
-
Updated Recent Changes section w3c/wot-thing-description#832, by @takuki.
-
Clarification of example 29 w3c/wot-thing-description#831, by @vcharpenay.
-
Fix respec problem w3c/wot-thing-description#830, by @mlagally.
-
"HTTP Protocol Binding" is now "Protocol Binding based on HTTP". w3c/wot-thing-description#828, by @takuki.
-
WIP: Define Terminology Section 3 as non-normative w3c/wot-thing-description#827, by @sebastiankb.
-
Fix for #799 and update date on validation schema w3c/wot-thing-description#826, by @egekorkan.
-
Update privacy risks and mitigations for CR2 w3c/wot-thing-description#825, by @mmccool.
-
Updates to Implementation report and at-risk items for CR2 w3c/wot-thing-description#823, by @mmccool.
-
Make oauth2/flow mandatory, remove default w3c/wot-thing-description#822, by @mmccool.
-
PR that moves WoT-Arch to informative references section w3c/wot-thing-description#821, by @sebastiankb.
-
Addresses issue #794 (set 'id' optional and remove 'unique') w3c/wot-thing-description#820, by @sebastiankb.
-
-
18 pull requests merged.
-
Fix CR2 request to include missing assertion w3c/wot-thing-description#837.
-
List td-writeall-consumer as at-risk w3c/wot-thing-description#836.
-
Update CR2 Request with Master w3c/wot-thing-description#834.
-
Minor At-risk fixes and IR updates w3c/wot-thing-description#835.
-
Updated Recent Changes section w3c/wot-thing-description#832.
-
Fix respec problem w3c/wot-thing-description#830.
-
Clarification of example 29 w3c/wot-thing-description#831.
-
Update privacy risks and mitigations for CR2 w3c/wot-thing-description#825.
-
"HTTP Protocol Binding" is now "Protocol Binding based on HTTP". w3c/wot-thing-description#828.
-
Fix for #799 and update date on validation schema w3c/wot-thing-description#826.
-
Make oauth2/flow mandatory, remove default w3c/wot-thing-description#822.
-
PR that moves WoT-Arch to informative references section w3c/wot-thing-description#821.
-
WIP: Define Terminology Section 3 as non-normative w3c/wot-thing-description#827.
-
Updates to Implementation report and at-risk items for CR2 w3c/wot-thing-description#823.
-
Added section on JSON-LD context w3c/wot-thing-description#811.
-
Addresses issue #794 (set 'id' optional and remove 'unique') w3c/wot-thing-description#820.
-
Fix for issue #807 w3c/wot-thing-description#819.
-
changes Thing Template to Thing Description Template w3c/wot-thing-description#818.
-
-
12 pull requests received 28 new comments.
-
WIP: Define Terminology Section 3 as non-normative w3c/wot-thing-description#827 (6 comments by @ashimura, @mlagally, @mmccool, @sebastiankb)
-
Added section on JSON-LD context w3c/wot-thing-description#811 (5 comments by @sebastiankb, @takuki, @vcharpenay)
-
Addresses issue #794 (set 'id' optional and remove 'unique') w3c/wot-thing-description#820 (3 comments by @sebastiankb)
-
Fix for #799 and update date on validation schema w3c/wot-thing-description#826 (2 comments by @egekorkan, @sebastiankb)
-
Make oauth2/flow mandatory, remove default w3c/wot-thing-description#822 (2 comments by @sebastiankb)
-
Updates to Implementation report and at-risk items for CR2 w3c/wot-thing-description#823 (2 comments by @mmccool, @sebastiankb)
-
Update privacy risks and mitigations for CR2 w3c/wot-thing-description#825 (1 comment by @sebastiankb)
-
"HTTP Protocol Binding" is now "Protocol Binding based on HTTP". w3c/wot-thing-description#828 (1 comment by @sebastiankb)
-
PR that moves WoT-Arch to informative references section w3c/wot-thing-description#821 (1 comment by @sebastiankb)
-
changes Thing Template to Thing Description Template w3c/wot-thing-description#818 (1 comment by @mlagally)
-
w3c/wot-scripting-api
-
1 issue opened.
-
*Soften* statements "value MUST be JSON" w3c/wot-scripting-api#198, by @danielpeintner.
-
-
1 issue closed.
-
Simplified API for JavaScript and other programming languages w3c/wot-scripting-api#64.
-
-
2 issues received 5 new comments.
-
*Soften* statements "value MUST be JSON" w3c/wot-scripting-api#198 (3 comments by @egekorkan, @zolkis)
-
Simplified API for JavaScript and other programming languages w3c/wot-scripting-api#64 (2 comments by @draggett, @zolkis)
-
-
2 pull requests opened.
-
feedback from wd4 w3c/wot-scripting-api#197, by @ashimura.
-
Release WD4 w3c/wot-scripting-api#196, by @zolkis.
-
-
2 pull requests merged.
-
feedback from wd4 w3c/wot-scripting-api#197.
-
Release WD4 w3c/wot-scripting-api#196.
-
w3c/wot-binding-templates
-
5 issues received 6 new comments.
-
Meta-interaction is missing from section 2.3 Interaction Types w3c/wot-binding-templates#59 (1 comment by @egekorkan)
-
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 @takuki)
-
1 pull request opened.
-
Multiple Contributions w3c/wot-binding-templates#79, by @egekorkan.
-
w3c/wotwg
-
1 pull request opened.
-
feat: point to latest note w3c/wotwg#8, by @danielpeintner.
-
Participants
-
1 participant joined.
-
Ted Guild (W3C) joined.
-
GitHub
w3c/wot-thing-description
-
5 issues opened.
-
EventAffordance - unclear alignment of Data Schemas with response messages w3c/wot-thing-description#817, by @hrennau.
-
Implementation report uses the words client and server w3c/wot-thing-description#815, by @egekorkan.
-
Reasoning is missing why Example 29 design is considered a good practice w3c/wot-thing-description#813, by @takuki.
-
EventAffordance cannot describe contentType of event messages w3c/wot-thing-description#812, by @hrennau.
-
[question] How to describe observeOnly properties? w3c/wot-thing-description#810, by @egekorkan.
-
-
9 issues closed.
-
No mechanism to indicate what the "default language" of a description is [I18N] w3c/wot-thing-description#635.
-
Multilanguage section clarity [I18N] w3c/wot-thing-description#637.
-
Clarify about language negotiation [I18N] w3c/wot-thing-description#638.
-
DataSchema format field and patterns [I18N] w3c/wot-thing-description#639.
-
dateTime reference when mapping to JSON types [I18N] w3c/wot-thing-description#641.
-
clarify permitted language tags for titles/descriptions [I18N] w3c/wot-thing-description#642.
-
Remove or update github links in the spec w3c/wot-thing-description#792.
-
Proposals are referenced by Google and have wrong date w3c/wot-thing-description#808.
-
Name vs title in TD examples w3c/wot-thing-description#793.
-
-
18 issues received 45 new comments.
-
server-data-schema and server-data-schema-extras are contradictory (for a first time reader) w3c/wot-thing-description#807 (7 comments by @egekorkan, @hrennau, @sebastiankb)
-
EventAffordance cannot describe contentType of event messages w3c/wot-thing-description#812 (6 comments by @egekorkan, @hrennau, @sebastiankb)
-
Proposals are referenced by Google and have wrong date w3c/wot-thing-description#808 (5 comments by @danielpeintner, @egekorkan, @k-toumura, @sebastiankb)
-
[question] How to describe observeOnly properties? w3c/wot-thing-description#810 (3 comments by @egekorkan, @sebastiankb, @zolkis)
-
No mechanism to indicate what the "default language" of a description is [I18N] w3c/wot-thing-description#635 (2 comments by @aphillips, @sebastiankb)
-
Multilanguage section clarity [I18N] w3c/wot-thing-description#637 (2 comments by @aphillips, @sebastiankb)
-
Clarify about language negotiation [I18N] w3c/wot-thing-description#638 (2 comments by @aphillips, @sebastiankb)
-
DataSchema format field and patterns [I18N] w3c/wot-thing-description#639 (2 comments by @aphillips, @sebastiankb)
-
dateTime reference when mapping to JSON types [I18N] w3c/wot-thing-description#641 (2 comments by @aphillips, @sebastiankb)
-
clarify permitted language tags for titles/descriptions [I18N] w3c/wot-thing-description#642 (2 comments by @aphillips, @sebastiankb)
-
EventAffordance - unclear alignment of Data Schemas with response messages w3c/wot-thing-description#817 (2 comments by @egekorkan, @hrennau)
-
Reasoning is missing why Example 29 design is considered a good practice w3c/wot-thing-description#813 (2 comments by @hrennau, @sebastiankb)
-
Rename Thing Template to Thing Description Template / TD Template w3c/wot-thing-description#801 (2 comments by @sebastiankb, @takuki)
-
Single 'base' field but multiple 'forms' elements w3c/wot-thing-description#803 (1 comment by @sebastiankb)
-
Implementation report uses the words client and server w3c/wot-thing-description#815 (1 comment by @sebastiankb)
-
Retrieve raw JSON data for context namespaces w3c/wot-thing-description#790 (1 comment by @vcharpenay)
-
-
6 pull requests opened.
-
Fix for issue #807 w3c/wot-thing-description#819, by @egekorkan.
-
changes Thing Template to Thing Description Template w3c/wot-thing-description#818, by @sebastiankb.
-
provide static date + a robots file for avoiding indexing w3c/wot-thing-description#816, by @sebastiankb.
-
remove simplified TD proposal w3c/wot-thing-description#814, by @sebastiankb.
-
Added section on JSON-LD context w3c/wot-thing-description#811, by @vcharpenay.
-
Fixed a typo. w3c/wot-thing-description#809, by @takuki.
-
-
2 pull requests merged.
-
provide static date + a robots file for avoiding indexing w3c/wot-thing-description#816.
-
Fixed a typo. w3c/wot-thing-description#809.
-
-
1 pull request closed.
-
remove simplified TD proposal w3c/wot-thing-description#814.
-
-
3 pull requests received 6 new comments.
-
remove simplified TD proposal w3c/wot-thing-description#814 (3 comments by @danielpeintner, @sebastiankb)
-
provide static date + a robots file for avoiding indexing w3c/wot-thing-description#816 (2 comments by @danielpeintner, @sebastiankb)
-
w3c/wot-scripting-api
-
4 issues opened.
-
Should writeProperty() return a value w3c/wot-scripting-api#193, by @danielpeintner.
-
Discuss the modularization of WoT scripts w3c/wot-scripting-api#192, by @vcharpenay.
-
Create testing plan w3c/wot-scripting-api#190, by @mmccool.
-
Mis-match between interaction and interaction-handler w3c/wot-scripting-api#188, by @danielpeintner.
-
-
1 issue closed.
-
Mis-match between interaction and interaction-handler w3c/wot-scripting-api#188.
-
-
2 issues reopened.
-
handlers for unobserving property/event missing w3c/wot-scripting-api#183, by @zolkis.
-
handlers for unobserving property/event missing w3c/wot-scripting-api#183, by @danielpeintner.
-
-
3 issues received 9 new comments.
-
handlers for unobserving property/event missing w3c/wot-scripting-api#183 (6 comments by @danielpeintner, @mmccool, @zolkis)
-
Mis-match between interaction and interaction-handler w3c/wot-scripting-api#188 (2 comments by @zolkis)
-
-
4 pull requests opened.
-
Fix HTML errors w3c/wot-scripting-api#195, by @zolkis.
-
Revert subscription ID change, see #183 w3c/wot-scripting-api#194, by @zolkis.
-
Next api 2019 w3c/wot-scripting-api#191, by @danielpeintner.
-
Update constructors. Add InteractionOptions to handlers. w3c/wot-scripting-api#189, by @zolkis.
-
-
4 pull requests merged.
-
Fix HTML errors w3c/wot-scripting-api#195.
-
Next api 2019 w3c/wot-scripting-api#191.
-
Revert subscription ID change, see #183 w3c/wot-scripting-api#194.
-
Update constructors. Add InteractionOptions to handlers. w3c/wot-scripting-api#189.
-
-
4 pull requests received 6 new comments.
-
Update constructors. Add InteractionOptions to handlers. w3c/wot-scripting-api#189 (3 comments by @danielpeintner, @zolkis)
-
w3c/wot-binding-templates
-
1 issue opened.
-
observeOnly properties w3c/wot-binding-templates#78, by @egekorkan.
-
-
9 issues closed.
-
Section 2.2.2 Media Types should clarify the usage of "profile" attribute's in TD w3c/wot-binding-templates#69.
-
Section name 2.2.1 "Relation Types" is not accurate w3c/wot-binding-templates#57.
-
"unobserveproperty" is missing w3c/wot-binding-templates#54.
-
Mention of XML should be dropped w3c/wot-binding-templates#55.
-
subProtocol lowercase only w3c/wot-binding-templates#60.
-
uriVariables needs to be described w3c/wot-binding-templates#63.
-
Inconsistency between OCF Batch Payload Example and Schema w3c/wot-binding-templates#64.
-
References are not used properly w3c/wot-binding-templates#76.
-
subscription, data, cancellation need to be added w3c/wot-binding-templates#56.
-
-
12 issues received 13 new comments.
-
align with the vocabulary in "CoAP in RDF" ontology and IANA CoRE Parameters page w3c/wot-binding-templates#47 (2 comments by @danielpeintner, @egekorkan)
-
Section 2.2.2 Media Types should clarify the usage of "profile" attribute's in TD w3c/wot-binding-templates#69 (1 comment by @egekorkan)
-
Section name 2.2.1 "Relation Types" is not accurate w3c/wot-binding-templates#57 (1 comment by @egekorkan)
-
Structure of protocol binding block and terminology w3c/wot-binding-templates#2 (1 comment by @egekorkan)
-
Inconsistency between OCF Batch Payload Example and Schema w3c/wot-binding-templates#64 (1 comment by @egekorkan)
-
subscription, data, cancellation need to be added w3c/wot-binding-templates#56 (1 comment by @takuki)
-
-
1 pull request opened.
-
WIP: Pre publish w3c/wot-binding-templates#77, by @egekorkan.
-
-
1 pull request merged.
-
WIP: Pre publish w3c/wot-binding-templates#77.
-
w3c/wot-architecture
-
1 issue opened.
-
Update Figures 25 + 27-29 to call out private security data and public security metadata w3c/wot-architecture#386, by @mlagally.
-
-
2 issues closed.
-
definition of privacy is too weak w3c/wot-architecture#375.
-
definition of security is too weak w3c/wot-architecture#376.
-
-
6 issues received 10 new comments.
-
Update Figures 25 + 27-29 to call out private security data and public security metadata w3c/wot-architecture#386 (1 comment by @mlagally)
-
5 pull requests opened.
-
[Editorial] Add and update SVG files w3c/wot-architecture#389, by @k-toumura.
-
Update Figures 25 + 27-29 w3c/wot-architecture#388, by @k-toumura.
-
Clarify terminology - security configuration / data w3c/wot-architecture#385, by @mlagally.
-
Modify security and privacy definitions to refer to ISO standards w3c/wot-architecture#384, by @mmccool.
-
Defined Data Schema in Terminology section. w3c/wot-architecture#383, by @takuki.
-
-
3 pull requests merged.
-
Clarify terminology - security configuration / data w3c/wot-architecture#385.
-
Modify security and privacy definitions to refer to ISO standards w3c/wot-architecture#384.
-
Defined Data Schema in Terminology section. w3c/wot-architecture#383.
-
-
1 pull request closed.
-
Delete definitions of Security and Privacy w3c/wot-architecture#368.
-
-
2 pull requests received 4 new comments.
-
Clarify terminology - security configuration / data w3c/wot-architecture#385 (3 comments by @ereshetova, @k-toumura, @mmccool)
-
w3c/wot-profile
-
5 issues opened.
-
[idea] Detecting a profile via a TD w3c/wot-profile#13, by @egekorkan.
-
single profile or smart home + industrial profile w3c/wot-profile#12, by @mlagally.
-
HTTP Protocol Binding duplicated in TD spec w3c/wot-profile#11, by @benfrancis.
-
Reduce or remove the constraints in section 7.2 Baseline Information Model w3c/wot-profile#10, by @benfrancis.
-
Thing Template Profile and Digital Twin Profile are bad examples w3c/wot-profile#9, by @benfrancis.
-
-
6 issues received 14 new comments.
-
"Core" profile name has undesired implications w3c/wot-profile#5 (6 comments by @benfrancis, @draggett, @egekorkan)
-
Thing Template Profile and Digital Twin Profile are bad examples w3c/wot-profile#9 (1 comment by @draggett)
-
How to support composable "Vertical" vs. "Horizontal" Profiles w3c/wot-profile#8 (1 comment by @benfrancis)
-
-
1 pull request opened.
-
(WIP) Updates to Use Cases and Requirements from TPAC w3c/wot-profile#14, by @mmccool.
-
-
1 pull request merged.
-
(WIP) Updates to Use Cases and Requirements from TPAC w3c/wot-profile#14.
-
Participants
-
1 organization joined.
-
Conexxus joined.
-
GitHub
w3c/wot-thing-description
-
8 issues opened.
-
Proposals are referenced by Google and have wrong date w3c/wot-thing-description#808, by @egekorkan.
-
server-data-schema and server-data-schema-extras are contradictory (for a first time reader) w3c/wot-thing-description#807, by @egekorkan.
-
add a new vocabulary term "profile" with a String type w3c/wot-thing-description#806, by @mlagally.
-
Improve Explainer with User-Oriented Use Cases w3c/wot-thing-description#805, by @mmccool.
-
rules and test suite for conversion between JSON schema and RDF w3c/wot-thing-description#804, by @rob-metalinkage.
-
Single 'base' field but multiple 'forms' elements w3c/wot-thing-description#803, by @6d77.
-
Rename Thing Template to Thing Description Template / TD Template w3c/wot-thing-description#801, by @sebastiankb.
-
extend op options with observeallproperties and observemultipleproperties w3c/wot-thing-description#800, by @sebastiankb.
-
-
6 issues received 10 new comments.
-
Single 'base' field but multiple 'forms' elements w3c/wot-thing-description#803 (5 comments by @6d77, @danielpeintner, @takuki, @zolkis)
-
add a new vocabulary term "profile" with a String type w3c/wot-thing-description#806 (1 comment by @takuki)
-
rules and test suite for conversion between JSON schema and RDF w3c/wot-thing-description#804 (1 comment by @takuki)
-
Rename Thing Template to Thing Description Template / TD Template w3c/wot-thing-description#801 (1 comment by @mlagally)
-
Question: difference between operation types writeallproperties vs. writemultipleproperties w3c/wot-thing-description#799 (1 comment by @takuki)
-
-
1 pull request opened.
-
Update few links + add chapter link w3c/wot-thing-description#802, by @sebastiankb.
-
-
1 pull request merged.
-
Update few links + add chapter link w3c/wot-thing-description#802.
-
-
1 pull request received 1 new comment.
w3c/wot-scripting-api
-
3 issues opened.
-
getTD() method instead of td attribute w3c/wot-scripting-api#184, by @danielpeintner.
-
handlers for unobserving property/event missing w3c/wot-scripting-api#183, by @danielpeintner.
-
readProperty() does not allow for uriVariables or other parameters w3c/wot-scripting-api#182, by @danielpeintner.
-
-
15 issues closed.
-
Can an Exposed Thing provide a Protocol Binding? w3c/wot-scripting-api#45.
-
General API discussion (was: "Proposal: readMutlipleProperties and writeMultipleProperties") w3c/wot-scripting-api#132.
-
Align with TD (name/value pairs) w3c/wot-scripting-api#157.
-
Debugging w3c/wot-scripting-api#34.
-
Management Thing - update verb w3c/wot-scripting-api#33.
-
policies of security enforcement in the scripting runtime w3c/wot-scripting-api#26.
-
Isolation of scripts / sandbox and access to outside w3c/wot-scripting-api#25.
-
Metadata related to a script to let a runtime decide in which execution context it should run w3c/wot-scripting-api#29.
-
Management Thing - verb semantics clarification w3c/wot-scripting-api#35.
-
Dynamic Management Things - Management TD for each installed script w3c/wot-scripting-api#36.
-
Security, WoT Scripting API: security metadata in API w3c/wot-scripting-api#91.
-
Signal end of life of an ExposedThing to the related ConsumedThings w3c/wot-scripting-api#114.
-
readProperty() does not allow for uriVariables or other parameters w3c/wot-scripting-api#182.
-
getTD() method instead of td attribute w3c/wot-scripting-api#184.
-
Spec: Examples using JSON string instead of object w3c/wot-scripting-api#181.
-
-
15 issues received 47 new comments.
-
readProperty() does not allow for uriVariables or other parameters w3c/wot-scripting-api#182 (14 comments by @danielpeintner, @zolkis)
-
WIP: Implementation experience while realizing new API in node-wot w3c/wot-scripting-api#180 (7 comments by @danielpeintner, @zolkis)
-
getTD() method instead of td attribute w3c/wot-scripting-api#184 (7 comments by @danielpeintner, @zolkis)
-
handlers for unobserving property/event missing w3c/wot-scripting-api#183 (7 comments by @danielpeintner, @zolkis)
-
policies of security enforcement in the scripting runtime w3c/wot-scripting-api#26 (1 comment by @zolkis)
-
Isolation of scripts / sandbox and access to outside w3c/wot-scripting-api#25 (1 comment by @zolkis)
-
Metadata related to a script to let a runtime decide in which execution context it should run w3c/wot-scripting-api#29 (1 comment by @zolkis)
-
Dynamic Management Things - Management TD for each installed script w3c/wot-scripting-api#36 (1 comment by @zolkis)
-
Spec: Examples using JSON string instead of object w3c/wot-scripting-api#181 (1 comment by @danielpeintner)
-
-
3 pull requests opened.
-
Clarify ExposedThing default handlers vs script provided handlers. Editorial fixes. w3c/wot-scripting-api#187, by @zolkis.
-
Fix #180: Clarify ExposedThing Property initialization w3c/wot-scripting-api#186, by @zolkis.
-
Handle implementation feedback from node-wot w3c/wot-scripting-api#185, by @zolkis.
-
-
2 pull requests merged.
-
Clarify ExposedThing default handlers vs script provided handlers. Editorial fixes. w3c/wot-scripting-api#187.
-
Handle implementation feedback from node-wot w3c/wot-scripting-api#185.
-
-
1 pull request closed.
-
Fix #180: Clarify ExposedThing Property initialization w3c/wot-scripting-api#186.
-
-
3 pull requests received 7 new comments.
-
Handle implementation feedback from node-wot w3c/wot-scripting-api#185 (4 comments by @danielpeintner, @zolkis)
-
Fix #180: Clarify ExposedThing Property initialization w3c/wot-scripting-api#186 (2 comments by @danielpeintner, @zolkis)
-
Clarify ExposedThing default handlers vs script provided handlers. Editorial fixes. w3c/wot-scripting-api#187 (1 comment by @danielpeintner)
-
w3c/wot-binding-templates
-
2 issues opened.
-
References are not used properly w3c/wot-binding-templates#76, by @egekorkan.
-
Definitions and Terminology reference w3c/wot-binding-templates#75, by @egekorkan.
-
-
1 issue closed.
-
Definitions and Terminology reference w3c/wot-binding-templates#75.
-
-
11 issues received 27 new comments.
-
subscription, data, cancellation need to be added w3c/wot-binding-templates#56 (4 comments by @egekorkan, @takuki)
-
MQTT Vocabulary needs better terms w3c/wot-binding-templates#72 (3 comments by @egekorkan, @mjkoster)
-
Inconsistency between OCF Batch Payload Example and Schema w3c/wot-binding-templates#64 (2 comments by @egekorkan)
-
MQTT Vocabulary Option values are unsigned int w3c/wot-binding-templates#74 (2 comments by @egekorkan)
-
Meta-interaction is missing from section 2.3 Interaction Types w3c/wot-binding-templates#59 (1 comment by @egekorkan)
-
1 pull request merged.
-
Various fixes to the issues w3c/wot-binding-templates#71.
-
-
1 pull request received 2 new comments.
w3c/wot-profile
-
7 issues opened.
-
How to support composable "Vertical" vs. "Horizontal" Profiles w3c/wot-profile#8, by @mmccool.
-
Reduce Number of Goals or Differentiate w3c/wot-profile#7, by @mmccool.
-
Recommended Security w3c/wot-profile#6, by @mmccool.
-
"Core" profile name has undesired implications w3c/wot-profile#5, by @danielpeintner.
-
Split Data Model constraints and bindings w3c/wot-profile#4, by @danielpeintner.
-
Evaluate Data Schema Constraints w3c/wot-profile#3, by @danielpeintner.
-
Way to identify profile(s) w3c/wot-profile#2, by @danielpeintner.
-
-
3 issues received 9 new comments.
-
"Core" profile name has undesired implications w3c/wot-profile#5 (2 comments by @egekorkan, @mlagally)
-
1 pull request opened.
-
initial version w3c/wot-profile#1, by @mlagally.
-
-
1 pull request merged.
-
initial version w3c/wot-profile#1.
-
w3c/wot-architecture
-
1 issue opened.
-
Data Schema should be briefly explained in Architecture Document w3c/wot-architecture#382, by @takuki.
-
-
1 issue closed.
-
broken reference in definition of Personally Identifiable Information (PII) w3c/wot-architecture#377.
-
-
2 issues reopened.
-
define "Private security (meta)data" w3c/wot-architecture#380, by @samuelweiler.
-
TAG interoperability concerns w3c/wot-architecture#371, by @mlagally.
-
-
6 issues received 12 new comments.
-
define "Private security (meta)data" w3c/wot-architecture#380 (3 comments by @mlagally, @samuelweiler)
-
broken reference in definition of Personally Identifiable Information (PII) w3c/wot-architecture#377 (1 comment by @mlagally)
-
Data Schema should be briefly explained in Architecture Document w3c/wot-architecture#382 (1 comment by @mlagally)
-
1 pull request merged.
-
Add definition of private security configuration and data w3c/wot-architecture#381.
-
w3c/wot-security
-
4 issues received 4 new comments.
-
Update Definitions of Security and Privacy in Architecture Document w3c/wot-security#134 (1 comment by @mmccool)
-
Review Privacy Mitigations for TD ids and fingerprinting w3c/wot-security#136 (1 comment by @mmccool)
Participants
-
1 organization left.
-
Orange left.
-
GitHub
w3c/wot-binding-templates
-
9 issues opened.
-
MQTT Vocabulary Option values are unsigned int w3c/wot-binding-templates#74, by @egekorkan.
-
Align Vocabulary tables with TD spec w3c/wot-binding-templates#73, by @egekorkan.
-
MQTT Vocabulary needs better terms w3c/wot-binding-templates#72, by @egekorkan.
-
Section 2.2.2 Media Types should clarify the usage of "profile" attribute's in TD w3c/wot-binding-templates#69, by @takuki.
-
subprotocol example and prose alignment with TD spec w3c/wot-binding-templates#68, by @takuki.
-
Broken links in Binding Spec to context files w3c/wot-binding-templates#66, by @mlagally.
-
Section 2.1.2 Data Types and value constraints not consistent with TD spec w3c/wot-binding-templates#65, by @takuki.
-
Inconsistency between OCF Batch Payload Example and Schema w3c/wot-binding-templates#64, by @takuki.
-
uriVariables needs to be described w3c/wot-binding-templates#63, by @takuki.
-
-
10 issues closed.
-
no vacabulary defintion for CoAP and MQTT yet w3c/wot-binding-templates#61.
-
Media Types should be Content Types w3c/wot-binding-templates#58.
-
Broken links in Binding Spec to context files w3c/wot-binding-templates#66.
-
subprotocol example and prose alignment with TD spec w3c/wot-binding-templates#68.
-
Section 2.1.2 Data Types and value constraints not consistent with TD spec w3c/wot-binding-templates#65.
-
Compile proposal for URI Templates w3c/wot-binding-templates#44.
-
Event Implementation Proposal (HTTP+WebSocket) w3c/wot-binding-templates#7.
-
Review comments from August 2018 w3c/wot-binding-templates#52.
-
Consider the Mozilla pattern for events w3c/wot-binding-templates#16.
-
Is "allOf" in EXAMPLE 6-8 correct? w3c/wot-binding-templates#34.
-
-
28 issues received 57 new comments.
-
no vacabulary defintion for CoAP and MQTT yet w3c/wot-binding-templates#61 (8 comments by @egekorkan, @sebastiankb, @takuki)
-
Meta-interaction is missing from section 2.3 Interaction Types w3c/wot-binding-templates#59 (6 comments by @danielpeintner, @egekorkan, @takuki)
-
subProtocol lowercase only w3c/wot-binding-templates#60 (5 comments by @egekorkan, @sebastiankb, @takuki)
-
Media Types should be Content Types w3c/wot-binding-templates#58 (4 comments by @egekorkan, @mjkoster, @takuki)
-
Section 2.1.2 Data Types and value constraints not consistent with TD spec w3c/wot-binding-templates#65 (3 comments by @egekorkan, @takuki)
-
Section 2.2.2 Media Types should clarify the usage of "profile" attribute's in TD w3c/wot-binding-templates#69 (2 comments by @egekorkan, @mjkoster)
-
Section name 2.2.1 "Relation Types" is not accurate w3c/wot-binding-templates#57 (2 comments by @egekorkan, @takuki)
-
"Platforms" with more than one meaning should be clarified w3c/wot-binding-templates#53 (2 comments by @egekorkan, @takuki)
-
Event Implementation Proposal (HTTP+WebSocket) w3c/wot-binding-templates#7 (2 comments by @egekorkan, @yamagile)
-
subprotocol example and prose alignment with TD spec w3c/wot-binding-templates#68 (1 comment by @egekorkan)
-
Review Comments: W3C Editor's Draft 23 January 2018 w3c/wot-binding-templates#21 (1 comment by @egekorkan)
-
Do we need a protocol binding to describe notification using WebHooks? w3c/wot-binding-templates#40 (1 comment by @egekorkan)
-
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)
-
What are priorities for the next revision, next plugfest w3c/wot-binding-templates#41 (1 comment by @egekorkan)
-
align with the vocabulary in "CoAP in RDF" ontology and IANA CoRE Parameters page w3c/wot-binding-templates#47 (1 comment by @egekorkan)
-
Inconsistency between OCF Batch Payload Example and Schema w3c/wot-binding-templates#64 (1 comment by @egekorkan)
-
Use cases and requirements for protocol binding w3c/wot-binding-templates#3 (1 comment by @egekorkan)
-
Broken links in Binding Spec to context files w3c/wot-binding-templates#66 (1 comment by @egekorkan)
-
-
3 pull requests opened.
-
Various fixes to the issues w3c/wot-binding-templates#71, by @egekorkan.
-
Use indirect link through references for WebSub and SSE (for issue 68) w3c/wot-binding-templates#70, by @takuki.
-
WIP: Updating to new TD spec and definitions w3c/wot-binding-templates#67, by @egekorkan.
-
-
4 pull requests merged.
-
Moving sequence diagrams from architecture spec to binding spec w3c/wot-binding-templates#51.
-
Use indirect link through references for WebSub and SSE (for issue 68) w3c/wot-binding-templates#70.
-
Review changes for post-Bundang release w3c/wot-binding-templates#48.
-
WIP: Updating to new TD spec and definitions w3c/wot-binding-templates#67.
-
-
1 pull request closed.
-
Added id to the header of section 3.2 Interaction Verbs w3c/wot-binding-templates#50.
-
-
4 pull requests received 8 new comments.
-
WIP: Updating to new TD spec and definitions w3c/wot-binding-templates#67 (4 comments by @egekorkan, @mjkoster)
-
Moving sequence diagrams from architecture spec to binding spec w3c/wot-binding-templates#51 (1 comment by @egekorkan)
-
w3c/wot-scripting-api
-
4 issues opened.
-
Spec: Examples using JSON string instead of object w3c/wot-scripting-api#181, by @danielpeintner.
-
WIP: Implementation experience while realizing new API in node-wot w3c/wot-scripting-api#180, by @danielpeintner.
-
Consider changing how Properties are read w3c/wot-scripting-api#178, by @zolkis.
-
Consider changing next() in ThingDiscovery w3c/wot-scripting-api#177, by @zolkis.
-
-
2 issues closed.
-
Consider changing next() in ThingDiscovery w3c/wot-scripting-api#177.
-
Consider changing how Properties are read w3c/wot-scripting-api#178.
-
-
5 issues received 7 new comments.
-
WIP: Implementation experience while realizing new API in node-wot w3c/wot-scripting-api#180 (3 comments by @danielpeintner, @zolkis)
-
-
1 pull request opened.
-
Correct Web IDL for new errors. Add ed note for iterables. w3c/wot-scripting-api#179, by @zolkis.
-
-
1 pull request merged.
-
Correct Web IDL for new errors. Add ed note for iterables. w3c/wot-scripting-api#179.
-
-
1 pull request received 2 new comments.
-
Correct Web IDL for new errors. Add ed note for iterables. w3c/wot-scripting-api#179 (2 comments by @danielpeintner, @zolkis)
-
w3c/wot-thing-description
-
12 issues opened.
-
Question: difference between operation types writeallproperties vs. writemultipleproperties w3c/wot-thing-description#799, by @danielpeintner.
-
WoT TD ontology HTML document can describe how to retrieve turtle representation w3c/wot-thing-description#797, by @takuki.
-
Missing references for WebSub and Server-Sent Events w3c/wot-thing-description#795, by @takuki.
-
make privacy mitigations mandatory w3c/wot-thing-description#794, by @samuelweiler.
-
Name vs title in TD examples w3c/wot-thing-description#793, by @akeranen.
-
Remove or update github links in the spec w3c/wot-thing-description#792, by @sebastiankb.
-
should be clearer about where the definition of the HTTP Protocol Binding is w3c/wot-thing-description#791, by @dbaron.
-
Retrieve raw JSON data for context namespaces w3c/wot-thing-description#790, by @danielpeintner.
-
Handle at risk features before publishing as proposed rec w3c/wot-thing-description#789, by @kenchris.
-
Explainer: Mention alternative rejected solutions w3c/wot-thing-description#788, by @kenchris.
-
Move Transformation to RDF (now removed from TD) to TD ontology document w3c/wot-thing-description#787, by @takuki.
-
Move MQTT (and CoAP) example to Protocol Binding Templates document w3c/wot-thing-description#786, by @takuki.
-
-
3 issues closed.
-
WoT TD ontology HTML document can describe how to retrieve turtle representation w3c/wot-thing-description#797.
-
Missing references for WebSub and Server-Sent Events w3c/wot-thing-description#795.
-
Namespace IRIs need to be populated on w3.org Web server w3c/wot-thing-description#432.
-
-
17 issues received 43 new comments.
-
make privacy mitigations mandatory w3c/wot-thing-description#794 (10 comments by @mmccool, @pes10k, @samuelweiler, @sebastiankb, @takuki)
-
[At-Risk] Implementations of OAuth2SecurityScheme needed w3c/wot-thing-description#730 (6 comments by @benfrancis, @mkovatsc, @mlagally, @takuki)
-
Question: difference between operation types writeallproperties vs. writemultipleproperties w3c/wot-thing-description#799 (5 comments by @danielpeintner, @egekorkan, @sebastiankb, @takuki)
-
Retrieve raw JSON data for context namespaces w3c/wot-thing-description#790 (4 comments by @sebastiankb, @takuki)
-
Ontology HTML files are not yet WG Notes w3c/wot-thing-description#708 (3 comments by @ashimura, @mkovatsc, @takuki)
-
WoT TD ontology HTML document can describe how to retrieve turtle representation w3c/wot-thing-description#797 (2 comments by @sebastiankb, @takuki)
-
Missing references for WebSub and Server-Sent Events w3c/wot-thing-description#795 (2 comments by @sebastiankb, @takuki)
-
should be clearer about where the definition of the HTTP Protocol Binding is w3c/wot-thing-description#791 (1 comment by @takuki)
-
Handle at risk features before publishing as proposed rec w3c/wot-thing-description#789 (1 comment by @takuki)
-
Explainer: Mention alternative rejected solutions w3c/wot-thing-description#788 (1 comment by @takuki)
-
Move Transformation to RDF (now removed from TD) to TD ontology document w3c/wot-thing-description#787 (1 comment by @takuki)
-
clarify permitted language tags for titles/descriptions [I18N] w3c/wot-thing-description#642 (1 comment by @sebastiankb)
-
Thing Description Serialization and BOM [I18N] w3c/wot-thing-description#640 (1 comment by @sebastiankb)
-
DataSchema format field and patterns [I18N] w3c/wot-thing-description#639 (1 comment by @sebastiankb)
-
-
2 pull requests opened.
-
Small editorial improvements done on July 23, 2019. w3c/wot-thing-description#798, by @takuki.
-
Added references for WebSub and SSE (for issue #795) w3c/wot-thing-description#796, by @takuki.
-
-
2 pull requests merged.
-
Small editorial improvements done on July 23, 2019. w3c/wot-thing-description#798.
-
Added references for WebSub and SSE (for issue #795) w3c/wot-thing-description#796.
-
-
1 pull request received 1 new comment.
-
Small editorial improvements done on July 23, 2019. w3c/wot-thing-description#798 (1 comment by @sebastiankb)
-
w3c/wot-architecture
-
8 issues opened.
-
define "Private security (meta)data" w3c/wot-architecture#380, by @samuelweiler.
-
broken reference in definition of Personally Identifiable Information (PII) w3c/wot-architecture#377, by @dbaron.
-
definition of security is too weak w3c/wot-architecture#376, by @dbaron.
-
definition of privacy is too weak w3c/wot-architecture#375, by @dbaron.
-
Where did w3c-wot-td-context.jsonld and w3c-wot-common-context.jsonld go? w3c/wot-architecture#374, by @onovo1.
-
Add missing names of authors to the reference section. w3c/wot-architecture#372, by @mlagally.
-
TAG interoperability concerns w3c/wot-architecture#371, by @mlagally.
-
Review scripting API section wrt. TAG comment w3c/wot-architecture#370, by @mlagally.
-
-
2 issues closed.
-
Review scripting API section wrt. TAG comment w3c/wot-architecture#370.
-
Add missing names of authors to the reference section. w3c/wot-architecture#372.
-
-
10 issues received 29 new comments.
-
Where did w3c-wot-td-context.jsonld and w3c-wot-common-context.jsonld go? w3c/wot-architecture#374 (15 comments by @danielpeintner, @egekorkan, @mlagally, @onovo1, @takuki, @vcharpenay)
-
Review scripting API section wrt. TAG comment w3c/wot-architecture#370 (4 comments by @danielpeintner, @mlagally)
-
broken reference in definition of Personally Identifiable Information (PII) w3c/wot-architecture#377 (1 comment by @mlagally)
-
Add missing names of authors to the reference section. w3c/wot-architecture#372 (1 comment by @mlagally)
-
-
6 pull requests opened.
-
Add definition of private security configuration and data w3c/wot-architecture#381, by @k-toumura.
-
Described what JSON-LD additionally brings to processing (Issue #371) w3c/wot-architecture#379, by @takuki.
-
fix broken reference for "personally identifiable information" w3c/wot-architecture#378, by @mlagally.
-
Add missing names of authors to the reference section w3c/wot-architecture#373, by @mlagally.
-
Add definition for personally identifiable information w3c/wot-architecture#369, by @mlagally.
-
Delete definitions of Security and Privacy w3c/wot-architecture#368, by @mmccool.
-
-
4 pull requests merged.
-
Described what JSON-LD additionally brings to processing (Issue #371) w3c/wot-architecture#379.
-
fix broken reference for "personally identifiable information" w3c/wot-architecture#378.
-
Add definition for personally identifiable information w3c/wot-architecture#369.
-
Add missing names of authors to the reference section w3c/wot-architecture#373.
-
-
4 pull requests received 15 new comments.
-
Delete definitions of Security and Privacy w3c/wot-architecture#368 (11 comments by @mlagally, @mmccool, @takuki)
-
fix broken reference for "personally identifiable information" w3c/wot-architecture#378 (2 comments by @k-toumura)
-
Described what JSON-LD additionally brings to processing (Issue #371) w3c/wot-architecture#379 (1 comment by @mlagally)
-
Add definition for personally identifiable information w3c/wot-architecture#369 (1 comment by @mmccool)
-
w3c/wot-security
-
4 issues opened.
-
Review Lifecycle model w3c/wot-security#138, by @mlagally.
-
Review Privacy Mitigations for TD ids and fingerprinting w3c/wot-security#136, by @mmccool.
-
Clarify that an Update System is Necessary for Security w3c/wot-security#135, by @mmccool.
-
Update Definitions of Security and Privacy in Architecture Document w3c/wot-security#134, by @mmccool.
-
-
4 issues closed.
-
Update wot-security to align with Architecture CR vocabulary w3c/wot-security#126.
-
Change name to Security and Privacy Guidelines w3c/wot-security#129.
-
Merge "Security Testing Plan" document into this document w3c/wot-security#130.
-
Update the figures to follow new teminology w3c/wot-security#132.
-
-
6 issues received 12 new comments.
-
Terminology inconsistency - Proxy and Gateway are used interchangeably. w3c/wot-security#123 (3 comments by @mmccool, @takuki)
-
Update Definitions of Security and Privacy in Architecture Document w3c/wot-security#134 (3 comments by @mlagally, @mmccool)
-
Update wot-security to align with Architecture CR vocabulary w3c/wot-security#126 (1 comment by @mmccool)
-
Merge "Security Testing Plan" document into this document w3c/wot-security#130 (1 comment by @mmccool)
-
1 pull request opened.
-
Change "Local and Remote Proxy" to "Local and Remote Intermediary" w3c/wot-security#137, by @takuki.
-
-
1 pull request merged.
-
Fixing last figures w3c/wot-security#133.
-
Participants
-
1 organization joined.
-
Ierae Securiy, Inc. joined.
-
-
1 organization left.
-
Ierae Securiy, Inc. left.
-
GitHub
w3c/wot-thing-description
-
21 issues opened.
-
Dead links in the implementation report w3c/wot-thing-description#775, by @egekorkan.
-
TD Producer field in TD (similar to Server header field in HTTP) w3c/wot-thing-description#774, by @mkovatsc.
-
TD Processor: Clarify that TD Producer only or TD Consumer only is valid w3c/wot-thing-description#772, by @mkovatsc.
-
Status of Ontology Documents w3c/wot-thing-description#770, by @vcharpenay.
-
Update Recent Changes section for Proposed REC w3c/wot-thing-description#769, by @takuki.
-
Update references to "Security and Privacy Guidelines" w3c/wot-thing-description#760, by @mmccool.
-
Reconsider security & securityDefinitions being mandatory w3c/wot-thing-description#757, by @benfrancis.
-
[Testing] td-titles-descriptions is tested wrongly w3c/wot-thing-description#753, by @egekorkan.
-
DISCUSS: Can we Relax Implementation Requirements for Extensions? w3c/wot-thing-description#752, by @mmccool.
-
Add a way to supress output lines in implementation report w3c/wot-thing-description#751, by @mmccool.
-
[Testing] Additional Implementations required for Basic Sec w3c/wot-thing-description#750, by @egekorkan.
-
[Testing] Additional implementations required for BearerSec w3c/wot-thing-description#749, by @egekorkan.
-
[Testing] Additional Implementations needed for Form features w3c/wot-thing-description#748, by @egekorkan.
-
[Testing] Additional Implementations need to cover the op values w3c/wot-thing-description#747, by @egekorkan.
-
[Testing] Automated Tests Needed for Some "Manual" Assertions w3c/wot-thing-description#743, by @mmccool.
-
[Testing] Manual Validation is Needed for Security Assertions w3c/wot-thing-description#742, by @mmccool.
-
[Testing] Manual Validation is needed for Multilanguage Assertions w3c/wot-thing-description#741, by @mmccool.
-
[Testing] Manual Validation needed for ExpectedResponse contentType Assertion w3c/wot-thing-description#740, by @mmccool.
-
[Testing] Implementations of Digest QoP sub-feature needed w3c/wot-thing-description#739, by @mmccool.
-
[Testing] Additional Manual Validation Needed for Text Direction Assertions w3c/wot-thing-description#738, by @mmccool.
-
[Testing] Additional Manual Validation for IANA Requirements Needed w3c/wot-thing-description#737, by @mmccool.
-
-
47 issues closed.
-
[At-Risk] Implementations of proxy feature in SecurityScheme needed w3c/wot-thing-description#729.
-
Update Recent Changes section for Proposed REC w3c/wot-thing-description#769.
-
Status of Ontology Documents w3c/wot-thing-description#770.
-
TD Processor: Clarify that TD Producer only or TD Consumer only is valid w3c/wot-thing-description#772.
-
Figure 2 title "JSON schema vocabulary" should be "Data Schema Vocabulary" w3c/wot-thing-description#700.
-
[Testing] Additional Implementations need to cover the op values w3c/wot-thing-description#747.
-
DISCUSS: Can we Relax Implementation Requirements for Extensions? w3c/wot-thing-description#752.
-
[Testing] Wrong default value in assertion descriptions of td-default-X w3c/wot-thing-description#702.
-
[Testing] td-default-idempotent is used for writeOnly w3c/wot-thing-description#701.
-
Specification of @type w3c/wot-thing-description#698.
-
WoT Test Cases document? w3c/wot-thing-description#699.
-
Ontology HTML files are not yet WG Notes w3c/wot-thing-description#708.
-
Describe automated testing in TD Implementation Report w3c/wot-thing-description#710.
-
[Testing] Additional implementation needed for Action features w3c/wot-thing-description#717.
-
[Testing] Additional implementations needed for HTTP method defaults w3c/wot-thing-description#719.
-
[Testing] Additional implementations are needed for Event features w3c/wot-thing-description#720.
-
[Testing] Additional assertions needed for JSON open ecosystem requirements w3c/wot-thing-description#721.
-
[Testing] Additional Manual Validation Needed for Text Direction Assertions w3c/wot-thing-description#738.
-
[At-Risk] Implementations of APIKeySecurityScheme needed w3c/wot-thing-description#736.
-
[Testing] Manual Validation is Needed for Security Assertions w3c/wot-thing-description#742.
-
[Testing] Manual Validation is needed for Multilanguage Assertions w3c/wot-thing-description#741.
-
Dead links in the implementation report w3c/wot-thing-description#775.
-
[Testing] Additional implementations required for BearerSec w3c/wot-thing-description#749.
-
Leftover change - "name" to "title" w3c/wot-thing-description#696.
-
Example 33 is missing op for status Property w3c/wot-thing-description#714.
-
Editorial and other minor comments w3c/wot-thing-description#679.
-
No link to A.2 in toc w3c/wot-thing-description#706.
-
Lingual correction in 5.3.1.3 PropertyAffordance w3c/wot-thing-description#711.
-
Example 32 Event form missing default value listing w3c/wot-thing-description#713.
-
[Testing] Additional Implementations needed for DataSchema features w3c/wot-thing-description#718.
-
[Testing] Additional Manual Validation for IANA Requirements Needed w3c/wot-thing-description#737.
-
[Testing] Test results for op in Form seem to be incorrect w3c/wot-thing-description#726.
-
[Testing] Additional implementations are needed for Security features w3c/wot-thing-description#725.
-
Update references to "Security and Privacy Guidelines" w3c/wot-thing-description#760.
-
[Testing] Additional implementations are needed for Link features w3c/wot-thing-description#724.
-
Fix respec issues w3c/wot-thing-description#686.
-
[At-Risk] Implementations of qop feature of DigestSecurityScheme needed w3c/wot-thing-description#734.
-
[Testing] Manual Validation needed for ExpectedResponse contentType Assertion w3c/wot-thing-description#740.
-
[Testing] Additional Implementations needed for Form features w3c/wot-thing-description#748.
-
[Testing] Automated Tests Needed for Some "Manual" Assertions w3c/wot-thing-description#743.
-
[Testing] Additional implementations are needed for Property features w3c/wot-thing-description#723.
-
[Testing] Additional Implementations required for Basic Sec w3c/wot-thing-description#750.
-
[Testing] Test results for type in DataSchema seem to be incorrect w3c/wot-thing-description#728.
-
Add a way to supress output lines in implementation report w3c/wot-thing-description#751.
-
[Testing] td-titles-descriptions is tested wrongly w3c/wot-thing-description#753.
-
[Testing] Additional Examples are needed for MultiLanguage objects w3c/wot-thing-description#722.
-
[Testing] Additional implementations needed for Thing features w3c/wot-thing-description#727.
-
-
1 issue reopened.
-
Leftover change - "name" to "title" w3c/wot-thing-description#696, by @danielpeintner.
-
-
57 issues received 186 new comments.
-
[Testing] Additional Manual Validation Needed for Text Direction Assertions w3c/wot-thing-description#738 (13 comments by @k-toumura, @mkovatsc, @mmccool, @takuki)
-
[Testing] Additional Implementations needed for DataSchema features w3c/wot-thing-description#718 (11 comments by @egekorkan, @mmccool, @sebastiankb)
-
[Testing] Manual Validation is Needed for Security Assertions w3c/wot-thing-description#742 (10 comments by @mkovatsc, @mmccool, @takuki, @vcharpenay, @yamagile)
-
Reconsider security & securityDefinitions being mandatory w3c/wot-thing-description#757 (9 comments by @benfrancis, @draggett, @mkovatsc, @mlagally, @mmccool)
-
[Testing] Implementations of Digest QoP sub-feature needed w3c/wot-thing-description#739 (8 comments by @mkovatsc, @mmccool, @yamagile)
-
DISCUSS: Can we Relax Implementation Requirements for Extensions? w3c/wot-thing-description#752 (8 comments by @mkovatsc, @mmccool, @sebastiankb, @takuki)
-
[Testing] Additional Implementations need to cover the op values w3c/wot-thing-description#747 (7 comments by @egekorkan, @mkovatsc, @mmccool)
-
[Testing] Additional assertions needed for JSON open ecosystem requirements w3c/wot-thing-description#721 (6 comments by @danielpeintner, @egekorkan, @mkovatsc, @mmccool, @takuki)
-
Dead links in the implementation report w3c/wot-thing-description#775 (6 comments by @egekorkan, @mkovatsc, @mmccool)
-
[Testing] Automated Tests Needed for Some "Manual" Assertions w3c/wot-thing-description#743 (6 comments by @egekorkan, @mmccool)
-
[At-Risk] Implementations of OAuth2SecurityScheme needed w3c/wot-thing-description#730 (5 comments by @mkovatsc, @mmccool, @sebastiankb, @yamagile)
-
[Testing] Manual Validation is needed for Multilanguage Assertions w3c/wot-thing-description#741 (5 comments by @k-toumura, @mkovatsc, @mmccool, @takuki)
-
[Testing] Additional implementations are needed for Link features w3c/wot-thing-description#724 (5 comments by @mkovatsc, @mmccool)
-
[Testing] Additional implementations are needed for Event features w3c/wot-thing-description#720 (4 comments by @mkovatsc, @mmccool, @sebastiankb)
-
[Testing] Additional implementations are needed for Property features w3c/wot-thing-description#723 (4 comments by @egekorkan, @mmccool)
-
[Testing] Additional Implementations required for Basic Sec w3c/wot-thing-description#750 (4 comments by @mkovatsc, @mmccool, @yamagile)
-
TD Processor: Clarify that TD Producer only or TD Consumer only is valid w3c/wot-thing-description#772 (3 comments by @mkovatsc)
-
[Testing] Additional implementation needed for Action features w3c/wot-thing-description#717 (3 comments by @mkovatsc, @mmccool)
-
[Testing] Additional implementations needed for HTTP method defaults w3c/wot-thing-description#719 (3 comments by @mkovatsc, @mmccool)
-
[Testing] Additional implementations required for BearerSec w3c/wot-thing-description#749 (3 comments by @mkovatsc, @yamagile)
-
Leftover change - "name" to "title" w3c/wot-thing-description#696 (3 comments by @danielpeintner, @sebastiankb, @takuki)
-
[Testing] Test results for op in Form seem to be incorrect w3c/wot-thing-description#726 (3 comments by @egekorkan, @mmccool)
-
Add a way to supress output lines in implementation report w3c/wot-thing-description#751 (3 comments by @mmccool)
-
[At-Risk] Implementations of proxy feature in SecurityScheme needed w3c/wot-thing-description#729 (2 comments by @mkovatsc, @mmccool)
-
Update Recent Changes section for Proposed REC w3c/wot-thing-description#769 (2 comments by @mkovatsc)
-
Figure 2 title "JSON schema vocabulary" should be "Data Schema Vocabulary" w3c/wot-thing-description#700 (2 comments by @mkovatsc, @takuki)
-
No "with default values" checkbox for Appendix A examples w3c/wot-thing-description#715 (2 comments by @mkovatsc)
-
[Testing] td-default-idempotent is used for writeOnly w3c/wot-thing-description#701 (2 comments by @mkovatsc, @mmccool)
-
[At-Risk] Implementations of PSKSecurityScheme needed w3c/wot-thing-description#733 (2 comments by @mkovatsc, @mmccool)
-
[At-Risk] Implementations of APIKeySecurityScheme needed w3c/wot-thing-description#736 (2 comments by @mkovatsc, @yamagile)
-
Make a request for TD media type registration at IANA w3c/wot-thing-description#560 (2 comments by @mkovatsc)
-
[Testing] Additional Manual Validation for IANA Requirements Needed w3c/wot-thing-description#737 (2 comments by @mmccool)
-
[Testing] Additional implementations are needed for Security features w3c/wot-thing-description#725 (2 comments by @mmccool)
-
Example 33 is missing op for status Property w3c/wot-thing-description#714 (2 comments by @sebastiankb)
-
Example 32 Event form missing default value listing w3c/wot-thing-description#713 (2 comments by @sebastiankb)
-
Lingual correction in 5.3.1.3 PropertyAffordance w3c/wot-thing-description#711 (2 comments by @sebastiankb)
-
[Testing] Additional Implementations needed for Form features w3c/wot-thing-description#748 (2 comments by @egekorkan, @mmccool)
-
[Testing] Test results for type in DataSchema seem to be incorrect w3c/wot-thing-description#728 (2 comments by @egekorkan, @mmccool)
-
[Testing] Wrong default value in assertion descriptions of td-default-X w3c/wot-thing-description#702 (1 comment by @mkovatsc)
-
Describe automated testing in TD Implementation Report w3c/wot-thing-description#710 (1 comment by @mkovatsc)
-
[At-Risk] Implementations of CertSecurityScheme needed w3c/wot-thing-description#732 (1 comment by @mkovatsc)
-
[At-Risk] Implementations of PublicSecurityScheme needed w3c/wot-thing-description#735 (1 comment by @mkovatsc)
-
Update references to "Security and Privacy Guidelines" w3c/wot-thing-description#760 (1 comment by @mmccool)
-
[At-Risk] Implementations of qop feature of DigestSecurityScheme needed w3c/wot-thing-description#734 (1 comment by @mmccool)
-
[Testing] Manual Validation needed for ExpectedResponse contentType Assertion w3c/wot-thing-description#740 (1 comment by @mmccool)
-
[Testing] td-titles-descriptions is tested wrongly w3c/wot-thing-description#753 (1 comment by @egekorkan)
-
[Testing] Additional Examples are needed for MultiLanguage objects w3c/wot-thing-description#722 (1 comment by @mmccool)
-
[Testing] Additional implementations needed for Thing features w3c/wot-thing-description#727 (1 comment by @mmccool)
-
-
28 pull requests opened.
-
Remove heading 7.2 w3c/wot-thing-description#785, by @mkovatsc.
-
Update changelog (fix #769) w3c/wot-thing-description#784, by @mkovatsc.
-
Fix ontology documentation file status (now ED) (#770) w3c/wot-thing-description#783, by @mkovatsc.
-
Remove Appendix D (see resolution) w3c/wot-thing-description#782, by @mkovatsc.
-
Clarify TD Processor (#772) w3c/wot-thing-description#781, by @mkovatsc.
-
Figure 2 title was changed to "Data Schema Vocabulary" (Issue #700) w3c/wot-thing-description#780, by @takuki.
-
Figure 2 title was changed to "Data Schema Vocabulary" (Issue #700) w3c/wot-thing-description#779, by @takuki.
-
Added Recent Changes section for changes made since Candidate Recommendation w3c/wot-thing-description#778, by @takuki.
-
Add RFC references for security schemes w3c/wot-thing-description#777, by @mkovatsc.
-
Update Links on report and report template w3c/wot-thing-description#776, by @egekorkan.
-
add extra asserts for bearer extensions w3c/wot-thing-description#773, by @egekorkan.
-
Update oracle.html w3c/wot-thing-description#771, by @mlagally.
-
String-meta requirement is not an assertion in TD (Issue #738) w3c/wot-thing-description#768, by @takuki.
-
String-meta requirement is not an assertion in TD (Issue #738) w3c/wot-thing-description#767, by @takuki.
-
A requirement (Can ignore BOM) is not an assertion of TD (Issue #721) w3c/wot-thing-description#766, by @takuki.
-
A requirement (Can ignore BOM) is not an assertion of TD (Issue #721) w3c/wot-thing-description#765, by @takuki.
-
Added Matthias as a co-editor, added several names in acknowledgement. w3c/wot-thing-description#764, by @takuki.
-
Update Implementation Report Instructions w3c/wot-thing-description#763, by @mmccool.
-
New Implementation Report Draft: June 11 w3c/wot-thing-description#762, by @mmccool.
-
Update Wot Security and Privacy Guidelines reference w3c/wot-thing-description#761, by @mmccool.
-
Fix some editorial issues (replaces PR #758) w3c/wot-thing-description#759, by @sebastiankb.
-
WIP: fix some editorial issues w3c/wot-thing-description#758, by @sebastiankb.
-
Final post-WS2 F2F Implementation Report Draft w3c/wot-thing-description#756, by @mmccool.
-
Update test results w3c/wot-thing-description#755, by @mmccool.
-
Updated test report after day 1 of post-WS2 F2F w3c/wot-thing-description#754, by @mmccool.
-
New test results post-WS2 w3c/wot-thing-description#746, by @mmccool.
-
[Testing] add new extra asserts w3c/wot-thing-description#745, by @egekorkan.
-
WIP: Updated RDF vocabularies w3c/wot-thing-description#744, by @vcharpenay.
-
-
27 pull requests merged.
-
Update changelog (fix #769) w3c/wot-thing-description#784.
-
Remove heading 7.2 w3c/wot-thing-description#785.
-
Clarify TD Processor (#772) w3c/wot-thing-description#781.
-
Remove Appendix D (see resolution) w3c/wot-thing-description#782.
-
Fix ontology documentation file status (now ED) (#770) w3c/wot-thing-description#783.
-
Figure 2 title was changed to "Data Schema Vocabulary" (Issue #700) w3c/wot-thing-description#780.
-
Figure 2 title was changed to "Data Schema Vocabulary" (Issue #700) w3c/wot-thing-description#779.
-
Add RFC references for security schemes w3c/wot-thing-description#777.
-
Added Recent Changes section for changes made since Candidate Recommendation w3c/wot-thing-description#778.
-
Update Links on report and report template w3c/wot-thing-description#776.
-
add extra asserts for bearer extensions w3c/wot-thing-description#773.
-
Refactored RDF examples for simplicity w3c/wot-thing-description#688.
-
Update oracle.html w3c/wot-thing-description#771.
-
reflected feedback from CR except rfc2119-assertion w3c/wot-thing-description#716.
-
Fix some editorial issues (replaces PR #758) w3c/wot-thing-description#759.
-
String-meta requirement is not an assertion in TD (Issue #738) w3c/wot-thing-description#767.
-
A requirement (Can ignore BOM) is not an assertion of TD (Issue #721) w3c/wot-thing-description#765.
-
Added Matthias as a co-editor, added several names in acknowledgement. w3c/wot-thing-description#764.
-
Update Implementation Report Instructions w3c/wot-thing-description#763.
-
New Implementation Report Draft: June 11 w3c/wot-thing-description#762.
-
Update Wot Security and Privacy Guidelines reference w3c/wot-thing-description#761.
-
Final post-WS2 F2F Implementation Report Draft w3c/wot-thing-description#756.
-
Update test results w3c/wot-thing-description#755.
-
Updated test report after day 1 of post-WS2 F2F w3c/wot-thing-description#754.
-
New test results post-WS2 w3c/wot-thing-description#746.
-
[Testing] add new extra asserts w3c/wot-thing-description#745.
-
Update Test results post-CR (using only TDs provided by implementers) w3c/wot-thing-description#707.
-
-
1 pull request closed.
-
WIP: fix some editorial issues w3c/wot-thing-description#758.
-
-
14 pull requests received 33 new comments.
-
Refactored RDF examples for simplicity w3c/wot-thing-description#688 (11 comments by @mlagally, @sebastiankb, @takuki, @vcharpenay)
-
A requirement (Can ignore BOM) is not an assertion of TD (Issue #721) w3c/wot-thing-description#766 (4 comments by @mkovatsc, @mmccool, @takuki)
-
WIP: Updated RDF vocabularies w3c/wot-thing-description#744 (3 comments by @mkovatsc, @takuki, @vcharpenay)
-
reflected feedback from CR except rfc2119-assertion w3c/wot-thing-description#716 (2 comments by @mmccool)
-
Figure 2 title was changed to "Data Schema Vocabulary" (Issue #700) w3c/wot-thing-description#780 (1 comment by @mkovatsc)
-
String-meta requirement is not an assertion in TD (Issue #738) w3c/wot-thing-description#768 (1 comment by @mmccool)
-
Fix some editorial issues (replaces PR #758) w3c/wot-thing-description#759 (1 comment by @sebastiankb)
-
w3c/wot-architecture
-
4 issues opened.
-
General TL;DR problem w3c/wot-architecture#366, by @mkovatsc.
-
Define gateway w3c/wot-architecture#365, by @samuelweiler.
-
How does one connect "directly to the cloud"? w3c/wot-architecture#364, by @samuelweiler.
-
Update changelog for PR transition w3c/wot-architecture#363, by @mkovatsc.
-
-
4 issues closed.
-
Accessibility review of figures w3c/wot-architecture#314.
-
Update changelog for PR transition w3c/wot-architecture#363.
-
Acknowledge all contributors w3c/wot-architecture#329.
-
WoT Security and Privacy Considerations vs Guidelines w3c/wot-architecture#323.
-
-
9 issues received 19 new comments.
-
Update Wikipedia page on WoT w3c/wot-architecture#207 (4 comments by @mkovatsc, @mlagally, @mmccool, @smnmyr)
-
WoT Security and Privacy Considerations vs Guidelines w3c/wot-architecture#323 (2 comments by @mlagally, @mmccool)
-
-
6 pull requests opened.
-
restoring images for TAG explainer w3c/wot-architecture#367, by @mlagally.
-
Update index.html w3c/wot-architecture#362, by @mlagally.
-
Update index.html w3c/wot-architecture#361, by @mlagally.
-
Update index.html w3c/wot-architecture#360, by @mlagally.
-
regenerate PNG and add SVG files w3c/wot-architecture#359, by @k-toumura.
-
Accessibility+cleanup w3c/wot-architecture#358, by @mlagally.
-
-
7 pull requests merged.
-
restoring images for TAG explainer w3c/wot-architecture#367.
-
Update index.html w3c/wot-architecture#360.
-
Update index.html w3c/wot-architecture#361.
-
Update index.html w3c/wot-architecture#362.
-
regenerate PNG and add SVG files w3c/wot-architecture#359.
-
Accessibility+cleanup w3c/wot-architecture#358.
-
Update index.html w3c/wot-architecture#355.
-
-
2 pull requests received 2 new comments.
w3c/wot-binding-templates
-
11 issues opened.
-
Introduction section structure and content w3c/wot-binding-templates#62, by @takuki.
-
no vacabulary defintion for CoAP and MQTT yet w3c/wot-binding-templates#61, by @sebastiankb.
-
subProtocol lowercase only w3c/wot-binding-templates#60, by @sebastiankb.
-
Meta-interaction is missing from section 2.3 Interaction Types w3c/wot-binding-templates#59, by @takuki.
-
Media Types should be Content Types w3c/wot-binding-templates#58, by @takuki.
-
Section name 2.2.1 "Relation Types" is not accurate w3c/wot-binding-templates#57, by @takuki.
-
subscription, data, cancellation need to be added w3c/wot-binding-templates#56, by @takuki.
-
Mention of XML should be dropped w3c/wot-binding-templates#55, by @takuki.
-
"unobserveproperty" is missing w3c/wot-binding-templates#54, by @takuki.
-
"Platforms" with more than one meaning should be clarified w3c/wot-binding-templates#53, by @takuki.
-
Review comments from August 2018 w3c/wot-binding-templates#52, by @takuki.
-
-
1 issue received 1 new comment.
-
"Platforms" with more than one meaning should be clarified w3c/wot-binding-templates#53 (1 comment by @sebastiankb)
-
w3c/wot-scripting-api
-
3 issues opened.
-
ConsumeThing.instance is misleading w3c/wot-scripting-api#176, by @relu91.
-
Separate the client and server interfaces w3c/wot-scripting-api#173, by @zolkis.
-
Update references to "Security and Privacy Guidelines" w3c/wot-scripting-api#172, by @mmccool.
-
-
18 issues closed.
-
Align argument names with terminology in TD spec w3c/wot-scripting-api#146.
-
Security Testing and Validation URLs return 404 w3c/wot-scripting-api#151.
-
Synchronization use cases w3c/wot-scripting-api#28.
-
Support for Capabilities w3c/wot-scripting-api#44.
-
Consequences of setting "writable" to false for Scripting w3c/wot-scripting-api#106.
-
Specify result of writeProperty() method w3c/wot-scripting-api#110.
-
Should Thing Directory Interface (register/unregister/discover) be part of WoT standard? w3c/wot-scripting-api#126.
-
URI Templates / Variables (Alignment with Binding&TD) w3c/wot-scripting-api#149.
-
Improve discover() signature w3c/wot-scripting-api#137.
-
WebIDL : attributes vs functions w3c/wot-scripting-api#167.
-
Remove Discovery from Core WoT interface? w3c/wot-scripting-api#168.
-
ConsumeThing.instance is misleading w3c/wot-scripting-api#176.
-
Last minute TD change: "name" changed to "title" on thing level w3c/wot-scripting-api#171.
-
Update references to "Security and Privacy Guidelines" w3c/wot-scripting-api#172.
-
Separate the client and server interfaces w3c/wot-scripting-api#173.
-
Exposing notifications, subscribe, unsubscribe w3c/wot-scripting-api#153.
-
Mechanism for Observing Things, Properties, handling Thing Events and Discovery w3c/wot-scripting-api#158.
-
Exclude fetch specification from Scripting API w3c/wot-scripting-api#162.
-
-
17 issues received 19 new comments.
-
Consequences of setting "writable" to false for Scripting w3c/wot-scripting-api#106 (1 comment by @zolkis)
-
Should Thing Directory Interface (register/unregister/discover) be part of WoT standard? w3c/wot-scripting-api#126 (1 comment by @zolkis)
-
URI Templates / Variables (Alignment with Binding&TD) w3c/wot-scripting-api#149 (1 comment by @zolkis)
-
Produce() method should ignore instance specific information w3c/wot-scripting-api#156 (1 comment by @zolkis)
-
Mechanism for Observing Things, Properties, handling Thing Events and Discovery w3c/wot-scripting-api#158 (1 comment by @zolkis)
-
2 pull requests opened.
-
Rebase the draft branch w3c/wot-scripting-api#175, by @zolkis.
-
Separate client and server API w3c/wot-scripting-api#174, by @zolkis.
-
-
2 pull requests merged.
-
Separate client and server API w3c/wot-scripting-api#174.
-
Rebase the draft branch w3c/wot-scripting-api#175.
-
-
1 pull request received 9 new comments.
w3c/wot-security
-
3 issues opened.
-
Update the figures to follow new teminology w3c/wot-security#132, by @ereshetova.
-
Merge "Security Testing Plan" document into this document w3c/wot-security#130, by @mmccool.
-
Change name to Security and Privacy Guidelines w3c/wot-security#129, by @mmccool.
-
-
3 pull requests opened.
-
Fixing last figures w3c/wot-security#133, by @ereshetova.
-
WoT S&P note updates w3c/wot-security#131, by @ereshetova.
-
typo fix: dutes->duties w3c/wot-security#128, by @terriko.
-
-
3 pull requests merged.
-
WoT S&P note updates w3c/wot-security#131.
-
typo fix: dutes->duties w3c/wot-security#128.
-
various small fixes around general readability and display w3c/wot-security#127.
-
-
2 pull requests received 2 new comments.
w3c/wot-security-best-practices
-
1 pull request opened.
-
doc: Link to published HTML file w3c/wot-security-best-practices#4, by @rzr.
-
TR publications
-
2 documents published.
-
Web of Things (WoT) Architecture published as a Candidate Recommendation Snapshot. History of Web of Things (WoT) Architecture
-
Web of Things (WoT) Thing Description published as a Candidate Recommendation Snapshot. History of Web of Things (WoT) Thing Description
-
Participants
-
1 participant joined.
-
Joshue O'Connor (W3C) joined.
-
GitHub
w3c/wot-thing-description
-
87 issues opened.
-
[At-Risk] Implementations of APIKeySecurityScheme needed w3c/wot-thing-description#736, by @mmccool.
-
[At-Risk] Implementations of PublicSecurityScheme needed w3c/wot-thing-description#735, by @mmccool.
-
[At-Risk] Implementations of qop feature of DigestSecurityScheme needed w3c/wot-thing-description#734, by @mmccool.
-
[At-Risk] Implementations of PSKSecurityScheme needed w3c/wot-thing-description#733, by @mmccool.
-
[At-Risk] Implementations of CertSecurityScheme needed w3c/wot-thing-description#732, by @mmccool.
-
Bringing back PoP Security Scheme w3c/wot-thing-description#731, by @mmccool.
-
[At-Risk] Implementations of OAuth2SecurityScheme needed w3c/wot-thing-description#730, by @mmccool.
-
[At-Risk] Implementations of proxy feature in SecurityScheme needed w3c/wot-thing-description#729, by @mmccool.
-
[Testing] Test results for type in DataSchema seem to be incorrect w3c/wot-thing-description#728, by @mmccool.
-
[Testing] Additional implementations needed for Thing features w3c/wot-thing-description#727, by @mmccool.
-
[Testing] Test results for op in Form seem to be incorrect w3c/wot-thing-description#726, by @mmccool.
-
[Testing] Additional implementations are needed for Security features w3c/wot-thing-description#725, by @mmccool.
-
[Testing] Additional implementations are needed for Link features w3c/wot-thing-description#724, by @mmccool.
-
[Testing] Additional implementations are needed for Property features w3c/wot-thing-description#723, by @mmccool.
-
[Testing] Additional Examples are needed for MultiLanguage objects w3c/wot-thing-description#722, by @mmccool.
-
[Testing] Additional assertions needed for JSON open ecosystem requirements w3c/wot-thing-description#721, by @mmccool.
-
[Testing] Additional implementations are needed for Event features w3c/wot-thing-description#720, by @mmccool.
-
[Testing] Additional implementations needed for HTTP method defaults w3c/wot-thing-description#719, by @mmccool.
-
[Testing] Additional Implementations needed for DataSchema features w3c/wot-thing-description#718, by @mmccool.
-
[Testing] Additional implementation needed for Action features w3c/wot-thing-description#717, by @mmccool.
-
No "with default values" checkbox for Appendix A examples w3c/wot-thing-description#715, by @mkovatsc.
-
Example 33 is missing op for status Property w3c/wot-thing-description#714, by @mkovatsc.
-
Example 32 Event form missing default value listing w3c/wot-thing-description#713, by @mkovatsc.
-
Multiple methodName's ? w3c/wot-thing-description#712, by @danielpeintner.
-
Lingual correction in 5.3.1.3 PropertyAffordance w3c/wot-thing-description#711, by @mkovatsc.
-
Describe automated testing in TD Implementation Report w3c/wot-thing-description#710, by @mmccool.
-
Ontology HTML files are not yet WG Notes w3c/wot-thing-description#708, by @takuki.
-
No link to A.2 in toc w3c/wot-thing-description#706, by @sebastiankb.
-
[Testing] td-data-schema-objects_properties should be removed w3c/wot-thing-description#704, by @egekorkan.
-
[Testing] td-data-schema-objects_items is still present w3c/wot-thing-description#703, by @egekorkan.
-
[Testing] Wrong default value in assertion descriptions of td-default-X w3c/wot-thing-description#702, by @egekorkan.
-
[Testing] td-default-idempotent is used for writeOnly w3c/wot-thing-description#701, by @egekorkan.
-
Figure 2 title "JSON schema vocabulary" should be "Data Schema Vocabulary" w3c/wot-thing-description#700, by @takuki.
-
WoT Test Cases document? w3c/wot-thing-description#699, by @mkovatsc.
-
Specification of @type w3c/wot-thing-description#698, by @vcharpenay.
-
Leftover change - "name" to "title" w3c/wot-thing-description#696, by @danielpeintner.
-
Fix respec issues w3c/wot-thing-description#686, by @mlagally.
-
Editorial and other minor comments w3c/wot-thing-description#679, by @danielpeintner.
-
Figure 1: Ensure Subclass relation between PropertyAffordance and DataSchema is visible w3c/wot-thing-description#678, by @mkovatsc.
-
Section 4 needs better clearification about the context file usage w3c/wot-thing-description#676, by @sebastiankb.
-
Need a $id for the JSON Schema w3c/wot-thing-description#674, by @jmcanterafonseca.
-
@context for TD trailing '/' ? w3c/wot-thing-description#673, by @jmcanterafonseca.
-
Checklist for collected issues w3c/wot-thing-description#671, by @mkovatsc.
-
both class instantiation constraints must apply w3c/wot-thing-description#670, by @mlagally.
-
Section 5: assignment function is underspecified w3c/wot-thing-description#669, by @mlagally.
-
Improve definitions of type and assignment functions w3c/wot-thing-description#668, by @mlagally.
-
Section 5: The instance relationship for simple types is unclear w3c/wot-thing-description#667, by @mlagally.
-
Semantically equivalence and semantic validity of TD‘s is undefined w3c/wot-thing-description#666, by @mlagally.
-
JSON-LD context file w3c/wot-thing-description#665, by @mlagally.
-
Namespace clarifications by Ralph w3c/wot-thing-description#654, by @mkovatsc.
-
Alternative Namespaces (www.w3.org/ns/...) w3c/wot-thing-description#652, by @mkovatsc.
-
Acknowledge all contributors w3c/wot-thing-description#649, by @mlagally.
-
base direction considerations [I18N] w3c/wot-thing-description#643, by @aphillips.
-
clarify permitted language tags for titles/descriptions [I18N] w3c/wot-thing-description#642, by @aphillips.
-
dateTime reference when mapping to JSON types [I18N] w3c/wot-thing-description#641, by @aphillips.
-
Thing Description Serialization and BOM [I18N] w3c/wot-thing-description#640, by @aphillips.
-
DataSchema format field and patterns [I18N] w3c/wot-thing-description#639, by @aphillips.
-
Clarify about language negotiation [I18N] w3c/wot-thing-description#638, by @aphillips.
-
Multilanguage section clarity [I18N] w3c/wot-thing-description#637, by @aphillips.
-
(editorial) content type examples may be misleading w3c/wot-thing-description#636, by @aphillips.
-
No mechanism to indicate what the "default language" of a description is [I18N] w3c/wot-thing-description#635, by @aphillips.
-
Make value of "support" an anyURI w3c/wot-thing-description#633, by @mmccool.
-
Tables in Section 5 should use proper Type terms w3c/wot-thing-description#631, by @mkovatsc.
-
Human-readable "name" has i18n problem - rely on "title"/"titles" in Thing instead? w3c/wot-thing-description#630, by @mmccool.
-
Inconsistency on accepted values for @context w3c/wot-thing-description#628, by @egekorkan.
-
`ThingDescription` term shall be defined in the @context and be the @type of TDs? w3c/wot-thing-description#627, by @jmcanterafonseca.
-
change the order of the terms in the Form class table w3c/wot-thing-description#621, by @mkovatsc.
-
Modify list of formats in token SecurityScheme to allow for extensions w3c/wot-thing-description#618, by @mkovatsc.
-
Allow array for response in From class? w3c/wot-thing-description#617, by @mkovatsc.
-
Serialization assertions in Section 5 w3c/wot-thing-description#615, by @mkovatsc.
-
Make security scheme identifiers more visible w3c/wot-thing-description#613, by @mkovatsc.
-
Misleading assertions for security w3c/wot-thing-description#612, by @mkovatsc.
-
Default value of "contentType" in "response" w3c/wot-thing-description#611, by @mkovatsc.
-
JSON name vs member and other corrections w3c/wot-thing-description#609, by @mkovatsc.
-
Usage of the term Vocabulary Term w3c/wot-thing-description#608, by @mkovatsc.
-
Incomplete change to Affordances w3c/wot-thing-description#607, by @mkovatsc.
-
Make Section 6. Thing Description Serialization normative w3c/wot-thing-description#606, by @mkovatsc.
-
Update 2. Terminology w3c/wot-thing-description#605, by @mkovatsc.
-
Consider to cross reference JSON Schema definitions (external or internal) w3c/wot-thing-description#604, by @jmcanterafonseca.
-
Typo throughout the draft w3c/wot-thing-description#602, by @jmcanterafonseca.
-
Annex B : ThingTemplate : Is it normative? w3c/wot-thing-description#600, by @jmcanterafonseca.
-
Example 2 title could be improved w3c/wot-thing-description#599, by @jmcanterafonseca.
-
Add text direction definition w3c/wot-thing-description#598, by @mmccool.
-
Update at-risk and minimize spurious highlighting w3c/wot-thing-description#597, by @mmccool.
-
Remove Direct Reference to wot-security-best-practices w3c/wot-thing-description#596, by @mmccool.
-
i18n checklist for "Defining language values" w3c/wot-thing-description#595, by @ashimura.
-
id field in TD Templates w3c/wot-thing-description#593, by @egekorkan.
-
-
83 issues closed.
-
[Testing] td-data-schema-objects_items is still present w3c/wot-thing-description#703.
-
[Testing] td-data-schema-objects_properties should be removed w3c/wot-thing-description#704.
-
Figure 1: Ensure Subclass relation between PropertyAffordance and DataSchema is visible w3c/wot-thing-description#678.
-
Acknowledge all contributors w3c/wot-thing-description#649.
-
Check against i18n Review Checklist w3c/wot-thing-description#582.
-
i18n checklist for declaring language at the resource level w3c/wot-thing-description#584.
-
i18n checklist for Working with numbers w3c/wot-thing-description#579.
-
Make Section 6. Thing Description Serialization normative w3c/wot-thing-description#606.
-
Human-readable "name" has i18n problem - rely on "title"/"titles" in Thing instead? w3c/wot-thing-description#630.
-
i18n checklist for Working with time w3c/wot-thing-description#578.
-
i18n checklist for Working with personal names w3c/wot-thing-description#580.
-
i18n checklist for "Defining language values" w3c/wot-thing-description#595.
-
Alternative Namespaces (www.w3.org/ns/...) w3c/wot-thing-description#652.
-
both class instantiation constraints must apply w3c/wot-thing-description#670.
-
Section 5: assignment function is underspecified w3c/wot-thing-description#669.
-
Improve definitions of type and assignment functions w3c/wot-thing-description#668.
-
Checklist for collected issues w3c/wot-thing-description#671.
-
Section 4 needs better clearification about the context file usage w3c/wot-thing-description#676.
-
Update at-risk and minimize spurious highlighting w3c/wot-thing-description#597.
-
Clarify on the timezone of DateTime serialization in TD w3c/wot-thing-description#586.
-
@context for TD trailing '/' ? w3c/wot-thing-description#673.
-
Section 5: The instance relationship for simple types is unclear w3c/wot-thing-description#667.
-
Semantically equivalence and semantic validity of TD‘s is undefined w3c/wot-thing-description#666.
-
5.4.7 CertSecurityScheme - Pre-shared key identity w3c/wot-thing-description#553.
-
Modify list of formats in token SecurityScheme to allow for extensions w3c/wot-thing-description#618.
-
JSON-LD context file w3c/wot-thing-description#665.
-
Change description for 'observable' to reflect its purpose w3c/wot-thing-description#521.
-
Usage of "endpoint" throughout document w3c/wot-thing-description#554.
-
Make security scheme identifiers more visible w3c/wot-thing-description#613.
-
Default value of "contentType" in "response" w3c/wot-thing-description#611.
-
Define form context w3c/wot-thing-description#555.
-
Inconsistency on accepted values for @context w3c/wot-thing-description#628.
-
Use JSON-Schema Draft07 in JSON Schemas w3c/wot-thing-description#549.
-
Namespace clarifications by Ralph w3c/wot-thing-description#654.
-
Update references to external ontologies (OM, SAREF) w3c/wot-thing-description#576.
-
Inconsistency in the first paragraphs of section w3c/wot-thing-description#564.
-
(editorial) content type examples may be misleading w3c/wot-thing-description#636.
-
Example 2 title could be improved w3c/wot-thing-description#599.
-
Add text direction definition w3c/wot-thing-description#598.
-
change the order of the terms in the Form class table w3c/wot-thing-description#621.
-
Property names should be singular w3c/wot-thing-description#297.
-
Clarify how new security schemes can be given in extensions w3c/wot-thing-description#501.
-
Make value of "support" an anyURI w3c/wot-thing-description#633.
-
Alignment with SOSA/SSN (and iot.schema.org) w3c/wot-thing-description#259.
-
On Links, RFC 8288, and the RDF representation of Links w3c/wot-thing-description#262.
-
Identifiers for Properties, Actions, Events w3c/wot-thing-description#292.
-
Vocabulary term "data" in TD context is missing w3c/wot-thing-description#429.
-
Vocabulary term "subprotocol" in TD context is missing w3c/wot-thing-description#430.
-
Vocabulary term "securityDefinitions" in TD context is missing w3c/wot-thing-description#431.
-
`ThingDescription` term shall be defined in the @context and be the @type of TDs? w3c/wot-thing-description#627.
-
Serialization assertions in Section 5 w3c/wot-thing-description#615.
-
names in Thing level should be MultiLanguage and not mandatory w3c/wot-thing-description#464.
-
Tables in Section 5 should use proper Type terms w3c/wot-thing-description#631.
-
[Editorial] Example hrefs are inconsistent w3c/wot-thing-description#547.
-
Event examples are not enough w3c/wot-thing-description#351.
-
Rename created --> createdAt. lastModified --> modifiedAt w3c/wot-thing-description#546.
-
Model has no formal ground w3c/wot-thing-description#393.
-
Semantics of Forms.op "writeallproperties" is unclear w3c/wot-thing-description#568.
-
Reading and writing Properties are not consistent w3c/wot-thing-description#563.
-
In JSON Schemas put definitions at the beginning w3c/wot-thing-description#550.
-
Usage of the term Vocabulary Term w3c/wot-thing-description#608.
-
Typo throughout the draft w3c/wot-thing-description#602.
-
Top level versus root versus thing resource w3c/wot-thing-description#535.
-
@context below document level for parts of TD w3c/wot-thing-description#587.
-
[Editorial] Links to serialization examples from the vocabulary w3c/wot-thing-description#384.
-
[Editorial] Grouping of mandatory terms w3c/wot-thing-description#407.
-
JSON-LD Best Practice - Version JSON-LD Context files w3c/wot-thing-description#442.
-
Incomplete change to Affordances w3c/wot-thing-description#607.
-
Update 2. Terminology w3c/wot-thing-description#605.
-
Remove Direct Reference to wot-security-best-practices w3c/wot-thing-description#596.
-
Misleading assertions for security w3c/wot-thing-description#612.
-
Fix urn:dev: in examples w3c/wot-thing-description#552.
-
contentEncoding form field w3c/wot-thing-description#557.
-
JSON name vs member and other corrections w3c/wot-thing-description#609.
-
Annex B : ThingTemplate : Is it normative? w3c/wot-thing-description#600.
-
Selection of the op types should extendable w3c/wot-thing-description#556.
-
td:scope is used but does not defined w3c/wot-thing-description#296.
-
range of jsonschema:minimum and jsonschema:maximum w3c/wot-thing-description#295.
-
Semantic Annotation in the Thing Description w3c/wot-thing-description#263.
-
Proper IANA Considerations section w3c/wot-thing-description#588.
-
Typo - htv / http in Example 2 w3c/wot-thing-description#577.
-
"format" in DataSchema needs an example w3c/wot-thing-description#478.
-
i18n check item: TD spec describes a format or data that is likely to need localization w3c/wot-thing-description#583.
-
-
6 issues reopened.
-
Allow "security" to include both SecurityScheme objects and declared identifiers w3c/wot-thing-description#300, by @mmccool.
-
id field in TD Templates w3c/wot-thing-description#593, by @mlagally.
-
change the order of the terms in the Form class table w3c/wot-thing-description#621, by @sebastiankb.
-
names in Thing level should be MultiLanguage and not mandatory w3c/wot-thing-description#464, by @mmccool.
-
Change description for 'observable' to reflect its purpose w3c/wot-thing-description#521, by @mkovatsc.
-
Identifiers for Properties, Actions, Events w3c/wot-thing-description#292, by @zolkis.
-
-
107 issues received 430 new comments.
-
Human-readable "name" has i18n problem - rely on "title"/"titles" in Thing instead? w3c/wot-thing-description#630 (19 comments by @egekorkan, @mkovatsc, @mmccool, @sebastiankb, @takuki)
-
Modify list of formats in token SecurityScheme to allow for extensions w3c/wot-thing-description#618 (19 comments by @jmcanterafonseca, @mkovatsc, @mmccool, @vcharpenay)
-
No mechanism to indicate what the "default language" of a description is [I18N] w3c/wot-thing-description#635 (13 comments by @aphillips, @mkovatsc, @mmccool)
-
i18n checklist for Handling base direction for strings w3c/wot-thing-description#585 (12 comments by @mkovatsc, @mmccool, @r12a)
-
Clarify on the timezone of DateTime serialization in TD w3c/wot-thing-description#586 (12 comments by @jmcanterafonseca, @mkovatsc, @sebastiankb, @vcharpenay)
-
Clarify about language negotiation [I18N] w3c/wot-thing-description#638 (11 comments by @aphillips, @mkovatsc, @mmccool)
-
Acknowledge all contributors w3c/wot-thing-description#649 (10 comments by @jmcanterafonseca, @mkovatsc, @mlagally, @mmccool, @sebastiankb, @takuki, @zolkis)
-
id field in TD Templates w3c/wot-thing-description#593 (10 comments by @egekorkan, @mkovatsc, @mlagally, @sebastiankb, @takuki)
-
Make value of "support" an anyURI w3c/wot-thing-description#633 (10 comments by @egekorkan, @mkovatsc, @mmccool, @sebastiankb)
-
Identifiers for Properties, Actions, Events w3c/wot-thing-description#292 (8 comments by @mmccool, @vcharpenay, @zolkis)
-
Serialization assertions in Section 5 w3c/wot-thing-description#615 (8 comments by @mkovatsc, @mmccool)
-
Inconsistency on accepted values for @context w3c/wot-thing-description#628 (8 comments by @egekorkan, @mkovatsc, @sebastiankb)
-
Alternative Namespaces (www.w3.org/ns/...) w3c/wot-thing-description#652 (7 comments by @ashimura, @mkovatsc, @sebastiankb)
-
dateTime reference when mapping to JSON types [I18N] w3c/wot-thing-description#641 (7 comments by @aphillips, @mkovatsc, @mmccool, @vcharpenay)
-
Improve definitions of type and assignment functions w3c/wot-thing-description#668 (7 comments by @mkovatsc, @vcharpenay)
-
Inconsistency in the first paragraphs of section w3c/wot-thing-description#564 (7 comments by @egekorkan, @mkovatsc, @sebastiankb, @vcharpenay)
-
Example 2 title could be improved w3c/wot-thing-description#599 (7 comments by @jmcanterafonseca, @mkovatsc, @sebastiankb)
-
Namespace IRIs need to be populated on w3.org Web server w3c/wot-thing-description#432 (6 comments by @ashimura, @mkovatsc, @vcharpenay)
-
Make a request for TD media type registration at IANA w3c/wot-thing-description#560 (6 comments by @ektrah, @mkovatsc)
-
Section 5: The instance relationship for simple types is unclear w3c/wot-thing-description#667 (6 comments by @mkovatsc, @vcharpenay)
-
Change description for 'observable' to reflect its purpose w3c/wot-thing-description#521 (6 comments by @mkovatsc, @sebastiankb, @zolkis)
-
Default value of "contentType" in "response" w3c/wot-thing-description#611 (6 comments by @mkovatsc, @sebastiankb)
-
clarify permitted language tags for titles/descriptions [I18N] w3c/wot-thing-description#642 (6 comments by @aphillips, @mkovatsc, @mmccool)
-
`ThingDescription` term shall be defined in the @context and be the @type of TDs? w3c/wot-thing-description#627 (6 comments by @jmcanterafonseca, @mkovatsc, @vcharpenay)
-
Differnt colors for <code> markup w3c/wot-thing-description#349 (5 comments by @mkovatsc, @mmccool, @takuki)
-
Section 5: assignment function is underspecified w3c/wot-thing-description#669 (5 comments by @mkovatsc, @mlagally, @vcharpenay)
-
5.4.7 CertSecurityScheme - Pre-shared key identity w3c/wot-thing-description#553 (5 comments by @mkovatsc, @mmccool)
-
Multilanguage section clarity [I18N] w3c/wot-thing-description#637 (5 comments by @mkovatsc, @mmccool, @takuki)
-
Make security scheme identifiers more visible w3c/wot-thing-description#613 (5 comments by @egekorkan, @mmccool, @vcharpenay)
-
names in Thing level should be MultiLanguage and not mandatory w3c/wot-thing-description#464 (5 comments by @egekorkan, @mkovatsc, @mmccool)
-
[Editorial] Example hrefs are inconsistent w3c/wot-thing-description#547 (5 comments by @egekorkan, @mkovatsc, @sebastiankb)
-
Rename created --> createdAt. lastModified --> modifiedAt w3c/wot-thing-description#546 (5 comments by @jmcanterafonseca, @mlagally, @sebastiankb)
-
Misleading assertions for security w3c/wot-thing-description#612 (5 comments by @mkovatsc, @mmccool)
-
base direction considerations [I18N] w3c/wot-thing-description#643 (4 comments by @mkovatsc, @mmccool, @takuki)
-
Allow array for response in From class? w3c/wot-thing-description#617 (4 comments by @mkovatsc, @sebastiankb)
-
Use JSON-Schema Draft07 in JSON Schemas w3c/wot-thing-description#549 (4 comments by @egekorkan, @sebastiankb, @vcharpenay)
-
Thing Description Serialization and BOM [I18N] w3c/wot-thing-description#640 (4 comments by @mkovatsc, @mmccool)
-
DataSchema format field and patterns [I18N] w3c/wot-thing-description#639 (4 comments by @mkovatsc, @mmccool, @takuki)
-
[Editorial] inline JSON is formatted like normal text w3c/wot-thing-description#468 (4 comments by @egekorkan, @mkovatsc, @sebastiankb)
-
Allow "security" to include both SecurityScheme objects and declared identifiers w3c/wot-thing-description#300 (4 comments by @mkovatsc, @mmccool)
-
Usage of the term Vocabulary Term w3c/wot-thing-description#608 (4 comments by @mkovatsc, @vcharpenay)
-
@context below document level for parts of TD w3c/wot-thing-description#587 (4 comments by @mkovatsc, @sebastiankb, @takuki)
-
Incomplete change to Affordances w3c/wot-thing-description#607 (4 comments by @mkovatsc, @vcharpenay)
-
Figure 1: Ensure Subclass relation between PropertyAffordance and DataSchema is visible w3c/wot-thing-description#678 (3 comments by @mkovatsc, @mmccool, @vcharpenay)
-
i18n checklist for declaring language at the resource level w3c/wot-thing-description#584 (3 comments by @mkovatsc, @mmccool)
-
i18n checklist for Working with time w3c/wot-thing-description#578 (3 comments by @mkovatsc, @mmccool)
-
Need a $id for the JSON Schema w3c/wot-thing-description#674 (3 comments by @mkovatsc, @sebastiankb, @vcharpenay)
-
Update references to external ontologies (OM, SAREF) w3c/wot-thing-description#576 (3 comments by @vcharpenay)
-
Tables in Section 5 should use proper Type terms w3c/wot-thing-description#631 (3 comments by @mkovatsc, @sebastiankb)
-
Reading and writing Properties are not consistent w3c/wot-thing-description#563 (3 comments by @egekorkan, @sebastiankb)
-
In JSON Schemas put definitions at the beginning w3c/wot-thing-description#550 (3 comments by @egekorkan, @jmcanterafonseca)
-
[Testing] Wrong default value in assertion descriptions of td-default-X w3c/wot-thing-description#702 (2 comments by @mmccool)
-
Leftover change - "name" to "title" w3c/wot-thing-description#696 (2 comments by @danielpeintner, @mmccool)
-
JSON Schema/Hyper-Schema compatibility goals? w3c/wot-thing-description#115 (2 comments by @mkovatsc)
-
Make Section 6. Thing Description Serialization normative w3c/wot-thing-description#606 (2 comments by @mkovatsc)
-
i18n checklist for Working with personal names w3c/wot-thing-description#580 (2 comments by @mkovatsc, @mmccool)
-
both class instantiation constraints must apply w3c/wot-thing-description#670 (2 comments by @vcharpenay)
-
Update at-risk and minimize spurious highlighting w3c/wot-thing-description#597 (2 comments by @mmccool, @sebastiankb)
-
Semantically equivalence and semantic validity of TD‘s is undefined w3c/wot-thing-description#666 (2 comments by @vcharpenay)
-
Usage of "endpoint" throughout document w3c/wot-thing-description#554 (2 comments by @mkovatsc, @sebastiankb)
-
(editorial) content type examples may be misleading w3c/wot-thing-description#636 (2 comments by @mkovatsc, @vcharpenay)
-
change the order of the terms in the Form class table w3c/wot-thing-description#621 (2 comments by @sebastiankb, @vcharpenay)
-
Clarify how new security schemes can be given in extensions w3c/wot-thing-description#501 (2 comments by @sebastiankb, @vcharpenay)
-
i18n check item: TD spec describes a format or data that is likely to need localization w3c/wot-thing-description#583 (2 comments by @mmccool)
-
Describe automated testing in TD Implementation Report w3c/wot-thing-description#710 (1 comment by @mmccool)
-
[Testing] td-default-idempotent is used for writeOnly w3c/wot-thing-description#701 (1 comment by @mmccool)
-
[Testing] td-data-schema-objects_items is still present w3c/wot-thing-description#703 (1 comment by @mmccool)
-
[Testing] td-data-schema-objects_properties should be removed w3c/wot-thing-description#704 (1 comment by @mmccool)
-
i18n checklist for "Defining language values" w3c/wot-thing-description#595 (1 comment by @mkovatsc)
-
JSON Schema security scheme could be moved to a separate file and referenced from the main schema w3c/wot-thing-description#551 (1 comment by @sebastiankb)
-
Alignment with SOSA/SSN (and iot.schema.org) w3c/wot-thing-description#259 (1 comment by @vcharpenay)
-
On Links, RFC 8288, and the RDF representation of Links w3c/wot-thing-description#262 (1 comment by @vcharpenay)
-
Top level versus root versus thing resource w3c/wot-thing-description#535 (1 comment by @sebastiankb)
-
Semantics of Forms.op "writeallproperties" is unclear w3c/wot-thing-description#568 (1 comment by @sebastiankb)
-
JSON-LD Best Practice - Version JSON-LD Context files w3c/wot-thing-description#442 (1 comment by @mkovatsc)
-
[Editorial] Links to serialization examples from the vocabulary w3c/wot-thing-description#384 (1 comment by @mkovatsc)
-
Remove Direct Reference to wot-security-best-practices w3c/wot-thing-description#596 (1 comment by @mmccool)
-
Selection of the op types should extendable w3c/wot-thing-description#556 (1 comment by @sebastiankb)
-
Consider to cross reference JSON Schema definitions (external or internal) w3c/wot-thing-description#604 (1 comment by @egekorkan)
-
range of jsonschema:minimum and jsonschema:maximum w3c/wot-thing-description#295 (1 comment by @vcharpenay)
-
Semantic Annotation in the Thing Description w3c/wot-thing-description#263 (1 comment by @vcharpenay)
-
-
61 pull requests opened.
-
reflected feedback from CR except rfc2119-assertion w3c/wot-thing-description#716, by @ashimura.
-
WIP: Updated test results 5.22 (using "fixed" TDs) w3c/wot-thing-description#709, by @mmccool.
-
Update Test results post-CR (using only TDs provided by implementers) w3c/wot-thing-description#707, by @mmccool.
-
update extra assertions w3c/wot-thing-description#705, by @egekorkan.
-
Fixed first/last name order in the acknowledgement section. w3c/wot-thing-description#697, by @takuki.
-
Fixed tense in SOTD in marking sections with "This section is at risk" w3c/wot-thing-description#695, by @takuki.
-
Fixed tense in SOTD in marking sections with "This section is at risk" w3c/wot-thing-description#694, by @takuki.
-
Merged recent master branch changes into editorials-for-ralph-comments branch w3c/wot-thing-description#693, by @takuki.
-
Editorials for Ralph's comments w3c/wot-thing-description#692, by @mmccool.
-
Edited UML diagrams in Section 5.1 Overview (bis) w3c/wot-thing-description#691, by @vcharpenay.
-
Annotate at-risk features with searchable text w3c/wot-thing-description#690, by @mmccool.
-
Incorporated Ralph's editorial comments. w3c/wot-thing-description#689, by @takuki.
-
Refactored RDF examples for simplicity w3c/wot-thing-description#688, by @vcharpenay.
-
Edited UML diagrams in Section 5.1 Overview w3c/wot-thing-description#687, by @vcharpenay.
-
fix changes3 link w3c/wot-thing-description#685, by @mmccool.
-
Remove section 4.2 referring to obsolete ns namespaces w3c/wot-thing-description#684, by @mmccool.
-
Update base text direction and date-time rules w3c/wot-thing-description#683, by @mmccool.
-
Updated JSON-LD wording in namespace section w3c/wot-thing-description#682, by @vcharpenay.
-
resolved comments from review from PR #677 w3c/wot-thing-description#681, by @sebastiankb.
-
Post-Review Changes of 5.2 Preliminaries w3c/wot-thing-description#680, by @vcharpenay.
-
address all items in #671 w3c/wot-thing-description#677, by @sebastiankb.
-
Mark defaults associated with at-risk features as at-risk w3c/wot-thing-description#675, by @mmccool.
-
Timezone of DateTime serialization in TD w3c/wot-thing-description#672, by @vcharpenay.
-
op fixes again w3c/wot-thing-description#664, by @sebastiankb.
-
Update op values definitions for Affordances w3c/wot-thing-description#663, by @sebastiankb.
-
Added a few names in Acknowledgement based on GitHub contribution. w3c/wot-thing-description#662, by @takuki.
-
merging master into takuki-issue-649 w3c/wot-thing-description#661, by @takuki.
-
Updated Acknowledgements section (for issue #649) w3c/wot-thing-description#660, by @takuki.
-
Address default values for response content types w3c/wot-thing-description#659, by @sebastiankb.
-
Update Link and Form w3c/wot-thing-description#658, by @egekorkan.
-
Fixed some typos and a translation error w3c/wot-thing-description#657, by @takuki.
-
WIP: Implementation of Decisions on Namespace w3c/wot-thing-description#656, by @vcharpenay.
-
Fix various SecurityScheme problems (Issues 618, 553) w3c/wot-thing-description#655, by @mmccool.
-
Update validation schema w3c/wot-thing-description#653, by @egekorkan.
-
Limit at-risk items to those necessary for CR transition w3c/wot-thing-description#651, by @mmccool.
-
Added health warning and reference to string-meta (for issue #643) w3c/wot-thing-description#650, by @takuki.
-
"titles" in Thing class is optional (for issue #630) w3c/wot-thing-description#648, by @takuki.
-
Clarified DataSchema format field (for issue #639) w3c/wot-thing-description#647, by @takuki.
-
Align structure, fix #599, and address i18n comments w3c/wot-thing-description#646, by @mkovatsc.
-
Fixed the description of "title" and "titles" in td.ttl w3c/wot-thing-description#645, by @takuki.
-
Address issue #630 (remove name from Thing level, add title + titles, support is typed to anyURI) w3c/wot-thing-description#644, by @sebastiankb.
-
WIP Fixes for #564 w3c/wot-thing-description#634, by @egekorkan.
-
Update validation schema w3c/wot-thing-description#632, by @egekorkan.
-
Default value table + reponse term handling in Forms w3c/wot-thing-description#629, by @sebastiankb.
-
WIP: Major editorial pass w3c/wot-thing-description#626, by @mkovatsc.
-
Improve subscription example w3c/wot-thing-description#625, by @mkovatsc.
-
fix #621 and #554 w3c/wot-thing-description#624, by @sebastiankb.
-
Update terminology and references w3c/wot-thing-description#623, by @mkovatsc.
-
rename lastModified --> modified w3c/wot-thing-description#622, by @sebastiankb.
-
Add assertions for language objects and text direction (issue 598) w3c/wot-thing-description#620, by @mmccool.
-
Remove reference to wot-security-best-practices w3c/wot-thing-description#619, by @mmccool.
-
WIP: Updates (mainly) in Section 5 w3c/wot-thing-description#616, by @sebastiankb.
-
WIP: small rearrangements and changes in Annex chapter w3c/wot-thing-description#614, by @sebastiankb.
-
Revision of Section 6 w3c/wot-thing-description#610, by @mkovatsc.
-
Fix JSON Schema to match latest TD Spec version w3c/wot-thing-description#603, by @jmcanterafonseca.
-
Fix #599 w3c/wot-thing-description#601, by @jmcanterafonseca.
-
Add IANA section w3c/wot-thing-description#594, by @mkovatsc.
-
fixed id fields of TD examples w3c/wot-thing-description#592, by @egekorkan.
-
Added support for @language in @context w3c/wot-thing-description#591, by @takuki.
-
WIP: namespace update w3c/wot-thing-description#590, by @vcharpenay.
-
Redefine identity more generically in security schemes w3c/wot-thing-description#589, by @mmccool.
-
-
52 pull requests merged.
-
update extra assertions w3c/wot-thing-description#705.
-
Fixed first/last name order in the acknowledgement section. w3c/wot-thing-description#697.
-
Fixed tense in SOTD in marking sections with "This section is at risk" w3c/wot-thing-description#695.
-
Fixed tense in SOTD in marking sections with "This section is at risk" w3c/wot-thing-description#694.
-
Merged recent master branch changes into editorials-for-ralph-comments branch w3c/wot-thing-description#693.
-
Edited UML diagrams in Section 5.1 Overview (bis) w3c/wot-thing-description#691.
-
Editorials for Ralph's comments w3c/wot-thing-description#692.
-
Annotate at-risk features with searchable text w3c/wot-thing-description#690.
-
Incorporated Ralph's editorial comments. w3c/wot-thing-description#689.
-
fix changes3 link w3c/wot-thing-description#685.
-
Remove section 4.2 referring to obsolete ns namespaces w3c/wot-thing-description#684.
-
Update base text direction and date-time rules w3c/wot-thing-description#683.
-
Post-Review Changes of 5.2 Preliminaries w3c/wot-thing-description#680.
-
Updated JSON-LD wording in namespace section w3c/wot-thing-description#682.
-
resolved comments from review from PR #677 w3c/wot-thing-description#681.
-
address all items in #671 w3c/wot-thing-description#677.
-
Mark defaults associated with at-risk features as at-risk w3c/wot-thing-description#675.
-
Timezone of DateTime serialization in TD w3c/wot-thing-description#672.
-
Fix various SecurityScheme problems (Issues 618, 553) w3c/wot-thing-description#655.
-
op fixes again w3c/wot-thing-description#664.
-
Update op values definitions for Affordances w3c/wot-thing-description#663.
-
Address default values for response content types w3c/wot-thing-description#659.
-
Added a few names in Acknowledgement based on GitHub contribution. w3c/wot-thing-description#662.
-
merging master into takuki-issue-649 w3c/wot-thing-description#661.
-
Updated Acknowledgements section (for issue #649) w3c/wot-thing-description#660.
-
WIP: Implementation of Decisions on Namespace w3c/wot-thing-description#656.
-
Fixed some typos and a translation error w3c/wot-thing-description#657.
-
Update validation schema w3c/wot-thing-description#653.
-
Update validation schema w3c/wot-thing-description#632.
-
WIP Fixes for #564 w3c/wot-thing-description#634.
-
Limit at-risk items to those necessary for CR transition w3c/wot-thing-description#651.
-
Align structure, fix #599, and address i18n comments w3c/wot-thing-description#646.
-
Added health warning and reference to string-meta (for issue #643) w3c/wot-thing-description#650.
-
"titles" in Thing class is optional (for issue #630) w3c/wot-thing-description#648.
-
Clarified DataSchema format field (for issue #639) w3c/wot-thing-description#647.
-
Fixed the description of "title" and "titles" in td.ttl w3c/wot-thing-description#645.
-
Address issue #630 (remove name from Thing level, add title + titles, support is typed to anyURI) w3c/wot-thing-description#644.
-
Add assertions for language objects and text direction (issue 598) w3c/wot-thing-description#620.
-
Default value table + reponse term handling in Forms w3c/wot-thing-description#629.
-
WIP: Major editorial pass w3c/wot-thing-description#626.
-
Improve subscription example w3c/wot-thing-description#625.
-
Update terminology and references w3c/wot-thing-description#623.
-
fix #621 and #554 w3c/wot-thing-description#624.
-
rename lastModified --> modified w3c/wot-thing-description#622.
-
Remove reference to wot-security-best-practices w3c/wot-thing-description#619.
-
Revision of Section 6 w3c/wot-thing-description#610.
-
WIP: small rearrangements and changes in Annex chapter w3c/wot-thing-description#614.
-
WIP: namespace update w3c/wot-thing-description#590.
-
Redefine identity more generically in security schemes w3c/wot-thing-description#589.
-
Add IANA section w3c/wot-thing-description#594.
-
fixed id fields of TD examples w3c/wot-thing-description#592.
-
Added support for @language in @context w3c/wot-thing-description#591.
-
-
6 pull requests closed.
-
WIP: Updated test results 5.22 (using "fixed" TDs) w3c/wot-thing-description#709.
-
Edited UML diagrams in Section 5.1 Overview w3c/wot-thing-description#687.
-
Update Link and Form w3c/wot-thing-description#658.
-
Fix JSON Schema to match latest TD Spec version w3c/wot-thing-description#603.
-
Fix #599 w3c/wot-thing-description#601.
-
WIP: Updates (mainly) in Section 5 w3c/wot-thing-description#616.
-
-
29 pull requests received 293 new comments.
-
Add assertions for language objects and text direction (issue 598) w3c/wot-thing-description#620 (105 comments by @mkovatsc, @mmccool)
-
Align structure, fix #599, and address i18n comments w3c/wot-thing-description#646 (38 comments by @mkovatsc, @mlagally, @mmccool, @sebastiankb)
-
Refactored RDF examples for simplicity w3c/wot-thing-description#688 (18 comments by @mlagally, @vcharpenay)
-
Fix various SecurityScheme problems (Issues 618, 553) w3c/wot-thing-description#655 (17 comments by @mkovatsc, @mmccool)
-
Address default values for response content types w3c/wot-thing-description#659 (12 comments by @egekorkan, @mkovatsc)
-
Update validation schema w3c/wot-thing-description#632 (10 comments by @egekorkan, @jmcanterafonseca, @mkovatsc, @mlagally, @sebastiankb)
-
Update Test results post-CR (using only TDs provided by implementers) w3c/wot-thing-description#707 (9 comments by @egekorkan, @mmccool, @sebastiankb)
-
Default value table + reponse term handling in Forms w3c/wot-thing-description#629 (9 comments by @mkovatsc, @sebastiankb)
-
Fix JSON Schema to match latest TD Spec version w3c/wot-thing-description#603 (8 comments by @ashimura, @egekorkan, @jmcanterafonseca, @mkovatsc, @sebastiankb)
-
Post-Review Changes of 5.2 Preliminaries w3c/wot-thing-description#680 (5 comments by @mmccool, @vcharpenay)
-
Update Link and Form w3c/wot-thing-description#658 (5 comments by @egekorkan, @mkovatsc, @vcharpenay)
-
Annotate at-risk features with searchable text w3c/wot-thing-description#690 (4 comments by @mkovatsc)
-
Edited UML diagrams in Section 5.1 Overview w3c/wot-thing-description#687 (3 comments by @mkovatsc, @sebastiankb, @vcharpenay)
-
WIP: Updated test results 5.22 (using "fixed" TDs) w3c/wot-thing-description#709 (2 comments by @mmccool)
-
Remove reference to wot-security-best-practices w3c/wot-thing-description#619 (2 comments by @mkovatsc, @sebastiankb)
-
WIP: Implementation of Decisions on Namespace w3c/wot-thing-description#656 (1 comment by @sebastiankb)
-
Limit at-risk items to those necessary for CR transition w3c/wot-thing-description#651 (1 comment by @mmccool)
-
w3c/wot-security
-
2 issues opened.
-
Update wot-security to align with Architecture CR vocabulary w3c/wot-security#126, by @mmccool.
-
Align Security and Privacy Considerations section of Architecture CR with wot-security w3c/wot-security#125, by @mmccool.
-
-
5 issues closed.
-
Align with Architecture document w3c/wot-security#13.
-
Add Material for "Industrial/Critical infrastructure environment" scenarios w3c/wot-security#21.
-
Add Material for "Business/Corporate environment" scenarios w3c/wot-security#20.
-
Separate Discovery/Expose w3c/wot-security#14.
-
Support both strings and SecurityScheme objects in "security" fields w3c/wot-security#122.
-
-
10 issues received 12 new comments.
-
Terminology inconsistency - Proxy and Gateway are used interchangeably. w3c/wot-security#123 (1 comment by @mmccool)
-
Align Security and Privacy Considerations section of Architecture CR with wot-security w3c/wot-security#125 (1 comment by @mmccool)
-
Align Security and Privacy Considerations section of Architecture CR with wot-security w3c/wot-security#35 (1 comment by @mmccool)
-
Add Material for "Industrial/Critical infrastructure environment" scenarios w3c/wot-security#21 (1 comment by @mmccool)
-
Add Material for "Business/Corporate environment" scenarios w3c/wot-security#20 (1 comment by @mmccool)
-
Support both strings and SecurityScheme objects in "security" fields w3c/wot-security#122 (1 comment by @mmccool)
-
1 pull request opened.
-
various small fixes around general readability and display w3c/wot-security#127, by @ereshetova.
-
w3c/wot-architecture
-
23 issues opened.
-
ReSpec warning about RFC7049 in non-normative section w3c/wot-architecture#357, by @mkovatsc.
-
Broken internal reference w3c/wot-architecture#356, by @mkovatsc.
-
Update TD reference to PR version of TD spec w3c/wot-architecture#352, by @mlagally.
-
Address TAG and Security review feedback w3c/wot-architecture#351, by @mlagally.
-
Post CR editorial fixes w3c/wot-architecture#350, by @mlagally.
-
TODO Fix Section 7 w3c/wot-architecture#339, by @mkovatsc.
-
Reference CR version of TD spec w3c/wot-architecture#336, by @mlagally.
-
Read through CR-candidate-3 - minor issues w3c/wot-architecture#333, by @danielpeintner.
-
Acknowledge all contributors w3c/wot-architecture#329, by @mlagally.
-
WoT Security and Privacy Considerations vs Guidelines w3c/wot-architecture#323, by @mkovatsc.
-
Editorial Cleanup - search and replace w3c/wot-architecture#322, by @mlagally.
-
Remove "Scripting Runtime" from Terminology section w3c/wot-architecture#320, by @mlagally.
-
Security and Privacy Guidelines not listed as building block in the introduction w3c/wot-architecture#315, by @mkovatsc.
-
Accessibility review of figures w3c/wot-architecture#314, by @mlagally.
-
Improve "Data Schema" illustration in figures w3c/wot-architecture#312, by @mkovatsc.
-
Fix capitalization of Headings in Section 5 w3c/wot-architecture#311, by @mkovatsc.
-
"resolve merge conflict" commit reverted figure updates w3c/wot-architecture#294, by @mkovatsc.
-
Remove Direct Reference to wot-security-best-practices and wot-security-testing-plan w3c/wot-architecture#284, by @mmccool.
-
update section: 8.9.2 Existing Device Described with a Thing Description w3c/wot-architecture#279, by @mlagally.
-
Remove "Scripting Runtime" as a term, use execution environment w3c/wot-architecture#278, by @mlagally.
-
Remove other scripting language environments from the WoT scripting API section w3c/wot-architecture#277, by @mlagally.
-
Add text to section "Existing Device Described with a Thing Description" w3c/wot-architecture#276, by @mlagally.
-
Move definitions from section 10.1 to terminology w3c/wot-architecture#275, by @mlagally.
-
-
40 issues closed.
-
ReSpec warning about RFC7049 in non-normative section w3c/wot-architecture#357.
-
Broken internal reference w3c/wot-architecture#356.
-
Read through CR-candidate-3 - minor issues w3c/wot-architecture#333.
-
Reference CR version of TD spec w3c/wot-architecture#336.
-
Integration Patterns w3c/wot-architecture#9.
-
Editorial Cleanup - search and replace w3c/wot-architecture#322.
-
Improve "Data Schema" illustration in figures w3c/wot-architecture#312.
-
Fix capitalization of Headings in Section 5 w3c/wot-architecture#311.
-
Revise "6.6.1 Hypermedia driven" section w3c/wot-architecture#235.
-
Set up assertion extraction tooling w3c/wot-architecture#234.
-
Support Patterns without Local Proxies w3c/wot-architecture#134.
-
TODO Fix Section 7 w3c/wot-architecture#339.
-
Remove "Scripting Runtime" from Terminology section w3c/wot-architecture#320.
-
Security and Privacy Guidelines not listed as building block in the introduction w3c/wot-architecture#315.
-
Add a definition of Proxy w3c/wot-architecture#182.
-
Legacy adaption w3c/wot-architecture#181.
-
Consistent diagrams w3c/wot-architecture#228.
-
Fix Terminology: NAT -> (NAT-) Proxy w3c/wot-architecture#212.
-
6.5 Hypermedia Controls: Addtional examples of similar standards? w3c/wot-architecture#246.
-
Markup all assertions w3c/wot-architecture#249.
-
Move definitions from section 10.1 to terminology w3c/wot-architecture#275.
-
Add text to section "Existing Device Described with a Thing Description" w3c/wot-architecture#276.
-
Remove "Scripting Runtime" as a term, use execution environment w3c/wot-architecture#278.
-
update section: 8.9.2 Existing Device Described with a Thing Description w3c/wot-architecture#279.
-
Remove Direct Reference to wot-security-best-practices and wot-security-testing-plan w3c/wot-architecture#284.
-
Remove other scripting language environments from the WoT scripting API section w3c/wot-architecture#277.
-
Editorial: Consider rewording the relationship to CoRAL w3c/wot-architecture#236.
-
"resolve merge conflict" commit reverted figure updates w3c/wot-architecture#294.
-
Terminology definition of Application w3c/wot-architecture#260.
-
Align section 10 with improved section 6 from issue 188 w3c/wot-architecture#217.
-
Align section 9 with improved section 6 from issue 188 w3c/wot-architecture#216.
-
Align section 7 with improved section 6 from issue 188 w3c/wot-architecture#214.
-
Section 8.10.2 Existing Device Described with a Thing Description is too restrictive w3c/wot-architecture#209.
-
Clarification of the term "behavior" w3c/wot-architecture#220.
-
Update figure 21 and figure 22 w3c/wot-architecture#232.
-
Align section 8 with improved section 6 from issue 188 w3c/wot-architecture#215.
-
handle i18n questions w3c/wot-architecture#248.
-
"WoT network components" in abstract is not immediately clear w3c/wot-architecture#205.
-
Relationship between academic project and W3C WoT is not clear w3c/wot-architecture#206.
-
"concrete deployment scenarios" are not described w3c/wot-architecture#204.
-
-
1 issue reopened.
-
Read through CR-candidate-3 - minor issues w3c/wot-architecture#333, by @mlagally.
-
-
38 issues received 113 new comments.
-
Remove "Scripting Runtime" as a term, use execution environment w3c/wot-architecture#278 (16 comments by @mkovatsc, @mlagally, @zolkis)
-
Editorial Cleanup - search and replace w3c/wot-architecture#322 (10 comments by @k-toumura, @mkovatsc, @mlagally)
-
Markup all assertions w3c/wot-architecture#249 (10 comments by @k-toumura, @mlagally, @mmccool, @takuki, @zolkis)
-
WoT Security and Privacy Considerations vs Guidelines w3c/wot-architecture#323 (5 comments by @mlagally, @mmccool)
-
Read through CR-candidate-3 - minor issues w3c/wot-architecture#333 (5 comments by @mkovatsc, @mlagally)
-
Accessibility review of figures w3c/wot-architecture#314 (4 comments by @ashimura, @mkovatsc, @mlagally, @mmccool)
-
"resolve merge conflict" commit reverted figure updates w3c/wot-architecture#294 (4 comments by @k-toumura, @mkovatsc, @mlagally)
-
Security and Privacy Guidelines not listed as building block in the introduction w3c/wot-architecture#315 (3 comments by @mkovatsc)
-
Revise "6.6.1 Hypermedia driven" section w3c/wot-architecture#235 (3 comments by @mkovatsc, @mlagally)
-
Move definitions from section 10.1 to terminology w3c/wot-architecture#275 (3 comments by @mlagally, @mmccool)
-
Remove other scripting language environments from the WoT scripting API section w3c/wot-architecture#277 (3 comments by @mkovatsc, @zolkis)
-
Fix capitalization of Headings in Section 5 w3c/wot-architecture#311 (2 comments by @mkovatsc, @mlagally)
-
Remove "Scripting Runtime" from Terminology section w3c/wot-architecture#320 (2 comments by @mkovatsc)
-
6.5 Hypermedia Controls: Addtional examples of similar standards? w3c/wot-architecture#246 (2 comments by @mkovatsc)
-
Align section 10 with improved section 6 from issue 188 w3c/wot-architecture#217 (2 comments by @mkovatsc, @mmccool)
-
Section 8.10.2 Existing Device Described with a Thing Description is too restrictive w3c/wot-architecture#209 (2 comments by @mkovatsc, @mmccool)
-
ReSpec warning about RFC7049 in non-normative section w3c/wot-architecture#357 (1 comment by @mkovatsc)
-
Editorial: Consider rewording the relationship to CoRAL w3c/wot-architecture#236 (1 comment by @mkovatsc)
-
Align section 9 with improved section 6 from issue 188 w3c/wot-architecture#216 (1 comment by @mkovatsc)
-
Align section 7 with improved section 6 from issue 188 w3c/wot-architecture#214 (1 comment by @mkovatsc)
-
Add text to section "Existing Device Described with a Thing Description" w3c/wot-architecture#276 (1 comment by @mmccool)
-
update section: 8.9.2 Existing Device Described with a Thing Description w3c/wot-architecture#279 (1 comment by @mmccool)
-
Remove Direct Reference to wot-security-best-practices and wot-security-testing-plan w3c/wot-architecture#284 (1 comment by @mmccool)
-
-
73 pull requests opened.
-
Update index.html w3c/wot-architecture#355, by @mlagally.
-
Update index.html w3c/wot-architecture#354, by @mlagally.
-
apply feedback from the CR version w3c/wot-architecture#353, by @ashimura.
-
Add change log w3c/wot-architecture#349, by @mmccool.
-
Fix broken reference w3c/wot-architecture#348, by @mkovatsc.
-
approved changes from WoT chairs and architecture editors (9.5.) w3c/wot-architecture#347, by @mlagally.
-
arch-call-on-9-5-[POST-CR-cand3] Align with TD spec terminology and fix 6.7 w3c/wot-architecture#346, by @mlagally.
-
CR changes since CR-candidate-3 - includes PRs 321, 337 and 340 w3c/wot-architecture#345, by @mlagally.
-
implementing editorial changes w3c/wot-architecture#344, by @mlagally.
-
Align with TD terminology and fixes for 6.7 w3c/wot-architecture#343, by @mlagally.
-
Issue 322 search and replace w3c/wot-architecture#342, by @mlagally.
-
Modifying the title of section 9.2 w3c/wot-architecture#341, by @mlagally.
-
Issue 333 minor editorial-arch-call w3c/wot-architecture#340, by @mlagally.
-
[POST-CR-cand3] Align with TD spec terminology and fix 6.7 w3c/wot-architecture#338, by @mkovatsc.
-
Issue 322 search and replace w3c/wot-architecture#337, by @mlagally.
-
Modifying the title of section 9.2 w3c/wot-architecture#335, by @takuki.
-
Cr candidate 3 w3c/wot-architecture#334, by @takuki.
-
Cr candidate 3 w3c/wot-architecture#332, by @mlagally.
-
Issue 329 contributors w3c/wot-architecture#331, by @mlagally.
-
Issue 329 contributors w3c/wot-architecture#330, by @mlagally.
-
Issue 134 device registers itself pattern w3c/wot-architecture#328, by @mlagally.
-
Editorial chapter 9 w3c/wot-architecture#327, by @mlagally.
-
Diagram dataschemas w3c/wot-architecture#326, by @mlagally.
-
sync with master w3c/wot-architecture#325, by @mlagally.
-
Editorial chapter 8 w3c/wot-architecture#324, by @mlagally.
-
Editorial Chapter 9 w3c/wot-architecture#321, by @mlagally.
-
Issue 134 device registers itself pattern w3c/wot-architecture#319, by @mlagally.
-
Issue 311 capitalisation of headings w3c/wot-architecture#318, by @mlagally.
-
Improve Data Schema illustration w3c/wot-architecture#317, by @k-toumura.
-
Improve abstract and introduction w3c/wot-architecture#316, by @mkovatsc.
-
Cr candidate 2 w3c/wot-architecture#313, by @mlagally.
-
minor edit w3c/wot-architecture#310, by @mlagally.
-
WIP: Editorial chapter 10 w3c/wot-architecture#309, by @mlagally.
-
WIP: Editorial chapter 9 w3c/wot-architecture#308, by @mlagally.
-
Diagram rearrange w3c/wot-architecture#307, by @mlagally.
-
Editorial chapter 7 w3c/wot-architecture#306, by @mlagally.
-
Editorial chapter 6 w3c/wot-architecture#305, by @mlagally.
-
Diagram rearrange w3c/wot-architecture#304, by @mlagally.
-
Mkovatsc patch scripting runtime w3c/wot-architecture#303, by @mlagally.
-
Editorial chapter 8 w3c/wot-architecture#302, by @mlagally.
-
Editorial chapter 7 w3c/wot-architecture#301, by @mlagally.
-
Editorial chapter 6 w3c/wot-architecture#300, by @mlagally.
-
WIP: Duplicate of Fix #236 and #246 w3c/wot-architecture#299, by @mkovatsc.
-
Hypermedia Controls examples (Fix #236 and #246) w3c/wot-architecture#298, by @mkovatsc.
-
Fix figures - restore 3 PNGs that were overwritten by a merge w3c/wot-architecture#297, by @mlagally.
-
Diagram rearrange w3c/wot-architecture#296, by @k-toumura.
-
[Editorial] Patch for issue 212 - NAT device w3c/wot-architecture#295, by @mlagally.
-
Revise usage of term proxy w3c/wot-architecture#293, by @mkovatsc.
-
Remove Application definition from Terminology w3c/wot-architecture#292, by @mkovatsc.
-
Fix #277 and #278 w3c/wot-architecture#291, by @mkovatsc.
-
Move security definitions to terminology (issue 275) w3c/wot-architecture#290, by @mmccool.
-
Update discussion of support for existing devices (issues 279 and 276) w3c/wot-architecture#289, by @mmccool.
-
Remove direct refs to sec best practices and testing docs w3c/wot-architecture#288, by @mmccool.
-
Mark up all assertions w3c/wot-architecture#287, by @mmccool.
-
Restoring wot-architecture-figures-new2 w3c/wot-architecture#286, by @mmccool.
-
Mark up all assertions w3c/wot-architecture#285, by @mmccool.
-
Added references to pioneering WoT works. w3c/wot-architecture#283, by @takuki.
-
Added references to pioneering WoT works. w3c/wot-architecture#282, by @takuki.
-
Updated taki-issue-206 branch with the latest in master w3c/wot-architecture#281, by @takuki.
-
Cr candidate 1 w3c/wot-architecture#280, by @mlagally.
-
clarify how existing devices can be used w3c/wot-architecture#274, by @mlagally.
-
Clarify use of existing devices (Issue #209) w3c/wot-architecture#273, by @mmccool.
-
Update section 10 w3c/wot-architecture#272, by @mlagally.
-
Update Section 10 (Issue #217) w3c/wot-architecture#271, by @mmccool.
-
Taki issue 206 w3c/wot-architecture#270, by @mlagally.
-
Mkovatsc patch figures 1 w3c/wot-architecture#269, by @mlagally.
-
Align section 7 w3c/wot-architecture#267, by @mlagally.
-
Taki issue 216 w3c/wot-architecture#266, by @mlagally.
-
Mkovatsc patch section 8 w3c/wot-architecture#265, by @mlagally.
-
Issue 212: Fix Terminology: NAT -> (NAT-) Proxy w3c/wot-architecture#264, by @mlagally.
-
Aligned section 9 with improved section 6 (for issue #216) w3c/wot-architecture#263, by @takuki.
-
Aligned section 9 with improved section 6 (for issue #216) w3c/wot-architecture#262, by @takuki.
-
-
54 pull requests merged.
-
Update index.html w3c/wot-architecture#354.
-
apply feedback from the CR version w3c/wot-architecture#353.
-
Add change log w3c/wot-architecture#349.
-
Fix broken reference w3c/wot-architecture#348.
-
approved changes from WoT chairs and architecture editors (9.5.) w3c/wot-architecture#347.
-
arch-call-on-9-5-[POST-CR-cand3] Align with TD spec terminology and fix 6.7 w3c/wot-architecture#346.
-
CR changes since CR-candidate-3 - includes PRs 321, 337 and 340 w3c/wot-architecture#345.
-
Modifying the title of section 9.2 w3c/wot-architecture#335.
-
Cr candidate 3 w3c/wot-architecture#332.
-
implementing editorial changes w3c/wot-architecture#344.
-
Issue 322 search and replace w3c/wot-architecture#342.
-
Modifying the title of section 9.2 w3c/wot-architecture#341.
-
Cr candidate 3 w3c/wot-architecture#334.
-
Issue 329 contributors w3c/wot-architecture#331.
-
Issue 134 device registers itself pattern w3c/wot-architecture#328.
-
Editorial chapter 9 w3c/wot-architecture#327.
-
Editorial chapter 8 w3c/wot-architecture#324.
-
Diagram dataschemas w3c/wot-architecture#326.
-
sync with master w3c/wot-architecture#325.
-
Improve abstract and introduction w3c/wot-architecture#316.
-
WIP: Editorial chapter 9 w3c/wot-architecture#308.
-
WIP: Editorial chapter 10 w3c/wot-architecture#309.
-
Cr candidate 2 w3c/wot-architecture#313.
-
minor edit w3c/wot-architecture#310.
-
Diagram rearrange w3c/wot-architecture#307.
-
Editorial chapter 7 w3c/wot-architecture#306.
-
Editorial chapter 6 w3c/wot-architecture#305.
-
Diagram rearrange w3c/wot-architecture#304.
-
Mkovatsc patch scripting runtime w3c/wot-architecture#303.
-
Remove direct refs to sec best practices and testing docs w3c/wot-architecture#288.
-
Revise usage of term proxy w3c/wot-architecture#293.
-
Hypermedia Controls examples (Fix #236 and #246) w3c/wot-architecture#298.
-
[Editorial] Patch for issue 212 - NAT device w3c/wot-architecture#295.
-
Update discussion of support for existing devices (issues 279 and 276) w3c/wot-architecture#289.
-
Fix figures - restore 3 PNGs that were overwritten by a merge w3c/wot-architecture#297.
-
Remove Application definition from Terminology w3c/wot-architecture#292.
-
Move security definitions to terminology (issue 275) w3c/wot-architecture#290.
-
Mark up all assertions w3c/wot-architecture#287.
-
Restoring wot-architecture-figures-new2 w3c/wot-architecture#286.
-
Added references to pioneering WoT works. w3c/wot-architecture#283.
-
Added references to pioneering WoT works. w3c/wot-architecture#282.
-
Updated taki-issue-206 branch with the latest in master w3c/wot-architecture#281.
-
Aligned section 9 with improved section 6 (for issue #216) w3c/wot-architecture#263.
-
Moved the historical information to the acknowledgement (Issue #206) w3c/wot-architecture#258.
-
Cr candidate 1 w3c/wot-architecture#280.
-
clarify how existing devices can be used w3c/wot-architecture#274.
-
Update section 10 w3c/wot-architecture#272.
-
Taki issue 206 w3c/wot-architecture#270.
-
Mkovatsc patch figures 1 w3c/wot-architecture#269.
-
Issue 212 w3c/wot-architecture#268.
-
Align section 7 w3c/wot-architecture#267.
-
Taki issue 216 w3c/wot-architecture#266.
-
Mkovatsc patch section 8 w3c/wot-architecture#265.
-
Aligned section 9 with improved section 6 (for issue #216) w3c/wot-architecture#262.
-
-
23 pull requests closed.
-
[POST-CR-cand3] Align with TD spec terminology and fix 6.7 w3c/wot-architecture#338.
-
Issue 333 minor editorial-arch-call w3c/wot-architecture#340.
-
Issue 322 search and replace w3c/wot-architecture#337.
-
Editorial Chapter 9 w3c/wot-architecture#321.
-
Align with TD terminology and fixes for 6.7 w3c/wot-architecture#343.
-
Issue 329 contributors w3c/wot-architecture#330.
-
Issue 134 device registers itself pattern w3c/wot-architecture#319.
-
Issue 311 capitalisation of headings w3c/wot-architecture#318.
-
Improve Data Schema illustration w3c/wot-architecture#317.
-
Editorial chapter 8 w3c/wot-architecture#302.
-
Editorial chapter 7 w3c/wot-architecture#301.
-
Diagram rearrange w3c/wot-architecture#296.
-
Fix #277 and #278 w3c/wot-architecture#291.
-
Editorial chapter 6 w3c/wot-architecture#300.
-
WIP: Duplicate of Fix #236 and #246 w3c/wot-architecture#299.
-
Mark up all assertions w3c/wot-architecture#285.
-
Clarify use of existing devices (Issue #209) w3c/wot-architecture#273.
-
Update Section 10 (Issue #217) w3c/wot-architecture#271.
-
Issue 212: Fix Terminology: NAT -> (NAT-) Proxy w3c/wot-architecture#264.
-
Align Section 8 (Fix #215) w3c/wot-architecture#261.
-
Align section 7 and update ReSpec configuration w3c/wot-architecture#259.
-
Update Figures 27 and 28 (Servient implementation) and also 25 w3c/wot-architecture#244.
-
Figure revision and cleanup w3c/wot-architecture#251.
-
-
1 pull request reopened.
-
Editorial chapter 7 w3c/wot-architecture#301, by @mlagally.
-
-
40 pull requests received 186 new comments.
-
arch-call-on-9-5-[POST-CR-cand3] Align with TD spec terminology and fix 6.7 w3c/wot-architecture#346 (16 comments by @mkovatsc)
-
apply feedback from the CR version w3c/wot-architecture#353 (13 comments by @ashimura, @k-toumura, @mkovatsc, @mlagally)
-
Improve Data Schema illustration w3c/wot-architecture#317 (6 comments by @k-toumura, @mkovatsc, @mlagally)
-
Aligned section 9 with improved section 6 (for issue #216) w3c/wot-architecture#263 (6 comments by @mlagally, @takuki)
-
[POST-CR-cand3] Align with TD spec terminology and fix 6.7 w3c/wot-architecture#338 (2 comments by @mkovatsc, @mlagally)
-
Remove direct refs to sec best practices and testing docs w3c/wot-architecture#288 (2 comments by @mkovatsc)
-
Update discussion of support for existing devices (issues 279 and 276) w3c/wot-architecture#289 (2 comments by @mkovatsc)
-
Remove Application definition from Terminology w3c/wot-architecture#292 (2 comments by @mlagally, @zolkis)
-
Move security definitions to terminology (issue 275) w3c/wot-architecture#290 (2 comments by @mkovatsc, @mlagally)
-
CR changes since CR-candidate-3 - includes PRs 321, 337 and 340 w3c/wot-architecture#345 (1 comment by @mlagally)
-
Moved the historical information to the acknowledgement (Issue #206) w3c/wot-architecture#258 (1 comment by @takuki)
-
Update Figures 27 and 28 (Servient implementation) and also 25 w3c/wot-architecture#244 (1 comment by @mlagally)
w3c/wot-scripting-api
-
2 issues opened.
-
Last minute TD change: "name" changed to "title" on thing level w3c/wot-scripting-api#171, by @danielpeintner.
-
Subscribe vs Observe Property w3c/wot-scripting-api#169, by @danielpeintner.
-
-
2 issues closed.
-
Subscribe vs Observe Property w3c/wot-scripting-api#169.
-
Remove uriVariables from ConsumedThing interactions w3c/wot-scripting-api#166.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
WiP: Editorial sweep w3c/wot-scripting-api#170, by @zolkis.
-
-
2 pull requests merged.
-
WiP: Editorial sweep w3c/wot-scripting-api#170.
-
Rewrite the spec according to past few months discussions for the new WD w3c/wot-scripting-api#165.
-
-
2 pull requests received 13 new comments.
-
Rewrite the spec according to past few months discussions for the new WD w3c/wot-scripting-api#165 (10 comments by @danielpeintner, @zolkis)
-
Participants
-
1 organization joined.
-
Ierae Securiy, Inc. joined.
-
-
2 organizations left.
-
MindX left.
-
Technische Universitaet Berlin left.
-
GitHub
w3c/wot-thing-description
-
34 issues opened.
-
Proper IANA Considerations section w3c/wot-thing-description#588, by @mkovatsc.
-
@context below document level for parts of TD w3c/wot-thing-description#587, by @takuki.
-
Clarify on the timezone of DateTime serialization in TD w3c/wot-thing-description#586, by @takuki.
-
i18n checklist for Handling base direction for strings w3c/wot-thing-description#585, by @takuki.
-
i18n checklist for declaring language at the resource level w3c/wot-thing-description#584, by @takuki.
-
i18n check item: TD spec describes a format or data that is likely to need localization w3c/wot-thing-description#583, by @takuki.
-
Check against i18n Review Checklist w3c/wot-thing-description#582, by @takuki.
-
i18n checklist for Working with personal names w3c/wot-thing-description#580, by @chachamimm.
-
i18n checklist for Working with numbers w3c/wot-thing-description#579, by @takuki.
-
i18n checklist for Working with time w3c/wot-thing-description#578, by @ToruKawaguchi.
-
Typo - htv / http in Example 2 w3c/wot-thing-description#577, by @azaroth42.
-
Update references to external ontologies (OM, SAREF) w3c/wot-thing-description#576, by @vcharpenay.
-
Clarify assertions in Section 5 & 6 w3c/wot-thing-description#575, by @vcharpenay.
-
Make Section 6 normative? w3c/wot-thing-description#572, by @vcharpenay.
-
Can uriVariables be encapsulated in Protocol Bindings? w3c/wot-thing-description#569, by @zolkis.
-
Semantics of Forms.op "writeallproperties" is unclear w3c/wot-thing-description#568, by @zolkis.
-
Inconsistency in the first paragraphs of section w3c/wot-thing-description#564, by @egekorkan.
-
Reading and writing Properties are not consistent w3c/wot-thing-description#563, by @egekorkan.
-
"htv:method" in Example 11 w3c/wot-thing-description#561, by @ashimura.
-
Make a request for TD media type registration at IANA w3c/wot-thing-description#560, by @sebastiankb.
-
TD-TAG-review branch needs to be merged into master w3c/wot-thing-description#559, by @takuki.
-
TD has no support for describing methods w3c/wot-thing-description#558, by @mkovatsc.
-
contentEncoding form field w3c/wot-thing-description#557, by @mkovatsc.
-
Selection of the op types should extendable w3c/wot-thing-description#556, by @sebastiankb.
-
Define form context w3c/wot-thing-description#555, by @mkovatsc.
-
Usage of "endpoint" throughout document w3c/wot-thing-description#554, by @mkovatsc.
-
5.4.7 CertSecurityScheme - Pre-shared key identity w3c/wot-thing-description#553, by @mkovatsc.
-
Fix urn:dev: in examples w3c/wot-thing-description#552, by @mkovatsc.
-
JSON Schema security scheme could be moved to a separate file and referenced from the main schema w3c/wot-thing-description#551, by @jmcanterafonseca.
-
In JSON Schemas put definitions at the beginning w3c/wot-thing-description#550, by @jmcanterafonseca.
-
Use JSON-Schema Draft07 in JSON Schemas w3c/wot-thing-description#549, by @jmcanterafonseca.
-
Is @context properly specified in JSON-LD examples? w3c/wot-thing-description#548, by @jmcanterafonseca.
-
[Editorial] Example hrefs are inconsistent w3c/wot-thing-description#547, by @egekorkan.
-
Rename created --> createdAt. lastModified --> modifiedAt w3c/wot-thing-description#546, by @jmcanterafonseca.
-
-
45 issues closed.
-
Map of type w3c/wot-thing-description#345.
-
Clarify assertions in Section 5 & 6 w3c/wot-thing-description#575.
-
TD has no support for describing methods w3c/wot-thing-description#558.
-
base URI definition in Thing class is a bit confusing w3c/wot-thing-description#454.
-
Fix links on the HTML documentation of wot-security and json-schema vocabularies w3c/wot-thing-description#287.
-
@context defined as of type array only w3c/wot-thing-description#471.
-
Standard format for time stamps w3c/wot-thing-description#522.
-
Can uriVariables be encapsulated in Protocol Bindings? w3c/wot-thing-description#569.
-
Make Section 6 normative? w3c/wot-thing-description#572.
-
Prepare modular vocabulary w3c/wot-thing-description#167.
-
Is WoT ontology normative or not w3c/wot-thing-description#56.
-
TD-TAG-review branch needs to be merged into master w3c/wot-thing-description#559.
-
Clearification about 'Simple' and 'Full' TD Serialization w3c/wot-thing-description#539.
-
Mandatory fields vs default value w3c/wot-thing-description#337.
-
Must be serialized as array w3c/wot-thing-description#396.
-
"htv:method" in Example 11 w3c/wot-thing-description#561.
-
7.2 Transformation to JSON-LD & RDF seems unnecessary w3c/wot-thing-description#444.
-
No "deceleration" in example 30 w3c/wot-thing-description#378.
-
Require UTF-8 encoding of TDs w3c/wot-thing-description#331.
-
Clarify relationship of security schemes between WoT and OpenAPI w3c/wot-thing-description#201.
-
parent and child assertions w3c/wot-thing-description#387.
-
Consider adding "scopes" to bearer and pop SecuritySchemes w3c/wot-thing-description#475.
-
rename event keywords subscription and cancellation w3c/wot-thing-description#403.
-
top level assertions w3c/wot-thing-description#312.
-
Assertions for namespace / JSON-LD context file w3c/wot-thing-description#280.
-
type should be provided always in TD w3c/wot-thing-description#258.
-
Material to pitch use of semantics in TDs w3c/wot-thing-description#53.
-
items is data schema or JSON Object or array of data schema? w3c/wot-thing-description#364.
-
[Editorial] Introduction paragraph 3, not-clear mention of "simple" w3c/wot-thing-description#385.
-
[typo] Typo at Introduction section w3c/wot-thing-description#540.
-
[question] Forms without href if base is defined w3c/wot-thing-description#383.
-
Subscription and Cancellation response and request data schemas w3c/wot-thing-description#398.
-
@context and @type are not in Information Model w3c/wot-thing-description#394.
-
scopes explanation in form is not linked to oauth2 in securityDefinitions w3c/wot-thing-description#470.
-
security in forms mentions lower levels w3c/wot-thing-description#350.
-
@context for security and data schema w3c/wot-thing-description#536.
-
Should the Full Validation Schema be referenced w3c/wot-thing-description#473.
-
Assertions in section 7.1 redundant? w3c/wot-thing-description#434.
-
Adding new subprotocols w3c/wot-thing-description#410.
-
Metadata fields in Thing (mandatory and optional) w3c/wot-thing-description#142.
-
Remove note in Section 6 w3c/wot-thing-description#514.
-
Vocabulary change: InteractionPattern to Affordance w3c/wot-thing-description#282.
-
Delete writeOnly w3c/wot-thing-description#266.
-
Web Link definitions should be in an own namespaces w3c/wot-thing-description#253.
-
Is @context properly specified in JSON-LD examples? w3c/wot-thing-description#548.
-
-
1 issue reopened.
-
i18n checklist for Working with time w3c/wot-thing-description#578, by @ToruKawaguchi.
-
-
51 issues received 118 new comments.
-
JSON-LD Best Practice - Version JSON-LD Context files w3c/wot-thing-description#442 (9 comments by @ashimura, @ektrah, @mkovatsc, @msporny, @sebastiankb, @vcharpenay)
-
Clearification about 'Simple' and 'Full' TD Serialization w3c/wot-thing-description#539 (9 comments by @jmcanterafonseca, @sebastiankb, @takuki)
-
Testing "type = array of X" assertions w3c/wot-thing-description#388 (5 comments by @egekorkan, @mmccool, @sebastiankb)
-
contentEncoding form field w3c/wot-thing-description#557 (5 comments by @ektrah, @mkovatsc, @sebastiankb, @takuki)
-
In JSON Schemas put definitions at the beginning w3c/wot-thing-description#550 (5 comments by @egekorkan, @jmcanterafonseca)
-
"format" in DataSchema needs an example w3c/wot-thing-description#478 (4 comments by @egekorkan, @jmcanterafonseca, @sebastiankb)
-
Typo - htv / http in Example 2 w3c/wot-thing-description#577 (4 comments by @azaroth42, @sebastiankb, @vcharpenay)
-
TD has no support for describing methods w3c/wot-thing-description#558 (4 comments by @mkovatsc, @sebastiankb, @vcharpenay)
-
Selection of the op types should extendable w3c/wot-thing-description#556 (4 comments by @egekorkan, @sebastiankb)
-
Use JSON-Schema Draft07 in JSON Schemas w3c/wot-thing-description#549 (4 comments by @egekorkan, @jmcanterafonseca)
-
Clarify assertions in Section 5 & 6 w3c/wot-thing-description#575 (3 comments by @egekorkan, @vcharpenay)
-
@context defined as of type array only w3c/wot-thing-description#471 (3 comments by @jmcanterafonseca, @sebastiankb, @vcharpenay)
-
Namespace IRIs need to be populated on w3.org Web server w3c/wot-thing-description#432 (3 comments by @mkovatsc, @vcharpenay)
-
Reading and writing Properties are not consistent w3c/wot-thing-description#563 (3 comments by @mkovatsc, @sebastiankb)
-
Standard format for time stamps w3c/wot-thing-description#522 (3 comments by @jmcanterafonseca, @sebastiankb, @vcharpenay)
-
JSON Schema security scheme could be moved to a separate file and referenced from the main schema w3c/wot-thing-description#551 (3 comments by @egekorkan, @jmcanterafonseca)
-
i18n checklist for Working with personal names w3c/wot-thing-description#580 (2 comments by @mmccool, @takuki)
-
Can uriVariables be encapsulated in Protocol Bindings? w3c/wot-thing-description#569 (2 comments by @zolkis)
-
Make a request for TD media type registration at IANA w3c/wot-thing-description#560 (2 comments by @ektrah, @sebastiankb)
-
[question] Forms without href if base is defined w3c/wot-thing-description#383 (2 comments by @egekorkan, @mkovatsc)
-
5.4.7 CertSecurityScheme - Pre-shared key identity w3c/wot-thing-description#553 (1 comment by @mmccool)
-
Allow "security" to include both SecurityScheme objects and declared identifiers w3c/wot-thing-description#300 (1 comment by @sebastiankb)
-
ThingTemplate definition is missing in td.ttl w3c/wot-thing-description#416 (1 comment by @sebastiankb)
-
Fix links on the HTML documentation of wot-security and json-schema vocabularies w3c/wot-thing-description#287 (1 comment by @sebastiankb)
-
Inconsistency in the first paragraphs of section w3c/wot-thing-description#564 (1 comment by @vcharpenay)
-
TD-TAG-review branch needs to be merged into master w3c/wot-thing-description#559 (1 comment by @takuki)
-
items is data schema or JSON Object or array of data schema? w3c/wot-thing-description#364 (1 comment by @egekorkan)
-
[Editorial] inline JSON is formatted like normal text w3c/wot-thing-description#468 (1 comment by @egekorkan)
-
Subscription and Cancellation response and request data schemas w3c/wot-thing-description#398 (1 comment by @egekorkan)
-
[Editorial] DataSchema subclass order is not consistent w3c/wot-thing-description#467 (1 comment by @egekorkan)
-
@context and @type are not in Information Model w3c/wot-thing-description#394 (1 comment by @egekorkan)
-
scopes explanation in form is not linked to oauth2 in securityDefinitions w3c/wot-thing-description#470 (1 comment by @egekorkan)
-
Is @context properly specified in JSON-LD examples? w3c/wot-thing-description#548 (1 comment by @vcharpenay)
-
Rename created --> createdAt. lastModified --> modifiedAt w3c/wot-thing-description#546 (1 comment by @sebastiankb)
-
-
9 pull requests opened.
-
Updated test results - 25 April 2019 w3c/wot-thing-description#581, by @mmccool.
-
WIP: more formal definitions for assertions in Sections 5 & 6 w3c/wot-thing-description#574, by @vcharpenay.
-
change description in validation schema w3c/wot-thing-description#573, by @egekorkan.
-
Remove full schema validation related information w3c/wot-thing-description#571, by @egekorkan.
-
Integrate master branch changes onto TAG Review branch w3c/wot-thing-description#570, by @takuki.
-
Do not use term "Thing Resource" (Issue #535) w3c/wot-thing-description#567, by @takuki.
-
Syncing with TAG branch. w3c/wot-thing-description#566, by @takuki.
-
Fix assertion that items MUST be object w3c/wot-thing-description#565, by @egekorkan.
-
WIP: small issue fixes w3c/wot-thing-description#562, by @egekorkan.
-
-
13 pull requests merged.
-
Updated test results - 25 April 2019 w3c/wot-thing-description#581.
-
WIP: more formal definitions for assertions in Sections 5 & 6 w3c/wot-thing-description#574.
-
change description in validation schema w3c/wot-thing-description#573.
-
Remove full schema validation related information w3c/wot-thing-description#571.
-
Integrate master branch changes onto TAG Review branch w3c/wot-thing-description#570.
-
Do not use term "Thing Resource" (Issue #535) w3c/wot-thing-description#567.
-
Syncing with TAG branch. w3c/wot-thing-description#566.
-
Fix assertion that items MUST be object w3c/wot-thing-description#565.
-
WIP: small issue fixes w3c/wot-thing-description#562.
-
Clarify WoT/OpenAPI relationship w3c/wot-thing-description#545.
-
Assert TDs must be serialized using UTF-8 w3c/wot-thing-description#543.
-
Update full schema w3c/wot-thing-description#542.
-
Update simple schema w3c/wot-thing-description#541.
-
-
1 pull request closed.
-
RDF model proposal MJK w3c/wot-thing-description#162.
-
-
4 pull requests received 4 new comments.
-
Remove full schema validation related information w3c/wot-thing-description#571 (1 comment by @sebastiankb)
w3c/wot-architecture
-
35 issues opened.
-
Terminology definition of Application w3c/wot-architecture#260, by @mkovatsc.
-
Markup all assertions w3c/wot-architecture#249, by @mlagally.
-
handle i18n questions w3c/wot-architecture#248, by @mlagally.
-
6.5 Hypermedia Controls: Addtional examples of similar standards? w3c/wot-architecture#246, by @ashimura.
-
Editorial: Consider rewording the relationship to CoRAL w3c/wot-architecture#236, by @mlagally.
-
Revise "6.6.1 Hypermedia driven" section w3c/wot-architecture#235, by @mlagally.
-
Set up assertion extraction tooling w3c/wot-architecture#234, by @mlagally.
-
Actions and Events: remove details about data schemas w3c/wot-architecture#233, by @mlagally.
-
Update figure 21 and figure 22 w3c/wot-architecture#232, by @mlagally.
-
Update Figure 16 w3c/wot-architecture#231, by @mlagally.
-
Align Figure 15 with new terminology w3c/wot-architecture#230, by @mlagally.
-
Create 3 figures for overview section 6.1 w3c/wot-architecture#229, by @mlagally.
-
Consistent diagrams w3c/wot-architecture#228, by @mlagally.
-
Clarification of the term "behavior" w3c/wot-architecture#220, by @mkovatsc.
-
Move section A into the Binding Template document w3c/wot-architecture#218, by @mlagally.
-
Align section 10 with improved section 6 from issue 188 w3c/wot-architecture#217, by @mlagally.
-
Align section 9 with improved section 6 from issue 188 w3c/wot-architecture#216, by @mlagally.
-
Align section 8 with improved section 6 from issue 188 w3c/wot-architecture#215, by @mlagally.
-
Align section 7 with improved section 6 from issue 188 w3c/wot-architecture#214, by @mlagally.
-
Fix WoT Client Terminology w3c/wot-architecture#213, by @mlagally.
-
Fix Terminology: NAT -> (NAT-) Proxy w3c/wot-architecture#212, by @mlagally.
-
Fix Servient definition in section 9 w3c/wot-architecture#211, by @mlagally.
-
Language clarifications in section 9 w3c/wot-architecture#210, by @mlagally.
-
Section 8.10.2 Existing Device Described with a Thing Description is too restrictive w3c/wot-architecture#209, by @mlagally.
-
Need deployment example for Cloud Server with Client devices w3c/wot-architecture#208, by @mlagally.
-
Update Wikipedia page on WoT w3c/wot-architecture#207, by @mlagally.
-
Relationship between academic project and W3C WoT is not clear w3c/wot-architecture#206, by @takuki.
-
"WoT network components" in abstract is not immediately clear w3c/wot-architecture#205, by @takuki.
-
"concrete deployment scenarios" are not described w3c/wot-architecture#204, by @takuki.
-
validate all references w3c/wot-architecture#200, by @mlagally.
-
Missing batch operation types w3c/wot-architecture#199, by @mkovatsc.
-
Form definition fixes w3c/wot-architecture#198, by @mkovatsc.
-
Check usage of "media type" vs "content type" w3c/wot-architecture#197, by @mkovatsc.
-
Summary section 4.3 should must not mandate client server roles of specific blocks w3c/wot-architecture#195, by @mlagally.
-
Duplicated text at https://w3c.github.io/wot-architecture/#sec-web-thing w3c/wot-architecture#194, by @jmcanterafonseca.
-
-
26 issues closed.
-
Update Figure 16 w3c/wot-architecture#231.
-
Align Figure 15 with new terminology w3c/wot-architecture#230.
-
Create 3 figures for overview section 6.1 w3c/wot-architecture#229.
-
Move section A into the Binding Template document w3c/wot-architecture#218.
-
Fix WoT Client Terminology w3c/wot-architecture#213.
-
Fix Servient definition in section 9 w3c/wot-architecture#211.
-
Language clarifications in section 9 w3c/wot-architecture#210.
-
Summary section 4.3 should must not mandate client server roles of specific blocks w3c/wot-architecture#195.
-
Duplicated text at https://w3c.github.io/wot-architecture/#sec-web-thing w3c/wot-architecture#194.
-
Describe Server and Client at the section "6.2 WoT Architecture" w3c/wot-architecture#188.
-
Section 6.2 seems Redundant (System Configuration) w3c/wot-architecture#180.
-
Mark Example Sequences section as non-normative, fix diagrams w3c/wot-architecture#178.
-
Actions and Events: remove details about data schemas w3c/wot-architecture#233.
-
Check usage of "media type" vs "content type" w3c/wot-architecture#197.
-
Missing batch operation types w3c/wot-architecture#199.
-
Form definition fixes w3c/wot-architecture#198.
-
Make Interaction affordances normative? w3c/wot-architecture#174.
-
Define "Web Technology" and target protocols w3c/wot-architecture#133.
-
Don't enforce server paradigm on devices w3c/wot-architecture#146.
-
Resolve Editor Notes w3c/wot-architecture#164.
-
Editorial work w3c/wot-architecture#153.
-
Fix component diagrams in section 6 w3c/wot-architecture#165.
-
Clarify requirement in section 5.1.10 w3c/wot-architecture#166.
-
Use "Exposed Thing" and "Consumed Thing" consistently w3c/wot-architecture#171.
-
Align terminology and improve english wording in section 9 w3c/wot-architecture#175.
-
Fix references w3c/wot-architecture#192.
-
-
1 issue reopened.
-
Describe Server and Client at the section "6.2 WoT Architecture" w3c/wot-architecture#188, by @mkovatsc.
-
-
27 issues received 60 new comments.
-
Describe Server and Client at the section "6.2 WoT Architecture" w3c/wot-architecture#188 (15 comments by @k-toumura, @mkovatsc, @mlagally, @mmccool, @takuki)
-
Section 6.2 seems Redundant (System Configuration) w3c/wot-architecture#180 (3 comments by @mkovatsc, @mlagally)
-
Duplicated text at https://w3c.github.io/wot-architecture/#sec-web-thing w3c/wot-architecture#194 (2 comments by @k-toumura, @mlagally)
-
6.5 Hypermedia Controls: Addtional examples of similar standards? w3c/wot-architecture#246 (1 comment by @mkovatsc)
-
Align section 8 with improved section 6 from issue 188 w3c/wot-architecture#215 (1 comment by @mkovatsc)
-
Align section 7 with improved section 6 from issue 188 w3c/wot-architecture#214 (1 comment by @mlagally)
-
Relationship between academic project and W3C WoT is not clear w3c/wot-architecture#206 (1 comment by @mlagally)
-
"WoT network components" in abstract is not immediately clear w3c/wot-architecture#205 (1 comment by @mlagally)
-
Align section 9 with improved section 6 from issue 188 w3c/wot-architecture#216 (1 comment by @k-toumura)
-
Summary section 4.3 should must not mandate client server roles of specific blocks w3c/wot-architecture#195 (1 comment by @k-toumura)
-
-
33 pull requests opened.
-
Align Section 8 (Fix #215) w3c/wot-architecture#261, by @mkovatsc.
-
Align section 7 and update ReSpec configuration w3c/wot-architecture#259, by @k-toumura.
-
Moved the historical information to the acknowledgement (Issue #206) w3c/wot-architecture#258, by @takuki.
-
Moved the historical information to the acknowledgement (Issue #206) w3c/wot-architecture#257, by @takuki.
-
(Editorial) "WoT Network Components" to "devices" (Issue #205) w3c/wot-architecture#256, by @takuki.
-
(Editorial) "WoT Network Components" to "devices" (Issue #205) w3c/wot-architecture#255, by @takuki.
-
(Editorial) "patterns" of concrete deployment scenarios (Issue #204) w3c/wot-architecture#254, by @takuki.
-
Editorial fix for Issue #204 w3c/wot-architecture#253, by @takuki.
-
Editorial fix for Issue #204 w3c/wot-architecture#252, by @takuki.
-
Figure revision and cleanup w3c/wot-architecture#251, by @mkovatsc.
-
Update Figure 16 Linked Things w3c/wot-architecture#250, by @k-toumura.
-
changing Kajimoto-san's affiliation w3c/wot-architecture#247, by @ashimura.
-
WIP: Assertion tooling w3c/wot-architecture#245, by @mmccool.
-
Update Figures 27 and 28 (Servient implementation) and also 25 w3c/wot-architecture#244, by @mmccool.
-
Update PPT master for Figures 21 and 22 w3c/wot-architecture#243, by @mmccool.
-
Fix Web Thing text and figure and fix #230 (overview figure) w3c/wot-architecture#242, by @mkovatsc.
-
Fix #233 (no exact number of schemas in Affordances) w3c/wot-architecture#241, by @mkovatsc.
-
Fix #197 (Media Type vs Content Type) w3c/wot-architecture#240, by @mkovatsc.
-
Update figures and terminology in section 9. WoT Deployments w3c/wot-architecture#239, by @k-toumura.
-
Add and update figures in section 6. WoT Architecture w3c/wot-architecture#238, by @k-toumura.
-
Use case figures updates and other minor editorial fixes. w3c/wot-architecture#237, by @k-toumura.
-
Updated section 6.10 System Configuration (for Issue #188) w3c/wot-architecture#227, by @takuki.
-
emphasize 'Describe, don't prescribe' in Abstract w3c/wot-architecture#226, by @k-toumura.
-
Fix SVG figures w3c/wot-architecture#225, by @k-toumura.
-
Merge pull request #29 from w3c/master w3c/wot-architecture#224, by @mlagally.
-
Update of TAG version as agreed in call on 11.4. w3c/wot-architecture#223, by @mlagally.
-
Issue 218 remvove sequence diagrams w3c/wot-architecture#222, by @mlagally.
-
Revision of Section 6 to reflect Things and Consumers w3c/wot-architecture#221, by @mkovatsc.
-
Move Section 6.2 to the end of 6 w3c/wot-architecture#219, by @mkovatsc.
-
Update diagrams w3c/wot-architecture#203, by @mlagally.
-
Terminology updates w3c/wot-architecture#202, by @mlagally.
-
Update a figure in use case summary w3c/wot-architecture#201, by @k-toumura.
-
Terminology review with IETF w3c/wot-architecture#196, by @mkovatsc.
-
-
26 pull requests merged.
-
(Editorial) "patterns" of concrete deployment scenarios (Issue #204) w3c/wot-architecture#254.
-
(Editorial) "WoT Network Components" to "devices" (Issue #205) w3c/wot-architecture#256.
-
Moved the historical information to the acknowledgement (Issue #206) w3c/wot-architecture#257.
-
(Editorial) "WoT Network Components" to "devices" (Issue #205) w3c/wot-architecture#255.
-
Editorial fix for Issue #204 w3c/wot-architecture#253.
-
Fix Web Thing text and figure and fix #230 (overview figure) w3c/wot-architecture#242.
-
changing Kajimoto-san's affiliation w3c/wot-architecture#247.
-
Fix #233 (no exact number of schemas in Affordances) w3c/wot-architecture#241.
-
Fix #197 (Media Type vs Content Type) w3c/wot-architecture#240.
-
Update figures and terminology in section 9. WoT Deployments w3c/wot-architecture#239.
-
Add and update figures in section 6. WoT Architecture w3c/wot-architecture#238.
-
Use case figures updates and other minor editorial fixes. w3c/wot-architecture#237.
-
Updated section 6.10 System Configuration (for Issue #188) w3c/wot-architecture#227.
-
Update PPT master for Figures 21 and 22 w3c/wot-architecture#243.
-
emphasize 'Describe, don't prescribe' in Abstract w3c/wot-architecture#226.
-
Fix SVG figures w3c/wot-architecture#225.
-
Revision of Section 6 to reflect Things and Consumers w3c/wot-architecture#221.
-
Update of TAG version as agreed in call on 11.4. w3c/wot-architecture#223.
-
Issue 218 remvove sequence diagrams w3c/wot-architecture#222.
-
Update diagrams w3c/wot-architecture#203.
-
Move Section 6.2 to the end of 6 w3c/wot-architecture#219.
-
Update a figure in use case summary w3c/wot-architecture#201.
-
Terminology updates w3c/wot-architecture#202.
-
Terminology review with IETF w3c/wot-architecture#196.
-
WIP: Sync TAG-review updates back into master w3c/wot-architecture#187.
-
Revise Section 11 (now Appendix A) Example Sequences to use consistent terminology w3c/wot-architecture#189.
-
-
4 pull requests closed.
-
Update Figure 16 Linked Things w3c/wot-architecture#250.
-
Editorial fix for Issue #204 w3c/wot-architecture#252.
-
WIP: Assertion tooling w3c/wot-architecture#245.
-
Merge pull request #29 from w3c/master w3c/wot-architecture#224.
-
-
20 pull requests received 135 new comments.
-
Align Section 8 (Fix #215) w3c/wot-architecture#261 (37 comments by @k-toumura, @mkovatsc, @mlagally)
-
Revision of Section 6 to reflect Things and Consumers w3c/wot-architecture#221 (32 comments by @mkovatsc, @mlagally)
-
Updated section 6.10 System Configuration (for Issue #188) w3c/wot-architecture#227 (15 comments by @k-toumura, @mkovatsc, @takuki)
-
Terminology review with IETF w3c/wot-architecture#196 (8 comments by @k-toumura, @mkovatsc, @mlagally, @takuki)
-
Update Figures 27 and 28 (Servient implementation) and also 25 w3c/wot-architecture#244 (6 comments by @mkovatsc, @mlagally, @mmccool)
-
WIP: Sync TAG-review updates back into master w3c/wot-architecture#187 (5 comments by @k-toumura, @mlagally, @mmccool)
-
Moved the historical information to the acknowledgement (Issue #206) w3c/wot-architecture#258 (4 comments by @mkovatsc, @mlagally)
-
Fix Web Thing text and figure and fix #230 (overview figure) w3c/wot-architecture#242 (4 comments by @k-toumura, @mlagally)
-
Add and update figures in section 6. WoT Architecture w3c/wot-architecture#238 (4 comments by @k-toumura, @mkovatsc, @mlagally)
-
Use case figures updates and other minor editorial fixes. w3c/wot-architecture#237 (3 comments by @k-toumura, @mlagally)
-
Revise Section 11 (now Appendix A) Example Sequences to use consistent terminology w3c/wot-architecture#189 (1 comment by @mlagally)
-
Fixed a link in security_and_privacy.md to point to the TD repository. w3c/wot-architecture#190 (1 comment by @mlagally)
-
Fix references to unpublished security drafts and TAG TD spec w3c/wot-architecture#193 (1 comment by @mlagally)
-
w3c/wot-scripting-api
-
3 issues opened.
-
Remove Discovery from Core WoT interface? w3c/wot-scripting-api#168, by @danielpeintner.
-
WebIDL : attributes vs functions w3c/wot-scripting-api#167, by @danielpeintner.
-
Remove uriVariables from ConsumedThing interactions w3c/wot-scripting-api#166, by @zolkis.
-
-
1 issue closed.
-
typescript definitions: Items should not be required in an ArraySchema w3c/wot-scripting-api#163.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Rewrite the spec according to past few months discussions for the new WD w3c/wot-scripting-api#165, by @zolkis.
-
-
1 pull request merged.
-
Fix #163 w3c/wot-scripting-api#164.
-
-
2 pull requests received 3 new comments.
-
Rewrite the spec according to past few months discussions for the new WD w3c/wot-scripting-api#165 (2 comments by @zolkis)
-
w3c/wot-security
-
3 issues closed.
-
Add Material for "Security Validation" section w3c/wot-security#23.
-
Security Best Practices for WoT Systems w3c/wot-security#102.
-
Update terminology in testing plan to be consistent with ITU terminology w3c/wot-security#124.
-
-
6 issues received 7 new comments.
-
Terminology inconsistency - Proxy and Gateway are used interchangeably. w3c/wot-security#123 (2 comments by @mmccool)
-
Support both strings and SecurityScheme objects in "security" fields w3c/wot-security#122 (1 comment by @mmccool)
-
Update terminology in testing plan to be consistent with ITU terminology w3c/wot-security#124 (1 comment by @mmccool)
-
-
1 pull request closed.
-
New subsection on HTTP & WebSockets w3c/wot-security#37.
-
-
1 pull request received 1 new comment.
w3c/wot-binding-templates
-
1 pull request opened.
-
Moving sequence diagrams from architecture spec to binding spec w3c/wot-binding-templates#51, by @mlagally.
-
GitHub
w3c/wot-thing-description
-
23 issues opened.
-
[typo] Typo at Introduction section w3c/wot-thing-description#540, by @egekorkan.
-
Clearification about 'Simple' and 'Full' TD Serialization w3c/wot-thing-description#539, by @sebastiankb.
-
@context for security and data schema w3c/wot-thing-description#536, by @egekorkan.
-
Top level versus root versus thing resource w3c/wot-thing-description#535, by @egekorkan.
-
Standard format for time stamps w3c/wot-thing-description#522, by @akeranen.
-
Change description for 'observable' to reflect its purpose w3c/wot-thing-description#521, by @sebastiankb.
-
Remove note in Section 6 w3c/wot-thing-description#514, by @sebastiankb.
-
JSON-LD Examples are not valid according to schema w3c/wot-thing-description#511, by @egekorkan.
-
Clarify how new security schemes can be given in extensions w3c/wot-thing-description#501, by @mmccool.
-
Possible typo at the explanation of format w3c/wot-thing-description#496, by @egekorkan.
-
@type in PropertyAffordance level can relate to DataSchema AND InteractionAffordance w3c/wot-thing-description#495, by @egekorkan.
-
Consider adding "components" to TD ontology w3c/wot-thing-description#490, by @mlagally.
-
Link model figure is mis-labeled as "Security Model" w3c/wot-thing-description#483, by @takuki.
-
Allow multi-language descriptions in SecuritySchemes w3c/wot-thing-description#479, by @mmccool.
-
"format" in DataSchema needs an example w3c/wot-thing-description#478, by @takuki.
-
"anchor" needs an example w3c/wot-thing-description#477, by @takuki.
-
Consider adding "scopes" to bearer and pop SecuritySchemes w3c/wot-thing-description#475, by @mmccool.
-
Should the Full Validation Schema be referenced w3c/wot-thing-description#473, by @egekorkan.
-
@context defined as of type array only w3c/wot-thing-description#471, by @danielpeintner.
-
scopes explanation in form is not linked to oauth2 in securityDefinitions w3c/wot-thing-description#470, by @egekorkan.
-
[Editorial] links are rendered splitted in Firefox w3c/wot-thing-description#469, by @egekorkan.
-
[Editorial] inline JSON is formatted like normal text w3c/wot-thing-description#468, by @egekorkan.
-
[Editorial] DataSchema subclass order is not consistent w3c/wot-thing-description#467, by @egekorkan.
-
-
26 issues closed.
-
security assertion missing w3c/wot-thing-description#367.
-
[ImplementationReport] numbered ids are not properly linked to the spec w3c/wot-thing-description#404.
-
Possible typo at the explanation of format w3c/wot-thing-description#496.
-
JSON Schema too strict on @context contents w3c/wot-thing-description#447.
-
op values are not explained w3c/wot-thing-description#405.
-
Using "http" as a term is strange w3c/wot-thing-description#443.
-
Link's href description talks about interaction pattern w3c/wot-thing-description#421.
-
Allow Form's "rel" to be a string or an array w3c/wot-thing-description#236.
-
Do we need a URI datatype? w3c/wot-thing-description#226.
-
id renaming w3c/wot-thing-description#377.
-
uriVariable does not seem to be proper defined or example is wrong w3c/wot-thing-description#376.
-
Example1, Example2 and Example35 contain validation errors w3c/wot-thing-description#448.
-
Default values for op w3c/wot-thing-description#386.
-
Rename ID term td-readOnly-observable-default to td-safe-idempotent-default w3c/wot-thing-description#399.
-
@type in PropertyAffordance level can relate to DataSchema AND InteractionAffordance w3c/wot-thing-description#495.
-
Link model figure is mis-labeled as "Security Model" w3c/wot-thing-description#483.
-
JSON-LD Examples are not valid according to schema w3c/wot-thing-description#511.
-
Property extending DataSchema w3c/wot-thing-description#338.
-
readOnly and writeOnly should be optional for action parameters w3c/wot-thing-description#322.
-
Assertion/Schema mismatch for td-{property,event,action}-arrays w3c/wot-thing-description#321.
-
id term is missing w3c/wot-thing-description#317.
-
A way to read all Properties at once? w3c/wot-thing-description#151.
-
Same description of `identity` field in CertSecurityScheme/PublicSecurityScheme/PSKSecurityScheme w3c/wot-thing-description#233.
-
Allow multi-language descriptions in SecuritySchemes w3c/wot-thing-description#479.
-
[Editorial] links are rendered splitted in Firefox w3c/wot-thing-description#469.
-
Could not create representation for the ontology server webservice. w3c/wot-thing-description#438.
-
-
55 issues received 138 new comments.
-
Clarify how new security schemes can be given in extensions w3c/wot-thing-description#501 (9 comments by @mmccool, @vcharpenay)
-
@type in PropertyAffordance level can relate to DataSchema AND InteractionAffordance w3c/wot-thing-description#495 (7 comments by @sebastiankb, @takuki, @vcharpenay)
-
op values are not explained w3c/wot-thing-description#405 (6 comments by @mjkoster, @mkovatsc, @sebastiankb, @takuki)
-
Consider adding "scopes" to bearer and pop SecuritySchemes w3c/wot-thing-description#475 (5 comments by @egekorkan, @mmccool)
-
Must be serialized as array w3c/wot-thing-description#396 (5 comments by @egekorkan, @sebastiankb, @vcharpenay)
-
names in Thing level should be MultiLanguage and not mandatory w3c/wot-thing-description#464 (5 comments by @egekorkan, @mmccool, @sebastiankb, @takuki)
-
Consider adding "components" to TD ontology w3c/wot-thing-description#490 (5 comments by @mlagally, @mmccool, @sebastiankb)
-
Change description for 'observable' to reflect its purpose w3c/wot-thing-description#521 (4 comments by @mmccool, @sebastiankb, @takuki)
-
[Editorial] Introduction paragraph 3, not-clear mention of "simple" w3c/wot-thing-description#385 (4 comments by @egekorkan, @sebastiankb)
-
7.2 Transformation to JSON-LD & RDF seems unnecessary w3c/wot-thing-description#444 (4 comments by @sebastiankb, @takuki, @vcharpenay)
-
JSON Schema too strict on @context contents w3c/wot-thing-description#447 (4 comments by @egekorkan, @sebastiankb, @vcharpenay)
-
Vocabulary change: InteractionPattern to Affordance w3c/wot-thing-description#282 (4 comments by @mjkoster, @mkovatsc, @sebastiankb, @vcharpenay)
-
@context for security and data schema w3c/wot-thing-description#536 (3 comments by @mmccool, @sebastiankb)
-
Should the Full Validation Schema be referenced w3c/wot-thing-description#473 (3 comments by @egekorkan, @sebastiankb)
-
[Editorial] links are rendered splitted in Firefox w3c/wot-thing-description#469 (3 comments by @egekorkan, @k-toumura)
-
Rename ID term td-readOnly-observable-default to td-safe-idempotent-default w3c/wot-thing-description#399 (3 comments by @mmccool, @sebastiankb)
-
Namespace IRIs need to be populated on w3.org Web server w3c/wot-thing-description#432 (3 comments by @ashimura, @sebastiankb, @vcharpenay)
-
Using "http" as a term is strange w3c/wot-thing-description#443 (3 comments by @msporny, @sebastiankb, @vcharpenay)
-
Clarify relationship of security schemes between WoT and OpenAPI w3c/wot-thing-description#201 (2 comments by @mmccool, @sebastiankb)
-
Clearification about 'Simple' and 'Full' TD Serialization w3c/wot-thing-description#539 (2 comments by @egekorkan, @sebastiankb)
-
Standard format for time stamps w3c/wot-thing-description#522 (2 comments by @mmccool, @sebastiankb)
-
Event examples are not enough w3c/wot-thing-description#351 (2 comments by @egekorkan, @sebastiankb)
-
base URI definition in Thing class is a bit confusing w3c/wot-thing-description#454 (2 comments by @sebastiankb, @takuki)
-
JSON-LD Best Practice - Version JSON-LD Context files w3c/wot-thing-description#442 (2 comments by @msporny, @vcharpenay)
-
Possible typo at the explanation of format w3c/wot-thing-description#496 (2 comments by @danielpeintner, @sebastiankb)
-
JSON-LD Examples are not valid according to schema w3c/wot-thing-description#511 (2 comments by @egekorkan, @vcharpenay)
-
Property extending DataSchema w3c/wot-thing-description#338 (2 comments by @sebastiankb, @vcharpenay)
-
Subscription and Cancellation response and request data schemas w3c/wot-thing-description#398 (2 comments by @sebastiankb)
-
items is data schema or JSON Object or array of data schema? w3c/wot-thing-description#364 (2 comments by @egekorkan, @vcharpenay)
-
Web Link definitions should be in an own namespaces w3c/wot-thing-description#253 (2 comments by @sebastiankb, @vcharpenay)
-
Could not create representation for the ontology server webservice. w3c/wot-thing-description#438 (2 comments by @vcharpenay, @yamagile)
-
scopes explanation in form is not linked to oauth2 in securityDefinitions w3c/wot-thing-description#470 (1 comment by @mmccool)
-
[ImplementationReport] numbered ids are not properly linked to the spec w3c/wot-thing-description#404 (1 comment by @mmccool)
-
Example1, Example2 and Example35 contain validation errors w3c/wot-thing-description#448 (1 comment by @sebastiankb)
-
[question] Forms without href if base is defined w3c/wot-thing-description#383 (1 comment by @sebastiankb)
-
readOnly and writeOnly should be optional for action parameters w3c/wot-thing-description#322 (1 comment by @sebastiankb)
-
Link model figure is mis-labeled as "Security Model" w3c/wot-thing-description#483 (1 comment by @vcharpenay)
-
Allow multi-language descriptions in SecuritySchemes w3c/wot-thing-description#479 (1 comment by @mmccool)
-
Link's href description talks about interaction pattern w3c/wot-thing-description#421 (1 comment by @vcharpenay)
-
-
57 pull requests opened.
-
Clarify WoT/OpenAPI relationship w3c/wot-thing-description#545, by @mmccool.
-
Minor formatting fixes for security extension example w3c/wot-thing-description#544, by @mmccool.
-
Assert TDs must be serialized using UTF-8 w3c/wot-thing-description#543, by @mmccool.
-
Update full schema w3c/wot-thing-description#542, by @egekorkan.
-
Update simple schema w3c/wot-thing-description#541, by @egekorkan.
-
Security extension example and namespaces w3c/wot-thing-description#538, by @mmccool.
-
Update at-risk assertions w3c/wot-thing-description#537, by @mmccool.
-
Recovering the tweak (#476 and #491) to avoid getting the egregious link presentation. w3c/wot-thing-description#534, by @takuki.
-
Use the TD-TAG-review version of TD draft spec in the TD Explainer on that branch. w3c/wot-thing-description#533, by @takuki.
-
synchronize with master w3c/wot-thing-description#532, by @sebastiankb.
-
update template with latest TD spec link for review w3c/wot-thing-description#531, by @sebastiankb.
-
Corrected reference to RDF Appendix in Explainer w3c/wot-thing-description#530, by @vcharpenay.
-
Updates to TAG review Explainer regarding JSON-LD 1.1 alignment w3c/wot-thing-description#529, by @mmccool.
-
Updated Recent Changes section in tag-review.html. w3c/wot-thing-description#528, by @takuki.
-
Updated appendix section D Recent Changes . w3c/wot-thing-description#527, by @takuki.
-
Sync PR with master w3c/wot-thing-description#526, by @vcharpenay.
-
Added link from 6.1 to Appendix C w3c/wot-thing-description#525, by @vcharpenay.
-
Update TAG submit message to be consistent with WoT Architecture w3c/wot-thing-description#524, by @mmccool.
-
Fixed issue in rendering nested context information w3c/wot-thing-description#523, by @vcharpenay.
-
Added references to RFC3987 and LINKED-DATA. w3c/wot-thing-description#520, by @takuki.
-
Fixed a bug in PR #518 w3c/wot-thing-description#519, by @takuki.
-
Improved #517 (editorial) w3c/wot-thing-description#518, by @takuki.
-
Clarified base URI definition (for Issue #454) w3c/wot-thing-description#517, by @takuki.
-
Create jsonld TD validation w3c/wot-thing-description#516, by @egekorkan.
-
Update validation schema w3c/wot-thing-description#515, by @egekorkan.
-
WIP: Rewrote all parts related to JSON-LD II w3c/wot-thing-description#513, by @vcharpenay.
-
Update validation schema w3c/wot-thing-description#512, by @egekorkan.
-
Rewrote all parts related to JSON-LD w3c/wot-thing-description#510, by @vcharpenay.
-
Added subclass relation between PropertyAffordance and DataSchema w3c/wot-thing-description#509, by @vcharpenay.
-
Fixing model w.r.t. subprotocols w3c/wot-thing-description#508, by @vcharpenay.
-
Testing updates prior to wide review w3c/wot-thing-description#507, by @mmccool.
-
Explainer Updates w3c/wot-thing-description#506, by @mmccool.
-
Updated Explainer w3c/wot-thing-description#505, by @mmccool.
-
Added assertions for how readOnly/writeOnly value constrain op values. (Issue #405) w3c/wot-thing-description#504, by @takuki.
-
readOnly/writeOnly/observable are no longer mandatory. (Issue #405) w3c/wot-thing-description#503, by @takuki.
-
Form's op is now mandatory with default values defined. (Issue #405) w3c/wot-thing-description#502, by @takuki.
-
Updated test results w3c/wot-thing-description#500, by @mmccool.
-
New test results w3c/wot-thing-description#499, by @mmccool.
-
Update validation schema w3c/wot-thing-description#498, by @egekorkan.
-
Updated test results on March 11 w3c/wot-thing-description#497, by @mmccool.
-
Added an Example in TD Explainer. w3c/wot-thing-description#494, by @takuki.
-
Fixed one typo "HutGub" and removed "normative" adjective in Explainer as suggested. w3c/wot-thing-description#493, by @takuki.
-
Re-formatted Appendix 3 on RDF Transformation w3c/wot-thing-description#492, by @vcharpenay.
-
Add id to conformance section, again w3c/wot-thing-description#491, by @k-toumura.
-
Add At-risk Highlighting to "Status of This Document" section w3c/wot-thing-description#489, by @mmccool.
-
Moved Transformation section to Appendix, added a note that TD is not JSON-LD. w3c/wot-thing-description#488, by @takuki.
-
TD Explainer v0.1 w3c/wot-thing-description#487, by @takuki.
-
Added "What does TD contribute to IoT Interoperability?" section in Explainer. w3c/wot-thing-description#486, by @takuki.
-
New manual inputs from Panasonic; updated at-risk w3c/wot-thing-description#485, by @mmccool.
-
Wrote a section "What role does TD specification play in WoT?" in Explainer w3c/wot-thing-description#484, by @takuki.
-
This file needs to be moved to a sub-directory. w3c/wot-thing-description#482, by @takuki.
-
Fix ids for context (@context,@type,id) vocab w3c/wot-thing-description#481, by @mmccool.
-
Allow MultiLanguage "descriptions" in SecuritySchemes w3c/wot-thing-description#480, by @mmccool.
-
Add id to conformance section w3c/wot-thing-description#476, by @k-toumura.
-
Add context to vocab ids w3c/wot-thing-description#474, by @mmccool.
-
Update Validation Schema w3c/wot-thing-description#472, by @egekorkan.
-
Moved default-value table back to Section 5 (issue #337) w3c/wot-thing-description#466, by @takuki.
-
-
54 pull requests merged.
-
Minor formatting fixes for security extension example w3c/wot-thing-description#544.
-
Security extension example and namespaces w3c/wot-thing-description#538.
-
Update at-risk assertions w3c/wot-thing-description#537.
-
Recovering the tweak (#476 and #491) to avoid getting the egregious link presentation. w3c/wot-thing-description#534.
-
Use the TD-TAG-review version of TD draft spec in the TD Explainer on that branch. w3c/wot-thing-description#533.
-
synchronize with master w3c/wot-thing-description#532.
-
Corrected reference to RDF Appendix in Explainer w3c/wot-thing-description#530.
-
update template with latest TD spec link for review w3c/wot-thing-description#531.
-
Updates to TAG review Explainer regarding JSON-LD 1.1 alignment w3c/wot-thing-description#529.
-
Updated Recent Changes section in tag-review.html. w3c/wot-thing-description#528.
-
Updated appendix section D Recent Changes . w3c/wot-thing-description#527.
-
Sync PR with master w3c/wot-thing-description#526.
-
Added link from 6.1 to Appendix C w3c/wot-thing-description#525.
-
Update TAG submit message to be consistent with WoT Architecture w3c/wot-thing-description#524.
-
Fixed issue in rendering nested context information w3c/wot-thing-description#523.
-
Added references to RFC3987 and LINKED-DATA. w3c/wot-thing-description#520.
-
Fixed a bug in PR #518 w3c/wot-thing-description#519.
-
Improved #517 (editorial) w3c/wot-thing-description#518.
-
Clarified base URI definition (for Issue #454) w3c/wot-thing-description#517.
-
Create jsonld TD validation w3c/wot-thing-description#516.
-
Update validation schema w3c/wot-thing-description#515.
-
WIP: Rewrote all parts related to JSON-LD II w3c/wot-thing-description#513.
-
Rewrote all parts related to JSON-LD w3c/wot-thing-description#510.
-
Update validation schema w3c/wot-thing-description#512.
-
Added subclass relation between PropertyAffordance and DataSchema w3c/wot-thing-description#509.
-
Fixing model w.r.t. subprotocols w3c/wot-thing-description#508.
-
Explainer Updates w3c/wot-thing-description#506.
-
Update validation schema w3c/wot-thing-description#498.
-
Testing updates prior to wide review w3c/wot-thing-description#507.
-
Updated test results w3c/wot-thing-description#500.
-
Re-formatted Appendix 3 on RDF Transformation w3c/wot-thing-description#492.
-
Add id to conformance section, again w3c/wot-thing-description#491.
-
Updated Explainer w3c/wot-thing-description#505.
-
Added assertions for how readOnly/writeOnly value constrain op values. (Issue #405) w3c/wot-thing-description#504.
-
readOnly/writeOnly/observable are no longer mandatory. (Issue #405) w3c/wot-thing-description#503.
-
Form's op is now mandatory with default values defined. (Issue #405) w3c/wot-thing-description#502.
-
New test results w3c/wot-thing-description#499.
-
Updated test results on March 11 w3c/wot-thing-description#497.
-
Added an Example in TD Explainer. w3c/wot-thing-description#494.
-
Fixed one typo "HutGub" and removed "normative" adjective in Explainer as suggested. w3c/wot-thing-description#493.
-
Add At-risk Highlighting to "Status of This Document" section w3c/wot-thing-description#489.
-
Fix syntax errors in several examples w3c/wot-thing-description#449.
-
Moved Transformation section to Appendix, added a note that TD is not JSON-LD. w3c/wot-thing-description#488.
-
Allow MultiLanguage "descriptions" in SecuritySchemes w3c/wot-thing-description#480.
-
Add id to conformance section w3c/wot-thing-description#476.
-
Update Validation Schema w3c/wot-thing-description#472.
-
TD Explainer v0.1 w3c/wot-thing-description#487.
-
Added "What does TD contribute to IoT Interoperability?" section in Explainer. w3c/wot-thing-description#486.
-
New manual inputs from Panasonic; updated at-risk w3c/wot-thing-description#485.
-
Wrote a section "What role does TD specification play in WoT?" in Explainer w3c/wot-thing-description#484.
-
This file needs to be moved to a sub-directory. w3c/wot-thing-description#482.
-
Fix ids for context (@context,@type,id) vocab w3c/wot-thing-description#481.
-
Add context to vocab ids w3c/wot-thing-description#474.
-
Moved default-value table back to Section 5 (issue #337) w3c/wot-thing-description#466.
-
-
1 pull request closed.
-
Remove td-unique-identifiers assertion w3c/wot-thing-description#436.
-
-
15 pull requests received 28 new comments.
-
Security extension example and namespaces w3c/wot-thing-description#538 (7 comments by @mmccool, @takuki)
-
Re-formatted Appendix 3 on RDF Transformation w3c/wot-thing-description#492 (2 comments by @sebastiankb, @vcharpenay)
-
Add At-risk Highlighting to "Status of This Document" section w3c/wot-thing-description#489 (2 comments by @k-toumura, @mmccool)
-
Fixed issue in rendering nested context information w3c/wot-thing-description#523 (1 comment by @sebastiankb)
-
WIP: Rewrote all parts related to JSON-LD II w3c/wot-thing-description#513 (1 comment by @sebastiankb)
-
Allow MultiLanguage "descriptions" in SecuritySchemes w3c/wot-thing-description#480 (1 comment by @mmccool)
-
w3c/wot-architecture
-
35 issues opened.
-
Fix references w3c/wot-architecture#192, by @mmccool.
-
Describe Server and Client at the section "6.2 WoT Architecture" w3c/wot-architecture#188, by @chachamimm.
-
Add a definition of Proxy w3c/wot-architecture#182, by @mmccool.
-
Legacy adaption w3c/wot-architecture#181, by @mmccool.
-
Section 6.2 seems Redundant (System Configuration) w3c/wot-architecture#180, by @mmccool.
-
Mark Example Sequences section as non-normative, fix diagrams w3c/wot-architecture#178, by @mmccool.
-
Align terminology and improve english wording in section 9 w3c/wot-architecture#175, by @mlagally.
-
Make Interaction affordances normative? w3c/wot-architecture#174, by @mlagally.
-
Use "Exposed Thing" and "Consumed Thing" consistently w3c/wot-architecture#171, by @mmccool.
-
Clarify requirement in section 5.1.10 w3c/wot-architecture#166, by @mlagally.
-
Fix component diagrams in section 6 w3c/wot-architecture#165, by @mlagally.
-
Resolve Editor Notes w3c/wot-architecture#164, by @mlagally.
-
Editorial work w3c/wot-architecture#153, by @mlagally.
-
Explain scripting runtime in section 8 Servient Implementation w3c/wot-architecture#152, by @mlagally.
-
Review/Update section 8.10 Inter Connection of Servients w3c/wot-architecture#151, by @mlagally.
-
Describe WoT Server and WoT Client at the beginning of section "6. WoT Architecture" w3c/wot-architecture#149, by @ashimura.
-
draft text for chapter 7.4 WoT Security and Privacy Guidelines w3c/wot-architecture#148, by @mlagally.
-
Don't enforce server paradigm on devices w3c/wot-architecture#146, by @mlagally.
-
Thing directories w3c/wot-architecture#144, by @mlagally.
-
Accessibility w3c/wot-architecture#142, by @mkovatsc.
-
Create change history w3c/wot-architecture#141, by @mlagally.
-
Support Patterns without Local Proxies w3c/wot-architecture#134, by @mmccool.
-
Define "Web Technology" and target protocols w3c/wot-architecture#133, by @mmccool.
-
Clarify WoT Runtime vs other known runtimes w3c/wot-architecture#130, by @zolkis.
-
Create Architecture explanation document w3c/wot-architecture#117, by @mlagally.
-
Cleanup security and privacy guidelines chapter 10 w3c/wot-architecture#116, by @mlagally.
-
Move definition of "Runtime" from section 8 to section 7. w3c/wot-architecture#114, by @mlagally.
-
Realign "Abstract" and "Introduction" sections w3c/wot-architecture#113, by @mlagally.
-
Chapter 4.1.1: needs text for consumer application domain w3c/wot-architecture#112, by @mlagally.
-
Create text for chapter "8.1.1 Native" w3c/wot-architecture#111, by @mlagally.
-
Rewrite chapter 7.5 Interconnection of servients and move to chapter "9 WoT Deployments" w3c/wot-architecture#110, by @mlagally.
-
Revise / Align chapter 8 with chapter 6 Wot Architecture w3c/wot-architecture#109, by @mlagally.
-
Short description of iot.schema.org for section 7.1. w3c/wot-architecture#108, by @mlagally.
-
Rewrite Section 4.2.4 Gateways w3c/wot-architecture#107, by @mlagally.
-
Rewrite section "4.2.3 Remote Access" w3c/wot-architecture#106, by @mlagally.
-
-
38 issues closed.
-
Create change history w3c/wot-architecture#141.
-
Provide more information of the "Thing Directory" w3c/wot-architecture#47.
-
Replace the figure of the Building Blocks w3c/wot-architecture#88.
-
Review/Update section 8.10 Inter Connection of Servients w3c/wot-architecture#151.
-
Rewrite chapter 7.5 Interconnection of servients and move to chapter "9 WoT Deployments" w3c/wot-architecture#110.
-
Cleanup security and privacy guidelines chapter 10 w3c/wot-architecture#116.
-
Create Architecture explanation document w3c/wot-architecture#117.
-
Describe WoT Server and WoT Client at the beginning of section "6. WoT Architecture" w3c/wot-architecture#149.
-
Explain scripting runtime in section 8 Servient Implementation w3c/wot-architecture#152.
-
Short description of iot.schema.org for section 7.1. w3c/wot-architecture#108.
-
Thing directories w3c/wot-architecture#144.
-
Propose draft text for 7.4 WoT Security and Privacy Guidelines w3c/wot-architecture#78.
-
Revise / Align chapter 8 with chapter 6 Wot Architecture w3c/wot-architecture#109.
-
Clarify WoT Runtime vs other known runtimes w3c/wot-architecture#130.
-
draft text for chapter 7.4 WoT Security and Privacy Guidelines w3c/wot-architecture#148.
-
Accessibility w3c/wot-architecture#142.
-
Industrial Section: Image sources needed w3c/wot-architecture#100.
-
Realign "Abstract" and "Introduction" sections w3c/wot-architecture#113.
-
Chapter 4.1.1: needs text for consumer application domain w3c/wot-architecture#112.
-
Create text for chapter "8.1.1 Native" w3c/wot-architecture#111.
-
Rewrite Section 4.2.4 Gateways w3c/wot-architecture#107.
-
Rewrite section "4.2.3 Remote Access" w3c/wot-architecture#106.
-
Thing Description in High-level architecture w3c/wot-architecture#86.
-
Refine Terminology for WoT Runtime w3c/wot-architecture#83.
-
Propose draft text for section 7.3 WoT Scripting API w3c/wot-architecture#77.
-
Propose draft text for chapters 6.1 and 6.2 w3c/wot-architecture#76.
-
Terminology w3c/wot-architecture#35.
-
Motivate for Interaction model, media types etc in Functional Requirements - Common Principles w3c/wot-architecture#75.
-
Break down proxy scenarios w3c/wot-architecture#74.
-
Mention Security also as a building block w3c/wot-architecture#72.
-
A Thing may be the abstraction of more than one entity. w3c/wot-architecture#60.
-
Hyperlinks to terms w3c/wot-architecture#85.
-
Use the term "Twin" instead of "proxy" w3c/wot-architecture#98.
-
new common pattern: multiple devices with multiple clouds w3c/wot-architecture#99.
-
Move definition of "Runtime" from section 8 to section 7. w3c/wot-architecture#114.
-
Clear definition about Properties, Actions, and Events w3c/wot-architecture#51.
-
Wrap up Burlingame F2F Plugfest and Terminology "Servient" w3c/wot-architecture#46.
-
Respec - Various normative references in informative sections w3c/wot-architecture#91.
-
-
36 issues received 98 new comments.
-
Clarify WoT Runtime vs other known runtimes w3c/wot-architecture#130 (28 comments by @mkovatsc, @mlagally, @mmccool, @zolkis)
-
Use "Exposed Thing" and "Consumed Thing" consistently w3c/wot-architecture#171 (9 comments by @mlagally, @mmccool, @zolkis)
-
Replace the figure of the Building Blocks w3c/wot-architecture#88 (5 comments by @mkovatsc, @mlagally, @mmccool)
-
Create Architecture explanation document w3c/wot-architecture#117 (4 comments by @mkovatsc, @mlagally)
-
Don't enforce server paradigm on devices w3c/wot-architecture#146 (3 comments by @mlagally, @mmccool)
-
Mention Security also as a building block w3c/wot-architecture#72 (3 comments by @mkovatsc, @mlagally)
-
Mark Example Sequences section as non-normative, fix diagrams w3c/wot-architecture#178 (2 comments by @mmccool)
-
Align terminology and improve english wording in section 9 w3c/wot-architecture#175 (2 comments by @mmccool)
-
Short description of iot.schema.org for section 7.1. w3c/wot-architecture#108 (2 comments by @mkovatsc, @mmccool)
-
Rewrite chapter 7.5 Interconnection of servients and move to chapter "9 WoT Deployments" w3c/wot-architecture#110 (2 comments by @mlagally)
-
Describe WoT Server and WoT Client at the beginning of section "6. WoT Architecture" w3c/wot-architecture#149 (2 comments by @mlagally)
-
Define "Web Technology" and target protocols w3c/wot-architecture#133 (2 comments by @mlagally, @mmccool)
-
new common pattern: multiple devices with multiple clouds w3c/wot-architecture#99 (2 comments by @mlagally)
-
Respec - Various normative references in informative sections w3c/wot-architecture#91 (2 comments by @k-toumura, @mlagally)
-
Explain scripting runtime in section 8 Servient Implementation w3c/wot-architecture#152 (1 comment by @mmccool)
-
Review/Update section 8.10 Inter Connection of Servients w3c/wot-architecture#151 (1 comment by @mlagally)
-
Chapter 4.1.1: needs text for consumer application domain w3c/wot-architecture#112 (1 comment by @ToruKawaguchi)
-
Move definition of "Runtime" from section 8 to section 7. w3c/wot-architecture#114 (1 comment by @mlagally)
-
Clear definition about Properties, Actions, and Events w3c/wot-architecture#51 (1 comment by @mlagally)
-
-
58 pull requests opened.
-
Fix references to unpublished security drafts and TAG TD spec w3c/wot-architecture#193, by @mmccool.
-
Fix security references for TAG review w3c/wot-architecture#191, by @mmccool.
-
Fixed a link in security_and_privacy.md to point to the TD repository. w3c/wot-architecture#190, by @takuki.
-
Revise Section 11 (now Appendix A) Example Sequences to use consistent terminology w3c/wot-architecture#189, by @mmccool.
-
WIP: Sync TAG-review updates back into master w3c/wot-architecture#187, by @mmccool.
-
WIP: Resynch TAG-review branch with master w3c/wot-architecture#186, by @mmccool.
-
Updates to Security and Privacy Questionnaire w3c/wot-architecture#185, by @mmccool.
-
Updates to Security and Privacy Questionnaire w3c/wot-architecture#184, by @mmccool.
-
Fix scripting API link in TAG message w3c/wot-architecture#183, by @mmccool.
-
WIP: fixing respec, sections, ... w3c/wot-architecture#179, by @mlagally.
-
Cleanup TAG review request w3c/wot-architecture#177, by @mlagally.
-
Clean up/expand section 9, fix ExposedThing/ConsumedThing, terminology fixes, spell check w3c/wot-architecture#176, by @mmccool.
-
Issues 146, 164, 165, 166 w3c/wot-architecture#173, by @mlagally.
-
TAG submission documents w3c/wot-architecture#172, by @mmccool.
-
Cleanup in Section 7 and 8 (WoT BB and Servient Impl) w3c/wot-architecture#170, by @mmccool.
-
Editorial 4 w3c/wot-architecture#169, by @mlagally.
-
WIP: editorial fixes-4 w3c/wot-architecture#168, by @mlagally.
-
Issue #110, #151, #47 w3c/wot-architecture#167, by @mryuichi.
-
Clean up Security Considerations section (#116) w3c/wot-architecture#163, by @mmccool.
-
Remove Section 6.1 Overview w3c/wot-architecture#162, by @mryuichi.
-
Issue #110, #151, #47 w3c/wot-architecture#161, by @mryuichi.
-
Add references to some useful ontologies (#108) w3c/wot-architecture#160, by @mmccool.
-
Clean up figures and explanations in section 7 (Building Blocks) and 8 (Servient Implementation) (#152) w3c/wot-architecture#159, by @mmccool.
-
Issue 149 - chapter 6 with client, server and servient w3c/wot-architecture#158, by @mlagally.
-
Correct and add Scripting related content. Fix some of the whitespace… w3c/wot-architecture#157, by @zolkis.
-
'edge' is missing w3c/wot-architecture#156, by @sebastiankb.
-
Update figures in High-Level Architecture section w3c/wot-architecture#155, by @k-toumura.
-
Revised figures w3c/wot-architecture#154, by @mmccool.
-
Solve source problem of the Smart Factory Image w3c/wot-architecture#150, by @sebastiankb.
-
Add text on accessibility w3c/wot-architecture#147, by @mkovatsc.
-
Editorial cleanup 3 w3c/wot-architecture#145, by @mlagally.
-
Runtime/Building Block/Servient Implementation Refinements w3c/wot-architecture#143, by @mmccool.
-
Architecture Explainer: Compress intro and goals/non-goals w3c/wot-architecture#140, by @mkovatsc.
-
ABANDONED: Security Considerations w3c/wot-architecture#139, by @mmccool.
-
Remove TD-specific content from explainer w3c/wot-architecture#138, by @mmccool.
-
Update Smart Factory Use Case w3c/wot-architecture#137, by @sebastiankb.
-
Editorial 2 w3c/wot-architecture#136, by @mlagally.
-
Editorial cleanup 1 w3c/wot-architecture#135, by @mlagally.
-
Replaced the figure in section 4.3 summary w3c/wot-architecture#132, by @mryuichi.
-
[Editorial] fix for Use Case section w3c/wot-architecture#131, by @k-toumura.
-
Explainer Cleanup w3c/wot-architecture#129, by @mmccool.
-
Add '8.1.1 Native' w3c/wot-architecture#128, by @k-toumura.
-
make the diagram style more consistent. w3c/wot-architecture#127, by @k-toumura.
-
Issue106 107 w3c/wot-architecture#126, by @mlagally.
-
Explainer Updates w3c/wot-architecture#125, by @mmccool.
-
Added Smart Home as Consumer use case w3c/wot-architecture#124, by @ToruKawaguchi.
-
Update index.html w3c/wot-architecture#123, by @mlagally.
-
rewrite of chapter 4.1: Application Domains w3c/wot-architecture#121, by @mlagally.
-
Explainer: Application scenarios and use cases w3c/wot-architecture#120, by @mlagally.
-
Explainer - Building Blocks Section w3c/wot-architecture#119, by @mmccool.
-
Issue 113 realign abstract and introduction sections w3c/wot-architecture#118, by @mlagally.
-
fixing terminology section w3c/wot-architecture#115, by @mlagally.
-
Issue 99 multiple device cloud pattern w3c/wot-architecture#105, by @mlagally.
-
Issue 98: use "digital twin" instead of "proxy" w3c/wot-architecture#104, by @mlagally.
-
Add conformance section w3c/wot-architecture#103, by @k-toumura.
-
Update section 3.2 common patterns again (#96) w3c/wot-architecture#102, by @mryuichi.
-
Revised WoT Building Blocks section w3c/wot-architecture#101, by @mmccool.
-
-
49 pull requests merged.
-
Fix references to unpublished security drafts and TAG TD spec w3c/wot-architecture#193.
-
Fixed a link in security_and_privacy.md to point to the TD repository. w3c/wot-architecture#190.
-
Updates to Security and Privacy Questionnaire w3c/wot-architecture#185.
-
Fix scripting API link in TAG message w3c/wot-architecture#183.
-
Cleanup TAG review request w3c/wot-architecture#177.
-
Clean up/expand section 9, fix ExposedThing/ConsumedThing, terminology fixes, spell check w3c/wot-architecture#176.
-
TAG submission documents w3c/wot-architecture#172.
-
Issues 146, 164, 165, 166 w3c/wot-architecture#173.
-
Cleanup in Section 7 and 8 (WoT BB and Servient Impl) w3c/wot-architecture#170.
-
Editorial 4 w3c/wot-architecture#169.
-
Issue #110, #151, #47 w3c/wot-architecture#167.
-
Issue 149 - chapter 6 with client, server and servient w3c/wot-architecture#158.
-
Clean up Security Considerations section (#116) w3c/wot-architecture#163.
-
Correct and add Scripting related content. Fix some of the whitespace… w3c/wot-architecture#157.
-
Clean up figures and explanations in section 7 (Building Blocks) and 8 (Servient Implementation) (#152) w3c/wot-architecture#159.
-
Add references to some useful ontologies (#108) w3c/wot-architecture#160.
-
Update figures in High-Level Architecture section w3c/wot-architecture#155.
-
Editorial cleanup 3 w3c/wot-architecture#145.
-
'edge' is missing w3c/wot-architecture#156.
-
Revised figures w3c/wot-architecture#154.
-
Architecture Explainer: Compress intro and goals/non-goals w3c/wot-architecture#140.
-
Solve source problem of the Smart Factory Image w3c/wot-architecture#150.
-
Runtime/Building Block/Servient Implementation Refinements w3c/wot-architecture#143.
-
Add text on accessibility w3c/wot-architecture#147.
-
Update Smart Factory Use Case w3c/wot-architecture#137.
-
Remove TD-specific content from explainer w3c/wot-architecture#138.
-
Editorial 2 w3c/wot-architecture#136.
-
Issue106 107 w3c/wot-architecture#126.
-
Revised WoT Building Blocks section w3c/wot-architecture#101.
-
Editorial cleanup 1 w3c/wot-architecture#135.
-
Replaced the figure in section 4.3 summary w3c/wot-architecture#132.
-
fixing terminology section w3c/wot-architecture#115.
-
Clarify the definition of InteractionAffordance per discussion in TD TF. w3c/wot-architecture#92.
-
[Editorial] fix for Use Case section w3c/wot-architecture#131.
-
Issue 113 realign abstract and introduction sections w3c/wot-architecture#118.
-
Explainer Cleanup w3c/wot-architecture#129.
-
rewrite of chapter 4.1: Application Domains w3c/wot-architecture#121.
-
Added Smart Home as Consumer use case w3c/wot-architecture#124.
-
Add '8.1.1 Native' w3c/wot-architecture#128.
-
make the diagram style more consistent. w3c/wot-architecture#127.
-
Explainer Updates w3c/wot-architecture#125.
-
Update index.html w3c/wot-architecture#123.
-
Explainer w3c/wot-architecture#122.
-
Explainer: Application scenarios and use cases w3c/wot-architecture#120.
-
Explainer - Building Blocks Section w3c/wot-architecture#119.
-
Issue 98: use "digital twin" instead of "proxy" w3c/wot-architecture#104.
-
Update section 3.2 common patterns again (#96) w3c/wot-architecture#102.
-
Issue 99 multiple device cloud pattern w3c/wot-architecture#105.
-
Add conformance section w3c/wot-architecture#103.
-
-
10 pull requests closed.
-
Fix security references for TAG review w3c/wot-architecture#191.
-
WIP: Resynch TAG-review branch with master w3c/wot-architecture#186.
-
Updates to Security and Privacy Questionnaire w3c/wot-architecture#184.
-
WIP: fixing respec, sections, ... w3c/wot-architecture#179.
-
WIP: editorial fixes-4 w3c/wot-architecture#168.
-
Issue #110, #151, #47 w3c/wot-architecture#161.
-
Remove Section 6.1 Overview w3c/wot-architecture#162.
-
ABANDONED: Security Considerations w3c/wot-architecture#139.
-
Replace the figure of "3.3 use case summary" w3c/wot-architecture#95.
-
Update 3.2 common patterns w3c/wot-architecture#96.
-
-
1 pull request reopened.
-
Issue #110, #151, #47 w3c/wot-architecture#167, by @mryuichi.
-
-
26 pull requests received 137 new comments.
-
Revised WoT Building Blocks section w3c/wot-architecture#101 (17 comments by @mlagally, @mmccool, @mryuichi)
-
Clean up/expand section 9, fix ExposedThing/ConsumedThing, terminology fixes, spell check w3c/wot-architecture#176 (12 comments by @mlagally, @mmccool)
-
Architecture Explainer: Compress intro and goals/non-goals w3c/wot-architecture#140 (11 comments by @mkovatsc, @mlagally, @mmccool, @zolkis)
-
Clarify the definition of InteractionAffordance per discussion in TD TF. w3c/wot-architecture#92 (10 comments by @k-toumura, @mjkoster, @mkovatsc, @mlagally, @takuki, @vcharpenay)
-
Updates to Security and Privacy Questionnaire w3c/wot-architecture#185 (9 comments by @mmccool, @takuki)
-
Runtime/Building Block/Servient Implementation Refinements w3c/wot-architecture#143 (8 comments by @mlagally, @mmccool, @zolkis)
-
fixing terminology section w3c/wot-architecture#115 (6 comments by @k-toumura, @mlagally, @mryuichi, @takuki)
-
non-obtrusive style for dfn links, and some link related corrections. w3c/wot-architecture#89 (3 comments by @k-toumura, @mlagally)
-
Correct and add Scripting related content. Fix some of the whitespace… w3c/wot-architecture#157 (2 comments by @mmccool)
-
Replace the figure of "3.3 use case summary" w3c/wot-architecture#95 (2 comments by @mlagally, @mryuichi)
-
Added Smart Home as Consumer use case w3c/wot-architecture#124 (2 comments by @mlagally, @ToruKawaguchi)
-
Fixed a link in security_and_privacy.md to point to the TD repository. w3c/wot-architecture#190 (1 comment by @mmccool)
-
Clean up figures and explanations in section 7 (Building Blocks) and 8 (Servient Implementation) (#152) w3c/wot-architecture#159 (1 comment by @mmccool)
w3c/wot-security-best-practices
-
1 issue opened.
-
Add a best practice description on logging security events w3c/wot-security-best-practices#3, by @ereshetova.
-
-
1 pull request merged.
-
WIP: Flesh out point-form and empty sections w3c/wot-security-best-practices#2.
-
w3c/wot-scripting-api
-
1 issue opened.
-
typescript definitions: Items should not be required in an ArraySchema w3c/wot-scripting-api#163, by @hasbel.
-
-
1 issue received 1 new comment.
-
typescript definitions: Items should not be required in an ArraySchema w3c/wot-scripting-api#163 (1 comment by @danielpeintner)
-
-
1 pull request merged.
-
Revise scripting use cases and terminology. w3c/wot-scripting-api#161.
-
-
2 pull requests received 2 new comments.
GitHub
w3c/wot-thing-description
-
28 issues opened.
-
names in Thing level should be MultiLanguage and not mandatory w3c/wot-thing-description#464, by @egekorkan.
-
base URI definition in Thing class is a bit confusing w3c/wot-thing-description#454, by @takuki.
-
Example1, Example2 and Example35 contain validation errors w3c/wot-thing-description#448, by @mlagally.
-
JSON Schema too strict on @context contents w3c/wot-thing-description#447, by @mlagally.
-
7.2 Transformation to JSON-LD & RDF seems unnecessary w3c/wot-thing-description#444, by @msporny.
-
Using "http" as a term is strange w3c/wot-thing-description#443, by @msporny.
-
JSON-LD Best Practice - Version JSON-LD Context files w3c/wot-thing-description#442, by @msporny.
-
DataSchema has DataSchema w3c/wot-thing-description#440, by @egekorkan.
-
Moving property, action, event under InteractionPattern w3c/wot-thing-description#439, by @egekorkan.
-
Could not create representation for the ontology server webservice. w3c/wot-thing-description#438, by @yamagile.
-
Assertions in section 7.1 redundant? w3c/wot-thing-description#434, by @vcharpenay.
-
Namespace IRIs need to be populated on w3.org Web server w3c/wot-thing-description#432, by @vcharpenay.
-
Vocabulary term "securityDefinitions" in TD context is missing w3c/wot-thing-description#431, by @danicic.
-
Vocabulary term "subprotocol" in TD context is missing w3c/wot-thing-description#430, by @danicic.
-
Vocabulary term "data" in TD context is missing w3c/wot-thing-description#429, by @danicic.
-
What does "convergence" mean in "Basic Representation Format Assumptions" section? w3c/wot-thing-description#426, by @takuki.
-
Link's href description talks about interaction pattern w3c/wot-thing-description#421, by @takuki.
-
ThingTemplate definition is missing in td.ttl w3c/wot-thing-description#416, by @takuki.
-
Explaining Validation Schema w3c/wot-thing-description#412, by @egekorkan.
-
Adding new subprotocols w3c/wot-thing-description#410, by @egekorkan.
-
Explaining of subprotocols w3c/wot-thing-description#409, by @egekorkan.
-
Antonym of observeproperty w3c/wot-thing-description#408, by @egekorkan.
-
[Editorial] Grouping of mandatory terms w3c/wot-thing-description#407, by @egekorkan.
-
Full JSON Schema support w3c/wot-thing-description#406, by @egekorkan.
-
op values are not explained w3c/wot-thing-description#405, by @egekorkan.
-
[ImplementationReport] numbered ids are not properly linked to the spec w3c/wot-thing-description#404, by @egekorkan.
-
rename event keywords subscription and cancellation w3c/wot-thing-description#403, by @mlagally.
-
Rename ID term td-readOnly-observable-default to td-safe-idempotent-default w3c/wot-thing-description#399, by @sebastiankb.
-
-
39 issues closed.
-
Explaining of subprotocols w3c/wot-thing-description#409.
-
JSON Schema for TD Instance Validation too permissive w3c/wot-thing-description#187.
-
TPAC resolution: Observable Properties and Events w3c/wot-thing-description#61.
-
Thing Interfaces / Thing Models w3c/wot-thing-description#279.
-
Clarify type value of "null" for properties w3c/wot-thing-description#222.
-
properties, actions and events need name **and** label field names w3c/wot-thing-description#216.
-
vendor-specific TD extensions w3c/wot-thing-description#212.
-
Model possible responses in forms w3c/wot-thing-description#250.
-
In section 5.4, CoAP, MQTT are refered. w3c/wot-thing-description#334.
-
Singular+plural terms in TD are confusing w3c/wot-thing-description#359.
-
contentType in Response w3c/wot-thing-description#363.
-
Rename 'Versioning' as 'VersionInfo' w3c/wot-thing-description#370.
-
Antonym of observeproperty w3c/wot-thing-description#408.
-
What does "convergence" mean in "Basic Representation Format Assumptions" section? w3c/wot-thing-description#426.
-
Update TD Model diagrams w3c/wot-thing-description#346.
-
Example 32 is not valid w3c/wot-thing-description#347.
-
Missing reference for Webhooks w3c/wot-thing-description#380.
-
Testing Clarifications w3c/wot-thing-description#291.
-
Assertions should be self-contained w3c/wot-thing-description#301.
-
Form contentType vs. Link type w3c/wot-thing-description#306.
-
Clarify "scope" field semantics w3c/wot-thing-description#217.
-
Inputs in Events Definition w3c/wot-thing-description#231.
-
Declarative protocol bindings in TD w3c/wot-thing-description#237.
-
WoT Security Ontology incorrectly linked w3c/wot-thing-description#257.
-
TD Events w3c/wot-thing-description#17.
-
Explaining Validation Schema w3c/wot-thing-description#412.
-
Moving property, action, event under InteractionPattern w3c/wot-thing-description#439.
-
use of scopes not clear w3c/wot-thing-description#355.
-
DataSchema has DataSchema w3c/wot-thing-description#440.
-
Core Vocabulary Definition - fix schema links w3c/wot-thing-description#211.
-
Full JSON Schema support w3c/wot-thing-description#406.
-
Form relation type values (rel) w3c/wot-thing-description#179.
-
Include JSON Schema's "anyOf", "allOf" and "not"? w3c/wot-thing-description#298.
-
Namespaces: clarify if HTTP namespace is normative w3c/wot-thing-description#210.
-
6.1 talks only about unsigned int w3c/wot-thing-description#395.
-
Vocabulary term ambiguous w3c/wot-thing-description#392.
-
td-event-response-arrays assertion is wrong w3c/wot-thing-description#365.
-
TD Event in Thing-to-Thing interactions w3c/wot-thing-description#333.
-
confused in using JSON-LD w3c/wot-thing-description#335.
-
-
72 issues received 176 new comments.
-
Vocabulary change: InteractionPattern to Affordance w3c/wot-thing-description#282 (25 comments by @mkovatsc, @mlagally, @sebastiankb, @takuki, @vcharpenay)
-
Identifiers for Properties, Actions, Events w3c/wot-thing-description#292 (11 comments by @egekorkan, @mkovatsc, @mmccool, @vcharpenay)
-
Subscription and Cancellation response and request data schemas w3c/wot-thing-description#398 (9 comments by @egekorkan, @mkovatsc, @mlagally, @mmccool, @sebastiankb, @vcharpenay)
-
op values are not explained w3c/wot-thing-description#405 (5 comments by @egekorkan, @mkovatsc, @mmccool, @sebastiankb)
-
Example1, Example2 and Example35 contain validation errors w3c/wot-thing-description#448 (5 comments by @mlagally, @sebastiankb)
-
Link's href description talks about interaction pattern w3c/wot-thing-description#421 (4 comments by @sebastiankb, @vcharpenay)
-
Web Link definitions should be in an own namespaces w3c/wot-thing-description#253 (4 comments by @egekorkan, @sebastiankb, @vcharpenay)
-
7.2 Transformation to JSON-LD & RDF seems unnecessary w3c/wot-thing-description#444 (4 comments by @sebastiankb, @vcharpenay)
-
Using "http" as a term is strange w3c/wot-thing-description#443 (3 comments by @mmccool, @sebastiankb, @vcharpenay)
-
rename event keywords subscription and cancellation w3c/wot-thing-description#403 (3 comments by @egekorkan, @mkovatsc, @sebastiankb)
-
ThingTemplate definition is missing in td.ttl w3c/wot-thing-description#416 (3 comments by @mlagally, @sebastiankb, @vcharpenay)
-
use of scopes not clear w3c/wot-thing-description#355 (3 comments by @egekorkan, @mmccool, @sebastiankb)
-
uriVariable does not seem to be proper defined or example is wrong w3c/wot-thing-description#376 (3 comments by @mmccool, @sebastiankb)
-
Must be serialized as array w3c/wot-thing-description#396 (3 comments by @danielpeintner, @mkovatsc, @mmccool)
-
@context and @type are not in Information Model w3c/wot-thing-description#394 (3 comments by @mmccool, @takuki)
-
Form relation type values (rel) w3c/wot-thing-description#179 (3 comments by @mjkoster, @mkovatsc, @sebastiankb)
-
JSON Schema too strict on @context contents w3c/wot-thing-description#447 (2 comments by @egekorkan, @sebastiankb)
-
base URI definition in Thing class is a bit confusing w3c/wot-thing-description#454 (2 comments by @mkovatsc, @sebastiankb)
-
JSON Schema/Hyper-Schema compatibility goals? w3c/wot-thing-description#115 (2 comments by @handrews, @sebastiankb)
-
[ImplementationReport] numbered ids are not properly linked to the spec w3c/wot-thing-description#404 (2 comments by @egekorkan, @sebastiankb)
-
Namespace IRIs need to be populated on w3.org Web server w3c/wot-thing-description#432 (2 comments by @sebastiankb, @takuki)
-
What does "convergence" mean in "Basic Representation Format Assumptions" section? w3c/wot-thing-description#426 (2 comments by @sebastiankb)
-
Same description of `identity` field in CertSecurityScheme/PublicSecurityScheme/PSKSecurityScheme w3c/wot-thing-description#233 (2 comments by @mmccool, @sebastiankb)
-
Moving property, action, event under InteractionPattern w3c/wot-thing-description#439 (2 comments by @egekorkan, @zolkis)
-
Assertion/Schema mismatch for td-{property,event,action}-arrays w3c/wot-thing-description#321 (2 comments by @sebastiankb, @takuki)
-
items is data schema or JSON Object or array of data schema? w3c/wot-thing-description#364 (2 comments by @sebastiankb, @takuki)
-
Include JSON Schema's "anyOf", "allOf" and "not"? w3c/wot-thing-description#298 (2 comments by @egekorkan, @sebastiankb)
-
Vocabulary term "data" in TD context is missing w3c/wot-thing-description#429 (2 comments by @egekorkan, @vcharpenay)
-
TD Event in Thing-to-Thing interactions w3c/wot-thing-description#333 (2 comments by @AndreMaz, @sebastiankb)
-
JSON Schema for TD Instance Validation too permissive w3c/wot-thing-description#187 (1 comment by @egekorkan)
-
TPAC resolution: Observable Properties and Events w3c/wot-thing-description#61 (1 comment by @sebastiankb)
-
Clarify type value of "null" for properties w3c/wot-thing-description#222 (1 comment by @sebastiankb)
-
Fix links on the HTML documentation of wot-security and json-schema vocabularies w3c/wot-thing-description#287 (1 comment by @sebastiankb)
-
Could not create representation for the ontology server webservice. w3c/wot-thing-description#438 (1 comment by @sebastiankb)
-
Core Vocabulary Definition - fix schema links w3c/wot-thing-description#211 (1 comment by @sebastiankb)
-
Clarify relationship of security schemes between WoT and OpenAPI w3c/wot-thing-description#201 (1 comment by @mmccool)
-
Vocabulary term "subprotocol" in TD context is missing w3c/wot-thing-description#430 (1 comment by @vcharpenay)
-
Vocabulary term "securityDefinitions" in TD context is missing w3c/wot-thing-description#431 (1 comment by @vcharpenay)
-
-
39 pull requests opened.
-
op member in form has context-dependent enumerated values (issue #236) w3c/wot-thing-description#465, by @takuki.
-
Created Web linking module w3c/wot-thing-description#463, by @vcharpenay.
-
incorporate new Hitachi results w3c/wot-thing-description#462, by @mmccool.
-
Update test results w3c/wot-thing-description#461, by @mmccool.
-
Improving the text describing how to make a JSON schema for stricter validation (Issue #412) w3c/wot-thing-description#460, by @takuki.
-
Fixed a phrase in the first paragraph of in section 6.1 (Issue #426) w3c/wot-thing-description#459, by @takuki.
-
Moving property, action, event under InteractionAffordance (for issue #439) w3c/wot-thing-description#458, by @takuki.
-
Fixed a label for "names" in td.ttl (related to PR #451) w3c/wot-thing-description#457, by @takuki.
-
Further clarified the explanation about the items in the "@context" array w3c/wot-thing-description#456, by @takuki.
-
Clarified JSON number representation used for representing integers. w3c/wot-thing-description#455, by @takuki.
-
Some small changes reflecting comments received during the 2/15 TD call. w3c/wot-thing-description#453, by @takuki.
-
Added an explanation about the items in the @context array w3c/wot-thing-description#452, by @takuki.
-
Fixed bug in displaying 'descriptions' (Section 5) w3c/wot-thing-description#451, by @vcharpenay.
-
Recovered missing @type term in InteractionAffordance. w3c/wot-thing-description#450, by @takuki.
-
Fix syntax errors in several examples w3c/wot-thing-description#449, by @mlagally.
-
Split the @context assertion into two as discussed in TD telecon. w3c/wot-thing-description#446, by @takuki.
-
Added 'map of' assertions w3c/wot-thing-description#445, by @vcharpenay.
-
Fixed a typo ("deceleration" changed to "declaration") w3c/wot-thing-description#441, by @takuki.
-
Mark and Define Maps w3c/wot-thing-description#437, by @mmccool.
-
Remove td-unique-identifiers assertion w3c/wot-thing-description#436, by @mmccool.
-
WIP: Modified assertions on @context w3c/wot-thing-description#435, by @vcharpenay.
-
Updated test results adding new @context assertions w3c/wot-thing-description#433, by @mmccool.
-
Mentioned the use of content negotiation (for issue #359) w3c/wot-thing-description#428, by @takuki.
-
Described default values for @context (for issue #394) w3c/wot-thing-description#427, by @takuki.
-
Datatype Integer serialization is specified. (for issue #395) w3c/wot-thing-description#425, by @takuki.
-
Gave definition to "vocabulary term" (for issue #392) w3c/wot-thing-description#424, by @takuki.
-
Changed the editors note in Appendix A JSON Schema for TD (#412) w3c/wot-thing-description#423, by @takuki.
-
Added @context to DataSchema and SecurityScheme w3c/wot-thing-description#422, by @takuki.
-
Repaired a bug in PR #417. w3c/wot-thing-description#420, by @takuki.
-
'Versioning' was renamed as 'VersionInfo' (#370) w3c/wot-thing-description#419, by @takuki.
-
added @context and @type in UML diagrams. w3c/wot-thing-description#418, by @takuki.
-
Added @type in Thing/InteractionPattern/DataSchema definition. w3c/wot-thing-description#417, by @takuki.
-
Added @context in Thing definition. w3c/wot-thing-description#415, by @takuki.
-
Tooling to highlight at-risk assertions w3c/wot-thing-description#414, by @mmccool.
-
Remove scopes and security at interaction level w3c/wot-thing-description#413, by @mmccool.
-
Final (mostly, probably) Princeton TestFest results w3c/wot-thing-description#411, by @mmccool.
-
update at-risk items in IR w3c/wot-thing-description#402, by @mmccool.
-
add atrisk assertions w3c/wot-thing-description#401, by @egekorkan.
-
Sort assertions in impl report by id w3c/wot-thing-description#400, by @mmccool.
-
-
37 pull requests merged.
-
op member in form has context-dependent enumerated values (issue #236) w3c/wot-thing-description#465.
-
Created Web linking module w3c/wot-thing-description#463.
-
incorporate new Hitachi results w3c/wot-thing-description#462.
-
Update test results w3c/wot-thing-description#461.
-
Improving the text describing how to make a JSON schema for stricter validation (Issue #412) w3c/wot-thing-description#460.
-
Fixed a phrase in the first paragraph of in section 6.1 (Issue #426) w3c/wot-thing-description#459.
-
Moving property, action, event under InteractionAffordance (for issue #439) w3c/wot-thing-description#458.
-
Fixed a label for "names" in td.ttl (related to PR #451) w3c/wot-thing-description#457.
-
Fixed bug in displaying 'descriptions' (Section 5) w3c/wot-thing-description#451.
-
Further clarified the explanation about the items in the "@context" array w3c/wot-thing-description#456.
-
Clarified JSON number representation used for representing integers. w3c/wot-thing-description#455.
-
Some small changes reflecting comments received during the 2/15 TD call. w3c/wot-thing-description#453.
-
Added an explanation about the items in the @context array w3c/wot-thing-description#452.
-
Recovered missing @type term in InteractionAffordance. w3c/wot-thing-description#450.
-
Split the @context assertion into two as discussed in TD telecon. w3c/wot-thing-description#446.
-
Added 'map of' assertions w3c/wot-thing-description#445.
-
WIP: Modified assertions on @context w3c/wot-thing-description#435.
-
Fixed a typo ("deceleration" changed to "declaration") w3c/wot-thing-description#441.
-
Updated test results adding new @context assertions w3c/wot-thing-description#433.
-
WIP: JSON-LD transformation w3c/wot-thing-description#368.
-
Mentioned the use of content negotiation (for issue #359) w3c/wot-thing-description#428.
-
Described default values for @context (for issue #394) w3c/wot-thing-description#427.
-
Datatype Integer serialization is specified. (for issue #395) w3c/wot-thing-description#425.
-
Gave definition to "vocabulary term" (for issue #392) w3c/wot-thing-description#424.
-
Changed the editors note in Appendix A JSON Schema for TD (#412) w3c/wot-thing-description#423.
-
Added @context to DataSchema and SecurityScheme w3c/wot-thing-description#422.
-
Remove scopes and security at interaction level w3c/wot-thing-description#413.
-
Tooling to highlight at-risk assertions w3c/wot-thing-description#414.
-
Repaired a bug in PR #417. w3c/wot-thing-description#420.
-
'Versioning' was renamed as 'VersionInfo' (#370) w3c/wot-thing-description#419.
-
added @context and @type in UML diagrams. w3c/wot-thing-description#418.
-
Added @type in Thing/InteractionPattern/DataSchema definition. w3c/wot-thing-description#417.
-
Added @context in Thing definition. w3c/wot-thing-description#415.
-
Final (mostly, probably) Princeton TestFest results w3c/wot-thing-description#411.
-
update at-risk items in IR w3c/wot-thing-description#402.
-
add atrisk assertions w3c/wot-thing-description#401.
-
Sort assertions in impl report by id w3c/wot-thing-description#400.
-
-
1 pull request closed.
-
Mark and Define Maps w3c/wot-thing-description#437.
-
-
1 pull request reopened.
-
Fix syntax errors in several examples w3c/wot-thing-description#449, by @sebastiankb.
-
-
8 pull requests received 20 new comments.
-
WIP: Modified assertions on @context w3c/wot-thing-description#435 (6 comments by @mmccool, @takuki, @vcharpenay)
-
Remove td-unique-identifiers assertion w3c/wot-thing-description#436 (3 comments by @mmccool, @sebastiankb)
-
Fix syntax errors in several examples w3c/wot-thing-description#449 (2 comments by @sebastiankb, @vcharpenay)
-
Clarified JSON number representation used for representing integers. w3c/wot-thing-description#455 (1 comment by @takuki)
-
Remove scopes and security at interaction level w3c/wot-thing-description#413 (1 comment by @mmccool)
-
w3c/wot-architecture
-
14 issues opened.
-
Industrial Section: Image sources needed w3c/wot-architecture#100, by @sebastiankb.
-
new common pattern: multiple devices with multiple clouds w3c/wot-architecture#99, by @mlagally.
-
Use the term "Twin" instead of "proxy" w3c/wot-architecture#98, by @mlagally.
-
Respec - Various normative references in informative sections w3c/wot-architecture#91, by @mlagally.
-
Replace the figure of the Building Blocks w3c/wot-architecture#88, by @mryuichi.
-
Thing Description in High-level architecture w3c/wot-architecture#86, by @k-toumura.
-
Hyperlinks to terms w3c/wot-architecture#85, by @k-toumura.
-
Refine Terminology for WoT Runtime w3c/wot-architecture#83, by @mmccool.
-
Propose draft text for 7.4 WoT Security and Privacy Guidelines w3c/wot-architecture#78, by @mlagally.
-
Propose draft text for section 7.3 WoT Scripting API w3c/wot-architecture#77, by @mlagally.
-
Propose draft text for chapters 6.1 and 6.2 w3c/wot-architecture#76, by @mlagally.
-
Motivate for Interaction model, media types etc in Functional Requirements - Common Principles w3c/wot-architecture#75, by @mlagally.
-
Break down proxy scenarios w3c/wot-architecture#74, by @mlagally.
-
Mention Security also as a building block w3c/wot-architecture#72, by @sebastiankb.
-
-
7 issues closed.
-
Write .md for Identity Management w3c/wot-architecture#50.
-
Working Draft for Prague PlugFest w3c/wot-architecture#49.
-
Terminology for "Semantics" w3c/wot-architecture#45.
-
Beginner Terms w3c/wot-architecture#44.
-
Thing proxies w3c/wot-architecture#26.
-
Grammatical issue in "ConsumedThing interface" description in the section "WoT Scripting API" w3c/wot-architecture#61.
-
Grammatical issue in the first para in the section "7.1 WoT Client" w3c/wot-architecture#62.
-
-
23 issues received 40 new comments.
-
Hyperlinks to terms w3c/wot-architecture#85 (5 comments by @k-toumura, @mkovatsc, @mlagally, @takuki)
-
Thing Description in High-level architecture w3c/wot-architecture#86 (4 comments by @mkovatsc, @mlagally)
-
Mention Security also as a building block w3c/wot-architecture#72 (4 comments by @mkovatsc, @mlagally)
-
Clear definition about Properties, Actions, and Events w3c/wot-architecture#51 (3 comments by @mkovatsc, @mlagally, @sebastiankb)
-
Replace the figure of the Building Blocks w3c/wot-architecture#88 (2 comments by @mlagally, @mryuichi)
-
Propose draft text for section 7.3 WoT Scripting API w3c/wot-architecture#77 (1 comment by @mkovatsc)
-
A Thing may be the abstraction of more than one entity. w3c/wot-architecture#60 (1 comment by @mlagally)
-
Propose draft text for 7.4 WoT Security and Privacy Guidelines w3c/wot-architecture#78 (1 comment by @mlagally)
-
Wrap up Burlingame F2F Plugfest and Terminology "Servient" w3c/wot-architecture#46 (1 comment by @mlagally)
-
Grammatical issue in "ConsumedThing interface" description in the section "WoT Scripting API" w3c/wot-architecture#61 (1 comment by @mlagally)
-
Grammatical issue in the first para in the section "7.1 WoT Client" w3c/wot-architecture#62 (1 comment by @mlagally)
-
-
16 pull requests opened.
-
Upload PPT for figures of architecture w3c/wot-architecture#97, by @mryuichi.
-
Update 3.2 common patterns w3c/wot-architecture#96, by @mryuichi.
-
Replace the figure of "3.3 use case summary" w3c/wot-architecture#95, by @mryuichi.
-
Add 6.5 Inter connection of servients w3c/wot-architecture#94, by @mryuichi.
-
Replace the figure of the Building Blocks w3c/wot-architecture#93, by @mryuichi.
-
Clarify the definition of InteractionAffordance per discussion in TD TF. w3c/wot-architecture#92, by @takuki.
-
Adding Scalability and Interoperability requirements w3c/wot-architecture#90, by @mlagally.
-
non-obtrusive style for dfn links, and some link related corrections. w3c/wot-architecture#89, by @k-toumura.
-
Issue86 new figures w3c/wot-architecture#87, by @mlagally.
-
Restructure 13 2 w3c/wot-architecture#84, by @mlagally.
-
add PPTX file for cross-domain use case figures w3c/wot-architecture#82, by @k-toumura.
-
Updated common pattern figures - new section on digital twin w3c/wot-architecture#81, by @mlagally.
-
Recover references to figure w3c/wot-architecture#80, by @k-toumura.
-
Merging "Restructure" branch to main branch w3c/wot-architecture#79, by @mlagally.
-
Merge fixes from Princeton F2F session w3c/wot-architecture#73, by @mkovatsc.
-
Restructure w3c/wot-architecture#71, by @mkovatsc.
-
-
18 pull requests merged.
-
Add 6.5 Inter connection of servients w3c/wot-architecture#94.
-
Replace the figure of the Building Blocks w3c/wot-architecture#93.
-
Adding Scalability and Interoperability requirements w3c/wot-architecture#90.
-
non-obtrusive style for dfn links, and some link related corrections. w3c/wot-architecture#89.
-
Issue86 new figures w3c/wot-architecture#87.
-
Upload PPT for figures of architecture w3c/wot-architecture#97.
-
Restructure 13 2 w3c/wot-architecture#84.
-
Recover references to figure w3c/wot-architecture#80.
-
add PPTX file for cross-domain use case figures w3c/wot-architecture#82.
-
Imported terminology to index.html w3c/wot-architecture#66.
-
Add cross-domain collaboration use case. w3c/wot-architecture#65.
-
Added proposal/requirements to index.html as new chapter for review by editors w3c/wot-architecture#64.
-
Strawman merging all PRs until 23.1.2019 w3c/wot-architecture#59.
-
Adding WoT runtime risks to S&P section w3c/wot-architecture#63.
-
Editorial fixes w3c/wot-architecture#56.
-
Merging "Restructure" branch to main branch w3c/wot-architecture#79.
-
Merge fixes from Princeton F2F session w3c/wot-architecture#73.
-
Restructure w3c/wot-architecture#71.
-
-
2 pull requests closed.
-
Updated common pattern figures - new section on digital twin w3c/wot-architecture#81.
-
a spelling mistake w3c/wot-architecture#57.
-
-
10 pull requests received 14 new comments.
-
Updated common pattern figures - new section on digital twin w3c/wot-architecture#81 (1 comment by @mlagally)
w3c/wot-security-best-practices
-
1 pull request opened.
-
WIP: Flesh out point-form and empty sections w3c/wot-security-best-practices#2, by @mmccool.
-
w3c/wot-scripting-api
-
1 issue opened.
-
Exclude fetch specification from Scripting API w3c/wot-scripting-api#162, by @danielpeintner.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Revise scripting use cases and terminology. w3c/wot-scripting-api#161, by @zolkis.
-
Reorganize the Security section w3c/wot-scripting-api#160, by @zolkis.
-
-
2 pull requests merged.
-
Reorganize the Security section w3c/wot-scripting-api#160.
-
Rewriting S&P section without normative statements w3c/wot-scripting-api#155.
-
-
2 pull requests received 10 new comments.
-
Rewriting S&P section without normative statements w3c/wot-scripting-api#155 (7 comments by @ereshetova, @zolkis)
-
w3c/wot-security-testing-plan
-
1 pull request opened.
-
Update to ITU vocab, add summary w3c/wot-security-testing-plan#6, by @mmccool.
-
-
1 pull request merged.
-
Update to ITU vocab, add summary w3c/wot-security-testing-plan#6.
-
w3c/wot-security
-
1 issue opened.
-
Update terminology in testing plan to be consistent with ITU terminology w3c/wot-security#124, by @mmccool.
-
-
1 issue received 1 new comment.
-
Update terminology in testing plan to be consistent with ITU terminology w3c/wot-security#124 (1 comment by @mmccool)
-
Participants
-
1 organization left.
-
Media Access Australia left.
-
GitHub
w3c/wot-thing-description
-
32 issues opened.
-
Subscription and Cancellation response and request data schemas w3c/wot-thing-description#398, by @egekorkan.
-
Must be serialized as array w3c/wot-thing-description#396, by @egekorkan.
-
6.1 talks only about unsigned int w3c/wot-thing-description#395, by @egekorkan.
-
@context and @type are not in Information Model w3c/wot-thing-description#394, by @egekorkan.
-
Model has no formal ground w3c/wot-thing-description#393, by @egekorkan.
-
Vocabulary term ambiguous w3c/wot-thing-description#392, by @egekorkan.
-
Testing "type = array of X" assertions w3c/wot-thing-description#388, by @egekorkan.
-
parent and child assertions w3c/wot-thing-description#387, by @egekorkan.
-
Default values for op w3c/wot-thing-description#386, by @egekorkan.
-
[Editorial] Introduction paragraph 3, not-clear mention of "simple" w3c/wot-thing-description#385, by @egekorkan.
-
[Editorial] Links to serialization examples from the vocabulary w3c/wot-thing-description#384, by @egekorkan.
-
[question] Forms without href if base is defined w3c/wot-thing-description#383, by @egekorkan.
-
Missing reference for Webhooks w3c/wot-thing-description#380, by @takuki.
-
No "deceleration" in example 30 w3c/wot-thing-description#378, by @takuki.
-
id renaming w3c/wot-thing-description#377, by @sebastiankb.
-
uriVariable does not seem to be proper defined or example is wrong w3c/wot-thing-description#376, by @danielpeintner.
-
Rename 'Versioning' as 'VersionInfo' w3c/wot-thing-description#370, by @vcharpenay.
-
security assertion missing w3c/wot-thing-description#367, by @egekorkan.
-
td-event-response-arrays assertion is wrong w3c/wot-thing-description#365, by @egekorkan.
-
items is data schema or JSON Object or array of data schema? w3c/wot-thing-description#364, by @egekorkan.
-
contentType in Response w3c/wot-thing-description#363, by @egekorkan.
-
Singular+plural terms in TD are confusing w3c/wot-thing-description#359, by @zolkis.
-
use of scopes not clear w3c/wot-thing-description#355, by @egekorkan.
-
Event examples are not enough w3c/wot-thing-description#351, by @egekorkan.
-
security in forms mentions lower levels w3c/wot-thing-description#350, by @egekorkan.
-
Differnt colors for <code> markup w3c/wot-thing-description#349, by @mlagally.
-
Example 32 is not valid w3c/wot-thing-description#347, by @egekorkan.
-
Update TD Model diagrams w3c/wot-thing-description#346, by @sebastiankb.
-
Map of type w3c/wot-thing-description#345, by @danielpeintner.
-
Property extending DataSchema w3c/wot-thing-description#338, by @danielpeintner.
-
Mandatory fields vs default value w3c/wot-thing-description#337, by @danielpeintner.
-
Group *similar* vocabulary terms together w3c/wot-thing-description#336, by @danielpeintner.
-
-
13 issues closed.
-
Group *similar* vocabulary terms together w3c/wot-thing-description#336.
-
Enabling Interaction History (making Actions the only way to modify state) w3c/wot-thing-description#155.
-
Typo at Appendix B ("definea") w3c/wot-thing-description#332.
-
read and write property : different payload formats w3c/wot-thing-description#238.
-
Relation ObjectSchema to DataSchema should be 0..N w3c/wot-thing-description#315.
-
Units in TD core vocabulary w3c/wot-thing-description#244.
-
Internationalization (i18n) of human-readable TD fields w3c/wot-thing-description#161.
-
contenttype for forms w3c/wot-thing-description#260.
-
support term should be a URI type w3c/wot-thing-description#310.
-
Do vocabulary terms have a JSON key representation? w3c/wot-thing-description#293.
-
Extensible metadata fields w3c/wot-thing-description#311.
-
writable vs. readOnly w3c/wot-thing-description#209.
-
Add Action attributes w3c/wot-thing-description#130.
-
-
1 issue reopened.
-
security assertion missing w3c/wot-thing-description#367, by @egekorkan.
-
-
36 issues received 85 new comments.
-
Allow "security" to include both SecurityScheme objects and declared identifiers w3c/wot-thing-description#300 (9 comments by @mmccool, @ToruKawaguchi, @vcharpenay, @zolkis)
-
Singular+plural terms in TD are confusing w3c/wot-thing-description#359 (8 comments by @egekorkan, @sebastiankb, @zolkis)
-
Mandatory fields vs default value w3c/wot-thing-description#337 (7 comments by @egekorkan, @sebastiankb, @takuki, @vcharpenay)
-
Map of type w3c/wot-thing-description#345 (7 comments by @danielpeintner, @egekorkan, @ToruKawaguchi)
-
TD Event in Thing-to-Thing interactions w3c/wot-thing-description#333 (6 comments by @AndreMaz, @sebastiankb, @takuki)
-
uriVariable does not seem to be proper defined or example is wrong w3c/wot-thing-description#376 (3 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
items is data schema or JSON Object or array of data schema? w3c/wot-thing-description#364 (2 comments by @egekorkan)
-
Group *similar* vocabulary terms together w3c/wot-thing-description#336 (2 comments by @danielpeintner, @takuki)
-
Clarify type value of "null" for properties w3c/wot-thing-description#222 (2 comments by @sebastiankb, @takuki)
-
td-event-response-arrays assertion is wrong w3c/wot-thing-description#365 (2 comments by @egekorkan, @sebastiankb)
-
Property extending DataSchema w3c/wot-thing-description#338 (2 comments by @mariapoveda, @vcharpenay)
-
Subscription and Cancellation response and request data schemas w3c/wot-thing-description#398 (1 comment by @ToruKawaguchi)
-
Vocabulary change: InteractionPattern to Affordance w3c/wot-thing-description#282 (1 comment by @egekorkan)
-
[question] Forms without href if base is defined w3c/wot-thing-description#383 (1 comment by @danielpeintner)
-
readOnly and writeOnly should be optional for action parameters w3c/wot-thing-description#322 (1 comment by @mlagally)
-
properties, actions and events need name **and** label field names w3c/wot-thing-description#216 (1 comment by @sebastiankb)
-
Namespaces: clarify if HTTP namespace is normative w3c/wot-thing-description#210 (1 comment by @sebastiankb)
-
Enabling Interaction History (making Actions the only way to modify state) w3c/wot-thing-description#155 (1 comment by @sebastiankb)
-
-
31 pull requests opened.
-
More AssertionTester fixes w3c/wot-thing-description#397, by @mmccool.
-
Fix missing results due to json/jsonld issue w3c/wot-thing-description#391, by @mmccool.
-
Fix SmartThings implementation description w3c/wot-thing-description#390, by @mmccool.
-
Latest assertion tester run w3c/wot-thing-description#389, by @mmccool.
-
Updated Test Results for Princeton Test Fest - OpenDay at 11am w3c/wot-thing-description#382, by @mmccool.
-
Handle default assertions in IR w3c/wot-thing-description#381, by @mmccool.
-
Added mention to "Thing Templates" in the Recent Changes section. w3c/wot-thing-description#379, by @takuki.
-
correct validation schema properties in data schema w3c/wot-thing-description#375, by @egekorkan.
-
Added a normative reference to IANA-URI-SCHEMES. w3c/wot-thing-description#374, by @takuki.
-
Fixed typos in NullSchema section (related to issue #222) w3c/wot-thing-description#373, by @takuki.
-
Display vocabulary terms in the order specified in td-validation.ttl w3c/wot-thing-description#372, by @takuki.
-
Added non-normative references to CoAP and MQTT to address #334 w3c/wot-thing-description#371, by @takuki.
-
Update diagrams after changes in Sec. 5 w3c/wot-thing-description#369, by @vcharpenay.
-
WIP: JSON-LD transformation w3c/wot-thing-description#368, by @vcharpenay.
-
Re-organized Recent Changes section w3c/wot-thing-description#366, by @takuki.
-
Fix accidental assertion ID duplicates w3c/wot-thing-description#362, by @mmccool.
-
Handle assertion variants in Implementation Report w3c/wot-thing-description#361, by @mmccool.
-
Behavioral section and assertions w3c/wot-thing-description#360, by @mmccool.
-
change security assertions in td-vocab to MUST w3c/wot-thing-description#358, by @egekorkan.
-
Change DataSchema mention in td-security assertion to SecurityScheme w3c/wot-thing-description#357, by @egekorkan.
-
fix examples and update validation schema w3c/wot-thing-description#356, by @egekorkan.
-
Correct security mandatory-with-default values w3c/wot-thing-description#354, by @mmccool.
-
Make securityDefinitions mandatory w3c/wot-thing-description#353, by @mmccool.
-
Fix Json Typo w3c/wot-thing-description#352, by @egekorkan.
-
Update Schema for Princeton testfest w3c/wot-thing-description#348, by @egekorkan.
-
It was made clearer as to how clients use meta interactions. w3c/wot-thing-description#344, by @takuki.
-
Description of "op" now references "interaction verb" w3c/wot-thing-description#343, by @takuki.
-
fix: there is no contentType "application/text" --> use "text/plain" ... w3c/wot-thing-description#342, by @danielpeintner.
-
It was made clearer that operations of "forms" in Thing are all about Properties. w3c/wot-thing-description#341, by @takuki.
-
Added an example that shows how to use forms at the top level. w3c/wot-thing-description#340, by @takuki.
-
Added "forms" to the top-level (i.e. Thing) for addressing issue #151. w3c/wot-thing-description#339, by @takuki.
-
-
27 pull requests merged.
-
More AssertionTester fixes w3c/wot-thing-description#397.
-
Fix missing results due to json/jsonld issue w3c/wot-thing-description#391.
-
Fix SmartThings implementation description w3c/wot-thing-description#390.
-
Latest assertion tester run w3c/wot-thing-description#389.
-
Updated Test Results for Princeton Test Fest - OpenDay at 11am w3c/wot-thing-description#382.
-
Behavioral section and assertions w3c/wot-thing-description#360.
-
correct validation schema properties in data schema w3c/wot-thing-description#375.
-
Handle default assertions in IR w3c/wot-thing-description#381.
-
Added mention to "Thing Templates" in the Recent Changes section. w3c/wot-thing-description#379.
-
fix examples and update validation schema w3c/wot-thing-description#356.
-
Added a normative reference to IANA-URI-SCHEMES. w3c/wot-thing-description#374.
-
Fixed typos in NullSchema section (related to issue #222) w3c/wot-thing-description#373.
-
Display vocabulary terms in the order specified in td-validation.ttl w3c/wot-thing-description#372.
-
Added non-normative references to CoAP and MQTT to address #334 w3c/wot-thing-description#371.
-
Update diagrams after changes in Sec. 5 w3c/wot-thing-description#369.
-
Re-organized Recent Changes section w3c/wot-thing-description#366.
-
Fix accidental assertion ID duplicates w3c/wot-thing-description#362.
-
Handle assertion variants in Implementation Report w3c/wot-thing-description#361.
-
Correct security mandatory-with-default values w3c/wot-thing-description#354.
-
Make securityDefinitions mandatory w3c/wot-thing-description#353.
-
Update Schema for Princeton testfest w3c/wot-thing-description#348.
-
It was made clearer as to how clients use meta interactions. w3c/wot-thing-description#344.
-
Description of "op" now references "interaction verb" w3c/wot-thing-description#343.
-
It was made clearer that operations of "forms" in Thing are all about Properties. w3c/wot-thing-description#341.
-
Added an example that shows how to use forms at the top level. w3c/wot-thing-description#340.
-
Added "forms" to the top-level (i.e. Thing) for addressing issue #151. w3c/wot-thing-description#339.
-
Update MultiLanguage w3c/wot-thing-description#330.
-
-
4 pull requests closed.
-
Change DataSchema mention in td-security assertion to SecurityScheme w3c/wot-thing-description#357.
-
change security assertions in td-vocab to MUST w3c/wot-thing-description#358.
-
Fix Json Typo w3c/wot-thing-description#352.
-
fix: there is no contentType "application/text" --> use "text/plain" ... w3c/wot-thing-description#342.
-
-
8 pull requests received 25 new comments.
-
change security assertions in td-vocab to MUST w3c/wot-thing-description#358 (10 comments by @egekorkan, @mmccool)
-
Behavioral section and assertions w3c/wot-thing-description#360 (5 comments by @egekorkan, @mmccool, @sebastiankb)
-
fix examples and update validation schema w3c/wot-thing-description#356 (3 comments by @egekorkan, @sebastiankb)
-
Change DataSchema mention in td-security assertion to SecurityScheme w3c/wot-thing-description#357 (2 comments by @mmccool, @sebastiankb)
-
fix: there is no contentType "application/text" --> use "text/plain" ... w3c/wot-thing-description#342 (1 comment by @sebastiankb)
-
w3c/wotwg
-
1 issue closed.
-
Add security directory w3c/wotwg#2.
-
-
1 issue received 1 new comment.
-
1 pull request closed.
-
Quick n' dirty news feed w3c/wotwg#7.
-
-
1 pull request received 1 new comment.
w3c/wot-architecture
-
7 pull requests opened.
-
Add a new text for the seciton Deployment Scenario w3c/wot-architecture#70, by @mryuichi.
-
Added new text for requirements and WoT servient architecture w3c/wot-architecture#69, by @mryuichi.
-
Added new text for requirements w3c/wot-architecture#68, by @mryuichi.
-
Integration of all contributions until 190124 w3c/wot-architecture#67, by @mlagally.
-
Imported terminology to index.html w3c/wot-architecture#66, by @ToruKawaguchi.
-
Add cross-domain collaboration use case. w3c/wot-architecture#65, by @k-toumura.
-
Added proposal/requirements to index.html as new chapter for review by editors w3c/wot-architecture#64, by @ToruKawaguchi.
-
-
3 pull requests merged.
-
Add a new text for the seciton Deployment Scenario w3c/wot-architecture#70.
-
Added new text for requirements and WoT servient architecture w3c/wot-architecture#69.
-
Integration of all contributions until 190124 w3c/wot-architecture#67.
-
-
1 pull request closed.
-
Added new text for requirements w3c/wot-architecture#68.
-
-
1 pull request received 1 new comment.
w3c/wot-security-testing-plan
-
5 pull requests opened.
-
Add test plan section w3c/wot-security-testing-plan#5, by @mmccool.
-
New Content: Intro, Best Practices, Functional Testing w3c/wot-security-testing-plan#4, by @mmccool.
-
Polish Elena's draft w3c/wot-security-testing-plan#3, by @mmccool.
-
Initial text for adversarial testing w3c/wot-security-testing-plan#2, by @ereshetova.
-
Initial template w3c/wot-security-testing-plan#1, by @mmccool.
-
-
5 pull requests merged.
-
Add test plan section w3c/wot-security-testing-plan#5.
-
New Content: Intro, Best Practices, Functional Testing w3c/wot-security-testing-plan#4.
-
Polish Elena's draft w3c/wot-security-testing-plan#3.
-
Initial text for adversarial testing w3c/wot-security-testing-plan#2.
-
Initial template w3c/wot-security-testing-plan#1.
-
w3c/wot-security
-
1 issue opened.
-
Terminology inconsistency - Proxy and Gateway are used interchangeably. w3c/wot-security#123, by @takuki.
-
w3c/wot-scripting-api
-
1 issue opened.
-
Mechanism for Observing Things, Properties, handling Thing Events and Discovery w3c/wot-scripting-api#158, by @zolkis.
-
-
2 issues received 8 new comments.
-
Mechanism for Observing Things, Properties, handling Thing Events and Discovery w3c/wot-scripting-api#158 (6 comments by @cynthia, @domenic, @zolkis)
-
URI Templates / Variables (Alignment with Binding&TD) w3c/wot-scripting-api#149 (2 comments by @danielpeintner, @zolkis)
-
-
1 pull request opened.
-
Add appendix for WebIDL index w3c/wot-scripting-api#159, by @zolkis.
-
-
1 pull request merged.
-
Add appendix for WebIDL index w3c/wot-scripting-api#159.
-
-
1 pull request received 2 new comments.
w3c/wot-binding-templates
-
1 pull request opened.
-
Added id to the header of section 3.2 Interaction Verbs w3c/wot-binding-templates#50, by @takuki.
-
w3c/wot-security-best-practices
-
1 pull request opened.
-
Initial template w3c/wot-security-best-practices#1, by @mmccool.
-
-
1 pull request merged.
-
Initial template w3c/wot-security-best-practices#1.
-