Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reorganize and consolidate work items #55

Merged
merged 7 commits into from
Feb 28, 2023
Merged

Reorganize and consolidate work items #55

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
615825a
reorganize work items
egekorkan Feb 21, 2023
47ca46e
Merge remote-tracking branch 'origin/main' into ege-consolidation-2
egekorkan Feb 27, 2023
0b6a833
Merge branch 'main' into ege-consolidation-2
mmccool Feb 27, 2023
8c141f7
incorporate @mmccool input and @benfrancis feedback
egekorkan Feb 27, 2023
533587e
refine work items
egekorkan Feb 28, 2023
7b69f00
delete first list and add updates to spec
egekorkan Feb 28, 2023
f521e06
add @benfrancis feedback
egekorkan Feb 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 35 additions & 10 deletions wot-wg-2023-draft.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,16 +205,41 @@ <h2>Motivation and Background</h2>
<h2>Scope</h2>
<!-- What exactly is in scope, and out of scope.
For legal review. Be brief. -->
<p>During this charter, the Working Group would:</p>
<ul>
<li>Update the Architecture, Thing Description, Profile, and Discovery specifications
to address major issues discovered during implementation of the 1.0 and 1.1 specifications.
Unlike the last charter, these would not be limited to backward-compatible updates.</li>
<li>Reorganize Security Schemes and Protocol/Payload Bindings to be more modular and less specific
to HTTP.</li>
<li>Update and improve security and privacy controls.</li>
<li>Address the functional requirements of new use cases, such as Digital Twins.</li>
</ul>
<p>During this charter, the Working Group would work on the following:</p>

<dl>
<dt><strong>Updates to existing specifications</strong>:</dt>
<dd>The WG will add new features and address issues discovered during implementation of already published specifications.
Unlike the last charter, these would not be limited to backward-compatible updates.
</dd>
<dt><strong>Support WoT Interoperability</strong>:</dt>
<dd>The WG will improve out-of-the-box interoperability and enable the integration of WoT into other ecosystems and communities.
Thus, the WG will define core binding and profiling mechanisms, specify additional protocol and payload bindings, and define appropriate profiles.
</dd>
<dt>
<strong>Improve Management of TDs</strong>:
</dt>
<dd>
Additional mechanisms around for the management of TDs are needed to improve workflows that use them.
Thus, the WG will update the Discovery specification with additional features, including geolocation.
In other specifications, the WG intends to add a mechanism to sign TDs, define how to manage versions of TDs and define how to
parse, validate, consume and lint TDs.
</dd>
<dt>
<strong>Increase Descriptiveness of TDs</strong>:
</dt>
<dd>
The WG will work on increasing the descriptive power of TDs to allow using them in more use cases. This includes
describing dynamic resources, reusable connections, historical values (timeseries), repeating payloads, both static and dynamic
geolocation information, manageable actions and more precise definitions of data schemas for each type of operation.
</dd>
<dt><strong>Improve Security and Privacy</strong>:</dt>
<dd>Define reusable, external security vocabularies, simplify the use of security schemes, and define and onboarding
lifecycle process to establish mutual trust and identification, and other work as appropriate.</dd>
<dt><strong>New Use Cases</strong>:
</dt>
<dd>Address the functional requirements of new use cases, such as Digital Twins.</dd>
</dl>

<p>
Details for planned work items, which however are subject to change, are available in a
Expand Down