Welcome to the experimental Linked Data wrapper for iFixit, the community repair wiki. Every device dereferences to an RDF description: iFixit's repairability score, which kinds of replacement part are sold for it, the battery capacity its teardown reports, how many repair guides exist, and where the device sits in iFixit's device tree.
This is a live view that queries the iFixit API on request. Nothing is stored beyond a cache bounded to 24 hours.
iFixit's wiki content is CC BY-NC-SA 3.0. The NC matters: this licence does not permit commercial reuse, and derivatives must be shared alike. Every document served here states it, and anything you build from this data inherits it. That is a sharper restriction than the other sources in this family, which are open-licence or public-sector.
The content is community-contributed and unverified. A repairability score is iFixit's own teardown assessment — an editorial judgement by repairers — and is not comparable with the EU energy label's repairability class or the French indice de durabilité, both computed from published scoring grids.
iFixit documents what its community has taken apart, which is a small and well-known subset of any product register. Of 40 smartphone models sampled from the EU's EPREL register in August 2026, none had an iFixit device page: that register is dominated by long-tail rugged and budget brands, and iFixit is not. Absence here is absence of a teardown, never absence of a device.
Browsing starts at device/Root, the top of iFixit's
device tree: every device carries skos:broader and
skos:narrower, so the tree walks in both directions once you have
somewhere to begin — device/Root → device/Phone → device/iPhone
→ device/iPhone 12. The dataset description at
index names it too, so a client that dereferences that rather
than reading this page finds the same way in.
5,000 mAh. A naive
parser reads that as 000; this one consumes the separator and
sanity-bounds the result. The document flags the figure as read from prose.
These few things — four products and a company — are used as examples
across the whole linked-* family, so one thing can be followed
from register to register. Nothing appears in all of them: each entry
below is an overlap between two or three, and the gaps are as informative as
the matches.
TQ75LS03FWUXXCUXXC regional suffix is truncated — the two registers designate the same television differently, which is the single biggest obstacle to joining them.6921081531228SM-S938BNL. It is the exception. For the large manufacturers the two registers name different legal persons entirely: EPREL lists AB Electrolux (SE), Samsung Electronics (UK) Limited, Haier Iberia, SLU (ES) and Candy Hoover Group SRL (IT), while the French registers name the arm that places goods on the French market. The two record different roles — who filed the energy label, versus who carries the French end-of-life obligation — so companies must not be joined by name. Even here there is a wrinkle worth seeing: one company holds two Immatriculations, and the battery stream sits on the second, so reading the first alone would suggest Fairphone has no battery obligation.These are links between landing pages only. The RDF each wrapper serves asserts no cross-wrapper statement: a join between two registers is a claim that needs evidence, and it belongs to whoever makes it, not to the data.
Content negotiation: suffix wins, then Accept, then HTML.
Add .ttl, .nt, .rdf, .jsonld,
.json or .html to any resource above.