Information design (also known as 'information architecture') is the study of the details of complex systems. Among these are websites, user interactions, databases, technical writing documentation, and human-computer interfaces.
Corporate design manuals are modular. Information technology is modular. They're both modular because modularity is the only way to deal with complex information such as corporate design for multinationals or thousands of lines of code.
Lo sviluppo di un’architettura dell’informazione prevede parecchie sfide, ma una biblioteca è un ambiente relativamente ben definito e sono disponibili molte esperienze e sapere collettivo da cui attingere. I siti web, d’altro canto, presentano un serie di nuove sfide.
Systems engineering is moving away from specially-designed and built systems to integration of commercial off-the-shelf (COTS) hardware and software. COTS brings new challenges to technical communicators. In the past, we found all our information in-house, now it comes from many sources. We must change our process from pure development to information integration, and we must be part of the COTS selection process.
There are several tools that can help you generate an XML Schema document from either an instance or a DTD. This hack shows you how to get the job done with little fuss.
The common wisdom is that we now live in the age of information; the freedom and access we have to data is unprecedented in history; and the efficiency and convenience of online commerce, research, and communication has already transformed our lives for the better. While this is true, of course, our excitement should be tempered by a few realizations.
All the books tell me to set goals for my site. OK. They say that those goals need to be measurable and definite. Fine. But asking my client, “What are the site’s goals?” never seemed to get me what I wanted. It occurred to me that a better approach might be to get some background info from the client and then set the goals and present them to the client for approval.
Staff at the U.S. Environmental Protection Agency created a template then steadily converted Web pages to achieve a 'corporate face' for www.EPA.gov, the Agency's Internet site. Management and maintenance of Agency Web pages rests among the technical subject matter and administrative experts within headquarters, program, and regional offices and laboratories – rather than centralized. Template design, deployment and conversion involved many employees and contractors nationwide, and took almost one year. As of February 1, more than 90% of EPA's Internet pages comply with the template, and staff continue improvements to the Agency's public Web resources.
Now we come to the point of actually producing documents using structural markup—either eXtensible Markup Language (XML) or Standard Generalized Markup Language (SGML). Our sequence of topics illustrates the recommended steps to follow when you first implement structural markup: Learn about it and convince yourself and your organization of its benefits, identify your specific goals and expectations, and spend plenty of time selecting or designing your document structures. Only then should you get down to the specifics of how to produce XML or SGML documents. If you simply try to drop in an XML editor to replace your current word processing application, you will be lucky to avoid total disaster.
The DITA OpenToolkit (DITA OT) provides a way to produce multiple outputs, including Portable Document Format (PDF) files; however, the technology for creating PDF files is limited, and modifying the formatting is challenging. This paper explains the alternatives and trade-offs for each method and helps demystify the decision process.
Are you storing data about your constituents in three, five, even ten different databases? If so, you're not alone ' but it's costing you in time, lost revenue and decreased impact. Paul Hagen describes how to get all your data into one place with an integrated CRM strategy.
It's hard to look at a page of text and try to decide where to divide things to create individual topics. That "bottom up" approach is kind of pointless, in fact. There are better ways.
So you know all about reading and parsing XML files, and even checking if they're well-formed and valid. Now, take a step into more advanced territory with this expose of two objects that let you dynamically create well-formed XML documents in your ASP.NET scripts.
Jamie Owen explores how we can best utilize cues in our work by understanding how memory, cognitive psychology, and multimedia research affect how information is encoded and retrieved.
A well-known advocate for the effective use of new technologies in the legal profession, New Orleans-based attorney Ernest Svenson finds Adobe Acrobat and PDF to be highly valued tools in a document-intensive field.
With the overall purpose of improving the information literacy skills of librarianship and information science students, an academic portal specifically centred on abstracts and abstracting resources is proposed. We take the existing literature, together with our knowledge and experience of abstract/abstracting topics and web-based technologies to conceive the research design. The research mainly consists of the selection, assessment and web-display of the most relevant abstracts on knowledge management, information representation, natural language processing, abstract/abstracting, modelling the scientific document, information retrieval and information evaluation. The resulting Cyberabstracts portal presents its products consistently and includes reference, abstract, keywords, assessment and access to the full document. Improvement opportunities for this unique subject-based gateway, representing much more than a mere subject catalogue, are uncovered as the starting point on a planned route towards excellence.
The rules for finding schema components when validating a document using W3C's XML Schema 1.0 are widely misunderstood. This presentation will the rules for constructing a schema and describe the reasoning behind the design.
Personalization is coming to technical communication, and the results may not be pretty. n offering the individual an opportunity to pick and choose among XML content objects, we risk causing confusion when the organization of the site appears to shift, and familiar landmarks disappear. Critical content may become invisible to the user. The very process of creating preferences, custom options, or an entire personal profile adds a complex distraction that many users may resent, because it takes them away from their original task for so long that they forget what they were doing. Even advanced search mechanisms, which promise to pinpoint the exact information object the user wants, risk baffling users with their own complexity.
DITA is an architecture for creating topic-oriented, information-typed content that can be reused and single-sourced in a variety of ways. It is also an architecture for creating new information types and describing new information domains based on existing types and domains. This allows groups to create very specific, targeted document type definitions using a process called specialization, while still sharing common output transforms and design rules developed for more general types and domains.