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.
Webster's Dictionary defines information as: "The act of informing; the communication of knowledge". Information design is a highly specialized area of design that involves making large amounts of complex information clear and accessible to audiences of one to several hundred thousand. This section of Design Forum looks at characteristics and issues connected to this interesting and often misunderstood area of design. It contains articles both general and specialized that address issues, constraints and characteristics and attempts to formulate a working definition for those who are new to the subject. Is information design the best example of 'form following function' in graphic design? Designers usually love it or hate it...why?
Welcome practitioners, educators and students from all experience design disciplines! The goal of this archive is to build a teachable and learnable body of knowledge for the extended experience design community, which can be referenced and is freely accessible. These cases have been peer-reviewed and present best-practices from each year.
The primary purpose of intranets is to support staff in doing their jobs, to help them complete common business tasks. In practice, however, this can be very frustrating on many intranets. Policies are located in one section, procedures in another section, and forms in a third. Information then needs to be hunted out in order to complete even simple activities. The effectiveness of intranets can be greatly enhanced by bringing together all of the information and tools relating to a task or a subject, and presenting them in a single location.
XML editors have traditionally been modeled after the first SGML editor written in 1985, a long time before creating, managing, and distributing structured information was well understood. Now, nearly 20 years later, there are more choices for users interested in creating structured information. Specifically, this presentation discusses alternatives that include Web-based distributed collaborative XML document creation, "tag-free" tools, non-formatting structured editors, and even using common office tools in creating your XML documents.
While I'm a big fan of XML for many purposes, it's a misconception that it's the single best solution in every scenario, and it's worthwhile to consider the alternatives in situations where the benefits of XML are not necessary. In this article, I discuss alternatives to XML, SGML, and HTML that might be suitable when budgets are more limited. While XML is perfect for highly coded information, other options can work well for many kinds of information. Markup languages are at the high end of the cost spectrum, so if you don't need the benefits they provide, you certainly should consider the alternatives discussed below.
Can we reasonably judge authority? How can we make good decisions in the information age? How do we know enough to ask the right questions? Peter Morville takes a moment to talk with us about these and other potential answers, his most recent book, the death of data, and our fascination with the future.
ASIST provides the people, programs and publications that keep your career moving forward. Whether you need to improve your productivity through better information retrieval, satisfy the information needs of your clients and constiuents, or need to understand or affect information policies, ASIST can help you address all of these diverse needs.
SGML is a language for describing the structure of a document. The language involves using a system of tags for elements of a document. Document analysis is the process of discovering the elements of a document and understanding how the parts work together to form the document.
You've seen reader comments on weblogs and other Web 2.0 sites, but the Atom protocol makes it possible to create and manage such comments in a very flexible way. Flexible Web annotations is an idea that will open up an entirely new class of Web applications with very little actual new invention. Learn how to create a system to manage annotations for anything on the Web, from nearly anywhere.
This article explains the basics of XSL to transform XML documents using simple examples. We will gradually focus on using ASP.NET to implement XSLT for any XML document and even to database queries. It introduces different ways of implementing XSL from browser's perspective and server's perspective. We will also discuss some tips to generate automated XML from database queries and then transform them to HTML using XSL transformations.
The two most well-known XSLT processors are probably the Apache project's Xalan (available in both a Java and C++ version) and the Java-based Saxon, which was written by XSLT 2.0 specification editor Michael Kay. If those are the only two XSLT processors you currently use, it's worth checking out Daniel Veillard's libxslt.
Currently, visual XML structured authoring applications can typically handle a small number of XML vocabularies. In some cases, they can even handle them in limited nested scenarios. One of the purposes of creating XML documents with compound vocabularies is to present related information on a given topic in different manners (tables, charts, etc). The synchronization of views between objects of different vocabularies in real-time editing helps authors realize this potential. In this presentation we will discuss an approach to visually creating, editing and synchronizing, nested compound XML vocabularies within one document. The open nature of the architecture enables developers to create plug-ins for new vocabularies including the ability to define synchronization. Also this architecture provides simple method to define visualization of a new vocabulary by utilizing plug-ins already developed and activated.
Can a technical communicator step in and create a striking booth to attract attendees and successfully market a company? You bet – it is easier than it looks. Designing a tradeshow booth is a fun exploration of a communicator’s talents in design, organization, and writing. And if you dare to add some creativity to your talents, success comes automatically.
Both parks and document design share the same goal: to satisfy patrons and entice them to return. The common characteristics - available for many activities, easy navigation and circulation, appropriate equipment, effective use of space, and patron safety - are applied to document design. So take a walk - in a park - to find out about document design.
There are two camps in technical documentation. There’s the “quick web” folks who connect easily and author easily, and then there’s the “structured quality” camp that requires more thoughtful testing and time spent on task analysis and information architecture.
Learn from Dr. JoAnn Hackos, President of Comtech Services, Inc. and Director of the Center for Information-Development Management (CIDM), how to evaluate your legacy content and assess how close you are to the DITA standard. Understand the decision-making process you need to follow to prepare for the conversion process. Consider if your team should first restructure your content in your current tool environment or wait to restructure and rewrite following conversion.
The domain model is a familiar concept to most OOP (Object Oriented Programming) developers and architects, and has been used successfully in a variety of systems and projects. But how does this principle apply to SOA-based solutions?
The Argus Center for Information Architecture works to define and advance the evolving discipline of information architecture. The Argus Center serves as a focal point for learning about the theory and practice of information architecture. Towards this goal, we: manage a selective collection of links to the most remarkable content, events, and people in our field; produce original articles, white papers, conferences, and seminars that draw from the experience and expertise of the Argus team; conduct research, independently and through partnerships, focused on improving our collective understanding of information architecture.