Main Page: Difference between revisions

Main Page (view source)

Revision as of 21:14, 25 September 2018

1 byte added , 25 September 2018

→‎Functionality Description

Shraddha

Write, autoreview, editor, reviewer

3,129

edits

@@ Line 20: / Line 20: @@
 ===Functionality Description===
-This paragraph gives objective of the protocol in brief. We try to make it as general and complete as possible in order to cover a wide range of protocols under the same functionality and similar methods used. It should be able to give a clear idea about the task to be achieved and roles of the parties involved. No arbitrary names should be given to the parties. This would help avoid any confusion and also, make the functionality (roles) of the parties obvious. Eg. Blind Quantum Computing protocols should be written as Client-Server participating in the protocol, not Alice-Bob. We escape the use of fictional names unless needed, for e.g.- Key Distribution.
+This paragraph gives objective of the protocol in brief and should be kept as general and complete as possible in order to cover a wide range of protocols under the same functionality and similar methods used. It should be able to give a clear idea about the task to be achieved and roles of the parties involved. No arbitrary names should be given to the parties. This would help avoid any confusion and also, make the functionality (roles) of the parties obvious. Eg. Blind Quantum Computing protocols should be written as Client-Server participating in the protocol, not Alice-Bob. We escape the use of fictional names unless needed, for e.g.- Key Distribution.
   '''Tags:''' This block should include all different classes of categorization that this protocol belongs to, in the quantum library. Example- Two party crypto/ client-server/multi party(three or more), quantum enhanced classical/fully quantum functionality, specific/ universal task. It would also include the stage of the protocol.
 ===See Also===
 Any related formal description can be mentioned here. Tags and See Also are essential parts of this formal description. The peron in charge of writing the first draft of the formal description should make the attempt of adding as many tags and see also point as possible as this will eventually defines the structure of the Wikipedia.