Lorawan Next Steps

In today's session with OPC Foundation and Lora alliance, we have discussed potential next steps:

- [x] Investigating how common are the terms like polynomial, switch etc.
- [ ] Testing with UA Edge Translator (some breaking changes are there but did not change WoT ingestion)
- Changing the codebase to comply with the new keywords
- [ ] Mapping to OPC UA with examples
- Basic mapping with simple types: shows that it works, let people adapt to their use case. WoT Binding spec to be used
- Advanced mapping with companion specs: A good example should be found but lower priority compared to the basic mapping.
- [x] Changing the W3C binding document (not part of Eclipse Foundation work)
- Adding all the terms in there
- lorav:mostSignificantByte -> we don't have the word swap problem here. We can use bigEndian with default false since the wording is confusing
- [x] Events consideration
- We should start changing properties to events as Lora devices are event driven
- Edge translator now supports it.
- Switching to events should not effect this tool at all
- [x] Outreach
- https://lora-alliance.org/event/lora-alliance-technical-committee-meeting-members-only-3/ Also has a webcast. We may be able to talk about it
- Things Conference in September. We already have confirmed demo and keynote.
- Moving Examples to examples repo

No files, tests, or entry points are named. Start by scoping the unchecked UA Edge Translator and OPC UA mapping items, using the WoT Binding spec and the noted translator behavior as references; done requires concrete decisions and implementation targets for keyword compatibility, mappings, and examples.

Written by the indexing model from the issue text.