<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>For Authors on Transactions on Computer Science and Intelligent Systems Research</title>
    <link>https://tcsisr.wepub.org/for-authors/</link>
    <description>Recent content in For Authors on Transactions on Computer Science and Intelligent Systems Research</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://tcsisr.wepub.org/for-authors/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Copyright &amp; Licence</title>
      <link>https://tcsisr.wepub.org/for-authors/copyright-licence/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://tcsisr.wepub.org/for-authors/copyright-licence/</guid>
      <description>&lt;p&gt;TCSISR proceedings are published on a gold open access basis. This page explains the copyright and licensing terms that apply to your paper.&lt;/p&gt;
&lt;h2 id=&#34;licence&#34;&gt;Licence&lt;/h2&gt;
&lt;p&gt;All articles published in TCSISR conference series are published under the &lt;strong&gt;CC BY-NC 4.0&lt;/strong&gt; user license. This licence allows others to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Remix, tweak, and build upon your work&lt;/strong&gt; for non-commercial purposes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Copy and redistribute&lt;/strong&gt; the material in any medium or format.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Under this licence, users must:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fee Information</title>
      <link>https://tcsisr.wepub.org/for-authors/fee-information/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://tcsisr.wepub.org/for-authors/fee-information/</guid>
      <description>&lt;p&gt;TCSISR operates on a gold open access basis. This page explains the fee structure for authors and conference organisers.&lt;/p&gt;
&lt;h2 id=&#34;no-publication-fees-for-authors&#34;&gt;No Publication Fees for Authors&lt;/h2&gt;
&lt;p&gt;The online publication of each proceedings volume is sponsored by the conference organisers. As a result, &lt;strong&gt;no additional publication fees are required from individual authors&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Authors are not required to pay any article processing charges (APCs), page charges, or submission fees to TCSISR.&lt;/p&gt;
&lt;h2 id=&#34;what-the-conference-organiser-sponsors&#34;&gt;What the Conference Organiser Sponsors&lt;/h2&gt;
&lt;p&gt;The conference organiser&amp;rsquo;s sponsorship covers:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Generative AI Policy</title>
      <link>https://tcsisr.wepub.org/for-authors/generative-ai-policy/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://tcsisr.wepub.org/for-authors/generative-ai-policy/</guid>
      <description>&lt;p&gt;TCSISR follows the COPE Ethics Guidelines and recognises the evolving role of generative AI tools in academic writing. This policy sets out our expectations for authors, reviewers, and editors.&lt;/p&gt;
&lt;h2 id=&#34;for-authors&#34;&gt;For Authors&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Disclosure required&lt;/strong&gt;: If you have used generative AI tools (such as ChatGPT or similar large language models) in the preparation of your manuscript — including for drafting text, generating figures, or translating content — you must describe the use in a statement in your manuscript.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Authorship&lt;/strong&gt;: Generative AI tools cannot be listed as authors. Authorship implies responsibility that can only be attributed to humans.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Accountability&lt;/strong&gt;: You remain fully responsible for the accuracy, originality, and integrity of your manuscript, regardless of any AI tools used.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Prohibited uses&lt;/strong&gt;: AI tools must not be used to fabricate data, generate fake citations, or misrepresent the work of others.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;for-reviewers&#34;&gt;For Reviewers&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Confidentiality&lt;/strong&gt;: Reviewers must not upload manuscripts or any part of them to generative AI tools, as this may breach confidentiality.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Disclosure&lt;/strong&gt;: If a reviewer uses AI tools to assist in the review process (for example, to check language), this must be disclosed to the editor.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Judgment&lt;/strong&gt;: The scientific judgment in the review must be the reviewer&amp;rsquo;s own. AI-generated comments must not replace the reviewer&amp;rsquo;s critical assessment.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;for-editors&#34;&gt;For Editors&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Editors must ensure that the peer review process remains confidential and that manuscripts are not shared with AI tools without author consent.&lt;/li&gt;
&lt;li&gt;Editors have the authority to reject manuscripts where undisclosed or inappropriate use of AI tools is suspected.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;compliance&#34;&gt;Compliance&lt;/h2&gt;
&lt;p&gt;This policy is aligned with the COPE Ethics Guidelines and the policies of major academic publishers. TCSISR reserves the right to update this policy as the technological and ethical landscape evolves.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Post-publication Changes</title>
      <link>https://tcsisr.wepub.org/for-authors/post-publication-changes/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://tcsisr.wepub.org/for-authors/post-publication-changes/</guid>
      <description>&lt;p&gt;After a manuscript is published online, it becomes the version of record. TCSISR allows authors to make changes only in cases of genuine scientific error. This page explains the types of changes that are permitted and the process for requesting them.&lt;/p&gt;
&lt;h2 id=&#34;types-of-post-publication-changes&#34;&gt;Types of Post-publication Changes&lt;/h2&gt;
&lt;h3 id=&#34;correction-erratum&#34;&gt;Correction (Erratum)&lt;/h3&gt;
&lt;p&gt;A correction is issued when a significant error is identified in a published paper that affects the scientific content or conclusions. The error must be attributable to the authors and not to the publisher.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Preparing Your Paper</title>
      <link>https://tcsisr.wepub.org/for-authors/preparing-your-paper/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://tcsisr.wepub.org/for-authors/preparing-your-paper/</guid>
      <description>&lt;p&gt;Authors must prepare their papers using the TCSISR MS Word template and convert them to PDF format before submission to the conference organiser.&lt;/p&gt;
&lt;h2 id=&#34;paper-format&#34;&gt;Paper Format&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Template&lt;/strong&gt;: Download the TCSISR MS Word template package.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Format&lt;/strong&gt;: The submission file must be in OpenOffice, Microsoft Word, or RTF document format.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Length&lt;/strong&gt;: Papers should typically be 6–8 pages, including references and appendices. Specific length requirements may be set by the conference organiser.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Font&lt;/strong&gt;: Use a 12-point font throughout.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Spacing&lt;/strong&gt;: Text should be single-spaced.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Italics&lt;/strong&gt;: Use italics rather than underlining (except for URL addresses).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Figures and tables&lt;/strong&gt;: Place all illustrations, figures, and tables within the text at the appropriate points, rather than at the end.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;required-elements&#34;&gt;Required Elements&lt;/h2&gt;
&lt;p&gt;Each paper must include:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
