QR Codes in your documents

QR codes are one method to ease the information exchange between classical medias and mobile devices (common usage direct link to the corresponding web page in paper based catalogs, manuals, ....).

But how to create those QR codes without too much complexity?

Google Chart API provides:

• chart wizard to create QR codes and corresponding styling
• infographics API to create static images based on posted chart definition (URLs)

viola. You now have a easy to use backend for creation of QR codes using e.g XSL-T.

The following code is taken from "QR Codes in DTIA Output" which shows how to create QR codes for PDF output of the DITA-OT using XSL-FO:

<!-- Insert QR code -->
<xsl:template match="*[contains(@class,' topic/xref ')]
                      [contains(@outputclass, 'qrcode')]">
<fo:external-graphic>
<xsl:attribute name="src"><xsl:value-of select="concat('https://chart.
googleapis.com/chart?cht=qr&amp;chs=100x100&amp;chl=', .)"/>
</xsl:attribute>
</fo:external-graphic>
</xsl:template>

 see: http://ditanauts.org/2012/03/14/qr-codes-in-dita-ouput/

Sample (code: <img src="http://chart.apis.google.com/chart?chs=200x100&cht=qr&chl=http%3A%2F%2Ftrent-intovalue.blogspot.de%2F2006%2F05%2Ftrent-definition.html" width="200" height="100" alt="" />):

Google Wave: backbone for real information collaboration

beside Microsoft still working on getting search on existing information done (last try http://www.bing.com/) Google tries to re-invent the creation, usage and collaboration of information with upcoming "Google Wave".

having a deeper look into the already available information the most interesting part of the design is that the complete architecture is based on hosted information transformation based on a group of humans and automated participants. the overall architecture looks clean and the demo provided here: http://www.youtube.com/v/v_UyVmITiYQ&hl=en&fs=1&rel=0 looks promising.

such kind of infrastructure has the capability to be used in all kind information centric workflows especially those happens in the "cloud". creation and further development of engineering artifacts from customer requirements to user stories to design documents and testing artifacts up to the usage of the same information in technical docs created for them. such workflow always requires a information object centric architecture and in addition collaboration feature sets.

we have to see if Wave will succeed, means if developer comunity contribute and use the existing extension points if so, i'm looking forward to see what can be done with this promising infrastructure.....

in my point of view the future of information goes away from document paradigm and end up in the a more message oriented paradigm where a group of people work on structured / semi-structured information objects (messages / topics) and assemble them in a final stage in each business workflow to a document, web-page, calculation sheet, ..... this means a document is "just one output for one audience" and describe just one usage of the information at a certain time.

in those days search is still essential but just as one way to navigate through the specific information pool and only if the hits are relevant for further usage (try to search for "Microsoft" on www.bing.com and see if the provided hits are relevant enough for you.....)

see also:

http://www.infoq.com/news/2009/06/wave
http://mashable.com/2009/05/31/google-wave-features/