is always a collection (e.g stations) and thus has to be a noun plural form, even if the will only carry one single by design. While and are predefined in this document, will always be an identifier or the keyword $id or $spec. The depth of the URI tree is limited to 3, i.e. Deviation of actual interface definition must be minimized in a reasonable way. The API described herein follows some general 'design rules' or 'paradigms'. The connection between client and server is always a TCP/IP connection that allows http(s):// and ws(s):// protocols on top. While any client can have different contexts, the web server can have different services providing a number of resources that hold a number of elements. The general architecture of a system using the herein defined interfaces is split into WebServer and Client (Figure 1: Example of system architecture). The response is always of contentType: application/json (or application/.+json for a dedicated version), this also applies for the WebSocket interface. All services provide mainly HTTP_GET, HTTP_POST, HTTP_PUT, HTTP_DELETE (herein called GET, POST, PUT, DELETE) and WebSocket interfaces. This document provides an overview over web services on the WebInfotainment platform. Please consult the complete list of acknowledged W3C Member Submissions. Please consult the requirements associated with Memberģ.3 of the W3C Patent Policy. Publication of acknowledged Member Submissions at the W3C site is one of A W3C Team Comment has been published in conjunction with this Member Submission. Product of a chartered W3C group, but is published as potential input to
Publication of this document by W3C indicates no endorsement of itsĬontent by W3C, nor that W3C has, is, or will be allocating any Members have made a formal Submission request to W3C for discussion. īy publishing this document, W3C acknowledges that the Submitting A list of current W3C publications can be found in the W3C technical reports index at. Other documents may supersede this document. This section describes the status of this document at the time of its publication. Version 1.9.0-w3c Abstract Status of this document Volkswagen Infotainment Web Interface protocol specification (viwi protocol)