vanderwal.net

One thing that I have had the benefit of viewing and discussing while at SXSWi is Flash. Folks from Macromedia have shown their soon to be released version of Flash. Flash MX (as it is named) has some very good new features, in its providing common Web development objects to help developers create scroll bars and the like very easily. The application seems to provide object or extensions to Flash that streamline the process to building something usable and consistent in Flash.

The best new feature of Flash is content can now be made accessible for those with sight disabilities. This is greatly helpful as Flash is largely a visual information development and presentation tool. The information is now usable by site readers that read information aloud stored in Flash. This has been a large hinderance for many folks who would like to adopt Flash into their development tool belt, but had restrictions that limited the use of Flash because it locked out a segment of the users who had visual disabilities.

There is one large element in Flash that is completely disappointing still. The information is not accessible for reuse. All Flash can provide is visual information presentation, which restricts a user's ability to copy and paste or to have the information machine readable. The information is locked in an unusable format for these purposes. What does this affect? If a hotel provides their phone number and address in their Flash presentation the user can not copy and paste the information out into their PIM (Outlook, Access, Palm desktop, etc.), to an e-mail, or text message that the user could read from their PDA or cell phone (given messaging capabilities). The user would also be restricted from grabbing the information to put together a matrix from which to make decisions or to supply to others to make their comparisons. The locking of information in Flash requires the user to retype the information provided, which introduces the ability for errors in the information that was carefully crafted.

Not only do human users have the inability to re-purpose the information, which is a great benefit to those providing the information, but machines are precluded from accessing the information. If the same hotel wants to be included in their city's chamber of commerce listing on the CCoC Web site the hotel information can not be easily extracted by the CCoC as it could be from HTML (using an id tag) or XML. The information is locked again in an unusable and un-reusable format. The creators of the content lose, and could possibly lose big by not having information that is easily reused. This becomes increasingly important with the growing use of Web Services that rely on machine readable or machine accessible information.

Why the hotel scenario? Macromedia used the hotel demonstration to highlight some of their great new features. As I watched the presentation I kept wondering if the information was still unusable for purposes other than reading or having the information read to the user. It was later confirmed the information was still un-reusable, but Macromedia is also aware of this strong down side to the information presentation and is working hard at fixing the issues.

Yesterday was all about getting the synapses to fire in the right order at SXSWi. I was running on sever sleep deprivation from phones and alarm clocks ringing when I had not finished my needed sleep cycle. None-the-less I had a great time. I greatly enjoyed Steve Champeon's peer panel on Non-Traditional Web Design, as it focussed on the fine art of tagging content, understanding the uses of information, and the true separation of content, presentation, and application controlling the information. The Web Demo panel I was on seemed to go rather well as there were a broad spectrum of sites reviewed and the information from the panel to the developers was of great use (I hope) as I think we all learned something.

The evening provided good entertainment, a wonderful gattering at the EFF party. Once again many folks adjourned to the Omni Hotel lobby for the after-hours social gathering. I spent much of the time just listening to conversation and occasionally partaking. Of intrigue was Rusty of Kuro5hin and Adam of Brian of Slashdot discussion development of site tools that will help a dynamic site fly, keep in mind all these tools are in Perl.

Representational State Transfer (REST) and the Real World provides the ability to add security to XML-based Web Services, among other beneficial elements.

The school of hard knocks teaches us to learn where the pitfalls may lie in our plans as we are in the discovery and planning stages so we do not add to our "lessons learned". Web Services Pitfalls from O'Reilly Net and XML.com provides this wonderful bruise saving insight.

Web Services, the new plastic. More on Web Services in A List Apart article. Patrick Cooney provides a wonderfully quick background and foundation of understanding on WS.

The current term the neighbor from the Graduate would say is "Web Services". If you have Mac OS X, then O'Reilly Net's "AppleScript Primer for Mac OS X" is your passage to understanding how to do Web Services today. This means you don't have to wait for the expensive .Net Framework as you have the the technology now.

Web Services Interoperability from James†Snell on O'Reilly Net's XML.Com. This wonderful piece demonstrates, with code, the interaction that is currently possible with standard development environments. This is familiar territory for me from a recent past life, although it was not using SOAP, like these examples do.