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.
According to experts, the Semantic Web, an enhancement of the conventional web, is paving the way for new functionalities in future, web-based applications. The possible scenarios that we could face are reminiscent of fiction and cinema, where you just need to think of the question for which we are seeking answers. An invisible assistant would then perform the search.
First of all, understand that you don’t have to learn it. Every year more and more toolds come out that help place a layer between you and the native XML. In a few years time you will hardly even realise there is XML underneath.
'What I need are highly condensed overviews,' I thought, 'like those comic books that convert great literary works into a few illustrated pages. They condense Moby Dick down to 12 pages and provide a version of Great Expectations that can be read in 15 minutes.'
There is a discipline, known as information architecture; and there is a role, known as the information architect. They have developed more or less hand in hand, and up to now any discussion of one has involved discussion of the other. But now that may have to change.
iaslash is a news site for information architects, modeled on slashdot, interested in information organization, usability, user testing, user interface design, and other areas related to the access and use of information in information-use environments.
Where the seams of information and public space overlap and intersect, Elliott Malkin creates projects that span genres from religion to natural science. In a preview of his upcoming IDEA conference talk, Malkin talks about home-movies, butterflies, and designing for unofficial signs in public space.
Current methods of access to the electronic resources offered by the Internet make little use of basic principles of information organization and retrieval, relying instead on relatively informal and, at times, ad hoc approaches. This creates problems in terms of the volume of information retrieved by a user of the Internet and the precision with which that information matches the user's information need. There is a plethora of engineering resources available on the Internet, yet no systematic method of retrieval is available to engineers who are in need of the most current information in their discipline. The Internet is often the only immediate source of the most current engineering resources. The purpose of this project is to identify electronic resources that could be of value to engineers and to represent these resources in a manner that enables engineers to make timely, informed decisions about the usefulness of the resources. This paper addresses the specific objectives the project which include: 1) the development of selection criteria for electronic engineering resources; 2) the identification of electronic resources of interest to engineers, as defined by the selection policy; and 3) the creation of abstracts for these electronic resources that will include at least two hyperlinks to other related electronic resources.
This paper identifies common problems faced by information designers and suggests a set of heuristics that could be used to evaluate information design. By examining reception and transmission errors, the paper explores the different channels available to the designer, the errors that can be introduced through those channels, and possible solutions that might mitigate or eliminate those errors.
The validity of the term architecture for information work has been the source of some contention among both IAs and traditional architects. I have been forcefully reminded in recent weeks, through my dependence on information technology, just how limited the architecture of information spaces can be compared to the physical structures of our world. Just as a problem with the plumbing or the roof of your home tends to grab your attention and demand resolution, computers in their various forms can make demands on users that stretch the patience and emotional stability of even the most sanguine.
Intranets don't self-organize. Without planned, centralized information architectures and clearly defined published processes, they become unproductive. Intranets often have applications that either don't work properly, are too difficult to learn, or have no clear business benefit. Applications, like content, must be able to establish a clear return on investment.
One of my goals was to make it easy to get help for using specific parts of our application. Users don’t need to know the name of the panel or feature they are trying to use. They just need to know where they are working on the screen, and they can click through to get the help that discusses that part of the screen.
Design of information tends to be controlled by the functionality of the tools and technology. The last decade has seen a powerful move to online materials and a move away from paper. The next 5 years will see a move to new ways of structuring information for multiple media, multiple audiences, and multiple types information. The use of document databases, single sourcing, and knowledge webs will redefine 'writing.' As we move into the next millennium, information developers need to take control of the technology to support information design. This article addresses the changing face of technology, information design, and skills required to ensure effective information development in support of user needs.
The focus of this paper and the presentation will be to discuss how XML has changed and improved the legislative and regulatory document creation and management processes for agencies of the federal government. During the presentation, we will briefly describe the evolution of XML adaptation in the Legislative Branch agencies. A more in depth discussion can be found at xml.house.gov.
“SGML is too complex and too costly to implement widely. ” This criticism has often been leveled at the Standard Generalized Markup Language. Mainstream SGML, a new open architecture, challenges that view. Traditionally, implementation has required companies to invest heavily in training. Authors had to learn how to create documents using complex SGML syntax. This method was time-consuming and yielded a slow return on investment. The Mainstream approach to implementing SGML uses resources that already exist in a company. Mainstream SGML provides an alternative to costly, complex native SGML document management systems. This workshop shows you how you can use mainstream SGML to successfully implement SGML in your mainstream business and publishing processes.
Standard Generalized Markup Language (SGML) is an accepted standard today. It promises to free many companies and industries from problems with document conversion, compatibility, and interoperability. Whether you’re curious about SGML’s benefits or actively planning to implement SGML, this workshop will help. As a participant, you will learn how to apply a life-cycle approach to implementing SGML. Through hands-on exercises, you will gain the knowledge to succesfully plan and implement SGML solutions.
Standard Generalized Markup Language (SGML) is an accepted standard today. It promises to free many companies and industries from problems with document conversion, compatibility, and interoperability. Whether you’re curious about SGML’s benefits or actively planning to implement SGML, this workshop can help. As a participant, you will learn how to apply a life-cycle approach to implementing SGML. Through hands-on exercises, you will gain the knowledge to successfully plan and implement SGML solutions.