The OpenDocument XML.org web site is not longer accepting new posts. Information on this page is preserved for legacy purposes only. For current information on ODF, please see the OASIS OpenDocument Technical Committee.

Diff for Editorial guidelines

Tue, 2006-07-11 20:32 by adminSun, 2006-06-25 19:40 by admin
Changes to Body
Line 1Line 1
-
<p><span lang="EN"><a href="http://xml.org"><font size="2">XML.org</font></a><font size="2"> is based on trust in a community of participants that behave in a manner that helps others. </font></span></p>
+
<p><span lang="EN"><a href="http://xml.org"><font size="2">XML.org</font></a><font size="2"> is based on trust in a community of participants that behave in a manner that helps others. </font></span></p>
-
<p><span lang="EN"><span lang="EN"><font size="2"></font></span></span></p>
+
<p><span lang="EN"><span lang="EN"><font size="2"></font></span></span></p>
-
<p><span lang="EN"><span lang="EN"></span><font size="2">OASIS reserves the right to remove any content that it deems inaccurate, inappropriate, misleading, not directly related to the Focus Area topic, or not in keeping with the mission of the site. Those who violate this editorial policy repeatedly may be prohibited from future participation. See our <a href="http://opendocument.xml.org/code-of-conduct">Code of Conduct</a> for more information.<br /> </font></span></p>
+
<p><span lang="EN"><span lang="EN"></span><font size="2">OASIS reserves the right to remove any content that it deems inaccurate, inappropriate, misleading, not directly related to the Focus Area topic, or not in keeping with the mission of the site. Those who violate this editorial policy repeatedly may be prohibited from future participation. See our <a href="http://dita.xml.org/code-of-conduct">Code of Conduct</a> for more information.<br /> </font></span></p>
-
<p><span lang="EN"></span></p>
+
<p><span lang="EN"></span></p>
-
<p><span lang="EN"><font size="2"></font></span></p>
+
<p><span lang="EN"><font size="2"></font></span></p>
-
<p><span lang="EN"><font size="2"></font></span></p>
+
<p><span lang="EN"><font size="2"></font></span></p>
-
<p><span lang="EN">
+
<p><span lang="EN">
-
<p><span lang="EN"></span><span lang="EN"><font size="3"><font size="2"></font>
+
<p><span lang="EN"></span><span lang="EN"><font size="3"><font size="2"></font>
-
<p><strong><font color="#6699cc"><span style="font-weight: bold;"><font size="2">Links and Attribution</font></span></font></strong></p>
+
<p><font color="#6699cc"><span style="font-weight: bold;"><font size="2">Links and Attribution</font></span></font></p>
-
</font>
+
</font>
-
<p><span lang="EN"><span lang="EN"><font size="2">XML.org is not intended to serve as a repository for materials, nor to violate the rights of any third party. When referencing external publications (including press releases, white papers, books, etc.), a user should not insert or republish a full document, even if they own the document.&nbsp; Instead, insert only excerpts from, or links to, such documents. If you are not the owner of a document, be sure to provide an excerpt that is sufficiently brief to fall within the &quot;fair use&quot; exemption under copyright law, or create your own summary. In addition, authors should not relinquish copyrights on their materials.</font></span></span></p>
+
<p><span lang="EN"><span lang="EN"><font size="2">XML.org is not intended to serve as a repository for materials, nor to violate the rights of any third party. When referencing external publications (including press releases, white papers, books, etc.), a user should not insert or republish a full document, even if they own the document.&nbsp; Instead, insert only excerpts from, or links to, such documents. If you are not the owner of a document, be sure to provide an excerpt that is sufficiently brief to fall within the &quot;fair use&quot; exemption under copyright law, or create your own summary. In addition, authors should not relinquish copyrights on their materials.</font></span></span></p>
-
<p><font size="2">When referencing XML.org content on other sites or documents, individuals should respect the source of the material and include appropriate attribution.<br /></font></p>
+
<p><font size="2">When referencing XML.org content on other sites or documents, individuals should respect the source of the material and include appropriate attribution.<br /></font></p>
-
<p><font size="2"></font></p>
+
<p><font size="2"></font></p>
-
<span lang="EN"><span lang="EN">
+
<span lang="EN"><span lang="EN">
-
<p><font color="#6699cc"><strong><font size="2">Collaborating on Specifications</font></strong></font></p>
+
<p><font color="#6699cc"><strong><font size="2">Collaborating on Specifications</font></strong></font></p>
-
<font size="2"><font size="2">
+
<font size="2"><font size="2">
-
<p>XML.org Focus Area Community pages are intended to allow readers to benefit from one another's experiences by articulating use cases, collaborating on best practices, and sharing information on products, services, news, resources, and events. </p>
+
<p>XML.org Focus Area Community pages are intended to allow readers to benefit from one another's experiences by articulating use cases, collaborating on best practices, and sharing information on products, services, news, resources, and events. </p>
-
<p>It is important to note, however, that actual work on creating or revising an <a href="http://www.oasis-open.org/specs/index.php">OASIS Standard</a> or specification must take place within an <a href="http://www.oasis-open.org/committees/committees.php">OASIS Committee</a>, under the open <a href="http://www.oasis-open.org/committees/process.php">OASIS Technical Process</a>. This process, which governs issues such as transparency, contributions, licensing, participation, and disclosure, assures that OASIS Standards remain widely available and safe to implement, produced in an open, democratic, and accountable method.</p>
+
<p>It is important to note, however, that actual work on creating or revising an <a href="http://www.oasis-open.org/specs/index.php">OASIS Standard</a> or specification must take place within an <a href="http://www.oasis-open.org/committees/committees.php">OASIS Committee</a>, under the open <a href="http://www.oasis-open.org/committees/process.php">OASIS Technical Process</a>. This process, which governs issues such as transparency, contributions, licensing, participation, and disclosure, assures that OASIS Standards remain widely available and safe to implement, produced in an open, democratic, and accountable method.</p>
-
<p>All those who wish to participate in standards development or more closely observe this work are strongly encouraged to <a href="http://www.oasis-open.org/join/">join OASIS</a>. A variety of membership levels are offered to assure that everyone affected by standards may contribute to their creation.</p>
+
<p>All those who wish to participate in standards development or more closely observe this work are strongly encouraged to <a href="http://www.oasis-open.org/join/">join OASIS</a>. A variety of membership levels are offered to assure that everyone affected by standards may contribute to their creation.</p>
-
<p>For those who would like to provide feedback on OASIS work, a &quot;comment&quot; form is provided on each <a href="http://www.oasis-open.org/committees/committees.php">OASIS Committee</a> homepage. Feature requests for additions or changes to specifications should be directed through these comment forms. All comments are documented and reviewed by the appropriate OASIS Committee members and publicly archived.</p>
+
<p>For those who would like to provide feedback on OASIS work, a &quot;comment&quot; form is provided on each <a href="http://www.oasis-open.org/committees/committees.php">OASIS Committee</a> homepage. Feature requests for additions or changes to specifications should be directed through these comment forms. All comments are documented and reviewed by the appropriate OASIS Committee members and publicly archived.</p>
-
</font></font></span></span></span></p>
+
</font></font></span></span></span></p>
-
&nbsp;<br />See the <a href="http://fa.xml.org/styleguide">XML.org Focus Area Styleguide</a> for more information.</span></p>
+
&nbsp;<br />See the <a href="http://dita.xml.org/styleguide">XML.org Focus Area Styleguide</a> for more information.</span></p>
 
