Write, autoreview, editor, reviewer
3,129
edits
Submissions: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
We invite you to contribute to the Quantum Protocol Zoo. Your contribution can have one of the following forms: | We invite you to contribute to the Quantum Protocol Zoo. Your contribution can have one of the following forms: | ||
* '''Functionality | * '''Functionality page:''' describing a general task for a quantum network; | ||
* '''Protocol | * '''Protocol page:''' describing a particular protocol for a defined functionality. | ||
Each of | Each of pages 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 | Currently, submissions can be made via Google forms, see link below. In the Google form, you should specify which page (functionality or protocol page) 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. | 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. | ||
| Line 12: | Line 12: | ||
==Guidelines== | ==Guidelines== | ||
Protocol | Protocol page describes a specific protocol implementing the defined functionality (the "how"). Following are the section-wise guidelines for protocol pages for submission. Contributors may consider an example from the [[Protocol Library]] too if needed. | ||
</br> | </br> | ||
*'''Introductory paragraph''' gives a link to the functionality page, article on the example protocol and justify how the | *'''Introductory paragraph''' gives a link to the functionality page, article on the example protocol and justify how the | ||
| Line 20: | Line 20: | ||
**Avoid mathematical equations or notations. | **Avoid mathematical equations or notations. | ||
**Try to provide a real-life use case for the protocol example signing documents etc.. | **Try to provide a real-life use case for the protocol example signing documents etc.. | ||
*'''Tags''' are terms used to link several pages on the zoo similar or useful in certain aspect for the concerned | *'''Tags''' are terms used to link several pages on the zoo similar or useful in certain aspect for the concerned page. Categories to which the pages belong can also be mentioned here. | ||
** Available [[:Category:Categories|categories]] for the zoo | ** Available [[:Category:Categories|categories]] for the zoo pages can be found in the Navigation menu. | ||
*'''Assumptions''' describe the scenario in which the protocol will be successful and hence, it is necessary to be mentioned before one starts discussing the protocol. | *'''Assumptions''' describe the scenario in which the protocol will be successful and hence, it is necessary to be mentioned before one starts discussing the protocol. | ||
**List all the assumptions taken on the hardware setup or adversary in the given protocol. | **List all the assumptions taken on the hardware setup or adversary in the given protocol. | ||
| Line 45: | Line 45: | ||
can be divided into Preparation and Computation Stage. | can be divided into Preparation and Computation Stage. | ||
** Every stage (there can be only one stage in a protocol too) should have Inputs and Outputs for each party. | ** Every stage (there can be only one stage in a protocol too) should have Inputs and Outputs for each party. | ||
*'''Further Information''' This is a review section on all the similar protocol in terms of the method used. It can be skipped and different contributors can choose to write this section for various | *'''Further Information''' This is a review section on all the similar protocol in terms of the method used. It can be skipped and different contributors can choose to write this section for various pages uploaded on the zoo. | ||