Archive for the ‘Web Standards’ Category

The PSO is Getting Naked!

Tuesday, April 4th, 2006

April 5th is the first annual CSS Naked Day!

Welcome to the first annual CSS naked day which will be happening April 5th, 2006. The idea behind this event is to promote Web Standards. Plain and simple. This includes proper use of (x)html, semantic markup, a good hierarchy structure, and; well, a fun play on words. I mean, who doesn’t want to get naked?. Feel free to see the original reference article for more information.

SAP Portal and Web Standards

Monday, April 3rd, 2006

It has been a while since my last post. I have been hard at work contracting at a top pharma company in the Philadelphia area, developing their new website. For some strange reason, this company has decided to use the SAP Portal system to power their website. This has cause me nothing but problem with codiong. Usually the SAP portal system uses dozens of iframes throughout the site. With this newest version of the SAP portal, they introduced something that SAP calls “the light framework.” The light framework replaces the annoying and inaccessible iframes with a just as annoying and unnecessary nested tabling system.

I have been developing the internal pages using 100% valid XHTML and CSS, but after it enters the portal, any CSS layout styles I used were pretty much rendered useless. The nested tables destroy any dignity I gave it with dirty markup.

Today, while surfing the SAP Developer Networks, I read the latest post from Sven Kannengiesser. He goes through a little exercise on how to make the SAP Portal a little more Web Standards compliant. I had to chuckle at the article because of its attempt to teach developers of SAP about web standards. On the one hand, I find it awesome that someone at SAP cares enough about the front-end code to post something on the SAP blog. On the other hand, if a developer writes clean and compliant code, the SAP Portal destroys it with HTMLB and design layouts from 1999. Companies pay top dollar for this system and the code is cluttered with inconsistencies. Some <table> tags are written in all CAPS, while others are mixed case, and others are correctly all lowercase. There are also a number of empty tables lying around for no reason. There are many attributes that are not surrounded by quotes and most single line elements are not closed properly.

Why do people pay top dollar for such a half-assed product? My only hope is that this post gets back to the SAP developers and they decide to hire Eric Myer to oversee the front end development and produced SAP code. Until that happens, I will keep beating the SAP framework into submission while trying to make it as semantic as possible.

The original lord of standards

Friday, March 31st, 2006

Any good, upstanding web nerd knows Tim Berners-Lee. Recently he was interviewed by the British Computer Society. Berners-Lee makes some very good points about the state of the web and the direction its heading. Most of all he captures the essence of what has been discussed at several of the PSO meetings when asked about professionalism in IT.

When it comes to professionalism as a general topic there are important things to talk about and it makes sense to talk about being professional in IT. This may be a biased point of view, but standards are vital so that IT professionals can provide systems that last.

Customers need to be given control of their own data - not being tied into a certain manufacturer so that when there are problems they are always obliged to go back to them. IT professionals have a responsibility to understand the use of standards and the importance of making Web applications that work with any kind of device.

They need to take the view that data is a precious thing and will last longer than the systems themselves.

This point drives home the fact that Web Standards and best practices as a whole are more than just the trendy way to design. This idea is the driving force behind efforts like microformats. Web Standards provide us with a means of sharing information and proliferating it into the future.

Smuggling Proprietary CSS and the Validity of the Validator

Thursday, February 9th, 2006

Will makes an interesting point in his blog post about using browser-specific CSS and still having webpages validate. His quandry:

Have you ever been tempted to use a CSS property such as -moz-border-radius, but can’t stand the thought of having a page that refuses to validate?

He can’t add it to an external stylesheet through <link>, nor can he use it internally within <style>; if he does, neither will validate.

However, adding the proprietary CSS to a style attribute on an element gets around the problem, since the W3C HTML validator does not check the validity of CSS within style attributes.

Observe; the code below uses the -moz-border-radius, but the resulting HTML will still validate.

The code:

<div style="padding: 0.25em 0.5em;
   border: 2px solid #605953;
   -moz-border-radius: 25px;
   background: #f1efec;">
Lorem ipsum dolor sit amet, consectetuer adipiscing elit.
</div>

The result:

Lorem ipsum dolor sit amet, consectetuer adipiscing elit.

On the one hand, it’s a neat trick (not necessarily a hack) that gets around the validator and allows a developer to use non-standard styles on his page. On the other hand, that’s exactly it: it’s non-standard; and I agree whole-heartedly with Will, who so colorfully elucidates:

Yeah, it is kind of an ugly method, but you shouldn’t care since if you’re going to use it, right? After all, depending on proprietary CSS is like depending on a rotten wood catwalk over a tank full of the proverbial kind of bovine fecal matter.

All of the above got my brain thinking about validation and standards.

The W3C Validators are not the end-all-be-all definitive sources for creating standards-based websites. As Will (and now I) have successfully pointed out, proprietary (and, in most cases, non-standard, non-valid) code can be “smuggled” into a website and can trick the validators into thinking the code is perfectly valid.

The point is that standards are about much more than just validation. They are also about what works for you. You may have a certain work ethic, i.e. a personal standard, that no one else has heard of, let alone uses for himself. Does that make your work ethic any less valid? Pft. Of course not.

Any Joe with an Internet connection and a text editor can create a page that validates and claim it’s “standards-compliant”. As Mike Davidson wrote almost twenty months ago:

Web standards are about all the processes involved in publishing information over IP. [...] Just because you can validate your code doesn’t mean you are better than anybody else. Heck, it doesn’t even necessarily mean you write better code than anybody else. [...] Spewing validation manifestos on message boards isn’t going to show you how to listen, negotiate, compromise, and execute.

Developers Recommended to Support IE Rivals

Wednesday, January 25th, 2006

Web developers have been told to ensure that the sites they build are operable with browsers which rival Internet Explorer. This includes open-source heroes Firefox and Apple’s Safari. Deri Jones of SciVisum explains their reasoning and has the XiTI metrics to back it up:

Jones advised web developers to develop code around the W3C’s Cascading Style Sheets 2 specification, which simplifies site development by separating content and presentation, and makes sites more accessible to disabled people. “Those that stick to standards have much more reliable, stable and fast web sites,” Jones argued. “They should keep it simple, and [taking into consideration] accessibility issues also improves the performance of web sites.”