Common use of Web Service Clause in Contracts

Web Service. The Airport or a third party designated and identified by the Airport to the Recipient, shall provide a web service in order to accept data from the Recipient in the following manner: a. The web service shall use HTTPS protocol to submit all requests and posts. b. The web service shall allow HTTPS POST for all “pings” from Recipient. c. The web service shall accept the values for the following attributes as defined in the following list in the URL: “uid”, “tnc_id”, “license_plate”, “timestamp”, “txn_type”, “ ride_count”, “Ion”, “lat”. Parameters must be URL encoded. d. A username and secret phrase shall be shared in order to create a basic authorization mechanism for all requests from Recipient. Base64 encoding of the <username:password> shall be provided in the HTTP Authorization Header for all HTTPS requests. e. Data from Recipient shall be posted to the following URL with the following parameters with URL encoding (based on RFC 1738: ▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇/rfc/rfcl 738.txt) employed: <TBD> Example: <TBD> Airport agrees to maintain commonly accepted administrative, physical, technical, and procedural safeguards to protect the Interface Data in the possession of Airport against unauthorized access or disclosure.

Web Service. The Airport or a third party designated and identified by the Airport to the Recipient, shall provide a web service in order to accept data from the Recipient in the following manner: a. The web service shall use HTTPS protocol to submit all requests and posts. b. The web service shall allow HTTPS POST for all “pings” from Recipient. c. The web service shall accept the values for the following attributes as defined in the following list in the URL: “uid”, “tnc_id”, “license_plate”, “timestamp”, “txn_type”, “ ride_count”, “Ion”, “lat”. Parameters must be URL encoded. d. A username and secret phrase shall be shared in order to create a basic authorization mechanism for all requests from Recipient. Base64 encoding of the <username:password> shall be provided in the HTTP Authorization Header for all HTTPS requests. e. Data from Recipient shall be posted to the following URL with the following parameters with URL encoding (based on RFC 1738: ▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇/rfc/rfcl 738.txt) employed: <TBD> Example: <TBD> Airport agrees to maintain commonly accepted administrative, physical, technical, technical and procedural safeguards to protect the Interface Data in the possession of Airport against unauthorized access or disclosure.