diff options
| author |   Romain Forlot <romain.forlot@iot.bzh> | 2017-06-26 15:06:10 +0200 |
|---|---|---|
| committer | Romain Forlot <romain.forlot@iot.bzh> | 2017-06-29 16:55:12 +0200 |
| commit | f007f831ab9ee3ce7010719300ffd84e4a787301 (patch) | |
| tree | 5055e30bdf06bdeeb9a355c1342a5dfd8f6a0163 /signaling | |
| parent | eca44ae331bfe8bc4021541d5bf00c0fd8525f08 (diff) | |
Fix: wrong array format
Change-Id: I1c2c1479980c391dd037ce93cf5a30c36a07085a
Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
Diffstat (limited to 'signaling')
| -rw-r--r-- | signaling/architecture.md | 27 |
1 files changed, 13 insertions, 14 deletions
diff --git a/signaling/architecture.md b/signaling/architecture.md index 8c6064d..48d596f 100644 --- a/signaling/architecture.md +++ b/signaling/architecture.md @@ -226,20 +226,19 @@ as simple as a signal service. The same remarks apply for automation languages. Further investigations leads to some specifications already presents like the one from Jaguar Land Rover [[VISS]], for **Vehicule Information Service Specification** and another from Volkwagen AG named [[ViWi]], stand for -**Volkwagen Infotainment Web Interface**. Each ones has their pro and cons. -Let's see a little comparison: - -TODO: List of features not pro cons -| VISS | ViWi | -|-------------------------------------------------------|-------------------------------------------------------------------| -| + Filtering on node (not possible on several nodes or branches) | | + Describe a protocol | -| + Access restrictions to signals | + Ability to specify custom signals | -| +/- Use high level development languages | + RESTful HTTP calls | -| - One big Server that handle requests | + Stateless | -| - Filtering | + Filtering, sorting | -| - Static signals tree not extensible [[VSS]] | -/+ Use JSON objects to communicate | -| - Use of AMB ? | - Identification of resources may be a bit heavy going using UUID | -| - Use of Websocket | | +**Volkwagen Infotainment Web Interface**. Each ones has their differences and +provides different approach serving the same goal: + +| VISS | ViWi | +|---------------------------------------------------------------|-----------------------------------------------------------------| +| Filtering on node (not possible on several nodes or branches) | Describe a protocol | +| Access restrictions to signals | Ability to specify custom signals | +| Use high level development languages | RESTful HTTP calls | +| One big Server that handle requests | Stateless | +| Filtering | Filtering, sorting | +| Static signals tree not extensible [[VSS]] | Use JSON objects to communicate | +| Use of AMB ? | Identification of resources may be a bit heavy going using UUID | +| Use of Websocket | | About **[[VISS]]** specification, the major problem comes from the fact that signals are specified under the [[VSS]], **Vehicle Signal Specification**. So, |