For seven years, our Silicon Designer product has expanded in use, across many countries, languages, and use cases. From B2B applications where franchises easily manage brand collateral, to some of the largest consumer-facing document personalization sites on the planet, our product has proven itself to be solid and reliable, yet also very extensible. It is integrated with numerous forms of shopping cart, DAM system, workflow system, and database, and it has diverse forms of User Interface:

no two Silicon Designers look the same!

Making it easy for our clients to customize their unique implementations has been our top priority. We have found that web standards, implemented correctly, make all the difference.

As more and more organizations implement web-to-print workflows that meet their ever-changing business demands, they often find that customization of their chosen solution is a must. Yet with HTML5 based solutions, this customization layer can be a significant challenge. This is due to the vastly different ways in which software vendors decide to combine the overlapping technologies.

SVG certainly crashed and burned before it rose like a phoenix from the ashes...

Sometime in 1998, a former co-worker who had gone to work at Adobe came by my office at Bertlesmann to inform me of a brand new technology that she knew would excite me: PGML, or "Precision Graphics Markup Language." This was the Adobe flavor of XML for Vector Graphics. As Jon Warnock put it at the time:

"The PGML proposal solves a growing need for a precise specification that enables members of the Web community to readily and reliably post, control and interact with graphics on the Web."

I fell for it, hook, line and sinker, and ever since that time, I have followed the standards for XML-based vector graphics closely. PGML (mainly from Adobe) and VML (mainly from Microsoft), as well as a few other similar efforts (Web Schematics, Hyper Graphics Markup Language, WebCGM, and DrawML) soon merged into a "real" W3C standard, called Scalable Vector Graphics (SVG). This promised to serve as a format for rendering interactive vector graphics in Web browsers, which at that time (the era of Netscape Navigator 4.7 and Internet Explorer 5) was only possible with Macromedia Flash.

Completely obvious in the year 2000

What made SVG so cool? It could almost be considered "PostScript for the Web," so it certainly made sense for Adobe to sponsor and support it in its infancy: with SVG (as with PostScript), art was primarily described via vectors, a method far more efficient (and more naturally "scalable") than using raster images.

I was writing a press release recently, and I was just about to write a heading that has been something of a mantra the past 20 years: "Standards are the Future". But I paused, realizing the product I was describing is completely standards-based, thanks to recent technology advances. I corrected the title, and I think now is the right time to declare victory for web standards over proprietary technologies and walled gardens.

As of 2015, web standards-based approaches at last make complete sense for the majority of software use cases, at least those that our company works with on a daily basis. Sure, there are places where walled gardens and native software have a valid reason to exist, but those have become the exception rather than the rule.

1