Add workaround for missing content types in response fields, use correct affordance keys

eclipse-thingweb / domus-tdd-api

Semantic storage for device metadata based on W3C Thing Description information model

https://thingweb.io

Other

4 stars 3 forks source link

Add workaround for missing content types in response fields, use correct affordance keys #14

Closed JKRhb closed 3 days ago

JKRhb commented 6 days ago

This PR includes the workaround needed to resolve #13. It is based on a similar PR (https://github.com/vaimee/zion/pull/52) I submitted to ZION dealing with the same issue.

While working on this issue, I noticed that the TDD's TD did not use the correct affordance keys to be compliant with the Discovery specification (c.f. the Thing Model in section 7.3.2.4). Therefore, I also adjusted the keys to improve the directory's interoperability.

JKRhb commented 6 days ago

This PR now also contains the changes made by @Murloc6 in their PR and should only be merged afterward.

wiresio commented 3 days ago

Thanks Jan!