Web of Things Working Group - Activity in 2018
No matches.
TR publications
-
1 document published.
GitHub
w3c/wot-thing-description
-
11 issues opened.
-
confused in using JSON-LD w3c/wot-thing-description#335, by @PaulJeong14.
-
In section 5.4, CoAP, MQTT are refered. w3c/wot-thing-description#334, by @PaulJeong14.
-
TD Event in Thing-to-Thing interactions w3c/wot-thing-description#333, by @AndreMaz.
-
Typo at Appendix B ("definea") w3c/wot-thing-description#332, by @ashimura.
-
Require UTF-8 encoding of TDs w3c/wot-thing-description#331, by @mmccool.
-
readOnly and writeOnly should be optional for action parameters w3c/wot-thing-description#322, by @mlagally.
-
Assertion/Schema mismatch for td-{property,event,action}-arrays w3c/wot-thing-description#321, by @mmccool.
-
Example 1 missing contentType w3c/wot-thing-description#319, by @egekorkan.
-
writeOnly and readOnly examples w3c/wot-thing-description#318, by @egekorkan.
-
id term is missing w3c/wot-thing-description#317, by @sebastiankb.
-
Relation ObjectSchema to DataSchema should be 0..N w3c/wot-thing-description#315, by @LukasFritzeDev.
-
-
11 issues closed.
-
Update information model figures to account for Security Definitions w3c/wot-thing-description#289.
-
Automatic generation of diagrams (Sec. 5.1) w3c/wot-thing-description#276.
-
Clarify whether security is mandatory w3c/wot-thing-description#230.
-
Fix formatting of autogenerated section 5 w3c/wot-thing-description#206.
-
Example 1 missing contentType w3c/wot-thing-description#319.
-
Do we include securityDefinitions? w3c/wot-thing-description#145.
-
TD and iot.schema.org w3c/wot-thing-description#18.
-
writeOnly and readOnly examples w3c/wot-thing-description#318.
-
Rename of label to title and enum titles 'oneOf' w3c/wot-thing-description#156.
-
RFC 8259 (JSON) does not define "keys", but names w3c/wot-thing-description#194.
-
Term "form" left in Example w3c/wot-thing-description#313.
-
-
1 issue reopened.
-
id term is missing w3c/wot-thing-description#317, by @sebastiankb.
-
-
45 issues received 99 new comments.
-
Internationalization (i18n) of human-readable TD fields w3c/wot-thing-description#161 (9 comments by @mlagally, @sebastiankb, @takuki, @ToruKawaguchi)
-
Delete writeOnly w3c/wot-thing-description#266 (8 comments by @danielpeintner, @draggett, @handrews, @mmccool, @sebastiankb)
-
readOnly and writeOnly should be optional for action parameters w3c/wot-thing-description#322 (7 comments by @mkovatsc, @mlagally, @mmccool, @sebastiankb)
-
Clarify type value of "null" for properties w3c/wot-thing-description#222 (4 comments by @handrews, @mlagally, @sebastiankb)
-
Allow Form's "rel" to be a string or an array w3c/wot-thing-description#236 (4 comments by @mlagally, @sebastiankb, @vcharpenay)
-
Error conditions for form requests w3c/wot-thing-description#303 (4 comments by @draggett, @mlagally, @sebastiankb)
-
clarify semantics of actions w3c/wot-thing-description#213 (4 comments by @benfrancis, @draggett, @mlagally)
-
support term should be a URI type w3c/wot-thing-description#310 (4 comments by @mmccool, @sebastiankb, @takuki)
-
Thing Interfaces / Thing Models w3c/wot-thing-description#279 (3 comments by @mlagally, @sebastiankb, @ToruKawaguchi)
-
Model possible responses in forms w3c/wot-thing-description#250 (3 comments by @sebastiankb, @takuki)
-
read and write property : different payload formats w3c/wot-thing-description#238 (2 comments by @mlagally, @sebastiankb)
-
A way to read all Properties at once? w3c/wot-thing-description#151 (2 comments by @mkovatsc, @takuki)
-
Relation ObjectSchema to DataSchema should be 0..N w3c/wot-thing-description#315 (2 comments by @sebastiankb)
-
Assertion/Schema mismatch for td-{property,event,action}-arrays w3c/wot-thing-description#321 (2 comments by @sebastiankb)
-
Identifiers for Properties, Actions, Events w3c/wot-thing-description#292 (2 comments by @draggett, @mmccool)
-
Automatic generation of diagrams (Sec. 5.1) w3c/wot-thing-description#276 (2 comments by @sebastiankb, @takuki)
-
Example 1 missing contentType w3c/wot-thing-description#319 (2 comments by @egekorkan, @sebastiankb)
-
Rename of label to title and enum titles 'oneOf' w3c/wot-thing-description#156 (2 comments by @sebastiankb, @takuki)
-
RFC 8259 (JSON) does not define "keys", but names w3c/wot-thing-description#194 (2 comments by @sebastiankb, @takuki)
-
Include JSON Schema's "anyOf", "allOf" and "not"? w3c/wot-thing-description#298 (1 comment by @mmccool)
-
Update information model figures to account for Security Definitions w3c/wot-thing-description#289 (1 comment by @mmccool)
-
Allow "security" to include both SecurityScheme objects and declared identifiers w3c/wot-thing-description#300 (1 comment by @mmccool)
-
Same description of `identity` field in CertSecurityScheme/PublicSecurityScheme/PSKSecurityScheme w3c/wot-thing-description#233 (1 comment by @sebastiankb)
-
Namespaces: clarify if HTTP namespace is normative w3c/wot-thing-description#210 (1 comment by @sebastiankb)
-
Add overridable global default value(s) for mediaType w3c/wot-thing-description#204 (1 comment by @sebastiankb)
-
Clarify relationship of security schemes between WoT and OpenAPI w3c/wot-thing-description#201 (1 comment by @sebastiankb)
-
Metadata fields in Thing (mandatory and optional) w3c/wot-thing-description#142 (1 comment by @takuki)
-
-
11 pull requests opened.
-
Update MultiLanguage w3c/wot-thing-description#330, by @yamagile.
-
add tabbed example for Example 1 (Simple vs Full) w3c/wot-thing-description#329, by @danielpeintner.
-
add full Tab Example for Example 1 w3c/wot-thing-description#328, by @danielpeintner.
-
Use BCP 47 for language identification w3c/wot-thing-description#327, by @takuki.
-
Updated Recent Changes section. w3c/wot-thing-description#326, by @takuki.
-
Added missing 'id' field w3c/wot-thing-description#325, by @vcharpenay.
-
remove writable key from property interaction type and remove readOnly and writeOnly from the required list w3c/wot-thing-description#324, by @egekorkan.
-
Remove writeOnly and readOnly from the required list w3c/wot-thing-description#323, by @egekorkan.
-
Update validation schema according to changes of Lyon TPAC w3c/wot-thing-description#320, by @egekorkan.
-
Updated Recent Changes section. w3c/wot-thing-description#316, by @takuki.
-
Implementation Report: Dec 2018 Test Fest Results w3c/wot-thing-description#314, by @mmccool.
-
-
10 pull requests merged.
-
Implementation Report: Dec 2018 Test Fest Results w3c/wot-thing-description#314.
-
add tabbed example for Example 1 (Simple vs Full) w3c/wot-thing-description#329.
-
Use BCP 47 for language identification w3c/wot-thing-description#327.
-
Added missing 'id' field w3c/wot-thing-description#325.
-
Thing templates, including examples w3c/wot-thing-description#299.
-
remove writable key from property interaction type and remove readOnly and writeOnly from the required list w3c/wot-thing-description#324.
-
Updated Recent Changes section. w3c/wot-thing-description#326.
-
Remove writeOnly and readOnly from the required list w3c/wot-thing-description#323.
-
Update validation schema according to changes of Lyon TPAC w3c/wot-thing-description#320.
-
Updated Recent Changes section. w3c/wot-thing-description#316.
-
-
1 pull request closed.
-
add full Tab Example for Example 1 w3c/wot-thing-description#328.
-
-
2 pull requests received 3 new comments.
-
remove writable key from property interaction type and remove readOnly and writeOnly from the required list w3c/wot-thing-description#324 (2 comments by @egekorkan, @sebastiankb)
-
Implementation Report: Dec 2018 Test Fest Results w3c/wot-thing-description#314 (1 comment by @mmccool)
-
w3c/wot-scripting-api
-
2 issues received 2 new comments.
-
URI Templates / Variables (Alignment with Binding&TD) w3c/wot-scripting-api#149 (1 comment by @danielpeintner)
-
w3c/wot-security
-
2 issues received 4 new comments.
w3c/wot-binding-templates
-
1 issue received 2 new comments.
w3c/wot-architecture
-
1 pull request opened.
-
Adding WoT runtime risks to S&P section w3c/wot-architecture#63, by @ereshetova.
-
-
1 pull request received 3 new comments.
-
Adding WoT runtime risks to S&P section w3c/wot-architecture#63 (3 comments by @ereshetova, @zolkis)
-
w3c/wotwg
-
1 issue received 1 new comment.
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
-
1 organization joined.
-
Tencent joined.
-
GitHub
w3c/wot-thing-description
-
25 issues opened.
-
Term "form" left in Example w3c/wot-thing-description#313, by @danielpeintner.
-
top level assertions w3c/wot-thing-description#312, by @draggett.
-
Extensible metadata fields w3c/wot-thing-description#311, by @mlagally.
-
support term should be a URI type w3c/wot-thing-description#310, by @sebastiankb.
-
Is the use of "$ref" and "definitions" allowed in TD ? w3c/wot-thing-description#307, by @ToruKawaguchi.
-
Form contentType vs. Link type w3c/wot-thing-description#306, by @benfrancis.
-
Binary Properties w3c/wot-thing-description#305, by @benfrancis.
-
Error conditions for form requests w3c/wot-thing-description#303, by @benfrancis.
-
How do you cancel or query the state of an action request? w3c/wot-thing-description#302, by @benfrancis.
-
Assertions should be self-contained w3c/wot-thing-description#301, by @mmccool.
-
Allow "security" to include both SecurityScheme objects and declared identifiers w3c/wot-thing-description#300, by @mmccool.
-
Include JSON Schema's "anyOf", "allOf" and "not"? w3c/wot-thing-description#298, by @vcharpenay.
-
Property names should be singular w3c/wot-thing-description#297, by @maximelefrancois86.
-
td:scope is used but does not defined w3c/wot-thing-description#296, by @maximelefrancois86.
-
range of jsonschema:minimum and jsonschema:maximum w3c/wot-thing-description#295, by @maximelefrancois86.
-
Do vocabulary terms have a JSON key representation? w3c/wot-thing-description#293, by @maximelefrancois86.
-
Identifiers for Properties, Actions, Events w3c/wot-thing-description#292, by @maximelefrancois86.
-
Testing Clarifications w3c/wot-thing-description#291, by @mkovatsc.
-
Update information model figures to account for Security Definitions w3c/wot-thing-description#289, by @mmccool.
-
Copy paste error in the description in Example 21 w3c/wot-thing-description#288, by @mlagally.
-
Fix links on the HTML documentation of wot-security and json-schema vocabularies w3c/wot-thing-description#287, by @vcharpenay.
-
Spelling mistake in "Section 5.2.4 Events" description w3c/wot-thing-description#283, by @srirama179.
-
Vocabulary change: InteractionPattern to Affordance w3c/wot-thing-description#282, by @vcharpenay.
-
Assertions for namespace / JSON-LD context file w3c/wot-thing-description#280, by @mlagally.
-
Thing Interfaces / Thing Models w3c/wot-thing-description#279, by @mlagally.
-
-
8 issues closed.
-
Binary Properties w3c/wot-thing-description#305.
-
Split TD into abstract interaction model and protocol binding w3c/wot-thing-description#91.
-
Simplified TD: schema w3c/wot-thing-description#107.
-
TD model figure shows wrong cardinalities when serialization has default values w3c/wot-thing-description#184.
-
Copy paste error in the description in Example 21 w3c/wot-thing-description#288.
-
Spelling mistake in "Section 5.2.4 Events" description w3c/wot-thing-description#283.
-
TD Serializations w3c/wot-thing-description#16.
-
Stray mentions of "rel" under "forms" w3c/wot-thing-description#267.
-
-
1 issue reopened.
-
td:scope is used but does not defined w3c/wot-thing-description#296, by @maximelefrancois86.
-
-
45 issues received 173 new comments.
-
How do you cancel or query the state of an action request? w3c/wot-thing-description#302 (14 comments by @benfrancis, @draggett, @mkovatsc)
-
Alignment with SOSA/SSN (and iot.schema.org) w3c/wot-thing-description#259 (14 comments by @mariapoveda, @maximelefrancois86, @mjkoster, @mkovatsc, @takuki, @vcharpenay)
-
A way to read all Properties at once? w3c/wot-thing-description#151 (11 comments by @benfrancis, @draggett, @handrews, @mkovatsc, @sebastiankb, @zolkis)
-
Delete writeOnly w3c/wot-thing-description#266 (11 comments by @handrews, @mkovatsc, @mlagally, @mmccool)
-
Assertions for namespace / JSON-LD context file w3c/wot-thing-description#280 (10 comments by @maximelefrancois86, @mkovatsc, @mlagally, @takuki, @vcharpenay)
-
Inputs in Events Definition w3c/wot-thing-description#231 (10 comments by @draggett, @mkovatsc, @takuki, @zolkis)
-
Internationalization (i18n) of human-readable TD fields w3c/wot-thing-description#161 (8 comments by @handrews, @mkovatsc, @sebastiankb)
-
Testing Clarifications w3c/wot-thing-description#291 (8 comments by @ashimura, @draggett, @mkovatsc, @mmccool)
-
Vocabulary change: InteractionPattern to Affordance w3c/wot-thing-description#282 (7 comments by @hibaymj, @mariapoveda, @mkovatsc, @takuki, @vcharpenay)
-
Automatic generation of diagrams (Sec. 5.1) w3c/wot-thing-description#276 (6 comments by @sebastiankb, @takuki, @vcharpenay)
-
Property names should be singular w3c/wot-thing-description#297 (6 comments by @draggett, @maximelefrancois86, @mmccool, @zolkis)
-
Semantic Annotation in the Thing Description w3c/wot-thing-description#263 (5 comments by @maximelefrancois86, @mkovatsc, @takuki)
-
Is the use of "$ref" and "definitions" allowed in TD ? w3c/wot-thing-description#307 (5 comments by @egekorkan, @handrews, @mmccool, @sebastiankb, @ToruKawaguchi)
-
Thing Interfaces / Thing Models w3c/wot-thing-description#279 (5 comments by @mlagally, @sebastiankb)
-
Model possible responses in forms w3c/wot-thing-description#250 (4 comments by @mkovatsc, @sebastiankb)
-
Error conditions for form requests w3c/wot-thing-description#303 (4 comments by @draggett, @handrews, @mlagally)
-
Do vocabulary terms have a JSON key representation? w3c/wot-thing-description#293 (3 comments by @mkovatsc, @sebastiankb)
-
clarify semantics of actions w3c/wot-thing-description#213 (3 comments by @draggett, @mlagally, @sebastiankb)
-
Identifiers for Properties, Actions, Events w3c/wot-thing-description#292 (3 comments by @draggett, @mkovatsc, @vcharpenay)
-
read and write property : different payload formats w3c/wot-thing-description#238 (3 comments by @mkovatsc, @mlagally)
-
support term should be a URI type w3c/wot-thing-description#310 (2 comments by @danielpeintner, @sebastiankb)
-
Clarify type value of "null" for properties w3c/wot-thing-description#222 (2 comments by @sebastiankb)
-
On Links, RFC 8288, and the RDF representation of Links w3c/wot-thing-description#262 (2 comments by @maximelefrancois86, @mkovatsc)
-
WoT Security Ontology incorrectly linked w3c/wot-thing-description#257 (2 comments by @draggett, @sebastiankb)
-
Update information model figures to account for Security Definitions w3c/wot-thing-description#289 (1 comment by @sebastiankb)
-
Allow "security" to include both SecurityScheme objects and declared identifiers w3c/wot-thing-description#300 (1 comment by @mmccool)
-
Rename of label to title and enum titles 'oneOf' w3c/wot-thing-description#156 (1 comment by @sebastiankb)
-
Split TD into abstract interaction model and protocol binding w3c/wot-thing-description#91 (1 comment by @sebastiankb)
-
TD model figure shows wrong cardinalities when serialization has default values w3c/wot-thing-description#184 (1 comment by @sebastiankb)
-
Allow Form's "rel" to be a string or an array w3c/wot-thing-description#236 (1 comment by @sebastiankb)
-
Copy paste error in the description in Example 21 w3c/wot-thing-description#288 (1 comment by @sebastiankb)
-
Spelling mistake in "Section 5.2.4 Events" description w3c/wot-thing-description#283 (1 comment by @sebastiankb)
-
-
12 pull requests opened.
-
Testing: script to merge test results w3c/wot-thing-description#309, by @mmccool.
-
Added panasonic.html to testing/implementations w3c/wot-thing-description#308, by @ToruKawaguchi.
-
Added automatic rendering of figures w3c/wot-thing-description#304, by @vcharpenay.
-
Thing templates, including examples w3c/wot-thing-description#299, by @mlagally.
-
Yet another update to the implementation report generator w3c/wot-thing-description#294, by @mmccool.
-
Even More Updates to Implementation Report Generator w3c/wot-thing-description#290, by @mmccool.
-
Updated Implementation Report Generator w3c/wot-thing-description#286, by @mmccool.
-
Generate Test/Implementation Report w3c/wot-thing-description#285, by @mmccool.
-
Update/Redo Security Definitions w3c/wot-thing-description#284, by @mmccool.
-
Added a link from Changes section to security section (6.1.7) for the latest change w3c/wot-thing-description#281, by @takuki.
-
Template for Implementation Report w3c/wot-thing-description#278, by @mmccool.
-
Security definitions w3c/wot-thing-description#277, by @mmccool.
-
-
15 pull requests merged.
-
Testing: script to merge test results w3c/wot-thing-description#309.
-
Yet another update to the implementation report generator w3c/wot-thing-description#294.
-
Added automatic rendering of figures w3c/wot-thing-description#304.
-
Added panasonic.html to testing/implementations w3c/wot-thing-description#308.
-
Even More Updates to Implementation Report Generator w3c/wot-thing-description#290.
-
Updated Implementation Report Generator w3c/wot-thing-description#286.
-
Update/Redo Security Definitions w3c/wot-thing-description#284.
-
Security Considerations section w3c/wot-thing-description#207.
-
Security scopes example w3c/wot-thing-description#269.
-
Remove URL postfixes from all security terms w3c/wot-thing-description#268.
-
Generate Test/Implementation Report w3c/wot-thing-description#285.
-
Added a link from Changes section to security section (6.1.7) for the latest change w3c/wot-thing-description#281.
-
Security cleanup w3c/wot-thing-description#265.
-
Security definitions w3c/wot-thing-description#277.
-
Template for Implementation Report w3c/wot-thing-description#278.
-
-
3 pull requests closed.
-
Added axioms to the JSON schema vocab for readOnly, writeOnly w3c/wot-thing-description#264.
-
Oracle Review Comments on TD spec draft / Device model chapter w3c/wot-thing-description#205.
-
TD and datatypes diagram w3c/wot-thing-description#150.
-
-
1 pull request reopened.
-
Oracle Review Comments on TD spec draft / Device model chapter w3c/wot-thing-description#205, by @mlagally.
-
-
15 pull requests received 38 new comments.
-
Security Considerations section w3c/wot-thing-description#207 (8 comments by @mmccool, @sebastiankb, @takuki)
-
Yet another update to the implementation report generator w3c/wot-thing-description#294 (3 comments by @mmccool)
-
Oracle Review Comments on TD spec draft / Device model chapter w3c/wot-thing-description#205 (3 comments by @mlagally, @sebastiankb)
-
Update/Redo Security Definitions w3c/wot-thing-description#284 (3 comments by @mmccool, @sebastiankb)
-
Remove URL postfixes from all security terms w3c/wot-thing-description#268 (3 comments by @mmccool, @sebastiankb)
-
Thing templates, including examples w3c/wot-thing-description#299 (2 comments by @mlagally, @sebastiankb)
-
Added automatic rendering of figures w3c/wot-thing-description#304 (2 comments by @mmccool, @sebastiankb)
-
Added axioms to the JSON schema vocab for readOnly, writeOnly w3c/wot-thing-description#264 (2 comments by @sebastiankb, @vcharpenay)
-
Added panasonic.html to testing/implementations w3c/wot-thing-description#308 (1 comment by @mmccool)
-
Even More Updates to Implementation Report Generator w3c/wot-thing-description#290 (1 comment by @mmccool)
-
Added a link from Changes section to security section (6.1.7) for the latest change w3c/wot-thing-description#281 (1 comment by @mmccool)
-
w3c/wot-scripting-api
-
3 issues opened.
-
Align with TD (name/value pairs) w3c/wot-scripting-api#157, by @danielpeintner.
-
Produce() method should ignore instance specific information w3c/wot-scripting-api#156, by @egekorkan.
-
Exposing notifications, subscribe, unsubscribe w3c/wot-scripting-api#153, by @zolkis.
-
-
1 issue closed.
-
API must allow to specify concrete media type w3c/wot-scripting-api#112.
-
-
1 issue reopened.
-
API must allow to specify concrete media type w3c/wot-scripting-api#112, by @zolkis.
-
-
4 issues received 23 new comments.
-
Exposing notifications, subscribe, unsubscribe w3c/wot-scripting-api#153 (10 comments by @draggett, @zolkis)
-
Produce() method should ignore instance specific information w3c/wot-scripting-api#156 (9 comments by @egekorkan, @zolkis)
-
API must allow to specify concrete media type w3c/wot-scripting-api#112 (3 comments by @egekorkan, @zolkis)
-
-
2 pull requests opened.
-
Rewriting S&P section without normative statements w3c/wot-scripting-api#155, by @ereshetova.
-
Typescript update w3c/wot-scripting-api#154, by @mkovatsc.
-
-
2 pull requests merged.
-
Typescript update w3c/wot-scripting-api#154.
-
move https://github.com/thingweb/wot-typescript-definitions to scripting repo w3c/wot-scripting-api#152.
-
-
1 pull request received 16 new comments.
-
Rewriting S&P section without normative statements w3c/wot-scripting-api#155 (16 comments by @danielpeintner, @ereshetova, @zolkis)
-
w3c/wot-security
-
4 issues opened.
-
Support both strings and SecurityScheme objects in "security" fields w3c/wot-security#122, by @mmccool.
-
Support CORS w3c/wot-security#121, by @mmccool.
-
Add securityDefinitions w3c/wot-security#120, by @mmccool.
-
Remove Url Postfixes in Security Parameter Names w3c/wot-security#119, by @mmccool.
-
-
12 issues closed.
-
Topology scenarios w3c/wot-security#50.
-
Require Not Exposing Immutable Hardware Identifiers? w3c/wot-security#70.
-
Define TD/API Security requirements for 2018 spring plugfest. w3c/wot-security#59.
-
Privacy Risks of The Things Directory, WoT Servient Gateway, and Gateway w3c/wot-security#71.
-
Consider adding TLS-SRP authentication scheme w3c/wot-security#97.
-
Metadata: OpenID Connect w3c/wot-security#75.
-
Metadata: Proxy w3c/wot-security#81.
-
Discuss Security Implications of TD Change and Deletion Notification w3c/wot-security#100.
-
Review TD Security Considerations w3c/wot-security#115.
-
Signing and encrypting body of actual responses of interaction pattern endpoints w3c/wot-security#118.
-
Remove Url Postfixes in Security Parameter Names w3c/wot-security#119.
-
Add securityDefinitions w3c/wot-security#120.
-
-
14 issues received 14 new comments.
-
Define TD/API Security requirements for 2018 spring plugfest. w3c/wot-security#59 (1 comment by @mmccool)
-
Privacy Risks of The Things Directory, WoT Servient Gateway, and Gateway w3c/wot-security#71 (1 comment by @mmccool)
-
Discuss Security Implications of TD Change and Deletion Notification w3c/wot-security#100 (1 comment by @mmccool)
-
Signing and encrypting body of actual responses of interaction pattern endpoints w3c/wot-security#118 (1 comment by @mmccool)
w3c/wot-architecture
-
2 issues opened.
-
Grammatical issue in the first para in the section "7.1 WoT Client" w3c/wot-architecture#62, by @srirama179.
-
Grammatical issue in "ConsumedThing interface" description in the section "WoT Scripting API" w3c/wot-architecture#61, by @srirama179.
-
TR publications
-
1 document published.
-
Web of Things (WoT) Thing Description published as a Working Draft. History of Web of Things (WoT) Thing Description
-
Participants
-
2 organizations joined.
-
SmartThings, Inc. joined.
-
Inswave Co., Ltd. joined.
-
-
1 organization left.
-
TPGi left.
-
GitHub
w3c/wot-thing-description
-
17 issues opened.
-
Automatic generation of diagrams (Sec. 5.1) w3c/wot-thing-description#276, by @vcharpenay.
-
Stray mentions of "rel" under "forms" w3c/wot-thing-description#267, by @mmccool.
-
Delete writeOnly w3c/wot-thing-description#266, by @mmccool.
-
Semantic Annotation in the Thing Description w3c/wot-thing-description#263, by @maximelefrancois86.
-
On Links, RFC 8288, and the RDF representation of Links w3c/wot-thing-description#262, by @maximelefrancois86.
-
contenttype for forms w3c/wot-thing-description#260, by @mkovatsc.
-
Alignment with SOSA/SSN (and iot.schema.org) w3c/wot-thing-description#259, by @vcharpenay.
-
type should be provided always in TD w3c/wot-thing-description#258, by @jmcanterafonseca.
-
WoT Security Ontology incorrectly linked w3c/wot-thing-description#257, by @jmcanterafonseca.
-
Web Link definitions should be in an own namespaces w3c/wot-thing-description#253, by @sebastiankb.
-
Model possible responses in forms w3c/wot-thing-description#250, by @mmccool.
-
rel of Forms contain typo for allowed values w3c/wot-thing-description#246, by @egekorkan.
-
Units in TD core vocabulary w3c/wot-thing-description#244, by @mkovatsc.
-
Invalid JSON Object at Example 9 w3c/wot-thing-description#243, by @egekorkan.
-
read and write property : different payload formats w3c/wot-thing-description#238, by @mlagally.
-
Declarative protocol bindings in TD w3c/wot-thing-description#237, by @mkovatsc.
-
Allow Form's "rel" to be a string or an array w3c/wot-thing-description#236, by @AndreMaz.
-
-
23 issues closed.
-
Invalid JSON Object at Example 9 w3c/wot-thing-description#243.
-
rel of Forms contain typo for allowed values w3c/wot-thing-description#246.
-
Unique Names for Properties, Events, and Actions w3c/wot-thing-description#191.
-
Interaction pattern - clarify unique name w3c/wot-thing-description#214.
-
Why are default values mandatory in JSON-LD serialisation? w3c/wot-thing-description#202.
-
Versioning container w3c/wot-thing-description#166.
-
Proposal for a way to model TD in RDF w3c/wot-thing-description#163.
-
OneM2M request to set a attribute w3c/wot-thing-description#154.
-
Abstract vs. Concrete Protocol Bindings w3c/wot-thing-description#112.
-
De-mystifying semantic models for the web of things w3c/wot-thing-description#93.
-
Defaults and Reasoning w3c/wot-thing-description#90.
-
Start on experimental JSON Thing Description serialization (cont.) w3c/wot-thing-description#76.
-
Metadata for protocol bindings w3c/wot-thing-description#15.
-
TD Data Types w3c/wot-thing-description#14.
-
Should non-web protocols be accommodated by the WoT Thing Description? w3c/wot-thing-description#113.
-
Top-level links member and links vs forms w3c/wot-thing-description#88.
-
Inconsistent `rel` description in 5.2.6 Form and 5.2.7 Link w3c/wot-thing-description#235.
-
Simplified TD: @type w3c/wot-thing-description#104.
-
Simplify to no forms field on sub-properties? w3c/wot-thing-description#140.
-
DataSchema for non-JSON / non-structured data w3c/wot-thing-description#223.
-
Duplicated description of `required` field in 5.3.3 ObjectSchema w3c/wot-thing-description#232.
-
Simplified TD: forms w3c/wot-thing-description#108.
-
subProtocol missing for form field w3c/wot-thing-description#193.
-
-
1 issue reopened.
-
Versioning container w3c/wot-thing-description#166, by @sebastiankb.
-
-
48 issues received 156 new comments.
-
Form relation type values (rel) w3c/wot-thing-description#179 (28 comments by @benfrancis, @draggett, @ektrah, @handrews, @hibaymj, @mkovatsc, @takuki, @zolkis)
-
writable vs. readOnly w3c/wot-thing-description#209 (13 comments by @draggett, @egekorkan, @ghost, @mkovatsc, @sebastiankb, @ToruKawaguchi, @vcharpenay)
-
Rename of label to title and enum titles 'oneOf' w3c/wot-thing-description#156 (12 comments by @benfrancis, @draggett, @handrews, @lgleim, @mkovatsc, @sebastiankb, @takuki)
-
Declarative protocol bindings in TD w3c/wot-thing-description#237 (12 comments by @draggett, @mkovatsc)
-
Alignment with SOSA/SSN (and iot.schema.org) w3c/wot-thing-description#259 (8 comments by @maximelefrancois86, @takuki, @vcharpenay)
-
Delete writeOnly w3c/wot-thing-description#266 (8 comments by @handrews, @mkovatsc, @sebastiankb, @takuki, @vcharpenay, @zolkis)
-
Metadata fields in Thing (mandatory and optional) w3c/wot-thing-description#142 (6 comments by @mkovatsc, @sebastiankb, @takuki)
-
read and write property : different payload formats w3c/wot-thing-description#238 (5 comments by @benfrancis, @mkovatsc, @mlagally, @mmccool)
-
Allow Form's "rel" to be a string or an array w3c/wot-thing-description#236 (4 comments by @egekorkan, @handrews, @mkovatsc, @sebastiankb)
-
Inputs in Events Definition w3c/wot-thing-description#231 (4 comments by @egekorkan, @mkovatsc, @ToruKawaguchi)
-
rel of Forms contain typo for allowed values w3c/wot-thing-description#246 (3 comments by @sebastiankb, @ToruKawaguchi)
-
Inconsistent `rel` description in 5.2.6 Form and 5.2.7 Link w3c/wot-thing-description#235 (3 comments by @handrews, @sebastiankb, @verymuch)
-
TD model figure shows wrong cardinalities when serialization has default values w3c/wot-thing-description#184 (2 comments by @sebastiankb, @takuki)
-
Model possible responses in forms w3c/wot-thing-description#250 (2 comments by @mkovatsc, @sebastiankb)
-
Enabling Interaction History (making Actions the only way to modify state) w3c/wot-thing-description#155 (2 comments by @sebastiankb, @takuki)
-
Simplify to no forms field on sub-properties? w3c/wot-thing-description#140 (2 comments by @mariapoveda, @mkovatsc)
-
Unique Names for Properties, Events, and Actions w3c/wot-thing-description#191 (1 comment by @sebastiankb)
-
Core Vocabulary Definition - fix schema links w3c/wot-thing-description#211 (1 comment by @sebastiankb)
-
Namespaces: clarify if HTTP namespace is normative w3c/wot-thing-description#210 (1 comment by @sebastiankb)
-
Why are default values mandatory in JSON-LD serialisation? w3c/wot-thing-description#202 (1 comment by @sebastiankb)
-
De-mystifying semantic models for the web of things w3c/wot-thing-description#93 (1 comment by @sebastiankb)
-
Start on experimental JSON Thing Description serialization (cont.) w3c/wot-thing-description#76 (1 comment by @sebastiankb)
-
Should non-web protocols be accommodated by the WoT Thing Description? w3c/wot-thing-description#113 (1 comment by @mkovatsc)
-
Add overridable global default value(s) for mediaType w3c/wot-thing-description#204 (1 comment by @mkovatsc)
-
DataSchema for non-JSON / non-structured data w3c/wot-thing-description#223 (1 comment by @mkovatsc)
-
Duplicated description of `required` field in 5.3.3 ObjectSchema w3c/wot-thing-description#232 (1 comment by @mkovatsc)
-
RFC 8259 (JSON) does not define "keys", but names w3c/wot-thing-description#194 (1 comment by @mkovatsc)
-
-
24 pull requests opened.
-
Removed an obsolete editors note that was not even included in the generated index.html w3c/wot-thing-description#275, by @takuki.
-
Clarified the definition of Property by mentioning readOnly and writeOnly fields in a note w3c/wot-thing-description#274, by @takuki.
-
Updated changes section to reflect the addition of unit field in DataSchema class w3c/wot-thing-description#273, by @takuki.
-
Updated changes section to reflect renaming of mediaType in Link class w3c/wot-thing-description#272, by @takuki.
-
"rel" is now "op" in form. w3c/wot-thing-description#271, by @takuki.
-
Updated recent changes section to reflect all changes made after 3rd Working Draft. w3c/wot-thing-description#270, by @takuki.
-
Security scopes example w3c/wot-thing-description#269, by @mmccool.
-
Remove URL postfixes from all security terms w3c/wot-thing-description#268, by @mmccool.
-
Security cleanup w3c/wot-thing-description#265, by @mmccool.
-
Added axioms to the JSON schema vocab for readOnly, writeOnly w3c/wot-thing-description#264, by @vcharpenay.
-
test plan cleanup w3c/wot-thing-description#261, by @mmccool.
-
analyzed normative assertions w3c/wot-thing-description#256, by @egekorkan.
-
Td4lyon w3c/wot-thing-description#255, by @sebastiankb.
-
add type and contenttype verification in the validation schema w3c/wot-thing-description#254, by @egekorkan.
-
update schema w3c/wot-thing-description#252, by @egekorkan.
-
update validation schema w3c/wot-thing-description#251, by @egekorkan.
-
Further improved the wording changed in PR #248. w3c/wot-thing-description#249, by @takuki.
-
Improved Type description for const and enum fields in DataSchema w3c/wot-thing-description#248, by @takuki.
-
update validation schema w3c/wot-thing-description#247, by @egekorkan.
-
Removed array definition for 'version' w3c/wot-thing-description#245, by @vcharpenay.
-
"anyType" in DataSchema section should not have a link w3c/wot-thing-description#242, by @takuki.
-
Recovered informal references. w3c/wot-thing-description#241, by @takuki.
-
Fixed a link to "anyType" definition. w3c/wot-thing-description#240, by @takuki.
-
Fixed duplicate ID "td-string-type" issue. w3c/wot-thing-description#239, by @takuki.
-
-
19 pull requests merged.
-
Removed an obsolete editors note that was not even included in the generated index.html w3c/wot-thing-description#275.
-
Clarified the definition of Property by mentioning readOnly and writeOnly fields in a note w3c/wot-thing-description#274.
-
Updated changes section to reflect the addition of unit field in DataSchema class w3c/wot-thing-description#273.
-
Updated changes section to reflect renaming of mediaType in Link class w3c/wot-thing-description#272.
-
"rel" is now "op" in form. w3c/wot-thing-description#271.
-
Updated recent changes section to reflect all changes made after 3rd Working Draft. w3c/wot-thing-description#270.
-
test plan cleanup w3c/wot-thing-description#261.
-
analyzed normative assertions w3c/wot-thing-description#256.
-
Td4lyon w3c/wot-thing-description#255.
-
add type and contenttype verification in the validation schema w3c/wot-thing-description#254.
-
update schema w3c/wot-thing-description#252.
-
Further improved the wording changed in PR #248. w3c/wot-thing-description#249.
-
Improved Type description for const and enum fields in DataSchema w3c/wot-thing-description#248.
-
update validation schema w3c/wot-thing-description#247.
-
Removed array definition for 'version' w3c/wot-thing-description#245.
-
"anyType" in DataSchema section should not have a link w3c/wot-thing-description#242.
-
Recovered informal references. w3c/wot-thing-description#241.
-
Fixed a link to "anyType" definition. w3c/wot-thing-description#240.
-
Fixed duplicate ID "td-string-type" issue. w3c/wot-thing-description#239.
-
-
1 pull request closed.
-
update validation schema w3c/wot-thing-description#251.
-
-
6 pull requests received 11 new comments.
-
Added axioms to the JSON schema vocab for readOnly, writeOnly w3c/wot-thing-description#264 (1 comment by @mmccool)
-
Further improved the wording changed in PR #248. w3c/wot-thing-description#249 (1 comment by @takuki)
w3c/wot-scripting-api
-
2 issues opened.
-
Security Testing and Validation URLs return 404 w3c/wot-scripting-api#151, by @egekorkan.
-
URI Templates / Variables (Alignment with Binding&TD) w3c/wot-scripting-api#149, by @danielpeintner.
-
-
2 issues received 7 new comments.
-
Align argument names with terminology in TD spec w3c/wot-scripting-api#146 (5 comments by @mkovatsc, @zolkis)
-
URI Templates / Variables (Alignment with Binding&TD) w3c/wot-scripting-api#149 (2 comments by @zolkis)
-
-
4 pull requests opened.
-
move https://github.com/thingweb/wot-typescript-definitions to scripting repo w3c/wot-scripting-api#152, by @danielpeintner.
-
Update WebIDL w3c/wot-scripting-api#150, by @zolkis.
-
Updating the content of security & privacy section w3c/wot-scripting-api#148, by @ereshetova.
-
Fix PropertyWriteHandler text w3c/wot-scripting-api#147, by @zolkis.
-
-
3 pull requests merged.
-
Update WebIDL w3c/wot-scripting-api#150.
-
Updating the content of security & privacy section w3c/wot-scripting-api#148.
-
Fix PropertyWriteHandler text w3c/wot-scripting-api#147.
-
-
2 pull requests received 5 new comments.
-
Updating the content of security & privacy section w3c/wot-scripting-api#148 (3 comments by @ereshetova, @zolkis)
-
w3c/wot-architecture
-
1 issue opened.
-
A Thing may be the abstraction of more than one entity. w3c/wot-architecture#60, by @maximelefrancois86.
-
-
1 issue received 1 new comment.
-
A Thing may be the abstraction of more than one entity. w3c/wot-architecture#60 (1 comment by @vcharpenay)
-
-
1 pull request opened.
-
Strawman merging all PRs until 23.1.2019 w3c/wot-architecture#59, by @mlagally.
-
w3c/wot-binding-templates
-
1 issue opened.
-
CoAP Blockwise Indicator w3c/wot-binding-templates#49, by @mkovatsc.
-
-
7 issues closed.
-
How do Protocol Bindings work for exposed things? w3c/wot-binding-templates#4.
-
Revising the 'form' vocabulary? w3c/wot-binding-templates#29.
-
'base' missing in Example 15 w3c/wot-binding-templates#18.
-
Add the "subProtocol" form element w3c/wot-binding-templates#33.
-
Typo: readData, writeData in rel -> readProperty, writeProperty w3c/wot-binding-templates#36.
-
Is a binding template specification necessary? w3c/wot-binding-templates#28.
-
Is rel used as a single string or as array? w3c/wot-binding-templates#38.
-
-
6 issues received 10 new comments.
-
Compile proposal for URI Templates w3c/wot-binding-templates#44 (4 comments by @mkovatsc, @sebastiankb)
-
How do Protocol Bindings work for exposed things? w3c/wot-binding-templates#4 (2 comments by @mjkoster, @mkovatsc)
-
Typo: readData, writeData in rel -> readProperty, writeProperty w3c/wot-binding-templates#36 (1 comment by @mkovatsc)
-
-
1 pull request received 1 new comment.
w3c/wot-security
-
1 issue received 1 new comment.
-
Signing and encrypting body of actual responses of interaction pattern endpoints w3c/wot-security#118 (1 comment by @mmccool)
-
Participants
-
1 organization joined.
-
The Clearing House joined.
-
-
1 organization left.
-
PTC left.
-
GitHub
w3c/wot-security
-
1 issue opened.
-
Signing and encrypting body of actual responses of interaction pattern endpoints w3c/wot-security#118, by @MooXo.
-
-
2 pull requests opened.
-
Working into Master w3c/wot-security#117, by @mmccool.
-
Fix the figures in section 7 w3c/wot-security#116, by @ereshetova.
-
-
2 pull requests merged.
-
Working into Master w3c/wot-security#117.
-
Fix the figures in section 7 w3c/wot-security#116.
-
-
1 pull request received 1 new comment.
w3c/wot-thing-description
-
8 issues opened.
-
Inconsistent `rel` description in 5.2.6 Form and 5.2.7 Link w3c/wot-thing-description#235, by @verymuch.
-
Same description of `identity` field in CertSecurityScheme/PublicSecurityScheme/PSKSecurityScheme w3c/wot-thing-description#233, by @verymuch.
-
Duplicated description of `required` field in 5.3.3 ObjectSchema w3c/wot-thing-description#232, by @verymuch.
-
Inputs in Events Definition w3c/wot-thing-description#231, by @sebastiankb.
-
Clarify whether security is mandatory w3c/wot-thing-description#230, by @mmccool.
-
Do we need a URI datatype? w3c/wot-thing-description#226, by @mlagally.
-
DataSchema for non-JSON / non-structured data w3c/wot-thing-description#223, by @mkovatsc.
-
Clarify type value of "null" for properties w3c/wot-thing-description#222, by @mlagally.
-
-
2 issues closed.
-
Normative References w3c/wot-thing-description#218.
-
scopes should be array of strings w3c/wot-thing-description#215.
-
-
1 issue reopened.
-
Duplicated description of `required` field in 5.3.3 ObjectSchema w3c/wot-thing-description#232, by @takuki.
-
-
16 issues received 47 new comments.
-
properties, actions and events need name **and** label field names w3c/wot-thing-description#216 (7 comments by @mkovatsc, @mlagally, @sebastiankb, @takuki, @vcharpenay, @zolkis)
-
Inputs in Events Definition w3c/wot-thing-description#231 (7 comments by @mjkoster, @takuki, @zolkis)
-
writable vs. readOnly w3c/wot-thing-description#209 (4 comments by @benfrancis, @handrews, @takuki, @zolkis)
-
Core Vocabulary Definition - fix schema links w3c/wot-thing-description#211 (4 comments by @mkovatsc, @mmccool, @takuki, @vcharpenay)
-
Clarify type value of "null" for properties w3c/wot-thing-description#222 (4 comments by @handrews, @mlagally, @takuki)
-
Duplicated description of `required` field in 5.3.3 ObjectSchema w3c/wot-thing-description#232 (3 comments by @takuki, @vcharpenay)
-
Internationalization (i18n) of human-readable TD fields w3c/wot-thing-description#161 (3 comments by @danielpeintner, @sebastiankb, @takuki)
-
DataSchema for non-JSON / non-structured data w3c/wot-thing-description#223 (2 comments by @handrews, @sebastiankb)
-
-
9 pull requests opened.
-
Fixed jsonschema:required duplicated declaration w3c/wot-thing-description#234, by @vcharpenay.
-
Update XSD datatype links w3c/wot-thing-description#229, by @vcharpenay.
-
Added a normative reference IANA media types. w3c/wot-thing-description#228, by @takuki.
-
Recovered informative references. w3c/wot-thing-description#227, by @takuki.
-
Fix Respec Config bug w3c/wot-thing-description#225, by @mmccool.
-
Regen index.html and testing/plan.html w3c/wot-thing-description#224, by @mmccool.
-
Assertion for unique-within-a-TD identifiers for interaction patterns w3c/wot-thing-description#221, by @mmccool.
-
Add OpenAPI informative reference w3c/wot-thing-description#220, by @mmccool.
-
Make scopes an array of string w3c/wot-thing-description#219, by @mmccool.
-
-
9 pull requests merged.
-
Fixed jsonschema:required duplicated declaration w3c/wot-thing-description#234.
-
Update XSD datatype links w3c/wot-thing-description#229.
-
Added a normative reference IANA media types. w3c/wot-thing-description#228.
-
Recovered informative references. w3c/wot-thing-description#227.
-
Fix Respec Config bug w3c/wot-thing-description#225.
-
Regen index.html and testing/plan.html w3c/wot-thing-description#224.
-
Assertion for unique-within-a-TD identifiers for interaction patterns w3c/wot-thing-description#221.
-
Add OpenAPI informative reference w3c/wot-thing-description#220.
-
Make scopes an array of string w3c/wot-thing-description#219.
-
-
5 pull requests received 14 new comments.
-
Assertion for unique-within-a-TD identifiers for interaction patterns w3c/wot-thing-description#221 (4 comments by @mlagally, @mmccool, @takuki, @vcharpenay)
-
Oracle Review Comments on TD spec draft / Device model chapter w3c/wot-thing-description#205 (3 comments by @mlagally, @vcharpenay)
-
w3c/wot-scripting-api
-
7 issues opened.
-
Align argument names with terminology in TD spec w3c/wot-scripting-api#146, by @mkovatsc.
-
Missing setActionHandler() w3c/wot-scripting-api#144, by @mkovatsc.
-
Outsource dictionary definitions to the TD spec w3c/wot-scripting-api#143, by @zolkis.
-
Replace explicit type definitions with reference to TD spec w3c/wot-scripting-api#142, by @zolkis.
-
General Scripting API review comments (2018-09-04) w3c/wot-scripting-api#141, by @danielpeintner.
-
Align Security Vocabulary Definition with TDs w3c/wot-scripting-api#140, by @danielpeintner.
-
Include normative statements to Security & Privacy considerations section w3c/wot-scripting-api#139, by @ereshetova.
-
-
16 issues closed.
-
Missing setActionHandler() w3c/wot-scripting-api#144.
-
Arguments to ExposedThing.register() w3c/wot-scripting-api#87.
-
Retrieving information from ThingDescription (or internal metadata) w3c/wot-scripting-api#38.
-
Dynamic update of Thing model may break clients w3c/wot-scripting-api#85.
-
Consistency check vs other WoT specifications w3c/wot-scripting-api#47.
-
Define TD for script manager Thing w3c/wot-scripting-api#23.
-
node-wot Korea target implementation experience w3c/wot-scripting-api#125.
-
Why is expose() asynchronous? w3c/wot-scripting-api#130.
-
Why is emitEvent() asynchronous? w3c/wot-scripting-api#131.
-
Replace explicit type definitions with reference to TD spec w3c/wot-scripting-api#142.
-
Include normative statements to Security & Privacy considerations section w3c/wot-scripting-api#139.
-
Outsource dictionary definitions to the TD spec w3c/wot-scripting-api#143.
-
JSONType gaps w3c/wot-scripting-api#118.
-
General Scripting API review comments (2018-09-04) w3c/wot-scripting-api#141.
-
Align Security Vocabulary Definition with TDs w3c/wot-scripting-api#140.
-
DataSchema type must not be required w3c/wot-scripting-api#133.
-
-
21 issues received 27 new comments.
-
Replace explicit type definitions with reference to TD spec w3c/wot-scripting-api#142 (2 comments by @zolkis)
-
General Scripting API review comments (2018-09-04) w3c/wot-scripting-api#141 (2 comments by @danielpeintner, @zolkis)
-
Align Security Vocabulary Definition with TDs w3c/wot-scripting-api#140 (2 comments by @danielpeintner, @zolkis)
-
Should Thing Directory Interface (register/unregister/discover) be part of WoT standard? w3c/wot-scripting-api#126 (1 comment by @zolkis)
-
Retrieving information from ThingDescription (or internal metadata) w3c/wot-scripting-api#38 (1 comment by @zolkis)
-
Consequences of setting "writable" to false for Scripting w3c/wot-scripting-api#106 (1 comment by @zolkis)
-
Signal end of life of an ExposedThing to the related ConsumedThings w3c/wot-scripting-api#114 (1 comment by @zolkis)
-
General API discussion (was: "Proposal: readMutlipleProperties and writeMultipleProperties") w3c/wot-scripting-api#132 (1 comment by @zolkis)
-
Include normative statements to Security & Privacy considerations section w3c/wot-scripting-api#139 (1 comment by @ereshetova)
-
2 pull requests opened.
-
Fix #144: add setActionHandler() w3c/wot-scripting-api#145, by @zolkis.
-
Simplifications w3c/wot-scripting-api#138, by @zolkis.
-
-
3 pull requests merged.
-
Fix #144: add setActionHandler() w3c/wot-scripting-api#145.
-
Simplifications w3c/wot-scripting-api#138.
-
Add algorithm descriptions w3c/wot-scripting-api#134.
-
-
3 pull requests received 30 new comments.
w3c/wot-architecture
-
1 pull request opened.
-
Create proposals folder and submit straw-man of new requirements section w3c/wot-architecture#58, by @ToruKawaguchi.
-
-
1 pull request merged.
-
Create proposals folder and submit straw-man of new requirements section w3c/wot-architecture#58.
-
w3c/wot-binding-templates
-
1 issue received 1 new comment.
-
Do we need a protocol binding to describe notification using WebHooks? w3c/wot-binding-templates#40 (1 comment by @mlagally)
-
-
1 pull request opened.
-
Review changes for post-Bundang release w3c/wot-binding-templates#48, by @mkovatsc.
-
-
1 pull request merged.
-
Mjkoster update bundang w3c/wot-binding-templates#45.
-
-
1 pull request received 1 new comment.
GitHub
w3c/wot-thing-description
-
25 issues opened.
-
Normative References w3c/wot-thing-description#218, by @mlagally.
-
Clarify "scope" field semantics w3c/wot-thing-description#217, by @mlagally.
-
properties, actions and events need name **and** label field names w3c/wot-thing-description#216, by @mlagally.
-
scopes should be array of strings w3c/wot-thing-description#215, by @mlagally.
-
Interaction pattern - clarify unique name w3c/wot-thing-description#214, by @mlagally.
-
clarify semantics of actions w3c/wot-thing-description#213, by @mlagally.
-
vendor-specific TD extensions w3c/wot-thing-description#212, by @mlagally.
-
Core Vocabulary Definition - fix schema links w3c/wot-thing-description#211, by @mlagally.
-
Namespaces: clarify if HTTP namespace is normative w3c/wot-thing-description#210, by @mlagally.
-
writable vs. readOnly w3c/wot-thing-description#209, by @benfrancis.
-
Fix formatting of autogenerated section 5 w3c/wot-thing-description#206, by @mlagally.
-
Add overridable global default value(s) for mediaType w3c/wot-thing-description#204, by @mmccool.
-
Why are default values mandatory in JSON-LD serialisation? w3c/wot-thing-description#202, by @mlagally.
-
Clarify relationship of security schemes between WoT and OpenAPI w3c/wot-thing-description#201, by @mlagally.
-
Default value for mediaType w3c/wot-thing-description#196, by @sebastiankb.
-
RFC 8259 (JSON) does not define "keys", but names w3c/wot-thing-description#194, by @mkovatsc.
-
subProtocol missing for form field w3c/wot-thing-description#193, by @mkovatsc.
-
Unique Names for Properties, Events, and Actions w3c/wot-thing-description#191, by @mmccool.
-
JSON Schema for TD Instance Validation too permissive w3c/wot-thing-description#187, by @ToruKawaguchi.
-
DataSchema definition should be from the JSON Schema vocab, not from the TD vocab w3c/wot-thing-description#186, by @vcharpenay.
-
Use w3.org TD Context w3c/wot-thing-description#185, by @vcharpenay.
-
TD model figure shows wrong cardinalities when serialization has default values w3c/wot-thing-description#184, by @danielpeintner.
-
Usage of "scopes" w3c/wot-thing-description#181, by @vcharpenay.
-
Form relation type values (rel) w3c/wot-thing-description#179, by @mkovatsc.
-
PSK Security Scheme needs work w3c/wot-thing-description#178, by @mmccool.
-
-
14 issues closed.
-
Should links have a "security" tag? w3c/wot-thing-description#148.
-
Default value for mediaType w3c/wot-thing-description#196.
-
Usage of "scopes" w3c/wot-thing-description#181.
-
Include security field in interaction patterns? w3c/wot-thing-description#146.
-
Include description in security configuration? w3c/wot-thing-description#147.
-
PSK Security Scheme needs work w3c/wot-thing-description#178.
-
Use w3.org TD Context w3c/wot-thing-description#185.
-
DataSchema definition should be from the JSON Schema vocab, not from the TD vocab w3c/wot-thing-description#186.
-
Normative JSON Schema for TD validation in TD spec w3c/wot-thing-description#169.
-
Comparing simplified proposals for thing descriptions w3c/wot-thing-description#101.
-
Simplified TD: @context w3c/wot-thing-description#103.
-
Restructuring of top level term 'name' w3c/wot-thing-description#122.
-
Simplified TD Example Questions and Requests for Extension w3c/wot-thing-description#131.
-
Ontology modularization w3c/wot-thing-description#149.
-
-
29 issues received 140 new comments.
-
Form relation type values (rel) w3c/wot-thing-description#179 (48 comments by @benfrancis, @ektrah, @handrews, @mjkoster, @mkovatsc)
-
Rename of label to title and enum titles 'oneOf' w3c/wot-thing-description#156 (11 comments by @benfrancis, @handrews, @mkovatsc)
-
subProtocol missing for form field w3c/wot-thing-description#193 (10 comments by @benfrancis, @draggett, @mjkoster, @mmccool, @sebastiankb, @takuki, @vcharpenay)
-
A way to read all Properties at once? w3c/wot-thing-description#151 (9 comments by @benfrancis, @mjkoster, @mkovatsc)
-
Default value for mediaType w3c/wot-thing-description#196 (8 comments by @benfrancis, @danielpeintner, @mlagally, @sebastiankb, @takuki)
-
PSK Security Scheme needs work w3c/wot-thing-description#178 (8 comments by @mkovatsc, @mmccool, @vcharpenay)
-
writable vs. readOnly w3c/wot-thing-description#209 (6 comments by @benfrancis, @dhylands, @handrews, @zolkis)
-
TD model figure shows wrong cardinalities when serialization has default values w3c/wot-thing-description#184 (6 comments by @mkovatsc, @sebastiankb, @takuki)
-
JSON Schema for TD Instance Validation too permissive w3c/wot-thing-description#187 (3 comments by @mkovatsc, @takuki, @ToruKawaguchi)
-
Add overridable global default value(s) for mediaType w3c/wot-thing-description#204 (3 comments by @mmccool, @takuki)
-
RFC 8259 (JSON) does not define "keys", but names w3c/wot-thing-description#194 (2 comments by @mkovatsc, @mlagally)
-
Why are default values mandatory in JSON-LD serialisation? w3c/wot-thing-description#202 (2 comments by @mlagally, @takuki)
-
Internationalization (i18n) of human-readable TD fields w3c/wot-thing-description#161 (2 comments by @takuki, @ToruKawaguchi)
-
DataSchema definition should be from the JSON Schema vocab, not from the TD vocab w3c/wot-thing-description#186 (2 comments by @mkovatsc, @vcharpenay)
-
import/extend functionality in TD w3c/wot-thing-description#168 (2 comments by @mkovatsc, @mlagally)
-
properties, actions and events need name **and** label field names w3c/wot-thing-description#216 (1 comment by @benfrancis)
-
Clarify relationship of security schemes between WoT and OpenAPI w3c/wot-thing-description#201 (1 comment by @takuki)
-
Metadata fields in Thing (mandatory and optional) w3c/wot-thing-description#142 (1 comment by @mlagally)
-
Include security field in interaction patterns? w3c/wot-thing-description#146 (1 comment by @mmccool)
-
Include description in security configuration? w3c/wot-thing-description#147 (1 comment by @mmccool)
-
Comparing simplified proposals for thing descriptions w3c/wot-thing-description#101 (1 comment by @sebastiankb)
-
Simplified TD Example Questions and Requests for Extension w3c/wot-thing-description#131 (1 comment by @sebastiankb)
-
-
19 pull requests opened.
-
Added an editor's note (Issue #187) w3c/wot-thing-description#208, by @takuki.
-
Security Considerations section w3c/wot-thing-description#207, by @mmccool.
-
Oracle Review Comments on TD spec draft / Device model chapter w3c/wot-thing-description#205, by @mlagally.
-
Add cert and public security schemes to validation w3c/wot-thing-description#203, by @mmccool.
-
Fixed misspelling in acknowledgement section. w3c/wot-thing-description#200, by @takuki.
-
Add subProtocol w3c/wot-thing-description#199, by @mmccool.
-
Add CoAP/DTLS "cert" and "public" security schemes w3c/wot-thing-description#198, by @mmccool.
-
Updated "Recent Changes" section to include latest changes. w3c/wot-thing-description#197, by @takuki.
-
Editorial changes w3c/wot-thing-description#195, by @mkovatsc.
-
Move list of allowed rel values to ed note w3c/wot-thing-description#192, by @mmccool.
-
Minor Issue and English Review w3c/wot-thing-description#190, by @mmccool.
-
change security scheme none to nosec w3c/wot-thing-description#189, by @mmccool.
-
Removed superfluous "SimpleDataSchema" class w3c/wot-thing-description#188, by @vcharpenay.
-
Security example fixes w3c/wot-thing-description#183, by @mmccool.
-
Improved wording of Recent Changes section. w3c/wot-thing-description#182, by @takuki.
-
Updated RDF namespaces w3c/wot-thing-description#180, by @vcharpenay.
-
Rename "pname" parameter to "name" for API Key (and other security schemes) w3c/wot-thing-description#177, by @mmccool.
-
Added a section "Changes from Second Public Working Draft". w3c/wot-thing-description#176, by @takuki.
-
Added Changes section listing changes since second draft. w3c/wot-thing-description#175, by @takuki.
-
-
17 pull requests merged.
-
Added an editor's note (Issue #187) w3c/wot-thing-description#208.
-
Add cert and public security schemes to validation w3c/wot-thing-description#203.
-
Fixed misspelling in acknowledgement section. w3c/wot-thing-description#200.
-
Add CoAP/DTLS "cert" and "public" security schemes w3c/wot-thing-description#198.
-
Add subProtocol w3c/wot-thing-description#199.
-
Updated "Recent Changes" section to include latest changes. w3c/wot-thing-description#197.
-
Editorial changes w3c/wot-thing-description#195.
-
Move list of allowed rel values to ed note w3c/wot-thing-description#192.
-
Minor Issue and English Review w3c/wot-thing-description#190.
-
Removed superfluous "SimpleDataSchema" class w3c/wot-thing-description#188.
-
change security scheme none to nosec w3c/wot-thing-description#189.
-
Security example fixes w3c/wot-thing-description#183.
-
Updated RDF namespaces w3c/wot-thing-description#180.
-
Improved wording of Recent Changes section. w3c/wot-thing-description#182.
-
Make security configuration mandatory w3c/wot-thing-description#174.
-
Added a section "Changes from Second Public Working Draft". w3c/wot-thing-description#176.
-
Added Changes section listing changes since second draft. w3c/wot-thing-description#175.
-
-
1 pull request closed.
-
Rename "pname" parameter to "name" for API Key (and other security schemes) w3c/wot-thing-description#177.
-
-
12 pull requests received 34 new comments.
-
Oracle Review Comments on TD spec draft / Device model chapter w3c/wot-thing-description#205 (5 comments by @mlagally, @mmccool, @takuki)
-
Add cert and public security schemes to validation w3c/wot-thing-description#203 (4 comments by @mmccool, @sebastiankb)
-
Rename "pname" parameter to "name" for API Key (and other security schemes) w3c/wot-thing-description#177 (3 comments by @mmccool, @vcharpenay)
-
Make security configuration mandatory w3c/wot-thing-description#174 (3 comments by @benfrancis, @mmccool, @sebastiankb)
-
Add CoAP/DTLS "cert" and "public" security schemes w3c/wot-thing-description#198 (1 comment by @sebastiankb)
-
Move list of allowed rel values to ed note w3c/wot-thing-description#192 (1 comment by @sebastiankb)
-
Removed superfluous "SimpleDataSchema" class w3c/wot-thing-description#188 (1 comment by @sebastiankb)
w3c/wot-scripting-api
-
2 issues opened.
-
Improve discover() signature w3c/wot-scripting-api#137, by @zolkis.
-
DataSchema type must not be required w3c/wot-scripting-api#133, by @danielpeintner.
-
-
3 issues closed.
-
ThingAction misses input parameter for run() w3c/wot-scripting-api#121.
-
Clarification (avoiding confusion with term "name") w3c/wot-scripting-api#122.
-
Consider aligning the scripting API (webIDL) with the Interaction vocabulary w3c/wot-scripting-api#127.
-
-
1 issue reopened.
-
DataSchema type must not be required w3c/wot-scripting-api#133, by @zolkis.
-
-
6 issues received 28 new comments.
-
General API discussion (was: "Proposal: readMutlipleProperties and writeMultipleProperties") w3c/wot-scripting-api#132 (21 comments by @benfrancis, @draggett, @mkovatsc, @zolkis)
-
DataSchema type must not be required w3c/wot-scripting-api#133 (2 comments by @6d77, @danielpeintner)
-
Consider aligning the scripting API (webIDL) with the Interaction vocabulary w3c/wot-scripting-api#127 (2 comments by @mkovatsc)
-
ThingAction misses input parameter for run() w3c/wot-scripting-api#121 (1 comment by @danielpeintner)
-
Clarification (avoiding confusion with term "name") w3c/wot-scripting-api#122 (1 comment by @danielpeintner)
-
-
3 pull requests opened.
-
add IntegerSchema dictionary w3c/wot-scripting-api#136, by @danielpeintner.
-
fix: issue-30, DataSchema type must not be required w3c/wot-scripting-api#135, by @danielpeintner.
-
Add algorithm descriptions w3c/wot-scripting-api#134, by @zolkis.
-
-
3 pull requests merged.
-
add IntegerSchema dictionary w3c/wot-scripting-api#136.
-
fix: issue-30, DataSchema type must not be required w3c/wot-scripting-api#135.
-
Korea F2F changes w3c/wot-scripting-api#128.
-
-
3 pull requests received 10 new comments.
w3c/wot-security
-
2 issues opened.
-
Review TD Security Considerations w3c/wot-security#115, by @mmccool.
-
Add Schemes for Raw Public Keys and Certificate-based Public Keys in CoAP w3c/wot-security#109, by @mmccool.
-
-
11 issues closed.
-
Role of Consent w3c/wot-security#67.
-
Discussion of WoT Fingerprinting Risks w3c/wot-security#72.
-
Metadata: Interledger w3c/wot-security#76.
-
Consider supporting form-based authentication schemes w3c/wot-security#98.
-
Add Schemes for Raw Public Keys and Certificate-based Public Keys in CoAP w3c/wot-security#109.
-
Should Security schemes in TDs have priorities? w3c/wot-security#105.
-
Security implications of import w3c/wot-security#106.
-
Review Security Learnings from TPAC2017 w3c/wot-security#48.
-
Make links to the WoT Terminology from the WoT Architecture document w3c/wot-security#44.
-
Add a section on "Privacy Considerations" w3c/wot-security#36.
-
-
19 issues received 24 new comments.
-
Add Schemes for Raw Public Keys and Certificate-based Public Keys in CoAP w3c/wot-security#109 (3 comments by @mmccool)
-
Privacy Risks of The Things Directory, WoT Servient Gateway, and Gateway w3c/wot-security#71 (1 comment by @mmccool)
-
Discuss Security Implications of TD Change and Deletion Notification w3c/wot-security#100 (1 comment by @mmccool)
-
Make links to the WoT Terminology from the WoT Architecture document w3c/wot-security#44 (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 @ereshetova)
-
-
6 pull requests opened.
-
Syncing master and working w3c/wot-security#114, by @mmccool.
-
Syncing repos, no actual changes w3c/wot-security#113, by @mmccool.
-
Polish English w3c/wot-security#112, by @mmccool.
-
Catch up working to master w3c/wot-security#111, by @mmccool.
-
Merge Working into Master w3c/wot-security#110, by @mmccool.
-
Security scenarios section update w3c/wot-security#108, by @ereshetova.
-
-
6 pull requests merged.
-
Syncing master and working w3c/wot-security#114.
-
Syncing repos, no actual changes w3c/wot-security#113.
-
Polish English w3c/wot-security#112.
-
Catch up working to master w3c/wot-security#111.
-
Merge Working into Master w3c/wot-security#110.
-
Security scenarios section update w3c/wot-security#108.
-
-
2 pull requests received 7 new comments.
w3c/wot-architecture
-
1 pull request opened.
-
a spelling mistake w3c/wot-architecture#57, by @verymuch.
-
-
1 pull request merged.
-
Added explanation of using PlantUML to create diagrams from source text. w3c/wot-architecture#55.
-
-
1 pull request received 1 new comment.
w3c/wot-binding-templates
-
1 issue opened.
-
align with the vocabulary in "CoAP in RDF" ontology and IANA CoRE Parameters page w3c/wot-binding-templates#47, by @mjkoster.
-
-
1 issue received 2 new comments.
-
align with the vocabulary in "CoAP in RDF" ontology and IANA CoRE Parameters page w3c/wot-binding-templates#47 (2 comments by @mjkoster, @mkovatsc)
-
Participants
-
1 organization joined.
-
360 joined.
-
-
1 organization left.
-
RWE AG left.
-
GitHub
w3c/wot-thing-description
-
8 issues opened.
-
Normative JSON Schema for TD validation in TD spec w3c/wot-thing-description#169, by @sebastiankb.
-
import/extend functionality in TD w3c/wot-thing-description#168, by @sebastiankb.
-
Prepare modular vocabulary w3c/wot-thing-description#167, by @mkovatsc.
-
Versioning container w3c/wot-thing-description#166, by @sebastiankb.
-
Should "security" be mandatory? w3c/wot-thing-description#165, by @mmccool.
-
[error] label field is marked as mandatory in the 5.2.2 InteractionPattern w3c/wot-thing-description#164, by @egekorkan.
-
Proposal for a way to model TD in RDF w3c/wot-thing-description#163, by @mjkoster.
-
Internationalization (i18n) of human-readable TD fields w3c/wot-thing-description#161, by @mkovatsc.
-
-
4 issues closed.
-
Use TD context from WG repo instead of IG repo w3c/wot-thing-description#159.
-
Should "security" be mandatory? w3c/wot-thing-description#165.
-
[error] label field is marked as mandatory in the 5.2.2 InteractionPattern w3c/wot-thing-description#164.
-
New term 'thingVersion' or similar w3c/wot-thing-description#126.
-
-
15 issues received 68 new comments.
-
Proposal for a way to model TD in RDF w3c/wot-thing-description#163 (16 comments by @draggett, @mjkoster, @mkovatsc, @takuki)
-
A way to read all Properties at once? w3c/wot-thing-description#151 (14 comments by @benfrancis, @danielpeintner, @draggett, @mjkoster, @mkovatsc, @sebastiankb, @takuki, @zolkis)
-
Should "security" be mandatory? w3c/wot-thing-description#165 (10 comments by @benfrancis, @danielpeintner, @mkovatsc, @mmccool, @takuki)
-
import/extend functionality in TD w3c/wot-thing-description#168 (7 comments by @benfrancis, @mkovatsc, @sebastiankb, @takuki, @ToruKawaguchi, @vcharpenay)
-
Normative JSON Schema for TD validation in TD spec w3c/wot-thing-description#169 (5 comments by @sebastiankb, @vcharpenay)
-
Do we include securityDefinitions? w3c/wot-thing-description#145 (3 comments by @mmccool, @sebastiankb)
-
Top-level links member and links vs forms w3c/wot-thing-description#88 (3 comments by @draggett, @handrews, @jaller94)
-
Use TD context from WG repo instead of IG repo w3c/wot-thing-description#159 (2 comments by @mkovatsc, @sebastiankb)
-
Include description in security configuration? w3c/wot-thing-description#147 (1 comment by @mmccool)
-
Internationalization (i18n) of human-readable TD fields w3c/wot-thing-description#161 (1 comment by @benfrancis)
-
Rename of label to title and enum titles 'oneOf' w3c/wot-thing-description#156 (1 comment by @mkovatsc)
-
-
6 pull requests opened.
-
Make security configuration mandatory w3c/wot-thing-description#174, by @mmccool.
-
Cleaned TD ontology II w3c/wot-thing-description#173, by @vcharpenay.
-
Cleaned TD ontology w3c/wot-thing-description#172, by @vcharpenay.
-
Restructured JSON Schema and Security ontology modules w3c/wot-thing-description#171, by @vcharpenay.
-
Automate Normative Assertion Extraction, Round 2 w3c/wot-thing-description#170, by @mmccool.
-
RDF model proposal MJK w3c/wot-thing-description#162, by @mjkoster.
-
-
4 pull requests merged.
-
Cleaned TD ontology II w3c/wot-thing-description#173.
-
Automate Normative Assertion Extraction, Round 2 w3c/wot-thing-description#170.
-
Cleaned TD ontology w3c/wot-thing-description#172.
-
Restructured JSON Schema and Security ontology modules w3c/wot-thing-description#171.
-
-
1 pull request closed.
-
Automate Normative Assertion Extraction w3c/wot-thing-description#138.
-
-
5 pull requests received 8 new comments.
-
Cleaned TD ontology II w3c/wot-thing-description#173 (4 comments by @mkovatsc, @sebastiankb, @vcharpenay)
-
Restructured JSON Schema and Security ontology modules w3c/wot-thing-description#171 (1 comment by @mkovatsc)
-
Automate Normative Assertion Extraction, Round 2 w3c/wot-thing-description#170 (1 comment by @mmccool)
-
w3c/wot-security
-
2 issues opened.
-
Security implications of import w3c/wot-security#106, by @mmccool.
-
Should Security schemes in TDs have priorities? w3c/wot-security#105, by @mmccool.
-
-
3 issues received 5 new comments.
-
1 pull request opened.
-
Restructuring parts of the document + fixes w3c/wot-security#107, by @ereshetova.
-
-
1 pull request merged.
-
Restructuring parts of the document + fixes w3c/wot-security#107.
-
w3c/wot-architecture
-
2 pull requests opened.
-
Editorial fixes w3c/wot-architecture#56, by @akeranen.
-
Added explanation of using PlantUML to create diagrams from source text. w3c/wot-architecture#55, by @ToruKawaguchi.
-
-
1 pull request merged.
-
Added "Further things to consider" items as per comments at 6/27 main call w3c/wot-architecture#54.
-
-
2 pull requests received 2 new comments.
-
Added "Further things to consider" items as per comments at 6/27 main call w3c/wot-architecture#54 (1 comment by @Kazuo-Kajimoto)
w3c/wot-scripting-api
-
4 issues opened.
-
General API discussion (was: "Proposal: readMutlipleProperties and writeMultipleProperties") w3c/wot-scripting-api#132, by @sebastiankb.
-
Why is emitEvent() asynchronous? w3c/wot-scripting-api#131, by @mkovatsc.
-
Why is expose() asynchronous? w3c/wot-scripting-api#130, by @mkovatsc.
-
ReSpec issues w3c/wot-scripting-api#129, by @danielpeintner.
-
-
2 issues closed.
-
ReSpec issues w3c/wot-scripting-api#129.
-
Avoiding same name for functions in interfaces w3c/wot-scripting-api#124.
-
-
1 issue reopened.
-
Avoiding same name for functions in interfaces w3c/wot-scripting-api#124, by @danielpeintner.
-
-
8 issues received 48 new comments.
-
General API discussion (was: "Proposal: readMutlipleProperties and writeMultipleProperties") w3c/wot-scripting-api#132 (24 comments by @6d77, @benfrancis, @danielpeintner, @draggett, @mjkoster, @mkovatsc, @zolkis)
-
Consider aligning the scripting API (webIDL) with the Interaction vocabulary w3c/wot-scripting-api#127 (5 comments by @mjkoster, @mkovatsc, @zolkis)
-
Avoiding same name for functions in interfaces w3c/wot-scripting-api#124 (4 comments by @danielpeintner, @zolkis)
-
Should Thing Directory Interface (register/unregister/discover) be part of WoT standard? w3c/wot-scripting-api#126 (1 comment by @mkovatsc)
-
-
1 pull request opened.
-
Korea F2F changes w3c/wot-scripting-api#128, by @zolkis.
-
-
1 pull request received 14 new comments.
w3c/wot-binding-templates
-
1 issue opened.
-
Inputs for MQTT Binding w3c/wot-binding-templates#46, by @sebastiankb.
-
GitHub
w3c/wot-architecture
-
3 pull requests opened.
-
Added "Further things to consider" items as per comments at 6/27 main call w3c/wot-architecture#54, by @ToruKawaguchi.
-
Add Appendix A Example Sequences w3c/wot-architecture#53, by @ToruKawaguchi.
-
Add Appendix A Example Sequences w3c/wot-architecture#52, by @ToruKawaguchi.
-
-
1 pull request merged.
-
Add Appendix A Example Sequences w3c/wot-architecture#53.
-
-
1 pull request closed.
-
Add Appendix A Example Sequences w3c/wot-architecture#52.
-
-
1 pull request reopened.
-
Add Appendix A Example Sequences w3c/wot-architecture#52, by @ToruKawaguchi.
-
-
1 pull request received 1 new comment.
w3c/wot-thing-description
-
8 issues opened.
-
Use TD context from WG repo instead of IG repo w3c/wot-thing-description#159, by @vcharpenay.
-
Rename of label to title and enum titles 'oneOf' w3c/wot-thing-description#156, by @benfrancis.
-
Enabling Interaction History (making Actions the only way to modify state) w3c/wot-thing-description#155, by @lgleim.
-
OneM2M request to set a attribute w3c/wot-thing-description#154, by @fabriceblache.
-
[TD Playground] JSON Schema bug: "events" should not be mandatory w3c/wot-thing-description#153, by @mlagally.
-
Invalid Example in TD spec - TD playground contains wrong link w3c/wot-thing-description#152, by @mlagally.
-
A way to read all Properties at once? w3c/wot-thing-description#151, by @mkovatsc.
-
Ontology modularization w3c/wot-thing-description#149, by @mariapoveda.
-
-
19 issues closed.
-
[TD Playground] JSON Schema bug: "events" should not be mandatory w3c/wot-thing-description#153.
-
Invalid Example in TD spec - TD playground contains wrong link w3c/wot-thing-description#152.
-
Define few sibling classes or sub-classes in TD Ontology? w3c/wot-thing-description#135.
-
Oracle review comments on simplified TD draft snapshot on 27.4. w3c/wot-thing-description#133.
-
[TF-TD] Namespaces used in the TD / WoT ontology w3c/wot-thing-description#3.
-
Wrong type for field-name events w3c/wot-thing-description#136.
-
security became securityDefinitions w3c/wot-thing-description#141.
-
Handling interactions that have binary payloads w3c/wot-thing-description#120.
-
Add Security Metadata w3c/wot-thing-description#127.
-
New term 'support' at the top level w3c/wot-thing-description#125.
-
Field name `schema` in the `Event` pattern w3c/wot-thing-description#118.
-
Relax constraints on @context and @type in JSON-LD serialization w3c/wot-thing-description#114.
-
Simplified TD: Media Type w3c/wot-thing-description#110.
-
Simplified TD: base w3c/wot-thing-description#106.
-
Simplified TD: @id/id w3c/wot-thing-description#105.
-
properties, actions and events as objects using JSON-LD 1.1 w3c/wot-thing-description#87.
-
Alignment with Generic Sensor spec w3c/wot-thing-description#59.
-
(Intentional?) Removal of stability in property w3c/wot-thing-description#29.
-
Renaming of the term 'name' at the interaction level in 'label' w3c/wot-thing-description#123.
-
-
32 issues received 65 new comments.
-
[TD Playground] JSON Schema bug: "events" should not be mandatory w3c/wot-thing-description#153 (10 comments by @egekorkan, @mlagally, @sebastiankb)
-
A way to read all Properties at once? w3c/wot-thing-description#151 (9 comments by @benfrancis, @draggett, @mjkoster, @mkovatsc, @mlagallyw, @takuki, @ToruKawaguchi, @zolkis)
-
Simplify to no forms field on sub-properties? w3c/wot-thing-description#140 (6 comments by @mariapoveda, @mjkoster, @vcharpenay)
-
Ontology modularization w3c/wot-thing-description#149 (3 comments by @mariapoveda, @takuki, @vcharpenay)
-
Renaming of the term 'name' at the interaction level in 'label' w3c/wot-thing-description#123 (3 comments by @benfrancis, @sebastiankb)
-
Rename of label to title and enum titles 'oneOf' w3c/wot-thing-description#156 (2 comments by @sebastiankb, @takuki)
-
OneM2M request to set a attribute w3c/wot-thing-description#154 (2 comments by @benfrancis, @fabriceblache)
-
Top-level links member and links vs forms w3c/wot-thing-description#88 (2 comments by @benfrancis, @sebastiankb)
-
Invalid Example in TD spec - TD playground contains wrong link w3c/wot-thing-description#152 (2 comments by @egekorkan, @mlagally)
-
security became securityDefinitions w3c/wot-thing-description#141 (2 comments by @mmccool, @sebastiankb)
-
Material to pitch use of semantics in TDs w3c/wot-thing-description#53 (2 comments by @mkovatsc, @sebastiankb)
-
TPAC resolution: Observable Properties and Events w3c/wot-thing-description#61 (2 comments by @mkovatsc, @sebastiankb)
-
Define few sibling classes or sub-classes in TD Ontology? w3c/wot-thing-description#135 (1 comment by @sebastiankb)
-
Oracle review comments on simplified TD draft snapshot on 27.4. w3c/wot-thing-description#133 (1 comment by @sebastiankb)
-
[TF-TD] Namespaces used in the TD / WoT ontology w3c/wot-thing-description#3 (1 comment by @sebastiankb)
-
Handling interactions that have binary payloads w3c/wot-thing-description#120 (1 comment by @sebastiankb)
-
Field name `schema` in the `Event` pattern w3c/wot-thing-description#118 (1 comment by @sebastiankb)
-
Relax constraints on @context and @type in JSON-LD serialization w3c/wot-thing-description#114 (1 comment by @sebastiankb)
-
Comparing simplified proposals for thing descriptions w3c/wot-thing-description#101 (1 comment by @sebastiankb)
-
properties, actions and events as objects using JSON-LD 1.1 w3c/wot-thing-description#87 (1 comment by @sebastiankb)
-
(Intentional?) Removal of stability in property w3c/wot-thing-description#29 (1 comment by @sebastiankb)
-
-
4 pull requests opened.
-
Revert "fixed mistakes found during 22.06.18 webconf" w3c/wot-thing-description#160, by @sebastiankb.
-
fixed mistakes found during 22.06.18 webconf w3c/wot-thing-description#158, by @vcharpenay.
-
Various improvements (schema defs, ontology, rendering) w3c/wot-thing-description#157, by @vcharpenay.
-
TD and datatypes diagram w3c/wot-thing-description#150, by @mariapoveda.
-
-
3 pull requests merged.
-
fixed mistakes found during 22.06.18 webconf w3c/wot-thing-description#158.
-
Various improvements (schema defs, ontology, rendering) w3c/wot-thing-description#157.
-
Security Metadata w3c/wot-thing-description#144.
-
-
1 pull request closed.
-
Revert "fixed mistakes found during 22.06.18 webconf" w3c/wot-thing-description#160.
-
-
5 pull requests received 22 new comments.
-
TD and datatypes diagram w3c/wot-thing-description#150 (5 comments by @mariapoveda, @mmccool, @sebastiankb)
-
Revert "fixed mistakes found during 22.06.18 webconf" w3c/wot-thing-description#160 (2 comments by @sebastiankb)
-
fixed mistakes found during 22.06.18 webconf w3c/wot-thing-description#158 (1 comment by @sebastiankb)
w3c/wot-binding-templates
-
1 issue received 2 new comments.
-
1 pull request opened.
-
Mjkoster update bundang w3c/wot-binding-templates#45, by @mjkoster.
-
w3c/wot-security
-
3 issues closed.
-
Add mitigations to Privacy section w3c/wot-security#99.
-
Consider adding qop parameter for digest authentication w3c/wot-security#96.
-
Structuring the Security Vocabulary w3c/wot-security#101.
-
-
13 issues received 18 new comments.
-
Consider adding qop parameter for digest authentication w3c/wot-security#96 (2 comments by @mmccool)
-
Privacy Risks of The Things Directory, WoT Servient Gateway, and Gateway w3c/wot-security#71 (1 comment by @mmccool)
-
Discuss Security Implications of TD Change and Deletion Notification w3c/wot-security#100 (1 comment by @mmccool)
-
2 pull requests opened.
-
Working -> Master 2018.06.25 w3c/wot-security#104, by @mmccool.
-
add initial text on privacy mitigations w3c/wot-security#103, by @ereshetova.
-
-
2 pull requests merged.
-
Working -> Master 2018.06.25 w3c/wot-security#104.
-
add initial text on privacy mitigations w3c/wot-security#103.
-
-
1 pull request received 1 new comment.
w3c/wot-scripting-api
-
9 issues opened.
-
Consider aligning the scripting API (webIDL) with the Interaction vocabulary w3c/wot-scripting-api#127, by @mjkoster.
-
Should Thing Directory Interface (register/unregister/discover) be part of WoT standard? w3c/wot-scripting-api#126, by @farshadahmadi.
-
node-wot Korea target implementation experience w3c/wot-scripting-api#125, by @mkovatsc.
-
Avoiding same name for functions in interfaces w3c/wot-scripting-api#124, by @danielpeintner.
-
Redundant getter() in ExposedThing w3c/wot-scripting-api#123, by @danielpeintner.
-
Clarification (avoiding confusion with term "name") w3c/wot-scripting-api#122, by @danielpeintner.
-
ThingAction misses input parameter for run() w3c/wot-scripting-api#121, by @danielpeintner.
-
issue with addProperty/addAction/addEvent for ExposedThing w3c/wot-scripting-api#120, by @danielpeintner.
-
JSONType gaps w3c/wot-scripting-api#118, by @danielpeintner.
-
-
17 issues closed.
-
issue with addProperty/addAction/addEvent for ExposedThing w3c/wot-scripting-api#120.
-
Redundant getter() in ExposedThing w3c/wot-scripting-api#123.
-
Align with top-level 'link' field of the TD (for Prague WD) w3c/wot-scripting-api#93.
-
API improvement: track TD (interactions) w3c/wot-scripting-api#96.
-
Semantic annotations w3c/wot-scripting-api#97.
-
Clear description of the issue "using WebIDL to describe maplike access of JSON-LD documents with @ fields" w3c/wot-scripting-api#108.
-
Refineing the WoT.discover() function w3c/wot-scripting-api#109.
-
What we want from the Scripting API when based on Simplified TD w3c/wot-scripting-api#111.
-
Discovery filtering w3c/wot-scripting-api#115.
-
Security (and type) metadata w3c/wot-scripting-api#116.
-
Interaction Inits: @type = pattern ∪ semanticTypes w3c/wot-scripting-api#81.
-
Definition of ExposedThing.start()/.stop() w3c/wot-scripting-api#76.
-
ConsumedThing interface: The url read-only attribute represents the URL of the Thing w3c/wot-scripting-api#74.
-
Definition of ExposedThing.register()/.unregister() w3c/wot-scripting-api#75.
-
Dynamic Things and semantic vocabularies (`@context`) w3c/wot-scripting-api#84.
-
DataSchema type names alignments w3c/wot-scripting-api#89.
-
Topics for the Prague F2F w3c/wot-scripting-api#95.
-
-
22 issues received 50 new comments.
-
ThingAction misses input parameter for run() w3c/wot-scripting-api#121 (9 comments by @danielpeintner, @zolkis)
-
node-wot Korea target implementation experience w3c/wot-scripting-api#125 (4 comments by @mkovatsc, @zolkis)
-
Clarification (avoiding confusion with term "name") w3c/wot-scripting-api#122 (1 comment by @zolkis)
-
issue with addProperty/addAction/addEvent for ExposedThing w3c/wot-scripting-api#120 (1 comment by @zolkis)
-
Align with top-level 'link' field of the TD (for Prague WD) w3c/wot-scripting-api#93 (1 comment by @zolkis)
-
Clear description of the issue "using WebIDL to describe maplike access of JSON-LD documents with @ fields" w3c/wot-scripting-api#108 (1 comment by @zolkis)
-
What we want from the Scripting API when based on Simplified TD w3c/wot-scripting-api#111 (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)
-
Dynamic Things and semantic vocabularies (`@context`) w3c/wot-scripting-api#84 (1 comment by @zolkis)
-
1 pull request opened.
-
Corrections w3c/wot-scripting-api#119, by @zolkis.
-
-
2 pull requests merged.
-
Corrections w3c/wot-scripting-api#119.
-
API update w3c/wot-scripting-api#113.
-
-
1 pull request received 3 new comments.
Participants
-
1 organization left.
-
Department of Informatics, PUC-Rio left.
-
GitHub
w3c/wot-thing-description
-
8 issues opened.
-
Should links have a "security" tag? w3c/wot-thing-description#148, by @mmccool.
-
Include description in security configuration? w3c/wot-thing-description#147, by @mmccool.
-
Include security field in interaction patterns? w3c/wot-thing-description#146, by @mmccool.
-
Do we include securityDefinitions? w3c/wot-thing-description#145, by @mmccool.
-
Metadata fields in Thing (mandatory and optional) w3c/wot-thing-description#142, by @mkovatsc.
-
security became securityDefinitions w3c/wot-thing-description#141, by @mkovatsc.
-
Simplify to no forms field on sub-properties? w3c/wot-thing-description#140, by @mkovatsc.
-
Wrong type for field-name events w3c/wot-thing-description#136, by @danielpeintner.
-
-
3 issues closed.
-
Can semantic markup be optional? w3c/wot-thing-description#86.
-
Simplified TD: links w3c/wot-thing-description#109.
-
Simplified TD: Objects vs Arrays w3c/wot-thing-description#111.
-
-
15 issues received 78 new comments.
-
Oracle review comments on simplified TD draft snapshot on 27.4. w3c/wot-thing-description#133 (34 comments by @handrews, @mkovatsc, @mlagallyw, @sebastiankb)
-
Simplify to no forms field on sub-properties? w3c/wot-thing-description#140 (16 comments by @benfrancis, @mariapoveda, @mkovatsc, @sebastiankb, @ToruKawaguchi, @vcharpenay, @zolkis)
-
JSON Schema/Hyper-Schema compatibility goals? w3c/wot-thing-description#115 (6 comments by @handrews, @mkovatsc)
-
Renaming of the term 'name' at the interaction level in 'label' w3c/wot-thing-description#123 (6 comments by @benfrancis, @mkovatsc, @takuki, @zolkis)
-
security became securityDefinitions w3c/wot-thing-description#141 (4 comments by @mkovatsc, @mmccool, @zolkis)
-
Metadata fields in Thing (mandatory and optional) w3c/wot-thing-description#142 (2 comments by @mkovatsc, @mlagally)
-
Define few sibling classes or sub-classes in TD Ontology? w3c/wot-thing-description#135 (2 comments by @mkovatsc)
-
Should non-web protocols be accommodated by the WoT Thing Description? w3c/wot-thing-description#113 (1 comment by @mkovatsc)
-
Split TD into abstract interaction model and protocol binding w3c/wot-thing-description#91 (1 comment by @mlagally)
-
-
5 pull requests opened.
-
Security Metadata w3c/wot-thing-description#144, by @mmccool.
-
Edited ontology model w3c/wot-thing-description#143, by @vcharpenay.
-
Thing class should have "label" instead of "name". w3c/wot-thing-description#139, by @takuki.
-
Automate Normative Assertion Extraction w3c/wot-thing-description#138, by @mmccool.
-
Normative assertions for testing w3c/wot-thing-description#137, by @mmccool.
-
-
3 pull requests merged.
-
Test bed 2018 prague w3c/wot-thing-description#128.
-
Edited ontology model w3c/wot-thing-description#143.
-
Thing class should have "label" instead of "name". w3c/wot-thing-description#139.
-
-
1 pull request closed.
-
Normative assertions for testing w3c/wot-thing-description#137.
-
-
5 pull requests received 6 new comments.
-
Thing class should have "label" instead of "name". w3c/wot-thing-description#139 (1 comment by @zolkis)
w3c/wot-scripting-api
-
3 issues opened.
-
Extract normative assertions for testing w3c/wot-scripting-api#117, by @mmccool.
-
Security (and type) metadata w3c/wot-scripting-api#116, by @zolkis.
-
Discovery filtering w3c/wot-scripting-api#115, by @zolkis.
-
-
3 issues received 11 new comments.
-
Discovery filtering w3c/wot-scripting-api#115 (7 comments by @danielpeintner, @FanoRamparany, @zolkis)
-
Dynamic Management Things - Management TD for each installed script w3c/wot-scripting-api#36 (2 comments by @farshadahmadi, @zolkis)
-
Signal end of life of an ExposedThing to the related ConsumedThings w3c/wot-scripting-api#114 (2 comments by @mkovatsc, @mmccool)
-
-
1 pull request received 3 new comments.
w3c/wot-security
-
7 issues opened.
-
Security Best Practices for WoT Systems w3c/wot-security#102, by @mmccool.
-
Structuring the Security Vocabulary w3c/wot-security#101, by @mkovatsc.
-
Discuss Security Implications of TD Change and Deletion Notification w3c/wot-security#100, by @mmccool.
-
Add mitigations to Privacy section w3c/wot-security#99, by @mmccool.
-
Consider supporting form-based authentication schemes w3c/wot-security#98, by @mmccool.
-
Consider adding TLS-SRP authentication scheme w3c/wot-security#97, by @mmccool.
-
Consider adding qop parameter for digest authentication w3c/wot-security#96, by @mmccool.
-
-
7 issues closed.
-
Metadata: Versions w3c/wot-security#85.
-
Metadata: Cookie API Keys w3c/wot-security#78.
-
Metadata: Protocol-Specific or Generic w3c/wot-security#83.
-
Thing end of life signaling w3c/wot-security#93.
-
Is Provisioning in Scope? w3c/wot-security#15.
-
Thing Provider Data Specification w3c/wot-security#68.
-
Passive Observers Risk w3c/wot-security#69.
-
-
18 issues received 36 new comments.
-
Privacy Risks of The Things Directory, WoT Servient Gateway, and Gateway w3c/wot-security#71 (3 comments by @ereshetova, @mmccool)
-
2 pull requests opened.
-
Update Master with Working w3c/wot-security#95, by @mmccool.
-
Start on privacy section w3c/wot-security#94, by @ereshetova.
-
-
5 pull requests merged.
-
Update Master with Working w3c/wot-security#95.
-
Start on privacy section w3c/wot-security#94.
-
Tunnel configuration w3c/wot-security#92.
-
Simpler security metadata examples w3c/wot-security#91.
-
addressing issues 71, 68 and 69 w3c/wot-security#90.
-
-
3 pull requests received 5 new comments.
w3c/wotwg
-
1 issue opened.
-
no license w3c/wotwg#6, by @Parkjiwon1222.
-
-
1 pull request opened.
-
Quick n' dirty news feed w3c/wotwg#7, by @Parkjiwon1222.
-
w3c/wot-architecture
-
1 issue opened.
-
Clear definition about Properties, Actions, and Events w3c/wot-architecture#51, by @sebastiankb.
-
w3c/wot-binding-templates
-
1 issue opened.
-
Compile proposal for URI Templates w3c/wot-binding-templates#44, by @mkovatsc.
-
-
2 issues closed.
-
Ex. 11 uses non-existing HTTP vocabulary term w3c/wot-binding-templates#30.
-
@type inconsistencies in the examples w3c/wot-binding-templates#39.
-
-
8 issues received 10 new comments.
-
Is a binding template specification necessary? w3c/wot-binding-templates#28 (2 comments by @benfrancis, @mkovatsc)
-
Do we need a protocol binding to describe notification using WebHooks? w3c/wot-binding-templates#40 (2 comments by @mkovatsc, @mlagally)
-
TR publications
-
3 documents published.
-
Web of Things (WoT) Scripting API published as a Working Draft. History of Web of Things (WoT) Scripting API
-
Web of Things (WoT) Thing Description published as a Working Draft. History of Web of Things (WoT) Thing Description
-
Participants
-
2 organizations joined.
-
Orange joined.
-
Consensys joined.
-
GitHub
w3c/wot-thing-description
-
11 issues opened.
-
Define few sibling classes or sub-classes in TD Ontology? w3c/wot-thing-description#135, by @sebastiankb.
-
Oracle review comments on simplified TD draft snapshot on 27.4. w3c/wot-thing-description#133, by @mlagally.
-
Oracle review comments on simplified TD draft snapshot on 27.4. w3c/wot-thing-description#132, by @mlagallyw.
-
Simplified TD Example Questions and Requests for Extension w3c/wot-thing-description#131, by @mkovatsc.
-
Add Action attributes w3c/wot-thing-description#130, by @mkovatsc.
-
Add Security Metadata w3c/wot-thing-description#127, by @mmccool.
-
New term 'thingVersion' or similar w3c/wot-thing-description#126, by @sebastiankb.
-
New term 'support' at the top level w3c/wot-thing-description#125, by @sebastiankb.
-
New 'description' term for top level and interaction level w3c/wot-thing-description#124, by @sebastiankb.
-
Renaming of the term 'name' at the interaction level in 'label' w3c/wot-thing-description#123, by @sebastiankb.
-
Restructuring of top level term 'name' w3c/wot-thing-description#122, by @sebastiankb.
-
-
3 issues closed.
-
New 'description' term for top level and interaction level w3c/wot-thing-description#124.
-
Oracle review comments on simplified TD draft snapshot on 27.4. w3c/wot-thing-description#132.
-
Mandatory terms in specifications of Interaction Patterns w3c/wot-thing-description#117.
-
-
11 issues received 15 new comments.
-
Renaming of the term 'name' at the interaction level in 'label' w3c/wot-thing-description#123 (2 comments by @benfrancis, @sebastiankb)
-
New term 'support' at the top level w3c/wot-thing-description#125 (2 comments by @benfrancis, @sebastiankb)
-
Restructuring of top level term 'name' w3c/wot-thing-description#122 (2 comments by @benfrancis, @zolkis)
-
Define few sibling classes or sub-classes in TD Ontology? w3c/wot-thing-description#135 (1 comment by @vcharpenay)
-
New 'description' term for top level and interaction level w3c/wot-thing-description#124 (1 comment by @sebastiankb)
-
Oracle review comments on simplified TD draft snapshot on 27.4. w3c/wot-thing-description#133 (1 comment by @sebastiankb)
-
Oracle review comments on simplified TD draft snapshot on 27.4. w3c/wot-thing-description#132 (1 comment by @mlagallyw)
-
JSON Schema/Hyper-Schema compatibility goals? w3c/wot-thing-description#115 (1 comment by @benfrancis)
-
Mandatory terms in specifications of Interaction Patterns w3c/wot-thing-description#117 (1 comment by @sebastiankb)
-
-
3 pull requests opened.
-
Td json ld 1.1 w3c/wot-thing-description#134, by @sebastiankb.
-
Added JSON-LD 1.1 context for simplified TD w3c/wot-thing-description#129, by @vcharpenay.
-
Test bed 2018 prague w3c/wot-thing-description#128, by @danielpeintner.
-
-
3 pull requests merged.
-
Td json ld 1.1 w3c/wot-thing-description#134.
-
WIP: Simplified TD w3c/wot-thing-description#121.
-
Added JSON-LD 1.1 context for simplified TD w3c/wot-thing-description#129.
-
-
2 pull requests received 2 new comments.
w3c/wot-security
-
1 issue opened.
-
Thing end of life signaling w3c/wot-security#93, by @zolkis.
-
-
1 issue closed.
-
Add Lifecycle discussion w3c/wot-security#39.
-
-
10 issues received 11 new comments.
-
Add Material for "Industrial/Critical infrastructure environment" scenarios w3c/wot-security#21 (2 comments by @mmccool)
-
Privacy Risks of The Things Directory, WoT Servient Gateway, and Gateway w3c/wot-security#71 (1 comment by @mmccool)
-
Consider moving Thing lifecycle discussion to Architecture w3c/wot-security#65 (1 comment by @mmccool)
-
Add Material for "Business/Corporate environment" scenarios w3c/wot-security#20 (1 comment by @mmccool)
-
-
6 pull requests opened.
-
Tunnel configuration w3c/wot-security#92, by @mmccool.
-
Simpler security metadata examples w3c/wot-security#91, by @mmccool.
-
addressing issues 71, 68 and 69 w3c/wot-security#90, by @ereshetova.
-
Improving section 6 based on F2F discussions and scenarios w3c/wot-security#89, by @ereshetova.
-
Updates to Security Metadata Proposal w3c/wot-security#88, by @mmccool.
-
Update Master with Working - post Prague 2018 F2F Review w3c/wot-security#87, by @mmccool.
-
-
3 pull requests merged.
-
Updates to Security Metadata Proposal w3c/wot-security#88.
-
Improving section 6 based on F2F discussions and scenarios w3c/wot-security#89.
-
Update Master with Working - post Prague 2018 F2F Review w3c/wot-security#87.
-
-
3 pull requests received 8 new comments.
w3c/wot-scripting-api
-
6 issues opened.
-
Signal end of life of an ExposedThing to the related ConsumedThings w3c/wot-scripting-api#114, by @zolkis.
-
API must allow to specify concrete media type w3c/wot-scripting-api#112, by @mkovatsc.
-
What we want from the Scripting API when based on Simplified TD w3c/wot-scripting-api#111, by @mkovatsc.
-
Specify result of writeProperty() method w3c/wot-scripting-api#110, by @danielpeintner.
-
Refineing the WoT.discover() function w3c/wot-scripting-api#109, by @mkovatsc.
-
Clear description of the issue "using WebIDL to describe maplike access of JSON-LD documents with @ fields" w3c/wot-scripting-api#108, by @danielpeintner.
-
-
1 issue closed.
-
Images missing on w3c's primer w3c/wot-scripting-api#79.
-
-
8 issues received 41 new comments.
-
What we want from the Scripting API when based on Simplified TD w3c/wot-scripting-api#111 (21 comments by @danielpeintner, @mkovatsc, @vcharpenay, @zolkis)
-
Clear description of the issue "using WebIDL to describe maplike access of JSON-LD documents with @ fields" w3c/wot-scripting-api#108 (5 comments by @mkovatsc, @zolkis)
-
Specify result of writeProperty() method w3c/wot-scripting-api#110 (4 comments by @danielpeintner, @zolkis)
-
Definition of ExposedThing.register()/.unregister() w3c/wot-scripting-api#75 (1 comment by @mkovatsc)
-
-
1 pull request opened.
-
API update w3c/wot-scripting-api#113, by @zolkis.
-
w3c/wot-binding-templates
-
3 issues opened.
-
Event Binding for CoAP Multicast w3c/wot-binding-templates#43, by @mkovatsc.
-
Protocol Binding for OPC-UA w3c/wot-binding-templates#42, by @mmccool.
-
What are priorities for the next revision, next plugfest w3c/wot-binding-templates#41, by @mjkoster.
-
-
2 issues received 4 new comments.
-
What are priorities for the next revision, next plugfest w3c/wot-binding-templates#41 (3 comments by @mjkoster)
-
Participants
-
1 organization joined.
-
HTML5 Converged Technology Forum joined.
-
GitHub
w3c/wot-scripting-api
-
3 issues opened.
-
Very high frequency updates w3c/wot-scripting-api#107, by @draggett.
-
Consequences of setting "writable" to false for Scripting w3c/wot-scripting-api#106, by @danielpeintner.
-
Callbacks need to take Interaction name w3c/wot-scripting-api#102, by @mkovatsc.
-
-
1 issue closed.
-
Callbacks need to take Interaction name w3c/wot-scripting-api#102.
-
-
6 issues received 42 new comments.
-
Callbacks need to take Interaction name w3c/wot-scripting-api#102 (24 comments by @danielpeintner, @mkovatsc, @zolkis)
-
Security, WoT Scripting API: security metadata in API w3c/wot-scripting-api#91 (7 comments by @mkovatsc, @mmccool, @zolkis)
-
Security, WoT Scripting API doc: security failures w3c/wot-scripting-api#90 (3 comments by @mkovatsc, @zolkis)
-
API improvement: track TD (interactions) w3c/wot-scripting-api#96 (2 comments by @mkovatsc, @zolkis)
-
ConsumedThing interface: The url read-only attribute represents the URL of the Thing w3c/wot-scripting-api#74 (1 comment by @mkovatsc)
-
-
6 pull requests opened.
-
Update the Changes and Open Issues section w3c/wot-scripting-api#104, by @zolkis.
-
Fix handler callbacks WebIDL, update text and examples. w3c/wot-scripting-api#103, by @zolkis.
-
Fix examples w3c/wot-scripting-api#101, by @mkovatsc.
-
Follow consistent Properties-Actions-Events order w3c/wot-scripting-api#100, by @mkovatsc.
-
Use singular for field names (LD convention) w3c/wot-scripting-api#99, by @mkovatsc.
-
Change ThingProperty defaults w3c/wot-scripting-api#98, by @mkovatsc.
-
-
6 pull requests merged.
-
Update the Changes and Open Issues section w3c/wot-scripting-api#104.
-
Fix handler callbacks WebIDL, update text and examples. w3c/wot-scripting-api#103.
-
Fix examples w3c/wot-scripting-api#101.
-
Follow consistent Properties-Actions-Events order w3c/wot-scripting-api#100.
-
Use singular for field names (LD convention) w3c/wot-scripting-api#99.
-
Change ThingProperty defaults w3c/wot-scripting-api#98.
-
-
7 pull requests received 35 new comments.
-
Fix handler callbacks WebIDL, update text and examples. w3c/wot-scripting-api#103 (7 comments by @danielpeintner, @zolkis)
-
w3c/wot-scripting-api#105 (1 comment by @dontcallmedom)
w3c/wot-binding-templates
-
6 issues opened.
-
Do we need a protocol binding to describe notification using WebHooks? w3c/wot-binding-templates#40, by @mjkoster.
-
@type inconsistencies in the examples w3c/wot-binding-templates#39, by @nsorin.
-
Is rel used as a single string or as array? w3c/wot-binding-templates#38, by @sebastiankb.
-
Typo: readData, writeData in rel -> readProperty, writeProperty w3c/wot-binding-templates#36, by @mmccool.
-
Is "allOf" in EXAMPLE 6-8 correct? w3c/wot-binding-templates#34, by @yamagile.
-
Add the "subProtocol" form element w3c/wot-binding-templates#33, by @mjkoster.
-
-
2 issues received 3 new comments.
-
Is "allOf" in EXAMPLE 6-8 correct? w3c/wot-binding-templates#34 (2 comments by @mjkoster, @yamagile)
-
-
3 pull requests opened.
-
Update index.html with items from issues and meeting w3c/wot-binding-templates#37, by @mjkoster.
-
Updates from 2018-03-06 meeting w3c/wot-binding-templates#35, by @mjkoster.
-
add subProtocol w3c/wot-binding-templates#32, by @mjkoster.
-
-
4 pull requests merged.
-
Update index.html with items from issues and meeting w3c/wot-binding-templates#37.
-
Updates from 2018-03-06 meeting w3c/wot-binding-templates#35.
-
add subProtocol w3c/wot-binding-templates#32.
-
update dataSchema elements w3c/wot-binding-templates#31.
-
-
1 pull request reopened.
-
update dataSchema elements w3c/wot-binding-templates#31, by @mjkoster.
-
-
3 pull requests received 12 new comments.
-
Update index.html with items from issues and meeting w3c/wot-binding-templates#37 (6 comments by @mjkoster, @mkovatsc)
-
update dataSchema elements w3c/wot-binding-templates#31 (4 comments by @mjkoster, @mkovatsc, @sebastiankb)
-
w3c/wot-architecture
-
1 issue opened.
-
Write .md for Identity Management w3c/wot-architecture#50, by @mkovatsc.
-
-
1 issue received 2 new comments.
w3c/wot-security
-
11 issues opened.
-
Metadata: Versions w3c/wot-security#85, by @mmccool.
-
Review IIC Endpoint Security Best Practices white paper w3c/wot-security#84, by @mmccool.
-
Metadata: Protocol-Specific or Generic w3c/wot-security#83, by @mmccool.
-
Metadata: OCF Security Model w3c/wot-security#82, by @mmccool.
-
Metadata: Proxy w3c/wot-security#81, by @mmccool.
-
Metadata: Bearer Token Format w3c/wot-security#80, by @mmccool.
-
Metadata: API Key Format w3c/wot-security#79, by @mmccool.
-
Metadata: Cookie API Keys w3c/wot-security#78, by @mmccool.
-
Metadata: OAuth2.0 w3c/wot-security#77, by @mmccool.
-
Metadata: Interledger w3c/wot-security#76, by @mmccool.
-
Metadata: OpenID Connect w3c/wot-security#75, by @mmccool.
-
-
2 issues closed.
-
Metadata: OCF Security Model w3c/wot-security#82.
-
Metadata: API Key Format w3c/wot-security#79.
-
-
10 issues received 30 new comments.
-
2 pull requests opened.
-
Modified metadata proposal with flat generic schemes w3c/wot-security#86, by @mmccool.
-
Security metadata strawman w3c/wot-security#74, by @mmccool.
-
-
3 pull requests merged.
-
Modified metadata proposal with flat generic schemes w3c/wot-security#86.
-
Security metadata strawman w3c/wot-security#74.
-
initial text for lifecycle w3c/wot-security#63.
-
-
1 pull request reopened.
-
Modified metadata proposal with flat generic schemes w3c/wot-security#86, by @mmccool.
-
-
3 pull requests received 20 new comments.
w3c/wot-thing-description
-
17 issues opened.
-
Handling interactions that have binary payloads w3c/wot-thing-description#120, by @mmccool.
-
Field name `schema` in the `Event` pattern w3c/wot-thing-description#118, by @danicic.
-
Mandatory terms in specifications of Interaction Patterns w3c/wot-thing-description#117, by @danicic.
-
JSON Schema/Hyper-Schema compatibility goals? w3c/wot-thing-description#115, by @handrews.
-
Relax constraints on @context and @type in JSON-LD serialization w3c/wot-thing-description#114, by @vcharpenay.
-
Should non-web protocols be accommodated by the WoT Thing Description? w3c/wot-thing-description#113, by @benfrancis.
-
Abstract vs. Concrete Protocol Bindings w3c/wot-thing-description#112, by @benfrancis.
-
Simplified TD: Objects vs Arrays w3c/wot-thing-description#111, by @mkovatsc.
-
Simplified TD: Media Type w3c/wot-thing-description#110, by @mkovatsc.
-
Simplified TD: links w3c/wot-thing-description#109, by @mkovatsc.
-
Simplified TD: forms w3c/wot-thing-description#108, by @mkovatsc.
-
Simplified TD: schema w3c/wot-thing-description#107, by @mkovatsc.
-
Simplified TD: base w3c/wot-thing-description#106, by @mkovatsc.
-
Simplified TD: @id/id w3c/wot-thing-description#105, by @mkovatsc.
-
Simplified TD: @type w3c/wot-thing-description#104, by @mkovatsc.
-
Simplified TD: @context w3c/wot-thing-description#103, by @mkovatsc.
-
Comparing simplified proposals for thing descriptions w3c/wot-thing-description#101, by @draggett.
-
-
7 issues closed.
-
Data types for interaction models for things w3c/wot-thing-description#13.
-
Pragmatic TD validation w3c/wot-thing-description#74.
-
Section "5.2.6 DataSchema" should be independent from the serialisation format w3c/wot-thing-description#75.
-
Add 'link' as top-level field of the TD (for Prague WD) w3c/wot-thing-description#94.
-
Examples 27 and 28 of the document missing context w3c/wot-thing-description#69.
-
@Id and reference not explain properly w3c/wot-thing-description#58.
-
min and max vs. minimum and maximum w3c/wot-thing-description#84.
-
-
29 issues received 106 new comments.
-
Simplified TD: forms w3c/wot-thing-description#108 (10 comments by @benfrancis, @handrews, @mkovatsc)
-
Add 'link' as top-level field of the TD (for Prague WD) w3c/wot-thing-description#94 (10 comments by @handrews, @mkovatsc, @sebastiankb)
-
Split TD into abstract interaction model and protocol binding w3c/wot-thing-description#91 (8 comments by @benfrancis, @mkovatsc, @mlagally, @sebastiankb)
-
Simplified TD: @id/id w3c/wot-thing-description#105 (7 comments by @benfrancis, @draggett, @mkovatsc)
-
Simplified TD: @context w3c/wot-thing-description#103 (6 comments by @draggett, @mkovatsc, @sebastiankb, @zolkis)
-
Abstract vs. Concrete Protocol Bindings w3c/wot-thing-description#112 (6 comments by @benfrancis, @mjkoster, @mkovatsc)
-
Handling interactions that have binary payloads w3c/wot-thing-description#120 (5 comments by @mmccool, @sebastiankb)
-
Mandatory terms in specifications of Interaction Patterns w3c/wot-thing-description#117 (4 comments by @danicic, @mkovatsc, @sebastiankb)
-
Simplified TD: links w3c/wot-thing-description#109 (4 comments by @benfrancis, @handrews, @mkovatsc)
-
Top-level links member and links vs forms w3c/wot-thing-description#88 (4 comments by @draggett, @mjkoster, @mkovatsc)
-
Field name `schema` in the `Event` pattern w3c/wot-thing-description#118 (3 comments by @danicic, @mkovatsc, @sebastiankb)
-
Comparing simplified proposals for thing descriptions w3c/wot-thing-description#101 (3 comments by @mkovatsc, @zolkis)
-
@Id and reference not explain properly w3c/wot-thing-description#58 (2 comments by @onovo1, @sebastiankb)
-
properties, actions and events as objects using JSON-LD 1.1 w3c/wot-thing-description#87 (2 comments by @benfrancis, @handrews)
-
min and max vs. minimum and maximum w3c/wot-thing-description#84 (2 comments by @benfrancis, @sebastiankb)
-
JSON Schema/Hyper-Schema compatibility goals? w3c/wot-thing-description#115 (1 comment by @handrews)
-
Data types for interaction models for things w3c/wot-thing-description#13 (1 comment by @sebastiankb)
-
Relax constraints on @context and @type in JSON-LD serialization w3c/wot-thing-description#114 (1 comment by @sebastiankb)
-
Section "5.2.6 DataSchema" should be independent from the serialisation format w3c/wot-thing-description#75 (1 comment by @sebastiankb)
-
Examples 27 and 28 of the document missing context w3c/wot-thing-description#69 (1 comment by @sebastiankb)
-
-
5 pull requests opened.
-
WIP: Simplified TD w3c/wot-thing-description#121, by @mkovatsc.
-
Added Changes section. w3c/wot-thing-description#119, by @takuki.
-
Revert: Simplified TD with experiemental JSON-LD 1.1 features w3c/wot-thing-description#116, by @sebastiankb.
-
WIP: Simplified TD with experiemental JSON-LD 1.1 features w3c/wot-thing-description#102, by @mkovatsc.
-
Add post-Prague simplified TD proposal w3c/wot-thing-description#100, by @mkovatsc.
-
-
3 pull requests merged.
-
Added Changes section. w3c/wot-thing-description#119.
-
WIP: Simplified TD with experiemental JSON-LD 1.1 features w3c/wot-thing-description#102.
-
Add post-Prague simplified TD proposal w3c/wot-thing-description#100.
-
-
1 pull request closed.
-
Revert: Simplified TD with experiemental JSON-LD 1.1 features w3c/wot-thing-description#116.
-
-
2 pull requests received 6 new comments.
-
WIP: Simplified TD with experiemental JSON-LD 1.1 features w3c/wot-thing-description#102 (5 comments by @benfrancis, @mkovatsc, @zolkis)
-
Revert: Simplified TD with experiemental JSON-LD 1.1 features w3c/wot-thing-description#116 (1 comment by @mkovatsc)
-
GitHub
w3c/wot-thing-description
-
9 issues opened.
-
Add 'link' as top-level field of the TD (for Prague WD) w3c/wot-thing-description#94, by @mkovatsc.
-
De-mystifying semantic models for the web of things w3c/wot-thing-description#93, by @draggett.
-
Split TD into abstract interaction model and protocol binding w3c/wot-thing-description#91, by @mlagally.
-
Defaults and Reasoning w3c/wot-thing-description#90, by @draggett.
-
Top-level links member and links vs forms w3c/wot-thing-description#88, by @benfrancis.
-
properties, actions and events as objects using JSON-LD 1.1 w3c/wot-thing-description#87, by @benfrancis.
-
Can semantic markup be optional? w3c/wot-thing-description#86, by @benfrancis.
-
links vs. forms w3c/wot-thing-description#85, by @benfrancis.
-
min and max vs. minimum and maximum w3c/wot-thing-description#84, by @benfrancis.
-
-
12 issues closed.
-
Generalize inputData, outputData to "payload" w3c/wot-thing-description#66.
-
Definition of baseUri and href w3c/wot-thing-description#81.
-
links vs. forms w3c/wot-thing-description#85.
-
Section 6.1: security is array of objects w3c/wot-thing-description#60.
-
Default @context with http, https, or both? w3c/wot-thing-description#80.
-
Unit definition in TD w3c/wot-thing-description#70.
-
Examples in TD Deliverable do not use right context url w3c/wot-thing-description#68.
-
Properties, actions and events w3c/wot-thing-description#12.
-
Support of Scripts in ThingDescription w3c/wot-thing-description#57.
-
Alignment with Mozilla/Evrthng proposal w3c/wot-thing-description#63.
-
Provide "type" for Property w3c/wot-thing-description#64.
-
Do we need an "observeData" field? w3c/wot-thing-description#65.
-
-
1 issue reopened.
-
Definition of baseUri and href w3c/wot-thing-description#81, by @zolkis.
-
-
26 issues received 110 new comments.
-
Top-level links member and links vs forms w3c/wot-thing-description#88 (29 comments by @benfrancis, @draggett, @handrews, @mjkoster, @mkovatsc, @sebastiankb, @zolkis)
-
Add 'link' as top-level field of the TD (for Prague WD) w3c/wot-thing-description#94 (20 comments by @handrews, @mjkoster, @mkovatsc, @sebastiankb, @zolkis)
-
Generalize inputData, outputData to "payload" w3c/wot-thing-description#66 (11 comments by @benfrancis, @draggett, @mkovatsc, @zolkis)
-
properties, actions and events as objects using JSON-LD 1.1 w3c/wot-thing-description#87 (8 comments by @benfrancis, @draggett, @mkovatsc)
-
Can semantic markup be optional? w3c/wot-thing-description#86 (7 comments by @benfrancis, @draggett, @mkovatsc, @sebastiankb)
-
min and max vs. minimum and maximum w3c/wot-thing-description#84 (5 comments by @handrews, @mkovatsc, @sebastiankb)
-
Definition of baseUri and href w3c/wot-thing-description#81 (3 comments by @mkovatsc, @sebastiankb, @zolkis)
-
Alignment with Generic Sensor spec w3c/wot-thing-description#59 (2 comments by @sebastiankb, @zolkis)
-
[TF-TD] Namespaces used in the TD / WoT ontology w3c/wot-thing-description#3 (2 comments by @draggett, @mkovatsc)
-
Start on experimental JSON Thing Description serialization (cont.) w3c/wot-thing-description#76 (2 comments by @benfrancis, @domguinard)
-
De-mystifying semantic models for the web of things w3c/wot-thing-description#93 (1 comment by @draggett)
-
Default @context with http, https, or both? w3c/wot-thing-description#80 (1 comment by @sebastiankb)
-
Examples in TD Deliverable do not use right context url w3c/wot-thing-description#68 (1 comment by @sebastiankb)
-
Split TD into abstract interaction model and protocol binding w3c/wot-thing-description#91 (1 comment by @mkovatsc)
-
TPAC resolution: Observable Properties and Events w3c/wot-thing-description#61 (1 comment by @mkovatsc)
-
Section "5.2.6 DataSchema" should be independent from the serialisation format w3c/wot-thing-description#75 (1 comment by @mkovatsc)
-
-
9 pull requests opened.
-
added Link class to ontology w3c/wot-thing-description#99, by @vcharpenay.
-
Reference to JSON Schema should be informative w3c/wot-thing-description#98, by @takuki.
-
changed URI of w3c-wot-td-context.jsonld w3c/wot-thing-description#97, by @takuki.
-
turned *Data & value into *Schema (II) w3c/wot-thing-description#96, by @vcharpenay.
-
turned *Data & value into *Schema w3c/wot-thing-description#95, by @vcharpenay.
-
Updated data type definitions w3c/wot-thing-description#92, by @vcharpenay.
-
Chore/package.json w3c/wot-thing-description#83, by @bufferoverflow.
-
'rel' property not rendered (fixed) w3c/wot-thing-description#82, by @vcharpenay.
-
-
8 pull requests merged.
-
added Link class to ontology w3c/wot-thing-description#99.
-
Reference to JSON Schema should be informative w3c/wot-thing-description#98.
-
turned *Data & value into *Schema (II) w3c/wot-thing-description#96.
-
turned *Data & value into *Schema w3c/wot-thing-description#95.
-
fix typo w3c/wot-thing-description#89.
-
Updated data type definitions w3c/wot-thing-description#92.
-
Chore/package.json w3c/wot-thing-description#83.
-
'rel' property not rendered (fixed) w3c/wot-thing-description#82.
-
-
1 pull request closed.
-
changed URI of w3c-wot-td-context.jsonld w3c/wot-thing-description#97.
-
-
6 pull requests received 14 new comments.
-
turned *Data & value into *Schema w3c/wot-thing-description#95 (4 comments by @ToruKawaguchi, @vcharpenay, @zolkis)
-
Reference to JSON Schema should be informative w3c/wot-thing-description#98 (3 comments by @handrews, @sebastiankb)
-
changed URI of w3c-wot-td-context.jsonld w3c/wot-thing-description#97 (2 comments by @draggett, @sebastiankb)
-
w3c/wot-scripting-api
-
9 issues opened.
-
Semantic annotations w3c/wot-scripting-api#97, by @zolkis.
-
API improvement: track TD (interactions) w3c/wot-scripting-api#96, by @zolkis.
-
Topics for the Prague F2F w3c/wot-scripting-api#95, by @zolkis.
-
Align with top-level 'link' field of the TD (for Prague WD) w3c/wot-scripting-api#93, by @danielpeintner.
-
Security, WoT Scripting API: security metadata in API w3c/wot-scripting-api#91, by @ereshetova.
-
Security, WoT Scripting API doc: security failures w3c/wot-scripting-api#90, by @ereshetova.
-
DataSchema type names alignments w3c/wot-scripting-api#89, by @danielpeintner.
-
ReSpec WebIDL name collision issue for Observable w3c/wot-scripting-api#88, by @danielpeintner.
-
Arguments to ExposedThing.register() w3c/wot-scripting-api#87, by @zolkis.
-
-
13 issues closed.
-
Does Scripting need a dataType attribute for Property, Action, and Event w3c/wot-scripting-api#71.
-
Add means to indicate static/dynamic status of TD w3c/wot-scripting-api#83.
-
Mapping WoT event models in Scripting API w3c/wot-scripting-api#68.
-
RequestHandler per type or per type&name w3c/wot-scripting-api#72.
-
Add use cases w3c/wot-scripting-api#6.
-
WoT.consume(USVString url) sufficient for consuming things? w3c/wot-scripting-api#69.
-
Does WoT.Request need a "type" attribute w3c/wot-scripting-api#70.
-
API for next PlugFest (Prague 2018) w3c/wot-scripting-api#82.
-
JavaScript property management in the WoT Scripting API w3c/wot-scripting-api#77.
-
API improvements w3c/wot-scripting-api#78.
-
Use Observables instead of callbacks? w3c/wot-scripting-api#5.
-
ReSpec WebIDL name collision issue for Observable w3c/wot-scripting-api#88.
-
-
26 issues received 82 new comments.
-
Security, WoT Scripting API: security metadata in API w3c/wot-scripting-api#91 (23 comments by @ereshetova, @mkovatsc, @mmccool, @zolkis)
-
API improvement: track TD (interactions) w3c/wot-scripting-api#96 (8 comments by @danielpeintner, @mkovatsc, @zolkis)
-
Security, WoT Scripting API doc: security failures w3c/wot-scripting-api#90 (6 comments by @ereshetova, @zolkis)
-
Align with top-level 'link' field of the TD (for Prague WD) w3c/wot-scripting-api#93 (5 comments by @mkovatsc, @zolkis)
-
Definition of ExposedThing.register()/.unregister() w3c/wot-scripting-api#75 (5 comments by @knimura, @mkovatsc, @zolkis)
-
Definition of ExposedThing.start()/.stop() w3c/wot-scripting-api#76 (5 comments by @mkovatsc, @zolkis)
-
Dynamic update of Thing model may break clients w3c/wot-scripting-api#85 (3 comments by @mkovatsc, @zolkis)
-
JavaScript property management in the WoT Scripting API w3c/wot-scripting-api#77 (2 comments by @zolkis)
-
Use Observables instead of callbacks? w3c/wot-scripting-api#5 (2 comments by @danielpeintner, @zolkis)
-
Does Scripting need a dataType attribute for Property, Action, and Event w3c/wot-scripting-api#71 (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)
-
WoT.consume(USVString url) sufficient for consuming things? w3c/wot-scripting-api#69 (1 comment by @zolkis)
-
onObserve() cannot be used for both Property change notifications and Event notifications -- and should be removed alltogether w3c/wot-scripting-api#73 (1 comment by @zolkis)
-
ReSpec WebIDL name collision issue for Observable w3c/wot-scripting-api#88 (1 comment by @danielpeintner)
-
-
2 pull requests opened.
-
Use schema, inputSchema, outputSchema from updated TD spec. Add support for TD links. w3c/wot-scripting-api#94, by @zolkis.
-
Add support for chaining in ExposedThing w3c/wot-scripting-api#92, by @zolkis.
-
-
4 pull requests merged.
-
Use schema, inputSchema, outputSchema from updated TD spec. Add support for TD links. w3c/wot-scripting-api#94.
-
Fix markdown images links w3c/wot-scripting-api#80.
-
Add support for chaining in ExposedThing w3c/wot-scripting-api#92.
-
Update the API according to discussion in #82 and #78 w3c/wot-scripting-api#86.
-
-
1 pull request reopened.
-
Fix markdown images links w3c/wot-scripting-api#80, by @zolkis.
-
-
4 pull requests received 68 new comments.
-
Update the API according to discussion in #82 and #78 w3c/wot-scripting-api#86 (42 comments by @danielpeintner, @knimura, @mkovatsc, @zolkis)
-
Use schema, inputSchema, outputSchema from updated TD spec. Add support for TD links. w3c/wot-scripting-api#94 (16 comments by @danielpeintner, @knimura, @mkovatsc, @zolkis)
-
Fix markdown images links w3c/wot-scripting-api#80 (7 comments by @danielpeintner, @dontcallmedom, @zolkis)
-
Add support for chaining in ExposedThing w3c/wot-scripting-api#92 (3 comments by @danielpeintner, @knimura, @zolkis)
-
w3c/wot-security
-
8 issues opened.
-
Implementation of security support in node-wot w3c/wot-security#73, by @mkovatsc.
-
Discussion of WoT Fingerprinting Risks w3c/wot-security#72, by @jasonanovak.
-
Privacy Risks of The Things Directory, WoT Servient Gateway, and Gateway w3c/wot-security#71, by @jasonanovak.
-
Require Not Exposing Immutable Hardware Identifiers? w3c/wot-security#70, by @jasonanovak.
-
Passive Observers Risk w3c/wot-security#69, by @jasonanovak.
-
Thing Provider Data Specification w3c/wot-security#68, by @jasonanovak.
-
Role of Consent w3c/wot-security#67, by @jasonanovak.
-
Role of Platforms in WoT w3c/wot-security#66, by @jasonanovak.
-
-
3 issues received 3 new comments.
-
1 pull request received 5 new comments.
w3c/wot-binding-templates
-
3 issues opened.
-
Ex. 11 uses non-existing HTTP vocabulary term w3c/wot-binding-templates#30, by @vcharpenay.
-
Revising the 'form' vocabulary? w3c/wot-binding-templates#29, by @mkovatsc.
-
Is a binding template specification necessary? w3c/wot-binding-templates#28, by @benfrancis.
-
-
6 issues received 48 new comments.
-
Binding for next PlugFest (Prague 2018) w3c/wot-binding-templates#13 (22 comments by @handrews, @mjkoster, @mkovatsc, @sebastiankb, @vcharpenay, @zolkis)
-
Is a binding template specification necessary? w3c/wot-binding-templates#28 (13 comments by @benfrancis, @draggett, @mkovatsc, @zolkis)
-
RDF-compliant inputData/outputData modeling w3c/wot-binding-templates#23 (8 comments by @draggett, @mjkoster, @mkovatsc, @zolkis)
-
-
4 pull requests opened.
-
update dataSchema elements w3c/wot-binding-templates#31, by @mjkoster.
-
added CoAP vocab, designed after the HTTP RDF vocab w3c/wot-binding-templates#27, by @vcharpenay.
-
Update examples based on TD spec w3c/wot-binding-templates#26, by @yamagile.
-
-
3 pull requests merged.
-
Update examples based on TD spec w3c/wot-binding-templates#26.
-
Master w3c/wot-binding-templates#25.
-
added CoAP vocab, designed after the HTTP RDF vocab w3c/wot-binding-templates#27.
-
-
2 pull requests received 6 new comments.
-
Update examples based on TD spec w3c/wot-binding-templates#26 (3 comments by @mkovatsc, @vcharpenay, @yamagile)
-
update dataSchema elements w3c/wot-binding-templates#31 (3 comments by @mjkoster, @vcharpenay, @zolkis)
-
w3c/wot-architecture
-
1 issue opened.
-
Working Draft for Prague PlugFest w3c/wot-architecture#49, by @mkovatsc.
-
-
2 issues received 4 new comments.
Participants
-
1 organization joined.
-
Worldpay - FIS joined.
-
GitHub
w3c/wot-scripting-api
-
3 issues opened.
-
Dynamic update of Thing model may break clients w3c/wot-scripting-api#85, by @mlagally.
-
Dynamic Things and semantic vocabularies (`@context`) w3c/wot-scripting-api#84, by @mkovatsc.
-
Add means to indicate static/dynamic status of TD w3c/wot-scripting-api#83, by @mmccool.
-
-
5 issues received 12 new comments.
-
API for next PlugFest (Prague 2018) w3c/wot-scripting-api#82 (6 comments by @danielpeintner, @zolkis)
-
Dynamic update of Thing model may break clients w3c/wot-scripting-api#85 (2 comments by @mkovatsc, @zolkis)
-
Dynamic Things and semantic vocabularies (`@context`) w3c/wot-scripting-api#84 (2 comments by @mkovatsc, @zolkis)
-
-
1 pull request opened.
-
Update the API according to discussion in #82 and #78 w3c/wot-scripting-api#86, by @zolkis.
-
-
1 pull request received 6 new comments.
-
Update the API according to discussion in #82 and #78 w3c/wot-scripting-api#86 (6 comments by @mkovatsc, @zolkis)
-
w3c/wot-thing-description
-
5 issues opened.
-
Definition of baseUri and href w3c/wot-thing-description#81, by @sebastiankb.
-
Default @context with http, https, or both? w3c/wot-thing-description#80, by @danielpeintner.
-
Start on experimental JSON Thing Description serialization (cont.) w3c/wot-thing-description#76, by @sebastiankb.
-
Section "5.2.6 DataSchema" should be independent from the serialisation format w3c/wot-thing-description#75, by @mlagally.
-
Pragmatic TD validation w3c/wot-thing-description#74, by @mlagally.
-
-
2 issues closed.
-
[TF-TD] href in DataSchema w3c/wot-thing-description#9.
-
Links becoming Web Forms w3c/wot-thing-description#62.
-
-
10 issues received 14 new comments.
-
Examples 27 and 28 of the document missing context w3c/wot-thing-description#69 (4 comments by @onovo1, @sebastiankb)
-
Start on experimental JSON Thing Description serialization (cont.) w3c/wot-thing-description#76 (1 comment by @draggett)
-
(Intentional?) Removal of stability in property w3c/wot-thing-description#29 (1 comment by @sebastiankb)
-
Examples in TD Deliverable do not use right context url w3c/wot-thing-description#68 (1 comment by @sebastiankb)
-
-
5 pull requests opened.
-
typo fix w3c/wot-thing-description#79, by @sebastiankb.
-
typo fix w3c/wot-thing-description#78, by @sebastiankb.
-
Master w3c/wot-thing-description#77, by @mariapoveda.
-
Remove Link label and added "rel" w3c/wot-thing-description#73, by @mariapoveda.
-
link -> form w3c/wot-thing-description#72, by @mariapoveda.
-
-
3 pull requests merged.
-
Master w3c/wot-thing-description#77.
-
Remove Link label and added "rel" w3c/wot-thing-description#73.
-
link -> form w3c/wot-thing-description#72.
-
-
3 pull requests closed.
-
typo fix w3c/wot-thing-description#79.
-
typo fix w3c/wot-thing-description#78.
-
Added cardinality axioms in OWL file w3c/wot-thing-description#55.
-
-
2 pull requests received 3 new comments.
w3c/wot-binding-templates
-
3 issues opened.
-
RDF-compliant inputData/outputData modeling w3c/wot-binding-templates#23, by @mkovatsc.
-
Review Comments: W3C Editor's Draft 23 January 2018 w3c/wot-binding-templates#21, by @mlagally.
-
'base' missing in Example 15 w3c/wot-binding-templates#18, by @sebastiankb.
-
-
2 issues received 8 new comments.
-
RDF-compliant inputData/outputData modeling w3c/wot-binding-templates#23 (5 comments by @mkovatsc, @vcharpenay)
-
Binding for next PlugFest (Prague 2018) w3c/wot-binding-templates#13 (3 comments by @mkovatsc, @mlagally)
-
-
5 pull requests opened.
-
Editorial pass for FPWD w3c/wot-binding-templates#22, by @mkovatsc.
-
vocabulary and pattern update w3c/wot-binding-templates#20, by @mjkoster.
-
Vocabulary update w3c/wot-binding-templates#19, by @mjkoster.
-
Initial spec contribution w3c/wot-binding-templates#17, by @mjkoster.
-
5 pull requests merged.
-
typo fix w3c/wot-binding-templates#24.
-
Editorial pass for FPWD w3c/wot-binding-templates#22.
-
vocabulary and pattern update w3c/wot-binding-templates#20.
-
Vocabulary update w3c/wot-binding-templates#19.
-
Initial spec contribution w3c/wot-binding-templates#17.
-
-
2 pull requests received 4 new comments.
w3c/wot-architecture
-
1 issue opened.
-
Thing Discovery w3c/wot-architecture#48, by @NZSmartie.
-
-
1 issue received 2 new comments.
w3c/wot-security
-
2 issues opened.
-
Consider moving Thing lifecycle discussion to Architecture w3c/wot-security#65, by @mmccool.
-
Do TD updates cause (or arise from) security issues? w3c/wot-security#64, by @mmccool.
-
-
2 issues closed.
-
Align Threat model with IETF IoT RFC w3c/wot-security#40.
-
Upgrade ref links to https if possible w3c/wot-security#60.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
initial text for lifecycle w3c/wot-security#63, by @ereshetova.
-
-
1 pull request merged.
-
Addressing various open issues w3c/wot-security#62.
-
-
2 pull requests received 2 new comments.