[{"titre":"Nixing the Fix: Warranties, Mag-Moss, and restrictions on repairs","pubDate":"Tue, 06 Oct 2026 08:06:23 +0200","id":3199073,"description":"Nixing the Fix: Warranties, Mag-Moss, and restrictions on repairs lfair March 18, 2019 | 10:24AM Nixing the Fix: Warranties, Mag-Moss, and restrictions on repairs By Lesley Fair First, the bad news: That nifty purchase needs a repair. Now the good news for consumers: It’s still under warranty. But where can they go to get it fixed? Can the manufacturer restrict a consumer’s ability to go to the independent repair shop of their choice? Can the manufacturer use glue, non-standard screws, and proprietary diagnostic software that make it difficult for independent repair shops to fix things? Do limitations like these affect consumers’ rights under the Magnuson-Moss Warranty Act ? That’s the topic of Nixing the Fix: A Workshop on Repair Restrictions , an FTC event scheduled for July 16, 2019 . Enforced by the FTC, the Magnuson-Moss Warranty Act helps consumers make informed buying decisions and gives them access to remedies if the widget starts to fidget during the warranty period. One key consumer protection under Mag-Moss is that the law prohibits manufacturers from conditioning warranty coverage on the use of particular products or services. Here are some of the questions FTC staff intends to ask at Nixing the Fix : What’s the interplay between repair restrictions and the Magnuson-Moss Warranty Act’s anti-tying provision, which establishes that manufacturers can’t condition coverage on the use of parts or services identified by brand, trade, or corporate name? Do repair restrictions affect the market for extended warranties and service agreements? What types of restrictions are consumers running into when they try to get their stuff repaired? Are manufacturers’ restrictions having an impact on small fix-it businesses? Are manufacturers using software that may render products obsolete or unfixable if consumers engage in DIY or go to a local repair shop? Are repair restrictions necessary to reduce the risk of physical injury or to protect manufacturers from liability for products improperly repaired by others? Do consumers understand the effects of repair restrictions? We’re also looking for empirical research and data about the prevalence and impact of manufacturers’ repair restrictions. For example, what can you tell us about code that disables products that have been repaired by someone other than the manufacturer, product designs that make third-party repairs difficult (like attaching batteries with glue only the manufacturer can remove), contractual post-sale or licensing restrictions, or proprietary diagnostic software and replacement parts? Please send us your research and data by April 30, 2019. Do you have suggestions about possible panelists? Email us at nixingthefix@ftc.gov . Nixing the Fix will take place on July 16th at the FTC’s Constitution Center conference facility, 400 7th Street, S.W., in Washington, DC. It’s free and open to the public. You can file public comments online and we’ll keep the record open until September 16, 2019. Follow the Business Blog for more information about the agenda and for watch-the-webcast instructions.","source":"FTC USA Business Blog Posts","url":"https://www.ftc.gov/business-guidance/blog/2019/03/nixing-fix-warranties-mag-moss-restrictions-repairs"},{"source":"Blog d'Arthur Perret","url":"https://www.arthurperret.fr/blog/2023-11-01-document-theory-and-document-design.html","titre":"[Article] Document theory and document design","id":3047509,"pubDate":"Thu, 23 Jul 2026 10:17:34 +0200","description":"

This paper reports on an experiment which connects document design with document theory. Document design is about what documents should do. We use the example of document graphs and of Cosma, a visualization program created during the HyperOtlet research programme, to show how theory can inform design decisions and help conceptualize results. This paper is currently under peer review.

Document design or information design?

Findeli (2015) defines design as diagnostic and prescriptive, an example of “projective” epistemology: designers view the world as a project to realize, rather than an object to know. This definition of design implies that document design is less about what documents are and more about what they should do. This aligns with the evolution of document theory from an ontic view of documents to a functional one, which was pioneered by the European documentation movement in the first half of the twentieth century and reintroduced as “neo-documentation” in the literature during the 1990s.

Currently in the literature, document design is mostly considered to be a part of information design.1 The purpose of information design is to create effective communications (Renkema 2006 ; see also Pettersson 2002). Document design is usually taught within communications programs ; in the US, in either English or fine arts departments (Schriver 1997, p. 92‑93) ; in France, in Information and Communication Science departments.

Research on information design has very few connections with documentation. It has been criticized for its lack of theory: Carliner (2006, p. 10–14) warned about the field’s tendency to generalize findings despite shaky conceptual foundations and a limited understanding of topics such as the World Wide Web.2 We believe document theory can help address some of these challenges and bring perspective to information design.

Zacklad (2019) gives us an example of this. He draws from document theory to define information design as the interplay between textualization (creating content information), documentarization (shaping the medium) and auctorialization (creating author identities). Zacklad puts documentarization at the heart of information design (see fig. 1). Documentarization can be internal (the organization of fragments into documents) or external (the relational organization of documents, e.g. classification); it can involve different roles or positions (author, editor, printer/programmer, distributor, reader); it implies significant differences between designing the systems that involve documents (“system-oriented design”) and designing the documents themselves (“author design”).