Publication and Corrections Policy

Technical publications on alikoker.com.tr follow defined procedures for publication, revision, verification, citation, and correction.

Publication Dates

published_at is the date on which a work was first made publicly available on this website. The source code, project or academic work on which an article is based may be older. The publication date is not replaced with the beginning date of the underlying work.

modified_at is updated when a substantial revision changes the technical scope, result, method or interpretation of the content. Pure formatting corrections and insignificant typographical changes are not necessarily treated as substantial revisions.

verified_at records when technical accuracy, links or version-dependent information were checked again without necessarily changing the article.

Source Work and Provenance

When an article is based on an earlier software implementation, academic project or professional study, the source period is stated separately in the text where relevant. The source-work period and the web-publication date remain distinct.

Institution-specific, project-specific, package, table and similar identifying names may be anonymized when security, confidentiality or professional obligations require it. Anonymization must not alter the technical behavior being explained.

Project records on this site represent work developed directly by the author or implemented as part of academic study. When an article grows out of such work, it is linked to the relevant project or experience page. First-hand observations, measurements, and design decisions are kept distinct from information derived from the literature wherever possible. The original publication dates of older articles are preserved; later substantial technical revisions are recorded through modified_at.

Citations and References

Where sources are used, human-readable references and machine-readable citation relationships are provided together when feasible. The canonical HTML page is the primary source. Markdown, BibTeX, RIS and CSL-JSON outputs are alternate representations of the same work.

The author, title, publication date, language and canonical URL in citation outputs are generated dynamically from the current database record. Historical redirect slugs must not be cited as canonical sources.

General engineering articles use TechArticle or another appropriate general content type. Works that have the characteristics of a formal academic publication use ScholarlyArticle. Technical blog posts are not automatically represented as scholarly articles.

Corrections

When a technical error is identified, the content is not silently given a misleading new publication date. The text is corrected, modified_at is updated according to the significance of the change, and the nature of the revision is explained when necessary. Removed content is handled through an appropriate HTTP status or permanent redirect.

Turkish and English versions represent the same underlying work. Their titles, summaries, bodies, references and dates are intended to remain technically equivalent.

Knowledge Assistant and AI Layer

The site's Knowledge Assistant produces retrieval- and knowledge-graph-based answers from published and accessible alikoker.com.tr content, Wiki concepts, content relations, taxonomy, editorial metadata, and structured references. An assistant response is not an independent source or a new publication; the canonical source remains the published page on which the answer is grounded.

When the available evidence is insufficient, the assistant may return partial information or state that no sufficiently supported answer was found. Generated responses do not automatically modify published content, create a new editorial record, or retroactively change authorship, publication dates, or verification dates.

For technical claims, readers should prefer the canonical content page surfaced by the assistant and the structured references on that page. No hidden search-engine-specific text or separate content copy is produced for the Knowledge Assistant; human readers, search systems, and the assistant operate on the same canonical content and semantic relations.

Editorial Principles

Technical content on this site is published with an emphasis on original expression and traceable sourcing. First-hand implementation, measurement, experimentation, and engineering decisions are distinguished from externally sourced information wherever practicable. New material is not created by copying another source's section order, examples, narrative structure, or original expression; merely replacing words in another text is not treated as independent synthesis.

Where the technical scope requires it, primary and authoritative sources are preferred. Claims that can change over time, such as standards, legislation, product behaviour, version information, research findings, or current technical characteristics, may be re-verified before publication or after a substantial revision. Information that cannot be adequately verified is not presented as settled fact; uncertainty or scope limitations are stated when relevant.

Source Hierarchy and Verification

Depending on the subject, preference is given to official legislation and competent-authority publications, standards organisations, peer-reviewed academic literature, original technical documentation, and primary project sources. Secondary sources may provide context, but they are not intended to be the sole basis for critical or time-sensitive claims.

A citation found inside another source is not treated as equivalent to direct verification of the cited work. References should materially support the relevant claim, links should resolve to persistent or canonical sources where practicable, and unnecessary duplicate references are avoided.

Correction Classes

Minor typographical, punctuation, or presentation changes that do not alter meaning do not change the original publication date and are not necessarily treated as substantial revisions. Changes affecting the technical result, method, scope, interpretation of evidence, or a reader's likely conclusion are treated as substantive revisions and reflected in modified_at.

Where content itself is unchanged but its accuracy, links, version dependencies, or references have been checked again, verified_at may be used. Correcting a material error does not retroactively replace the original publication date. When the nature of a correction is meaningful to readers, its scope may be described in the content or the relevant editorial record.

AI-Assisted Editorial Work

Artificial-intelligence tools may be used as assistants for research, comparison, language review, structuring, or identifying possible omissions. Such use does not transfer source verification or editorial responsibility to an automated system. Fabricated references, unsupported certainty, concealed rewriting of another work, or treating generated output as independent evidence are inconsistent with this publication policy.

Responsibility for the final published content remains with the author. Suggestions produced by automated systems are checked against appropriate sources where high accuracy is required, particularly for legislation, security, scientific findings, software versions, and numerical claims.

Copyright, Licensing and Reuse

Publication policy is distinct from the licence governing reuse. Academic citation and limited uses independently permitted by law are not the same as republishing an entire work or a substantial part of it. Reuse conditions for original material on this site are described in the Copyright and Terms of Use.

For open-source software, the project-level LICENSE file takes precedence. Rights expressly granted by an open licence are not narrowed by this general policy.

Version and Evidence Trails

Database dates, source-control history, persistent publication records, DOI metadata, cryptographic hashes, and trusted timestamps may be used when evaluating publication and revision history. Their purpose is not to rewrite the past but to make it possible, where necessary, to explain which version of a work existed at a particular time and which sources supported it.

This policy should be read together with the Copyright and Terms of Use: this page describes publication and verification practices, while the copyright page describes ownership and reuse conditions.

Reporting a Correction

Technical errors, source discrepancies and translation differences can be reported through the channels on the Contact page. Including the page URL, the relevant statement, the proposed correction and an available primary source supports review. Confidential information, personal data and unpublished institutional material should not be submitted.