Domuk No, not an
issue with
the PHP - I
was
responding
to "AJAX not
being cross
site is
annoying"
MaxMouse Really? i
thought that
would only
be important
if the user
had some
kind of
control over
where the
XML came
from, if you
hard code it
(As in a PHP
file)
wouldn't
that
eliminate
XSS attacks?
Domuk Yes, but
very, very
necessary.
AJAX
requests run
in the
context of
the browser,
there'd be
no security
if it was
cross-domain
.
MaxMouse AJAX not
being cross
site is
annoying,
all other
scripts can
be used in
that way,
having to
resort to
PHP to patch
it is a
shame.
These are the guidelines in regards to article submissions. These are the rules by which editors will edit and how writers should write articles so that submissions may be published on the website, available for all to see.
Author Responsibilities
The article must be the submitters original work, or the submitter must have permission from the original author, with the original author and/or reference to other publication(s) of article cited appropriately.
All code included in the article should be accurate and should compile. If it is later found to not work, the article will be deleted from the archives unless the code can accurately be replaced.
All links should be valid. If there is a typographical error in the link and the editor cannot determine the correct URL, the hyperlink will be removed.
It is strongly encouraged that sources the submitter uses to write the article is published/linked appropriately in the article. If the article directly quotes another source, it should be cited within the article and set off in quotation marks.
Plagiarism is considered the theft of other people's ideas and/or expressions, claiming that they are your own. We are more interested in peoples ideas (crap as they may be), rather than just reproducing content found elsewhere.
Editor Responsibilities
The editor reserves the right to format and layout the article as he/she sees fit. This is for the purpose of formatting the article appropriately so it fits into the format of the website.
The editor will correct typographical errors, grammatical errors, and other errors not directly involved in the content of the article. If the editor knows the content is incorrect the article may be rejected.
The editor will check to ensure the accuracy of code. By means of a compiler and possibly a field test, if the editor has access to the appropriate equipment.
OSIX reserves the right to edit/amend the article at any point in the future without prior notification of the original submitter/author.
If an article is rejected for any reason, the editor should contact the submitter to the best of his or her ability to give the user constructive feedback for improvement.
Editors are strongly encouraged not to edit their own submissions. The reason for this is that the editing process is meant to get feedback from people other than yourself, and thus, it would defeat the purpose.
These guidelines are intended to provide a baseline to guarantee the quality of the content provided on the site. We are always seeking to improve so if you have any ideas or suggestions post them via the feedback link.
Copyright Open Source Institute, 2006 
