Common use of AIT Clause in Contracts

AIT. Connectivity with other systems / system-system and system interaction Figure 2: ▇▇▇▇▇ system architecture 1. The ▇▇▇▇▇ OSGi framework can only be used in compliance with the License. A copy of the license can be obtained at ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/licenses/lgpl- 2.1.txt. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. AIT is using and will use ▇▇▇▇▇ in other national and European R&D activities, field installations as well as for for exploitation. In order to provide a user interface which can be used on a wide variety of devices, great emphasis was put on using technology based on existing protocols, specifications and web standards from the World Wide Web Consortium (W3C)36, WHATWG37, The Internet Engineering Task Force (IETF®)38 as well as Standards from Ecma International®39. More specifically, the following protocols, specifications and standards were used:  W3C o HTML5: ▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/TR/html5/ Used for displaying data as well as playing multimedia data (video/audio) 36 ▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/Consortium/ 37 ▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇.▇▇▇/wiki/FAQ 38 ▇▇▇▇▇://▇▇▇▇.▇▇▇/ 39 ▇▇▇▇▇://▇▇▇.▇▇▇▇-▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/ directly in a browser without the need for additional plug-ins or 3rd party programs. o CSS: ▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/TR/CSS/ Used to design the user interface. o webRTC: ▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/TR/webrtc/ Used to establish VoIP (voice over IP) connection directly in the browser without the need for additional plug-ins or 3rd party programs. o Web Storage: ▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/TR/webstorage/ Used to locally store the deviceid of the user interface.  IETF® o WebSocket Protocol: ▇▇▇▇▇://▇▇▇▇▇.▇▇▇▇.▇▇▇/html/rfc6455 Used for enabling a full-duplex communication channel over a single TCP connection. o SIP: ▇▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇/rfc/rfc3261.txt Used for VoIP functionality.  WHATWG o WebSocket Interface: ▇▇▇▇▇://▇▇▇▇.▇▇▇▇.▇▇▇▇▇▇.▇▇▇/multipage/comms.html#network Interface specification of the WebSocket protocol in web applications  Ecma International® o ECMAScript: ISO/IEC 16262 (▇▇▇▇://▇▇▇.▇▇▇▇- ▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/▇▇▇▇▇▇▇▇▇▇▇▇/▇▇▇▇▇▇▇▇▇/▇▇▇▇-▇▇▇.▇▇▇) Used for adding dynamic interaction capabilities to otherwise static HTML based UIs.  JSON: o ISO/IEC DIS 21778 (▇▇▇▇://▇▇▇.▇▇▇▇- ▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/▇▇▇▇▇▇▇▇▇▇▇▇/▇▇▇▇▇▇▇▇▇/▇▇▇▇-▇▇▇.▇▇▇) Data exchange format between different components of the Miraculous-Life system.

AIT. Connectivity with other systems / system-system and system interaction Figure 2: ▇▇▇▇▇ system architectureinteraction 1. The ▇▇▇▇▇ OSGi framework can only be used in compliance with the License. A copy of the license can be obtained at ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/licenses/lgpl- 2.1.txt. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. AIT is using and will use ▇▇▇▇▇ in other national and European R&D activities, field installations as well as for for exploitation. In order to provide a user interface which can be used on a wide variety of devices, great emphasis was put on using technology based on existing protocols, specifications and web standards from the World Wide Web Consortium (W3C)36, WHATWG37, The Internet Engineering Task Force (IETF®)38 as well as Standards from Ecma International®39. More specifically, the following protocols, specifications and standards were used:  W3C o HTML5: ▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/TR/html5/ Used for displaying data as well as playing multimedia data (video/audio) 36 ▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/Consortium/ 37 ▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇.▇▇▇/wiki/FAQ 38 ▇▇▇▇▇://▇▇▇▇.▇▇▇/ 39 ▇▇▇▇▇://▇▇▇.▇▇▇▇-▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/ directly in a browser without the need for additional plug-ins or 3rd party programs. o CSS: ▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/TR/CSS/ Used to design the user interface. o webRTC: ▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/TR/webrtc/ Used to establish VoIP (voice over IP) connection directly in the browser without the need for additional plug-ins or 3rd party programs. o Web Storage: ▇▇▇▇▇://▇▇▇.▇▇.▇▇▇/TR/webstorage/ Used to locally store the deviceid of the user interface.  IETF® o WebSocket Protocol: ▇▇▇▇▇://▇▇▇▇▇.▇▇▇▇.▇▇▇/html/rfc6455 Used for enabling a full-duplex communication channel over a single TCP connection. o SIP: ▇▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇/rfc/rfc3261.txt Used for VoIP functionality.  WHATWG o WebSocket Interface: ▇▇▇▇▇://▇▇▇▇.▇▇▇▇.▇▇▇▇▇▇.▇▇▇/multipage/comms.html#network Interface specification of the WebSocket protocol in web applications  Ecma International® o ECMAScript: ISO/IEC 16262 (▇▇▇▇://▇▇▇.▇▇▇▇- ▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/▇▇▇▇▇▇▇▇▇▇▇▇/▇▇▇▇▇▇▇▇▇/▇▇▇▇-▇▇▇.▇▇▇) Used for adding dynamic interaction capabilities to otherwise static HTML based UIs.  JSON: o ISO/IEC DIS 21778 (▇▇▇▇://▇▇▇.▇▇▇▇- ▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/▇▇▇▇▇▇▇▇▇▇▇▇/▇▇▇▇▇▇▇▇▇/▇▇▇▇-▇▇▇.▇▇▇) Data exchange format between different components of the Miraculous-Life system.