Problem
docs/trademarks.md is not published anywhere. The legacy site served it at docs.tizen.org/trademarks/, but that site builds from the live branch, which has not moved since 2025-11-20. On the current site, samsungtizenos.com/docs/trademarks returns 404, as do /trademarks and /legal.
So the third-party trademark attribution notice is, in practice, no longer shown to readers.
Why it matters
The page exists by design. It was added in 57b3f30, "Add trademarks page and remove symbols from pages under open-source-project. Symbols: ®, ™, and ©" — individual pages dropped the symbols on the understanding that one page carried the attributions.
That premise still holds in the current corpus:
- 144 currently published documents (excluding generated API reference) still contain ®, ™, or ©.
- Third-party marks appear throughout: Wi-Fi 20,883 occurrences, Java 2,235, OpenGL 1,757, Windows 1,702, Intel 652, EGL 609, macOS 559, Vulkan 226, NVIDIA 219, UNIX 218, Chrome 196, WebGL 109, Apple 107, Android 93, Oracle 63.
The new site has no substitute. Its terms-of-use covers only Samsung's own intellectual property ("we and/or our licensors are the sole owners of the Site and all of its content"), with no third-party attributions. content-license.md in this repository is not one either — its trademark clause is scoped to "logos, trademarks ... contained on tizen.org websites", i.e. Tizen and Samsung brand features.
How it happened
The tizen.org.v2.docs pipeline copies files by slicing the TOCs it reads. docs/trademarks.md has an entry in docs/application/toc_all.md, but that TOC is consumed only through prefix slices (/application/dotnet/{get-started,guides,reference}/, /application/native/{guides,reference}/, /application/web/{guides,reference,tutorials}/), and /trademarks.md falls in none of them. It is not among the pipeline's seven fixed-file inputs either, and it appears zero times in the committed source manifests.
The pipeline had already noticed something: scripts/pipeline/reports/source-analysis-20260520-132346.json lists docs/trademarks.md with "occurrences": 5 as an unresolved reference.
Options
- Add wiring in
tizen.org.v2.docs — a fixed-file input, or fold it into the misc section — so the page is published under /docs/... again. This keeps the file as the single source of truth.
- Move the content to the site's footer legal group, alongside
terms-of-use and privacy-policy. Those are WordPress pages with no route or file in either repository, so this needs whoever owns them. Once done, docs/trademarks.md can be removed.
Note
This is a judgement for whoever owns the docs and, if relevant, legal. This issue only sets out the facts.
docs/get-started.md, docs/glossary.md, and docs/menu.yaml were unreachable in the same way and are removed in #2380. trademarks.md was deliberately left out of that PR because of the above.
Problem
docs/trademarks.mdis not published anywhere. The legacy site served it atdocs.tizen.org/trademarks/, but that site builds from thelivebranch, which has not moved since 2025-11-20. On the current site,samsungtizenos.com/docs/trademarksreturns 404, as do/trademarksand/legal.So the third-party trademark attribution notice is, in practice, no longer shown to readers.
Why it matters
The page exists by design. It was added in 57b3f30, "Add trademarks page and remove symbols from pages under open-source-project. Symbols: ®, ™, and ©" — individual pages dropped the symbols on the understanding that one page carried the attributions.
That premise still holds in the current corpus:
The new site has no substitute. Its
terms-of-usecovers only Samsung's own intellectual property ("we and/or our licensors are the sole owners of the Site and all of its content"), with no third-party attributions.content-license.mdin this repository is not one either — its trademark clause is scoped to "logos, trademarks ... contained on tizen.org websites", i.e. Tizen and Samsung brand features.How it happened
The
tizen.org.v2.docspipeline copies files by slicing the TOCs it reads.docs/trademarks.mdhas an entry indocs/application/toc_all.md, but that TOC is consumed only through prefix slices (/application/dotnet/{get-started,guides,reference}/,/application/native/{guides,reference}/,/application/web/{guides,reference,tutorials}/), and/trademarks.mdfalls in none of them. It is not among the pipeline's seven fixed-file inputs either, and it appears zero times in the committed source manifests.The pipeline had already noticed something:
scripts/pipeline/reports/source-analysis-20260520-132346.jsonlistsdocs/trademarks.mdwith"occurrences": 5as an unresolved reference.Options
tizen.org.v2.docs— a fixed-file input, or fold it into themiscsection — so the page is published under/docs/...again. This keeps the file as the single source of truth.terms-of-useandprivacy-policy. Those are WordPress pages with no route or file in either repository, so this needs whoever owns them. Once done,docs/trademarks.mdcan be removed.Note
This is a judgement for whoever owns the docs and, if relevant, legal. This issue only sets out the facts.
docs/get-started.md,docs/glossary.md, anddocs/menu.yamlwere unreachable in the same way and are removed in #2380.trademarks.mdwas deliberately left out of that PR because of the above.