Editorial, sourcing, and corrections policy
How RFID.me documents technical claims and keeps its open knowledge base accountable.
Authorship
Articles are published under the RFID.me organization unless a page explicitly names another author. An organization byline does not imply an individual reviewer, certification, or professional qualification.
Sources
We prefer primary material: standards-body records, protocol specifications, vendor manuals, and original technical documentation. Articles list important sources where factual claims depend on a standard, product behaviour, compatibility detail, or time-sensitive figure. Internal RFID.me links are labelled as related explanations, not presented as independent primary evidence.
Some standards are paywalled or available only as catalogue records. A link to an official record identifies the governing document; it does not imply that RFID.me republishes the specification.
Publication and update dates
Visible dates and structured-data dates are generated from the repository history for the content files that produce each route. The publication date is the earliest trustworthy content commit available in that history, and the modification date is the latest content-affecting commit. Sitemap dates use the same route record. When a dynamic route shares one template and data source with many entries, we omit a publication date unless the history can establish it for that individual entry.
Review and maintenance
Content is updated when standards, implementations, or explanations change. A recent modification date means the underlying route content changed; it is not a claim that a named expert performed a formal review on that date.
Corrections
If you find an error, include the page URL, the statement at issue, and a primary source supporting the correction in a GitHub report or contact [email protected]. Corrections are applied to the public content history rather than hidden behind an invented review record.