Grids are Good
markboulton.co.uk and ????
• yeeaahh.subtraction.com
• This is basic common sense – nothing new.
• Basically, come up with a flexible column/grid structure to afford many possible layouts that don’t harsh the eye when transitioning from one to teh other.
• 12 is a pretty number.
Tag, You’re It
Heath Row (named after an airport???), Oates (Flickr), Brown, Vander Wal
Georgia Oates (Flickr):
• Should tags be emergent or centrally controlled
• Flickr has about 9 000 000 unique tags. 3 000 new photos every minute.
• Controlled tag sturctures can exist within an emergent cloud (e.g., wildflower tagging group)
• Clusters
• Infection: doyourworst
• inference: tag cloud example
• When tagging the aggregate define things unintentionally
• folksonomy :: machine tags :: taxonomy
•
Brown (Consumating):
• Unique tags have little value, but rare and shared tags become more valuable until it become too ubiquitous
• Consumating is releasing its source code in the next couple of months (Perl).
Vander Wal
• Magnolia
• Public libraries are opening up books to folksonomy to enhance their catalog
• Cork’d – wine website
• lastfm
• realtravel
• UK Guardian is tagging their resources
• With emergent tagging it is actually difficult to stem similar tags because the groups that grow around them are different (more zen than logic)
• Scaling and Functionality: as #taggers adn #tags grows a tag gevolves: personal use, serendipity, social tagging powerful, mature system that gives you aggregate data that you sould not have foreseen
• LibraryThing example
• RawSugar and Amazon
• tagcommons
• if you make the tag clouds public then you must accept the good with the bad.
• see rawsugar “facets” – groups tags by inferring stems in the emergent tags
Getting to Consistency: Don’t Make Your Users Think
Jennifer Fraser (Corel), Alex Graveley (VMWare), Steve Johnson (Adobe)
• Consistency may not be indicated just to be consistent. It is important for similar functions, but each app needs identity.
• Cross platform compatibility can cause a cost to being consistent.
• If you are not careful, consistency becomes legacy.
• A focus upon features is not always inline with customer goals. Consistency might mean changing features to meet the same customer goals.
• This discussion could have greatly benefitted from having one of the people from the Microsoft Office team that developed the ribbon interface.
• Determining the workflows (use cases) for an app determines the environments that need to have consistency.
• Workspaces: role-based feature sets – not aimed at current, users, but as an entry point for new users (- Adobe guy)
• Apps on the web do not have extroverted consistency – no HIG.
Saturday, 10 March 2007 @ 10:00
Lindsey Simon, Web Developer, Dishola/Google
Joe Orr, Dev, NYCircuits Inc
XSLT is one of the most exciting technologies to come out of the XML family. Unfortunately, its incredible power and associated complexity can be overwhelming to new users preventing many from experimenting with it or causing them to quickly give up in disgust. In fact, unless the method of teaching and the common style of use for XSLT is radically changed to make it more accessible, XSLT will be relegated to niche status like SGML and other powerful technologies.
— David Jacobs (http://www.xfront.com/rescuing-xslt.html)
Simon:
Orr: