Submissions
We invite you to contribute to the Quantum Protocol Zoo. Your contribution can have one of the following forms:
- Functionality file: describing a general task for a quantum network;
- Protocol file: describing a particular protocol for a defined functionality.
Each of the files has a predefined format, see below. To keep the wiki consistent, we kindly ask you to follow the guidelines on the format.
Currently, submissions can be made via Google forms, see link below. In the Google form you should specify which file (functionality or protocol file) you would like to submit. Currently, we accept submissions in plain text (.txt file), supplemented with .png, .jpg or .pdf for figures. Note that Quantum Protocol Zoo accepts only published work. Submissions will be considered by the Quantum Protocol Zoo team and the final decision on acceptance resides with the team.
What is more, you can submit a request for an article in the Discussion section on this page. Such a request will be considered and, if accepted, added by to the wiki by the team. You are welcome to express your general comments in the Discussion to make the wiki more user-friendly.
Link to Google Form
https://forms.gle/ANokaD4iCzwvYjdb6
Format Guidelines
Functionality File
Functionality file describes a general task which can be realized in a quantum network (the "what"). It consists of the following sections.
- Functionality Description A lucid definition of functionality in discussion.
- Tags Any related page or list of protocols is connected by this section
- Use Case (if available) compares security, efficiency and practicality of quantum protocols with its available classical analogues; connects protocols with real world applications.
- Protocols List of different types of example protocol achieving the functionality (Each protocol in this list is written in the format given below) depending on the task achieved or Network Stages required to achieve the same functionality
- Properties All properties that should be satisfied by any protocol achieving the concerned functionality and other common terminologies used in all the protocols.
- Further Information Any issue that could not be addressed or find a place in the above sections or any review paper discussing a feature of various types of protocols related to the functionality.
Protocol File
Protocol file describes a specific protocol implementing the defined functionality (the "how"). It consists of the following sections.
- Link to the corresponding functionality together with short description of the method used and properties satisfied by a protocol.
- Tags Any related page or list of protocols is connected by this section
- Assumptions It describes the setting in which the protocol will be successful. Any assumption on the setup for the protocol below is listed in this section.
- Outline A non-mathematical detailed outline which provides a rough idea of the concerned protocol. A figure is accommodated for most protocols.
- Notation Connects the non-mathematical outline with further sections.
- Hardware requirements Order of digits related to threshold values, QBit Error Rate (QBER), parameters, etc.. are illustrated in this section.
- Properties A list of important information extracted from the protocol such as, parameters (threshold values), security claim, success probability, etc..
- Pseudocode Mathematical step-wise protocol algorithm helpful to write a subroutine.
- Further Information Any useful information that could not find its place in the above description goes here. Also, some pages on protocols might include short description as below for list of protocols in the same class of functionality and network stage that are easy to interpret after reading the concerned formal description (or are variants of the protocol discussed above):
- Theoretical Papers:
- How is it different from the above protocol
- Requirements
- Security
- Experimental Papers:
- Which paper or protocol does it implement
- Benchmark values for this demonstration