Support for multiple @context (aka support for Linked Data) about api

[mrstegeman]

(Moved from webthing-java repo)

@Martinocom I've fixed your second point via WebThingsIO/webthing-java@14ea1c7

[Martinocom]

If can be useful for someone, I made some researches about current libraries and what they can achieve. I still think that WebThings has the bigger potential (also 'cos I wanted to use some Kotlin to develop my apps), but for my purposes, as said, I cannot have one hardcoded URL for schema. Alternatives that I found are:

• WebThings: this library 👍 , but lack of support for multiple @context
• Arena Web Hub: lack of support for multiple @context
• ThingWeb: only NodeJS but does not change the @context value; not sure about support, but still better than nothing
• SmartThings: not suitable for creating Web Things
• jpasqua-WebThing or webthing-arduino: only arduino ones (no virtual devices)

I switched currently on ThingWeb and I'm figuring out how use a raw REST API for it.

[benfrancis]

@Martinocom Is the issue that you need to expose multiple contexts in the Thing Description, or that you need to consume multiple contexts from the Thing Description? I'm assuming it's the former given you originally filed this issue on the Java web thing library. Consuming multiple contexts using the WebThings Gateway's web thing adapter probably doesn't emit an error, but isn't explicitly supported yet.

This is one of the many differences between the Mozilla and W3C specifications that I intend to fix in a future version, potentially later this year, but I'm afraid it's going to take a long time to make these changes across all the WebThings libraries and gateway.

@mrstegeman In the meantime is there an easy way for Marcin to override the @context of a thing using the Java web thing library so that Marcin can add this feature for specific devices?

[mrstegeman]

@mrstegeman In the meantime is there an easy way for Marcin to override the @context of a thing using the Java web thing library so that Marcin can add this feature for specific devices?

No, it's hard-coded to use our schema URL.