Outils pour utilisateurs
recherche:masters:stage_rocher_gerald_collaboration_trilogis
Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentes Révision précédente Prochaine révision | Révision précédente | ||
|
recherche:masters:stage_rocher_gerald_collaboration_trilogis [2015/07/02 16:38] rocher [Meetings follow-up...] |
recherche:masters:stage_rocher_gerald_collaboration_trilogis [2015/07/02 16:40] (Version actuelle) rocher [Meetings follow-up...] |
||
|---|---|---|---|
| Ligne 28: | Ligne 28: | ||
| ==Minutes== | ==Minutes== | ||
| - | **1. NDA content refinement needed**\\ | + | **1. NDA content refinement requested**\\ |
| Jean-Yves explained that the proposed NDA terms, as is, are too large in the context of implementing a demonstrator illustrating I3S research results by using a subset of Trilogis innovative technologies.\\ | Jean-Yves explained that the proposed NDA terms, as is, are too large in the context of implementing a demonstrator illustrating I3S research results by using a subset of Trilogis innovative technologies.\\ | ||
| The NDA must at first protect confidential information disclosed by Trilogis and I3S in order for I3S to build the demonstrator. More particularly, the demonstrator development will require the provision of certain Trilogis software, products and associated documentation. Therefore, the NDA must accurately enumerate information disclosed by Trilogis and I3S, in the context of the collaboration, that must not be disclosed to third parties.\\ | The NDA must at first protect confidential information disclosed by Trilogis and I3S in order for I3S to build the demonstrator. More particularly, the demonstrator development will require the provision of certain Trilogis software, products and associated documentation. Therefore, the NDA must accurately enumerate information disclosed by Trilogis and I3S, in the context of the collaboration, that must not be disclosed to third parties.\\ | ||
| Ligne 38: | Ligne 38: | ||
| Stefano is concerned by the need, for the tag, to embed custom annotation along with an associated way to retrieve it from an external application. We proposed to retrieve the information from a REST service knowing that currently our application is relying on web service for devices (UPnP) but can be modified to manage REST approach.\\ Stefano proposed to look at the possibilities and come back to us with some proposals based on what can be technically done (Monday 07/06/15 meeting purpose, see below).\\ | Stefano is concerned by the need, for the tag, to embed custom annotation along with an associated way to retrieve it from an external application. We proposed to retrieve the information from a REST service knowing that currently our application is relying on web service for devices (UPnP) but can be modified to manage REST approach.\\ Stefano proposed to look at the possibilities and come back to us with some proposals based on what can be technically done (Monday 07/06/15 meeting purpose, see below).\\ | ||
| \\ | \\ | ||
| - | Not proposed during the meeting but discussed offline (Gérald/Jean-Yves) : a simpler solution, avoiding any modification in the existing Trilogis framework, and considering that the tag provides an ID and its localization, would be to build a crosstable (tag ID --> Annotations). This table would be managed by I3S and used to retrieve the annotations from the tag ID. | + | //Not proposed during the meeting but discussed offline (Gérald/Jean-Yves) : a simpler solution, avoiding any modification in the existing Trilogis framework (considering that the tag provides an ID and its localization), would be to build a crosstable (tag ID --> Annotations). This table would be managed by I3S and used to retrieve the annotations from the tag ID.// |
| **Next meeting planned Monday 07/06/15 at 10AM. | **Next meeting planned Monday 07/06/15 at 10AM. | ||
recherche/masters/stage_rocher_gerald_collaboration_trilogis.1435847934.txt.gz · Dernière modification: 2015/07/02 16:38 par rocher
Outils de la page
Sauf mention contraire, le contenu de ce wiki est placé sous les termes de la licence suivante : CC Attribution-Noncommercial-Share Alike 4.0 International
