7 | | * The web architecture, which defines how communication between the core elements can be orchestrated over web services. |
8 | | |
9 | | This project also contains a java-based reference implementation. It provides protocols, data structures and many components needed in negotiation such as isues, values, domain descriptions, preference profiles, timelines, negotiation protocols, json serialization of these items, automatic negotiation software, etc. |
10 | | |
11 | | This page contains technical documentation describing the core json structures for describing issues, values, bids, offers, negotiation events etc. |
| 7 | * The web architecture, which defines how communication between the core elements can be realized with [https://en.wikipedia.org/wiki/WebSocket websockets]. |
| 8 | |
| 9 | This page describes the core. This page shows the json structures mostly by example. The details of the core are spelled out by a java-based reference implementation contained here. |
| 10 | |
| 11 | The web architecture is split into 3 main parts: |
| 12 | * a runserver, where an actual negotiation is run. Running a negotiation means execution of the negotiation protocol (as specified in the core) over websockets |
| 13 | * a partiesserver, where a party (as specified in the core) can be hooked into a websocket |
| 14 | * a profilesserver, where profiles are served over websockets. |
| 15 | |
| 16 | The web architecture is detailed in the servers (see table below). |