eclipse-thingweb / dart_wot Goto Github PK

Support for Thing Models is currently missing, but should be added at some point as a feature (with low priority) to cover the whole TD specification.

After the repository transfer, we should update the copyright headers contained in the source files. Currently, the general structure looks like this:

Should we change the headers to something like this:

// Copyright 2021(?) Contributors to the Eclipse Foundation. All rights reserved. 
// Use of this source code is governed by a BSD-style 
// license that can be found in the LICENSE file.

or should we (additionally) also keep the original mentioning of "The NAMIB Project Developers"?

Tasks

• #67
• Update LICENSE file
• Update license information in copyright headers

At the moment, dart_wot is registered under the "verified publisher" namib.me on pub.dev, Dart and Flutter's package repository. For the nearer future, it would probably be nice to also have a verified publisher for thingweb.io, in order to be able to publish Dart packages in an "official" manner.

For the codecov badge to continue working, we may need to update the secret associated with this repository (see here).

While a number of SecuritySchemes have already been implemented, there are still a number of Schemes missing. This issue serves as a tracker for the remaining Schemes which can be devided into a generic one (the ComboSecurityScheme) and (mostly) HTTP or CoAP related ones.

Generic Schemes

• Implement ComboSecurityScheme (Feature is currently marked as "at risk")

HTTP Schemes

• Implement OAuth2SecurityScheme
  • Dart's oauth2 can be used to implement this
• Implement APIKeySecurityScheme

CoAP Schemes

• Implement PSKSecurityScheme
• #8

Implementation steps

• Finish data model and deserialization (see !45)
• Add ACE-OAuth support to CoAP binding

The interface is already defined in the scripting_api library and an ExposedThing class exists in the core library, but it is currently missing implementations for the methods it should provide according to the API specification. One prerequisite for a working ExposedThing is also a ProtocolServer implementation which in our case should be a basic CoapServer.

Implementation steps

• Implement ExposedThing methods in core library.
• Test with an implemented CoapServer or rather a mocked ProtocolServer.