<p>&nbsp;</p>
 
<p>&nbsp;</p>
Revision of Sun, 2006-06-25 19:40:

Editorial guidelines

XML.org is based on trust in a community of participants that behave in a manner that helps others.

OASIS reserves the right to remove any content that it deems inaccurate, inappropriate, misleading, not directly related to the Focus Area topic, or not in keeping with the mission of the site. Those who violate this editorial policy repeatedly may be prohibited from future participation. See our Code of Conduct for more information.

Links and Attribution

XML.org is not intended to serve as a repository for materials, nor to violate the rights of any third party. When referencing external publications (including press releases, white papers, books, etc.), a user should not insert or republish a full document, even if they own the document.  Instead, insert only excerpts from, or links to, such documents. If you are not the owner of a document, be sure to provide an excerpt that is sufficiently brief to fall within the "fair use" exemption under copyright law, or create your own summary. In addition, authors should not relinquish copyrights on their materials.

When referencing XML.org content on other sites or documents, individuals should respect the source of the material and include appropriate attribution.

Collaborating on Specifications

XML.org Focus Area Community pages are intended to allow readers to benefit from one another's experiences by articulating use cases, collaborating on best practices, and sharing information on products, services, news, resources, and events.

It is important to note, however, that actual work on creating or revising an OASIS Standard or specification must take place within an OASIS Committee, under the open OASIS Technical Process. This process, which governs issues such as transparency, contributions, licensing, participation, and disclosure, assures that OASIS Standards remain widely available and safe to implement, produced in an open, democratic, and accountable method.

All those who wish to participate in standards development or more closely observe this work are strongly encouraged to join OASIS. A variety of membership levels are offered to assure that everyone affected by standards may contribute to their creation.

For those who would like to provide feedback on OASIS work, a "comment" form is provided on each OASIS Committee homepage. Feature requests for additions or changes to specifications should be directed through these comment forms. All comments are documented and reviewed by the appropriate OASIS Committee members and publicly archived.

 
See the XML.org Focus Area Styleguide for more information.

 

XML.org Focus Areas: BPEL | DITA | ebXML | IDtrust | OpenDocument | SAML | UBL | UDDI
OASIS sites: OASIS | Cover Pages | XML.org | AMQP | CGM Open | eGov | Emergency | IDtrust | LegalXML | Open CSA | OSLC | WS-I