Web of Things Working Group - Activity in 2017
No matches.
TR publications
-
1 document published.
GitHub
w3c/wot-security
-
3 issues opened.
-
Integrity protection; require confidentiality w3c/wot-security#61, by @wseltzer.
-
Upgrade ref links to https if possible w3c/wot-security#60, by @mmccool.
-
Define TD/API Security requirements for 2018 spring plugfest. w3c/wot-security#59, by @mmccool.
-
-
7 issues received 11 new comments.
-
Define TD/API Security requirements for 2018 spring plugfest. w3c/wot-security#59 (4 comments by @ereshetova, @mmccool, @zolkis)
-
Authorization and minimizing access to TD in Things directory w3c/wot-security#53 (1 comment by @mmccool)
-
Add Material for "Secure Practices for designing WoT Scripts and WoT Script APIs" section w3c/wot-security#22 (1 comment by @mmccool)
-
-
3 pull requests opened.
-
Addressing various open issues w3c/wot-security#62, by @ereshetova.
-
addressing links problems & other issues pointed by Kaz w3c/wot-security#58, by @ereshetova.
-
add w3cid to Elena and McCool w3c/wot-security#57, by @ashimura.
-
-
2 pull requests merged.
-
addressing links problems & other issues pointed by Kaz w3c/wot-security#58.
-
add w3cid to Elena and McCool w3c/wot-security#57.
-
w3c/wot-thing-description
-
3 issues opened.
-
Unit definition in TD w3c/wot-thing-description#70, by @vcharpenay.
-
Examples 27 and 28 of the document missing context w3c/wot-thing-description#69, by @onovo1.
-
Examples in TD Deliverable do not use right context url w3c/wot-thing-description#68, by @sebastiankb.
-
-
2 issues received 4 new comments.
-
Examples in TD Deliverable do not use right context url w3c/wot-thing-description#68 (1 comment by @mkovatsc)
-
1 pull request opened.
-
Simplified JSON-LD w3c/wot-thing-description#71, by @danielpeintner.
-
-
1 pull request merged.
-
Simplified JSON-LD w3c/wot-thing-description#71.
-
w3c/wot-scripting-api
-
1 issue received 15 new comments.
-
API for next PlugFest (Prague 2018) w3c/wot-scripting-api#82 (15 comments by @danielpeintner, @mkovatsc, @mmccool, @zolkis)
-
w3c/wot-binding-templates
-
4 issues opened.
-
Consider the Mozilla pattern for events w3c/wot-binding-templates#16, by @mjkoster.
-
How does a Protocol Binding represent an item which is created as a result of an interaction w3c/wot-binding-templates#15, by @mjkoster.
-
MQTT Binding: Describing connection to the broker w3c/wot-binding-templates#14, by @mkovatsc.
-
Binding for next PlugFest (Prague 2018) w3c/wot-binding-templates#13, by @mkovatsc.
-
-
2 issues closed.
-
Observable Properties w3c/wot-binding-templates#10.
-
Links becoming Web Forms w3c/wot-binding-templates#12.
-
-
7 issues received 18 new comments.
-
Binding for next PlugFest (Prague 2018) w3c/wot-binding-templates#13 (8 comments by @danielpeintner, @mjkoster, @mkovatsc, @sebastiankb)
-
MQTT Binding: Describing connection to the broker w3c/wot-binding-templates#14 (3 comments by @mjkoster, @mkovatsc)
-
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 @vcharpenay)
-
How do Protocol Bindings work for exposed things? w3c/wot-binding-templates#4 (1 comment by @mkovatsc)
-
-
1 pull request merged.
-
vocabulary and examples w3c/wot-binding-templates#11.
-
-
1 pull request received 1 new comment.
w3c/wot-architecture
-
1 issue received 1 new comment.
GitHub
w3c/wot-architecture
-
4 issues opened.
-
Provide more information of the "Thing Directory" w3c/wot-architecture#47, by @onovo1.
-
Wrap up Burlingame F2F Plugfest and Terminology "Servient" w3c/wot-architecture#46, by @Kazuo-Kajimoto.
-
Terminology for "Semantics" w3c/wot-architecture#45, by @mkovatsc.
-
Beginner Terms w3c/wot-architecture#44, by @mkovatsc.
-
-
3 issues received 9 new comments.
-
Wrap up Burlingame F2F Plugfest and Terminology "Servient" w3c/wot-architecture#46 (7 comments by @mkovatsc, @mmccool, @mryuichi, @zolkis)
-
w3c/wot-scripting-api
-
3 issues opened.
-
API for next PlugFest (Prague 2018) w3c/wot-scripting-api#82, by @mkovatsc.
-
Interaction Inits: @type = pattern ∪ semanticTypes w3c/wot-scripting-api#81, by @mkovatsc.
-
Images missing on w3c's primer w3c/wot-scripting-api#79, by @rzr.
-
-
2 issues received 23 new comments.
-
API for next PlugFest (Prague 2018) w3c/wot-scripting-api#82 (6 comments by @danielpeintner, @mkovatsc, @zolkis)
-
1 pull request opened.
-
Fix markdown images links w3c/wot-scripting-api#80, by @rzr.
-
w3c/wot-thing-description
-
7 issues opened.
-
Generalize inputData, outputData to "payload" w3c/wot-thing-description#66, by @mmccool.
-
Do we need an "observeData" field? w3c/wot-thing-description#65, by @mmccool.
-
Provide "type" for Property w3c/wot-thing-description#64, by @mmccool.
-
Alignment with Mozilla/Evrthng proposal w3c/wot-thing-description#63, by @mkovatsc.
-
Links becoming Web Forms w3c/wot-thing-description#62, by @mkovatsc.
-
TPAC resolution: Observable Properties and Events w3c/wot-thing-description#61, by @mkovatsc.
-
Section 6.1: security is array of objects w3c/wot-thing-description#60, by @mkovatsc.
-
-
4 issues received 5 new comments.
-
Alignment with Mozilla/Evrthng proposal w3c/wot-thing-description#63 (2 comments by @mmccool, @poussa)
-
Generalize inputData, outputData to "payload" w3c/wot-thing-description#66 (1 comment by @vcharpenay)
-
TPAC resolution: Observable Properties and Events w3c/wot-thing-description#61 (1 comment by @zolkis)
-
-
1 pull request opened.
-
Test bed 2007 burlingame w3c/wot-thing-description#67, by @danielpeintner.
-
-
1 pull request merged.
-
Test bed 2007 burlingame w3c/wot-thing-description#67.
-
w3c/wot-security
-
7 issues opened.
-
Nesting security metadata in TD w3c/wot-security#56, by @ereshetova.
-
Document network reachability requirements for security schemes w3c/wot-security#55, by @ereshetova.
-
Study more related standards & methods for authentication & authorization w3c/wot-security#54, by @ereshetova.
-
Authorization and minimizing access to TD in Things directory w3c/wot-security#53, by @ereshetova.
-
Blockchains for WoT w3c/wot-security#52, by @ereshetova.
-
Signed TDs and implications on proxying w3c/wot-security#51, by @mkovatsc.
-
Topology scenarios w3c/wot-security#50, by @mkovatsc.
-
-
2 issues received 2 new comments.
w3c/wot-binding-templates
-
1 issue opened.
-
Links becoming Web Forms w3c/wot-binding-templates#12, by @mkovatsc.
-
-
1 issue received 1 new comment.
Participants
-
2 organizations joined.
-
Oracle Corporation joined.
-
Mitsubishi Electric Corporation joined.
-
GitHub
w3c/wot-scripting-api
-
13 issues opened.
-
API improvements w3c/wot-scripting-api#78, by @zolkis.
-
JavaScript property management in the WoT Scripting API w3c/wot-scripting-api#77, by @mkovatsc.
-
Definition of ExposedThing.start()/.stop() w3c/wot-scripting-api#76, by @mkovatsc.
-
Definition of ExposedThing.register()/.unregister() w3c/wot-scripting-api#75, by @mkovatsc.
-
ConsumedThing interface: The url read-only attribute represents the URL of the Thing w3c/wot-scripting-api#74, by @mkovatsc.
-
RequestHandler per type or per type&name w3c/wot-scripting-api#72, by @danielpeintner.
-
Does Scripting need a dataType attribute for Property, Action, and Event w3c/wot-scripting-api#71, by @danielpeintner.
-
Does WoT.Request need a "type" attribute w3c/wot-scripting-api#70, by @danielpeintner.
-
WoT.consume(USVString url) sufficient for consuming things? w3c/wot-scripting-api#69, by @danielpeintner.
-
Mapping WoT event models in Scripting API w3c/wot-scripting-api#68, by @zolkis.
-
WebIDL vs. prose mismatch w.r.t. ThingPropertyInit w3c/wot-scripting-api#66, by @danielpeintner.
-
Simplified API for JavaScript and other programming languages w3c/wot-scripting-api#64, by @draggett.
-
-
1 issue closed.
-
WebIDL vs. prose mismatch w.r.t. ThingPropertyInit w3c/wot-scripting-api#66.
-
-
14 issues received 113 new comments.
-
Does Scripting need a dataType attribute for Property, Action, and Event w3c/wot-scripting-api#71 (16 comments by @mkovatsc, @zolkis)
-
Does WoT.Request need a "type" attribute w3c/wot-scripting-api#70 (13 comments by @danielpeintner, @mkovatsc, @zolkis)
-
Simplified API for JavaScript and other programming languages w3c/wot-scripting-api#64 (12 comments by @draggett, @mkovatsc, @zolkis)
-
Definition of ExposedThing.start()/.stop() w3c/wot-scripting-api#76 (11 comments by @mkovatsc, @zolkis)
-
Mapping WoT event models in Scripting API w3c/wot-scripting-api#68 (8 comments by @mkovatsc, @zolkis)
-
RequestHandler per type or per type&name w3c/wot-scripting-api#72 (8 comments by @mkovatsc, @zolkis)
-
Can an Exposed Thing provide a Protocol Binding? w3c/wot-scripting-api#45 (5 comments by @Kazuo-Kajimoto, @mkovatsc, @zolkis)
-
WoT.consume(USVString url) sufficient for consuming things? w3c/wot-scripting-api#69 (5 comments by @danielpeintner, @mkovatsc, @zolkis)
-
onObserve() cannot be used for both Property change notifications and Event notifications -- and should be removed alltogether w3c/wot-scripting-api#73 (4 comments by @mkovatsc, @zolkis)
-
Definition of ExposedThing.register()/.unregister() w3c/wot-scripting-api#75 (3 comments by @mkovatsc, @zolkis)
-
JavaScript property management in the WoT Scripting API w3c/wot-scripting-api#77 (1 comment by @zolkis)
-
ConsumedThing interface: The url read-only attribute represents the URL of the Thing w3c/wot-scripting-api#74 (1 comment by @zolkis)
-
2 pull requests opened.
-
fix issue https://github.com/w3c/wot-scripting-api/issues/66 w3c/wot-scripting-api#67, by @danielpeintner.
-
ThingFilter uses non-existing/wrong enum w3c/wot-scripting-api#65, by @danielpeintner.
-
-
2 pull requests merged.
-
fix issue https://github.com/w3c/wot-scripting-api/issues/66 w3c/wot-scripting-api#67.
-
ThingFilter uses non-existing/wrong enum w3c/wot-scripting-api#65.
-
-
1 pull request closed.
-
Structure use cases w3c/wot-scripting-api#63.
-
-
3 pull requests received 4 new comments.
-
fix issue https://github.com/w3c/wot-scripting-api/issues/66 w3c/wot-scripting-api#67 (2 comments by @zolkis)
-
w3c/wot-binding-templates
-
3 issues opened.
-
Observable Properties w3c/wot-binding-templates#10, by @mkovatsc.
-
Mapping JSON to CBOR w3c/wot-binding-templates#8, by @mmccool.
-
Event Implementation Proposal (HTTP+WebSocket) w3c/wot-binding-templates#7, by @yamagile.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
vocabulary and examples w3c/wot-binding-templates#11, by @mjkoster.
-
Initial spec contribution w3c/wot-binding-templates#9, by @mjkoster.
-
-
1 pull request merged.
-
Initial spec contribution w3c/wot-binding-templates#9.
-
-
1 pull request closed.
-
Initial spec draft w3c/wot-binding-templates#5.
-
-
1 pull request received 2 new comments.
w3c/wot-thing-description
-
4 issues opened.
-
Alignment with Generic Sensor spec w3c/wot-thing-description#59, by @zolkis.
-
@Id and reference not explain properly w3c/wot-thing-description#58, by @onovo1.
-
Support of Scripts in ThingDescription w3c/wot-thing-description#57, by @danielpeintner.
-
Is WoT ontology normative or not w3c/wot-thing-description#56, by @takuki.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Proposed specification for input/output type definition w3c/wot-thing-description#54.
-
-
1 pull request received 2 new comments.
-
Proposed specification for input/output type definition w3c/wot-thing-description#54 (2 comments by @vcharpenay)
-
w3c/wot-security
-
11 issues opened.
-
Review Security Learnings from TPAC2017 w3c/wot-security#48, by @mmccool.
-
Reference Fetch standard in addition to CORS w3c/wot-security#46, by @mmccool.
-
Make links to the standard security terms w3c/wot-security#45, by @ereshetova.
-
Make links to the WoT Terminology from the WoT Architecture document w3c/wot-security#44, by @ereshetova.
-
Clean up Security Objectives section w3c/wot-security#41, by @mmccool.
-
Align Threat model with IETF IoT RFC w3c/wot-security#40, by @mmccool.
-
Add Lifecycle discussion w3c/wot-security#39, by @mmccool.
-
Add a section on "Privacy Considerations" w3c/wot-security#36, by @mmccool.
-
Align Security and Privacy Considerations section of Architecture CR with wot-security w3c/wot-security#35, by @mmccool.
-
Security scenarios involving HTTP and WebSockets w3c/wot-security#34, by @draggett.
-
Cite WoT Architecture Doc in Intro w3c/wot-security#32, by @mmccool.
-
-
9 issues closed.
-
Cite WoT Architecture Doc in Intro w3c/wot-security#32.
-
Clean up Security Objectives section w3c/wot-security#41.
-
Fix definition links to threat model w3c/wot-security#28.
-
Use ReSpec markup for figures and definitions w3c/wot-security#29.
-
Add Material for "Examples of WoT security configurations w3c/wot-security#19.
-
Add Material for "Existing Security Best Practices" section w3c/wot-security#18.
-
Clean up Abstract w3c/wot-security#17.
-
Remove redundant threat model material w3c/wot-security#25.
-
Fix Table formatting and Threat Model highlighting w3c/wot-security#16.
-
-
15 issues received 28 new comments.
-
Security scenarios involving HTTP and WebSockets w3c/wot-security#34 (4 comments by @ereshetova, @mmccool)
-
Make links to the WoT Terminology from the WoT Architecture document w3c/wot-security#44 (3 comments by @mmccool, @zolkis)
-
Use ReSpec markup for figures and definitions w3c/wot-security#29 (3 comments by @ereshetova, @mmccool)
-
Add Material for "Examples of WoT security configurations w3c/wot-security#19 (1 comment by @ereshetova)
-
Add Material for "Secure Practices for designing WoT Scripts and WoT Script APIs" section w3c/wot-security#22 (1 comment by @mmccool)
-
-
7 pull requests opened.
-
script mgmt API --> Script Management Interface w3c/wot-security#49, by @ereshetova.
-
Remove redundant security objectives content w3c/wot-security#47, by @mmccool.
-
Big cleanup of Threat model to allign with past 3 months of discussions w3c/wot-security#43, by @ereshetova.
-
Making Security objectives use links to threat definitions w3c/wot-security#42, by @ereshetova.
-
Adding & correcting content for sections 5.1-5.4 w3c/wot-security#38, by @ereshetova.
-
New subsection on HTTP & WebSockets w3c/wot-security#37, by @draggett.
-
remove redundant threat model w3c/wot-security#33, by @mmccool.
-
-
10 pull requests merged.
-
script mgmt API --> Script Management Interface w3c/wot-security#49.
-
Remove redundant security objectives content w3c/wot-security#47.
-
Big cleanup of Threat model to allign with past 3 months of discussions w3c/wot-security#43.
-
Making Security objectives use links to threat definitions w3c/wot-security#42.
-
Adding & correcting content for sections 5.1-5.4 w3c/wot-security#38.
-
Initial content for "Existing Best Practices" section w3c/wot-security#30.
-
Adding content and references for section 5.1 w3c/wot-security#31.
-
remove redundant threat model w3c/wot-security#33.
-
Fix table formatting for threat model w3c/wot-security#27.
-
Clean up abstract w3c/wot-security#26.
-
-
1 pull request closed.
-
Remove redundant markdown threat model w3c/wot-security#24.
-
-
9 pull requests received 27 new comments.
-
Big cleanup of Threat model to allign with past 3 months of discussions w3c/wot-security#43 (11 comments by @ereshetova, @mmccool, @zolkis)
-
New subsection on HTTP & WebSockets w3c/wot-security#37 (4 comments by @draggett, @ereshetova, @mmccool)
-
Adding & correcting content for sections 5.1-5.4 w3c/wot-security#38 (3 comments by @ereshetova, @zolkis)
-
Making Security objectives use links to threat definitions w3c/wot-security#42 (1 comment by @mmccool)
-
w3c/wot-architecture
-
1 issue received 1 new comment.
TR publications
-
3 documents published.
-
Web of Things (WoT) Architecture published as a First Public Working Draft. History of Web of Things (WoT) Architecture
-
Web of Things (WoT) Scripting API published as a First Public Working Draft. History of Web of Things (WoT) Scripting API
-
Web of Things (WoT) Thing Description published as a First Public Working Draft. History of Web of Things (WoT) Thing Description
-
Participants
-
1 participant joined.
-
Michael Koster (W3C Invited Experts) joined.
-
GitHub
w3c/wot-scripting-api
-
1 issue opened.
-
Editorial issues to be solved for FPWD w3c/wot-scripting-api#57, by @ashimura.
-
-
3 issues closed.
-
Procedure for proposing updates w3c/wot-scripting-api#42.
-
Editorial issues to be solved for FPWD w3c/wot-scripting-api#57.
-
Clean up / reorganize the repo w3c/wot-scripting-api#48.
-
-
2 issues received 2 new comments.
-
10 pull requests opened.
-
Structure use cases w3c/wot-scripting-api#63, by @wiresio.
-
Update use cases. w3c/wot-scripting-api#62, by @zolkis.
-
Editorial changes w3c/wot-scripting-api#60, by @zolkis.
-
Fix Pubrules issues w3c/wot-scripting-api#59, by @zolkis.
-
Fix #57, edits w3c/wot-scripting-api#58, by @zolkis.
-
Editorial fixes for FPWD w3c/wot-scripting-api#56, by @zolkis.
-
Small fixes. w3c/wot-scripting-api#55, by @zolkis.
-
Fixes for FPWD w3c/wot-scripting-api#54, by @zolkis.
-
update security section editor's note w3c/wot-scripting-api#53, by @mmccool.
-
FPWD edits w3c/wot-scripting-api#52, by @zolkis.
-
-
10 pull requests merged.
-
Update use cases. w3c/wot-scripting-api#62.
-
Editorial changes w3c/wot-scripting-api#60.
-
Fix Pubrules issues w3c/wot-scripting-api#59.
-
Fix #57, edits w3c/wot-scripting-api#58.
-
Editorial fixes for FPWD w3c/wot-scripting-api#56.
-
Small fixes. w3c/wot-scripting-api#55.
-
Fixes for FPWD w3c/wot-scripting-api#54.
-
update security section editor's note w3c/wot-scripting-api#53.
-
FPWD edits w3c/wot-scripting-api#52.
-
Repo cleanup. Consistency checks. w3c/wot-scripting-api#51.
-
-
6 pull requests received 12 new comments.
w3c/wot-security
-
14 issues opened.
-
Use ReSpec markup for figures and definitions w3c/wot-security#29, by @mmccool.
-
Fix definition links to threat model w3c/wot-security#28, by @mmccool.
-
Remove redundant threat model material w3c/wot-security#25, by @mmccool.
-
Add Material for "Security Validation" section w3c/wot-security#23, by @mmccool.
-
Add Material for "Secure Practices for designing WoT Scripts and WoT Script APIs" section w3c/wot-security#22, by @mmccool.
-
Add Material for "Industrial/Critical infrastructure environment" scenarios w3c/wot-security#21, by @mmccool.
-
Add Material for "Business/Corporate environment" scenarios w3c/wot-security#20, by @mmccool.
-
Add Material for "Examples of WoT security configurations w3c/wot-security#19, by @mmccool.
-
Add Material for "Existing Security Best Practices" section w3c/wot-security#18, by @mmccool.
-
Clean up Abstract w3c/wot-security#17, by @mmccool.
-
Fix Table formatting and Threat Model highlighting w3c/wot-security#16, by @mmccool.
-
Is Provisioning in Scope? w3c/wot-security#15, by @mmccool.
-
Separate Discovery/Expose w3c/wot-security#14, by @mmccool.
-
Align with Architecture document w3c/wot-security#13, by @mmccool.
-
-
4 issues received 5 new comments.
-
17 pull requests opened.
-
Adding content and references for section 5.1 w3c/wot-security#31, by @ereshetova.
-
Initial content for "Existing Best Practices" section w3c/wot-security#30, by @mmccool.
-
Fix table formatting for threat model w3c/wot-security#27, by @mmccool.
-
Clean up abstract w3c/wot-security#26, by @mmccool.
-
Remove redundant markdown threat model w3c/wot-security#24, by @mmccool.
-
Working w3c/wot-security#12, by @ereshetova.
-
Add Elena Reshetova as Editor w3c/wot-security#11, by @mmccool.
-
Convert MD files to HTML in index w3c/wot-security#10, by @mmccool.
-
Add HTML rendering links to README.md w3c/wot-security#9, by @mmccool.
-
Working w3c/wot-security#8, by @ereshetova.
-
Working w3c/wot-security#7, by @ereshetova.
-
link to index.html w3c/wot-security#6, by @mmccool.
-
update README.md with working/master branch instructions w3c/wot-security#5, by @mmccool.
-
sync new README.md w3c/wot-security#4, by @mmccool.
-
Update with changes from Matthias w3c/wot-security#3, by @mmccool.
-
Initial checkin with content from old TD doc w3c/wot-security#2, by @mmccool.
-
add references, links w3c/wot-security#1, by @mmccool.
-
-
11 pull requests merged.
-
Add Elena Reshetova as Editor w3c/wot-security#11.
-
Working w3c/wot-security#12.
-
Convert MD files to HTML in index w3c/wot-security#10.
-
Add HTML rendering links to README.md w3c/wot-security#9.
-
Working w3c/wot-security#8.
-
link to index.html w3c/wot-security#6.
-
update README.md with working/master branch instructions w3c/wot-security#5.
-
sync new README.md w3c/wot-security#4.
-
Update with changes from Matthias w3c/wot-security#3.
-
Initial checkin with content from old TD doc w3c/wot-security#2.
-
add references, links w3c/wot-security#1.
-
-
1 pull request closed.
-
Working w3c/wot-security#7.
-
-
7 pull requests received 8 new comments.
w3c/wot-thing-description
-
4 issues opened.
-
Material to pitch use of semantics in TDs w3c/wot-thing-description#53, by @mkovatsc.
-
[FPWD] Feedback call in State of this Document w3c/wot-thing-description#52, by @mkovatsc.
-
[FPWD] Read through and comments w3c/wot-thing-description#49, by @danielpeintner.
-
[FPWD] Abstract w3c/wot-thing-description#48, by @mkovatsc.
-
-
9 issues closed.
-
[FPWD] Read through and comments w3c/wot-thing-description#49.
-
Content negotiation for TD namespace w3c/wot-thing-description#20.
-
Best practices for standardising Linked Data Vocabularies w3c/wot-thing-description#19.
-
Check Consistency of Terminology with Definitions w3c/wot-thing-description#31.
-
[FPWD] Feedback call in State of this Document w3c/wot-thing-description#52.
-
[FPWD] Abstract w3c/wot-thing-description#48.
-
[FPWD] Property has a field "writable" or "isWritable"? (in Section 4.2.3 Property) w3c/wot-thing-description#35.
-
[FPWD] Class issue vs. ednote w3c/wot-thing-description#27.
-
Improve abstract w3c/wot-thing-description#30.
-
-
13 issues received 52 new comments.
-
[FPWD] Read through and comments w3c/wot-thing-description#49 (30 comments by @sebastiankb, @vcharpenay)
-
Check Consistency of Terminology with Definitions w3c/wot-thing-description#31 (5 comments by @mkovatsc, @sebastiankb, @takuki)
-
(Intentional?) Removal of stability in property w3c/wot-thing-description#29 (2 comments by @sebastiankb, @takuki)
-
[FPWD] Property has a field "writable" or "isWritable"? (in Section 4.2.3 Property) w3c/wot-thing-description#35 (2 comments by @sebastiankb)
-
Best practices for standardising Linked Data Vocabularies w3c/wot-thing-description#19 (1 comment by @sebastiankb)
-
[FPWD] Feedback call in State of this Document w3c/wot-thing-description#52 (1 comment by @sebastiankb)
-
-
12 pull requests opened.
-
Added cardinality axioms in OWL file w3c/wot-thing-description#55, by @mariapoveda.
-
Proposed specification for input/output type definition w3c/wot-thing-description#54, by @vcharpenay.
-
Changed "Fujitsu Ltd." to real affiliation w3c/wot-thing-description#51, by @takuki.
-
Replace security section with Editor's note and hyperlink to wot-security w3c/wot-thing-description#50, by @mmccool.
-
fix hyperlinks (to wot-security); add ed note w3c/wot-thing-description#47, by @mmccool.
-
Removed redundant tables from JSON-LD Serialization section w3c/wot-thing-description#46, by @takuki.
-
Some terminology fix w3c/wot-thing-description#45, by @takuki.
-
Correct abstract grammar w3c/wot-thing-description#43, by @mmccool.
-
Added "Terminology" section, created "informative references" section. w3c/wot-thing-description#42, by @takuki.
-
Fixed bibliography. w3c/wot-thing-description#41, by @takuki.
-
Improved description of 4.2.2 InteractionPattern, and fixed bibliography w3c/wot-thing-description#40, by @takuki.
-
-
10 pull requests merged.
-
Changed "Fujitsu Ltd." to real affiliation w3c/wot-thing-description#51.
-
Replace security section with Editor's note and hyperlink to wot-security w3c/wot-thing-description#50.
-
fix hyperlinks (to wot-security); add ed note w3c/wot-thing-description#47.
-
Removed redundant tables from JSON-LD Serialization section w3c/wot-thing-description#46.
-
Some terminology fix w3c/wot-thing-description#45.
-
fix typos w3c/wot-thing-description#44.
-
Correct abstract grammar w3c/wot-thing-description#43.
-
Added "Terminology" section, created "informative references" section. w3c/wot-thing-description#42.
-
Fixed bibliography. w3c/wot-thing-description#41.
-
Improved description of 4.2.2 InteractionPattern, and fixed bibliography w3c/wot-thing-description#40.
-
-
1 pull request closed.
-
Added proposed alignment to W3C&OGC SOSA/SSN as per ACTION-115 w3c/wot-thing-description#28.
-
-
1 pull request received 2 new comments.
-
Added proposed alignment to W3C&OGC SOSA/SSN as per ACTION-115 w3c/wot-thing-description#28 (2 comments by @maximelefrancois86, @sebastiankb)
-
w3c/wot-binding-templates
-
1 issue opened.
-
Clarifying the scope and motivation for binding templates w3c/wot-binding-templates#6, by @draggett.
-
-
2 issues received 7 new comments.
-
Clarifying the scope and motivation for binding templates w3c/wot-binding-templates#6 (4 comments by @draggett, @zolkis)
-
Start list of protocols and platform dialects to describe w3c/wot-binding-templates#1 (3 comments by @mmccool)
-
w3c/wot-architecture
-
1 issue opened.
-
Arrow between App+Scripts and TD in Fig. 10 w3c/wot-architecture#43, by @ToruKawaguchi.
-
-
5 issues closed.
-
Consistency check w3c/wot-architecture#30.
-
Must close IG architecture draft w3c/wot-architecture#4.
-
Arrow between App+Scripts and TD in Fig. 10 w3c/wot-architecture#43.
-
Security Considerations w3c/wot-architecture#32.
-
3. Use Cases w3c/wot-architecture#34.
-
-
6 issues received 28 new comments.
-
Consistency check w3c/wot-architecture#30 (15 comments by @Kazuo-Kajimoto, @mkovatsc, @mmccool, @zolkis)
-
Arrow between App+Scripts and TD in Fig. 10 w3c/wot-architecture#43 (2 comments by @mkovatsc, @ToruKawaguchi)
-
-
5 pull requests opened.
-
FPWD polish -- with contributor alignment! w3c/wot-architecture#42, by @mkovatsc.
-
FPWD polish w3c/wot-architecture#41, by @mkovatsc.
-
Security refinements w3c/wot-architecture#40, by @mmccool.
-
Consistency fixes w3c/wot-architecture#39, by @mkovatsc.
-
Typos, small edits w3c/wot-architecture#38, by @mmccool.
-
-
6 pull requests merged.
-
FPWD polish -- with contributor alignment! w3c/wot-architecture#42.
-
FPWD polish w3c/wot-architecture#41.
-
Security refinements w3c/wot-architecture#40.
-
Consistency fixes w3c/wot-architecture#39.
-
Typos, small edits w3c/wot-architecture#38.
-
resolution for issue #34 w3c/wot-architecture#36.
-
-
4 pull requests received 4 new comments.
GitHub
w3c/wot-thing-description
-
5 issues opened.
-
[FPWD] Property has a field "writable" or "isWritable"? (in Section 4.2.3 Property) w3c/wot-thing-description#35, by @takuki.
-
Check Consistency of Terminology with Definitions w3c/wot-thing-description#31, by @mmccool.
-
Improve abstract w3c/wot-thing-description#30, by @mmccool.
-
(Intentional?) Removal of stability in property w3c/wot-thing-description#29, by @danielpeintner.
-
[FPWD] Class issue vs. ednote w3c/wot-thing-description#27, by @danielpeintner.
-
-
8 issues received 24 new comments.
-
Data types for interaction models for things w3c/wot-thing-description#13 (13 comments by @draggett, @handrews, @mariapoveda, @vcharpenay)
-
[FPWD] Property has a field "writable" or "isWritable"? (in Section 4.2.3 Property) w3c/wot-thing-description#35 (3 comments by @takuki, @zolkis)
-
Check Consistency of Terminology with Definitions w3c/wot-thing-description#31 (1 comment by @danielpeintner)
-
-
14 pull requests opened.
-
Addressing issue #27 w3c/wot-thing-description#39, by @takuki.
-
Improved Abstraction. w3c/wot-thing-description#38, by @takuki.
-
Serialization sections is ready. w3c/wot-thing-description#37, by @takuki.
-
Corrected some typos and wordings in td.ttl w3c/wot-thing-description#36, by @takuki.
-
Section 5.7 "Type System" is ready. w3c/wot-thing-description#34, by @takuki.
-
Introduction of 5.7 Type System section is ready w3c/wot-thing-description#33, by @takuki.
-
Security updates w3c/wot-thing-description#32, by @mmccool.
-
Added proposed alignment to W3C&OGC SOSA/SSN as per ACTION-115 w3c/wot-thing-description#28, by @maximelefrancois86.
-
Initial commit for Security Sections w3c/wot-thing-description#26, by @mmccool.
-
added 'name' in the definition of Thing and InteractionPattern w3c/wot-thing-description#25, by @vcharpenay.
-
Synchronizing content with current practices document w3c/wot-thing-description#24, by @takuki.
-
Reconciled conflicts between latest changes w3c/wot-thing-description#23, by @takuki.
-
Fixed rendering issues w3c/wot-thing-description#22, by @vcharpenay.
-
Included templete rendering code w3c/wot-thing-description#21, by @vcharpenay.
-
-
14 pull requests merged.
-
Addressing issue #27 w3c/wot-thing-description#39.
-
Improved Abstraction. w3c/wot-thing-description#38.
-
Serialization sections is ready. w3c/wot-thing-description#37.
-
Corrected some typos and wordings in td.ttl w3c/wot-thing-description#36.
-
Security updates w3c/wot-thing-description#32.
-
Section 5.7 "Type System" is ready. w3c/wot-thing-description#34.
-
Introduction of 5.7 Type System section is ready w3c/wot-thing-description#33.
-
Initial commit for Security Sections w3c/wot-thing-description#26.
-
added 'name' in the definition of Thing and InteractionPattern w3c/wot-thing-description#25.
-
Synchronizing content with current practices document w3c/wot-thing-description#24.
-
Reconciled conflicts between latest changes w3c/wot-thing-description#23.
-
Fixed rendering issues w3c/wot-thing-description#22.
-
Included templete rendering code w3c/wot-thing-description#21.
-
add semantic test-data w3c/wot-thing-description#11.
-
-
3 pull requests received 7 new comments.
w3c/wot-architecture
-
21 issues opened.
-
General issues for FPWD w3c/wot-architecture#37, by @danielpeintner.
-
Terminology w3c/wot-architecture#35, by @draggett.
-
3. Use Cases w3c/wot-architecture#34, by @mkovatsc.
-
Security Considerations w3c/wot-architecture#32, by @mkovatsc.
-
Consistency check w3c/wot-architecture#30, by @mkovatsc.
-
High-level content of the document w3c/wot-architecture#27, by @mkovatsc.
-
Thing proxies w3c/wot-architecture#26, by @mkovatsc.
-
Connectivity Section(s) w3c/wot-architecture#24, by @mkovatsc.
-
Link other documents such as TD, Scripting, Bindings w3c/wot-architecture#21, by @danielpeintner.
-
Git edit link pointing to wrong repo w3c/wot-architecture#20, by @danielpeintner.
-
Architecture > WoT Servient Architecture w3c/wot-architecture#19, by @mmccool.
-
Discovery API w3c/wot-architecture#18, by @mmccool.
-
Terminology missing/inconsistent w3c/wot-architecture#17, by @mmccool.
-
6.3 WoT servient on Smartphone - Browser as Servient w3c/wot-architecture#15, by @mkovatsc.
-
6.3 WoT servient on Smartphone - Browser + Servient w3c/wot-architecture#14, by @mkovatsc.
-
6. Mapping variations: Security and Privacy boxes in figures w3c/wot-architecture#13, by @mkovatsc.
-
6. Mapping variations: Web browser w3c/wot-architecture#12, by @mkovatsc.
-
"Security option" in 4.2 Scripting API w3c/wot-architecture#11, by @mkovatsc.
-
Fig.2 Protocol Binding Structure w3c/wot-architecture#10, by @mkovatsc.
-
Integration Patterns w3c/wot-architecture#9, by @mkovatsc.
-
Video, Audio treatment w3c/wot-architecture#8, by @Kazuo-Kajimoto.
-
-
14 issues closed.
-
General issues for FPWD w3c/wot-architecture#37.
-
Terminology missing/inconsistent w3c/wot-architecture#17.
-
Git edit link pointing to wrong repo w3c/wot-architecture#20.
-
Link other documents such as TD, Scripting, Bindings w3c/wot-architecture#21.
-
Connectivity Section(s) w3c/wot-architecture#24.
-
High-level content of the document w3c/wot-architecture#27.
-
6.3 WoT servient on Smartphone - Browser as Servient w3c/wot-architecture#15.
-
"Security option" in 4.2 Scripting API w3c/wot-architecture#11.
-
6.3 WoT servient on Smartphone - Browser + Servient w3c/wot-architecture#14.
-
Architecture > WoT Servient Architecture w3c/wot-architecture#19.
-
6. Mapping variations: Security and Privacy boxes in figures w3c/wot-architecture#13.
-
Fig.2 Protocol Binding Structure w3c/wot-architecture#10.
-
6. Mapping variations: Web browser w3c/wot-architecture#12.
-
Discovery API w3c/wot-architecture#18.
-
-
18 issues received 77 new comments.
-
Consistency check w3c/wot-architecture#30 (16 comments by @danielpeintner, @mkovatsc, @mmccool, @zolkis)
-
High-level content of the document w3c/wot-architecture#27 (8 comments by @Kazuo-Kajimoto, @mkovatsc, @mmccool, @mryuichi)
-
6.3 WoT servient on Smartphone - Browser as Servient w3c/wot-architecture#15 (5 comments by @mkovatsc, @mmccool, @zolkis)
-
Architecture > WoT Servient Architecture w3c/wot-architecture#19 (5 comments by @knimura, @mkovatsc, @mmccool, @zolkis)
-
6. Mapping variations: Web browser w3c/wot-architecture#12 (5 comments by @draggett, @mkovatsc, @mmccool)
-
Fig.2 Protocol Binding Structure w3c/wot-architecture#10 (4 comments by @draggett, @knimura, @mkovatsc)
-
6.3 WoT servient on Smartphone - Browser + Servient w3c/wot-architecture#14 (3 comments by @mkovatsc, @mmccool)
-
6. Mapping variations: Security and Privacy boxes in figures w3c/wot-architecture#13 (2 comments by @mkovatsc, @mmccool)
-
-
10 pull requests opened.
-
resolution for issue #34 w3c/wot-architecture#36, by @knimura.
-
Restructuring (see #27) w3c/wot-architecture#33, by @mkovatsc.
-
add term: WoT API w3c/wot-architecture#31, by @mmccool.
-
Proposed redefinition of "Thing" vs. "Servient" w3c/wot-architecture#29, by @vcharpenay.
-
Fixed preamble w3c/wot-architecture#28, by @mkovatsc.
-
Harmonized figure style w3c/wot-architecture#23, by @mkovatsc.
-
Harmonized figure style w3c/wot-architecture#22, by @mkovatsc.
-
Clean up formatting and English w3c/wot-architecture#16, by @mmccool.
-
Security architecture sections w3c/wot-architecture#7, by @mmccool.
-
Suggested updates to abstract w3c/wot-architecture#6, by @mmccool.
-
-
6 pull requests merged.
-
Restructuring (see #27) w3c/wot-architecture#33.
-
Fixed preamble w3c/wot-architecture#28.
-
Harmonized figure style w3c/wot-architecture#23.
-
Clean up formatting and English w3c/wot-architecture#16.
-
Security architecture sections w3c/wot-architecture#7.
-
Suggested updates to abstract w3c/wot-architecture#6.
-
-
3 pull requests closed.
-
add term: WoT API w3c/wot-architecture#31.
-
Proposed redefinition of "Thing" vs. "Servient" w3c/wot-architecture#29.
-
Harmonized figure style w3c/wot-architecture#22.
-
-
1 pull request reopened.
-
Harmonized figure style w3c/wot-architecture#23, by @mkovatsc.
-
-
8 pull requests received 52 new comments.
-
Proposed redefinition of "Thing" vs. "Servient" w3c/wot-architecture#29 (15 comments by @Kazuo-Kajimoto, @mkovatsc, @mmccool, @vcharpenay, @zolkis)
-
Suggested updates to abstract w3c/wot-architecture#6 (11 comments by @Kazuo-Kajimoto, @mkovatsc, @mmccool)
-
Restructuring (see #27) w3c/wot-architecture#33 (4 comments by @Kazuo-Kajimoto, @mkovatsc, @mmccool)
-
w3c/wot-scripting-api
-
6 issues opened.
-
Clean up / reorganize the repo w3c/wot-scripting-api#48, by @zolkis.
-
Consistency check vs other WoT specifications w3c/wot-scripting-api#47, by @zolkis.
-
Can an Exposed Thing provide a Protocol Binding? w3c/wot-scripting-api#45, by @mmccool.
-
Support for Capabilities w3c/wot-scripting-api#44, by @zolkis.
-
Procedure for proposing updates w3c/wot-scripting-api#42, by @danielpeintner.
-
Retrieving information from ThingDescription (or internal metadata) w3c/wot-scripting-api#38, by @danielpeintner.
-
-
1 issue closed.
-
Reaching out to Architecture TF w3c/wot-scripting-api#30.
-
-
9 issues received 20 new comments.
-
Retrieving information from ThingDescription (or internal metadata) w3c/wot-scripting-api#38 (9 comments by @danielpeintner, @draggett, @zolkis)
-
Isolation of scripts / sandbox and access to outside w3c/wot-scripting-api#25 (1 comment by @mmccool)
-
policies of security enforcement in the scripting runtime w3c/wot-scripting-api#26 (1 comment by @mmccool)
-
-
9 pull requests opened.
-
Repo cleanup. Consistency checks. w3c/wot-scripting-api#51, by @zolkis.
-
Remove obsolete files from the repo root w3c/wot-scripting-api#50, by @zolkis.
-
Reorganize and cleanup the repository w3c/wot-scripting-api#49, by @zolkis.
-
Add the Request interface, event definitions, expand descriptions. w3c/wot-scripting-api#46, by @zolkis.
-
Editorial changes. Rework WoT API section with new structure. w3c/wot-scripting-api#43, by @zolkis.
-
create WebIDL skeleton by fixing all WebIDL issues w3c/wot-scripting-api#41, by @danielpeintner.
-
Add Daniel Peintner as editor w3c/wot-scripting-api#40, by @zolkis.
-
HTML fixes and first try to restructure WebIDL w3c/wot-scripting-api#39, by @danielpeintner.
-
ManagerThing&ReverseProxy w3c/wot-scripting-api#37, by @knimura.
-
-
8 pull requests merged.
-
Remove obsolete files from the repo root w3c/wot-scripting-api#50.
-
Reorganize and cleanup the repository w3c/wot-scripting-api#49.
-
Add the Request interface, event definitions, expand descriptions. w3c/wot-scripting-api#46.
-
ManagerThing&ReverseProxy w3c/wot-scripting-api#37.
-
Editorial changes. Rework WoT API section with new structure. w3c/wot-scripting-api#43.
-
Add Daniel Peintner as editor w3c/wot-scripting-api#40.
-
create WebIDL skeleton by fixing all WebIDL issues w3c/wot-scripting-api#41.
-
HTML fixes and first try to restructure WebIDL w3c/wot-scripting-api#39.
-
-
1 pull request closed.
-
ManagerThing&ReverseProxy w3c/wot-scripting-api#32.
-
-
8 pull requests received 44 new comments.
-
Add the Request interface, event definitions, expand descriptions. w3c/wot-scripting-api#46 (16 comments by @danielpeintner, @knimura, @zolkis)
-
create WebIDL skeleton by fixing all WebIDL issues w3c/wot-scripting-api#41 (6 comments by @danielpeintner, @zolkis)
-
Editorial changes. Rework WoT API section with new structure. w3c/wot-scripting-api#43 (3 comments by @zolkis)
-
HTML fixes and first try to restructure WebIDL w3c/wot-scripting-api#39 (3 comments by @danielpeintner, @zolkis)
-
w3c/wot-binding-templates
-
2 issues opened.
-
How do Protocol Bindings work for exposed things? w3c/wot-binding-templates#4, by @mjkoster.
-
Use cases and requirements for protocol binding w3c/wot-binding-templates#3, by @draggett.
-
-
3 issues received 9 new comments.
-
Use cases and requirements for protocol binding w3c/wot-binding-templates#3 (5 comments by @draggett, @mjkoster, @mmccool, @zolkis)
-
Start list of protocols and platform dialects to describe w3c/wot-binding-templates#1 (3 comments by @draggett, @mjkoster, @mmccool)
-
Structure of protocol binding block and terminology w3c/wot-binding-templates#2 (1 comment by @mjkoster)
-
-
1 pull request opened.
-
Initial spec draft w3c/wot-binding-templates#5, by @mjkoster.
-
w3c/wotwg
-
1 pull request opened.
-
Add contribution workflow guidelines w3c/wotwg#5, by @zolkis.
-
-
1 pull request merged.
-
Add contribution workflow guidelines w3c/wotwg#5.
-
-
1 pull request received 4 new comments.
Participants
-
1 participant left.
-
Yingying Chen (W3C) left.
-
-
1 organization joined.
-
Baidu, Inc. joined.
-
-
1 organization left.
-
Baidu, Inc. left.
-
GitHub
w3c/wot-scripting-api
-
4 issues opened.
-
Dynamic Management Things - Management TD for each installed script w3c/wot-scripting-api#36, by @mjkoster.
-
Management Thing - verb semantics clarification w3c/wot-scripting-api#35, by @mmccool.
-
Management Thing - update verb w3c/wot-scripting-api#33, by @mmccool.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
ManagerThing&ReverseProxy w3c/wot-scripting-api#32, by @knimura.
-
Add examples to the Scripting API spec w3c/wot-scripting-api#31, by @zolkis.
-
-
1 pull request merged.
-
Add examples to the Scripting API spec w3c/wot-scripting-api#31.
-
-
1 pull request received 2 new comments.
w3c/wot-thing-description
-
9 issues opened.
-
Content negotiation for TD namespace w3c/wot-thing-description#20, by @draggett.
-
Best practices for standardising Linked Data Vocabularies w3c/wot-thing-description#19, by @draggett.
-
TD and iot.schema.org w3c/wot-thing-description#18, by @sebastiankb.
-
TD Events w3c/wot-thing-description#17, by @sebastiankb.
-
TD Serializations w3c/wot-thing-description#16, by @sebastiankb.
-
Metadata for protocol bindings w3c/wot-thing-description#15, by @sebastiankb.
-
TD Data Types w3c/wot-thing-description#14, by @sebastiankb.
-
Data types for interaction models for things w3c/wot-thing-description#13, by @draggett.
-
Properties, actions and events w3c/wot-thing-description#12, by @benfrancis.
-
-
5 issues received 38 new comments.
-
Properties, actions and events w3c/wot-thing-description#12 (30 comments by @benfrancis, @danielpeintner, @draggett, @mkovatsc, @sebastiankb, @vcharpenay)
-
Best practices for standardising Linked Data Vocabularies w3c/wot-thing-description#19 (3 comments by @draggett, @vcharpenay)
-
-
2 pull requests opened.
-
add semantic test-data w3c/wot-thing-description#11, by @danielpeintner.
-
Add OCF binding template examples to test-bed w3c/wot-thing-description#10, by @danielpeintner.
-
-
2 pull requests merged.
-
Add OCF binding template examples to test-bed w3c/wot-thing-description#10.
-
Test bed w3c/wot-thing-description#8.
-
w3c/wot-binding-templates
-
1 issue opened.
-
Structure of protocol binding block and terminology w3c/wot-binding-templates#2, by @Kazuo-Kajimoto.
-
-
1 issue received 1 new comment.
-
Structure of protocol binding block and terminology w3c/wot-binding-templates#2 (1 comment by @Kazuo-Kajimoto)
-
w3c/wot-architecture
-
2 issues opened.
-
Structure of protocol binding block and therminology w3c/wot-architecture#5, by @Kazuo-Kajimoto.
-
Must close IG architecture draft w3c/wot-architecture#4, by @mkovatsc.
-
-
3 issues closed.
-
Structure of protocol binding block and therminology w3c/wot-architecture#5.
-
Two separate layers for the Protocol Binding mechanism w3c/wot-architecture#3.
-
Typo / Disambiguation w3c/wot-architecture#1.
-
-
4 issues received 9 new comments.
-
Two separate layers for the Protocol Binding mechanism w3c/wot-architecture#3 (5 comments by @Kazuo-Kajimoto, @mkovatsc, @takuki)
-
Structure of protocol binding block and therminology w3c/wot-architecture#5 (1 comment by @Kazuo-Kajimoto)
-
w3c/wotwg
-
1 pull request merged.
-
Add WoT WG github repository links. w3c/wotwg#4.
-
Participants
-
1 organization joined.
-
Baidu, Inc. joined.
-
GitHub
w3c/wot-architecture
-
1 issue opened.
-
Two separate layers for the Protocol Binding mechanism w3c/wot-architecture#3, by @ashimura.
-
-
1 issue received 1 new comment.
-
Two separate layers for the Protocol Binding mechanism w3c/wot-architecture#3 (1 comment by @Tomoaki-Mizushima)
-
w3c/wot-thing-description
-
1 issue opened.
-
[TF-TD] href in DataSchema w3c/wot-thing-description#9, by @mariapoveda.
-
-
3 issues closed.
-
Adding Semantic Annotations to JSON Schema w3c/wot-thing-description#5.
-
Specify the expected type of JSON TD structures w3c/wot-thing-description#7.
-
All the figures of the document are missing w3c/wot-thing-description#1.
-
-
5 issues received 8 new comments.
-
Specify the expected type of JSON TD structures w3c/wot-thing-description#7 (4 comments by @danielpeintner, @sebastiankb, @takuki)
-
[TF-TD] Namespaces used in the TD / WoT ontology w3c/wot-thing-description#3 (1 comment by @sebastiankb)
-
-
1 pull request merged.
-
added folder for vocabulary files w3c/wot-thing-description#4.
-
-
1 pull request reopened.
-
added folder for vocabulary files w3c/wot-thing-description#4, by @mariapoveda.
-
-
1 pull request received 7 new comments.
-
added folder for vocabulary files w3c/wot-thing-description#4 (7 comments by @draggett, @mariapoveda, @sebastiankb)
-
w3c/wot-scripting-api
-
3 issues opened.
-
Reaching out to Architecture TF w3c/wot-scripting-api#30, by @h0ru5.
-
Metadata related to a script to let a runtime decide in which execution context it should run w3c/wot-scripting-api#29, by @h0ru5.
-
Synchronization use cases w3c/wot-scripting-api#28, by @zolkis.
-
-
2 issues received 12 new comments.
-
Synchronization use cases w3c/wot-scripting-api#28 (10 comments by @knimura, @mjkoster, @mkovatsc, @zolkis)
-
Metadata related to a script to let a runtime decide in which execution context it should run w3c/wot-scripting-api#29 (2 comments by @h0ru5)
-
Participants
-
3 organizations joined.
-
Internet Research Institute, Inc. joined.
-
RWE AG joined.
-
Hitachi, Ltd. joined.
-
GitHub
w3c/wot-scripting-api
-
3 issues opened.
-
policies of security enforcement in the scripting runtime w3c/wot-scripting-api#26, by @h0ru5.
-
Isolation of scripts / sandbox and access to outside w3c/wot-scripting-api#25, by @h0ru5.
-
Define TD for script manager Thing w3c/wot-scripting-api#23, by @zolkis.
-
-
6 issues closed.
-
Define UA/runtime for WoT w3c/wot-scripting-api#2.
-
Script management vs Thing management w3c/wot-scripting-api#22.
-
Adding readonly properties through ExposedThing interface w3c/wot-scripting-api#18.
-
Refactor Discovery API w3c/wot-scripting-api#17.
-
There are no way to stop thing discovering using ThingFilter + ThingCallback w3c/wot-scripting-api#16.
-
``ExposedThing`` and ``DynamicThing`` w3c/wot-scripting-api#14.
-
-
8 issues received 15 new comments.
-
Define TD for script manager Thing w3c/wot-scripting-api#23 (8 comments by @h0ru5, @mmccool, @zolkis)
-
Adding readonly properties through ExposedThing interface w3c/wot-scripting-api#18 (1 comment by @zolkis)
-
There are no way to stop thing discovering using ThingFilter + ThingCallback w3c/wot-scripting-api#16 (1 comment by @zolkis)
-
-
2 pull requests opened.
-
Fix WebIDL error. w3c/wot-scripting-api#27, by @zolkis.
-
added draft typescript definitions w3c/wot-scripting-api#24, by @h0ru5.
-
-
3 pull requests merged.
-
Fix WebIDL error. w3c/wot-scripting-api#27.
-
added draft typescript definitions w3c/wot-scripting-api#24.
-
Update WoT runtime, discovery, ExposedThing, ConsumedThing. w3c/wot-scripting-api#21.
-
-
3 pull requests received 9 new comments.
-
Update WoT runtime, discovery, ExposedThing, ConsumedThing. w3c/wot-scripting-api#21 (2 comments by @h0ru5)
w3c/wot-thing-description
-
2 issues opened.
-
Specify the expected type of JSON TD structures w3c/wot-thing-description#7, by @danielpeintner.
-
Adding Semantic Annotations to JSON Schema w3c/wot-thing-description#5, by @vcharpenay.
-
-
3 issues received 4 new comments.
-
[TF-TD] Namespaces used in the TD / WoT ontology w3c/wot-thing-description#3 (2 comments by @mmccool, @sebastiankb)
-
Specify the expected type of JSON TD structures w3c/wot-thing-description#7 (1 comment by @draggett)
-
All the figures of the document are missing w3c/wot-thing-description#1 (1 comment by @danielpeintner)
-
-
3 pull requests opened.
-
Test bed w3c/wot-thing-description#8, by @danielpeintner.
-
add missing figures after copying the content from current practices w3c/wot-thing-description#6, by @danielpeintner.
-
added folder for vocabulary files w3c/wot-thing-description#4, by @mariapoveda.
-
-
1 pull request merged.
-
add missing figures after copying the content from current practices w3c/wot-thing-description#6.
-
w3c/wot-binding-templates
-
1 issue opened.
-
Start list of protocols and platform dialects to describe w3c/wot-binding-templates#1, by @mkovatsc.
-
-
1 issue received 2 new comments.
-
Start list of protocols and platform dialects to describe w3c/wot-binding-templates#1 (2 comments by @mkovatsc, @zhangyongjing)
-
w3c/wotwg
-
1 pull request opened.
-
Add WoT WG github repository links. w3c/wotwg#4, by @zolkis.
-
w3c/wot-architecture
-
1 pull request merged.
-
fix a typo w3c/wot-architecture#2.
-
Participants
-
3 organizations joined.
-
Technische Universitaet Berlin joined.
-
Aalto University joined.
-
Panasonic Corporation joined.
-
GitHub
w3c/wot-thing-description
-
3 issues opened.
-
[TF-TD] Namespaces used in the TD / WoT ontology w3c/wot-thing-description#3, by @danicic.
-
[TF-TD] binary encodings w3c/wot-thing-description#2, by @sebastiankb.
-
All the figures of the document are missing w3c/wot-thing-description#1, by @onovo1.
-
-
2 issues received 6 new comments.
-
[TF-TD] Namespaces used in the TD / WoT ontology w3c/wot-thing-description#3 (2 comments by @danicic, @danielpeintner)
w3c/wot-scripting-api
-
4 issues opened.
-
Script management vs Thing management w3c/wot-scripting-api#22, by @zolkis.
-
Adding readonly properties through ExposedThing interface w3c/wot-scripting-api#18, by @zolkis.
-
Refactor Discovery API w3c/wot-scripting-api#17, by @zolkis.
-
There are no way to stop thing discovering using ThingFilter + ThingCallback w3c/wot-scripting-api#16, by @zolkis.
-
-
1 issue closed.
-
Rationale.md w3c/wot-scripting-api#15.
-
-
6 issues received 39 new comments.
-
Adding readonly properties through ExposedThing interface w3c/wot-scripting-api#18 (3 comments by @h0ru5, @zolkis)
-
There are no way to stop thing discovering using ThingFilter + ThingCallback w3c/wot-scripting-api#16 (2 comments by @zolkis)
-
3 pull requests opened.
-
Update WoT runtime, discovery, ExposedThing, ConsumedThing. w3c/wot-scripting-api#21, by @zolkis.
-
adding readOnly entry for Property initializer w3c/wot-scripting-api#20, by @h0ru5.
-
add primer document w3c/wot-scripting-api#19, by @knimura.
-
-
2 pull requests merged.
-
adding readOnly entry for Property initializer w3c/wot-scripting-api#20.
-
add primer document w3c/wot-scripting-api#19.
-
-
3 pull requests received 42 new comments.
-
Update WoT runtime, discovery, ExposedThing, ConsumedThing. w3c/wot-scripting-api#21 (32 comments by @h0ru5, @zolkis)
-
adding readOnly entry for Property initializer w3c/wot-scripting-api#20 (7 comments by @h0ru5, @zolkis)
-
w3c/wot-architecture
-
1 issue opened.
-
Typo / Disambiguation w3c/wot-architecture#1, by @smalich.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
fix a typo w3c/wot-architecture#2, by @knimura.
-
w3c/wotwg
-
2 issues opened.
-
Define WoT Runtime and Application w3c/wotwg#3, by @zolkis.
-
Add security directory w3c/wotwg#2, by @zolkis.
-
-
1 issue received 1 new comment.
Participants
-
2 organizations joined.
-
German Research Center for Artificial Intelligence (DFKI) Gmbh joined.
-
Alibaba Group joined.
-
GitHub
w3c/wot-scripting-api
-
3 issues opened.
-
Rationale.md w3c/wot-scripting-api#15, by @knimura.
-
``ExposedThing`` and ``DynamicThing`` w3c/wot-scripting-api#14, by @h0ru5.
-
Add use cases w3c/wot-scripting-api#6, by @knimura.
-
-
1 issue closed.
-
Use constructors for WoT objects w3c/wot-scripting-api#3.
-
-
6 issues received 45 new comments.
-
Define UA/runtime for WoT w3c/wot-scripting-api#2 (18 comments by @draggett, @h0ru5, @knimura, @zolkis)
-
Use constructors for WoT objects w3c/wot-scripting-api#3 (7 comments by @domenic, @h0ru5, @mkovatsc, @zolkis)
-
``ExposedThing`` and ``DynamicThing`` w3c/wot-scripting-api#14 (6 comments by @h0ru5, @knimura, @zolkis)
-
-
7 pull requests opened.
-
delete bogus directory w3c/wot-scripting-api#13, by @zolkis.
-
update rationale w3c/wot-scripting-api#12, by @knimura.
-
update rationale w3c/wot-scripting-api#11, by @knimura.
-
update rationale w3c/wot-scripting-api#10, by @knimura.
-
update rationale w3c/wot-scripting-api#9, by @knimura.
-
update rationale w3c/wot-scripting-api#8, by @knimura.
-
Add use cases. Refactor WebIDL. w3c/wot-scripting-api#7, by @zolkis.
-
-
5 pull requests merged.
-
delete bogus directory w3c/wot-scripting-api#13.
-
update rationale w3c/wot-scripting-api#12.
-
update rationale w3c/wot-scripting-api#8.
-
Add use cases. Refactor WebIDL. w3c/wot-scripting-api#7.
-
added use cases as discussed in scripting call w3c/wot-scripting-api#4.
-
-
3 pull requests closed.
-
update rationale w3c/wot-scripting-api#11.
-
update rationale w3c/wot-scripting-api#10.
-
update rationale w3c/wot-scripting-api#9.
-
-
1 pull request reopened.
-
update rationale w3c/wot-scripting-api#10, by @knimura.
-
-
3 pull requests received 12 new comments.
-
added use cases as discussed in scripting call w3c/wot-scripting-api#4 (3 comments by @h0ru5, @zolkis)
Participants
-
3 organizations joined.
-
Inria joined.
-
EVRYTHNG joined.
-
Fujitsu Limited joined.
-
GitHub
w3c/wot-scripting-api
-
3 issues opened.
-
Use Observables instead of callbacks? w3c/wot-scripting-api#5, by @zolkis.
-
Use constructors for WoT objects w3c/wot-scripting-api#3, by @zolkis.
-
Define UA/runtime for WoT w3c/wot-scripting-api#2, by @zolkis.
-
-
3 issues received 12 new comments.
-
Use constructors for WoT objects w3c/wot-scripting-api#3 (7 comments by @draggett, @knimura, @tobie, @zolkis)
-
-
2 pull requests opened.
-
added use cases as discussed in scripting call w3c/wot-scripting-api#4, by @h0ru5.
-
Initial version. w3c/wot-scripting-api#1, by @zolkis.
-
-
1 pull request merged.
-
Initial version. w3c/wot-scripting-api#1.
-
-
1 pull request received 5 new comments.
Participants
-
14 organizations joined.
-
Department of Informatics, PUC-Rio joined.
-
British Broadcasting Corporation joined.
-
Software AG joined.
-
Huawei joined.
-
Universidad Politécnica de Madrid joined.
-
MindX joined.
-
ACCESS CO., LTD. joined.
-
ERICSSON joined.
-
Korea Electronics Technology Institute (KETI) joined.
-
Electronics and Telecommunications Research Institute (ETRI) joined.
-
Siemens AG joined.
-
Media Access Australia joined.
-
TPGi joined.
-
Blockstream joined.
-
GitHub
w3c/wotwg
-
1 issue opened.
-
WoT WG page clean up w3c/wotwg#1, by @ashimura.
-
-
1 issue received 1 new comment.