[WoT IG] to converge on WoT architecture

Dear all,



as we circulated now some architecture views [Dave] [Kazuo Kajimoto] [Johannes] [Kazuaki Nimura] and even had some nice presentation how to use those to represent use cases [Claes] it is time to find a way how we can converge and compile this input. To my understanding this has two aspects



a)      Exchange the representation in a editable way which in the best case also allow for change tracking and

b)      Enable to use those to describe use cases or proposals



In the TF-AP last week an option to use [plantUML] for the variety of diagrams were discussed.



So I did the exercise to draft some architecture aspects from my view point and share



a)      the attached slides showing those aspects (I assume they are not self explanatory yet, but for sure you have some associations ;-) and

b)      the plantUML source code, so you can edit or augment the figures e.g. with an online editor e.g. [PlantText]



In the webconf tomorrow I can give a brief introduction to the slides, but even more important we need to discuss if we can agree to take plantUML for joint editing of these views and understanding. It is my understanding that in parallel Johannes is conducting some experiments to integrate plantUML figure generation into github so we not have to share two documents as done for illustration above but can work on a single one.



So please share your ideas on this.



BR,

Joerg



References:

[Dave] http://www.w3.org/2015/05/wot-framework.pdf

[Johannes] https://github.com/w3c/wot/blob/master/TF-AP/Example_sketch.md

[Kazuo Kajimoto] http://www.w3.org/2015/04/munich/kajimoto.pdf

[Kazuaki Nimura]https://lists.w3.org/Archives/Public/public-wot-ig/2015May/att-0022/A_use_case_and_architecture__Fujitsu_.pdf

[Claes] https://lists.w3.org/Archives/Public/public-wot-ig/2015May/att-0021/UC_Remote_health_monitoring_system_-_mapping_to_APIs_and_protocols.pdf

[plantUML] http://plantuml.sourceforge.net/index.html

[PlantText] http://www.planttext.com/planttext