#28773
What Managers Need to Know About DITA 
Product documentation is expensive--often, much more expensive than it needs to be. With DITA promising savings of 50% in product documentation preparation costs, and 80% in translation costs, managers need to know what DITA is and if it can work for their organization. This white paper distills the information that managers need to know about DITA.
Reichman, Katriel. Method M (2007). Articles>Documentation>Standards>DITA
#28750
When in Rome: Describing an API in its Own Terms with DITA 
To tame the API beast, a successful description must: be accurate and complete (of course); take the perspective of the programmer who's going to use the class.
Hennum, Erik and Mariana Alupului. STC Proceedings (2006). Presentations>Documentation>Standards>DITA
#26135
When is a Long Document Not a Long Document?
Change is upon us, whether we like it or not. HTML is the default technology for accessible documents online according to the W3C and most government standards. That means goodbye to the easy solution of flinging scores of long documents on to a web site as Word or PDF files.
McAlpine, Rachel. Quality Web Content (2005). Articles>Web Design>Writing>Standards
#28707
Where Our Standards Went Wrong
Regardless of whether we find validation impractical or imperative, the infighting in the standards community is the biggest obstacle to real progress. Instead of trying to understand what factors make both sides agitated, we've vilified the people on the other side of the argument. We need to identify what's making 100% validation so expensive and difficult, and work on removing those factors.
Marcotte, Ethan. List Apart, A (2007). Design>Web Design>Standards>Workflow
#20698
Spawned by recent conversations with friends, I’ve been thinking about people who are known for designing and working with web standards. Specifically those who have a strong interest in CSS or are already using style sheets to compliment or construct beautiful design. In these conversations, we’ve noted that this space seems heavily dominated by men. This concerns me.
Stop Design (2003). Articles>Web Design>Standards>Gender
#28422
If you're serious about reaching your full potential as a web page designer / producer, I believe you need to learn to code your sites by hand.
Hunt, Ben. Web Design From Scratch (2005). Design>Web Design>Standards>HTML
#20228
Why Don't You Code for Netscape?
Long considered the Holy Grail of web design, 'backward compatibility' has its place; but at this point in web development history, shouldn’t we be more concerned about forward compatibility? ALA makes the case for authoring to web standards instead of browser quirks.
Zeldman, Jeffrey. List Apart, A (2001). Design>Web Design>Standards>Web Browsers
#25521
Why Gecko Matters: What Netscape’s Upcoming Browser Will Mean to the Web
Netscape is about to unleash its new browser, built around the Gecko rendering engine. Theoretically the first completely standards-compliant web browser, Gecko enters a world where most people use IE5 (which is not completely standards-compliant). Is Netscape’s effort too little, too late? Or is it the beginning of a new and better way to create websites? Zeldman articulates The Web Standards Project's position and explains what Netscape’s browser will mean to the web.
Zeldman, Jeffrey. List Apart, A (2000). Articles>Web Design>Standards>Web Browsers
#22936
Why Hiptops are Harmful to Web Standards
Found out why the author has reservations about this handheld device and why it appears not to properly support web standards.
Accessify (2003). Design>Accessibility>Wireless Web>Standards
#25520
It complies with two key web standards. And leaves out two others. It's IE5 Macintosh Edition, the first browser on any platform to truly support HTML 4 and CSS-1. Its accessibility enhancements put the user in charge, and its clever new features solve long-standing cross-platform and usability problems. All this ... but still no XML or DOM.
Zeldman, Jeffrey. List Apart, A (2000). Design>Web Design>Standards
#31960
The last couple of years may have seen an increase in the level of interest and action around web standards. But it still isn’t filtering down to the mainstream.
Johansson, Roger. Vitamin (2006). Articles>Web Design>Standards
#27708
Why Won't Microsoft Join Existing Standards Efforts?
Microsoft has stated on numerous occasions that they believe in and support open standards. But from my experience, they do this not by joining existing open standards efforts, but instead by creating entirely new, parallel (and arguably redundant) 'open standards' efforts around their own technologies. And often it seems these new standards efforts are around new, untested, and immature technologies that began life as proprietary to Microsoft--introduced into the standards process when a pre-existing open standards effort already exists, and exists around proven and shipping technologies which were developed in the open with lots of input from a variety of expert stakeholders.
Korn, Peter. Sun Microsystems (2005). Articles>Word Processing>Standards>Microsoft Word
#27929
Recently the Microsoft blog told us that some of our CSS hacks will stop working in IE7, a fact we detailed in our first IE7 article. While this is generally good news, it is a bit disturbing that the Holly hack in particular will cease to function while many of the layout problems it is meant to fix will still be there, and will still need fixing.
Bergevin, Holly and John Gallant. Position is Everything. Design>Web Design>Standards>CSS
#27675
The World Grows Small: Open Standards for the Global Web
We know that crafting a more accessible website relies on understanding and using web standards including (X)HTML and CSS. It's interesting to see how the same practices relate directly to the design and development of internationalized sites.
Holzschlag, Molly E. List Apart, A (2006). Design>Web Design>International>Standards
#25353
The World Wide Web Consortium (W3C)
The World Wide Web Consortium (W3C) is an international consortium where Member organizations, a full-time staff, and the public work together to develop Web standards.
#29372
Writing DHTML that Meets the Cross-Platform Challenge 
DHTML coders have had to overcome many obstacles to writing clean, portable code, including specific browser requirements. See how some straightforward coding tenets can help you sidestep such challenges.
Robinson, Scott. TechRepublic (2003). Design>Web Design>Standards>DHTML
#10281
This article presents the history of the ANSI standard for preparation of Material Safety Data Sheets, and then provides a section-by-section guide to preparing MSDSs that comply with the standard.
Croft, Suzanne D. Technical Communication Online (1996). Articles>Risk Communication>Standards>Technical Writing
#24436
Introduces Web Services Description Language (WSDL), a type of document that defines the set of operations a Web service can perform.
Flaherty, Brian. Intercom (1995). Articles>Web Design>Standards
#21578
#28348
This Recommendation defines a new XHTML document type that is based upon the module framework and modules defined in Modularization of XHTML [XHTMLMOD]. The purpose of this document type is to serve as the basis for future extended XHTML 'family' document types, and to provide a consistent, forward-looking document type cleanly separated from the deprecated, legacy functionality of HTML 4 [HTML4] that was brought forward into the XHTML 1.0 [XHTML1] document types. This document type is essentially a reformulation of XHTML 1.0 Strict using XHTML Modules. This means that many facilities available in other XHTML Family document types (e.g., XHTML Frames) are not available in this document type. These other facilities are available through modules defined in Modularization of XHTML, and document authors are free to define document types based upon XHTML 1.1 that use these facilities (see [XHTMLMOD] for information on creating new document types).
W3C (2001). Design>Web Design>Standards>XHTML
#29983
But one of the lesser known differences between HTML and XHTML is that attributes within tags (such as the href attribute within a link tag) must use 'entities' for special reserved characters. For example, within mark-up, & has a special meaning. Greater than and less than signs (> and <) also have a special meaning, as they are used to define tags.
HyperWrite (2004). Articles>Web Design>Standards>XHTML
#28347
This document is version 1.1 of XHTML Modularization, an abstract modularization of XHTML and implementations of the abstraction using XML Document Type Definitions (DTDs), and XML Schemas. This modularization provides a means for subsetting and extending XHTML, a feature needed for extending XHTML's reach onto emerging platforms. This specification is intended for use by language designers as they construct new XHTML Family Markup Languages. This specification does not define the semantics of elements and attributes, only how those elements and attributes are assembled into modules, and from those modules into markup languages. This second version of this specification includes several minor updates to provide clarifications and address errors found in the first version. It also provides an implementation using XML Schemas.
W3C (2006). Design>Web Design>Standards>XHTML
#26650
XHTML Web Design for Beginners
Explores exactly what XHTML is, and how you can use it to start producing the next generation of Web pages.
Peck, Nigel. SitePoint (2003). Design>Web Design>Standards>XHTML
#14613
Douglas McLaughlin describes the history and features of XHTML, a reformulation of HTML 4.0 using XML syntax.
McLaughlin, Douglas J. Intercom (2000). Design>Web Design>Standards>XHTML
#14642
XHTML: What's in a Name(Space)?
McLaughlin explains the use of namespaces in XHTML.
McLaughlin, Douglas J. Intercom (2000). Design>Web Design>Standards>XHTML
