Submissions: Difference between revisions

Jump to navigation Jump to search
365 bytes removed ,  14 November 2018
m
mNo edit summary
Line 72: Line 72:
==Extra Information==
==Extra Information==
*Greek alphabets to be used for quantum states and Latin alphabets are to be used for classical states.
*Greek alphabets to be used for quantum states and Latin alphabets are to be used for classical states.
*If the paper used for given description has multiple protocols, pick the most general one and if needed one can merge it. The concerned paper thus goes in the relevant papers section mentioning the other versions of protocols as its one line description.
*If the paper used for given description has multiple protocols, pick the most general one and if needed one can merge it too. The concerned paper thus goes in the Discussion section mentioning the other versions of protocols as its one line description.
*Only published papers with proper security proof are to be considered. One that is easy to summarize and extract pseudo code from.
*Only published papers with proper security proof are to be considered. One that is easy to summarize and extract pseudo code from.
*Every formal description should contain the above mentioned structure in order to make it an independent page as we cannot direct the user to go through the general functionality description and then the concerned formal description.
*Every formal description should contain the above mentioned structure in order to make it an independent page even though we provide a link to the concerned functionality page.
*General Functionality Description is not needed for every protocol. One can write as many different versions of formal descriptions, depending on how different the protocols are in terms of resources used.
*General Functionality Description file will be written for a functionality once it accommodates more than two different types of protocols.
*Title of the formal description should reflect the functionality/branch of the functionality discussed in the concerned formal description. If not so, the main functionality should at least be included in tags such that when one searches for the concerned functionality he/she has the list of all the different versions in the search result.
*Title of the formal description should reflect the functionality and the method/network stage used in the concerned protocol. If not so, the main functionality should at least be included in tags such that when one searches for the concerned functionality he/she has the list of all the different versions in the search result.
*Only if the number of different formal descriptions for a functionality grows too big such that one can come up with a structure to categorize them in terms of resources, a general functionality description shall be designed.


Link for tex file of skeleton for the above format:[[yet to be uploaded|yet to be uploaded (a downloadable link)]]
Link for tex file of skeleton for the above format:[[yet to be uploaded|yet to be uploaded (a downloadable link)]]
Write, autoreview, editor, reviewer
3,129

edits

Navigation menu