Interface Specification Clause Samples

Interface Specification. The functional specification prepared by Seller that defines the radio frequency interface, logical and physical protocols necessary for Mobile Exchange Unit (MXU) interoperability with the Space System. It does not include the Voice Encoding Algorithm necessary for complete interoperability with the IRIDIUM Communications System.

Interface Specification. Unless otherwise agreed by the parties in ----------------------- writing, ACS shall not knowingly make any changes to the Products which obsoletes the interface specification applicable to the then current version of the Products and the then current version of the Xerox 4890 and 4635 Printers, the Docutech, or any other Xerox product which Xerox has notified ACS in writing are being used by end-user customers in connection with the Products.

Interface Specification. Seller agrees to develop and sell MXUs to third parties and to license to responsible and competent suppliers acceptable to Seller the rights to use the information in the MXU Interface Specification and the Voice Encoding Algorithm to the extent essential to manufacture and sell IRIDIUM MXU's, all pursuant to reasonable terms and conditions mutually acceptable to Seller and such third parties.

Interface Specification. The functional specification prepared by Seller that defines the radio frequency interface, logical, and physical protocols necessary for subscriber unit (voice, data, facsimile) interoperability with the Space System. It does not include the Voice Encoding Algorithm necessary for complete interoperability with the IRIDIUM Communication System.

Interface Specification. The preliminary interface specification for GRALAF is shown in Table 12. The purpose of the API is to ingest data, mainly network model, and generate the graph model for further analysis via GRALAF algorithms. Moreover, the results will be provided to the end user(s) or other elements in the architecture. Method URL Required Data Objects Returned Data Object GET liability/gralaf/graph /probability/node/<nodeID> nodeID Probability value GET liability/gralaf/graph /probability/link/<sourceNodeID>/<targetN odeID> sourceNodeID targetNodeID JSON object GET liability/gralaf/graph/liabilityList --- JSON object [1] ▇▇▇▇ ▇. ▇▇▇▇▇▇▇▇, “Liability and computer security: Nine principles.” In European Symposium on Research in Computer Security, pp. 231-245. Springer, Berlin, Heidelberg, 1994.‌ [2] 5GPPP, “5G Infrastructure Public Private Partnership (5GPPP) the next generation of communication networks and services,” ▇▇▇▇://▇▇▇▇▇▇▇▇▇▇▇▇▇.▇▇/wp-content/uploads/5GPPP- brochure-draft02.pdf. [3] ▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇▇, ▇▇▇▇▇▇ ▇▇▇, ▇▇▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇ ▇▇▇▇▇▇, ▇▇▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇, ▇▇▇▇▇▇ ▇▇▇▇▇▇, ▇▇▇▇ ▇▇▇▇▇▇▇▇▇▇, “The roadmap to 6G security and privacy", IEEE Open Journal of the Communications Society, 2021. [4] ▇. ▇▇▇▇▇▇▇▇, ▇. ▇▇▇, and ▇. ▇▇▇, “6G and beyond: The future of wireless communications systems,” IEEE Access, vol. 8, pp. 133 995–134 030, 2020. [5] ITU-T FG-NET-2030. “Network 2030 A blueprint of technology, applications and market drivers towards the year 2030 and beyond”, May 2019, online: ▇▇▇▇▇://▇▇▇.▇▇▇.▇▇▇/en/ITU- T/focusgroups/net2030/Documents/White_Paper.pdf. [6] SMA, “Network slicing use cases requirements,” ▇▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇/futurenetworks/wp- content/uploads/2020/01/2.1Network-Slicing-Use-Case-Requirements-Booklet-1.pdf, 2020. [7] ▇. ▇▇▇▇▇▇, “The legal and political battles of Y2K,” IEEE Annals of the History of Computing, 2020. [8] EC Report with recommendations to the Commission on a civil liability regime for artificial intelligence, ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇▇▇▇.▇▇/doceo/document/A-9-2020-0178_EN.html [9] EC Report on the safety and liability implications of Artificial Intelligence, the Internet of Things and robotics, ▇▇▇▇▇://▇▇.▇▇▇▇▇▇.▇▇/info/sites/info/files/report-safety-liability-artificial- intelligence-feb2020_en_1.pdf [10]ETSI NFV Release 4 Security; Security Management Specification, ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇▇.▇▇▇/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=58648 [11]▇. ▇▇▇▇▇▇▇▇, ▇.-▇. Louisot, and ▇. ▇▇▇▇, Risk quantification - Management Diagnosis and Hed...

Interface Specification. The LASM Referencing Service and the LASM Analysis Service allow MANIFEST elements to be exchanged data. Their interfaces are shown in Table 11. They will be designed to enable API based communication from the MANIFEST Class and Instance in the INSPIRE-5Gplus architecture. Table 11 APIs of the LASM Referencing Service and the LASM Analysis Service REST endpoint Method URL Required Data Objects Returned Data Object Referencin g Service GET /referencingpolicy -- Text file with SWRL rules POST /referencingpolicy Text file with SWRL rules -- POST /manifestclass Multipart(zip) JSON(string :manifestclass_ID, string: manifestclass_status) PUT /manifestclass/{ID} -- JSON(string: manifestclass_ID, string: manifestclass_status) GET /manifestclass/{ID}/status -- Status in plaintext GET /manifestclass/{ID}/file -- Manifestclass_JSON /manifestclass/findby JSON(map: key/criteria) Array(string: manifestclass_ID) Analysis Service POST /manifestinstance/ JSON(string: manifestclass_ID, string: instance_ID, JSON: instanciation) -- PUT /manifestinstance/{instance_ID} JSON(map: metrics/action) -- GET /manifestinstance/{instance_ID} JSON(map: metrics/value) GET /manifestinstance/{instance_ID}/file --

Interface Specification. Subject to the remainder of this section:

Interface Specification. Network Device Class Power Management Reference Specification, Version 1.0a OpenHCI: Open Host Controller Interface Specification for USB, Release 1.0a OnNow and Power Management Web page PC Card and CardBus Guidelines, Version 1.1 PCI Bus Power Management Interface Specification, Revision 1.1 PCI Bus Power Management Interface Specification, Revision 1.0 PCI Hot-Plug Specification, Revision 1.0 PCI IDE Controller Specification, Revision 1.0 PCI Local Bus Specification, Revision 2.2 (PCI 2.2)

Interface Specification. One Interface State Model Figure 1: One interface state model Table 3: Modes on the unit