We are always on the look out for new authors with quality writing skills & technical knowledge. If you have anything interesting to add about Web services, be it an article, tutorial or answering a knowledge base question, please Log in [0]first, and then Submit [0].

Please note that your story will not be published upon submission. As author you will have continuous edit access to your story. It will only be published online after a successful moderation [0] carried out by a set of content specialists. Moderation however does not apply to blogs, forums and comments.

Who can Submit?

Only authenticated users can submit stories. Therefore if you do not have a user account with OxygenTank, and you are interested in submitting a story kindly create an account [0] with us now! Template [0]]

Tutorials: A tutorial is an in depth how-to. They can contain images/code and a minimum number of 750 words (code excluded). Indicate the relative project(s)/programming language implementations and version(s) clearly in the content. List information of author(s), name, profession/designation, organization, email address etc. Tutorials may be attached as pdf/ppt. If so, then you must include an abstract/introduction of the tutorial on the body of the Submit page. [Template [0]]

Presentations: Attach your presentations as a odp/ppt and give a short introduction/abstract on the body of the submit page. Descriptive content with examples and code samples are encouraged. Accompanying notes for slides are also welcome. Indicate the relative project(s)/ programming language implementations and version(s) clearly. List information of author(s), name, profession/ designation, organization, email address etc.

Knowledge Base: Questions and answers, or any other material that do not fall in to the above categories maybe posted to the Knowledge Base. Mainly contain code and an average of 250 words (code excluded). Clearly note down the relative project(s)/programming language implementations and version(s), other dependent tools, environments etc. [Template [0]]

Case studies: The case study should describe a real life problem area, your analysis, and the course of action taken to remedy it. It may contain images/code with a minimum of 1500 words (excluding code). Indicate the relative project(s)/programming language implementations and version(s) clearly in the content. You may use fictitious names of companies and people if you have been requested to maintain confidentiality. [Template [0]]

White Papers: White papers are essays about a product, service, technology or methodology. It can include an explanation of how the technology was developed, how it is used, statistical analysis, etc. A white paper may be written in the Problem/Solution format. It may also emphasize business benefits. The word count should be at least 3000.

Template [0]]

Template [0]]

Template [0]]

Document Type Definitions [1], XML schemas [2] in a variety of languages (including RELAX [3], Schematron [4], the W3C Schema language [5], TREX [6], and others), Cascading Style Sheets [7], XSLT [8], and other style sheet specifications, Specification documents etc.