You are looking at the HTML representation of the XML format.
HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format.
To see the non HTML representation of the XML format, set format=xml.
See the complete documentation, or
API help for more information.
<?xml version="1.0"?>
<api>
<query-continue>
<allpages gapcontinue="Schedule" />
</query-continue>
<query>
<pages>
<page pageid="53" ns="0" title="Registration">
<revisions>
<rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">__NOTOC__
<!-- Registration -->
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"
<!-- Registration -->
| class="MainPageBG" style="width:100%; border:1px solid #f36766; background:#f9d6c9; vertical-align:top; color:#000;" |
{| id="mp-left" style="width:100%; vertical-align:top; background:#f9d6c9;"
| style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#f5baa3; font-family:inherit; font-size:120%; font-weight:bold; border:1px solid #f36766; text-align:left; color:#000; padding:0.2em 0.4em;">Registration Benefits</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">
* Access to all technical program activities with the exception of the tutorials, which have a separate fee.
* Access to all social program activities, including one welcome reception ticket and one gala dinner ticket.
* Access to lunch and coffee-break refreshments.
* Coverage for up to 2 papers. Cost for extra paper submissions will be announced later.
* 18 months of ISIF membership.
Student registrations provide all the benefits of regular registrations, but cover only one paper submission.
</div>
|-
|}
| style="border:1px solid transparent;" |<br />
|-
{{Organisation}}
__NOTOC____NOEDITSECTION__</rev>
</revisions>
</page>
<page pageid="51" ns="0" title="Review guidelines">
<revisions>
<rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve"><!-- ISIF Authors guidelines -->
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"
<!-- ISIF Authors guidelines -->
| class="MainPageBG" style="width:100%; border:1px solid #a3babf; background:#f5fdff; vertical-align:top; color:#000;" |
{| id="mp-left" style="width:100%; vertical-align:top; background:#e7f7e76;"
| style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:3px; background:#ceecf2; font-family:inherit; font-size:125%; font-weight:bold; border:1px solid #a3babf; text-align:left; color:#000; padding:0.2em 0.4em;">Review Process</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">
Fusion 2016 welcomes the submission of papers covering the topics listed in the [http://fusion2016.org/Call_For_Papers call for papers]. All submitted papers will undergo a thorough review process; each paper will be refereed by at least three experts in the field based on relevance, originality, significance, quality, and clarity.
Fusion 2016 follows a single-blind review process. All submissions must include information that identifies its authors.
|-
|}
| style="border:1px solid transparent;" |<br />
|-
<!-- ISIF Reviewer guidelines -->
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"
<!-- ISIF Reviewer guidelines -->
| class="MainPageBG" style="width:100%; border:1px solid #d6bdde; background:#f7eff7; vertical-align:top; color:#000;" |
{| id="mp-left" style="width:100%; vertical-align:top; background:#e7f7e76;"
| style="padding:2px;" | <h2 id="mp-tfa-h2" style="margin:4px; background:#e7deef; font-family:inherit; font-size:125%; font-weight:bold; border:1px solid #d6bdde; text-align:left; color:#000; padding:0.2em 0.4em;">ISIF Reviewer guidelines</h2>
|-
| style="color:#000;" | <div id="mp-tfa" style="padding:2px 5px">
* R1 - Reviewers must be technically competent in the specific technical area addressed by the paper under review. In particular, if a reviewer accepts to review a paper, he/she must accept to read it in sufficient depth to understand it and to refer to related earlier works reported in peer-reviewed journals (if any, and if necessary).
* R2 - Reviewers must employ professional language, strictly avoid ad hominem attacks, and avoid matters of literary taste, unless the authors’ literary style subverts technical clarity (excessive verbosity, for instance).
* R3 - Reviewers must provide a fair appreciation of the technical content of the paper, and also give some recommendations for its improvement whenever possible.
* R4 - Reviewers must have no personal, nor professional conflict of interest with the authors and must not try to block the publication, only if the technical content of the paper is proved incorrect. Every negative criticism about the paper must only be substantiated by sound scientific arguments.
* R5 - Reviewers must alert for possible plagiarism as defined by the IEEE: “...the reuse of someone else's prior ideas, processes, results, or words without explicitly acknowledging the original author and source”.
* R6 - Reviewers can recommend a few main references(s) related to the paper that have been omitted by the author(s), if any. This recommendation must be done sparingly and with carefulness. It must not be done to inflate the reviewer’s own bibliometric score, nor the scores of their associates.
* R7 - Reviewers must not try to impose their own ideas to modify the original direction of the paper under review. If the technical content of the paper is correct and if reviewers dislike the ideas developed in the paper, reviewers must accept the paper and they are free to submit later their own paper on the same topic once the accepted paper has been published.
* R8 - Reviewers are not allowed to diffuse or share by any means the content of the paper that they have accepted to review, nor use its technical content (even partially) for their own purposes.
</div>
|}
| style="border:1px solid transparent;" |<br />
|-
{{Organisation}}
__NOTOC____NOEDITSECTION__</rev>
</revisions>
</page>
</pages>
</query>
</api>