Great description of the distinction between architecture and design. Like InfoArch and InfoDesign, human cognition and perception.
"(...) user interface design is a context-specific articulation of an underlying information architecture. It is this IA foundation that provides the direct connection to how human end users find value in content and functionality. The articulatory relationship between architecture and design creates consistency of experience across diverse platforms and works to communicate the underlying information model we’ve asked users to adopt. (...) This basic distinction between architecture and design is not a new idea, but in the context of the Internet of Things, it does present architects and designers with a new set of challenges. In order to get a better sense of what has changed in this new context, it's worth taking a closer look at how the traditional model of IA for the web works."
Movies as a source of inspiration and vision visualization for HCI designers has grown more mature.
"It's not just that Her, the movie, is focused on people. It also shows us a future where technology is more people-centric. The world Her shows us is one where the technology has receded, or one where we've let it recede. It's a world where the pendulum has swung back the other direction, where a new generation of designers and consumers have accepted that technology isn't an end in itself - that it's the real world we're supposed to be connecting to."
And what about wall-size screens or future iTVs?
"(...) by embracing large screens, designers have the opportunity to work within a larger fold, presenting the user with more content simultaneously, lessen scrolling on longer pages, and create a richer, more expansive user experience. And by using the same practices we developed to adapt layouts to smaller screens and identifying some common patterns for large screens, we need not necessarily introduce extra cost or time to our projects."
Online typography, typefaces and fonts get mature, finally.
"With the chaos of different screen sizes and a new generation of web browsers, the design paradigms of layout and typography have shifted away from static layouts and system fonts to dynamic layouts and custom web fonts. But screens have not just changed in size but also in pixel density. In other words: maybe we do not just need responsive layouts, we might also need responsive typefaces."
The end of a long-lasting law. New law will be based upon another perspective of technology: paralellism.
"Technology cycles have been on a tear for decades, with each chip iteration bringing more capabilities at lower prices. But less can be more in tech products-and design is the way to balance that factor."
Hardware form factor only is just for one-dimensional designers.
"As people continue to go online using an ever increasing diversity of devices, responsive Web design has helped teams build amazing sites and apps that adapt their designs to smartphones, desktops, and everything in between. But many of these solutions are relying too much on a single factor to make important design decisions: screen size."
(Luke Wroblewski a.k.a. @lukew)
Cards and tags, a magic duo. Ask Paul Otlet or Bill Atkinson.
"We are currently witnessing a re-architecture of the web, away from pages and destinations, towards completely personalised experiences built on an aggregation of many individual pieces of content. Content being broken down into individual components and re-aggregated is the result of the rise of mobile technologies, billions of screens of all shapes and sizes, and unprecedented access to data from all kinds of sources through APIs and SDKs. This is driving the web away from many pages of content linked together, towards individual pieces of content aggregated together into one experience."
Trucks and cars. 'Cars' as the new driving experience on the information highway.
"The goal of this document is to rise above the current alphabet soup of technical standards and create some conjecture and possibly even motivation around how these standards can work together. The web can be so much more that what native apps can do. It can offer interactivity like water, pouring out of any device with nothing but a click. This is the super power of the web and isn’t appropriately appreciated as the key differentiator from native apps."
Tug of war between design and software engineering.
"The real challenge with the standard approach to integrating UX into Agile is fundamental to the staggered sprint model. The challenge is essentially that it is not wholly effective to try to be working ahead on the upcoming backlog items while at the same time supporting the development team, answering their questions, reviewing what they're doing, and providing ongoing feedback/microiteration with them."
System thinking for UX design is disrupting our field.
As web and industrial design begin to collide, UX and UI design are particularly ripe for disruption. ~ "The last major shift in design arguably occurred in the 90s as print design gave way to web design, and designers suddenly had to deal with web safe colors, alias fonts, and the information design challenges of a non-sequential medium. Two decades later, design is approaching a similarly monumental shift as designers move from designing for the web to designing for systems."
One of the giants on whom's shoulders we stand.
Interview with computing pioneer Alan Kay ~ "One way to think of all of these organizations is to realize that if they require a charismatic leader who will shoot people in the knees when needed, then the corporate organization and process is a failure. It means no group can come up with a good decision and make it stick just because it is a good idea. All the companies I've worked for have this deep problem of devolving to something like the hunting and gathering cultures of 100,000 years ago. If businesses could find a way to invent "agriculture" we could put the world back together and all would prosper."
(David Greelish ~ Techland)
"The best computer is a quiet, invisible servant." once said the legendary Mark Weiser.
"A user interface that is invisible and that provides seamless interaction possibilities will help the user focus on their goals and direct them to what they need."
And does web design also need a Gang of Four?
"I thought it would be interesting to explore if a connection between object oriented programming and how we develop visual design patterns exists."
Designers a.k.a. web designers and coders a.k.a. front-end coders.
"Last 15 years changed everything. Design is generally considered just as important as technology. User Experience Design became the key to success and it's hard to imagine any grown-up company, without UXers on board. (...) We don't need coding designers and designing coders – we need people who can communicate, respect and understand each other."
We tend to forget how important the content infrastructure and technology is.
"They create a language to express publishing, content management, or reuse concerns, and then expect writers to write directly into what is really an internal content management format. Putting a graphical face over the markup does nothing to change this. The graphical interface only hides the syntax of the XML. It does nothing to change the fact that authors are being asked to create what should be the internal semantics of the publishing system — semantics they generally neither care about nor understand."
(Mark Baker ~ EveryPageIsOne)
Can there be such a thing as software products?
"When something is wrong, it deviates from truth or fact. And I can say, with more confidence than ever, that traditional Agile software development methodologies (i.e. Scrum) are wrong for UX. In order to prove my case, I want to take you back to the inception of Agile (as I have read and experienced it) and its related software development methodologies. Along the way, we'll point out the reasons these methodologies are incompatible with the field of User Experience Design."
In the end, high quality screens will have more social impact than faster CPU cycles, improved bandwidth or cheaper storage. Think Retina Displays and beyond.
"Reasonably big monitors have finally become the most common class of desktop computer screen, dethroning the 1024×768 resolution that was long the target for web design."
The silver bullet is not as silver as you think it is.
"Reading blogs out there, you will notice that every attempt to fix a responsive design process is still very experimental: there are as many offered ways as there are blog articles about it! Progress is being made, but nothing is really set in stone at the moment. Knowing that, the most important thing right now is to make sure you ask the right questions at the start of each project, make the right choices, and jump into experimentation yourself with a maximum amount of pragmatism. If you find a good idea to make all of these challenges smoother, please write about it and share your discoveries on the web!"
(Rudy Rigot ~ Dev.Opera) ~ courtesy of luctiemessen
Knowing to code makes a better designer.
"In this column, we'll discuss innovative approaches to application design that are based on our personal experience in the trenches."
(Jim Nieters, Amit Pande, and Uday M. Shankar ~ UXmatters)
A well-thought through post on experience and systems. By IBM, who else.
"But, socio-technical systems are oriented toward people and services. While product excellence and competitive costs are also important to services, they are not enough. The service sector is oriented toward consumption, that is, toward people, who are the consumers of services. Therefore, an overriding design objective for good socio-technical, service oriented systems has to be a positive user experience. Ease of use, intuitive interfaces and good overall customer service must be key objectives for a well designed system."
Technology has always been a great driver of UX, closed or open.
"I've been doing a lot of research recently about mobile design patterns and UX best practices for smartphone and tablet devices for both iOS and Android platforms. One thing has stood out more than anything else during this process: no one is talking about Android."
It can mean many things. Depending of who asks.
"Many companies caught on to the mobile-first trend awhile back. Google surfaced their mobile-first strategy in 2010. As you've probably guessed from the name of this approach to site design, mobile first means designing an online experience for mobile before designing it for the desktop Web-or any other device. In the past, when users' focus was on the desktop Web, mobile design was an afterthought. But today, more people are using their mobile devices for online shopping and social networking than ever before, and most companies are designing for mobile. Mobile first requires a new approach to planning, UX design, and development that puts handheld devices at the forefront of both strategy and implementation. The digital landscape has changed, and companies have realized that consumers are now accessing more content on their mobile devices than anywhere else."
Or how UX and CX can be disruptive. Love the comments.
"A disruptive technology or disruptive innovation is an innovation that helps create a new market and value network, and eventually goes on to disrupt an existing market and value network. The term is used in business and technology literature to describe innovations that improve a product or service in ways that the market does not expect. Although the term disruptive technology is widely used, disruptive innovation seems a more appropriate term in many contexts since few technologies are intrinsically disruptive; rather, it is the business model that the technology enables that creates the disruptive impact."
As long as we see UX projects as software engineering projects and not the other way around, the plus and minus sides of the magnet will not connect.
"Teams moving to agile often struggle to integrate agile with best practices in user-centered design and user experience in general. Fortunately, using a UX Integration Matrix helps integrate UX and agile by including UX information and requirements right in the product backlog. While both agile and UX methods share some best practices-like iteration and defining requirements based on stories about users-agile and UX methods evolved for different purposes, supporting different values. Agile methods were developed without consideration for UX best practices. Early agile pioneers were working on in-house IT projects (custom software) or enterprise software."
Keep, hide or move. But are you telling the same story different on the desktop, the iPad or the smartphone?
"Responsive design can have a major impact on your content. I'll tell you how it works, how it can affect your content, and why you should-and need to-care."
Both fields seem to be at the wrong side of the magnet.
"(...) when experience design is married with agile development, the results can be a crisis of faith on either or both sides."
DTDT (again): Interface is part of the object and experience is part of the subject, be it for design or development purposes.
"UX Designers focus on the structure and layout of content, navigation and how users interact with them. (...) UI Developers focus on the way the functionality is displayed and the fine detail of how users interact with the interface."
What's the common denominator of structural programming, OVID, OOA/D, RUP, rapid/extreme programming and Agile? No design thinking regarding use involved.
"There really is something here. Lean UX is an important new way to think about what we do, and I think there's real meat on it. Let me explain."
Or, what a paragraph can do for you.
"In this article, I'd like to reacquaint you with the humble workhorse of communication that is the paragraph. Paragraphs are everywhere. In fact, at the high risk of stating the obvious, you are reading one now. Despite their ubiquity, we frequently neglect their presentation. This is a mistake. Here, we'll refer to some time-honored typesetting conventions, with an emphasis on readability, and offer guidance on adapting them effectively for devices and screens."
After the Age of Aquarius (source: Hair, the musical), we're now entering the Age of User Experience.
"(...) as pervasive and unstoppable as its progress may seem, the web can still be lost if we don't temper ideological extremisms that preach 'the one web' above all else, including pragmatism and user experience. In this (no doubt rather controversial) session, Aral Balkan will outline the essential role of user experience in our age and demonstrate how the web must embrace user experience if it is to compete with native. Flawed 'native is laserdisc' analogies will be shattered as Aral demonstrates how, in the Age of User Experience, the only possible future is a native one where focused, optimised, and expertly-crafted experiences empower, delight, and thrill users."
I guess, content is becoming as fluid as possible.
"The last few years have been a good time to be a web designer. After a decade of making do with the aging technologies, methods and assumptions that gave birth to mainstream web publishing, designers are starting to trade the tiresome challenge of controlling the user experience for a few more interesting ones."
Great to see UX disciplines applied to geek technology.
"Alex Payne explores the interaction design of APIs, particularly through the lens of the speaker's experience evolving the popular Twitter API. The speaker argues for the notion of a "humane" API", one derived from simplicity, "explorability" and consistency. Alex Payne is API Lead at Twitter, Inc., a communications service used by millions to share short messages."
So, there is much more involved with the languages of the Web than meets the eye.
"As use of mobile devices continues to skyrocket across the globe, we're seeing more ways to tackle the challenge of creating great Web experiences across multiple devices. But which approach is right for any given project? In an effort to help answer that question, I've compiled the reasons we opted to use a dual (separate mobile and desktop) template system to build our start-up."
Increasingly 'computer' becomes a generic term; its instantiations matter.
"Mobile use will rise, but desktop computers will remain important, forcing companies to design for multiple platforms, requiring continuity in visual design, features, user data, and tone of voice."
As a designer, you must know the materials you're working with: computational and connected data, information and content.
"Human-Computer Interaction has strong roots in Computer Science, and user experience design is almost exclusively a technology-focused practice. How much does UX design share with its engineering-focused sibling? I'm going to share some thoughts about my experiences from making the transition from software engineering to UX, and how my past career has made an influence in my roles as a user experience designer today."
Recurring issue, especially now with all the buzz around Agile, Scrum, and 'what-have-you'. IBM called it OVID.
"If the UX professional's job ends at the end of the design phase, something is wrong with the process."
Function follows feature follows user.
"The process by which most enterprise software is developed is fatally flawed. There are flaws in any software development process, but in the past 13 years I've seen one approach produce more bad software and blow more budgets than any other: requirements-driven software development. Thankfully, I've also had the opportunity to see the success of an alternative type of process, a process in which user experience design drives what gets developed. This type of process helps teams deliver good software on time and within their budgets."
A nice practice case with a few exceptions to the rule.
"There are two explanations for the endemic publishing paralysis. Either no one has made a good CMS yet - perhaps putting words and pictures on pages is the limit of our engineering capacities - or the CMS is a broken concept."
(Erik Hinton ~ TPM)
"Mobile first design is primarily about the starting point. After a site is complete, how can I tell whether or not the developer started from the mobile and built up to desktop or started from the desktop and whittled down to mobile? I didn't want to have to tear apart over a hundred sites in the Mediaqueri.es gallery to find the handful of mobile first sites. I needed some way to narrow the number of sites I cared about to some sort of manageable number."
"Religion, nationalism, and sports-team rivalries? They can't compare to the passion of a nerd's technical conviction. And so kerfuffles result. Well-intentioned zeal leads to distracting dustups. Alas, complex problems rarely resolve themselves into neat black-and-white principles. The only principle that ever seems reliable is drearily unsatisfying: 'it depends'. In the mobile world, we have the persistent and circular debate over whether the mobile web should be powered by the very same sites and webpages that render the desktop web."
"Code is the material that breathes life into a user experience, so we ought to get familiar with it."
"Jeremy Keith outlined the problem of digital preservation on the Web and provided some strategies for taking a long term view of our Web pages. (...) Preserving our culture requires holding on the little things that define our history. It's not a technical problem to preserve our culture and our story. But we need people to want to do so." (LukeW)
"Designing with modular scales is one way to make more conscious, meaningful choices about measurement on the web. Modular scales work with - not against - responsive design and grids, provide a sensible alternative to basing our compositions on viewport limitations du jour, and help us achieve a visual harmony not found in compositions that use arbitrary, conventional, or easily divisible numbers. As we've seen in this article, though, modular scales are tools - not dogma. The important thing for our readers, our craft, and our culture is that we take responsibility for our design decisions. Because in so doing, we'll make better ones." (Tim Brown ~ A List Apart)
"RIGHT NOW is the best time in more than a decade to create websites and applications. There are new opportunities: Webkit and Mobile, HTML5 and CSSS3, UX and Content Strategy. The landscape has changed in a good way. It's bringing up a lot of challenges (...)" (Jeremy Keith - Adactio)
"I'm perplexed by the reasoning that concludes that if a website is suffering from clear usability issues, the solution is to create a splinter site for some users while leaving everyone else to suffer on. Note that I'm not suggesting that everyone get the same experience - far from it. Thanks to progressive enhancement (and let's face it, responsive design done right is a perfect example of progressive enhancement) we can serve up the content that people want and display it to the best ability of any particular device. That's the key difference: start with the content, not the device." (Jeremy Keith ~ Adactio)
"The three parts of the series were split into the following segments: Part 1: Speed (The introduction to the series identified constraints in mobile design imposed by bandwidth, download and upload speeds.); Part 2: Dimensions (This section attempts to establish common limitations across groups of devices based on resolution and physical size. In addition, solutions for serving specific styles to groups of devices are offered, and analyzed.); Part 3: Behavior (Perhaps the least complete of the sections, this article attempts to show how users behave differently on handheld devices compared to desktops. At the same time, this area probably interests me most, but I believe much more testing will need to be done in regard to how gesture-based interfaces can be used in an acceptable way before the ideas explored here become more relevant.)" (David Leggett)
"DITA would have you believe that you can single source your way into every possible deliverable. In reality, you're just making potatoes in a few different ways (scalloped, mashed, boiled). You're still giving the user potatoes. VITA is a multimodal approach, giving the user a full array of nutrition options, so to speak. It educates and informs by touching almost every sensory input." (Tom Johnson)
"Software Engineering is typically much more formal than User Experience in they way they model an application before development begins. After pseudo code, the Unified Modeling Language (UML) is probably the most widely used modeling language among software engineers. It has developed from other object‑based analysis and design languages over a period of many years and provides software engineers with a visual language that describes the design of a system at multiple levels." (Peter Hornsby ~ UXmatters)
"Being someone who works for the web is having the best job in the world. There is really nothing that compares in terms of creativity, sharing and reach. Of course there are nagging issues but if we really take a look from afar at what we are doing there is a lot of fun to be had. In this session Chris Heilmann will show just how cool it is to be who we are and how to get joy out of our day to day jobs even when we think that everything is against us. We have the tools, we have the knowledge, we have the time. What we lack sometimes is the knowledge where to look, what to use and how to sell ourselves. Here you'll hear all about it and you will find a lot of reasons to be cheerful." (Fronteers 2010)
"A clear, straightforward design not only makes an application legible, it encourages usage. This guide will provide design knowledge and fundamentals for this type of UI development. We highly recommend that developers adopt the Metro design style whenever possible. Although requirements may vary based on the application, paralleling this experience will create a more consistent, fluid UI experience from the custom and built-in application view." (The Windows Phone Developers Blog)
"Capacitive screens has now become a commodity for touch screen devices. Screen technology is now taking the next leap and the coming years imagination is the only thing stopping us." (Mobile User Interface Blog)
"Good user experience isn't just about good design. Learn how to create a positive user experience by being fast, open, engaged, surprising, polite, and, well... being yourself. Chock full of examples from the web and beyond, this talk is a practical introduction for developers who are passionate about user experience but may not have a background in design." (Google I/O 2010)
"Font designers are very still very much focused on print. By and large, the money is in catering to professional customers in the printing industries: Books, magazines, displays, etc. Prices usually move on a sliding scale based on the number of users. The fear is that once fonts are on the web, they will become a commodity, the current model will break, and a devaluation of fonts, in general, will occur." (Richard Fink ~ A List Apart)
"As intranet projects benefit from powerful implementation platforms, teams should focus on optimizing the user experience for specific organizational needs, as 4 winning examples show." (Jakob Nielsen ~ Alertbox)
"Many companies have used the phrase "content is king" in recent years to talk about the importance of the material their sites ship. I heard this phrase first at Adobe Max a few years ago and have since noticed it in a number of places online. I think this is near to the mark but not quite there. In our framework here I've rephrased it as "The 'why' is king" because it puts the user at the center. Your content is pretty important to your site, but without users it's kind of worthless. The reason your users are coming to your site is of preeminent importance - that should drive your content. Then your content can drive your presentation, etc. etc." (R.J. Owen ~ Inside RIA)
"Today, we measure the size of the Web in exabytes and are uploading to it 15 times more data than we were 3 years ago. Technologies for sensing, storing, and sharing information are driving innovation in the tools available to help us understand our world in greater detail and accuracy than ever before. The implications of analyzing data on a massive scale transcend the tech industry, impacting the environmental sector, social justice issues, health and science research, and more. When coupled with astute technical insight, data is dynamic, accessible, and ultimately, creative." (Marissa Mayer)
"Perceptions of the web are changing. People are advocating that we treat the web like another application framework. An open, cross-platform, multi-device rival to Flash and Cocoa and everything else. I’m all for making the web richer, and exposing new functionality, but I value what makes the web weblike much, much more." (Ben Ward) courtesy of rogerjohansson
"Many people find it hard to picture a website as more than a bundle of content. This often makes explaining the mixture of languages used and the way everything comes together a difficult task. Because what makes up a website can be related and linked to the physiology of a human body, this article's comparison should help clients and beginners alike understand the complex nature of a site’s creation and components." (Alexander Dawson - Six Revisions)
"HTML is the unifying language of the World Wide Web. Using just the simple tags it contains, the human race has created an astoundingly diverse network of hyperlinked documents, from Amazon, eBay, and Wikipedia, to personal blogs and websites dedicated to cats that look like Hitler. HTML5 is the latest iteration of this lingua franca. While it is the most ambitious change to our common tongue, this isn’t the first time that HTML has been updated. The language has been evolving from the start." (Jeremy Keith ~ A List Apart)
"It's about the lines, not the points." (Duane Degler ~ Design for Context)
"Large scale websites require groups of specialists to design and develop a product that will be a commercial success. To develop a completely new site requires several teams to collaborate and this can be difficult. Particularly as different teams may be working with different methods. This case study shows how the ComputerWeekly user experience team integrated with an agile development group. It's important to note the methods we used do not guarantee getting the job done. People make or break any project. Finding and retaining good people is the most important ingredient for success." (James Kelway - Boxes and Arrows)
"In the modern, agile world, programmers defend themselves against changing requirements by showing customers the program as often as possible, and by being able to make rapid changes to suit the customers expressed needs. Interaction designers defend themselves against uncooperative programmers by doing ever more detailed design and documenting it with greater accuracy, detail, and precision." (Alan Cooper)
"Many of the most complex service systems being built and imagined today combine person-to-person encounters, technology-enhanced encounters, self-service, computational services, multi-channel, multidevice, and location-based and context-aware services. This paper examines the characteristic concerns and methods for these seven different design contexts to propose a unifying view that spans them, especially when the service-system is information-intensive. A focus on the information required to perform the service, how the responsibility to provide this information is divided between the service provider and service consumer, and the patterns that govern information exchange yields a more abstract description of service encounters and outcomes. This makes it easier to see the systematic relationships among the contexts that can be exploited as design parameters or patterns, such as the substitutability of stored or contextual information for person-to-person interactions." (Robert Glushko 2009)
"One of the more interesting tensions I have observed - since getting into user experience design about five years ago - is the almost sibling-rivalry tension between UX Designers and User Interface (UI) Developers. At the heart of the tension between them is the fact that most UI Developers consider themselves - and sometimes rightfully so - to be UI Designers. The coding part is like Picasso’s having to understand how to mix paint. It's not the value they add, just the mechanics of delivering the creative concepts." (Mike Hughes - UXmatters)
"This channel is a collection of projects about newer ways of human and physical interaction. It features interactive installations and systems with a strong focus on technologies such as multi-touch, tangible and gestural interfaces, augmented reality and physical computing." (@Jens Franke)
"User interfaces - the way we interact with our technologies - have evolved a lot over the years. From the original punch cards and printouts to monitors, mouses, and keyboards, all the way to the track pad, voice recognition, and interfaces designed to make it easier for the disabled to use computers, interfaces have progressed rapidly within the last few decades. But there's still a long way to go and there are many possible directions that future interface designs could take. We're already seeing some start to crop up and its exciting to think about how they’ll change our lives. In this article are than a dozen potential future user interfaces that we'll be seeing over the next few years (and some further into the future)." (Cameron Chapman - Six Revisions)
"The use of real world style transitions (flipping bookcase over, flipping pages, spreading stacks, rotating orientation, collecting selected elements into stacks) work extremely well with a multi-touch interface. I am using my physical body not a mechanical mouse so the response should feel more real world. This is also what Apple mentions in their UX guidelines." (Bill Scott - Looks Good works Well)
"Interviewing a front-end engineer is an interesting task primarily because most are self-taught. Startups and large companies alike have equal trouble finding quality front-end engineers simply because they don't know what to look for and which questions to ask. Having been around the industry for a while, I've developed my own methods for interviewing front-end engineers that I find to be very effective." (Nicholas C. Zakas - NCZOnline)
"The constraints that recessions impose; on budgets and on time can help us focus more sharply on what matters most, and sharpen our methods and skills to make us more competitive and better at what we do." (Andy Clarke - Stuff and Nonsense) - courtesy of herjeno
"What is the fastest way to get from a product idea to a rich internet application? By breaking down the communication barriers between designers and developers. This talk takes a quick look at how to build a shared vocabulary and use prototyping to bypass extensive wireframes and development specs." (Theresa Neil - Designing Web Interfaces)
"In this podcast Karl Stolley discusses his article, Using Microformats: Gateway to the Semantic Web, which appears in the September, 2009 issue of Transactions on Professional Communication. In the article Stolley explains and describes the use of several microformats, which make information marked up in HTML available for use in applications outside of traditional web browsers. Because microformats consist of minor additions to the HTML backbone of common webpages, they represent a simple but significant move toward what Tim Berners-Lee has called the Semantic Web—but without requiring the technical and practical shifts and time demands of a complete XML-based semantic web development approach." (Karl Stolley - IEEE Professional Communication Society)
"Bill Scott and I have reviewed hundreds of RIAs while compiling examples for our book Designing Web Interfaces: Principles and Patterns for Rich Interactions, and subsequent talks and articles. We recently realized that we had amassed quite a list of applications. Thinking other designers and developers might be interested in these resources, we applied two simple criteria to identify the top fifty." (Theresa Neil - InsideRIA)
"Businesses that historically have approached things in a purely scientific manner are now trying to engage their users at a more fundamental level. Through great experiences. And great experiences, the way in which these stories unfold, have this innate ability to change or enhance the way in which people view and interact with their world. We're not advocating that we throw our concerns about platforms and technology considerations out the window but rather how best to combine them with thoughtful, engaging design principles. The Art and Science behind great experiences balancing one another in harmony, embodied within the end product." (Christian Saylor - InsideRIA)
"Bill Scott shares six design patterns that are critical for creating effective web interfaces, focusing specifically on interaction design on the web. This presentation is a distillation of principles, patterns, and best practices for creating a rich experience unique to the web." (Bill Scott)
"Web design without technology is just art. You must understand the magic that gets it on the site." (Bill Scott - Looks Good Works Well)
"Many people enter the inside-out world of augmented reality (AR) by doing something as ordinary as visiting a major city like New York and trying to get to a local friend's favorite pizza shop, somewhere deep in Brooklyn, via public transportation. Standing in Times Square on a summer evening, they might hold up a new smart phone and pan it slowly around the Square to see a pointer to the nearest subway entrance overlaid on their phone’s video display of the buildings around them." (Joe Lamantia - UXmatters)
"The classical approach to the data aspect of system design distinguishes conceptual, logical, and physical models. Models of each type or level are governed by metamodels that specify the kinds of concepts and constraints that can be used by each model; in most cases metamodels are accompanied by languages for describing models. For example, in database design, conceptual models usually conform to the Entity-Relationship (ER) metamodel (or some extension of it), the logical model maps ER models to relational tables and introduces normalization, and the physical model handles implementation issues such as possible denormalizations in the context of a particular database schema language. In this modeling methodology, there is a single hierarchy of models that rests on the assumption that one data model spans all modeling levels and applies to all the applications in some domain. The 'one true model' approach assumes homogeneity, but this does not work very well for the Web. The Web as a constantly growing ecosystem of heterogeneous data and services has challenged a number of practices and theories about the design of IT landscapes. Instead of being governed by 'one true model' used by everyone, the underlying assumption of top-down design, Web data and services evolve in an uncoordinated fashion. As a result, a fundamental challenge with Web data and services is matching and mapping local and often partial models that not only are different models of the same application domain, but also differ, implicitly or explicitly, in their associated metamodels." (Erik Wilde and Robert J. Glushko)
"XHTML2, a standard-building project planning a successor to XHTML, has been cancelled." (Mark Bernstein)
"This specification defines the Service Modeling Language, Version 1.1 (SML) used to model complex services and systems, including their structure, constraints, policies, and best practices. SML uses XML Schema and Schematron. (...) The Service Modeling Language provides a rich set of constructs for creating models of complex services and systems. Depending on the application domain, these models may include information such as configuration, deployment, monitoring, policy, health, capacity planning, target operating range, service level agreements, and so on. Models provide value in several important ways." (W3C)
"Single sourcing and its pragmatic flip side, reuse, remind me a bit of the early days of the personal computer. Everybody wanted one, but many weren’t sure what they would do with a computer if they got one. Even among seasoned user assistance architects, single sourcing and reuse remain elusive concepts. I recently heard someone at an STC chapter meeting define single sourcing as producing the same document as both a Help file and as a PDF file. Basically true, but one would hope there is more to it than that." - (Mike Hughes - UXmatters)
"Writing for Kindle is like writing for print, the Web, and mobile devices combined; optimal usability means optimizing content for each platform's special characteristics." - (Jakob Nielsen - Alertbox)
"The Extensible Markup Language (XML), which just celebrated its 10th birthday 4, is one of the big success stories of the Web. Apart from basic Web technologies (URIs, HTTP, and HTML) and the advanced scripting driving the Web 2.0 wave, XML is by far the most successful and ubiquitous Web technology. With great power, however, comes great responsibility, so while XML's success is well earned as the first truly universal standard for structured data, it must now deal with numerous problems that have grown up around it. These are not entirely the fault of XML itself, but instead can be attributed to exaggerated claims and ideas of what XML is and what it can do." (Erik Wilde and Robert J. Glushko)
"An XML Pipeline specifies a sequence of operations to be performed on zero or more XML documents. Pipelines generally accept zero or more XML documents as input and produce zero or more XML documents as output. Pipelines are made up of simple steps which perform atomic operations on XML documents and constructs similar to conditionals, iteration, and exception handlers which control which steps are executed." (W3C)
"Forms can be dreadfully tricky to style and structure properly. Several articles that are out there focus on best practises for building forms using HTML en CSS. This article focusses in a non technical fashion on the use of meaningful nomenclature and how form semantics relate to elements that current markup standards have to offer. It may help you recognise structural patterns and to compose forms properly." (Cornelis Govert Adriaan Kolbach - cornae.org)
"The wheels of progress turn slowly, but turn they do. The crystal ball might be a little hazy, but the outline of XML's future is becoming clear. The exact time line is a tad uncertain, but where XML is going isn't. XML's future lies with the Web, and more specifically with Web publishing." (Elliotte R. Harold - IBM developersWork)
"Ten years ago, Håkon Wium Lie and Bert Bos gave us typographic control over web pages via CSS. But Verdana and Georgia take us only so far. Now Håkon shows us how to take web design out of the typographic ghetto, by harnessing the power of real TrueType fonts." (Håkon Wium Lie - A List Apart)
"One of the hallmark attributes of web standards-based design is the concept that proper use of semantic (X)HTML and CSS completely abstracts the presentation of a site from its content. One key real-world benefit of this separation is that come redesign time, one only needs to change or replace the CSS stylesheet, and needn't lay so much as a finger upon the hallowed grounds we call markup. I'm here to say that this mantra isn't much more than a fairy tale." (Jeff Croft)
"Once enough large web companies use web standards and loudly proclaim that fact, other large companies will start to be afraid of missing the Latest and Greatest (always a source of management panic), mend their ways, and start to demand standards awareness from their employees and freelancers, too." (Peter-Paul Koch - A List Apart)
"Today, complex layout methods have made it possible to borrow from interaction patterns of desktop applications, including drop down menu bars, expanding trees and tabs. It's this exact inevitable shift of desktop application design patterns to the page metaphor that has more than often led to confusion amongst both web designers and end users. In this era of AJAX en RIAs, the possibilities for user interface designers have become infinite. Hence the question arises: Have all of these developments actually led to an improved user experience?" (Cornelis Kolbach - cornae)
"To define a web-format that addresses existing problems and requirements, and will last, needs a lot of work and consultation. XHTML2 is close to ready now, and will go to last call this year we expect. XForms is already in widespread use. Even if XHTML2 is not available in browsers, it is excellent as a content language that can be transformed on the fly. Several large companies are already doing this. (Steven Pemberton)
"#1: Everything you know is wrong... sort of; #2: It's not going to look exactly the same everywhere unless you're willing to face some grief... and possibly not even then; #3: You will be forced to choose between the ideal and the practicable; #4: Perfection is not when there’s nothing to add, but when there’s nothing to take away; #5: Some sites are steaming heaps of edge cases; #6: Longer lead times are inevitable; #7: Coherent and sensible source order is the best of Good Things; #8: Descendant selectors are the beginning and end of genuinely powerful CSS rules; #9: In the real world, stylesheet hacks will get your project across the finish line; #10: Working around rendering bugs is like playing Whack-a-Mole; #11: When you're drowning in CSS layout problems, make sure of the width and height of the water, float without putting up a struggle, and get clear of the problems; #12: Background images will make the difference between the plain and the tastefully embellished." (Ben Henick - A List Apart)
"In this article, we’ll review what people are doing with microformats right now, and finish up by looking at a couple of cool projects that might whet your appetite for microformats' future prospects." (John Allsopp - Digital Web Magazine)
"By now there isn't a software developer on earth who isn't aware of the collection of programming technologies known as AJAX. But you can't bank awareness. So, how in concrete terms can you take advantage in your own projects of this newly popular way of delivering online content to users without reloading an entire page? How soon can you be monetizing AJAX?" - including a webcast by JJG. (SYS-CON Media)
"(1) Microformats enable the publishing and sharing of higher fidelity information on the Web. (2) Small bits of (X)HTML that identify richer data types like people and events in your webpages. (3) Building blocks that enable users to own, control, move, and share their data on the Web." (Tantek Çelik - An Event Apart)
"Big complex data models look really imposing and impressive, but at the end of the day, XForms got their start largely because the existing HTML forms just weren't expressive enough. Consider some of the more vexing problems associated with typical web forms. Suppose that you wished to..." (Kurt Cagle - O'Reilly XML Blog)
"You can't just ask Dreamweaver for the code - it's currently a hand coding exercise." (John Whalen - HFI)
The CD Version of the Fourteenth International World Wide Web Conference held at Makuhari Messe on May 10-14, 2005, in Chiba, Japan (WWW2005) - courtesy of stevenpemberton
"The development of Web technology has been an exciting ride, a series of socially motivated technical innovations some languishing, others catching on in a viral way. As each development has suggested many new ones, and much of the original vision is still unfulfilled, there is a lot to do. This talk will discuss new challenges and hopes for weblike systems on the net." (Tim Berners-Lee - Oxford Internet Institute Webcasts) - courtesy of boingboing
"It sometimes seems like widely popular web-standards innovation halted around 2000, and the last few years have been a period of very slow catch-up. Various visions of a new Web, a better Web, have come and gone, leaving behind useful parts but not yet transforming the Web. Are we on the edge of the next big thing? It may make sense to look at the last few big things, comparing their visions with what's happening today." (Simon St. Laurent - XML.com) - courtesy of thinkingandmaking
"The trick... is to make sure that each limited mechanical part of the Web, each application, is within itself composed of simple parts that will never get too powerful." - says Tim Berners-Lee (Tantek Çelik - Microformats)
"In December 2005, we did an analysis of a sample of slightly over a billion documents, extracting information about popular class names, elements, attributes, and related metadata. (...) You will need a browser with SVG and CSS support to view the result graphs correctly. We recommend Firefox 1.5." (Google Code) - courtesy of justaddwater
"(...) validating your XHTML files, migrating from XHTML to XML, possible XML standards, creating your own standard, validating your XML files, and creating an XML to HTML transform." (Char James-Tanny - WritersUA)
"In this two-part series, Edd Dumbill examines the various ways forward for HTML that Web authors, browser developers, and standards bodies propose. This series covers the incremental approach embodied by the WHATWG specifications and the radical cleanup of XHTML proposed by the W3C. Additionally, the author gives an overview of the W3C's new Rich Client Activity. Here in Part 1, Edd focuses primarily on two specifications being developed by WHATWG: Web Applications 1.0 (HTML5) and Web Forms 2.0." (Edd Dumbill - IBM)
"Recently, there has been a lot of talk about Rich Internet Applications (RIAs), how they work, and how to choose the appropriate RIA technology. Unfortunately, so far, we've had few discussions about the value of RIAs to users and how RIA technologies let us create better, more usable Web applications." (David Heller - UXmatters)
"With the recent rise in popularity of web technologies such as Flash and AJAX, it has become possible to create richer user experiences on the web. Even though these technologies are not actually new, we are now seeing their widespread adoption. Within the last six months, we have seen the christening of the term 'AJAX' and its broad acceptance. Most major websites are adding rich interaction to their existing features" (Bill Scott - Boxes and Arrows)
"This is the first part of a two-part article describing a detailed methodology for migrating HTML files to the structure and flexibility of XHTML and/or XML. By using XHTML to add structure and separate content from presentation, you'll be better positioned for a move to XML. Even if you never move to XML, your XHTML files will be easier to create and maintain, and will be more accessible." - (Char James-Tanny - WinWriterUA)
"Thanks to the generous permission of the speakers, you can listen to all these sessions from WE05." (Web Essentials 2005) - courtesy of webgraphics
"(...) the unexplored ways we can evolve Web conventions without the constraints of the old hypertext interaction model, are why the recent Ajax explosion signals a new chapter in the history of Web design." (Jesse James Garrett - OK/Cancel)
"In the past few years, developers could choose between two approaches when building a web application. The first approach was to create a screen-based system with very rich interactions using a sophisticated, powerful technology such as Java or Flash. The alternative approach was to create a page-based system using easier-to-learn core web standards like XHTML and CSS whose more basic capabilities force less-rich interactions. A new technological approach, dubbed Ajax, might just be the right mix between the two." (Joshua Porter - UI 10 Conference)
"As AJAX applications become more widespread and users begin to expect more of the rich interactions they enable, some of the over-communicating happening today may not be necessary. Until then, however, it's necessary to consider the expectations users have and meet them accordingly." (Luke Wroblewski - Functioning Form)
"Ajax breaks the interaction model of the Web. It faces the unique user interface problem of blending the expectations users have of a website with the behavior of a desktop application. This is the consequence of giving the user desktop app powers within their trusty browser." - (Quinn Norton - O'Reilly Network)
"State requires a lot of thought and consideration. If we are going to build the web for amateurization or personal information architectures that ease how people build and structure their use of the web, we must provide state." (Thomas VanderWal)
"Web Application Solutions is a guide that helps designers, product managers, and business owners evaluate some of the most popular Web application presentation layer solutions available today. We compare each solution through consistent criteria (deployment & reach, user interactions, processing, interface components and customization, back-end integration, future proofing, staffing and cost, unique features) and provide an overview, set of examples, and references for each." (Luke Wroblewski - Functioning Form)
"This document explains how and why using web standards will let you build websites in a way that saves time and money for the developer and provides a better experience for the visitor. Also discussed are other methods, guidelines and best practices that will help produce high-quality websites that are accessible to as many as possible." (Roger Johansson - 456 Berea Street)
"Ultimately, the push for standards-compliant code should come from the coding ranks. We need to enlighten all levels of management to the savings they can achieve by embracing Web standards. If the people on the front lines don't take on the job of promoting standards to management and management learns of these savings first, you'll be faced with a tougher challenge-why didn't you know to use and push for standards-compliant code?" (Alan K'necht - Digital Web Magazine)
"On the web, CSS is the style sheet language of choice. However, the usefulness of CSS is not limited to screens. If you want to transfer web content -- be it XML or HTML -- onto paper, there are good reasons to use CSS. The language is radically simpler than that of XSL, and it is suitable both on-screen and on paper. This means that you probably don't have to write a stylesheet at all but can reuse an existing one." (Håkon Wium Lie and Michael Day - xml.com)
"SMIL 2.0 has the following two design goals: (1) Define an XML-based language that allows authors to write interactive multimedia presentations. Using SMIL 2.0, an author can describe the temporal behavior of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen. (2) Allow reusing of SMIL 2.0 syntax and semantics in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL 2.0 components are used for integrating timing into XHTML and into SVG." (W3C)
"As an experiment in the use of SMIL, a captioned version of Jeffrey Zeldman's Web Essentials 04 video keynote, using Quicktime SMIL 1.0." (splintered)
"The World Wide Web uses relatively simple technologies with sufficient scalability, efficiency and utility that they have resulted in a remarkable information space of interrelated resources, growing across languages, cultures, and media. In an effort to preserve these properties of the information space as the technologies evolve, this architecture document discusses the core design components of the Web. They are identification of resources, representation of resource state, and the protocols that support the interaction between agents and resources in the space. We relate core design components, constraints, and good practices to the principles and properties they support." (W3C)
"So what does media-neutral content look like? It focuses on tasks and concepts, not on chapters and appendixes. It follows the same basic information design principles that have informed good manual design and good online design for decades: task orientation, minimalism, and scenario-based development. If you author tasks and concepts, rather than sections and paragraphs, you have the makings of a topic collection that can be reordered for different needs, supporting different task flows for different users, and supporting different reading paths for different media. " (Don Day, Erik Hennum, John Hunt, Michael Priestley, David Schell, Nancy Harrison - WritersUA)
"The World Wide Web's markup language has always been HTML. HTML was primarily designed as a language for semantically describing scientific documents, although its general design and adaptations over the years has enabled it to be used to describe a number of other types of documents. The main area that has not been adequately addressed by HTML is a vague subject referred to as Web Applications. This specification attempts to rectify this." (Web Hypertext Application Technology Working Group)
Unfinished version of an essay on 'Web applications'. - "The light-weight, Web-based applications ('webapps') of this essay are small, platform-independent programs that are downloaded on demand and execute inside a client program, such as a browser. They are thus like Java applets, but more 'script-like' than 'program-like' and therefore easier to write in many cases (though harder in others). They have a clearly separated user interface, that allows webapps to be easily adapted to different devices." (Bert Bos - The W3C Workshop on Web Applications and Compound Documents Position Papers)
"This essay is an excerpt from the book 'Peer-to-Peer Harnessing the Power of Disruptive Technologies'. It presents the goals that drive the developers of the best-known peer-to-peer systems, the problems they've faced, and the technical solutions they've found." (Rael Dornfest and Dan Brickley - O'Reilly openP2P)
"(...) the project seeks to define and develop a system is focused on the simulation and communication of complex ideas. We call this 'communication enhancement' - the direct extension of the abilities of humans to develop, understand, and describe even the most complex simulations." (About Croquet)
Doug Bowman Presentation at Web Essentials 04 - "Building designs with CSS is no longer a fringe activity practiced by standards geeks and early-adopters. Creative pioneers and highly skilled designers are bringing CSS to the mainstream. The explosion in popularity is ushering in a new wave of possibilities for web design. CSS provides greater design control, allows more flexibility, and enables sites to become attractive, accessible, and faster-loading, all at the same time." (Stopdesign) - courtesy of elearningpost
"The World Wide Web is an information space of interrelated resources. This information space is the basis of, and is shared by, a number of information systems. Within each of these systems, people and software retrieve, create, display, analyze, relate, and reason about resources. Web architecture defines the information space in terms of identification of resources, representation of resource state, and the protocols that support the interaction between agents and resources in the space." (W3C)
"The purpose of the SPARK project is to create a flexible, interoperable SVG-based user interface framework. Using well established and standardized languages including SVG, XML, Java and IDL, we went about creating a framework that could easily be used by others to rapidly develop SVG based applications or prototypes." (SVG Open 2003)
"Generally speaking, standards are a means to apply pressure on corporations to behave in a manner that is beneficial to everyone, not just the shareholders of the corporation." (Andrei Michael Herasimchuk - Design by Fire)
"With all the discussion about separating presentation from content (and structure), it's easy to lose track of the goal. So let's step back, define our terms, and take a look at why it matters." (Michael Cohen - A List Apart)
"The specifications in the Matrix are at least at Last Call stage, except if they are working on a Test Suite at Working Draft stage. An empty cell means that the data is either not available or not known by the maintainers of the Matrix. The Matrix contains 70 Recommendations, 18 Candidate Recommendations, 0 Proposed Recommendations and 15 Last Call Working Drafts." (W3C)
"Mixing the worlds of documents, programming, and visual design is a familiar experience for XML developers, especially when dealing with presentation technologies like SVG. Such mixtures can produce exciting new representations of information." (Fabio Arciniegas A. - XML.com)
"Even though Web standards are being embraced by many Web authors, some businesses are reluctant to invest in standards-based Web sites without concrete reasons to do so. To help Web authors interested in advocating Web standards, this article assembles arguments and information about Web standards into one document and explains Web standards in terms of how they affect business." (MACCAWS) - courtesy of elearningpost
"The number of wireless visitors using tiny browsers with ever increasing capacities is unlikely to diminish." (Heidi Pollock - Webmonkey) - courtesy of nick finck
"The concept of a datument as a hyperdocument for transmitting and preserving the complete content of a piece of scientific work is introduced. Currently the scientific publishing process loses almost all of the information environment that the author creates or possesses. It is shown that datuments can record and reproduce experiments and act as a lossless way of publishing science. This is illustrated with specific examples drawn from scientific documents and molecular science, showing how a datument containing molecular coordinates can be viewed in various styles and how typical documents deriving from organic and physical chemistry and expressed in XML can be transformed using XSLT." (Peter Murray-Rust and Henry S. Rzepa - Journal of Digital Information)
"The OWL Web Ontology Language is designed for use by applications that need to process the content of information instead of just presenting information to humans." - W3C Recommendation (W3C)
"A few years ago, virtually the only way to access the Web was through a personal computer or workstation. True, there were variations between the facilities offered by various browsers, some being capable of use on text-based terminals. However, almost invariably, Web access, for individuals without specific accessability needs, involved using a machine with a reasonably large, color display with full graphic capabilities. While this is still primarily true, since the middle of 2000, the number of different kinds of device that can access the Web has grown from a small number with essentially the same core capabilities to many hundreds with a wide variety of different capabilities. At the time of writing, mobile phones, smart phones, personal digital assistants, interactive television systems, voice response systems, kiosks and even certain domestic appliances can all access the Web." (W3C)
"The Zurgle project is a campaign to help clean up some of the sharper edges on the current Squeak desktop by adding things like emulated widgets and window skins." (Squeak)
"In this article, a try has been made to see CBD from a developer's perspective. We shall see that support does exist in terms of modeling the CBD process, but the level of support differs significantly at different stages of the process. We will see how UML supports a service-based architecture and what sorts of model it provides for the different people in the development team. We try to explore the different models provided by UML to analyze, design and implement the Component-Based systems and see what sort of support do they provide for the different levels in development process." (Amjad Bashir - Journal of Conceptual Modeling)
"Designing a data-intensive Web site amounts to specifying its characteristics in terms of various orthogonal abstractions, each captured by a distinct model. The structure, composition, navigation, and presentation models enable the description of read-only web sites. They can be extended to cope with the specification of content management and integration with external services, through the addition of operations, which can be defined and added to the hypertext model. They are invoked as a side effect of navigation and permit one to specify commonly found interaction patterns as data entry, personal data management, and shopping carts." (About WebML.org)
"Interaction (input, output) between the user and the application may often be conceptualized as a series of dialogs, managed by an interaction manager. A dialog is an interaction between the user and the application that involves turn-taking." (Peter Mikhalenko - XML.Com)
"Like XHTML, SVG, and RSS, XForms is an XML-based language written with tags that can be identified by surrounding angle brackets. (XML purists perfer to call these elements) Learning XForms is largely a matter of understanding what individual elements do, as well as how they interrelate. One difference is that XForms provides several more elements than form authors might be accustomed to. As a result, several tasks that would have otherwise required complicated scripting can be accomplished declaratively, just by putting the right elements in place." (About XForms Institute)
"Multipage tax input forms with calculations and validations; Web shop order forms (...) anything that needs user interaction within Web document formats." (Kari Pihkala, Mikko Honkala, and Petri Vuorimaa - SMIL Europe 2003)
OWL: Web Ontology Language - Overview
"The OWL Web Ontology Language is designed for use by applications that need to process the content of information instead of just presenting information to humans." (W3C)
"The World Wide Web is a network-spanning information space of resources interconnected by links. This information space is the basis of, and is shared by, a number of information systems. Within each of these systems, agents (people and software) retrieve, create, display, analyze, and reason about resources. Web architecture includes the definition of the information space in terms of identification and representation of its contents, and of the protocols that support the interaction of agents in an information system making use of the space. Web architecture is influenced by social requirements and software engineering principles, leading to design choices that constrain the behavior of systems using the Web in order to achieve desired properties of the shared information space: efficiency, scalability, and the potential for indefinite growth across languages, cultures, and media. This document reflects the three bases of Web architecture: identification, interaction, and representation." (W3C)
"There are problems, mostly editorial in nature, for which there are no technical solutions. As such, XML as a technology does not solve them. However, I think it does provide a platform on which to build solutions." (Norman Walsh - Journal of Digital Information / Theme: Information management)
"(...) a digital identifier for any object of intellectual property. A DOI provides a means of persistently identifying a piece of intellectual property on a digital network and associating it with related current data in a structured extensible way." (The Digital Object Identifier) - courtesy of leo robert klein
"(...) the xml schemas for Microsoft Office Word 2003 (WordprocessingML) along with documentation." (Infostructurebase) - courtesy of langemark
"It's time to take back control over the tabs which are continually growing in popularity as a primary means of site navigation. Now that CSS is widely supported, we can crank up the quality and appearance of the tabs on our sites." (Douglas Bowman - A List Apart 3.0)
"The key point of the semantic web is the conversion of the current structure of the web as a data storage (interpretable only by human beings, that are able to put the data into context) into a structure of information storage. In order to convert data into information we have to put it into context by adding metadata, data that contains the semantics, the explanation of the data it refers to; in the end, the context." (Juan C. Dürsteler - Info@Vis!)
"Strap on your mental protective gear and join IBM Fellow Grady Booch on a high-energy tour of things unusual, curious, and just plain weird. Of course there are lessons to be learned along the way, as we discover how common design principals inform even the most uncommon of entities. We'll also explore the evolution of different genres of architecture, the forces that have shaped them, and their practical manifestation in today's Web- and services-oriented architectures." (IBM Rational Events)
"These aren't formulas for determining the ROI of migrating to standards, but they are some pretty good financial justifications. 'It's what all the cool sites are doing' shouldn't be your only point when arguing for a switch to XHTML and CSS. The economic benefits of standardization are tangible. Once we can quantify them, businesses will begin realize the true promise of the Web - interoperable content freely shared." (Jeffrey Veen - Adaptive Path) - courtesy of lawrence lee
"Can you take a simple list and use different Cascading Style Sheets to create radically different list options? The Listamatic shows the power of CSS when applied to one simple list using samples (...)" (Max Design) - courtesy of jeffrey zeldman
"Here's where I begin to fly in the face of common consensus - it being that if you code to web standards, it makes for easier maintenance of your site to those joining a project later. My experience has, thus far, shown the opposite to be true. It pains me to admit this." (Ian Lloyd - Mezzoblue)
"(...) XForms, a combination of two of the most successful experiments ever performed on the Web: XML and forms." (Micah Dubinko)
"It takes the same amount of work and money to design for one browser as it does to design for all browsers and devices." (Jeffrey Zeldman)
"If youíre reading this article in the hopes of learning how to get an adult site listed in the 'school supplies' category on Google, we kindly suggest you fall off the face of the earth. Any hate mail regarding this can be directed to email@example.com. It's due time to pay her back for all those 'petting zoo pictures' that manage to bypass my spam filtering system." (Brandon Olejniczak - A List Apart)
"The Web is all about helping humans communicate, but what hopefully becomes clear from this essay is that writing specs also is a form of human communication. There is one word that summarizes nearly all the fancy keywords of this essay, and that is:..." (W3C) - courtesy of dave winer
"XForms is an XML application that represents the next generation of forms for the Web. By splitting traditional XHTML forms into three partsóXForms model, instance data, and user interfaceóit separates presentation from content, allows reuse, gives strong typingóreducing the number of round-trips to the server, as well as offering device independence and a reduced need for scripting." (W3C)
"Cascading Style Sheets can be one of the most important tools in a user-centered designerís toolkit when working on rapid prototyping. The combination of valid HTML/XHTML markup and external CSS can be used to rapidly create prototypes, speed up the development process, and easily incorporate more user-centered techniques into the design process." (Jeff Lash - Digital Web Magazine)
"If you mention Scalable Vector Graphics language (SVG) in a crowd of web developers they will immediately gravitate to the question of whether it can 'beat' Flash. Recently SVG Print has focused attention on the question of whether SVG can compete with PDF and Postscript. These are exciting possibilities: it would be great to unify these domains under a standardized, XML-based syntax. Nevertheless, it is ultimately quite limiting to define SVG by its success in replacing these existing technologies. SVG is much more than a Flash and PDF-killer." (Paul Prescod - SVG Open 2003)
"In the First Era of browser history Mosaic and the other early browsers ruled. The Second Era was that of Netscape dominance. Microsoft's challenge to Netscape marked the beginning of the Third Era, the Heroic Age of the Browser Wars. Netscape's bleeding to death marked the start of the Fourth Era of Explorer dominance. The recent news about Explorer shows that this Era has come to an end, too. We stand at the beginning of the Fifth Era of browser history. What will it bring?" (Peter Paul Koch - Evolt)
"Slides of the presentation held in Brussels, Belgium, on the 24 June, 2003 at the W3C Semantic Tour event, organized by the W3C Benelux Office (...)" (Ivan Herman - W3C)
"Squeak is a 'media authoring tool' -- software that you can download to your computer and then use to create your own media or share and play with others." (Alan Kay c.s.)
"The World Wide Web is a networked information system. Web Architecture consists of the requirements, constraints, principles, and choices that influence the design of the system and the behavior of agents within the system. When Web Architecture is followed, the large-scale effect is that of an efficient, scalable, shared information space." (W3C) - courtesy of tim bray
"The World Wide Web is a networked information system. Web Architecture consists of the requirements, constraints, principles, and design choices that influence the design of the system and the behavior of agents within the system. When followed, the large-scale effect is that of a shared information space. This document organizes the technical discussion of the system in three parts: identification, representation, and interaction. This document also addresses some non-technical (social) issues that contribute to the shared information space." (W3C) - courtesy of tim bray
"In this article, we're going to start a project to design an XML format that could be generated from IDL, TLB, XDT or any other representation of a portable component and then be read by any language that supports XML and further manipulated to generate GUI tools, documentation, and more." (Kyle Downey - O'Reilly XML.com)
"A demonstration of what can be accomplished visually through CSS-based design." - (Dave Shea)
"What are Web Servies? Program integration across application and organizational boundaries. (...) What is Semantic Web? Data integration across application, organizational boundaries." - (Tim Berners-Lee - The Twelfth International World Wide Web Conference)
"Taxomita is a tool for creating faceted taxonomies using PHP and MySQL." (Peter van Dijck)
"Recently in this space I complained that XML is too hard for programmers. That article got Slashdotted and was subsequently read by over thirty thousand people; I got a lot of feedback, quite a bit of it intelligent and thought-provoking. This note will argue that XML doesn't suck, and discuss some of the issues around the difficulties encountered by programmers." (Tim Bray - Antartica Systems) - courtesy of mark bernstein
"When the mainstream trade press first started writing about XML, one of the key benefits invariably cited was precise search. You don't hear much about that any more. It wasn't, and still isn't, the wrong idea, but XML-savvy search requires an investment in data preparation that virtually nobody was or is willing to make." (Jon Udell - XML.com)
"The goal of IML is to enable handheld computers, (that have limitations in the display size and input capabilities), to access and render content from the Internet." (Simputer Project) - courtesy of dmitri ragano
"Ultimately, I donít see a long term future for HTML as an application development solution. It is a misapplied tool that was never meant to be used for anything other than distributed publishing." (David Heller - Boxes and Arrows)
"(...) a modularized language for describing two-dimensional vector and mixed vector/raster graphics in XML." (W3C)
Embedding Flash while supporting standards (Drew McLellan - A List Apart)
"(...) to provide a language that can be used to describe the classes and relations between them that are inherent in Web documents and applications." (W3C)
"(...) guidelines for designing user agents that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological)." (W3C)
XUL is a new Netscape/Mozilla XML dialect that describes the elements of a traditional user interface. Faster and cleaner than HTML, it might just be the quickest way yet to code a UI. (Nigel McFarlane - DevX)
"(...) design principles for creating accessible Web sites." (W3C)
"Most people who have thought about XML at a high level haven’t thought too much about the problems inherent in converting unstructured content into a meaningful XML format." (Rizwan Virk - CambridgeDocs)
"(...) the set of principles that all agents in the system follow to create the large-scale effect of a shared information space." (The World Wide Web Consortium)
"Adhering to standard vocabularies has recently meant all too often that an item properly labeled and conforming to an expected form is naively accepted as being actually what it purports to be." (Walter Perry - xml.com)
"This article discusses the creation of useful graphical presentations of quantitative XML data using XSLT and SVG." (Fabio Arciniegas - O'Reilly's XML.COM)
"(...) W3C is developing standards for a new class of mobile devices that support multiple modes of interaction." (W3C)
"(...) a place to learn about topic maps" (Peter Van Dijck)
"A functional spec is a document detailing the client's requirements for an application." (mojofat)
"(...) a 'Semantic Web' that understands the meanings that underlie the tangle of information" (Mark Frauenfelder - MIT Technology Review)
XML Document Types for Everyone (doctypes.org)
"(...) the cultural clash between three groups often involved in Web projects: front-end developers, information architects and visual designers." (Gordon Bennett - Intranet Journal)
How to create flexible sites quickly using standards like CSS and XHTML. (James Lewin - The Lewin Group)
"The audience of this paper are developers and designers of web applications" (Jim Conallen)
"(...) they can help you to describe and understand emergent behaviour of complex and dynamic systems" (Use Case Maps User Group - Carleton University)
"This document lists all the modules to be contained in the future CSS3 specification" (W3C)
"Topic Maps provide for the specification of a standard, interchangeable hypertext navigation layer above diverse electronic information sources" (InfoLoom, Inc.)
"A new form of Web content that is meaningful to computers will unleash a revolution of new possibilities" (Tim Berners-Lee et al. - Scientific American)
"XHTML is both strong and important." (Molly E. Holzschlag - WebReview.com)
"(...) not a complete set of guidelines for good user agent behavior" (W3C)
"An information architect (...) possesses the background and aptitude for designing and implementing document structure" (Michael Floyd - Webtechniques)
"(...) developing the applicability of the Topic Maps Paradigm to the World Wide Web" (TopicMaps.org)
Point of Interest eXchange Language / NaVigation Markup Language (W3C Notes)
"Some curmudgeonly comments on bad Web design" (Eric S. Raymond)
"XML is very powerful (...)" (School of Library and Information Science at Indiana University)
A description of the information available in a well-formed XML document (W3C Working Draft)
Needed Rules for XML Documents (Simon St. Laurent at XML DevCon 2000 NYC)