Web of Things Working Group - Activity in 2021
No matches.
Participants
-
1 participant left.
-
lulu xie (Alibaba Group) left.
-
GitHub
w3c/wot-thing-description
-
15 issues opened.
-
op default values definition needs rethinking w3c/wot-thing-description#1346, by @egekorkan.
-
Wrong validation errors with SHACL w3c/wot-thing-description#1345, by @egekorkan.
-
Dereference 1.1 context file via new TD 1.1 IRI w3c/wot-thing-description#1343, by @sebastiankb.
-
title must be mandatory for properties, actions and events w3c/wot-thing-description#1338, by @mlagally.
-
Unclear what "Protocol Binding document" refers to in section 8.3 w3c/wot-thing-description#1326, by @benfrancis.
-
clarify whether vocabulary terms in the information model are case sensitive w3c/wot-thing-description#1325, by @mlagally.
-
Feedback on latest Editor's Draft w3c/wot-thing-description#1324, by @benfrancis.
-
Missing event/notification affordance or operation w3c/wot-thing-description#1323, by @mlagally.
-
Please address comments in https://github.com/w3c/wot-thing-description/pull/1301#pullrequestreview-826651669 w3c/wot-thing-description#1321, by @mlagally.
-
Removing Overview.html file w3c/wot-thing-description#1316, by @egekorkan.
-
[Editorial] HTML checkers shows errors w3c/wot-thing-description#1314, by @danielpeintner.
-
Add SHOULD assertion to security schemes that need TLS to be secure w3c/wot-thing-description#1313, by @mmccool.
-
Add more uriVariables examples w3c/wot-thing-description#1312, by @egekorkan.
-
[validation] Reorganize schema to have one inherited form schema w3c/wot-thing-description#1311, by @egekorkan.
-
hctl:hasTarget as a DatatypeProperty ? w3c/wot-thing-description#1310, by @ethieblin.
-
-
10 issues closed.
-
Add more uriVariables examples w3c/wot-thing-description#1312.
-
We need an OAuth2 example for TD 1.1 w3c/wot-thing-description#948.
-
title/titles and description/descriptions definition with global `@language` in the context w3c/wot-thing-description#1302.
-
Example misses default for observable w3c/wot-thing-description#1293.
-
Clarify readOnly/writeOnly w3c/wot-thing-description#1299.
-
Link Checker Errors w3c/wot-thing-description#1273.
-
Introduction is missing security component w3c/wot-thing-description#904.
-
Small typo regarding 5.3.1.1 w3c/wot-thing-description#925.
-
New terms hardwareRevision and softwareRevision? w3c/wot-thing-description#947.
-
New term 'serialNumber'? w3c/wot-thing-description#946.
-
-
1 issue reopened.
-
Evaluate geolocation terms in TD model (input from Profile TF) w3c/wot-thing-description#941, by @mlagally.
-
-
36 issues received 75 new comments.
-
Missing event/notification affordance or operation w3c/wot-thing-description#1323 (15 comments by @benfrancis, @chachamimm, @egekorkan, @mlagally, @relu91, @sebastiankb)
-
Unclear what "Protocol Binding document" refers to in section 8.3 w3c/wot-thing-description#1326 (7 comments by @benfrancis, @egekorkan, @mlagally, @relu91)
-
title must be mandatory for properties, actions and events w3c/wot-thing-description#1338 (5 comments by @egekorkan, @mlagally, @relu91, @sebastiankb)
-
Feedback on latest Editor's Draft w3c/wot-thing-description#1324 (4 comments by @benfrancis, @danielpeintner, @sebastiankb)
-
Please address comments in https://github.com/w3c/wot-thing-description/pull/1301#pullrequestreview-826651669 w3c/wot-thing-description#1321 (3 comments by @egekorkan, @mlagally, @relu91)
-
Make it clear that operation names are case sensitive w3c/wot-thing-description#1303 (3 comments by @danielpeintner, @egekorkan, @mlagally)
-
Evaluate geolocation terms in TD model (input from Profile TF) w3c/wot-thing-description#941 (3 comments by @egekorkan, @mlagally)
-
rel:type to multiple TMs w3c/wot-thing-description#1265 (3 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
We need extension ontology to include implicit and password flows in OAuth2 w3c/wot-thing-description#949 (2 comments by @mmccool, @relu91)
-
Clarify InteractionAffordance::contentType vs DataSchema::type w3c/wot-thing-description#839 (1 comment by @egekorkan)
-
Where to place the HTTP Default Binding and which format w3c/wot-thing-description#1274 (1 comment by @sebastiankb)
-
Self reference and unsolicited operation for events and properties w3c/wot-thing-description#1224 (1 comment by @egekorkan)
-
Consider defining additional vocabulary supporting Discovery w3c/wot-thing-description#1033 (1 comment by @mmccool)
-
[validation] Changing `oneOf` to `anyOf` for the validation of security scheme w3c/wot-thing-description#1055 (1 comment by @mmccool)
-
Guarantee RDF round-tripping for security definitions w3c/wot-thing-description#1125 (1 comment by @mmccool)
-
Canonicalization - Step 6 w.r.t. single value needed? w3c/wot-thing-description#1287 (1 comment by @mmccool)
-
Add SHOULD assertion to security schemes that need TLS to be secure w3c/wot-thing-description#1313 (1 comment by @egekorkan)
-
Introducing assumptions about TD instances that have no IP addresses w3c/wot-thing-description#977 (1 comment by @sebastiankb)
-
title/titles and description/descriptions definition with global `@language` in the context w3c/wot-thing-description#1302 (1 comment by @vcharpenay)
-
Consider removing section 9.3.1 Protocol Binding based on HTTP in version 1.1 w3c/wot-thing-description#1259 (1 comment by @sebastiankb)
-
Please check if the rules of chapter 5.2 are valid for a TM w3c/wot-thing-description#1300 (1 comment by @sebastiankb)
-
Move "canonical TD" terminology to architecture w3c/wot-thing-description#1297 (1 comment by @mlagally)
-
-
25 pull requests opened.
-
fix: object definition ref in ObjectSchema w3c/wot-thing-description#1344, by @relu91.
-
reorganize how to use uri schemes w3c/wot-thing-description#1342, by @egekorkan.
-
schema term in expected response w3c/wot-thing-description#1341, by @sebastiankb.
-
Manifest w3c/wot-thing-description#1340, by @sebastiankb.
-
update assertion td-context-ns-thing-mandatory w3c/wot-thing-description#1339, by @sebastiankb.
-
fix: minor singular vs plural issue w3c/wot-thing-description#1337, by @danielpeintner.
-
fix: some internal links w3c/wot-thing-description#1336, by @danielpeintner.
-
fix: typos and grammatical errors w3c/wot-thing-description#1335, by @danielpeintner.
-
TD Info Model fixes w3c/wot-thing-description#1334, by @sebastiankb.
-
update abstract w3c/wot-thing-description#1333, by @sebastiankb.
-
fix: some HTML markup issues w3c/wot-thing-description#1332, by @danielpeintner.
-
fix: move CBOR content types their own table row in section 5.3.2 w3c/wot-thing-description#1331, by @JKRhb.
-
Event consumer: Alternative 2 - event consumer affordance w3c/wot-thing-description#1330, by @mlagally.
-
Event consumer: Alternative 1 - event operation w3c/wot-thing-description#1329, by @mlagally.
-
Delete Overview.html w3c/wot-thing-description#1328, by @egekorkan.
-
fix(ontology): Use ontology URI and dcterms instead of dc w3c/wot-thing-description#1327, by @ethieblin.
-
fix: typos w3c/wot-thing-description#1322, by @danielpeintner.
-
Comment out unneeded editor's notes w3c/wot-thing-description#1320, by @mmccool.
-
Make forms inherited from a base form w3c/wot-thing-description#1319, by @egekorkan.
-
provide new namespaces for TD 1.1 w3c/wot-thing-description#1318, by @sebastiankb.
-
Adding id to tables w3c/wot-thing-description#1317, by @egekorkan.
-
add more urivariables examples w3c/wot-thing-description#1315, by @egekorkan.
-
New sub-sections to improve reading in Section 6.3 w3c/wot-thing-description#1309, by @sebastiankb.
-
Fix roundtripping with language tags w3c/wot-thing-description#1308, by @vcharpenay.
-
fix observable default assumption in Example 4 w3c/wot-thing-description#1307, by @sebastiankb.
-
-
12 pull requests merged.
-
fix: typos w3c/wot-thing-description#1322.
-
add more urivariables examples w3c/wot-thing-description#1315.
-
provide new namespaces for TD 1.1 w3c/wot-thing-description#1318.
-
Comment out unneeded editor's notes w3c/wot-thing-description#1320.
-
New sub-sections to improve reading in Section 6.3 w3c/wot-thing-description#1309.
-
update Section 8.3 w3c/wot-thing-description#1301.
-
Fix 948 (add OAuth2 flow examples) w3c/wot-thing-description#1264.
-
Fix roundtripping with language tags w3c/wot-thing-description#1308.
-
fix observable default assumption in Example 4 w3c/wot-thing-description#1307.
-
refactor: clarify that property can be retrieved and/or updated w3c/wot-thing-description#1306.
-
Fix links reported by LinkChecker w3c/wot-thing-description#1305.
-
Remove TD Canonicalization w3c/wot-thing-description#1304.
-
-
22 pull requests received 81 new comments.
-
TD Info Model fixes w3c/wot-thing-description#1334 (19 comments by @mlagally, @relu91, @sebastiankb)
-
Event consumer: Alternative 1 - event operation w3c/wot-thing-description#1329 (7 comments by @egekorkan, @mlagally, @sebastiankb)
-
Event consumer: Alternative 2 - event consumer affordance w3c/wot-thing-description#1330 (6 comments by @egekorkan, @mlagally, @relu91, @sebastiankb)
-
Fix roundtripping with language tags w3c/wot-thing-description#1308 (6 comments by @ethieblin, @Murloc6, @vcharpenay)
-
update Section 8.3 w3c/wot-thing-description#1301 (5 comments by @egekorkan, @mlagally, @sebastiankb)
-
add more urivariables examples w3c/wot-thing-description#1315 (4 comments by @benfrancis, @egekorkan, @sebastiankb)
-
Fix 948 (add OAuth2 flow examples) w3c/wot-thing-description#1264 (4 comments by @mmccool, @relu91, @sebastiankb)
-
schema term in expected response w3c/wot-thing-description#1341 (3 comments by @benfrancis, @egekorkan, @sebastiankb)
-
provide new namespaces for TD 1.1 w3c/wot-thing-description#1318 (3 comments by @egekorkan, @sebastiankb)
-
fix observable default assumption in Example 4 w3c/wot-thing-description#1307 (3 comments by @danielpeintner, @sebastiankb)
-
update assertion td-context-ns-thing-mandatory w3c/wot-thing-description#1339 (2 comments by @danielpeintner, @sebastiankb)
-
fix: move CBOR content types their own table row in section 5.3.2 w3c/wot-thing-description#1331 (2 comments by @danielpeintner, @JKRhb)
-
New sub-sections to improve reading in Section 6.3 w3c/wot-thing-description#1309 (1 comment by @sebastiankb)
-
refactor: clarify that property can be retrieved and/or updated w3c/wot-thing-description#1306 (1 comment by @sebastiankb)
-
w3c/wot-architecture
-
11 issues opened.
-
Cross link Section 5 and Section 6 with corresponding use cases w3c/wot-architecture#670, by @mlagally.
-
Need to have a description of "orchestration" deployment topologies in chapter 6 w3c/wot-architecture#666, by @mlagally.
-
Need to have a description of "virtual things" in chapter 6 w3c/wot-architecture#664, by @mlagally.
-
Remove op value table from Arch Spec w3c/wot-architecture#663, by @sebastiankb.
-
Need to have a description of a telemetry system topology in chapter 6 w3c/wot-architecture#661, by @mlagally.
-
Illustration for differentiation between Thing model vs Thing w3c/wot-architecture#657, by @mlagally.
-
Producer is missing in terminology section w3c/wot-architecture#656, by @sebastiankb.
-
Editorial cleanup before publication w3c/wot-architecture#652, by @mlagally.
-
Make System integration section informative w3c/wot-architecture#648, by @mlagally.
-
Make Device categories informative w3c/wot-architecture#647, by @mlagally.
-
[Index] Section structure, assertions, and issues w3c/wot-architecture#646, by @k-toumura.
-
-
10 issues closed.
-
`arch-property-readable` : The state exposed by a Property MUST be retrievable (readable). w3c/wot-architecture#633.
-
Make System integration section informative w3c/wot-architecture#648.
-
Update Terminology regarding Binding Templates w3c/wot-architecture#611.
-
Move terminology section from discovery to architecture spec w3c/wot-architecture#613.
-
Make Device categories informative w3c/wot-architecture#647.
-
1 issue reopened.
-
`arch-thing-bundling` : Things MAY be bundled together with a Consumer to enable Thing-to-Thing interaction. w3c/wot-architecture#634, by @sebastiankb.
-
-
20 issues received 24 new comments.
-
Need to have a description of a telemetry system topology in chapter 6 w3c/wot-architecture#661 (2 comments by @mlagally)
-
`arch-thing-bundling` : Things MAY be bundled together with a Consumer to enable Thing-to-Thing interaction. w3c/wot-architecture#634 (2 comments by @mlagally, @sebastiankb)
-
[Index] Section structure, assertions, and issues w3c/wot-architecture#646 (2 comments by @egekorkan, @k-toumura)
-
Illustration for differentiation between Thing model vs Thing w3c/wot-architecture#657 (1 comment by @mlagally)
-
Need to have a description of "virtual things" in chapter 6 w3c/wot-architecture#664 (1 comment by @mlagally)
-
`arch-op-wellknown-compare` : Well-known operation types MUST be compared using a case-insensitive comparison. w3c/wot-architecture#637 (1 comment by @mlagally)
-
Identify normative RFC2119 assertions that affect the TD specification w3c/wot-architecture#642 (1 comment by @mlagally)
-
Relationship between "8.7 Protocol Bindings" and "9.5 WoT Binding Templates" w3c/wot-architecture#608 (1 comment by @mlagally)
-
Review Chapter 6.7 in relation to Binding Templates 4.1 w3c/wot-architecture#617 (1 comment by @mlagally)
-
`arch-property-readable` : The state exposed by a Property MUST be retrievable (readable). w3c/wot-architecture#633 (1 comment by @sebastiankb)
-
-
15 pull requests opened.
-
Add a figure of Thing Model w3c/wot-architecture#671, by @k-toumura.
-
Producer definition w3c/wot-architecture#669, by @sebastiankb.
-
remove remove-arch-op-wellknown-compare assertion w3c/wot-architecture#668, by @mlagally.
-
adding placeholder section for virtual things w3c/wot-architecture#667, by @mlagally.
-
placeholder section on orchestration w3c/wot-architecture#665, by @mlagally.
-
remove arch-uri-scheme w3c/wot-architecture#662, by @sebastiankb.
-
editors note on telemetry w3c/wot-architecture#660, by @mlagally.
-
remove assertation arch-op-extension w3c/wot-architecture#659, by @sebastiankb.
-
Improve section structure w3c/wot-architecture#658, by @mlagally.
-
address #633 w3c/wot-architecture#655, by @sebastiankb.
-
remove assertations w3c/wot-architecture#654, by @sebastiankb.
-
Remove an assertion `arch-hypermedia-origin` w3c/wot-architecture#653, by @k-toumura.
-
Remove `arch-consumer-configuration` w3c/wot-architecture#651, by @k-toumura.
-
remove arch-methods assertion and section w3c/wot-architecture#650, by @relu91.
-
[Editorial] Make sections informative w3c/wot-architecture#649, by @k-toumura.
-
-
11 pull requests merged.
-
editors note on telemetry w3c/wot-architecture#660.
-
remove assertation arch-op-extension w3c/wot-architecture#659.
-
address #633 w3c/wot-architecture#655.
-
remove assertations w3c/wot-architecture#654.
-
Remove an assertion `arch-hypermedia-origin` w3c/wot-architecture#653.
-
Remove `arch-consumer-configuration` w3c/wot-architecture#651.
-
remove arch-methods assertion and section w3c/wot-architecture#650.
-
[Editorial] Make sections informative w3c/wot-architecture#649.
-
improve description of device categories w3c/wot-architecture#645.
-
Move common terms from Discovery to Architecture w3c/wot-architecture#644.
-
Address Binding Templates related issues w3c/wot-architecture#615.
-
-
4 pull requests received 5 new comments.
w3c/wot-binding-templates
-
2 issues opened.
-
Formalize the concept of `Data Schema Values`. w3c/wot-binding-templates#141, by @relu91.
-
XML template is more for green field devices w3c/wot-binding-templates#139, by @relu91.
-
-
2 issues closed.
-
Formalize the concept of `Data Schema Values`. w3c/wot-binding-templates#141.
-
MQTT and Modbus does not meet the architecture eligible criteria for a protocol binding w3c/wot-binding-templates#137.
-
-
3 issues received 19 new comments.
-
Formalize the concept of `Data Schema Values`. w3c/wot-binding-templates#141 (10 comments by @egekorkan, @relu91, @zolkis)
-
XML template is more for green field devices w3c/wot-binding-templates#139 (8 comments by @danielpeintner, @egekorkan, @relu91)
-
MQTT and Modbus does not meet the architecture eligible criteria for a protocol binding w3c/wot-binding-templates#137 (1 comment by @egekorkan)
-
-
2 pull requests opened.
-
Align mqtt document with the current project set-up w3c/wot-binding-templates#142, by @relu91.
-
Introduce draft for text binding template w3c/wot-binding-templates#140, by @relu91.
-
-
1 pull request received 5 new comments.
-
Align mqtt document with the current project set-up w3c/wot-binding-templates#142 (5 comments by @egekorkan, @JKRhb, @relu91)
-
w3c/wot-profile
-
6 issues opened.
-
Profile requirements w3c/wot-profile#156, by @mlagally.
-
Agree on a common definition of "out-of-the-box-interoperability" w3c/wot-profile#155, by @mlagally.
-
Describe Profile deployment scenarios w3c/wot-profile#154, by @mlagally.
-
Make base URI mandatory? w3c/wot-profile#153, by @mlagally.
-
Propose an outline for a new profile document w3c/wot-profile#152, by @mlagally.
-
Consolidate Error responses w3c/wot-profile#151, by @mlagally.
-
-
1 issue reopened.
-
Propose an outline for a new profile document w3c/wot-profile#152, by @mlagally.
-
-
10 issues received 63 new comments.
-
Propose an outline for a new profile document w3c/wot-profile#152 (29 comments by @ashimura, @benfrancis, @chachamimm, @egekorkan, @mlagally, @mmccool, @mryuichi)
-
Agree on a common definition of "out-of-the-box-interoperability" w3c/wot-profile#155 (10 comments by @benfrancis, @mlagally, @relu91)
-
Profile requirements w3c/wot-profile#156 (5 comments by @benfrancis, @k-toumura, @mryuichi, @relu91)
-
"Core" profile name has undesired implications w3c/wot-profile#5 (4 comments by @benfrancis, @danielpeintner)
-
Make base URI mandatory? w3c/wot-profile#153 (3 comments by @benfrancis, @danielpeintner, @mryuichi)
-
Allow multiple forms for interaction affordances in Core Profile w3c/wot-profile#60 (1 comment by @relu91)
-
-
1 pull request opened.
-
event-payload-format w3c/wot-profile#150, by @mlagally.
-
-
1 pull request closed.
-
Canonical representation 2 w3c/wot-profile#57.
-
-
8 pull requests received 27 new comments.
-
Remove WoT Core Data Model and update Core Profile introduction - closes #10 w3c/wot-profile#125 (2 comments by @benfrancis, @mlagally)
-
Add timestamps to actions protocol binding - closes #101 w3c/wot-profile#127 (2 comments by @mlagally)
-
Add timestamps to event protocol binding - closes #100 w3c/wot-profile#119 (1 comment by @benfrancis)
w3c/wot-scripting-api
-
4 issues opened.
-
Should we publish TS types also for `ThingModel`? w3c/wot-scripting-api#361, by @relu91.
-
Consider moving terminology definition to WoT Architecture w3c/wot-scripting-api#360, by @mlagally.
-
FIX ECMASCRIPT references w3c/wot-scripting-api#358, by @danielpeintner.
-
Correctly reference internal slots w3c/wot-scripting-api#357, by @relu91.
-
-
3 issues closed.
-
FIX ECMASCRIPT references w3c/wot-scripting-api#358.
-
Reference terminology section of the architecture specification w3c/wot-scripting-api#342.
-
`subscribeEvent` and `observerProperty` misaligned signature w3c/wot-scripting-api#343.
-
-
10 issues received 30 new comments.
-
Rename Use Cases section ? w3c/wot-scripting-api#355 (14 comments by @chachamimm, @danielpeintner, @mlagally, @relu91, @zolkis)
-
Discussion about read- write-/multipleproperties w3c/wot-scripting-api#219 (5 comments by @danielpeintner, @relu91, @zolkis)
-
Should we publish TS types also for `ThingModel`? w3c/wot-scripting-api#361 (1 comment by @danielpeintner)
-
Consider moving terminology definition to WoT Architecture w3c/wot-scripting-api#360 (1 comment by @zolkis)
-
Reference terminology section of the architecture specification w3c/wot-scripting-api#342 (1 comment by @danielpeintner)
-
`subscribeEvent` and `observerProperty` misaligned signature w3c/wot-scripting-api#343 (1 comment by @relu91)
-
-
2 pull requests opened.
-
Mark repo as host of note track work w3c/wot-scripting-api#359, by @dontcallmedom.
-
Allow only one subscription per affordance w3c/wot-scripting-api#356, by @relu91.
-
-
3 pull requests merged.
-
Allow only one subscription per affordance w3c/wot-scripting-api#356.
-
Mark repo as host of note track work w3c/wot-scripting-api#359.
-
refactor: move section "Terminology and conventions" right after "Conformance" w3c/wot-scripting-api#353.
-
-
3 pull requests received 14 new comments.
-
Allow only one subscription per affordance w3c/wot-scripting-api#356 (10 comments by @danielpeintner, @relu91, @zolkis)
-
refactor: move section "Terminology and conventions" right after "Conformance" w3c/wot-scripting-api#353 (3 comments by @danielpeintner, @zolkis)
-
w3c/wot-discovery
-
4 issues opened.
-
Multiple Responses from Peer-to-Peer Discovery w3c/wot-discovery#249, by @mmccool.
-
XPath response data model w3c/wot-discovery#247, by @farshidtz.
-
TDD Handle extra parameters when publishing/extensibility of the creation endpoint w3c/wot-discovery#246, by @relu91.
-
Disallow SPARQL UPDATE operations w3c/wot-discovery#245, by @farshidtz.
-
-
4 issues closed.
-
XPath response data model w3c/wot-discovery#247.
-
JSONPath response data model w3c/wot-discovery#156.
-
Make XPath optional/informative w3c/wot-discovery#238.
-
Move common terminology to the Architecture spec w3c/wot-discovery#240.
-
-
1 issue reopened.
-
Directories should notify subscribers when a TD is updated w3c/wot-discovery#28, by @egekorkan.
-
-
10 issues received 20 new comments.
-
Directories should notify subscribers when a TD is updated w3c/wot-discovery#28 (3 comments by @egekorkan, @farshidtz)
-
Multiple Responses from Peer-to-Peer Discovery w3c/wot-discovery#249 (3 comments by @benfrancis, @mmccool)
-
Disallow SPARQL UPDATE operations w3c/wot-discovery#245 (3 comments by @AndreaCimminoArriaga, @mmccool, @wiresio)
-
"Thing description" for Directory should be a "Thing Model" w3c/wot-discovery#86 (1 comment by @mmccool)
-
TDD Handle extra parameters when publishing/extensibility of the creation endpoint w3c/wot-discovery#246 (1 comment by @farshidtz)
-
5 pull requests opened.
-
Refactor event affordance and event type naming w3c/wot-discovery#251, by @farshidtz.
-
Incremental transfer as Performance Consideration w3c/wot-discovery#250, by @farshidtz.
-
Change XPath response to allow all responses w3c/wot-discovery#248, by @farshidtz.
-
Make XPath informative w3c/wot-discovery#244, by @farshidtz.
-
Add slight wording changes w3c/wot-discovery#243, by @wiresio.
-
-
4 pull requests merged.
-
Change XPath response to allow all responses w3c/wot-discovery#248.
-
Add slight wording changes w3c/wot-discovery#243.
-
Make XPath informative w3c/wot-discovery#244.
-
Delete common terms in terminology section w3c/wot-discovery#241.
-
-
2 pull requests received 11 new comments.
w3c/wot-security
-
1 issue received 1 new comment.
-
Terminology inconsistency - Proxy and Gateway are used interchangeably. w3c/wot-security#123 (1 comment by @mmccool)
-
w3c/wot-security-best-practices
-
2 issues opened.
-
Separate local and offline sections; they have distinct needs w3c/wot-security-best-practices#30, by @mmccool.
-
2 issues closed.
-
Update Secure Local Transport w3c/wot-security-best-practices#13.
-
Add Onboarding/Key Distribution Section w3c/wot-security-best-practices#27.
-
-
2 issues received 2 new comments.
-
Add a best practice description on logging security events w3c/wot-security-best-practices#3 (1 comment by @mmccool)
-
1 pull request merged.
-
Local transport and secure onboarding w3c/wot-security-best-practices#28.
-
Participants
-
1 participant left.
-
Clerley Silveira (Conexxus) left.
-
GitHub
w3c/wot-profile
-
21 issues opened.
-
Outdated reference to Architecture spec w3c/wot-profile#144, by @mlagally.
-
Outdated reference to TD spec w3c/wot-profile#143, by @mlagally.
-
Clarify RFC7807 Problem Details Format constraints w3c/wot-profile#142, by @mlagally.
-
how to handle multiple forms w3c/wot-profile#141, by @mlagally.
-
Add reference to security best practices document w3c/wot-profile#140, by @mlagally.
-
generic UI support w3c/wot-profile#138, by @mlagally.
-
Geolocation w3c/wot-profile#137, by @mlagally.
-
Support Class-0 and Class-1 devices w3c/wot-profile#136, by @mlagally.
-
Structured event object w3c/wot-profile#134, by @mlagally.
-
Normative Canonicalisation format w3c/wot-profile#132, by @mlagally.
-
Describe key use cases for Profiles w3c/wot-profile#128, by @mlagally.
-
Dependency on Cloud Events w3c/wot-profile#126, by @egekorkan.
-
Consider removing the External TD representations section w3c/wot-profile#122, by @benfrancis.
-
Complete or remove JSON Schema of the Core Profile w3c/wot-profile#120, by @benfrancis.
-
Review Abstract & Introduction w3c/wot-profile#115, by @benfrancis.
-
Add Links section to Core Profile w3c/wot-profile#114, by @benfrancis.
-
Remove `Accept` headers from requests with no response payloads w3c/wot-profile#113, by @benfrancis.
-
Add Discovery section to Core Profile w3c/wot-profile#112, by @benfrancis.
-
Add Identifier section to Core Profile w3c/wot-profile#111, by @benfrancis.
-
Blocker for publication w3c/wot-profile#110, by @mlagally.
-
-
6 issues closed.
-
Highlighting assertions w3c/wot-profile#74.
-
Consider removing the External TD representations section w3c/wot-profile#122.
-
Core/default profile should mandate HTTP support as a minimum requirement w3c/wot-profile#24.
-
HTTP Protocol Binding duplicated in TD spec w3c/wot-profile#11.
-
Term 'Core' may cause a false impression w3c/wot-profile#21.
-
Way to identify profile(s) w3c/wot-profile#2.
-
-
1 issue reopened.
-
Reduce or remove the constraints in section 7.2 Baseline Information Model w3c/wot-profile#10, by @benfrancis.
-
-
54 issues received 132 new comments.
-
how to handle multiple forms w3c/wot-profile#141 (11 comments by @benfrancis, @danielpeintner, @egekorkan, @mlagally, @sebastiankb)
-
Events - Scalable event mechanism for cloud use cases w3c/wot-profile#107 (11 comments by @benfrancis, @egekorkan, @mlagally)
-
Events need a way to express timestamps w3c/wot-profile#100 (10 comments by @benfrancis, @egekorkan, @mlagally)
-
generic UI support w3c/wot-profile#138 (7 comments by @benfrancis, @danielpeintner, @egekorkan, @mlagally)
-
Normative Canonicalisation format w3c/wot-profile#132 (6 comments by @benfrancis, @egekorkan, @mlagally)
-
Actions need a way to express time stamps w3c/wot-profile#101 (6 comments by @benfrancis, @mlagally)
-
Complete or remove JSON Schema of the Core Profile w3c/wot-profile#120 (5 comments by @egekorkan, @mlagally)
-
Clarify RFC7807 Problem Details Format constraints w3c/wot-profile#142 (3 comments by @benfrancis, @farshidtz)
-
Support Class-0 and Class-1 devices w3c/wot-profile#136 (3 comments by @benfrancis, @egekorkan, @jyhi)
-
Allow multiple forms for interaction affordances in Core Profile w3c/wot-profile#60 (2 comments by @benfrancis, @mlagally)
-
Consider removing the External TD representations section w3c/wot-profile#122 (2 comments by @benfrancis, @mlagally)
-
Actions Improvements: order of return values w3c/wot-profile#104 (2 comments by @benfrancis, @mlagally)
-
Reduce or remove the constraints in section 7.2 Baseline Information Model w3c/wot-profile#10 (2 comments by @benfrancis)
-
Reference Device Definition for the smallest possible platform for HTTP / TCP / JSON w3c/wot-profile#68 (2 comments by @benfrancis, @egekorkan)
-
Server Sent Events section to reference a stable reliable specification w3c/wot-profile#98 (1 comment by @benfrancis)
-
Should the Core Profile define a protocol binding for `observeproperty`/`unobserveproperty`? w3c/wot-profile#95 (1 comment by @benfrancis)
-
Eliminate ednote on single array elements (string vs array of [string]) ? w3c/wot-profile#64 (1 comment by @benfrancis)
-
Action affordance - check input / output type restrictions w3c/wot-profile#40 (1 comment by @benfrancis)
-
Core/default profile should mandate HTTP support as a minimum requirement w3c/wot-profile#24 (1 comment by @benfrancis)
-
-
20 pull requests opened.
-
Remove vocabulary note - closes #17 w3c/wot-profile#149, by @benfrancis.
-
Specify JSON serialisation of Problem Details Format - closes #142 w3c/wot-profile#148, by @benfrancis.
-
Update references to WoT Architecture 1.1 - closes #144 w3c/wot-profile#147, by @benfrancis.
-
Update references to WoT Thing Description 1.1 - closes #143 w3c/wot-profile#146, by @benfrancis.
-
removing outdated+obsolete content w3c/wot-profile#145, by @mlagally.
-
Define order of arrays in queryallactions - closes #104 w3c/wot-profile#135, by @benfrancis.
-
Reinstating the Open Issues section w3c/wot-profile#133, by @mlagally.
-
initial draft of a "common constraints" section w3c/wot-profile#131, by @mlagally.
-
Add Use cases section w3c/wot-profile#130, by @mlagally.
-
Introduction to use cases for profiles w3c/wot-profile#129, by @mlagally.
-
Add timestamps to actions protocol binding - closes #101 w3c/wot-profile#127, by @benfrancis.
-
Remove WoT Core Data Model and update Core Profile introduction - closes #10 w3c/wot-profile#125, by @benfrancis.
-
Move and reword Security section w3c/wot-profile#124, by @benfrancis.
-
Remove External TD representations section - closes #122 w3c/wot-profile#123, by @benfrancis.
-
Add Discovery section to HTTP Baseline Profile - closes #112 w3c/wot-profile#121, by @benfrancis.
-
Add timestamps to event protocol binding - closes #100 w3c/wot-profile#119, by @benfrancis.
-
Remove redundant Accept headers - closes #113 w3c/wot-profile#118, by @benfrancis.
-
Add Identifier section to Core Profile - closes #111 w3c/wot-profile#117, by @benfrancis.
-
Clean up w3c/wot-profile#116, by @benfrancis.
-
preparing implementation report - cleanup assertions w3c/wot-profile#109, by @mlagally.
-
-
2 pull requests merged.
-
Clean up w3c/wot-profile#116.
-
Remove External TD representations section - closes #122 w3c/wot-profile#123.
-
-
3 pull requests closed.
-
Introduction to use cases for profiles w3c/wot-profile#129.
-
Restructure WoT Core Profile section w3c/wot-profile#78.
-
device categories - initial draft w3c/wot-profile#70.
-
-
15 pull requests received 85 new comments.
-
Remove WoT Core Data Model and update Core Profile introduction - closes #10 w3c/wot-profile#125 (11 comments by @benfrancis, @mlagally, @mryuichi, @sebastiankb)
-
Add timestamps to actions protocol binding - closes #101 w3c/wot-profile#127 (6 comments by @benfrancis, @mlagally)
-
initial draft of a "common constraints" section w3c/wot-profile#131 (4 comments by @benfrancis, @mlagally, @sebastiankb)
-
Add timestamps to event protocol binding - closes #100 w3c/wot-profile#119 (3 comments by @benfrancis, @mlagally)
-
Add Discovery section to HTTP Baseline Profile - closes #112 w3c/wot-profile#121 (3 comments by @benfrancis, @mlagally)
-
Example TD and declarative protocol binding illustration - closes #90 w3c/wot-profile#91 (2 comments by @benfrancis)
-
Add Identifier section to Core Profile - closes #111 w3c/wot-profile#117 (2 comments by @benfrancis, @mlagally)
w3c/wot-thing-description
-
24 issues opened.
-
Make it clear that operation names are case sensitive w3c/wot-thing-description#1303, by @benfrancis.
-
title/titles and description/descriptions definition with global `@language` in the context w3c/wot-thing-description#1302, by @Murloc6.
-
Please check if the rules of chapter 5.2 are valid for a TM w3c/wot-thing-description#1300, by @mlagally.
-
Clarify readOnly/writeOnly w3c/wot-thing-description#1299, by @mlagally.
-
add default values to Class Definitions (Chapter 5.2) w3c/wot-thing-description#1298, by @mlagally.
-
Move "canonical TD" terminology to architecture w3c/wot-thing-description#1297, by @mlagally.
-
Canonicalization - array vs. single value w3c/wot-thing-description#1296, by @danielpeintner.
-
Default Value Definitions should sort security schemes w3c/wot-thing-description#1295, by @danielpeintner.
-
Default value section misses op default for Thing w3c/wot-thing-description#1294, by @danielpeintner.
-
Example misses default for observable w3c/wot-thing-description#1293, by @danielpeintner.
-
internationalization extension of multilang strings w3c/wot-thing-description#1290, by @sebastiankb.
-
Canonicalization - Step 6 w.r.t. single value needed? w3c/wot-thing-description#1287, by @danielpeintner.
-
Canonicalization Bug in sample w3c/wot-thing-description#1286, by @danielpeintner.
-
Default value - Class for observable is wrong w3c/wot-thing-description#1285, by @danielpeintner.
-
UML diagrams contain lines with multiple properties w3c/wot-thing-description#1280, by @mlagally.
-
New TD 1.1 namespace IRI w3c/wot-thing-description#1276, by @sebastiankb.
-
Where to place the HTTP Default Binding and which format w3c/wot-thing-description#1274, by @egekorkan.
-
Link Checker Errors w3c/wot-thing-description#1273, by @egekorkan.
-
Pointer (URI) to descriptions and titles w3c/wot-thing-description#1269, by @Citrullin.
-
Room information w3c/wot-thing-description#1268, by @tkzkno.
-
Red square around W3C Logo? w3c/wot-thing-description#1267, by @egekorkan.
-
tm:submodel missing from rel table w3c/wot-thing-description#1266, by @egekorkan.
-
rel:type to multiple TMs w3c/wot-thing-description#1265, by @egekorkan.
-
Consider removing section 9.3.1 Protocol Binding based on HTTP in version 1.1 w3c/wot-thing-description#1259, by @benfrancis.
-
-
32 issues closed.
-
Good Practice for observe property flow w3c/wot-thing-description#1258.
-
Default value - Class for observable is wrong w3c/wot-thing-description#1285.
-
Default Value Definitions should sort security schemes w3c/wot-thing-description#1295.
-
WOT TD round tripping for securityDefinitions w3c/wot-thing-description#1193.
-
Representation of examples (hidden information) w3c/wot-thing-description#1059.
-
Review resurrected Cert, Public, and PoP SecuritySchemes w3c/wot-thing-description#965.
-
Add a component mechanism to support mashups w3c/wot-thing-description#958.
-
streams and compound values - Issue 281 from w3c/wot w3c/wot-thing-description#934.
-
[multiLang] Should titles and descriptions be present in the TD after language negotation w3c/wot-thing-description#959.
-
No examples for observeproperty and unobserveproperty w3c/wot-thing-description#969.
-
JSON-LD 1.0 will be republished as superseded version w3c/wot-thing-description#970.
-
[ThingModel] Example of Oracle's device model (Festo) w3c/wot-thing-description#999.
-
[ThingModel] Example of Eclipse Vorto model w3c/wot-thing-description#1000.
-
Error in JSON Schema example (ontology doc) w3c/wot-thing-description#1219.
-
Consider defining an expiry date for a TD w3c/wot-thing-description#916.
-
Examples for actions using URI variables should explain why not using input w3c/wot-thing-description#910.
-
Make sure WoT TD and IETF RESTful architectures are consistent w3c/wot-thing-description#906.
-
Consider adding "components" to TD ontology w3c/wot-thing-description#490.
-
JSON Schema security scheme could be moved to a separate file and referenced from the main schema w3c/wot-thing-description#551.
-
Small incoherence in `forms` Thing Description core vocabulary w3c/wot-thing-description#1199.
-
Room information w3c/wot-thing-description#1268.
-
tm:submodel missing from rel table w3c/wot-thing-description#1266.
-
JSON Schema issue / request w3c/wot-thing-description#1235.
-
JSON schema misses ExpectedResponse definitions w3c/wot-thing-description#1237.
-
Pointer (URI) to descriptions and titles w3c/wot-thing-description#1269.
-
Versioning in TMs w3c/wot-thing-description#1182.
-
Unclear assertion on TMs w3c/wot-thing-description#1173.
-
What is the exact structure of TM placeholder identifiers? w3c/wot-thing-description#1252.
-
tm:ref pattern should be more clear w3c/wot-thing-description#1152.
-
An explainer table for the operation values is missing w3c/wot-thing-description#1074.
-
Minor spelling and grammar errors w3c/wot-thing-description#1165.
-
Issues with Thing Model schema w3c/wot-thing-description#1186.
-
-
3 issues reopened.
-
Allow more operations in a top level form w3c/wot-thing-description#1070, by @benfrancis.
-
op does not have with default tag anymore w3c/wot-thing-description#1192, by @benfrancis.
-
Allowing `type` to be an array w3c/wot-thing-description#1247, by @egekorkan.
-
-
48 issues received 121 new comments.
-
New TD 1.1 namespace IRI w3c/wot-thing-description#1276 (11 comments by @benfrancis, @danielpeintner, @egekorkan, @jyhi, @relu91, @sebastiankb)
-
Definition of Backwards Compatibility w3c/wot-thing-description#1243 (11 comments by @benfrancis, @egekorkan, @relu91, @sebastiankb)
-
Red square around W3C Logo? w3c/wot-thing-description#1267 (8 comments by @ashimura, @benfrancis, @egekorkan, @JKRhb, @k-toumura, @relu91)
-
Content Type for Thing Model (IANA registration needed) w3c/wot-thing-description#931 (6 comments by @ektrah, @JKRhb, @sebastiankb)
-
PropertyAffordance intro misleading ? w3c/wot-thing-description#1229 (5 comments by @benfrancis, @danielpeintner, @egekorkan, @mlagally)
-
Specifying a @context in json-schema w3c/wot-thing-description#1233 (5 comments by @egekorkan, @ioggstream)
-
how to find the Form pair for an operation, e.g. the unsubscribe Form for a given subscribe Form w3c/wot-thing-description#968 (5 comments by @benfrancis, @danielpeintner, @egekorkan, @relu91)
-
Default Value Definitions should sort security schemes w3c/wot-thing-description#1295 (4 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
Make it clear that operation names are case sensitive w3c/wot-thing-description#1303 (4 comments by @benfrancis, @egekorkan)
-
Default value section misses op default for Thing w3c/wot-thing-description#1294 (4 comments by @benfrancis, @egekorkan)
-
Canonicalization - array vs. single value w3c/wot-thing-description#1296 (3 comments by @danielpeintner, @sebastiankb)
-
Good Practice for observe property flow w3c/wot-thing-description#1258 (3 comments by @benfrancis, @sebastiankb)
-
Room information w3c/wot-thing-description#1268 (3 comments by @Citrullin, @egekorkan, @sebastiankb)
-
[security] API key and PSK security schemes are not referenced or explained w3c/wot-thing-description#998 (2 comments by @egekorkan, @mmccool)
-
We need extension ontology to include implicit and password flows in OAuth2 w3c/wot-thing-description#949 (2 comments by @egekorkan, @mmccool)
-
We need an OAuth2 example for TD 1.1 w3c/wot-thing-description#948 (2 comments by @mmccool, @sebastiankb)
-
For OAuth2 device flow, should we define a "device authorization" element? w3c/wot-thing-description#953 (2 comments by @mmccool)
-
Canonicalization - Step 6 w.r.t. single value needed? w3c/wot-thing-description#1287 (2 comments by @mmccool)
-
internationalization extension of multilang strings w3c/wot-thing-description#1290 (2 comments by @benfrancis, @danielpeintner)
-
op does not have with default tag anymore w3c/wot-thing-description#1192 (2 comments by @benfrancis, @sebastiankb)
-
Comments - Call for Review of WoT Thing Description 1.1 specification and resolution to publish update w3c/wot-thing-description#1137 (2 comments by @sebastiankb)
-
Where to place the HTTP Default Binding and which format w3c/wot-thing-description#1274 (2 comments by @benfrancis, @relu91)
-
Pointer (URI) to descriptions and titles w3c/wot-thing-description#1269 (2 comments by @Citrullin, @sebastiankb)
-
What is the exact structure of TM placeholder identifiers? w3c/wot-thing-description#1252 (2 comments by @sebastiankb)
-
Allowing `type` to be an array w3c/wot-thing-description#1247 (2 comments by @egekorkan, @sebastiankb)
-
Consider removing section 9.3.1 Protocol Binding based on HTTP in version 1.1 w3c/wot-thing-description#1259 (2 comments by @benfrancis, @egekorkan)
-
Move "canonical TD" terminology to architecture w3c/wot-thing-description#1297 (1 comment by @sebastiankb)
-
Small incoherence in `forms` Thing Description core vocabulary w3c/wot-thing-description#1199 (1 comment by @sebastiankb)
-
Example 35 is incorrect or has inconsistency w3c/wot-thing-description#942 (1 comment by @sebastiankb)
-
UML diagrams contain lines with multiple properties w3c/wot-thing-description#1280 (1 comment by @sebastiankb)
-
Representation of examples (hidden information) w3c/wot-thing-description#1059 (1 comment by @danielpeintner)
-
unit for human-redable / display purposes or as semantic annotation? w3c/wot-thing-description#1202 (1 comment by @benfrancis)
-
Consider adding DataSchema to response and additionalResponses w3c/wot-thing-description#1053 (1 comment by @benfrancis)
-
New terms hardwareRevision and softwareRevision? w3c/wot-thing-description#947 (1 comment by @sebastiankb)
-
Evaluate geolocation terms in TD model (input from Profile TF) w3c/wot-thing-description#941 (1 comment by @sebastiankb)
-
-
24 pull requests opened.
-
refactor: clarify that property can be retrieved and/or updated w3c/wot-thing-description#1306, by @danielpeintner.
-
Fix links reported by LinkChecker w3c/wot-thing-description#1305, by @danielpeintner.
-
Remove TD Canonicalization w3c/wot-thing-description#1304, by @mmccool.
-
update Section 8.3 w3c/wot-thing-description#1301, by @sebastiankb.
-
fix default table entry for observable w3c/wot-thing-description#1292, by @sebastiankb.
-
default value fix for observe + SPARQL fix for renderer w3c/wot-thing-description#1291, by @sebastiankb.
-
Add 'instantiation' property to security scheme w3c/wot-thing-description#1289, by @vcharpenay.
-
Add 'instantiation' property in TD ontology for propper roundtripping w3c/wot-thing-description#1288, by @vcharpenay.
-
add a note about observe behavior w3c/wot-thing-description#1284, by @sebastiankb.
-
update webhooks example w3c/wot-thing-description#1283, by @sebastiankb.
-
Add changelog w3c/wot-thing-description#1282, by @egekorkan.
-
DO NOT MERGE. Detecting new features w3c/wot-thing-description#1281, by @egekorkan.
-
print *all* code parts on print w3c/wot-thing-description#1279, by @danielpeintner.
-
add security aspect in intro + small type fix w3c/wot-thing-description#1278, by @sebastiankb.
-
add additional sample terms in sample sections 7.1.1 w3c/wot-thing-description#1277, by @sebastiankb.
-
fix titles and descriptions type problem + default value entries for security in w3c/wot-thing-description#1275, by @sebastiankb.
-
Update TM and tm generation script w3c/wot-thing-description#1272, by @relu91.
-
fix iri to iri-reference and add further instructions w3c/wot-thing-description#1271, by @egekorkan.
-
add tm:submodel entry in relation typ table w3c/wot-thing-description#1270, by @sebastiankb.
-
Fix 948 (add OAuth2 flow examples) w3c/wot-thing-description#1264, by @relu91.
-
additional text about TM versioning w3c/wot-thing-description#1263, by @sebastiankb.
-
fix default value link for op w3c/wot-thing-description#1262, by @sebastiankb.
-
Additional recommendation about the unit usage w3c/wot-thing-description#1261, by @sebastiankb.
-
update definition for forms w3c/wot-thing-description#1260, by @sebastiankb.
-
-
20 pull requests merged.
-
Add 'instantiation' property to security scheme w3c/wot-thing-description#1289.
-
fix default table entry for observable w3c/wot-thing-description#1292.
-
add a note about observe behavior w3c/wot-thing-description#1284.
-
print *all* code parts on print w3c/wot-thing-description#1279.
-
add security aspect in intro + small type fix w3c/wot-thing-description#1278.
-
add additional sample terms in sample sections 7.1.1 w3c/wot-thing-description#1277.
-
fix titles and descriptions type problem + default value entries for security in w3c/wot-thing-description#1275.
-
Update TM and tm generation script w3c/wot-thing-description#1272.
-
fix iri to iri-reference and add further instructions w3c/wot-thing-description#1271.
-
add tm:submodel entry in relation typ table w3c/wot-thing-description#1270.
-
additional text about TM versioning w3c/wot-thing-description#1263.
-
Fix JSON Schema issues w3c/wot-thing-description#1250.
-
fix default value link for op w3c/wot-thing-description#1262.
-
Additional recommendation about the unit usage w3c/wot-thing-description#1261.
-
update definition for forms w3c/wot-thing-description#1260.
-
Update impl.csv for 2021.10 Plugfest results w3c/wot-thing-description#1239.
-
fixes #1247 to allow type to be an array w3c/wot-thing-description#1254.
-
Add op values description table w3c/wot-thing-description#1257.
-
Updates for TM Chapter w3c/wot-thing-description#1207.
-
Fix issues in TM schema generation script w3c/wot-thing-description#1205.
-
-
5 pull requests closed.
-
DO NOT MERGE. Detecting new features w3c/wot-thing-description#1281.
-
WIP: swap securtiy and securityDefinition in context file w3c/wot-thing-description#937.
-
fix: fix RDF triples example from Thing description json-ld 1.1 w3c/wot-thing-description#1167.
-
default value fix for observe + SPARQL fix for renderer w3c/wot-thing-description#1291.
-
Add 'instantiation' property in TD ontology for propper roundtripping w3c/wot-thing-description#1288.
-
-
28 pull requests received 84 new comments.
-
Fix 948 (add OAuth2 flow examples) w3c/wot-thing-description#1264 (13 comments by @egekorkan, @mmccool, @relu91, @sebastiankb)
-
Add 'instantiation' property to security scheme w3c/wot-thing-description#1289 (7 comments by @ethieblin, @sebastiankb, @vcharpenay)
-
add a note about observe behavior w3c/wot-thing-description#1284 (6 comments by @danielpeintner, @sebastiankb)
-
Fix JSON Schema issues w3c/wot-thing-description#1250 (6 comments by @egekorkan, @relu91, @sebastiankb)
-
print *all* code parts on print w3c/wot-thing-description#1279 (5 comments by @danielpeintner, @sebastiankb)
-
add security aspect in intro + small type fix w3c/wot-thing-description#1278 (5 comments by @egekorkan, @sebastiankb)
-
fixes #1247 to allow type to be an array w3c/wot-thing-description#1254 (4 comments by @egekorkan, @sebastiankb)
-
fix default table entry for observable w3c/wot-thing-description#1292 (3 comments by @danielpeintner, @sebastiankb)
-
fix: fix RDF triples example from Thing description json-ld 1.1 w3c/wot-thing-description#1167 (3 comments by @sebastiankb, @vcharpenay)
-
add tm:submodel entry in relation typ table w3c/wot-thing-description#1270 (3 comments by @JKRhb, @sebastiankb)
-
additional text about TM versioning w3c/wot-thing-description#1263 (3 comments by @egekorkan, @sebastiankb)
-
add additional sample terms in sample sections 7.1.1 w3c/wot-thing-description#1277 (2 comments by @sebastiankb)
-
fix titles and descriptions type problem + default value entries for security in w3c/wot-thing-description#1275 (2 comments by @sebastiankb)
-
refactor: clarify that property can be retrieved and/or updated w3c/wot-thing-description#1306 (1 comment by @danielpeintner)
-
WIP: swap securtiy and securityDefinition in context file w3c/wot-thing-description#937 (1 comment by @sebastiankb)
-
fix iri to iri-reference and add further instructions w3c/wot-thing-description#1271 (1 comment by @sebastiankb)
-
Additional recommendation about the unit usage w3c/wot-thing-description#1261 (1 comment by @sebastiankb)
-
Update impl.csv for 2021.10 Plugfest results w3c/wot-thing-description#1239 (1 comment by @sebastiankb)
-
Fix issues in TM schema generation script w3c/wot-thing-description#1205 (1 comment by @sebastiankb)
-
w3c/wot-discovery
-
6 issues opened.
-
Move common terminology to the Architecture spec w3c/wot-discovery#240, by @mlagally.
-
Move USECASES to usecases document, add link to the spec w3c/wot-discovery#239, by @mlagally.
-
Make XPath optional/informative w3c/wot-discovery#238, by @mmccool.
-
JSONPath as a search query language w3c/wot-discovery#234, by @farshidtz.
-
Questionable W3C Link Checker Errors w3c/wot-discovery#233, by @egekorkan.
-
Bare minimal Query language for TDDs w3c/wot-discovery#232, by @relu91.
-
-
4 issues closed.
-
Reach out to JSONPath community w3c/wot-discovery#56.
-
Create Basic Query entry point w3c/wot-discovery#231.
-
Bare minimal Query language for TDDs w3c/wot-discovery#232.
-
Don't try to describe the Directory Service API in a Thing Description w3c/wot-discovery#172.
-
-
11 issues received 40 new comments.
-
Resolve TD/Thing ID Semantics (was Reconsider @type ThingID) w3c/wot-discovery#190 (12 comments by @benfrancis, @egekorkan, @farshidtz, @mmccool, @vcharpenay)
-
Create Basic Query entry point w3c/wot-discovery#231 (8 comments by @benfrancis, @farshidtz, @mmccool, @relu91)
-
Improving event type values in the Notification API w3c/wot-discovery#197 (3 comments by @benfrancis, @farshidtz)
-
Don't try to describe the Directory Service API in a Thing Description w3c/wot-discovery#172 (1 comment by @benfrancis)
-
-
5 pull requests opened.
-
Add placeholder section for thing model w3c/wot-discovery#242, by @farshidtz.
-
Delete common terms in terminology section w3c/wot-discovery#241, by @k-toumura.
-
Changes to make jsonpath informative w3c/wot-discovery#237, by @farshidtz.
-
Changes to make jsonpath informative (obsolete) w3c/wot-discovery#236, by @farshidtz.
-
WIP: Make JSONPath optional w3c/wot-discovery#235, by @mmccool.
-
-
2 pull requests merged.
-
Add placeholder section for thing model w3c/wot-discovery#242.
-
Changes to make jsonpath informative w3c/wot-discovery#237.
-
-
2 pull requests closed.
-
WIP: Make JSONPath optional w3c/wot-discovery#235.
-
Changes to make jsonpath informative (obsolete) w3c/wot-discovery#236.
-
-
3 pull requests received 5 new comments.
-
Delete common terms in terminology section w3c/wot-discovery#241 (3 comments by @k-toumura, @mmccool)
-
w3c/wot-architecture
-
20 issues opened.
-
Finding a place to put the security paragraph in the bindings chapter w3c/wot-architecture#643, by @egekorkan.
-
Identify normative RFC2119 assertions that affect the TD specification w3c/wot-architecture#642, by @mlagally.
-
`arch-methods` : Eligible protocols for W3C WoT MUST be based on a standard set of methods that are known a prior. w3c/wot-architecture#640, by @mlagally.
-
`arch-op-wellknown-compare` : Well-known operation types MUST be compared using a case-insensitive comparison. w3c/wot-architecture#637, by @mlagally.
-
`arch-consumer-configuration` : The configuration of the Consumer behavior MAY be exposed through the Thing. w3c/wot-architecture#636, by @mlagally.
-
`arch-thing-bundling` : Things MAY be bundled together with a Consumer to enable Thing-to-Thing interaction. w3c/wot-architecture#634, by @mlagally.
-
`arch-property-readable` : The state exposed by a Property MUST be retrievable (readable). w3c/wot-architecture#633, by @mlagally.
-
Why are Chapter 8 and 9 separated w3c/wot-architecture#630, by @egekorkan.
-
Splitting the architecture document w3c/wot-architecture#629, by @egekorkan.
-
Introduction does not mention section 6 w3c/wot-architecture#628, by @egekorkan.
-
Chapter 10 uses non RFC assertions w3c/wot-architecture#627, by @egekorkan.
-
Explaining of WoT operations w3c/wot-architecture#626, by @egekorkan.
-
Assertion review w3c/wot-architecture#625, by @egekorkan.
-
Move list of operations to the Thing Description specification w3c/wot-architecture#623, by @benfrancis.
-
Too many branches w3c/wot-architecture#622, by @egekorkan.
-
-
2 issues closed.
-
Too many branches w3c/wot-architecture#622.
-
Move list of operations to the Thing Description specification w3c/wot-architecture#623.
-
-
25 issues received 82 new comments.
-
Identify normative RFC2119 assertions that affect the TD specification w3c/wot-architecture#642 (8 comments by @benfrancis, @egekorkan, @mlagally, @sebastiankb)
-
Assertion review w3c/wot-architecture#625 (6 comments by @benfrancis, @egekorkan, @mlagally, @sebastiankb)
-
`arch-op-wellknown-compare` : Well-known operation types MUST be compared using a case-insensitive comparison. w3c/wot-architecture#637 (5 comments by @benfrancis, @mlagally, @sebastiankb)
-
`arch-td-consumers-process` : Consumers MUST be able to parse and process the TD representation format, which is based on JSON [[!RFC8259]]. w3c/wot-architecture#632 (4 comments by @benfrancis, @mlagally, @sebastiankb)
-
`arch-consumer-configuration` : The configuration of the Consumer behavior MAY be exposed through the Thing. w3c/wot-architecture#636 (4 comments by @benfrancis, @k-toumura, @mlagally, @sebastiankb)
-
Why are Chapter 8 and 9 separated w3c/wot-architecture#630 (4 comments by @danielpeintner, @egekorkan, @mlagally, @relu91)
-
`arch-property-readable` : The state exposed by a Property MUST be retrievable (readable). w3c/wot-architecture#633 (3 comments by @benfrancis, @mlagally, @sebastiankb)
-
`arch-thing-bundling` : Things MAY be bundled together with a Consumer to enable Thing-to-Thing interaction. w3c/wot-architecture#634 (2 comments by @benfrancis, @mlagally)
-
`arch-methods` : Eligible protocols for W3C WoT MUST be based on a standard set of methods that are known a prior. w3c/wot-architecture#640 (2 comments by @benfrancis, @mlagally)
-
`arch-op-extension` : The set of predefined operation types MAY be augmented by Extension operation types chosen by applications. w3c/wot-architecture#638 (2 comments by @benfrancis, @sebastiankb)
-
Move terminology section from discovery to architecture spec w3c/wot-architecture#613 (2 comments by @k-toumura, @mlagally)
-
Property affordances claimed to always readable w3c/wot-architecture#412 (2 comments by @egekorkan, @mlagally)
-
Relationship between "8.7 Protocol Bindings" and "9.5 WoT Binding Templates" w3c/wot-architecture#608 (2 comments by @egekorkan, @mlagally)
-
Move list of operations to the Thing Description specification w3c/wot-architecture#623 (2 comments by @benfrancis, @egekorkan)
-
Finding a place to put the security paragraph in the bindings chapter w3c/wot-architecture#643 (1 comment by @egekorkan)
-
Review Chapter 6.7 in relation to Binding Templates 4.1 w3c/wot-architecture#617 (1 comment by @egekorkan)
-
-
4 pull requests opened.
-
improve description of device categories w3c/wot-architecture#645, by @mlagally.
-
Move common terms from Discovery to Architecture w3c/wot-architecture#644, by @k-toumura.
-
precedence rule for terminology w3c/wot-architecture#631, by @mlagally.
-
preparing implementation report w3c/wot-architecture#624, by @mlagally.
-
-
2 pull requests merged.
-
preparing implementation report w3c/wot-architecture#624.
-
precedence rule for terminology w3c/wot-architecture#631.
-
-
3 pull requests received 48 new comments.
-
Address Binding Templates related issues w3c/wot-architecture#615 (42 comments by @egekorkan, @mlagally)
-
preparing implementation report w3c/wot-architecture#624 (4 comments by @egekorkan, @k-toumura, @mlagally)
-
Move common terms from Discovery to Architecture w3c/wot-architecture#644 (2 comments by @farshidtz, @k-toumura)
-
w3c/wot-scripting-api
-
5 issues opened.
-
Rename Use Cases section ? w3c/wot-scripting-api#355, by @danielpeintner.
-
Conformance section necessity w3c/wot-scripting-api#354, by @danielpeintner.
-
Next charter topics w3c/wot-scripting-api#352, by @danielpeintner.
-
Finding correct unsubscribe form w3c/wot-scripting-api#351, by @danielpeintner.
-
LinkChecker Errors w3c/wot-scripting-api#348, by @egekorkan.
-
-
2 issues closed.
-
Description for labels w3c/wot-scripting-api#336.
-
LinkChecker Errors w3c/wot-scripting-api#348.
-
-
10 issues received 20 new comments.
-
Clarify multiple requests for subscription/observation w3c/wot-scripting-api#346 (4 comments by @danielpeintner, @relu91, @zolkis)
-
Reference terminology section of the architecture specification w3c/wot-scripting-api#342 (1 comment by @danielpeintner)
-
w3c/wot-scripting-api#349 (1 comment by @danielpeintner)
-
w3c/wot-scripting-api#347 (1 comment by @danielpeintner)
-
2 pull requests opened.
-
refactor: move section "Terminology and conventions" right after "Conformance" w3c/wot-scripting-api#353, by @danielpeintner.
-
LinkChecker Errors w3c/wot-scripting-api#350, by @danielpeintner.
-
-
1 pull request merged.
-
LinkChecker Errors w3c/wot-scripting-api#350.
-
-
2 pull requests received 6 new comments.
-
refactor: move section "Terminology and conventions" right after "Conformance" w3c/wot-scripting-api#353 (5 comments by @danielpeintner, @zolkis)
-
w3c/wot-security-best-practices
-
3 issues opened.
-
Scripting API Issues Related to Security w3c/wot-security-best-practices#29, by @mmccool.
-
Add Onboarding/Key Distribution Section w3c/wot-security-best-practices#27, by @mmccool.
-
Separate security recommendations for Exposed and Consumed Things w3c/wot-security-best-practices#26, by @mmccool.
-
-
4 issues received 7 new comments.
-
Separate security recommendations for Exposed and Consumed Things w3c/wot-security-best-practices#26 (1 comment by @zolkis)
-
TD Signatures, Key Management, and Object Security w3c/wot-security-best-practices#14 (1 comment by @mmccool)
-
1 pull request opened.
-
Local transport and secure onboarding w3c/wot-security-best-practices#28, by @mmccool.
-
-
1 pull request received 3 new comments.
w3c/wot-binding-templates
-
3 issues opened.
-
MQTT and Modbus does not meet the architecture eligible criteria for a protocol binding w3c/wot-binding-templates#137, by @relu91.
-
Link Checker 404 for Architecture Terminology w3c/wot-binding-templates#136, by @egekorkan.
-
Consider removing section 2.2 HTTP Default Vocabulary Terms w3c/wot-binding-templates#135, by @benfrancis.
-
-
3 issues closed.
-
Link Checker 404 for Architecture Terminology w3c/wot-binding-templates#136.
-
Fix examples links w3c/wot-binding-templates#117.
-
Use `address` instead of `offeset` w3c/wot-binding-templates#115.
-
-
1 issue reopened.
-
Modbus Prefix w3c/wot-binding-templates#119, by @egekorkan.
-
-
2 issues received 23 new comments.
-
MQTT and Modbus does not meet the architecture eligible criteria for a protocol binding w3c/wot-binding-templates#137 (20 comments by @benfrancis, @egekorkan, @jyhi, @relu91, @sebastiankb)
-
Consider removing section 2.2 HTTP Default Vocabulary Terms w3c/wot-binding-templates#135 (3 comments by @benfrancis, @egekorkan, @mlagally)
-
-
1 pull request opened.
-
Fix broken links w3c/wot-binding-templates#138, by @egekorkan.
-
-
3 pull requests merged.
-
Fix broken links w3c/wot-binding-templates#138.
-
Create orphaned sections w3c/wot-binding-templates#131.
-
General improvements to the modbus ontology and spec files w3c/wot-binding-templates#129.
-
-
1 pull request received 1 new comment.
-
General improvements to the modbus ontology and spec files w3c/wot-binding-templates#129 (1 comment by @egekorkan)
-
w3c/wotwg
-
1 issue opened.
-
Closing this repo w3c/wotwg#10, by @egekorkan.
-
Past meetings
Participants
-
1 participant joined.
-
Farshid Tavakolizadeh (W3C Invited Experts) joined.
-
-
1 participant left.
-
Farshid Tavakolizadeh (W3C Invited Experts) left.
-
GitHub
w3c/wot-thing-description
-
16 issues opened.
-
Good Practice for observe property flow w3c/wot-thing-description#1258, by @danielpeintner.
-
Numbering tables w3c/wot-thing-description#1256, by @egekorkan.
-
Cleanup of the repository w3c/wot-thing-description#1255, by @egekorkan.
-
Specify relation/constraint between interactions with math w3c/wot-thing-description#1253, by @miguelrk.
-
What is the exact structure of TM placeholder identifiers? w3c/wot-thing-description#1252, by @egekorkan.
-
Indicating the relevant part of a payload w3c/wot-thing-description#1251, by @egekorkan.
-
Refer to external data schemas w3c/wot-thing-description#1249, by @relu91.
-
Reduce intrinsic protocol level redundancy w3c/wot-thing-description#1248, by @relu91.
-
Allowing `type` to be an array w3c/wot-thing-description#1247, by @egekorkan.
-
Constraining values of `contentType` w3c/wot-thing-description#1246, by @egekorkan.
-
Annotating TDs with test results w3c/wot-thing-description#1244, by @egekorkan.
-
Definition of Backwards Compatibility w3c/wot-thing-description#1243, by @egekorkan.
-
Linking to top level initial connections w3c/wot-thing-description#1242, by @egekorkan.
-
json-schema vocabulary: which version? w3c/wot-thing-description#1241, by @ioggstream.
-
JSON schema misses ExpectedResponse definitions w3c/wot-thing-description#1237, by @danielpeintner.
-
@type everywhere w3c/wot-thing-description#1236, by @sebastiankb.
-
-
2 issues closed.
-
Missing default value for observable w3c/wot-thing-description#908.
-
JSON Schema for Thing Model w3c/wot-thing-description#972.
-
-
40 issues received 65 new comments.
-
Definition of Backwards Compatibility w3c/wot-thing-description#1243 (11 comments by @benfrancis, @danielpeintner, @egekorkan, @relu91)
-
Indicating the relevant part of a payload w3c/wot-thing-description#1251 (4 comments by @k-toumura, @miguelrk, @mjkoster, @relu91)
-
Specify relation/constraint between interactions with math w3c/wot-thing-description#1253 (3 comments by @egekorkan, @miguelrk, @relu91)
-
Optional simple-type parameters w3c/wot-thing-description#1234 (3 comments by @danielpeintner, @egekorkan)
-
Representation of examples (hidden information) w3c/wot-thing-description#1059 (2 comments by @danielpeintner, @egekorkan)
-
Content Type for Thing Model (IANA registration needed) w3c/wot-thing-description#931 (1 comment by @egekorkan)
-
New terms hardwareRevision and softwareRevision? w3c/wot-thing-description#947 (1 comment by @egekorkan)
-
How to model multiple InteractionAffordances of the same nature w3c/wot-thing-description#963 (1 comment by @egekorkan)
-
[multiLang] Should titles and descriptions be present in the TD after language negotation w3c/wot-thing-description#959 (1 comment by @egekorkan)
-
Introducing assumptions about TD instances that have no IP addresses w3c/wot-thing-description#977 (1 comment by @egekorkan)
-
[ThingModel] Example of Eclipse Vorto model w3c/wot-thing-description#1000 (1 comment by @egekorkan)
-
Consider defining additional vocabulary supporting Discovery w3c/wot-thing-description#1033 (1 comment by @egekorkan)
-
alignment.ttl file should add the semantics of the external classes reused, at least the "type" w3c/wot-thing-description#1014 (1 comment by @egekorkan)
-
Modeling relations among InteractionAffordances w3c/wot-thing-description#1071 (1 comment by @egekorkan)
-
Comments - Call for Review of WoT Thing Description 1.1 specification and resolution to publish update w3c/wot-thing-description#1137 (1 comment by @egekorkan)
-
[validation] Changing `oneOf` to `anyOf` for the validation of security scheme w3c/wot-thing-description#1055 (1 comment by @egekorkan)
-
unit for human-redable / display purposes or as semantic annotation? w3c/wot-thing-description#1202 (1 comment by @sebastiankb)
-
JSON schema misses ExpectedResponse definitions w3c/wot-thing-description#1237 (1 comment by @danielpeintner)
-
-
7 pull requests opened.
-
Add op values description table w3c/wot-thing-description#1257, by @egekorkan.
-
fixes #1247 to allow type to be an array w3c/wot-thing-description#1254, by @egekorkan.
-
Fix JSON Schema issues w3c/wot-thing-description#1250, by @relu91.
-
Oct 2021 Testfest Implementation Report Update w3c/wot-thing-description#1245, by @mmccool.
-
Add TUM implementations w3c/wot-thing-description#1240, by @egekorkan.
-
Update impl.csv for 2021.10 Plugfest results w3c/wot-thing-description#1239, by @mmccool.
-
Remove duplicate line "enum" w3c/wot-thing-description#1238, by @ioggstream.
-
-
3 pull requests merged.
-
Oct 2021 Testfest Implementation Report Update w3c/wot-thing-description#1245.
-
Remove duplicate line "enum" w3c/wot-thing-description#1238.
-
Add TUM implementations w3c/wot-thing-description#1240.
-
-
6 pull requests received 25 new comments.
-
Updates for TM Chapter w3c/wot-thing-description#1207 (10 comments by @egekorkan, @sebastiankb, @thjaeckle)
-
Fix issues in TM schema generation script w3c/wot-thing-description#1205 (9 comments by @egekorkan, @JKRhb)
-
Oct 2021 Testfest Implementation Report Update w3c/wot-thing-description#1245 (2 comments by @mmccool)
-
w3c/wot-profile
-
2 issues opened.
-
Eventing Mechanisms of Smart Home Solutions w3c/wot-profile#108, by @egekorkan.
-
Events - Scalable event mechanism for cloud use cases w3c/wot-profile#107, by @mlagally.
-
w3c/wot-architecture
-
5 issues opened.
-
Group wide review w3c/wot-architecture#621, by @mlagally.
-
internationalisation requirements w3c/wot-architecture#620, by @mlagally.
-
operations are claimed to be extendable w3c/wot-architecture#619, by @egekorkan.
-
Review Chapter 6.7 in relation to Binding Templates 4.1 w3c/wot-architecture#617, by @egekorkan.
-
Add a reference to the Use Case document w3c/wot-architecture#616, by @mlagally.
-
-
1 issue closed.
-
Respec errors in rendered Architecture version w3c/wot-architecture#609.
-
-
4 issues received 8 new comments.
-
operations are claimed to be extendable w3c/wot-architecture#619 (3 comments by @egekorkan, @mlagally)
-
2 pull requests opened.
-
fixing respec errors - closes #609 w3c/wot-architecture#618, by @mlagally.
-
Address Binding Templates related issues w3c/wot-architecture#615, by @egekorkan.
-
-
1 pull request merged.
-
fixing respec errors - closes #609 w3c/wot-architecture#618.
-
-
2 pull requests received 16 new comments.
-
Address Binding Templates related issues w3c/wot-architecture#615 (15 comments by @egekorkan, @mlagally)
-
w3c/wot-binding-templates
-
2 issues opened.
-
Introduce security in protocols w3c/wot-binding-templates#134, by @egekorkan.
-
User Agent Adjustable Payload Examples per Protocol Binding w3c/wot-binding-templates#132, by @egekorkan.
-
-
1 issue reopened.
-
Use `address` instead of `offeset` w3c/wot-binding-templates#115, by @relu91.
-
-
1 issue received 1 new comment.
-
3 pull requests opened.
-
WIP - Proposal for OPCUA Binding w3c/wot-binding-templates#133, by @erossignon.
-
Create orphaned sections w3c/wot-binding-templates#131, by @egekorkan.
-
Full Review PR for others w3c/wot-binding-templates#130, by @egekorkan.
-
-
2 pull requests received 4 new comments.
-
General improvements to the modbus ontology and spec files w3c/wot-binding-templates#129 (3 comments by @danielpeintner, @egekorkan)
-
w3c/wot-discovery
-
4 issues opened.
-
Create Basic Query entry point w3c/wot-discovery#231, by @mmccool.
-
TD Probing upon registration w3c/wot-discovery#229, by @egekorkan.
-
Unclear assertion on validation w3c/wot-discovery#228, by @egekorkan.
-
Automate assertion extraction w3c/wot-discovery#227, by @mmccool.
-
-
2 issues closed.
-
Unclear assertion on validation w3c/wot-discovery#228.
-
TDD TD: Don't Actions need an input field w3c/wot-discovery#182.
-
-
12 issues received 28 new comments.
-
Read-Only Directories w3c/wot-discovery#208 (7 comments by @benfrancis, @danielpeintner, @farshidtz, @k-toumura, @mmccool, @relu91)
-
TDDs need to deal with missing @type w3c/wot-discovery#224 (4 comments by @AndreaCimminoArriaga, @mmccool)
-
Resolve TD/Thing ID Semantics (was Reconsider @type ThingID) w3c/wot-discovery#190 (3 comments by @AndreaCimminoArriaga, @mmccool)
-
Don't try to describe the Directory Service API in a Thing Description w3c/wot-discovery#172 (1 comment by @mmccool)
-
-
3 pull requests opened.
-
Clarify validation statements w3c/wot-discovery#230, by @farshidtz.
-
Add assertion list and extract script w3c/wot-discovery#226, by @k-toumura.
-
Add list of directory implementations w3c/wot-discovery#225, by @farshidtz.
-
-
4 pull requests merged.
-
Clarify validation statements w3c/wot-discovery#230.
-
Add assertion list and extract script w3c/wot-discovery#226.
-
Add list of directory implementations w3c/wot-discovery#225.
-
Add object types to actions w3c/wot-discovery#223.
-
-
2 pull requests received 7 new comments.
-
Add list of directory implementations w3c/wot-discovery#225 (5 comments by @AndreaCimminoArriaga, @farshidtz, @wiresio)
-
w3c/wot-scripting-api
-
2 issues opened.
-
Clarify multiple requests for subscription/observation w3c/wot-scripting-api#346, by @relu91.
-
`subscribeEvent` and `observerProperty` misaligned signature w3c/wot-scripting-api#343, by @relu91.
-
-
1 issue reopened.
-
`subscribeEvent` and `observerProperty` misaligned signature w3c/wot-scripting-api#343, by @relu91.
-
-
2 issues received 3 new comments.
-
Clarify multiple requests for subscription/observation w3c/wot-scripting-api#346 (2 comments by @danielpeintner, @zolkis)
-
`subscribeEvent` and `observerProperty` misaligned signature w3c/wot-scripting-api#343 (1 comment by @relu91)
-
-
2 pull requests opened.
-
chore: update TS definitions on NPM to 0.8.0-SNAPSHOT.20 w3c/wot-scripting-api#345, by @relu91.
-
fix(typescript): align subscribeEvent and observeProperty methods w3c/wot-scripting-api#344, by @relu91.
-
-
2 pull requests merged.
-
chore: update TS definitions on NPM to 0.8.0-SNAPSHOT.20 w3c/wot-scripting-api#345.
-
fix(typescript): align subscribeEvent and observeProperty methods w3c/wot-scripting-api#344.
-
w3c/wot-ejs
-
2 issues opened.
-
Add Use Cases w3c/wot-ejs#9, by @mmccool.
-
1 issue received 2 new comments.
Participants
-
3 participants joined.
-
Jiye Park (Siemens AG) joined.
-
Klaus Hartke (Siemens AG) joined.
-
Jan Romann (W3C Invited Experts) joined.
-
-
1 participant left.
-
Klaus Hartke (Siemens AG) left.
-
GitHub
w3c/wot-thing-description
-
14 issues opened.
-
JSON Schema issue / request w3c/wot-thing-description#1235, by @danielpeintner.
-
Optional simple-type parameters w3c/wot-thing-description#1234, by @danielpeintner.
-
Specifying a @context in json-schema w3c/wot-thing-description#1233, by @ioggstream.
-
Payload format for meta operations w3c/wot-thing-description#1231, by @egekorkan.
-
PropertyAffordance intro misleading ? w3c/wot-thing-description#1229, by @danielpeintner.
-
editorial: left over of a merge comment in canonicalization section w3c/wot-thing-description#1225, by @mlagally.
-
Self reference and unsolicited operation for events and properties w3c/wot-thing-description#1224, by @tuve.
-
Yet another Action Model w3c/wot-thing-description#1223, by @relu91.
-
IANA Registration for Thing Model definition w3c/wot-thing-description#1221, by @sebastiankb.
-
Specify sub-byte semantics w3c/wot-thing-description#1220, by @relu91.
-
Error in JSON Schema example (ontology doc) w3c/wot-thing-description#1219, by @vcharpenay.
-
Queston about https://www.w3.org/2019/wot/td#securityDefinitions w3c/wot-thing-description#1218, by @cecemel.
-
Payload pattern binding w3c/wot-thing-description#1217, by @sebastiankb.
-
URLs and IDs should not have embedded metadata w3c/wot-thing-description#1216, by @mmccool.
-
-
2 issues closed.
-
editorial: left over of a merge comment in canonicalization section w3c/wot-thing-description#1225.
-
How do you cancel or query the state of an action request? w3c/wot-thing-description#302.
-
-
21 issues received 59 new comments.
-
Describing initial connection w3c/wot-thing-description#878 (7 comments by @benfrancis, @egekorkan, @sebastiankb)
-
Is there a need for `invokeanyaction`/`queryallactions` operations? w3c/wot-thing-description#1200 (5 comments by @benfrancis, @egekorkan)
-
How do you cancel or query the state of an action request? w3c/wot-thing-description#302 (5 comments by @benfrancis, @sebastiankb)
-
Payload format for meta operations w3c/wot-thing-description#1231 (4 comments by @benfrancis, @egekorkan)
-
Yet another Action Model w3c/wot-thing-description#1223 (4 comments by @benfrancis, @danielpeintner, @egekorkan)
-
Payload pattern binding w3c/wot-thing-description#1217 (4 comments by @Citrullin, @egekorkan, @sebastiankb)
-
Self reference and unsolicited operation for events and properties w3c/wot-thing-description#1224 (3 comments by @egekorkan, @tuve)
-
TD File Extension Convention w3c/wot-thing-description#1214 (3 comments by @egekorkan, @sebastiankb)
-
PropertyAffordance intro misleading ? w3c/wot-thing-description#1229 (2 comments by @danielpeintner, @egekorkan)
-
Allow "security" to include both SecurityScheme objects and declared identifiers w3c/wot-thing-description#300 (2 comments by @egekorkan, @mmccool)
-
Thing Description Framing for RDF/JSON-LD round-tripping w3c/wot-thing-description#1981 (2 comments by @mmccool)
-
Queston about https://www.w3.org/2019/wot/td#securityDefinitions w3c/wot-thing-description#1218 (1 comment by @egekorkan)
-
editorial: left over of a merge comment in canonicalization section w3c/wot-thing-description#1225 (1 comment by @sebastiankb)
-
Error in JSON Schema example (ontology doc) w3c/wot-thing-description#1219 (1 comment by @danielpeintner)
-
unit for human-redable / display purposes or as semantic annotation? w3c/wot-thing-description#1202 (1 comment by @sebastiankb)
-
Small incoherence in `forms` Thing Description core vocabulary w3c/wot-thing-description#1199 (1 comment by @sebastiankb)
-
6 pull requests opened.
-
Add `queryallactions` operation w3c/wot-thing-description#1232, by @benfrancis.
-
[editorial] fix wrong or missing use of code brackets w3c/wot-thing-description#1230, by @egekorkan.
-
add new action model proposal in other formats w3c/wot-thing-description#1228, by @relu91.
-
Remove left over merge conflict seperators w3c/wot-thing-description#1227, by @JKRhb.
-
Add queryactioninstance and cancelactioninstance operations - closes #302 w3c/wot-thing-description#1226, by @benfrancis.
-
Add a new action model proposal w3c/wot-thing-description#1222, by @relu91.
-
-
7 pull requests merged.
-
[editorial] fix wrong or missing use of code brackets w3c/wot-thing-description#1230.
-
Add `queryallactions` operation w3c/wot-thing-description#1232.
-
Remove left over merge conflict seperators w3c/wot-thing-description#1227.
-
Add queryaction and cancelaction operations - closes #302 w3c/wot-thing-description#1208.
-
add new action model proposal in other formats w3c/wot-thing-description#1228.
-
Add a new action model proposal w3c/wot-thing-description#1222.
-
fix: maxItems,minItems are xsd:nonNegativeInteger w3c/wot-thing-description#1212.
-
-
2 pull requests closed.
-
Add queryactioninstance and cancelactioninstance operations - closes #302 w3c/wot-thing-description#1226.
-
WIP: TD Signatures w3c/wot-thing-description#1151.
-
-
11 pull requests received 29 new comments.
-
fix: maxItems,minItems are xsd:nonNegativeInteger w3c/wot-thing-description#1212 (6 comments by @danielpeintner, @sebastiankb, @w3cbot)
-
[editorial] fix wrong or missing use of code brackets w3c/wot-thing-description#1230 (4 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
Remove left over merge conflict seperators w3c/wot-thing-description#1227 (1 comment by @sebastiankb)
-
Add queryactioninstance and cancelactioninstance operations - closes #302 w3c/wot-thing-description#1226 (1 comment by @benfrancis)
-
Add queryaction and cancelaction operations - closes #302 w3c/wot-thing-description#1208 (1 comment by @sebastiankb)
w3c/wot-scripting-api
-
5 issues opened.
-
Reference terminology section of the architecture specification w3c/wot-scripting-api#342, by @mlagally.
-
Sync json schema task is failing w3c/wot-scripting-api#338, by @danielpeintner.
-
Use-case for selecting the preferred binding for a given interaction or all interactions w3c/wot-scripting-api#337, by @danielpeintner.
-
Description for labels w3c/wot-scripting-api#336, by @danielpeintner.
-
New op values (cancelaction, queryaction,and queryallactions) w3c/wot-scripting-api#335, by @danielpeintner.
-
-
2 issues closed.
-
Sync json schema task is failing w3c/wot-scripting-api#338.
-
NotFoundError is not used w3c/wot-scripting-api#334.
-
-
9 issues received 11 new comments.
-
Publish Thing Description schema and Types in another npm package w3c/wot-scripting-api#327 (3 comments by @benfrancis, @relu91, @zolkis)
-
w3c/wot-scripting-api#341 (1 comment by @danielpeintner)
-
Discussion about read- write-/multipleproperties w3c/wot-scripting-api#219 (1 comment by @danielpeintner)
-
Provide a convenient way to fetch a TD in simple case w3c/wot-scripting-api#216 (1 comment by @danielpeintner)
-
-
2 pull requests opened.
-
chore: ci bump node version w3c/wot-scripting-api#340, by @relu91.
-
Add NotFoundError for consumer algorithms w3c/wot-scripting-api#339, by @relu91.
-
-
3 pull requests merged.
-
chore: ci bump node version w3c/wot-scripting-api#340.
-
Add NotFoundError for consumer algorithms w3c/wot-scripting-api#339.
-
Label Table w3c/wot-scripting-api#333.
-
-
3 pull requests received 3 new comments.
w3c/wot-discovery
-
1 issue opened.
-
TDDs need to deal with missing @type w3c/wot-discovery#224, by @mmccool.
-
-
2 issues closed.
-
Assertions removed by mistake for Introductions? w3c/wot-discovery#193.
-
Implementing a DNS-based approach, are DNS-SD and mDNS mandatory? w3c/wot-discovery#200.
-
-
1 issue reopened.
-
Define role of "Discoverer/Registerer" w3c/wot-discovery#216, by @farshidtz.
-
-
10 issues received 24 new comments.
-
TDD TD: Don't Actions need an input field w3c/wot-discovery#182 (5 comments by @egekorkan, @farshidtz, @mmccool)
-
Implementing a DNS-based approach, are DNS-SD and mDNS mandatory? w3c/wot-discovery#200 (4 comments by @mmccool)
-
Resolve TD/Thing ID Semantics (was Reconsider @type ThingID) w3c/wot-discovery#190 (3 comments by @AndreaCimminoArriaga, @farshidtz, @mmccool)
-
Improving event type values in the Notification API w3c/wot-discovery#197 (3 comments by @benfrancis, @farshidtz, @mmccool)
-
Define role of "Discoverer/Registerer" w3c/wot-discovery#216 (2 comments by @benfrancis, @farshidtz)
-
Security bootstrapping during discovery w3c/wot-discovery#135 (2 comments by @benfrancis, @farshidtz)
-
-
4 pull requests opened.
-
Add object types to actions w3c/wot-discovery#223, by @farshidtz.
-
Discoverer w3c/wot-discovery#222, by @mmccool.
-
Update intro to introduction mechanisms w3c/wot-discovery#221, by @mmccool.
-
Fix assertion in section 5 w3c/wot-discovery#220, by @k-toumura.
-
-
3 pull requests merged.
-
Discoverer w3c/wot-discovery#222.
-
Update intro to introduction mechanisms w3c/wot-discovery#221.
-
Fix assertion in section 5 w3c/wot-discovery#220.
-
-
2 pull requests received 3 new comments.
w3c/wot-architecture
-
7 issues opened.
-
Additional terminology entries for binding spec w3c/wot-architecture#614, by @mlagally.
-
Move terminology section from discovery to architecture spec w3c/wot-architecture#613, by @mlagally.
-
Move terminology from TD to architecture spec w3c/wot-architecture#612, by @mlagally.
-
Update Terminology regarding Binding Templates w3c/wot-architecture#611, by @egekorkan.
-
Review / update list of editors w3c/wot-architecture#610, by @mlagally.
-
Respec errors in rendered Architecture version w3c/wot-architecture#609, by @mlagally.
-
Relationship between "8.7 Protocol Bindings" and "9.5 WoT Binding Templates" w3c/wot-architecture#608, by @ashimura.
-
-
1 issue closed.
-
Chapter 7.1.2 - rework "Thing Model" to new title/content "Instance descriptions and class models" w3c/wot-architecture#595.
-
-
2 issues received 2 new comments.
-
Relationship between "8.7 Protocol Bindings" and "9.5 WoT Binding Templates" w3c/wot-architecture#608 (1 comment by @mlagally)
-
3 pull requests merged.
-
Add Description and Model Section w3c/wot-architecture#600.
-
Section on profiles w3c/wot-architecture#592.
-
Update index.html w3c/wot-architecture#607.
-
-
2 pull requests received 8 new comments.
w3c/wot-security
-
1 issue opened.
-
Reference terminology section of the architecture spec w3c/wot-security#202, by @mlagally.
-
w3c/wot-binding-templates
-
4 issues opened.
-
Broken links in the HTTP document w3c/wot-binding-templates#128, by @JKRhb.
-
List of Changes before the next Working Draft w3c/wot-binding-templates#127, by @egekorkan.
-
uriVariables in bindings w3c/wot-binding-templates#126, by @tuve.
-
Payload based protocols w3c/wot-binding-templates#125, by @tuve.
-
-
3 issues closed.
-
Broken links in the HTTP document w3c/wot-binding-templates#128.
-
Splitting the Main Document w3c/wot-binding-templates#113.
-
uriVariables in bindings w3c/wot-binding-templates#126.
-
-
4 issues received 13 new comments.
-
Broken links in the HTTP document w3c/wot-binding-templates#128 (4 comments by @danielpeintner, @egekorkan, @JKRhb)
-
1 pull request opened.
-
General improvements to the modbus ontology and spec files w3c/wot-binding-templates#129, by @relu91.
-
-
1 pull request merged.
-
Restructuring the Main Document w3c/wot-binding-templates#123.
-
-
1 pull request closed.
-
WIP: Guideline to create a new protocol binding w3c/wot-binding-templates#104.
-
w3c/wot-profile
-
9 issues opened.
-
Action Improvements: retention time of action status w3c/wot-profile#106, by @mlagally.
-
Action Improvements: identity /owner of an action invocation w3c/wot-profile#105, by @mlagally.
-
Actions Improvements: order of return values w3c/wot-profile#104, by @mlagally.
-
How long should actionStatus resources be retained for? w3c/wot-profile#102, by @benfrancis.
-
Actions need a way to express time stamps w3c/wot-profile#101, by @mlagally.
-
Events need a way to express timestamps w3c/wot-profile#100, by @mlagally.
-
How does a Consumer conforming to the Core Profile get a list of ongoing actions? w3c/wot-profile#99, by @benfrancis.
-
Server Sent Events section to reference a stable reliable specification w3c/wot-profile#98, by @mlagally.
-
Clarification on timeout handling of cancel operations w3c/wot-profile#97, by @mlagally.
-
-
4 issues closed.
-
How long should actionStatus resources be retained for? w3c/wot-profile#102.
-
Events are loosely constrained w3c/wot-profile#42.
-
Action semantics w3c/wot-profile#81.
-
-
5 issues received 6 new comments.
-
How long should actionStatus resources be retained for? w3c/wot-profile#102 (1 comment by @benfrancis)
-
Action Improvements: identity /owner of an action invocation w3c/wot-profile#105 (1 comment by @mlagally)
-
How does a Consumer conforming to the Core Profile get a list of ongoing actions? w3c/wot-profile#99 (1 comment by @benfrancis)
-
1 pull request opened.
-
Define protocol binding for `queryallactions` - closes #99 and #102 w3c/wot-profile#103, by @benfrancis.
-
-
5 pull requests merged.
-
Define protocol binding for `queryallactions` - closes #99 and #102 w3c/wot-profile#103.
-
Define protocol binding for events - closes #42 w3c/wot-profile#92.
-
time format - initial draft w3c/wot-profile#94.
-
Define protocol binding for actions - closes #81 w3c/wot-profile#89.
-
Remove Canonical TD dependency from property binding w3c/wot-profile#96.
-
-
2 pull requests closed.
-
Adding paragraph on transport encoding w3c/wot-profile#86.
-
Draft: action semantics w3c/wot-profile#88.
-
-
6 pull requests received 18 new comments.
-
Define protocol binding for events - closes #42 w3c/wot-profile#92 (10 comments by @benfrancis, @mlagally)
-
w3c/wot-ejs
-
5 issues opened.
-
Define context URL w3c/wot-ejs#8, by @mmccool.
-
Update Acks w3c/wot-ejs#7, by @mmccool.
-
Consider extending to also supporting enveloping signatures w3c/wot-ejs#5, by @mmccool.
-
Resolve TD dependencies w3c/wot-ejs#4, by @mmccool.
-
-
2 issues received 4 new comments.
-
3 pull requests opened.
-
initial version w3c/wot-ejs#3, by @mmccool.
-
add link to rendered version w3c/wot-ejs#2, by @mmccool.
-
Update README.md w3c/wot-ejs#1, by @mmccool.
-
-
3 pull requests merged.
-
add link to rendered version w3c/wot-ejs#2.
-
initial version w3c/wot-ejs#3.
-
Update README.md w3c/wot-ejs#1.
-
w3c/wot-security-best-practices
-
1 issue opened.
-
Recommend best practices for TDDs w3c/wot-security-best-practices#24, by @mmccool.
-
-
1 issue closed.
-
Expand Acknowledgements w3c/wot-security-best-practices#16.
-
-
2 issues received 9 new comments.
-
TD Signatures, Key Management, and Object Security w3c/wot-security-best-practices#14 (6 comments by @ashimura, @mmccool)
-
-
1 pull request opened.
-
Add content to Acks w3c/wot-security-best-practices#25, by @mmccool.
-
-
1 pull request merged.
-
Add content to Acks w3c/wot-security-best-practices#25.
-
-
1 pull request received 1 new comment.
Participants
-
2 participants joined.
-
Josiane Xavier Parreira (Siemens AG) joined.
-
Fady Salama (Siemens AG) joined.
-
GitHub
w3c/wot-binding-templates
-
5 issues opened.
-
Specifications of Protocols submitted to node-wot w3c/wot-binding-templates#124, by @egekorkan.
-
Adjusting Michael Koster's Affiliation w3c/wot-binding-templates#122, by @egekorkan.
-
Define a policy to generate a `default` form w3c/wot-binding-templates#121, by @relu91.
-
Binding Prefixes w3c/wot-binding-templates#120, by @danielpeintner.
-
Modbus Prefix w3c/wot-binding-templates#119, by @danielpeintner.
-
-
1 issue closed.
-
How to propose a new binding + TD example w3c/wot-binding-templates#103.
-
-
5 issues received 11 new comments.
-
Specifications of Protocols submitted to node-wot w3c/wot-binding-templates#124 (2 comments by @Citrullin, @egekorkan)
-
Define a policy to generate a `default` form w3c/wot-binding-templates#121 (2 comments by @egekorkan)
-
1 pull request opened.
-
Restructuring the Main Document w3c/wot-binding-templates#123, by @egekorkan.
-
w3c/wot-scripting-api
-
1 issue opened.
-
NotFoundError is not used w3c/wot-scripting-api#334, by @danielpeintner.
-
-
4 issues closed.
-
Publish Thing Description schema and Types in another npm package w3c/wot-scripting-api#327.
-
Partial TD validation for input of produce() method w3c/wot-scripting-api#212.
-
Extract normative assertions for testing w3c/wot-scripting-api#117.
-
TypeScript - Type DataSchemaValue circularly references itself w3c/wot-scripting-api#301.
-
-
7 issues received 17 new comments.
-
Should writeProperty() return a value w3c/wot-scripting-api#193 (5 comments by @danielpeintner, @egekorkan, @relu91)
-
Partial TD validation for input of produce() method w3c/wot-scripting-api#212 (2 comments by @danielpeintner, @relu91)
-
TypeScript - Type DataSchemaValue circularly references itself w3c/wot-scripting-api#301 (1 comment by @danielpeintner)
-
3 pull requests opened.
-
Label Table w3c/wot-scripting-api#333, by @danielpeintner.
-
fix: links *new* typescript folder w3c/wot-scripting-api#332, by @danielpeintner.
-
docs: add readme about TS files and process w3c/wot-scripting-api#331, by @danielpeintner.
-
-
3 pull requests merged.
-
fix: links *new* typescript folder w3c/wot-scripting-api#332.
-
docs: add readme about TS files and process w3c/wot-scripting-api#331.
-
feat: move thing-description types to a dedicated package w3c/wot-scripting-api#329.
-
-
4 pull requests received 24 new comments.
-
Label Table w3c/wot-scripting-api#333 (12 comments by @danielpeintner, @egekorkan, @relu91, @zolkis)
-
feat: move thing-description types to a dedicated package w3c/wot-scripting-api#329 (10 comments by @danielpeintner, @relu91, @zolkis)
-
docs: add readme about TS files and process w3c/wot-scripting-api#331 (1 comment by @danielpeintner)
-
w3c/wot-thing-description
-
7 issues opened.
-
Specify format of additional information for TM-to-TD conversion? w3c/wot-thing-description#1215, by @JKRhb.
-
TD File Extension Convention w3c/wot-thing-description#1214, by @egekorkan.
-
Property-change / Event-fire frequency w3c/wot-thing-description#1213, by @danielpeintner.
-
Use of Additional Response in non-error cases w3c/wot-thing-description#1211, by @egekorkan.
-
unit URI generation error w3c/wot-thing-description#1210, by @Murloc6.
-
[TM] Use of instance in version should be banned in TMs w3c/wot-thing-description#1209, by @egekorkan.
-
Top-level `data` field for Thing Models? w3c/wot-thing-description#1206, by @JKRhb.
-
-
3 issues closed.
-
Why is contentType optional on AdditionalResponse? w3c/wot-thing-description#1189.
-
Rearranging examples for security in section 6.3.4 w3c/wot-thing-description#1141.
-
Top-level `data` field for Thing Models? w3c/wot-thing-description#1206.
-
-
12 issues received 41 new comments.
-
How do you cancel or query the state of an action request? w3c/wot-thing-description#302 (12 comments by @benfrancis, @egekorkan, @relu91, @sebastiankb)
-
Add "precision" to data schema w3c/wot-thing-description#1001 (7 comments by @mmccool, @sebastiankb)
-
Use of Additional Response in non-error cases w3c/wot-thing-description#1211 (6 comments by @benfrancis, @egekorkan, @farshidtz)
-
TD File Extension Convention w3c/wot-thing-description#1214 (4 comments by @benfrancis, @egekorkan, @FadySalama, @relu91)
-
JSON Schema validation issue wr.t. "format": "iri-reference" w3c/wot-thing-description#956 (2 comments by @danielpeintner, @egekorkan)
-
Top-level `data` field for Thing Models? w3c/wot-thing-description#1206 (2 comments by @egekorkan, @JKRhb)
-
Specify format of additional information for TM-to-TD conversion? w3c/wot-thing-description#1215 (1 comment by @relu91)
-
Why is contentType optional on AdditionalResponse? w3c/wot-thing-description#1189 (1 comment by @egekorkan)
-
Is there a need for `invokeanyaction`/`queryallactions` operations? w3c/wot-thing-description#1200 (1 comment by @benfrancis)
-
unit for human-redable / display purposes or as semantic annotation? w3c/wot-thing-description#1202 (1 comment by @Digital-Water)
-
Should it be possible to indicate whether writing a property returns set value? w3c/wot-thing-description#875 (1 comment by @sebastiankb)
-
-
3 pull requests opened.
-
fix: maxItems,minItems are xsd:nonNegativeInteger w3c/wot-thing-description#1212, by @ioggstream.
-
Add queryaction and cancelaction operations - closes #302 w3c/wot-thing-description#1208, by @benfrancis.
-
Updates for TM Chapter w3c/wot-thing-description#1207, by @sebastiankb.
-
-
3 pull requests merged.
-
Fix definition of multipleOf in TD schema w3c/wot-thing-description#1204.
-
Security reorder w3c/wot-thing-description#1201.
-
Draft Testing Report for TD 1.1 w3c/wot-thing-description#1155.
-
-
8 pull requests received 20 new comments.
-
Fix definition of multipleOf in TD schema w3c/wot-thing-description#1204 (7 comments by @danielpeintner, @egekorkan, @JKRhb, @sebastiankb, @w3cbot)
-
Add queryaction and cancelaction operations - closes #302 w3c/wot-thing-description#1208 (5 comments by @benfrancis, @JKRhb)
-
Draft Testing Report for TD 1.1 w3c/wot-thing-description#1155 (2 comments by @mmccool, @sebastiankb)
-
fix: maxItems,minItems are xsd:nonNegativeInteger w3c/wot-thing-description#1212 (1 comment by @danielpeintner)
-
w3c/wot-discovery
-
1 issue closed.
-
Method to query content length before exploration w3c/wot-discovery#146.
-
-
3 issues received 3 new comments.
-
Registration of Well-known URI, DNS-SD and DID Service Names, CoRE Resource Type w3c/wot-discovery#187 (1 comment by @mmccool)
-
-
3 pull requests opened.
-
HTTP HEAD method to request the content length (self-description) w3c/wot-discovery#219, by @farshidtz.
-
HTTP HEAD method to request the content length w3c/wot-discovery#218, by @farshidtz.
-
Add Well-Known URI and Service Name in "IANA Considerations" section w3c/wot-discovery#217, by @k-toumura.
-
-
3 pull requests merged.
-
HTTP HEAD method to request the content length (self-description) w3c/wot-discovery#219.
-
HTTP HEAD method to request the content length w3c/wot-discovery#218.
-
Add Well-Known URI and Service Name in "IANA Considerations" section w3c/wot-discovery#217.
-
w3c/wot-security-best-practices
-
4 issues received 6 new comments.
-
TD Signatures, Key Management, and Object Security w3c/wot-security-best-practices#14 (2 comments by @mmccool)
w3c/wot-profile
-
1 issue opened.
-
1 issue received 2 new comments.
-
Should the Core Profile define a protocol binding for `observeproperty`/`unobserveproperty`? w3c/wot-profile#95 (2 comments by @benfrancis, @egekorkan)
-
-
1 pull request opened.
-
Remove Canonical TD dependency from property binding w3c/wot-profile#96, by @benfrancis.
-
-
5 pull requests received 12 new comments.
-
Define protocol binding for actions - closes #81 w3c/wot-profile#89 (3 comments by @benfrancis, @mlagally)
-
Example TD and declarative protocol binding illustration - closes #90 w3c/wot-profile#91 (2 comments by @benfrancis, @mlagally)
w3c/wot-architecture
-
1 pull request opened.
-
Update index.html w3c/wot-architecture#607, by @lu-zero.
-
Participants
-
1 participant joined.
-
Thomas Jäckle (Robert Bosch GmbH) joined.
-
-
1 participant left.
-
Jan Šuráň (Fiserv) left.
-
-
1 organization left.
-
Fiserv left.
-
GitHub
w3c/wot-thing-description
-
16 issues opened.
-
IDs should not have embedded metadata w3c/wot-thing-description#1203, by @mmccool.
-
unit for human-redable / display purposes or as semantic annotation? w3c/wot-thing-description#1202, by @sebastiankb.
-
Is there a need for `invokeanyaction`/`queryallactions` operations? w3c/wot-thing-description#1200, by @benfrancis.
-
Small incoherence in `forms` Thing Description core vocabulary w3c/wot-thing-description#1199, by @relu91.
-
[discussion] TD Linting w3c/wot-thing-description#1195, by @egekorkan.
-
Type of `enum`, `const`, and `default` w3c/wot-thing-description#1194, by @JKRhb.
-
WOT TD round tripping for securityDefinitions w3c/wot-thing-description#1193, by @Murloc6.
-
op does not have with default tag anymore w3c/wot-thing-description#1192, by @egekorkan.
-
Canonicalization fixes w3c/wot-thing-description#1190, by @mmccool.
-
Why is contentType optional on AdditionalResponse? w3c/wot-thing-description#1189, by @egekorkan.
-
Array of Forms ordering w3c/wot-thing-description#1188, by @farshidtz.
-
datetime format in TD canonicalization w3c/wot-thing-description#1187, by @fatadel.
-
Thing Description Framing for RDF/JSON-LD round-tripping w3c/wot-thing-description#1981, by @ethieblin.
-
Issues with Thing Model schema w3c/wot-thing-description#1186, by @JKRhb.
-
Problems translating TDs to RDF and their validation w3c/wot-thing-description#1185, by @AndreaCimminoArriaga.
-
Roundtripping TDs and consequences of TD Canonicalization w3c/wot-thing-description#1183, by @danielpeintner.
-
-
10 issues closed.
-
Default value for observable w3c/wot-thing-description#1180.
-
Invalid TD in example w3c/wot-thing-description#1178.
-
format is listed under DataSchema w3c/wot-thing-description#1114.
-
Making the uriVariables recommendation paragraph an editor's note w3c/wot-thing-description#1138.
-
Differnt colors for <code> markup w3c/wot-thing-description#349.
-
`observeallproperties` and `unobserveallproperties` clarification w3c/wot-thing-description#1084.
-
"Previous version" link not available anymore w3c/wot-thing-description#1087.
-
max length payload metdata information w3c/wot-thing-description#1153.
-
const appears twice under DataSchema w3c/wot-thing-description#1115.
-
Add `subscribeallevents` and `unsubscribeallevents` operations w3c/wot-thing-description#1082.
-
-
43 issues received 107 new comments.
-
Describing initial connection w3c/wot-thing-description#878 (15 comments by @benfrancis, @danielpeintner, @egekorkan, @relu91, @sebastiankb)
-
Is there a need for `invokeanyaction`/`queryallactions` operations? w3c/wot-thing-description#1200 (6 comments by @benfrancis, @egekorkan, @sebastiankb)
-
How do you cancel or query the state of an action request? w3c/wot-thing-description#302 (5 comments by @benfrancis, @sebastiankb)
-
Why is contentType optional on AdditionalResponse? w3c/wot-thing-description#1189 (5 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
Type of `enum`, `const`, and `default` w3c/wot-thing-description#1194 (5 comments by @egekorkan, @JKRhb)
-
Problems translating TDs to RDF and their validation w3c/wot-thing-description#1185 (4 comments by @AndreaCimminoArriaga, @danielpeintner, @sebastiankb)
-
Array of Forms ordering w3c/wot-thing-description#1188 (4 comments by @AndreaCimminoArriaga, @relu91, @sebastiankb)
-
Validation of extensions and fetching from context URLs w3c/wot-thing-description#1181 (4 comments by @AndreaCimminoArriaga, @mmccool, @relu91)
-
JSON Schema validation issue wr.t. "format": "iri-reference" w3c/wot-thing-description#956 (3 comments by @egekorkan, @FadySalama)
-
Rename / retitle op for Things w3c/wot-thing-description#1174 (3 comments by @egekorkan, @FadySalama, @relu91)
-
"Previous version" link not available anymore w3c/wot-thing-description#1087 (3 comments by @danielpeintner, @egekorkan)
-
Clarifying how readmultipleproperties work w3c/wot-thing-description#848 (3 comments by @egekorkan, @JKRhb, @zolkis)
-
datetime format in TD canonicalization w3c/wot-thing-description#1187 (3 comments by @danielpeintner, @sebastiankb)
-
unit for human-redable / display purposes or as semantic annotation? w3c/wot-thing-description#1202 (2 comments by @egekorkan, @FadySalama)
-
op does not have with default tag anymore w3c/wot-thing-description#1192 (2 comments by @benfrancis, @sebastiankb)
-
[vocabulary] Consider adding keyword to describe synchronous actions w3c/wot-thing-description#890 (2 comments by @egekorkan, @mlagally)
-
Consider adding DataSchema to response and additionalResponses w3c/wot-thing-description#1053 (2 comments by @benfrancis, @egekorkan)
-
`observeallproperties` and `unobserveallproperties` clarification w3c/wot-thing-description#1084 (2 comments by @egekorkan)
-
Thing Description Framing for RDF/JSON-LD round-tripping w3c/wot-thing-description#1981 (2 comments by @ethieblin, @mmccool)
-
Add `subscribeallevents` and `unsubscribeallevents` operations w3c/wot-thing-description#1082 (2 comments by @benfrancis, @relu91)
-
Which is better to actuate devices, invoking ACTION or writing PROPERTY? w3c/wot-thing-description#1020 (2 comments by @mlagally, @mryuichi)
-
Roundtripping TDs and consequences of TD Canonicalization w3c/wot-thing-description#1183 (2 comments by @AndreaCimminoArriaga, @relu91)
-
An explainer table for the operation values is missing w3c/wot-thing-description#1074 (1 comment by @egekorkan)
-
Examples for actions using URI variables should explain why not using input w3c/wot-thing-description#910 (1 comment by @egekorkan)
-
HTTP Binding for providing historical events. w3c/wot-thing-description#892 (1 comment by @benfrancis)
-
Small incoherence in `forms` Thing Description core vocabulary w3c/wot-thing-description#1199 (1 comment by @egekorkan)
-
Making the uriVariables recommendation paragraph an editor's note w3c/wot-thing-description#1138 (1 comment by @egekorkan)
-
The "proxy-to" relation type overlaps "proxy" in security schemes w3c/wot-thing-description#1075 (1 comment by @egekorkan)
-
Rearranging examples for security in section 6.3.4 w3c/wot-thing-description#1141 (1 comment by @egekorkan)
-
Guarantee RDF round-tripping for security definitions w3c/wot-thing-description#1125 (1 comment by @AndreaCimminoArriaga)
-
-
8 pull requests opened.
-
Fix issues in TM schema generation script w3c/wot-thing-description#1205, by @JKRhb.
-
Fix definition of multipleOf in TD schema w3c/wot-thing-description#1204, by @JKRhb.
-
Security reorder w3c/wot-thing-description#1201, by @egekorkan.
-
Defaults fix w3c/wot-thing-description#1198, by @egekorkan.
-
fix example 37 and its canonical form w3c/wot-thing-description#1197, by @egekorkan.
-
Add social media icons to Readme w3c/wot-thing-description#1196, by @egekorkan.
-
Add subscribeallevents and unsubscribeallevents operations - closes #1082 w3c/wot-thing-description#1191, by @benfrancis.
-
correct <span> element for ComboSecurity assertion and add unique id w3c/wot-thing-description#1184, by @FadySalama.
-
-
6 pull requests merged.
-
Defaults fix w3c/wot-thing-description#1198.
-
fix example 37 and its canonical form w3c/wot-thing-description#1197.
-
fix: replace "name" with "title" in TM example w3c/wot-thing-description#1175.
-
Add social media icons to Readme w3c/wot-thing-description#1196.
-
correct <span> element for ComboSecurity assertion and add unique id w3c/wot-thing-description#1184.
-
Add subscribeallevents and unsubscribeallevents operations - closes #1082 w3c/wot-thing-description#1191.
-
-
12 pull requests received 40 new comments.
-
Fix issues in TM schema generation script w3c/wot-thing-description#1205 (8 comments by @egekorkan, @JKRhb)
-
Add social media icons to Readme w3c/wot-thing-description#1196 (7 comments by @danielpeintner, @egekorkan, @JKRhb, @mmccool)
-
Add subscribeallevents and unsubscribeallevents operations - closes #1082 w3c/wot-thing-description#1191 (7 comments by @benfrancis, @danielpeintner, @relu91, @sebastiankb)
-
fix: replace "name" with "title" in TM example w3c/wot-thing-description#1175 (5 comments by @JKRhb, @sebastiankb, @w3cbot)
-
correct <span> element for ComboSecurity assertion and add unique id w3c/wot-thing-description#1184 (5 comments by @ashimura, @danielpeintner, @egekorkan, @sebastiankb, @w3cbot)
-
Fix definition of multipleOf in TD schema w3c/wot-thing-description#1204 (2 comments by @egekorkan, @JKRhb)
-
fix: fix RDF triples example from Thing description json-ld 1.1 w3c/wot-thing-description#1167 (1 comment by @sebastiankb)
-
WIP: swap securtiy and securityDefinition in context file w3c/wot-thing-description#937 (1 comment by @sebastiankb)
-
w3c/wot-profile
-
1 issue opened.
-
Provide example TD and declarative protocol binding illustration for Core Profile w3c/wot-profile#90, by @benfrancis.
-
-
2 issues received 14 new comments.
-
Action semantics w3c/wot-profile#81 (13 comments by @benfrancis, @egekorkan, @mlagally, @relu91, @sebastiankb)
-
-
9 pull requests opened.
-
time format - initial draft w3c/wot-profile#94, by @mlagally.
-
WIP: reworking data model section w3c/wot-profile#93, by @mlagally.
-
Define protocol binding for events - closes #42 w3c/wot-profile#92, by @benfrancis.
-
Example TD and declarative protocol binding illustration - closes #90 w3c/wot-profile#91, by @benfrancis.
-
Define protocol binding for actions - closes #81 w3c/wot-profile#89, by @benfrancis.
-
Draft: action semantics w3c/wot-profile#88, by @mlagally.
-
Placeholder section on transport security w3c/wot-profile#87, by @mlagally.
-
Adding paragraph on transport encoding w3c/wot-profile#86, by @mlagally.
-
Create echonetExampleTD.td.jsonld w3c/wot-profile#85, by @egekorkan.
-
-
9 pull requests received 64 new comments.
-
Define protocol binding for events - closes #42 w3c/wot-profile#92 (20 comments by @benfrancis, @egekorkan, @mlagally, @mmccool, @relu91)
-
Define protocol binding for actions - closes #81 w3c/wot-profile#89 (17 comments by @benfrancis, @egekorkan, @mlagally, @mmccool)
-
Placeholder section on transport security w3c/wot-profile#87 (7 comments by @benfrancis, @danielpeintner, @mlagally, @mmccool)
-
Create echonetExampleTD.td.jsonld w3c/wot-profile#85 (6 comments by @danielpeintner, @egekorkan, @mlagally, @mmccool, @relu91)
-
WIP: reworking data model section w3c/wot-profile#93 (3 comments by @benfrancis, @egekorkan, @mmccool)
-
w3c/wot-scripting-api
-
1 issue opened.
-
Publish Thing Description schema and Types in another npm package w3c/wot-scripting-api#327, by @relu91.
-
-
1 issue closed.
-
Security, WoT Scripting API doc: security failures w3c/wot-scripting-api#90.
-
-
4 issues received 13 new comments.
-
Publish Thing Description schema and Types in another npm package w3c/wot-scripting-api#327 (10 comments by @danielpeintner, @egekorkan, @relu91)
-
`observeallproperties` and `unobserveallproperties` methods are missing w3c/wot-scripting-api#312 (1 comment by @danielpeintner)
-
w3c/wot-scripting-api#328 (1 comment by @danielpeintner)
-
-
1 pull request opened.
-
feat: move thing-description types to a dedicated package w3c/wot-scripting-api#329, by @relu91.
-
-
1 pull request received 6 new comments.
-
feat: move thing-description types to a dedicated package w3c/wot-scripting-api#329 (6 comments by @danielpeintner)
-
w3c/wot-security-best-practices
-
2 issues closed.
-
Clean up Draft w3c/wot-security-best-practices#12.
-
Add or Remove Summary Section w3c/wot-security-best-practices#15.
-
-
5 issues received 17 new comments.
-
Update Secure Local Transport w3c/wot-security-best-practices#13 (11 comments by @Citrullin, @mmccool)
-
TD Signatures, Key Management, and Object Security w3c/wot-security-best-practices#14 (2 comments by @mmccool)
-
-
7 pull requests opened.
-
Update index.html w3c/wot-security-best-practices#23, by @mmccool.
-
Update index.html w3c/wot-security-best-practices#22, by @mmccool.
-
Add local TLS/DTLS security via Raw Public Keys w3c/wot-security-best-practices#21, by @Citrullin.
-
Add Ed Note to Object Security w3c/wot-security-best-practices#19, by @mmccool.
-
Delete Summary w3c/wot-security-best-practices#18, by @mmccool.
-
Expand Acknowledgements w3c/wot-security-best-practices#17, by @mmccool.
-
-
7 pull requests merged.
-
Update index.html w3c/wot-security-best-practices#23.
-
Update index.html w3c/wot-security-best-practices#22.
-
Cleanup w3c/wot-security-best-practices#20.
-
Add local TLS/DTLS security via Raw Public Keys w3c/wot-security-best-practices#21.
-
Add Ed Note to Object Security w3c/wot-security-best-practices#19.
-
Delete Summary w3c/wot-security-best-practices#18.
-
Expand Acknowledgements w3c/wot-security-best-practices#17.
-
w3c/wot-discovery
-
2 issues opened.
-
Define role of "Discoverer/Registerer" w3c/wot-discovery#216, by @mmccool.
-
Sharing TDs via other means w3c/wot-discovery#212, by @mmccool.
-
-
18 issues closed.
-
Handle huge set of Thing Descriptions (pagination, streaming, etc.) w3c/wot-discovery#16.
-
Immutable Thing Description IDs inside the directory w3c/wot-discovery#39.
-
Small text improvements for 6.2.2.1.5 Listing w3c/wot-discovery#203.
-
Identifying what information is conveyed in the TD and what is conveyed in the text w3c/wot-discovery#183.
-
Which aspects of the Directory Service API's TD are normative? w3c/wot-discovery#144.
-
Clarifying Introduction Mechanisms w3c/wot-discovery#53.
-
How to deal with JSON-LD fragments in query responses w3c/wot-discovery#63.
-
Consider Role "Part of" TDs in Query Results w3c/wot-discovery#21.
-
Create structure to organize PoCs w3c/wot-discovery#9.
-
Update CSS to add syntax highlighting for normative TD content w3c/wot-discovery#41.
-
Define the WoT-Directory type somewhere (eg in new version of context, in 1.1) w3c/wot-discovery#43.
-
Publish updated WD w3c/wot-discovery#154.
-
Experimental discovery implementation using mDNS, DNS-SD and MongoDB w3c/wot-discovery#5.
-
Reorganize Prior work w3c/wot-discovery#10.
-
Define a concrete network API for a TD Directory service w3c/wot-discovery#8.
-
Index prior work w3c/wot-discovery#6.
-
Add DID to background.md w3c/wot-discovery#3.
-
EnrichedThing as a class? w3c/wot-discovery#169.
-
-
24 issues received 29 new comments.
-
Identifying what information is conveyed in the TD and what is conveyed in the text w3c/wot-discovery#183 (3 comments by @farshidtz, @mmccool)
-
"Thing description" for Directory should be a "Thing Model" w3c/wot-discovery#86 (2 comments by @mmccool)
-
Which aspects of the Directory Service API's TD are normative? w3c/wot-discovery#144 (1 comment by @mmccool)
-
Directories should notify subscribers when a TD is updated w3c/wot-discovery#28 (1 comment by @mmccool)
-
Handle huge set of Thing Descriptions (pagination, streaming, etc.) w3c/wot-discovery#16 (1 comment by @mmccool)
-
Update CSS to add syntax highlighting for normative TD content w3c/wot-discovery#41 (1 comment by @farshidtz)
-
Define the WoT-Directory type somewhere (eg in new version of context, in 1.1) w3c/wot-discovery#43 (1 comment by @farshidtz)
-
Experimental discovery implementation using mDNS, DNS-SD and MongoDB w3c/wot-discovery#5 (1 comment by @mmccool)
-
Define a concrete network API for a TD Directory service w3c/wot-discovery#8 (1 comment by @mmccool)
-
Registration of Well-known URI, DNS-SD and DID Service Names, CoRE Resource Type w3c/wot-discovery#187 (1 comment by @k-toumura)
-
-
5 pull requests opened.
-
Add HTTP paths to assertions w3c/wot-discovery#215, by @farshidtz.
-
Improvements to listing text w3c/wot-discovery#214, by @farshidtz.
-
Add alternative payload format (2) w3c/wot-discovery#213, by @wiresio.
-
Fix plural terms w3c/wot-discovery#211, by @farshidtz.
-
Minor assertion fixes w3c/wot-discovery#210, by @farshidtz.
-
-
6 pull requests merged.
-
Add alternative payload format (2) w3c/wot-discovery#213.
-
Add HTTP paths to assertions w3c/wot-discovery#215.
-
Improvements to listing text w3c/wot-discovery#214.
-
Fix plural terms w3c/wot-discovery#211.
-
Minor assertion fixes w3c/wot-discovery#210.
-
Thing Link usage examples w3c/wot-discovery#207.
-
-
1 pull request closed.
-
Add alternative payload format w3c/wot-discovery#168.
-
-
3 pull requests received 14 new comments.
-
Add alternative payload format (2) w3c/wot-discovery#213 (8 comments by @AndreaCimminoArriaga, @farshidtz, @mmccool, @wiresio)
-
w3c/wot-architecture
-
1 issue opened.
-
Move Table for ops to TD spec w3c/wot-architecture#606, by @mmccool.
-
-
2 issues closed.
-
Section 8.3 - device categories w3c/wot-architecture#598.
-
Chapter 8.1 TD: Remove / move discovery paragraph into the discovery section w3c/wot-architecture#594.
-
-
1 issue received 2 new comments.
-
2 pull requests opened.
-
Add observeallproperties, unobserveallproperties, subscribeallevents and unsubscribeallevents w3c/wot-architecture#605, by @benfrancis.
-
WIP: Provides text for TM w3c/wot-architecture#604, by @sebastiankb.
-
-
4 pull requests merged.
-
Add observeallproperties, unobserveallproperties, subscribeallevents and unsubscribeallevents w3c/wot-architecture#605.
-
WIP: Provides text for TM w3c/wot-architecture#604.
-
Fixup Device Classes w3c/wot-architecture#601.
-
Refactor TD/Discovery Material in Section 8 w3c/wot-architecture#602.
-
-
4 pull requests received 6 new comments.
w3c/wot-binding-templates
-
5 issues opened.
-
Introduce `contentType` byte order w3c/wot-binding-templates#118, by @relu91.
-
Fix examples links w3c/wot-binding-templates#117, by @relu91.
-
Use `quantity` instead of `length` w3c/wot-binding-templates#116, by @relu91.
-
Use `address` instead of `offeset` w3c/wot-binding-templates#115, by @relu91.
-
No default HTTP vocabulary for observable properties and events w3c/wot-binding-templates#114, by @JKRhb.
-
-
4 issues received 10 new comments.
-
No default HTTP vocabulary for observable properties and events w3c/wot-binding-templates#114 (5 comments by @egekorkan, @JKRhb)
-
Introduce `contentType` byte order w3c/wot-binding-templates#118 (3 comments by @egekorkan, @relu91, @sebastiankb)
-
-
2 pull requests merged.
-
Modbus Vocabulary w3c/wot-binding-templates#98.
-
Refining Modbus protocol binding w3c/wot-binding-templates#109.
-
-
1 pull request received 2 new comments.
w3c/wot-security
-
1 issue received 1 new comment.
TR publications
-
2 documents published.
-
Web of Things (WoT) Thing Description 1.1 published as a Working Draft. History of Web of Things (WoT) Thing Description 1.1
-
Web of Things (WoT) Discovery published as a Working Draft. History of Web of Things (WoT) Discovery
-
Participants
-
1 participant joined.
-
William Holroyd (Lenovo) joined.
-
-
1 organization joined.
-
Lenovo joined.
-
GitHub
w3c/wot-discovery
-
9 issues opened.
-
Read-Only Directories w3c/wot-discovery#208, by @RoboPhred.
-
Small text improvements for 6.2.2.1.5 Listing w3c/wot-discovery#203, by @sebastiankb.
-
Exploration Mechanisms w3c/wot-discovery#202, by @sebastiankb.
-
Sequence diagrams for DID based discovery approaches w3c/wot-discovery#201, by @sebastiankb.
-
Implementing a DNS-based approach, are DNS-SD and mDNS mandatory? w3c/wot-discovery#200, by @sebastiankb.
-
add dates to change log w3c/wot-discovery#199, by @mmccool.
-
Improving event type values in the Notification API w3c/wot-discovery#197, by @farshidtz.
-
Self-reference to wot-discovery w3c/wot-discovery#194, by @mmccool.
-
Assertions removed by mistake for Introductions? w3c/wot-discovery#193, by @mmccool.
-
-
3 issues closed.
-
Refactoring TDD Thing Description w3c/wot-discovery#133.
-
Self-reference to wot-discovery w3c/wot-discovery#194.
-
Update change log for WD2 w3c/wot-discovery#189.
-
-
10 issues received 32 new comments.
-
Resolve TD/Thing ID Semantics (was Reconsider @type ThingID) w3c/wot-discovery#190 (6 comments by @AndreaCimminoArriaga, @egekorkan, @farshidtz, @mmccool)
-
Small text improvements for 6.2.2.1.5 Listing w3c/wot-discovery#203 (4 comments by @farshidtz, @sebastiankb)
-
Assertions removed by mistake for Introductions? w3c/wot-discovery#193 (4 comments by @k-toumura, @mmccool)
-
Implementing a DNS-based approach, are DNS-SD and mDNS mandatory? w3c/wot-discovery#200 (3 comments by @k-toumura, @sebastiankb)
-
TDD TD: Don't Actions need an input field w3c/wot-discovery#182 (2 comments by @egekorkan, @mmccool)
-
Don't try to describe the Directory Service API in a Thing Description w3c/wot-discovery#172 (1 comment by @RoboPhred)
-
Improving event type values in the Notification API w3c/wot-discovery#197 (1 comment by @benfrancis)
-
9 pull requests opened.
-
Thing Link usage examples w3c/wot-discovery#207, by @farshidtz.
-
Revert to use UUID URN as system-generated TD identifier w3c/wot-discovery#206, by @farshidtz.
-
Add missing event IDs in SSE examples w3c/wot-discovery#205, by @farshidtz.
-
Refactor assertion IDs w3c/wot-discovery#204, by @farshidtz.
-
Notification API: pass event type in HTTP path instead of query w3c/wot-discovery#198, by @farshidtz.
-
Refactor Directory Service API TD (split events) w3c/wot-discovery#196, by @farshidtz.
-
Correction in IANA consideration internal reference w3c/wot-discovery#195, by @farshidtz.
-
Addition of change log WD2 w3c/wot-discovery#192, by @mmccool.
-
Refactor Directory Service API TD (retrieve one and search as actions, listing as things property) w3c/wot-discovery#191, by @farshidtz.
-
-
8 pull requests merged.
-
Revert to use UUID URN as system-generated TD identifier w3c/wot-discovery#206.
-
Add missing event IDs in SSE examples w3c/wot-discovery#205.
-
Refactor assertion IDs w3c/wot-discovery#204.
-
Notification API: pass event type in HTTP path instead of query w3c/wot-discovery#198.
-
Refactor Directory Service API TD (split events) w3c/wot-discovery#196.
-
Correction in IANA consideration internal reference w3c/wot-discovery#195.
-
Addition of change log WD2 w3c/wot-discovery#192.
-
-
2 pull requests closed.
-
Replace interaction affordances in directory TD with a single link to its API endpoint w3c/wot-discovery#179.
-
Refactor Directory Service API TD w3c/wot-discovery#184.
-
-
4 pull requests received 9 new comments.
-
Refactor Directory Service API TD (split events) w3c/wot-discovery#196 (4 comments by @benfrancis, @farshidtz)
-
Replace interaction affordances in directory TD with a single link to its API endpoint w3c/wot-discovery#179 (2 comments by @benfrancis, @mmccool)
-
w3c/wot-thing-description
-
17 issues opened.
-
Versioning in TMs w3c/wot-thing-description#1182, by @sebastiankb.
-
Validation of extensions and fetching from context URLs w3c/wot-thing-description#1181, by @mmccool.
-
Default value for observable w3c/wot-thing-description#1180, by @fatadel.
-
Missing assertion in ComboSecurityScheme w3c/wot-thing-description#1179, by @FadySalama.
-
Invalid TD in example w3c/wot-thing-description#1178, by @fatadel.
-
Using composition in favor of inheritance in Thing Models? w3c/wot-thing-description#1177, by @thjaeckle.
-
Rename / retitle op for Things w3c/wot-thing-description#1174, by @RoboPhred.
-
Unclear assertion on TMs w3c/wot-thing-description#1173, by @egekorkan.
-
Unclear assertion on security w3c/wot-thing-description#1172, by @egekorkan.
-
Fixing Thing Model assertion ids w3c/wot-thing-description#1171, by @egekorkan.
-
json-schema context uses undefined prefix xsd w3c/wot-thing-description#1170, by @RoboPhred.
-
Minor spelling and grammar errors w3c/wot-thing-description#1165, by @ajs124.
-
Event Filtering w3c/wot-thing-description#1164, by @mmccool.
-
[Schema] accept other OAuth2 flows w3c/wot-thing-description#1162, by @relu91.
-
Hacking together a working json-ld context. w3c/wot-thing-description#1161, by @RoboPhred.
-
[JSON-LD] Compacting property affordance leaves readOnly, minLength, maxLength aliased. w3c/wot-thing-description#1160, by @RoboPhred.
-
New context url nonfunctional in json-ld operations w3c/wot-thing-description#1159, by @RoboPhred.
-
-
9 issues closed.
-
Problems translating TDs from JSON-LD 1.1 to RDF and back w3c/wot-thing-description#1015.
-
Hacking together a working json-ld context. w3c/wot-thing-description#1161.
-
json-schema context uses undefined prefix xsd w3c/wot-thing-description#1170.
-
hasInputSchema (and probably others) compacts "type" as "@type", breaking json-schema compatibility w3c/wot-thing-description#994.
-
[json-schema][json-ld] Json Schema RDF context fails to round trip w3c/wot-thing-description#988.
-
[JSON-LD] Compacting property affordance leaves readOnly, minLength, maxLength aliased. w3c/wot-thing-description#1160.
-
Unclear assertion on security w3c/wot-thing-description#1172.
-
Fixing Thing Model assertion ids w3c/wot-thing-description#1171.
-
contentEncoding and contentMediaType should be moved under string schema w3c/wot-thing-description#1116.
-
-
21 issues received 75 new comments.
-
Rename / retitle op for Things w3c/wot-thing-description#1174 (16 comments by @danielpeintner, @egekorkan, @jyhi, @relu91, @RoboPhred, @sebastiankb)
-
[vocabulary] Consider adding keyword to describe synchronous actions w3c/wot-thing-description#890 (11 comments by @ashimura, @egekorkan, @k-toumura, @mlagally)
-
Using composition in favor of inheritance in Thing Models? w3c/wot-thing-description#1177 (10 comments by @mmccool, @RoboPhred, @sebastiankb, @thjaeckle)
-
[Schema] accept other OAuth2 flows w3c/wot-thing-description#1162 (7 comments by @danielpeintner, @egekorkan, @relu91)
-
json-schema context uses undefined prefix xsd w3c/wot-thing-description#1170 (6 comments by @RoboPhred, @sebastiankb, @vcharpenay)
-
Hacking together a working json-ld context. w3c/wot-thing-description#1161 (3 comments by @RoboPhred, @vcharpenay)
-
[JSON-LD] Compacting property affordance leaves readOnly, minLength, maxLength aliased. w3c/wot-thing-description#1160 (3 comments by @RoboPhred, @vcharpenay)
-
Guarantee RDF round-tripping for security definitions w3c/wot-thing-description#1125 (3 comments by @AndreaCimminoArriaga, @relu91)
-
Unclear assertion on security w3c/wot-thing-description#1172 (3 comments by @egekorkan, @sebastiankb)
-
hasInputSchema (and probably others) compacts "type" as "@type", breaking json-schema compatibility w3c/wot-thing-description#994 (2 comments by @vcharpenay)
-
Validation of extensions and fetching from context URLs w3c/wot-thing-description#1181 (1 comment by @mmccool)
-
Vocabulary term "scheme" not defined when used inside securityDefinitions w3c/wot-thing-description#915 (1 comment by @vcharpenay)
-
Which is better to actuate devices, invoking ACTION or writing PROPERTY? w3c/wot-thing-description#1020 (1 comment by @mryuichi)
-
[json-schema][json-ld] Json Schema RDF context fails to round trip w3c/wot-thing-description#988 (1 comment by @vcharpenay)
-
New context url nonfunctional in json-ld operations w3c/wot-thing-description#1159 (1 comment by @egekorkan)
-
-
11 pull requests opened.
-
Fix TM related assertion ids, explain a security assertion w3c/wot-thing-description#1176, by @egekorkan.
-
fix: replace "name" with "title" in TM example w3c/wot-thing-description#1175, by @JKRhb.
-
Use previously define uri for the `td:name` and `jsonschema:propertyName` w3c/wot-thing-description#1169, by @Murloc6.
-
fix: add wotsec context on securityDefinitions property w3c/wot-thing-description#1168, by @ethieblin.
-
fix: fix RDF triples example from Thing description json-ld 1.1 w3c/wot-thing-description#1167, by @ethieblin.
-
fix: fix RDF triples example from Thing description json-ld 1.1 w3c/wot-thing-description#1166, by @ethieblin.
-
add success to addResp and refactor addResp into definitions w3c/wot-thing-description#1163, by @egekorkan.
-
Proposal: use version field in schemas w3c/wot-thing-description#1158, by @relu91.
-
Fix ContentEncoding and ContentMediaType w3c/wot-thing-description#1157, by @relu91.
-
fix links, combo, date in the schema w3c/wot-thing-description#1156, by @egekorkan.
-
Draft Testing Report for TD 1.1 w3c/wot-thing-description#1155, by @mmccool.
-
-
8 pull requests merged.
-
Extend JSON-LD context to allow for round-tripping to/from N-Triples w3c/wot-thing-description#1077.
-
fix: add wotsec context on securityDefinitions property w3c/wot-thing-description#1168.
-
Fix TM related assertion ids, explain a security assertion w3c/wot-thing-description#1176.
-
Fix ContentEncoding and ContentMediaType w3c/wot-thing-description#1157.
-
add success to addResp and refactor addResp into definitions w3c/wot-thing-description#1163.
-
More fixes to canonicalization w3c/wot-thing-description#1129.
-
Proposal: use version field in schemas w3c/wot-thing-description#1158.
-
fix links, combo, date in the schema w3c/wot-thing-description#1156.
-
-
2 pull requests closed.
-
Use previously define uri for the `td:name` and `jsonschema:propertyName` w3c/wot-thing-description#1169.
-
fix: fix RDF triples example from Thing description json-ld 1.1 w3c/wot-thing-description#1166.
-
-
12 pull requests received 41 new comments.
-
Use previously define uri for the `td:name` and `jsonschema:propertyName` w3c/wot-thing-description#1169 (11 comments by @ethieblin, @Murloc6, @RoboPhred, @vcharpenay)
-
fix: fix RDF triples example from Thing description json-ld 1.1 w3c/wot-thing-description#1167 (6 comments by @AndreaCimminoArriaga, @Murloc6, @vcharpenay, @wiresio)
-
Fix ContentEncoding and ContentMediaType w3c/wot-thing-description#1157 (6 comments by @danielpeintner, @egekorkan, @relu91, @sebastiankb)
-
fix: replace "name" with "title" in TM example w3c/wot-thing-description#1175 (4 comments by @JKRhb, @sebastiankb)
-
fix: add wotsec context on securityDefinitions property w3c/wot-thing-description#1168 (1 comment by @w3cbot)
-
Fix TM related assertion ids, explain a security assertion w3c/wot-thing-description#1176 (1 comment by @egekorkan)
-
add success to addResp and refactor addResp into definitions w3c/wot-thing-description#1163 (1 comment by @sebastiankb)
-
Extend JSON-LD context to allow for round-tripping to/from N-Triples w3c/wot-thing-description#1077 (1 comment by @vcharpenay)
-
w3c/wot-security
-
1 issue closed.
-
Provide guidance on use of OAuth 2 flows w3c/wot-security#194.
-
-
1 issue received 1 new comment.
w3c/wot-architecture
-
6 issues opened.
-
Review Binding specification chapter 9.5 w3c/wot-architecture#599, by @mlagally.
-
Section 8.3 - device categories w3c/wot-architecture#598, by @mlagally.
-
improve profile section (8.3.) w3c/wot-architecture#597, by @mlagally.
-
Rename section 7.1 to "System Concepts", revisit chapter structure w3c/wot-architecture#596, by @mlagally.
-
Chapter 7.1.2 - rework "Thing Model" to new title/content "Instance descriptions and class models" w3c/wot-architecture#595, by @mlagally.
-
Chapter 8.1 TD: Remove / move discovery paragraph into the discovery section w3c/wot-architecture#594, by @mlagally.
-
-
6 pull requests opened.
-
Define and Discuss "Hubs" w3c/wot-architecture#603, by @mmccool.
-
Refactor TD/Discovery Material in Section 8 w3c/wot-architecture#602, by @mmccool.
-
Fixup Device Classes w3c/wot-architecture#601, by @mmccool.
-
Add Description and Model Section w3c/wot-architecture#600, by @mmccool.
-
Carry over of device categories from profiles w3c/wot-architecture#593, by @mlagally.
-
Section on profiles w3c/wot-architecture#592, by @mlagally.
-
-
1 pull request merged.
-
Carry over of device categories from profiles w3c/wot-architecture#593.
-
w3c/wot-scripting-api
-
3 issues received 5 new comments.
-
w3c/wot-scripting-api#323 (3 comments by @danielpeintner)
-
w3c/wot-scripting-api#326 (1 comment by @danielpeintner)
-
w3c/wot-scripting-api#322 (1 comment by @relu91)
-
-
2 pull requests opened.
-
Allign types with the current specification w3c/wot-scripting-api#325, by @relu91.
-
Fix sync action w3c/wot-scripting-api#324, by @relu91.
-
-
2 pull requests merged.
-
Fix sync action w3c/wot-scripting-api#324.
-
Allign types with the current specification w3c/wot-scripting-api#325.
-
-
1 pull request received 1 new comment.
-
Allign types with the current specification w3c/wot-scripting-api#325 (1 comment by @danielpeintner)
-
w3c/wot-binding-templates
-
1 issue opened.
-
Splitting the Main Document w3c/wot-binding-templates#113, by @egekorkan.
-
-
2 issues received 2 new comments.
w3c/wot-profile
-
2 issues opened.
-
The policy for the assertions identified w3c/wot-profile#84, by @chachamimm.
-
Action semantics w3c/wot-profile#81, by @mlagally.
-
-
1 issue received 6 new comments.
-
2 pull requests opened.
-
Fixed the mistake on second line in index.html w3c/wot-profile#83, by @chachamimm.
-
RFC 2119 markup: add css mark <span> into index.html w3c/wot-profile#82, by @chachamimm.
-
-
3 pull requests merged.
-
New Profile Mechanism section w3c/wot-profile#79.
-
Fixed the mistake on second line in index.html w3c/wot-profile#83.
-
RFC 2119 markup: add css mark <span> into index.html w3c/wot-profile#82.
-
-
1 pull request closed.
-
Reference device w3c/wot-profile#69.
-
-
4 pull requests received 5 new comments.
Participants
-
3 participants joined.
-
Michael Prorock (Tradeverifyd) joined.
-
Michael Koster (W3C Invited Experts) joined.
-
Vlad Baluta (W3C Invited Experts) joined.
-
-
4 participants left.
-
Martin Alvarez (Fundacion CTIC) left.
-
Kimberly Garcia (Siemens AG) left.
-
Ankit Srivastava (German Research Center for Artificial Intelligence (DFKI) Gmbh) left.
-
Benjamin Klotz (Institut Mines-Télécom) left.
-
-
1 organization joined.
-
Tradeverifyd joined.
-
GitHub
w3c/wot-discovery
-
11 issues opened.
-
Resolve TD/Thing ID Semantics (was Reconsider @type ThingID) w3c/wot-discovery#190, by @relu91.
-
Update change log for WD2 w3c/wot-discovery#189, by @mmccool.
-
Registration of Well-known URI, DNS-SD and DID Service Names, CoRE Resource Type w3c/wot-discovery#187, by @k-toumura.
-
Identifying what information is conveyed in the TD and what is conveyed in the text w3c/wot-discovery#183, by @egekorkan.
-
TDD TD: Don't Actions need an input field w3c/wot-discovery#182, by @egekorkan.
-
Review Comments from Ege Korkan w3c/wot-discovery#178, by @egekorkan.
-
Event payload filtering w3c/wot-discovery#176, by @farshidtz.
-
Don't try to describe the Directory Service API in a Thing Description w3c/wot-discovery#172, by @benfrancis.
-
Cleanup TTL/Expiry w3c/wot-discovery#171, by @mmccool.
-
EnrichedThing as a class? w3c/wot-discovery#169, by @AndreaCimminoArriaga.
-
Review profile error codes w3c/wot-discovery#167, by @mmccool.
-
-
4 issues closed.
-
Need to define the discovery types and vocabulary w3c/wot-discovery#54.
-
Cleanup TTL/Expiry w3c/wot-discovery#171.
-
Consider TTL Use cases w3c/wot-discovery#18.
-
Anonymous TDs in a directory w3c/wot-discovery#149.
-
-
16 issues received 43 new comments.
-
Don't try to describe the Directory Service API in a Thing Description w3c/wot-discovery#172 (8 comments by @benfrancis, @egekorkan, @relu91)
-
Review Comments from Ege Korkan w3c/wot-discovery#178 (4 comments by @benfrancis, @egekorkan, @mmccool)
-
TDD TD: Don't Actions need an input field w3c/wot-discovery#182 (3 comments by @egekorkan, @farshidtz)
-
Identifying what information is conveyed in the TD and what is conveyed in the text w3c/wot-discovery#183 (3 comments by @egekorkan, @farshidtz)
-
Resolve TD/Thing ID Semantics (was Reconsider @type ThingID) w3c/wot-discovery#190 (2 comments by @egekorkan, @farshidtz)
-
JSONPath response data model w3c/wot-discovery#156 (2 comments by @AndreaCimminoArriaga, @farshidtz)
-
Which aspects of the Directory Service API's TD are normative? w3c/wot-discovery#144 (2 comments by @mmccool)
-
-
12 pull requests opened.
-
Refactor Directory Service API TD (td->thing, split anonymous create action) w3c/wot-discovery#188, by @farshidtz.
-
Move API spec to appendices w3c/wot-discovery#186, by @farshidtz.
-
Refactor Directory Service API TD w3c/wot-discovery#184, by @benfrancis.
-
Update exploration figures and types w3c/wot-discovery#181, by @farshidtz.
-
Create JSON Schema for validation of discovery extensions w3c/wot-discovery#180, by @farshidtz.
-
Replace interaction affordances in directory TD with a single link to its API endpoint w3c/wot-discovery#179, by @benfrancis.
-
Remove payload-based event filtering w3c/wot-discovery#177, by @farshidtz.
-
Updated directory to new ontology model w3c/wot-discovery#175, by @AndreaCimminoArriaga.
-
Improvements to expiry w3c/wot-discovery#174, by @farshidtz.
-
Directory TD refactoring w3c/wot-discovery#173, by @farshidtz.
-
Ignoring unknown event types w3c/wot-discovery#170, by @farshidtz.
-
Add alternative payload format w3c/wot-discovery#168, by @wiresio.
-
-
10 pull requests merged.
-
Move API spec to appendices w3c/wot-discovery#186.
-
Refactor Directory Service API TD (td->thing, split anonymous create action) w3c/wot-discovery#188.
-
Update exploration figures and types w3c/wot-discovery#181.
-
Updated directory to new ontology model w3c/wot-discovery#175.
-
Create JSON Schema for validation of discovery extensions w3c/wot-discovery#180.
-
Improvements to expiry w3c/wot-discovery#174.
-
Remove payload-based event filtering w3c/wot-discovery#177.
-
Expiry date for registered TDs w3c/wot-discovery#162.
-
Typos against main w3c/wot-discovery#166.
-
Rename DirectoryDescription to ThingDirectory w3c/wot-discovery#161.
-
-
5 pull requests closed.
-
Directory TD refactoring w3c/wot-discovery#173.
-
Rename actions to match properties and events w3c/wot-discovery#160.
-
Split registration event into multiple events w3c/wot-discovery#159.
-
Combine properties into a single things property w3c/wot-discovery#158.
-
Ignoring unknown event types w3c/wot-discovery#170.
-
-
13 pull requests received 74 new comments.
-
Refactor Directory Service API TD w3c/wot-discovery#184 (13 comments by @benfrancis, @egekorkan, @farshidtz, @relu91)
-
Updated directory to new ontology model w3c/wot-discovery#175 (10 comments by @AndreaCimminoArriaga, @farshidtz, @mmccool)
-
Rename actions to match properties and events w3c/wot-discovery#160 (10 comments by @benfrancis, @farshidtz, @mmccool, @relu91)
-
Expiry date for registered TDs w3c/wot-discovery#162 (9 comments by @AndreaCimminoArriaga, @farshidtz, @mmccool)
-
Split registration event into multiple events w3c/wot-discovery#159 (8 comments by @benfrancis, @farshidtz, @mmccool)
-
Combine properties into a single things property w3c/wot-discovery#158 (8 comments by @benfrancis, @farshidtz, @mmccool)
-
Replace interaction affordances in directory TD with a single link to its API endpoint w3c/wot-discovery#179 (6 comments by @AndreaCimminoArriaga, @benfrancis, @farshidtz)
-
Create JSON Schema for validation of discovery extensions w3c/wot-discovery#180 (1 comment by @AndreaCimminoArriaga)
-
w3c/wot-security
-
1 issue opened.
-
Scripting related topics w3c/wot-security#201, by @zolkis.
-
-
4 issues received 9 new comments.
-
Add "Security and Privacy Considerations" to all use cases (or requirements) w3c/wot-security#168 (4 comments by @mmccool)
-
Add integrity protection (proof section) to TDs w3c/wot-security#166 (3 comments by @Citrullin, @mmccool)
-
w3c/wot-security-best-practices
-
6 issues opened.
-
Expand Acknowledgements w3c/wot-security-best-practices#16, by @mmccool.
-
Add or Remove Summary Section w3c/wot-security-best-practices#15, by @mmccool.
-
TD Signatures, Key Management, and Object Security w3c/wot-security-best-practices#14, by @mmccool.
-
Update Secure Local Transport w3c/wot-security-best-practices#13, by @mmccool.
-
Clean up Draft w3c/wot-security-best-practices#12, by @mmccool.
-
Define interpretation of MUST, SHOULD w3c/wot-security-best-practices#11, by @mmccool.
-
-
5 issues received 9 new comments.
-
TD Signatures, Key Management, and Object Security w3c/wot-security-best-practices#14 (3 comments by @mmccool, @OliverPfaff)
-
Update with Discovery and Directory recommendations w3c/wot-security-best-practices#7 (1 comment by @mmccool)
-
-
1 pull request merged.
-
Move oAuth2 flow from usecases to security-best-practices w3c/wot-security-best-practices#10.
-
w3c/wot-thing-description
-
18 issues opened.
-
Additional uses of schemaDefinitions w3c/wot-thing-description#1154, by @egekorkan.
-
max length payload metdata information w3c/wot-thing-description#1153, by @mlagally.
-
tm:ref pattern should be more clear w3c/wot-thing-description#1152, by @sebastiankb.
-
Canonicalization of named data schemas w3c/wot-thing-description#1150, by @mmccool.
-
SecuritySchemas and Links w3c/wot-thing-description#1149, by @relu91.
-
Clarify expectations of writing a property w3c/wot-thing-description#1146, by @danielpeintner.
-
Add op to support PATCH w3c/wot-thing-description#1143, by @mmccool.
-
Rearranging examples for security in section 6.3.4 w3c/wot-thing-description#1141, by @egekorkan.
-
Update Abstract and Introduction with TM information w3c/wot-thing-description#1140, by @sebastiankb.
-
Creating subsections for readability w3c/wot-thing-description#1139, by @egekorkan.
-
Making the uriVariables recommendation paragraph an editor's note w3c/wot-thing-description#1138, by @egekorkan.
-
Comments - Call for Review of WoT Thing Description 1.1 specification and resolution to publish update w3c/wot-thing-description#1137, by @danielpeintner.
-
Need context URL for directories w3c/wot-thing-description#1135, by @mmccool.
-
Consumer should/must ignore unknown event types w3c/wot-thing-description#1134, by @mmccool.
-
{{PLACEHOLDER_IDENTIFIER}} causes ReSpec rendering error w3c/wot-thing-description#1131, by @danielpeintner.
-
Publish updated WD for Thing Description 1.1 w3c/wot-thing-description#1127, by @sebastiankb.
-
The "pattern" term should be more restricted w3c/wot-thing-description#1126, by @sebastiankb.
-
Guarantee RDF round-tripping for security definitions w3c/wot-thing-description#1125, by @vcharpenay.
-
-
27 issues closed.
-
Update Abstract and Introduction with TM information w3c/wot-thing-description#1140.
-
Render script related issues w3c/wot-thing-description#973.
-
Clarify the usage of base64 encodings in DataSchema/ContentType w3c/wot-thing-description#912.
-
Thing Description versioning and Scripting API w3c/wot-thing-description#932.
-
"MultiLanguage Map" is used without definition w3c/wot-thing-description#983.
-
Add formal validation process w3c/wot-thing-description#1043.
-
{{PLACEHOLDER_IDENTIFIER}} causes ReSpec rendering error w3c/wot-thing-description#1131.
-
Unsubscribing and unobserving are not in default values w3c/wot-thing-description#957.
-
uriVariables needs to be more limited w3c/wot-thing-description#1068.
-
TDT shall allow to define placeholders w3c/wot-thing-description#897.
-
Add "multipleOf" term to NumberSchema and IntegerSchema w3c/wot-thing-description#841.
-
Provide Typescript types definitions for Thing Descriptions w3c/wot-thing-description#1097.
-
Replace required with tmRequired for TM w3c/wot-thing-description#1080.
-
Add 'minLength' and 'maxLength' to StringSchema w3c/wot-thing-description#889.
-
id field in TD Templates w3c/wot-thing-description#593.
-
ThingTemplate definition is missing in td.ttl w3c/wot-thing-description#416.
-
Allow array for response in From class? w3c/wot-thing-description#617.
-
Multiple methodName's ? w3c/wot-thing-description#712.
-
Refer to developer documentation from a TD w3c/wot-thing-description#918.
-
Suggestion for change in upcoming release - Update link for JSON LD 1.1 w3c/wot-thing-description#1066.
-
Is there a way to set default values for uriVariables? w3c/wot-thing-description#1093.
-
How to extend Data Schema terms while being JSON Schema compliant w3c/wot-thing-description#1094.
-
jsonschema:StringSchema: pattern missing and maxLength is defined wrongly w3c/wot-thing-description#1101.
-
add a new vocabulary term "profile" with a String type w3c/wot-thing-description#806.
-
Remove Vocabulary and Vocabulary Term Terminology w3c/wot-thing-description#1118.
-
change ThingModel to tm:ThingModel and extend to tm:extend? w3c/wot-thing-description#1100.
-
Canonical dates and times w3c/wot-thing-description#1117.
-
-
1 issue reopened.
-
JSON Schema validation issue wr.t. "format": "iri-reference" w3c/wot-thing-description#956, by @egekorkan.
-
-
40 issues received 76 new comments.
-
Add optional proof section to TDs w3c/wot-thing-description#940 (9 comments by @Citrullin, @farshidtz, @mmccool)
-
Guarantee RDF round-tripping for security definitions w3c/wot-thing-description#1125 (7 comments by @mmccool)
-
Clarify expectations of writing a property w3c/wot-thing-description#1146 (6 comments by @benfrancis, @danielpeintner, @egekorkan, @relu91, @zolkis)
-
Publish updated WD for Thing Description 1.1 w3c/wot-thing-description#1127 (5 comments by @danielpeintner, @gatemezing, @KotisK, @mmccool, @sebastiankb)
-
Making the uriVariables recommendation paragraph an editor's note w3c/wot-thing-description#1138 (3 comments by @danielpeintner, @egekorkan)
-
Provide Typescript types definitions for Thing Descriptions w3c/wot-thing-description#1097 (3 comments by @danielpeintner, @egekorkan, @relu91)
-
JSON Schema validation issue wr.t. "format": "iri-reference" w3c/wot-thing-description#956 (3 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
Render script related issues w3c/wot-thing-description#973 (2 comments by @danielpeintner, @sebastiankb)
-
Comments - Call for Review of WoT Thing Description 1.1 specification and resolution to publish update w3c/wot-thing-description#1137 (2 comments by @danielpeintner, @sebastiankb)
-
[question] Why is title or description necessary when titles or descriptions are present? w3c/wot-thing-description#985 (2 comments by @Citrullin, @sebastiankb)
-
contentEncoding and contentMediaType should be moved under string schema w3c/wot-thing-description#1116 (2 comments by @handrews, @sebastiankb)
-
{{PLACEHOLDER_IDENTIFIER}} causes ReSpec rendering error w3c/wot-thing-description#1131 (1 comment by @sebastiankb)
-
Which is better to actuate devices, invoking ACTION or writing PROPERTY? w3c/wot-thing-description#1020 (1 comment by @sebastiankb)
-
Unsubscribing and unobserving are not in default values w3c/wot-thing-description#957 (1 comment by @egekorkan)
-
Add "multipleOf" term to NumberSchema and IntegerSchema w3c/wot-thing-description#841 (1 comment by @egekorkan)
-
Consumer should/must ignore unknown event types w3c/wot-thing-description#1134 (1 comment by @egekorkan)
-
Add 'minLength' and 'maxLength' to StringSchema w3c/wot-thing-description#889 (1 comment by @sebastiankb)
-
ThingTemplate definition is missing in td.ttl w3c/wot-thing-description#416 (1 comment by @sebastiankb)
-
Refer to developer documentation from a TD w3c/wot-thing-description#918 (1 comment by @sebastiankb)
-
Is there a way to set default values for uriVariables? w3c/wot-thing-description#1093 (1 comment by @sebastiankb)
-
How to extend Data Schema terms while being JSON Schema compliant w3c/wot-thing-description#1094 (1 comment by @sebastiankb)
-
jsonschema:StringSchema: pattern missing and maxLength is defined wrongly w3c/wot-thing-description#1101 (1 comment by @sebastiankb)
-
add a new vocabulary term "profile" with a String type w3c/wot-thing-description#806 (1 comment by @sebastiankb)
-
Remove Vocabulary and Vocabulary Term Terminology w3c/wot-thing-description#1118 (1 comment by @sebastiankb)
-
change ThingModel to tm:ThingModel and extend to tm:extend? w3c/wot-thing-description#1100 (1 comment by @sebastiankb)
-
-
15 pull requests opened.
-
WIP: TD Signatures w3c/wot-thing-description#1151, by @mmccool.
-
fix broken internal links w3c/wot-thing-description#1148, by @danielpeintner.
-
PR including the comments w3c/wot-thing-description#1147, by @sebastiankb.
-
Changelog for 2nd WD w3c/wot-thing-description#1145, by @takuki.
-
Changelog for 2nd WD w3c/wot-thing-description#1144, by @takuki.
-
Update abstract and introduction section w3c/wot-thing-description#1142, by @sebastiankb.
-
fix: tweak minor example bugs w3c/wot-thing-description#1136, by @danielpeintner.
-
fix: some typos and misspellings w3c/wot-thing-description#1133, by @danielpeintner.
-
fix: ReSpec rendering issue w3c/wot-thing-description#1132, by @danielpeintner.
-
Update AdditionalExpectedResponses with named data schemas w3c/wot-thing-description#1130, by @mmccool.
-
More fixes to canonicalization w3c/wot-thing-description#1129, by @mmccool.
-
Canonicalization improvements w3c/wot-thing-description#1124, by @mmccool.
-
Introduce TM namespace / ontology and some TM updates w3c/wot-thing-description#1123, by @sebastiankb.
-
Update terminology section w3c/wot-thing-description#1122, by @sebastiankb.
-
Introduce profile term into TD model w3c/wot-thing-description#1121, by @sebastiankb.
-
-
17 pull requests merged.
-
fix broken internal links w3c/wot-thing-description#1148.
-
Update AdditionalExpectedResponses with named data schemas w3c/wot-thing-description#1130.
-
PR including the comments w3c/wot-thing-description#1147.
-
Update abstract and introduction section w3c/wot-thing-description#1142.
-
Changelog for 2nd WD w3c/wot-thing-description#1145.
-
Changelog for 2nd WD w3c/wot-thing-description#1144.
-
fix: tweak minor example bugs w3c/wot-thing-description#1136.
-
fix: some typos and misspellings w3c/wot-thing-description#1133.
-
fix: ReSpec rendering issue w3c/wot-thing-description#1132.
-
Canonicalization improvements w3c/wot-thing-description#1124.
-
add tm:required and tm:ref generation w3c/wot-thing-description#1113.
-
Introduce TM namespace / ontology and some TM updates w3c/wot-thing-description#1123.
-
Update terminology section w3c/wot-thing-description#1122.
-
WIP: Add Validation Section w3c/wot-thing-description#1085.
-
Address multiple DataSchema issues w3c/wot-thing-description#1104.
-
Introduce profile term into TD model w3c/wot-thing-description#1121.
-
Add validation for icon links w3c/wot-thing-description#1120.
-
-
1 pull request closed.
-
WIP: Add proof and proofChain sections w3c/wot-thing-description#943.
-
-
20 pull requests received 82 new comments.
-
Update abstract and introduction section w3c/wot-thing-description#1142 (21 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
More fixes to canonicalization w3c/wot-thing-description#1129 (18 comments by @danielpeintner, @mmccool, @sebastiankb)
-
Update AdditionalExpectedResponses with named data schemas w3c/wot-thing-description#1130 (4 comments by @mmccool, @sebastiankb)
-
add tm:required and tm:ref generation w3c/wot-thing-description#1113 (4 comments by @egekorkan, @sebastiankb)
-
Extend JSON-LD context to allow for round-tripping to/from N-Triples w3c/wot-thing-description#1077 (3 comments by @vcharpenay)
-
Introduce profile term into TD model w3c/wot-thing-description#1121 (3 comments by @benfrancis, @danielpeintner, @sebastiankb)
-
fix: ReSpec rendering issue w3c/wot-thing-description#1132 (2 comments by @danielpeintner, @sebastiankb)
-
Introduce TM namespace / ontology and some TM updates w3c/wot-thing-description#1123 (1 comment by @sebastiankb)
-
WIP: swap securtiy and securityDefinition in context file w3c/wot-thing-description#937 (1 comment by @sebastiankb)
-
w3c/wot-profile
-
2 issues opened.
-
OAuth2 and SSE Notifications w3c/wot-profile#397, by @farshidtz.
-
Action - double check node-wot's error codes, are there error response payloads? w3c/wot-profile#80, by @danielpeintner.
-
-
2 issues received 3 new comments.
-
Action - double check node-wot's error codes, are there error response payloads? w3c/wot-profile#80 (2 comments by @zolkis)
-
-
2 pull requests merged.
-
New Protocol Binding section w3c/wot-profile#77.
-
carry over requirements to use cases TF w3c/wot-profile#72.
-
-
3 pull requests received 21 new comments.
-
New Profile Mechanism section w3c/wot-profile#79 (13 comments by @benfrancis, @mlagally, @sebastiankb)
-
New Protocol Binding section w3c/wot-profile#77 (5 comments by @benfrancis, @egekorkan, @mlagally, @sebastiankb)
-
w3c/wot-architecture
-
1 issue opened.
-
Clarify optionality discovery mechanisms in section 8.4 w3c/wot-architecture#591, by @mlagally.
-
-
1 issue closed.
-
Introduction for discovery section (9.4) w3c/wot-architecture#557.
-
-
1 pull request merged.
-
Add Discovery refs, dfn, and section w3c/wot-architecture#588.
-
-
1 pull request received 2 new comments.
w3c/wot-scripting-api
-
1 issue opened.
-
Directory - How to find things around me? w3c/wot-scripting-api#321, by @danielpeintner.
-
-
5 issues received 30 new comments.
-
Should writeProperty() return a value w3c/wot-scripting-api#193 (14 comments by @danielpeintner, @egekorkan, @relu91, @zolkis)
-
Discovery TaskForce related issues w3c/wot-scripting-api#314 (8 comments by @mmccool, @relu91, @zolkis)
-
Directory - How to find things around me? w3c/wot-scripting-api#321 (3 comments by @relu91, @zolkis)
-
w3c/wot-scripting-api#320 (1 comment by @danielpeintner)
-
-
2 pull requests opened.
-
Add a github action to automatically sync the json schema w3c/wot-scripting-api#319, by @relu91.
-
Introduce thing description type from json schema w3c/wot-scripting-api#318, by @relu91.
-
-
2 pull requests merged.
-
Add a github action to automatically sync the json schema w3c/wot-scripting-api#319.
-
Introduce thing description type from json schema w3c/wot-scripting-api#318.
-
-
2 pull requests received 8 new comments.
-
Add a github action to automatically sync the json schema w3c/wot-scripting-api#319 (5 comments by @danielpeintner, @relu91, @zolkis)
-
Introduce thing description type from json schema w3c/wot-scripting-api#318 (3 comments by @danielpeintner, @zolkis)
-
w3c/wot-binding-templates
-
1 pull request received 10 new comments.
-
Refining Modbus protocol binding w3c/wot-binding-templates#109 (10 comments by @relu91, @sebastiankb)
-
Participants
-
1 participant joined.
-
Konstantinos Kotis (W3C Invited Experts) joined.
-
-
4 participants left.
-
Ted Guild (W3C) left.
-
Toru Kawaguchi (Panasonic Corporation) left.
-
Michael Koster (SmartThings, Inc.) left.
-
Kazuo Kajimoto (Panasonic Corporation) left.
-
GitHub
w3c/wot-profile
-
3 issues opened.
-
Markup of normative requirements (RFC 2119) w3c/wot-profile#76, by @mlagally.
-
Implementation Report w3c/wot-profile#75, by @mlagally.
-
Highlighting assertions w3c/wot-profile#74, by @egekorkan.
-
-
3 issues received 8 new comments.
-
3 pull requests opened.
-
New Profile Mechanism section w3c/wot-profile#79, by @benfrancis.
-
Restructure WoT Core Profile section w3c/wot-profile#78, by @benfrancis.
-
New Protocol Binding section w3c/wot-profile#77, by @benfrancis.
-
-
4 pull requests received 28 new comments.
-
New Protocol Binding section w3c/wot-profile#77 (12 comments by @benfrancis, @danielpeintner, @egekorkan, @sebastiankb)
-
New Profile Mechanism section w3c/wot-profile#79 (10 comments by @benfrancis, @danielpeintner, @egekorkan, @sebastiankb)
-
Restructure WoT Core Profile section w3c/wot-profile#78 (5 comments by @benfrancis, @egekorkan, @mmccool, @sebastiankb)
-
w3c/wot-discovery
-
7 issues opened.
-
Add Ability to Retrieve Original TD w3c/wot-discovery#165, by @mmccool.
-
Consider adding "poll hook" to registration (pull keepalive) w3c/wot-discovery#164, by @mmccool.
-
Better explain HTTP focus w3c/wot-discovery#157, by @mmccool.
-
JSONPath response data model w3c/wot-discovery#156, by @farshidtz.
-
Publish updated WD w3c/wot-discovery#154, by @mmccool.
-
Definition of Problem Details error types w3c/wot-discovery#150, by @farshidtz.
-
Anonymous TDs in a directory w3c/wot-discovery#149, by @farshidtz.
-
-
2 issues closed.
-
Richer diff model for update notifications w3c/wot-discovery#87.
-
Discussion about PR 124 w3c/wot-discovery#125.
-
-
10 issues received 31 new comments.
-
Anonymous TDs in a directory w3c/wot-discovery#149 (12 comments by @AndreaCimminoArriaga, @benfrancis, @egekorkan, @farshidtz, @mmccool, @vcharpenay)
-
Consider adding "poll hook" to registration (pull keepalive) w3c/wot-discovery#164 (1 comment by @farshidtz)
-
Should Directories store TD Models as well as Instances? w3c/wot-discovery#58 (1 comment by @mmccool)
-
-
11 pull requests opened.
-
Typos against main w3c/wot-discovery#166, by @danielpeintner.
-
Add pagination references and improve anonymous TD definition w3c/wot-discovery#163, by @farshidtz.
-
Expiry date for registered TDs w3c/wot-discovery#162, by @farshidtz.
-
Rename DirectoryDescription to ThingDirectory w3c/wot-discovery#161, by @benfrancis.
-
Rename actions to match properties and events w3c/wot-discovery#160, by @benfrancis.
-
Split registration event into multiple events w3c/wot-discovery#159, by @benfrancis.
-
Combine properties into a single things property w3c/wot-discovery#158, by @benfrancis.
-
Simplifying the events API query and payload w3c/wot-discovery#155, by @farshidtz.
-
Listing with pagination w3c/wot-discovery#153, by @farshidtz.
-
Add Registration ID to Enriched TD w3c/wot-discovery#152, by @farshidtz.
-
HTML formatting and editorial notes w3c/wot-discovery#151, by @farshidtz.
-
-
5 pull requests merged.
-
Add pagination references and improve anonymous TD definition w3c/wot-discovery#163.
-
Simplifying the events API query and payload w3c/wot-discovery#155.
-
Listing with pagination w3c/wot-discovery#153.
-
Add Registration ID to Enriched TD w3c/wot-discovery#152.
-
HTML formatting and editorial notes w3c/wot-discovery#151.
-
-
9 pull requests received 44 new comments.
-
Listing with pagination w3c/wot-discovery#153 (8 comments by @egekorkan, @farshidtz, @sebastiankb, @wiresio)
-
Add pagination references and improve anonymous TD definition w3c/wot-discovery#163 (5 comments by @mmccool)
-
Rename DirectoryDescription to ThingDirectory w3c/wot-discovery#161 (4 comments by @benfrancis, @farshidtz, @mmccool)
-
Simplifying the events API query and payload w3c/wot-discovery#155 (2 comments by @farshidtz, @mmccool)
-
Improvements to paginated TD retrieval spec w3c/wot-discovery#130 (2 comments by @farshidtz, @sebastiankb)
w3c/wot-security-best-practices
-
1 pull request opened.
-
Move oAuth2 flow from usecases to security-best-practices w3c/wot-security-best-practices#10, by @Citrullin.
-
-
1 pull request merged.
-
doc: Link to published HTML file w3c/wot-security-best-practices#4.
-
-
1 pull request received 9 new comments.
-
Move oAuth2 flow from usecases to security-best-practices w3c/wot-security-best-practices#10 (9 comments by @mmccool, @relu91)
-
w3c/wot-thing-description
-
19 issues opened.
-
Alignment with JSON Schema Draft v7 w3c/wot-thing-description#1119, by @egekorkan.
-
Remove Vocabulary and Vocabulary Term Terminology w3c/wot-thing-description#1118, by @sebastiankb.
-
Canonical dates and times w3c/wot-thing-description#1117, by @danielpeintner.
-
contentEncoding and contentMediaType should be moved under string schema w3c/wot-thing-description#1116, by @egekorkan.
-
const appears twice under DataSchema w3c/wot-thing-description#1115, by @egekorkan.
-
format is listed under DataSchema w3c/wot-thing-description#1114, by @egekorkan.
-
Identify Canonical TD w3c/wot-thing-description#1107, by @mmccool.
-
Canonical examples missing some elements w3c/wot-thing-description#1106, by @mmccool.
-
Canonical form: dateTime ambiguities w3c/wot-thing-description#1105, by @mmccool.
-
jsonschema:StringSchema: pattern missing and maxLength is defined wrongly w3c/wot-thing-description#1101, by @fennibay.
-
change ThingModel to tm:ThingModel and extend to tm:extend? w3c/wot-thing-description#1100, by @sebastiankb.
-
Provide Typescript types definitions for Thing Descriptions w3c/wot-thing-description#1097, by @relu91.
-
Adding Editor's Note for body location in security w3c/wot-thing-description#1096, by @egekorkan.
-
How to extend Data Schema terms while being JSON Schema compliant w3c/wot-thing-description#1094, by @egekorkan.
-
Is there a way to set default values for uriVariables? w3c/wot-thing-description#1093, by @farshidtz.
-
Missing top-level "base" field in TD 1.1. w3c/wot-thing-description#1091, by @farshidtz.
-
Fix default op values for Example 44 (used to be 42) w3c/wot-thing-description#1089, by @danielpeintner.
-
Why is the "template for Thing Descriptions" called a Thing Model? w3c/wot-thing-description#1088, by @farshidtz.
-
"Previous version" link not available anymore w3c/wot-thing-description#1087, by @egekorkan.
-
-
16 issues closed.
-
Two step generation of the TD from a TM should be clear w3c/wot-thing-description#1047.
-
Array definitions in Hypermedia Controls Vocabulary Definitions w3c/wot-thing-description#1048.
-
Missing Thing securityDefinitions in TD 1.1 w3c/wot-thing-description#1069.
-
Missing top-level "base" field in TD 1.1. w3c/wot-thing-description#1091.
-
Move terminology definitions to architecture w3c/wot-thing-description#1072.
-
Allow a webthing to provide an icon w3c/wot-thing-description#1063.
-
No mechanism to indicate the "desired" form entry w3c/wot-thing-description#877.
-
Canonical form: dateTime ambiguities w3c/wot-thing-description#1105.
-
Canonical examples missing some elements w3c/wot-thing-description#1106.
-
Fix default op values for Example 44 (used to be 42) w3c/wot-thing-description#1089.
-
Multiple OAuth 2.0 flows in security definitions w3c/wot-thing-description#929.
-
Why is the "template for Thing Descriptions" called a Thing Model? w3c/wot-thing-description#1088.
-
The term required in Thing Model is confusing w3c/wot-thing-description#1046.
-
Introduce tmRef for TM w3c/wot-thing-description#1081.
-
The "body" location value for security schemes is underspecified w3c/wot-thing-description#1037.
-
extend op options with observeallproperties and observemultipleproperties w3c/wot-thing-description#800.
-
-
38 issues received 102 new comments.
-
jsonschema:StringSchema: pattern missing and maxLength is defined wrongly w3c/wot-thing-description#1101 (9 comments by @danielpeintner, @egekorkan, @fennibay, @sebastiankb)
-
Fix default op values for Example 44 (used to be 42) w3c/wot-thing-description#1089 (9 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
Identify Canonical TD w3c/wot-thing-description#1107 (8 comments by @danielpeintner, @egekorkan, @mmccool, @relu91, @sebastiankb)
-
Canonical form: dateTime ambiguities w3c/wot-thing-description#1105 (7 comments by @danielpeintner, @mmccool)
-
[question] Why is title or description necessary when titles or descriptions are present? w3c/wot-thing-description#985 (5 comments by @benfrancis, @egekorkan, @sebastiankb)
-
Missing Thing securityDefinitions in TD 1.1 w3c/wot-thing-description#1069 (4 comments by @farshidtz, @mmccool, @sebastiankb)
-
`observeallproperties` and `unobserveallproperties` clarification w3c/wot-thing-description#1084 (4 comments by @benfrancis, @danielpeintner, @egekorkan, @sebastiankb)
-
How to extend Data Schema terms while being JSON Schema compliant w3c/wot-thing-description#1094 (4 comments by @egekorkan, @fennibay, @sebastiankb)
-
Why is the "template for Thing Descriptions" called a Thing Model? w3c/wot-thing-description#1088 (4 comments by @benfrancis, @farshidtz, @sebastiankb)
-
Is there a way to set default values for uriVariables? w3c/wot-thing-description#1093 (4 comments by @egekorkan, @farshidtz, @sebastiankb)
-
Allow more operations in a top level form w3c/wot-thing-description#1070 (4 comments by @benfrancis, @egekorkan, @relu91)
-
uriVariables with multiple forms w3c/wot-thing-description#1083 (4 comments by @benfrancis, @egekorkan, @mmccool)
-
[vocabulary] Consider adding keyword to describe synchronous actions w3c/wot-thing-description#890 (3 comments by @egekorkan, @sebastiankb)
-
Thing Models vs. Capability Schemas w3c/wot-thing-description#1078 (3 comments by @benfrancis, @egekorkan)
-
contentEncoding and contentMediaType should be moved under string schema w3c/wot-thing-description#1116 (2 comments by @danielpeintner, @relu91)
-
No mechanism to indicate the "desired" form entry w3c/wot-thing-description#877 (2 comments by @sebastiankb)
-
Adding Editor's Note for body location in security w3c/wot-thing-description#1096 (2 comments by @egekorkan, @mmccool)
-
The "proxy-to" relation type overlaps "proxy" in security schemes w3c/wot-thing-description#1075 (2 comments by @egekorkan, @mmccool)
-
Provide Typescript types definitions for Thing Descriptions w3c/wot-thing-description#1097 (1 comment by @relu91)
-
Two step generation of the TD from a TM should be clear w3c/wot-thing-description#1047 (1 comment by @sebastiankb)
-
Array definitions in Hypermedia Controls Vocabulary Definitions w3c/wot-thing-description#1048 (1 comment by @sebastiankb)
-
Missing top-level "base" field in TD 1.1. w3c/wot-thing-description#1091 (1 comment by @sebastiankb)
-
Move terminology definitions to architecture w3c/wot-thing-description#1072 (1 comment by @sebastiankb)
-
Multiple OAuth 2.0 flows in security definitions w3c/wot-thing-description#929 (1 comment by @farshidtz)
-
Suggestion for change in upcoming release - Update link for JSON LD 1.1 w3c/wot-thing-description#1066 (1 comment by @sebastiankb)
-
The term required in Thing Model is confusing w3c/wot-thing-description#1046 (1 comment by @sebastiankb)
-
extend op options with observeallproperties and observemultipleproperties w3c/wot-thing-description#800 (1 comment by @sebastiankb)
-
Need Fragment Identifier IANA registration for application/td+json w3c/wot-thing-description#1064 (1 comment by @mmccool)
-
Consider adding DataSchema to response and additionalResponses w3c/wot-thing-description#1053 (1 comment by @mmccool)
-
-
17 pull requests opened.
-
Add validation for icon links w3c/wot-thing-description#1120, by @relu91.
-
add tm:required and tm:ref generation w3c/wot-thing-description#1113, by @egekorkan.
-
Adding `tm:ref` and `tm:required` to tm schema generation w3c/wot-thing-description#1112, by @egekorkan.
-
Add fracsec rule to dateTime in Canonical TD w3c/wot-thing-description#1111, by @mmccool.
-
Add contentType default to canonicalization examples w3c/wot-thing-description#1110, by @mmccool.
-
restrict more uri variables w3c/wot-thing-description#1109, by @sebastiankb.
-
consumer forms selection w3c/wot-thing-description#1108, by @sebastiankb.
-
Address multiple DataSchema issues w3c/wot-thing-description#1104, by @sebastiankb.
-
Introduce Thing Icon w3c/wot-thing-description#1103, by @sebastiankb.
-
Update Terminology Section w3c/wot-thing-description#1102, by @sebastiankb.
-
fix: default op values for HTTP w3c/wot-thing-description#1099, by @danielpeintner.
-
Fix multiple TD model definitions w3c/wot-thing-description#1098, by @sebastiankb.
-
Two step generation of the TD from a TM w3c/wot-thing-description#1095, by @relu91.
-
rename required to tmRequired + top level definition w3c/wot-thing-description#1092, by @sebastiankb.
-
init tmRef w3c/wot-thing-description#1090, by @sebastiankb.
-
Add section to define Canonical serialization w3c/wot-thing-description#1086, by @mmccool.
-
WIP: Add Validation Section w3c/wot-thing-description#1085, by @mmccool.
-
-
13 pull requests merged.
-
Add fracsec rule to dateTime in Canonical TD w3c/wot-thing-description#1111.
-
Add contentType default to canonicalization examples w3c/wot-thing-description#1110.
-
restrict more uri variables w3c/wot-thing-description#1109.
-
consumer forms selection w3c/wot-thing-description#1108.
-
Introduce Thing Icon w3c/wot-thing-description#1103.
-
Update Terminology Section w3c/wot-thing-description#1102.
-
fix: default op values for HTTP w3c/wot-thing-description#1099.
-
Fix multiple TD model definitions w3c/wot-thing-description#1098.
-
Two step generation of the TD from a TM w3c/wot-thing-description#1095.
-
Add section to define Canonical serialization w3c/wot-thing-description#1086.
-
rename required to tmRequired + top level definition w3c/wot-thing-description#1092.
-
init tmRef w3c/wot-thing-description#1090.
-
Add JSON pointer assertion to definition of body sec location w3c/wot-thing-description#1058.
-
-
3 pull requests closed.
-
WIP: Fix cardinality of Link.rel w3c/wot-thing-description#1061.
-
Adding `tm:ref` and `tm:required` to tm schema generation w3c/wot-thing-description#1112.
-
fix: the "required" keyword was placed incorrectly in the TM schema w3c/wot-thing-description#1065.
-
-
20 pull requests received 102 new comments.
-
Add section to define Canonical serialization w3c/wot-thing-description#1086 (45 comments by @danielpeintner, @egekorkan, @farshidtz, @mmccool, @sebastiankb)
-
consumer forms selection w3c/wot-thing-description#1108 (15 comments by @egekorkan, @relu91, @sebastiankb, @zolkis)
-
rename required to tmRequired + top level definition w3c/wot-thing-description#1092 (6 comments by @egekorkan, @relu91, @sebastiankb)
-
restrict more uri variables w3c/wot-thing-description#1109 (5 comments by @egekorkan, @relu91, @sebastiankb)
-
WIP: Add Validation Section w3c/wot-thing-description#1085 (5 comments by @egekorkan, @mmccool, @sebastiankb)
-
add tm:required and tm:ref generation w3c/wot-thing-description#1113 (3 comments by @egekorkan, @sebastiankb)
-
Address multiple DataSchema issues w3c/wot-thing-description#1104 (3 comments by @egekorkan, @sebastiankb)
-
Two step generation of the TD from a TM w3c/wot-thing-description#1095 (3 comments by @relu91, @sebastiankb)
-
fix: the "required" keyword was placed incorrectly in the TM schema w3c/wot-thing-description#1065 (2 comments by @sebastiankb)
-
Add fracsec rule to dateTime in Canonical TD w3c/wot-thing-description#1111 (1 comment by @sebastiankb)
-
Add contentType default to canonicalization examples w3c/wot-thing-description#1110 (1 comment by @sebastiankb)
-
Extend JSON-LD context to allow for round-tripping to/from N-Triples w3c/wot-thing-description#1077 (1 comment by @sebastiankb)
-
Adding `tm:ref` and `tm:required` to tm schema generation w3c/wot-thing-description#1112 (1 comment by @egekorkan)
-
Add JSON pointer assertion to definition of body sec location w3c/wot-thing-description#1058 (1 comment by @sebastiankb)
-
w3c/wot-architecture
-
1 issue opened.
-
Implementation report w3c/wot-architecture#589, by @mlagally.
-
-
3 issues received 3 new comments.
-
New section on Security and Privacy considerations on Discovery w3c/wot-architecture#587 (1 comment by @mmccool)
-
1 pull request opened.
-
Move Partial TD definition to right place in list w3c/wot-architecture#590, by @danielpeintner.
-
-
2 pull requests merged.
-
Add terminology from binding templates w3c/wot-architecture#586.
-
Move Partial TD definition to right place in list w3c/wot-architecture#590.
-
-
1 pull request closed.
-
WIP: Terminology update w3c/wot-architecture#582.
-
-
3 pull requests received 3 new comments.
w3c/wot-scripting-api
-
4 issues opened.
-
Support Syntactic Queries in Body w3c/wot-scripting-api#317, by @mmccool.
-
Security TaskForce related issues w3c/wot-scripting-api#315, by @danielpeintner.
-
Discovery TaskForce related issues w3c/wot-scripting-api#314, by @danielpeintner.
-
ThingDescription TaskForce related issues w3c/wot-scripting-api#313, by @danielpeintner.
-
-
1 issue closed.
-
Simplify discovery methods w3c/wot-scripting-api#311.
-
-
1 issue reopened.
-
Should writeProperty() return a value w3c/wot-scripting-api#193, by @danielpeintner.
-
-
8 issues received 23 new comments.
-
Chose a particular security schema for an ExposedThing w3c/wot-scripting-api#299 (8 comments by @relu91, @zolkis)
-
Requirements for Managment APIs w3c/wot-scripting-api#298 (4 comments by @danielpeintner, @egekorkan, @relu91, @zolkis)
-
`observeallproperties` and `unobserveallproperties` methods are missing w3c/wot-scripting-api#312 (4 comments by @egekorkan, @zolkis)
-
Security TaskForce related issues w3c/wot-scripting-api#315 (2 comments by @danielpeintner, @relu91)
-
-
1 pull request opened.
-
Simplify discovery methods. Update examples. w3c/wot-scripting-api#316, by @zolkis.
-
-
1 pull request merged.
-
Simplify discovery methods. Update examples. w3c/wot-scripting-api#316.
-
-
1 pull request received 6 new comments.
-
Simplify discovery methods. Update examples. w3c/wot-scripting-api#316 (6 comments by @danielpeintner, @relu91, @zolkis)
-
w3c/wot-binding-templates
-
1 issue received 5 new comments.
-
1 pull request merged.
-
remove terminology since it is moving to architecture w3c/wot-binding-templates#112.
-
-
1 pull request received 1 new comment.
-
remove terminology since it is moving to architecture w3c/wot-binding-templates#112 (1 comment by @sebastiankb)
-
w3c/wot-security
-
1 issue opened.
-
Move away from rawgit w3c/wot-security#200, by @Citrullin.
-
-
3 issues received 10 new comments.
-
Update security and privacy considerations in Discovery w3c/wot-security#196 (3 comments by @mmccool)
Participants
-
2 participants joined.
-
Yoshiaki Fukami (Data Society Alliance) joined.
-
Jens Schimmelpfennig (Software AG) joined.
-
-
2 participants left.
-
Pekka Nikander (Aalto University) left.
-
Prasad Yendluri (Software AG) left.
-
GitHub
w3c/wot-scripting-api
-
4 issues opened.
-
`observeallproperties` and `unobserveallproperties` methods are missing w3c/wot-scripting-api#312, by @egekorkan.
-
Simplify discovery methods w3c/wot-scripting-api#311, by @zolkis.
-
Handling pagination w3c/wot-scripting-api#310, by @relu91.
-
Handle ThingDescriptions as streams w3c/wot-scripting-api#309, by @relu91.
-
-
5 issues closed.
-
Produce() method should ignore instance specific information w3c/wot-scripting-api#156.
-
ActionHandler returning InteractionInput always w3c/wot-scripting-api#302.
-
DataSchemaValue in TS should not be any w3c/wot-scripting-api#296.
-
Does PropertyMap need to be different for reading and writing a value? w3c/wot-scripting-api#293.
-
Feedback about InteractionOuput w3c/wot-scripting-api#306.
-
-
15 issues received 58 new comments.
-
Produce ExposedThing from a ThingModel instance w3c/wot-scripting-api#304 (17 comments by @danielpeintner, @relu91, @zolkis)
-
Should writeProperty() return a value w3c/wot-scripting-api#193 (8 comments by @egekorkan, @relu91, @zolkis)
-
`observeallproperties` and `unobserveallproperties` methods are missing w3c/wot-scripting-api#312 (5 comments by @danielpeintner, @egekorkan, @relu91, @zolkis)
-
Event Affordance subscription and cancellation payloads are not usable by scripting w3c/wot-scripting-api#208 (4 comments by @relu91, @zolkis)
-
Link the API specification to the Thing Description version w3c/wot-scripting-api#225 (3 comments by @danielpeintner, @relu91, @zolkis)
-
ActionHandler returning InteractionInput always w3c/wot-scripting-api#302 (3 comments by @danielpeintner, @relu91)
-
Does PropertyMap need to be different for reading and writing a value? w3c/wot-scripting-api#293 (3 comments by @relu91, @zolkis)
-
Feedback about InteractionOuput w3c/wot-scripting-api#306 (3 comments by @danielpeintner, @relu91, @zolkis)
-
Produce() method should ignore instance specific information w3c/wot-scripting-api#156 (1 comment by @relu91)
-
Partial TD validation for input of produce() method w3c/wot-scripting-api#212 (1 comment by @relu91)
-
-
2 pull requests opened.
-
Introduce PropertyReadMap and PropertyWriteMap in TS w3c/wot-scripting-api#308, by @relu91.
-
-
3 pull requests merged.
-
Introduce PropertyReadMap and PropertyWriteMap in TS w3c/wot-scripting-api#308.
-
fix 302 w3c/wot-scripting-api#307.
-
Factor out maplike interfaces property reads and writes w3c/wot-scripting-api#305.
-
-
3 pull requests received 11 new comments.
-
Factor out maplike interfaces property reads and writes w3c/wot-scripting-api#305 (7 comments by @danielpeintner, @relu91, @zolkis)
-
Introduce PropertyReadMap and PropertyWriteMap in TS w3c/wot-scripting-api#308 (3 comments by @danielpeintner, @relu91)
-
w3c/wot-discovery
-
15 issues opened.
-
Discovery context and namespace under w3.org/ns w3c/wot-discovery#148, by @farshidtz.
-
Add reference to Discovery paper by Arne Broering, Soumya Kanti Datta, and Christian Bonnet w3c/wot-discovery#147, by @mmccool.
-
Method to query content length before exploration w3c/wot-discovery#146, by @farshidtz.
-
Which aspects of the Directory Service API's TD are normative? w3c/wot-discovery#144, by @benfrancis.
-
SHACL validation w3c/wot-discovery#143, by @mmccool.
-
some class names in TD ontology do not match names in TD w3c/wot-discovery#142, by @mmccool.
-
Add query examples to spec w3c/wot-discovery#141, by @mmccool.
-
Allow Directory to return just a link w3c/wot-discovery#140, by @mmccool.
-
Allow plain HTTP in some cases w3c/wot-discovery#139, by @mmccool.
-
Security bootstrapping during discovery w3c/wot-discovery#135, by @benfrancis.
-
Discovery using MQTT? w3c/wot-discovery#134, by @JKRhb.
-
Refactoring TDD Thing Description w3c/wot-discovery#133, by @relu91.
-
Peer-to-Peer Queries Endpoint in Producers w3c/wot-discovery#132, by @mmccool.
-
Review IETF JSON Path draft w3c/wot-discovery#129, by @mmccool.
-
Discussion about PR 124 w3c/wot-discovery#125, by @wiresio.
-
-
1 issue closed.
-
Define error responses w3c/wot-discovery#44.
-
-
1 issue reopened.
-
Define the WoT-Directory type somewhere (eg in new version of context, in 1.1) w3c/wot-discovery#43, by @farshidtz.
-
-
25 issues received 100 new comments.
-
Refactoring TDD Thing Description w3c/wot-discovery#133 (29 comments by @benfrancis, @farshidtz, @relu91)
-
Security bootstrapping during discovery w3c/wot-discovery#135 (11 comments by @benfrancis, @farshidtz, @mjkoster, @mmccool, @relu91)
-
Which aspects of the Directory Service API's TD are normative? w3c/wot-discovery#144 (6 comments by @benfrancis, @farshidtz, @mmccool)
-
Incremental TDs provided by constrained devices w3c/wot-discovery#117 (5 comments by @benfrancis, @farshidtz, @mmccool)
-
Discussion about PR 124 w3c/wot-discovery#125 (5 comments by @AndreaCimminoArriaga, @farshidtz, @relu91, @wiresio)
-
Define the WoT-Directory type somewhere (eg in new version of context, in 1.1) w3c/wot-discovery#43 (4 comments by @AndreaCimminoArriaga, @benfrancis, @farshidtz)
-
Directories should notify subscribers when a TD is updated w3c/wot-discovery#28 (4 comments by @benfrancis, @farshidtz)
-
Handle huge set of Thing Descriptions (pagination, streaming, etc.) w3c/wot-discovery#16 (3 comments by @AndreaCimminoArriaga, @farshidtz)
-
A recommended approach to discovery of a gateway/intermediary w3c/wot-discovery#122 (3 comments by @farshidtz, @hspaay)
-
Define requirements and add section for validation w3c/wot-discovery#99 (2 comments by @AndreaCimminoArriaga, @farshidtz)
-
Should security be mandatory on directories for WoT Discovery? w3c/wot-discovery#96 (2 comments by @benfrancis, @mmccool)
-
some class names in TD ontology do not match names in TD w3c/wot-discovery#142 (1 comment by @mmccool)
-
Need to define the discovery types and vocabulary w3c/wot-discovery#54 (1 comment by @AndreaCimminoArriaga)
-
Should Directories store TD Models as well as Instances? w3c/wot-discovery#58 (1 comment by @relu91)
-
-
9 pull requests opened.
-
Listing with chunked transfer w3c/wot-discovery#145, by @farshidtz.
-
Improve directory intro w3c/wot-discovery#138, by @farshidtz.
-
Update jsonpath draft URL and date w3c/wot-discovery#137, by @farshidtz.
-
Validation error example w3c/wot-discovery#136, by @farshidtz.
-
Specify additional responses w3c/wot-discovery#131, by @farshidtz.
-
Improvements to paginated TD retrieval spec w3c/wot-discovery#130, by @farshidtz.
-
updates to geolocation proposal w3c/wot-discovery#128, by @mmccool.
-
Updated ontology source code, diagrams, and spec text w3c/wot-discovery#127, by @AndreaCimminoArriaga.
-
Uploading ontology source code and proposal text w3c/wot-discovery#126, by @AndreaCimminoArriaga.
-
-
9 pull requests merged.
-
Listing with chunked transfer w3c/wot-discovery#145.
-
Improve directory intro w3c/wot-discovery#138.
-
Update jsonpath draft URL and date w3c/wot-discovery#137.
-
Validation error example w3c/wot-discovery#136.
-
Specify additional responses w3c/wot-discovery#131.
-
updates to geolocation proposal w3c/wot-discovery#128.
-
Updated ontology source code, diagrams, and spec text w3c/wot-discovery#127.
-
Editorial fix: TDD and TTL note w3c/wot-discovery#123.
-
Registration spec: listing w3c/wot-discovery#124.
-
-
2 pull requests closed.
-
Improvements to paginated TD retrieval spec w3c/wot-discovery#130.
-
Uploading ontology source code and proposal text w3c/wot-discovery#126.
-
-
6 pull requests received 67 new comments.
-
Listing with chunked transfer w3c/wot-discovery#145 (36 comments by @benfrancis, @farshidtz, @mmccool, @relu91, @wiresio)
-
Updated ontology source code, diagrams, and spec text w3c/wot-discovery#127 (12 comments by @AndreaCimminoArriaga, @farshidtz)
-
Improvements to paginated TD retrieval spec w3c/wot-discovery#130 (7 comments by @AndreaCimminoArriaga, @danielpeintner, @farshidtz, @mmccool)
-
w3c/wot-thing-description
-
18 issues opened.
-
`observeallproperties` and `unobserveallproperties` clarification w3c/wot-thing-description#1084, by @egekorkan.
-
uriVariables with multiple forms w3c/wot-thing-description#1083, by @relu91.
-
Add `subscribeallevents` and `unsubscribeallevents` operations w3c/wot-thing-description#1082, by @benfrancis.
-
Introduce tmRef for TM w3c/wot-thing-description#1081, by @sebastiankb.
-
Replace required with tmRequired for TM w3c/wot-thing-description#1080, by @sebastiankb.
-
How to differentiate between sensor, actuator, status, configuration properties? w3c/wot-thing-description#1079, by @hspaay.
-
Thing Models vs. Capability Schemas w3c/wot-thing-description#1078, by @benfrancis.
-
What is the intended use of the manifest link relation? w3c/wot-thing-description#1076, by @benfrancis.
-
The "proxy-to" relation type overlaps "proxy" in security schemes w3c/wot-thing-description#1075, by @mmccool.
-
An explainer table for the operation values is missing w3c/wot-thing-description#1074, by @egekorkan.
-
No default HTTP binding for default event operations w3c/wot-thing-description#1073, by @benfrancis.
-
Move terminology definitions to architecture w3c/wot-thing-description#1072, by @mlagally.
-
Modeling relations among InteractionAffordances w3c/wot-thing-description#1071, by @fennibay.
-
Allow more operations in a top level form w3c/wot-thing-description#1070, by @benfrancis.
-
Missing Thing securityDefinitions in TD 1.1 w3c/wot-thing-description#1069, by @farshidtz.
-
uriVariables needs to be more limited w3c/wot-thing-description#1068, by @sebastiankb.
-
Suggestion for change in upcoming release - Update link for JSON LD 1.1 w3c/wot-thing-description#1066, by @GeorgFerdinandSchneider.
-
Need Fragment Identifier IANA registration for application/td+json w3c/wot-thing-description#1064, by @mmccool.
-
-
2 issues closed.
-
No default HTTP binding for default event operations w3c/wot-thing-description#1073.
-
Definition of contentEncoding should be of type xsd:string w3c/wot-thing-description#980.
-
-
30 issues received 95 new comments.
-
How to differentiate between sensor, actuator, status, configuration properties? w3c/wot-thing-description#1079 (14 comments by @benfrancis, @egekorkan, @hspaay, @relu91, @sebastiankb)
-
Allow more operations in a top level form w3c/wot-thing-description#1070 (9 comments by @benfrancis, @egekorkan, @hspaay, @relu91)
-
HTTP Binding for providing historical events. w3c/wot-thing-description#892 (8 comments by @benfrancis, @egekorkan, @relu91, @zolkis)
-
Consider adding DataSchema to response and additionalResponses w3c/wot-thing-description#1053 (8 comments by @egekorkan, @farshidtz, @mjkoster, @relu91, @sebastiankb)
-
Add `subscribeallevents` and `unsubscribeallevents` operations w3c/wot-thing-description#1082 (6 comments by @benfrancis, @egekorkan, @relu91)
-
uriVariables needs to be more limited w3c/wot-thing-description#1068 (5 comments by @egekorkan, @relu91)
-
uriVariables with multiple forms w3c/wot-thing-description#1083 (4 comments by @benfrancis, @egekorkan, @relu91)
-
How do you cancel or query the state of an action request? w3c/wot-thing-description#302 (4 comments by @benfrancis, @egekorkan, @sebastiankb)
-
Allow "security" to include both SecurityScheme objects and declared identifiers w3c/wot-thing-description#300 (4 comments by @benfrancis, @mmccool)
-
Problems translating TDs from JSON-LD 1.1 to RDF and back w3c/wot-thing-description#1015 (4 comments by @AndreaCimminoArriaga, @vcharpenay, @wiresio)
-
Thing Models vs. Capability Schemas w3c/wot-thing-description#1078 (2 comments by @benfrancis, @sebastiankb)
-
Need Fragment Identifier IANA registration for application/td+json w3c/wot-thing-description#1064 (2 comments by @mmccool, @sebastiankb)
-
Allow a webthing to provide an icon w3c/wot-thing-description#1063 (2 comments by @benfrancis, @relu91)
-
What is the intended use of the manifest link relation? w3c/wot-thing-description#1076 (1 comment by @danielpeintner)
-
Consider adding "components" to TD ontology w3c/wot-thing-description#490 (1 comment by @sebastiankb)
-
Is the use of "$ref" and "definitions" allowed in TD ? w3c/wot-thing-description#307 (1 comment by @sebastiankb)
-
An explainer table for the operation values is missing w3c/wot-thing-description#1074 (1 comment by @sebastiankb)
-
No default HTTP binding for default event operations w3c/wot-thing-description#1073 (1 comment by @benfrancis)
-
Allowing overwriting number types and its impact. w3c/wot-thing-description#1054 (1 comment by @sebastiankb)
-
Missing Thing securityDefinitions in TD 1.1 w3c/wot-thing-description#1069 (1 comment by @sebastiankb)
-
Modeling relations among InteractionAffordances w3c/wot-thing-description#1071 (1 comment by @vcharpenay)
-
Which is better to actuate devices, invoking ACTION or writing PROPERTY? w3c/wot-thing-description#1020 (1 comment by @relu91)
-
Two step generation of the TD from a TM should be clear w3c/wot-thing-description#1047 (1 comment by @sebastiankb)
-
Definition of contentEncoding should be of type xsd:string w3c/wot-thing-description#980 (1 comment by @sebastiankb)
-
-
3 pull requests opened.
-
Extend JSON-LD context to allow for round-tripping to/from N-Triples w3c/wot-thing-description#1077, by @vcharpenay.
-
Label test w3c/wot-thing-description#1067, by @egekorkan.
-
fix: the "required" keyword was placed incorrectly in the TM schema w3c/wot-thing-description#1065, by @spf00.
-
-
1 pull request merged.
-
fix issue #980 w3c/wot-thing-description#1060.
-
-
1 pull request closed.
-
Label test w3c/wot-thing-description#1067.
-
-
1 pull request reopened.
-
fix: the "required" keyword was placed incorrectly in the TM schema w3c/wot-thing-description#1065, by @egekorkan.
-
-
6 pull requests received 19 new comments.
-
Add JSON pointer assertion to definition of body sec location w3c/wot-thing-description#1058 (11 comments by @mmccool)
-
fix: the "required" keyword was placed incorrectly in the TM schema w3c/wot-thing-description#1065 (3 comments by @egekorkan, @sebastiankb)
-
WIP: swap securtiy and securityDefinition in context file w3c/wot-thing-description#937 (2 comments by @mmccool)
-
w3c/wot-architecture
-
3 issues opened.
-
New section on Security and Privacy considerations on Discovery w3c/wot-architecture#587, by @mlagally.
-
Architectural patterns: Introduce star(hub) vs. p2p section w3c/wot-architecture#585, by @mlagally.
-
Acknowledge additional contributors w3c/wot-architecture#584, by @mlagally.
-
-
1 issue closed.
-
Terminology: thing description fragments w3c/wot-architecture#574.
-
-
4 pull requests opened.
-
Add Discovery refs, dfn, and section w3c/wot-architecture#588, by @mmccool.
-
Add terminology from binding templates w3c/wot-architecture#586, by @egekorkan.
-
fix a typo w3c/wot-architecture#583, by @jamespullen.
-
WIP: Terminology update w3c/wot-architecture#582, by @mmccool.
-
-
1 pull request merged.
-
fix a typo w3c/wot-architecture#583.
-
-
2 pull requests received 6 new comments.
w3c/wot-profile
-
2 issues opened.
-
Refine Goals and Scope w3c/wot-profile#73, by @mmccool.
-
Collect Use Cases and Scenarios for Profiles w3c/wot-profile#71, by @mmccool.
-
-
4 issues received 29 new comments.
-
Refine Goals and Scope w3c/wot-profile#73 (21 comments by @benfrancis, @egekorkan, @mlagally, @mmccool, @relu91, @sebastiankb)
-
Collect Use Cases and Scenarios for Profiles w3c/wot-profile#71 (4 comments by @benfrancis, @egekorkan, @mlagally, @sebastiankb)
-
-
1 pull request opened.
-
carry over requirements to use cases TF w3c/wot-profile#72, by @mlagally.
-
-
1 pull request received 5 new comments.
w3c/wot-binding-templates
-
1 pull request opened.
-
remove terminology since it is moving to architecture w3c/wot-binding-templates#112, by @egekorkan.
-
-
1 pull request received 2 new comments.
w3c/wot-security
-
2 issues received 3 new comments.
-
Promoting an approach where every thing is a server is a security nightmare w3c/wot-security#197 (2 comments by @hspaay, @mmccool)
-
Update security and privacy considerations in Discovery w3c/wot-security#196 (1 comment by @mmccool)
-
w3c/wot-security-best-practices
-
2 issues opened.
-
Publish as a Note w3c/wot-security-best-practices#9, by @mmccool.
-
Add OAuth2 recommendations w3c/wot-security-best-practices#8, by @mmccool.
-
-
1 issue closed.
-
Add OAuth2 recommendations w3c/wot-security-best-practices#8.
-
-
2 issues received 2 new comments.
-
Update with Discovery and Directory recommendations w3c/wot-security-best-practices#7 (1 comment by @mmccool)
-
Participants
-
2 participants joined.
-
Philipp-Alexander Blum (W3C Invited Experts) joined.
-
Christine Perey (W3C Invited Experts) joined.
-
-
2 participants left.
-
Vagner Diniz (NIC.br - Brazilian Network Information Center) left.
-
Reinaldo Ferraz (NIC.br - Brazilian Network Information Center) left.
-
GitHub
w3c/wot-discovery
-
5 issues opened.
-
A recommended approach to discovery of a gateway/intermediary w3c/wot-discovery#122, by @hspaay.
-
RD usage (endpoint vs. resource) w3c/wot-discovery#120, by @chrysn.
-
Revisit terminology w3c/wot-discovery#119, by @mmccool.
-
Incremental TDs provided by constrained devices w3c/wot-discovery#117, by @mmccool.
-
Information model for interactions w3c/wot-discovery#116, by @mmccool.
-
-
3 issues closed.
-
A recommended approach to discovery of a gateway/intermediary w3c/wot-discovery#122.
-
RD usage (endpoint vs. resource) w3c/wot-discovery#120.
-
Add links section to directory information model w3c/wot-discovery#34.
-
-
11 issues received 37 new comments.
-
Handle huge set of Thing Descriptions (pagination, streaming, etc.) w3c/wot-discovery#16 (12 comments by @farshidtz, @mmccool, @relu91, @wiresio, @zolkis)
-
Creation of OpenAPI spec from Directory TD w3c/wot-discovery#82 (6 comments by @farshidtz, @wiresio)
-
A recommended approach to discovery of a gateway/intermediary w3c/wot-discovery#122 (5 comments by @egekorkan, @farshidtz, @hspaay)
-
RD usage (endpoint vs. resource) w3c/wot-discovery#120 (3 comments by @chrysn, @k-toumura, @mmccool)
-
Incremental TDs provided by constrained devices w3c/wot-discovery#117 (3 comments by @farshidtz, @mmccool)
-
Need to define the discovery types and vocabulary w3c/wot-discovery#54 (3 comments by @AndreaCimminoArriaga, @farshidtz)
-
Should Directories store TD Models as well as Instances? w3c/wot-discovery#58 (1 comment by @memelet)
-
-
7 pull requests opened.
-
Registration spec: listing w3c/wot-discovery#124, by @farshidtz.
-
Editorial fix: TDD and TTL note w3c/wot-discovery#123, by @farshidtz.
-
Type correction in Section 5.4, and some editorial fixes w3c/wot-discovery#121, by @k-toumura.
-
Refine the information model w3c/wot-discovery#118, by @farshidtz.
-
Specify self-described exploration w3c/wot-discovery#115, by @farshidtz.
-
WIP: Proposal for geolocation w3c/wot-discovery#114, by @mmccool.
-
Security and Privacy Considerations w3c/wot-discovery#113, by @mmccool.
-
-
7 pull requests merged.
-
WIP: Proposal for geolocation w3c/wot-discovery#114.
-
Security and Privacy Considerations w3c/wot-discovery#113.
-
Type correction in Section 5.4, and some editorial fixes w3c/wot-discovery#121.
-
Refine the information model w3c/wot-discovery#118.
-
Specify self-described exploration w3c/wot-discovery#115.
-
Describe the information model w3c/wot-discovery#112.
-
Update SPARQL DDoS ed note w3c/wot-discovery#107.
-
-
6 pull requests received 30 new comments.
-
Type correction in Section 5.4, and some editorial fixes w3c/wot-discovery#121 (5 comments by @mmccool)
w3c/wot-binding-templates
-
2 issues opened.
-
Issue with ReadMultiple w3c/wot-binding-templates#111, by @mjkoster.
-
Removing Section 4.3 w3c/wot-binding-templates#110, by @egekorkan.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Refining Modbus protocol binding w3c/wot-binding-templates#109, by @relu91.
-
-
1 pull request received 7 new comments.
-
Refining Modbus protocol binding w3c/wot-binding-templates#109 (7 comments by @mjkoster, @relu91, @sebastiankb)
-
w3c/wot-thing-description
-
14 issues opened.
-
Allow a webthing to provide an icon w3c/wot-thing-description#1063, by @cgerhard.
-
Representation of examples (hidden information) w3c/wot-thing-description#1059, by @danielpeintner.
-
Restrict `@type` and `rel` values w3c/wot-thing-description#1056, by @egekorkan.
-
[validation] Changing `oneOf` to `anyOf` for the validation of security scheme w3c/wot-thing-description#1055, by @egekorkan.
-
Allowing overwriting number types and its impact. w3c/wot-thing-description#1054, by @sebastiankb.
-
Consider adding DataSchema to response and additionalResponses w3c/wot-thing-description#1053, by @mmccool.
-
Updating NEW_FEATURES.md w3c/wot-thing-description#1051, by @egekorkan.
-
What can be a TM is not clearly defined w3c/wot-thing-description#1050, by @egekorkan.
-
Array definitions in Hypermedia Controls Vocabulary Definitions w3c/wot-thing-description#1048, by @sebastiankb.
-
Two step generation of the TD from a TM should be clear w3c/wot-thing-description#1047, by @egekorkan.
-
The term required in Thing Model is confusing w3c/wot-thing-description#1046, by @egekorkan.
-
keyword model is missing in VersionInfo definition w3c/wot-thing-description#1045, by @egekorkan.
-
Adding term to indicate a stream of data w3c/wot-thing-description#1044, by @egekorkan.
-
Add formal validation process w3c/wot-thing-description#1043, by @mmccool.
-
-
8 issues closed.
-
Restrict `@type` and `rel` values w3c/wot-thing-description#1056.
-
What can be a TM is not clearly defined w3c/wot-thing-description#1050.
-
keyword model is missing in VersionInfo definition w3c/wot-thing-description#1045.
-
HTML Thing Description Ontology - fragment identifier not fully correct w3c/wot-thing-description#1028.
-
Missing triple resolution in JSON-LD playground for properties forms w3c/wot-thing-description#905.
-
Ontology files return 404 w3c/wot-thing-description#917.
-
Missing "href" in Link under TD 1.1 w3c/wot-thing-description#1041.
-
[question] How to describe Philips Hue security scheme w3c/wot-thing-description#923.
-
-
22 issues received 57 new comments.
-
Two step generation of the TD from a TM should be clear w3c/wot-thing-description#1047 (9 comments by @danielpeintner, @egekorkan, @relu91, @sebastiankb)
-
Which is better to actuate devices, invoking ACTION or writing PROPERTY? w3c/wot-thing-description#1020 (7 comments by @egekorkan, @k-toumura, @mryuichi, @sebastiankb)
-
What can be a TM is not clearly defined w3c/wot-thing-description#1050 (6 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
Allowing overwriting number types and its impact. w3c/wot-thing-description#1054 (4 comments by @egekorkan, @relu91, @sebastiankb)
-
Adding term to indicate a stream of data w3c/wot-thing-description#1044 (4 comments by @egekorkan, @mjkoster, @relu91, @sebastiankb)
-
Allow a webthing to provide an icon w3c/wot-thing-description#1063 (3 comments by @benfrancis, @egekorkan)
-
Consider adding DataSchema to response and additionalResponses w3c/wot-thing-description#1053 (3 comments by @mjkoster, @mmccool, @sebastiankb)
-
HTML Thing Description Ontology - fragment identifier not fully correct w3c/wot-thing-description#1028 (3 comments by @vcharpenay)
-
Representation of examples (hidden information) w3c/wot-thing-description#1059 (2 comments by @danielpeintner, @egekorkan)
-
The term required in Thing Model is confusing w3c/wot-thing-description#1046 (2 comments by @danielpeintner, @sebastiankb)
-
ThingTemplate definition is missing in td.ttl w3c/wot-thing-description#416 (1 comment by @sebastiankb)
-
Array definitions in Hypermedia Controls Vocabulary Definitions w3c/wot-thing-description#1048 (1 comment by @vcharpenay)
-
Introducing assumptions about TD instances that have no IP addresses w3c/wot-thing-description#977 (1 comment by @sebastiankb)
-
keyword model is missing in VersionInfo definition w3c/wot-thing-description#1045 (1 comment by @sebastiankb)
-
The "body" location value for security schemes is underspecified w3c/wot-thing-description#1037 (1 comment by @mmccool)
-
Missing triple resolution in JSON-LD playground for properties forms w3c/wot-thing-description#905 (1 comment by @vcharpenay)
-
-
8 pull requests opened.
-
TD schema restrictions w3c/wot-thing-description#1062, by @egekorkan.
-
WIP: Fix cardinality of Link.rel w3c/wot-thing-description#1061, by @vcharpenay.
-
fix issue #980 w3c/wot-thing-description#1060, by @sebastiankb.
-
Add JSON pointer assertion to definition of body sec location w3c/wot-thing-description#1058, by @mmccool.
-
add script function to open tab w3c/wot-thing-description#1057, by @danielpeintner.
-
Fix HTML fragments in ontology docs w3c/wot-thing-description#1052, by @vcharpenay.
-
TM Schema generation w3c/wot-thing-description#1049, by @egekorkan.
-
Add additionalResponses to Form w3c/wot-thing-description#1042, by @mmccool.
-
-
8 pull requests merged.
-
TD schema restrictions w3c/wot-thing-description#1062.
-
TM Schema generation w3c/wot-thing-description#1049.
-
Add additionalResponses to Form w3c/wot-thing-description#1042.
-
add script function to open tab w3c/wot-thing-description#1057.
-
Topics around Thing Model w3c/wot-thing-description#1024.
-
Fix HTML fragments in ontology docs w3c/wot-thing-description#1052.
-
Add URI template location for security scheme parameters w3c/wot-thing-description#1032.
-
Init information about WoT relation types w3c/wot-thing-description#1034.
-
-
6 pull requests received 43 new comments.
-
Topics around Thing Model w3c/wot-thing-description#1024 (13 comments by @danielpeintner, @JKRhb, @sebastiankb)
-
TM Schema generation w3c/wot-thing-description#1049 (10 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
Add additionalResponses to Form w3c/wot-thing-description#1042 (9 comments by @mmccool, @relu91, @sebastiankb)
-
Add URI template location for security scheme parameters w3c/wot-thing-description#1032 (7 comments by @mmccool, @sebastiankb)
-
Init information about WoT relation types w3c/wot-thing-description#1034 (1 comment by @sebastiankb)
-
w3c/wot-profile
-
1 issue opened.
-
Reference Device Definition for the smallest possible platform for HTTP / TCP / JSON w3c/wot-profile#68, by @mlagally.
-
-
2 issues received 16 new comments.
-
Reference Device Definition for the smallest possible platform for HTTP / TCP / JSON w3c/wot-profile#68 (11 comments by @danielpeintner, @mlagally, @sebastiankb)
-
-
2 pull requests opened.
-
device categories - initial draft w3c/wot-profile#70, by @mlagally.
-
Reference device w3c/wot-profile#69, by @mlagally.
-
-
2 pull requests received 8 new comments.
w3c/wot-scripting-api
-
8 issues opened.
-
Feedback about InteractionOuput w3c/wot-scripting-api#306, by @relu91.
-
Produce ExposedThing from a ThingModel instance w3c/wot-scripting-api#304, by @relu91.
-
Separate ExposedThing API w3c/wot-scripting-api#303, by @zolkis.
-
ActionHandler returning InteractionInput always w3c/wot-scripting-api#302, by @danielpeintner.
-
TypeScript - Type DataSchemaValue circularly references itself w3c/wot-scripting-api#301, by @danielpeintner.
-
Should title be mandatory in ExposedThingInit? w3c/wot-scripting-api#300, by @relu91.
-
Chose a particular security schema for an ExposedThing w3c/wot-scripting-api#299, by @relu91.
-
Requirements for Managment APIs w3c/wot-scripting-api#298, by @relu91.
-
-
2 issues closed.
-
Partial TD validation w3c/wot-scripting-api#287.
-
PropertyReadHandler properly defined? w3c/wot-scripting-api#290.
-
-
1 issue reopened.
-
Feedback about InteractionOuput w3c/wot-scripting-api#306, by @zolkis.
-
-
12 issues received 42 new comments.
-
Feedback about InteractionOuput w3c/wot-scripting-api#306 (7 comments by @danielpeintner, @relu91, @zolkis)
-
Chose a particular security schema for an ExposedThing w3c/wot-scripting-api#299 (7 comments by @danielpeintner, @relu91, @zolkis)
-
DataSchemaValue in TS should not be any w3c/wot-scripting-api#296 (7 comments by @danielpeintner, @relu91, @zolkis)
-
Produce ExposedThing from a ThingModel instance w3c/wot-scripting-api#304 (6 comments by @relu91, @zolkis)
-
ActionHandler returning InteractionInput always w3c/wot-scripting-api#302 (3 comments by @danielpeintner, @relu91, @zolkis)
-
TypeScript - Type DataSchemaValue circularly references itself w3c/wot-scripting-api#301 (2 comments by @danielpeintner, @relu91)
-
Should title be mandatory in ExposedThingInit? w3c/wot-scripting-api#300 (2 comments by @danielpeintner, @relu91)
-
Does PropertyMap need to be different for reading and writing a value? w3c/wot-scripting-api#293 (1 comment by @danielpeintner)
-
Produce() method should ignore instance specific information w3c/wot-scripting-api#156 (1 comment by @relu91)
-
Simplification of interface InteractionOutput w3c/wot-scripting-api#292 (1 comment by @danielpeintner)
-
-
2 pull requests opened.
-
Factor out maplike interfaces property reads and writes w3c/wot-scripting-api#305, by @zolkis.
-
make TS definitions for DataSchemaValue more accurate w3c/wot-scripting-api#297, by @danielpeintner.
-
-
2 pull requests merged.
-
Add definitions for partialTD w3c/wot-scripting-api#289.
-
make TS definitions for DataSchemaValue more accurate w3c/wot-scripting-api#297.
-
-
3 pull requests received 20 new comments.
-
Add definitions for partialTD w3c/wot-scripting-api#289 (10 comments by @danielpeintner, @relu91, @zolkis)
-
make TS definitions for DataSchemaValue more accurate w3c/wot-scripting-api#297 (6 comments by @danielpeintner, @relu91)
-
Factor out maplike interfaces property reads and writes w3c/wot-scripting-api#305 (4 comments by @danielpeintner, @zolkis)
-
w3c/wot-architecture
-
1 issue opened.
-
Consolidate usage of gateway, edge and hub w3c/wot-architecture#581, by @mlagally.
-
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Update index.html - Terminology definition for TD Fragment w3c/wot-architecture#580.
-
-
1 pull request closed.
-
Define TD Fragment w3c/wot-architecture#579.
-
-
1 pull request received 7 new comments.
w3c/wot-security
-
2 issues received 10 new comments.
-
Update security and privacy considerations in Discovery w3c/wot-security#196 (5 comments by @mmccool)
-
1 pull request opened.
-
Add crypto hardware survey in /background w3c/wot-security#199, by @Citrullin.
-
-
1 pull request merged.
-
Add crypto hardware survey in /background w3c/wot-security#199.
-
-
1 pull request received 1 new comment.
Participants
-
3 participants left.
-
Ryo Kajiwara (Ierae Securiy, Inc.) left.
-
Xiaoru Li (Baidu, Inc.) left.
-
Siyang Liu (Baidu, Inc.) left.
-
-
1 organization left.
-
Baidu, Inc. left.
-
GitHub
w3c/wot-profile
-
4 issues opened.
-
Max number of objects w3c/wot-profile#67, by @mlagally.
-
Max size of a Core Profile-compliant TD w3c/wot-profile#66, by @mlagally.
-
Eliminate ednote on single array elements (string vs array of [string]) ? w3c/wot-profile#64, by @mlagally.
-
Accessibility review of WoT Profile specification w3c/wot-profile#63, by @mlagally.
-
-
1 issue closed.
-
FPWD Feedback by Sebastian w3c/wot-profile#45.
-
-
5 issues received 11 new comments.
-
Max size of a Core Profile-compliant TD w3c/wot-profile#66 (5 comments by @benfrancis, @mlagally, @sebastiankb)
-
Allow multiple forms for interaction affordances in Core Profile w3c/wot-profile#60 (1 comment by @mlagally)
-
-
3 pull requests opened.
-
Update index.html - Max nesting of elements. w3c/wot-profile#65, by @mlagally.
-
apply the diff with the FPWD version w3c/wot-profile#62, by @ashimura.
-
Mark repo as host of rec-track work w3c/wot-profile#61, by @dontcallmedom.
-
-
3 pull requests merged.
-
Update index.html - Max nesting of elements. w3c/wot-profile#65.
-
apply the diff with the FPWD version w3c/wot-profile#62.
-
Mark repo as host of rec-track work w3c/wot-profile#61.
-
-
1 pull request received 1 new comment.
w3c/wot-thing-description
-
9 issues opened.
-
Missing "href" in Link under TD 1.1 w3c/wot-thing-description#1041, by @farshidtz.
-
Fixed locations for JSON Schema files w3c/wot-thing-description#1040, by @egekorkan.
-
Review the latest TD draft from the point of view of accessibility w3c/wot-thing-description#1039, by @sebastiankb.
-
The "body" location value for security schemes is underspecified w3c/wot-thing-description#1037, by @mmccool.
-
Wrong context in JSON Schema for TD v1.1 w3c/wot-thing-description#1036, by @farshidtz.
-
Consider defining additional vocabulary supporting Discovery w3c/wot-thing-description#1033, by @mmccool.
-
ReSpec Warnings w3c/wot-thing-description#1029, by @danielpeintner.
-
HTML Thing Description Ontology - fragment identifier not fully correct w3c/wot-thing-description#1028, by @danielpeintner.
-
Multiple bases or forms? w3c/wot-thing-description#1026, by @Citrullin.
-
-
5 issues closed.
-
Wrong context in JSON Schema for TD v1.1 w3c/wot-thing-description#1036.
-
ReSpec Warnings w3c/wot-thing-description#1029.
-
Add hint that relation type values are collected. w3c/wot-thing-description#978.
-
[DataSchema] maximum and minimum are not clear about inclusiveness w3c/wot-thing-description#1010.
-
Multiple bases or forms? w3c/wot-thing-description#1026.
-
-
18 issues received 49 new comments.
-
JSON Schema for Thing Model w3c/wot-thing-description#972 (9 comments by @danielpeintner, @egekorkan, @handrews, @relu91, @sebastiankb)
-
import/extend functionality in TD w3c/wot-thing-description#168 (5 comments by @egekorkan, @JKRhb, @kolotu, @sebastiankb)
-
Wrong context in JSON Schema for TD v1.1 w3c/wot-thing-description#1036 (4 comments by @danielpeintner, @egekorkan, @farshidtz)
-
Is the use of "$ref" and "definitions" allowed in TD ? w3c/wot-thing-description#307 (4 comments by @danielpeintner, @handrews, @sebastiankb)
-
[question] How to describe Philips Hue security scheme w3c/wot-thing-description#923 (4 comments by @egekorkan, @mmccool, @sebastiankb)
-
Multiple bases or forms? w3c/wot-thing-description#1026 (3 comments by @Citrullin, @danielpeintner, @sebastiankb)
-
[security] API key and PSK security schemes are not referenced or explained w3c/wot-thing-description#998 (3 comments by @egekorkan, @mmccool)
-
The "body" location value for security schemes is underspecified w3c/wot-thing-description#1037 (2 comments by @egekorkan, @mmccool)
-
Consider to cross reference JSON Schema definitions (external or internal) w3c/wot-thing-description#604 (2 comments by @handrews, @TuranElchuev)
-
Refer to developer documentation from a TD w3c/wot-thing-description#918 (2 comments by @mlagally, @sebastiankb)
-
Which is better to actuate devices, invoking ACTION or writing PROPERTY? w3c/wot-thing-description#1020 (2 comments by @egekorkan, @mryuichi)
-
Allow array for response in From class? w3c/wot-thing-description#617 (2 comments by @mjkoster, @sebastiankb)
-
Definition of contentEncoding should be of type xsd:string w3c/wot-thing-description#980 (1 comment by @sebastiankb)
-
JSON Schema breaking changes in Drafts 2019 and newer w3c/wot-thing-description#1017 (1 comment by @handrews)
-
-
7 pull requests opened.
-
Add draft TD context URI w3c/wot-thing-description#1038, by @farshidtz.
-
Extended forms in case of mutliple op values w3c/wot-thing-description#1035, by @sebastiankb.
-
Init information about WoT relation types w3c/wot-thing-description#1034, by @sebastiankb.
-
Add URI template location for security scheme parameters w3c/wot-thing-description#1032, by @mmccool.
-
Improve descriptions of apikey and psk security schemes w3c/wot-thing-description#1031, by @mmccool.
-
fix: respec warnings w3c/wot-thing-description#1030, by @danielpeintner.
-
apply changes for the FPWD of ver 1.1 spec w3c/wot-thing-description#1027, by @ashimura.
-
-
7 pull requests merged.
-
Add draft TD context URI w3c/wot-thing-description#1038.
-
Improve descriptions of apikey and psk security schemes w3c/wot-thing-description#1031.
-
Extended forms in case of mutliple op values w3c/wot-thing-description#1035.
-
fix: respec warnings w3c/wot-thing-description#1030.
-
Introduce observeAllProperties and unobserveAllProperties w3c/wot-thing-description#1025.
-
Issue 1010 w3c/wot-thing-description#1021.
-
apply changes for the FPWD of ver 1.1 spec w3c/wot-thing-description#1027.
-
-
13 pull requests received 64 new comments.
-
Init information about WoT relation types w3c/wot-thing-description#1034 (13 comments by @danielpeintner, @egekorkan, @sebastiankb)
-
Improve descriptions of apikey and psk security schemes w3c/wot-thing-description#1031 (11 comments by @danielpeintner, @egekorkan, @mmccool, @sebastiankb)
-
Topics around Thing Model w3c/wot-thing-description#1024 (9 comments by @JKRhb, @relu91, @sebastiankb)
-
Add URI template location for security scheme parameters w3c/wot-thing-description#1032 (8 comments by @danielpeintner, @egekorkan, @mmccool, @relu91, @sebastiankb)
-
Add draft TD context URI w3c/wot-thing-description#1038 (7 comments by @danielpeintner, @egekorkan, @farshidtz, @sebastiankb)
-
Introduce observeAllProperties and unobserveAllProperties w3c/wot-thing-description#1025 (6 comments by @danielpeintner, @sebastiankb, @vcharpenay)
-
Extended forms in case of mutliple op values w3c/wot-thing-description#1035 (2 comments by @egekorkan, @sebastiankb)
-
apply changes for the FPWD of ver 1.1 spec w3c/wot-thing-description#1027 (2 comments by @egekorkan, @sebastiankb)
-
WIP: Add proof and proofChain sections w3c/wot-thing-description#943 (2 comments by @mmccool, @sebastiankb)
-
w3c/wot-thing-description#924 (1 comment by @sebastiankb)
-
w3c/wot-thing-description#964 (1 comment by @sebastiankb)
-
w3c/wot-discovery
-
1 issue opened.
-
Geolocation query filters for AR w3c/wot-discovery#111, by @mmccool.
-
-
1 issue closed.
-
How do we handle federation in SPARQL queries w3c/wot-discovery#97.
-
-
7 issues received 12 new comments.
-
Need to define the discovery types and vocabulary w3c/wot-discovery#54 (3 comments by @mmccool, @relu91)
-
Define the WoT-Directory type somewhere (eg in new version of context, in 1.1) w3c/wot-discovery#43 (2 comments by @mmccool, @relu91)
-
Canonicalization requirements for directories w3c/wot-discovery#104 (2 comments by @AndreaCimminoArriaga, @mmccool)
-
Add evaluation features for advanced directory services w3c/wot-discovery#92 (1 comment by @Citrullin)
-
-
5 pull requests opened.
-
Describe the information model w3c/wot-discovery#112, by @farshidtz.
-
Update README.md to point at WOT-Usecases repo w3c/wot-discovery#110, by @cperey.
-
Correct combo scheme w3c/wot-discovery#109, by @farshidtz.
-
apply the diff with the FPWD version w3c/wot-discovery#108, by @ashimura.
-
Update SPARQL DDoS ed note w3c/wot-discovery#107, by @mmccool.
-
-
5 pull requests merged.
-
Update README.md to point at WOT-Usecases repo w3c/wot-discovery#110.
-
Correct combo scheme w3c/wot-discovery#109.
-
apply the diff with the FPWD version w3c/wot-discovery#108.
-
Add and refer to a single validation section w3c/wot-discovery#106.
-
Updated document with federation w3c/wot-discovery#105.
-
-
4 pull requests received 9 new comments.
-
Describe the information model w3c/wot-discovery#112 (3 comments by @AndreaCimminoArriaga, @farshidtz)
w3c/wot-architecture
-
1 issue opened.
-
Accessibility considerations of WoT architecture w3c/wot-architecture#578, by @mlagally.
-
-
2 issues received 5 new comments.
-
Create terminology definition for "partial TD" w3c/wot-architecture#453 (3 comments by @danielpeintner, @mlagally, @relu91)
-
Terminology: thing description fragments w3c/wot-architecture#574 (2 comments by @danielpeintner, @relu91)
-
-
4 pull requests opened.
-
Update index.html - Terminology definition for TD Fragment w3c/wot-architecture#580, by @mlagally.
-
Define TD Fragment w3c/wot-architecture#579, by @mlagally.
-
Introduce Partial TD definition w3c/wot-architecture#577, by @relu91.
-
apply changes for fpwd w3c/wot-architecture#576, by @ashimura.
-
-
2 pull requests merged.
-
Introduce Partial TD definition w3c/wot-architecture#577.
-
apply changes for fpwd w3c/wot-architecture#576.
-
-
2 pull requests received 11 new comments.
-
Introduce Partial TD definition w3c/wot-architecture#577 (8 comments by @ashimura, @danielpeintner, @mlagally, @relu91, @zolkis)
-
w3c/wot-scripting-api
-
6 issues opened.
-
DataSchemaValue in TS should not be any w3c/wot-scripting-api#296, by @relu91.
-
Should value function return DataSchemaValue? w3c/wot-scripting-api#294, by @relu91.
-
Does PropertyMap need to be different for reading and writing a value? w3c/wot-scripting-api#293, by @danielpeintner.
-
Simplification of interface InteractionOutput w3c/wot-scripting-api#292, by @danielpeintner.
-
PropertyReadHandler properly defined? w3c/wot-scripting-api#290, by @danielpeintner.
-
Partial TD validation w3c/wot-scripting-api#287, by @danielpeintner.
-
-
4 issues closed.
-
Should value function return DataSchemaValue? w3c/wot-scripting-api#294.
-
Update references to upcoming documents w3c/wot-scripting-api#278.
-
Bring back updated links to whatwg w3c/wot-scripting-api#284.
-
Provide Task force description w3c/wot-scripting-api#285.
-
-
10 issues received 20 new comments.
-
DataSchemaValue in TS should not be any w3c/wot-scripting-api#296 (3 comments by @danielpeintner, @relu91, @zolkis)
-
Should value function return DataSchemaValue? w3c/wot-scripting-api#294 (3 comments by @danielpeintner)
-
Simplification of interface InteractionOutput w3c/wot-scripting-api#292 (3 comments by @danielpeintner, @relu91, @zolkis)
-
PropertyReadHandler properly defined? w3c/wot-scripting-api#290 (2 comments by @danielpeintner, @relu91)
-
Does PropertyMap need to be different for reading and writing a value? w3c/wot-scripting-api#293 (1 comment by @zolkis)
-
-
5 pull requests opened.
-
feat: use DataSchemaValue for value() function in InteractionOutput w3c/wot-scripting-api#295, by @danielpeintner.
-
fix: PropertyReadHandler returning promise with InteractionInput w3c/wot-scripting-api#291, by @danielpeintner.
-
Add definitions for partialTD w3c/wot-scripting-api#289, by @relu91.
-
apply the diff with the Note1 version w3c/wot-scripting-api#288, by @ashimura.
-
apply the diff with the Note1 version w3c/wot-scripting-api#286, by @ashimura.
-
-
3 pull requests merged.
-
feat: use DataSchemaValue for value() function in InteractionOutput w3c/wot-scripting-api#295.
-
fix: PropertyReadHandler returning promise with InteractionInput w3c/wot-scripting-api#291.
-
apply the diff with the Note1 version w3c/wot-scripting-api#288.
-
-
1 pull request closed.
-
apply the diff with the Note1 version w3c/wot-scripting-api#286.
-
-
4 pull requests received 17 new comments.
-
Add definitions for partialTD w3c/wot-scripting-api#289 (9 comments by @danielpeintner, @egekorkan, @relu91, @zolkis)
-
fix: PropertyReadHandler returning promise with InteractionInput w3c/wot-scripting-api#291 (6 comments by @danielpeintner, @relu91, @zolkis)
-
w3c/wot-security
-
1 issue closed.
-
Review security architecture of Home Assistant w3c/wot-security#191.
-
-
6 issues received 12 new comments.
-
Review security architecture of Home Assistant w3c/wot-security#191 (4 comments by @mmccool, @relu91)
-
Promoting an approach where every thing is a server is a security nightmare w3c/wot-security#197 (4 comments by @hspaay, @mmccool)
-
Update security and privacy considerations in Discovery w3c/wot-security#196 (1 comment by @mmccool)
-
Review security architecture of Mozilla WebThings gateway w3c/wot-security#188 (1 comment by @mmccool)
-
-
1 pull request opened.
-
Update hubs.md with OpenHABs content w3c/wot-security#198, by @mmccool.
-
-
1 pull request merged.
-
Update hubs.md with OpenHABs content w3c/wot-security#198.
-
w3c/wot-binding-templates
-
1 pull request opened.
-
fix: MQTT markup w3c/wot-binding-templates#108, by @danielpeintner.
-
-
1 pull request merged.
-
fix: MQTT markup w3c/wot-binding-templates#108.
-
-
1 pull request received 1 new comment.