Weblog

Tuesday, 20 January 2009

  • Dataportability: a Comment I Made…

     Dataportability: a Comment I Made...

    Some of you have allready noticed two distinct barcodes on my weblog. One conventional barcode and a strange looking 2d barcode (picture on the left!). What’s that all about? Let me tell you a little more.

    Barcodes are ways to create computer-readable information. The well known barcodes you find on your products in the supermarket and on books simply represent a series of numbers. In the supermarket product you can tell the country of origin and the manufacturer and product code from the barcodes. This is all governed by international standards. This means that (in theory at least) all different products have different barcodes and are therefor identifiable.

    In books barcodes are used to create a computer-readable version of the ISBN or International Standardized Book Number. Every title has it’s own barcode and therefor is identifiable. This is practical for libraries, but also for you. If you are a member of librarything.com for instance, you could simply use a cheap barcode-scanner to enter the ISBN-codes of your books and thereby add your books to your collection-records in this social network. It’s practical for those with limited numerical data-entry skills and tech geeks alike. (and just plain fun).

    A weblog could be considered a magazine or a book. However the standardization committees behind the ISBN numbering did not think it was a good idea to give out ISBN’s to blogs. That’s why ibsn.org/ started their own version of a ISBN-like numbering scheme for blogs, IBSN, the Internet Blog Serial Number. Naturally we need a computer-readable form for such a number, hence the IBSN barcodes. Mine can be found in the sidebar over there: –>

    Barcodes are a bit limited. Limited to numerical information, and limited in size. If you want more information or alphanumeric information, you need something else. Enter the 2d barcode. With 2d barcodes you can create a computer-readable code that contains for instance an URL or an actual address. You could create codes containing all contact-information or any text of choice.

    One interesting part of this concept is that you could actually attach a 2d barcode to a real-life object and therefor create a link to a website about the object in the real world. There are many applications allready in existance that you can use on your mobile phone to photograph a 2d barcode and than visit the URL it contains. This type of 2d barcode is called a QR-code and actually connects the real life to the virtual one.

    Another use could be to put your 2d barcode pointing to your website or weblog on your business cards or to put your 2d barcode pointing to a special sale website on the label of products. These are very attractive uses for such codes.

    The use of these barcodes is still limited but it could be the next big thing in advertising and the way to connect the outside world with the online one we spend lots of time in these days.

    I hope you like that post, feel free to comment

    4c685b3de1f98bc3665afa55cc11559d Dataportability: a Comment I Made...

    Reblog this post [with Zemanta]

    Related posts…

    4c685b3de1f98bc3665afa55cc11559d Dataportability: a Comment I Made...


    Share/Save/Bookmark

    Leave / read comments

Friday, 09 January 2009

Friday, 02 January 2009

Wednesday, 24 December 2008

Tuesday, 23 December 2008

  • Information Overload, The Solution?

    Binnenhof 3 Standardization for interoperability is a good thing. Standards make interoperability possible, make governance easier and cost lower. But how should you go about choosing your favorite standards? In this post I want to tell you the way the Dutch Goverenment chooses and I’ll tell you why I don’t agree. (and note that this is my personal opinion!)

    Standards in this sense are choices. Choices to use certain methods and technologies, and also the choice not to use certain others. It’s a way to limit the variation therefor making it easier to exchange date or interact between organisations and between applications. There is however a problem with limiting the possibilities. What happens when certain organisations or applications can’t support your standards of choice? Do you force them to change or do you make an exception? How do you accomodate the diversity that you are confronted with?

    When you look at a government, made up of many organisations, and many times more applications, you will easily see that there will be exceptions, there will be diversity. The question is whether allowing diversity, and accomodating for it is a bad thing. I don’t think so. I think that diversity isn’t necessarily bad. However, you will need to be able to deal with it. That’s where ‘Decoupling’ or Loose Coupling comes into play. An intermediate system that ’speaks multiple languages’ will help you translate between different technologies and methods. These systems exist and are called Enterprise Application Integration or Enterprise Service Bus. Using one of those allows you to accept multiple standards and still create integration and interaction between organisations and applications.

    The Dutch government has chosen a very specific standard for interoperability: EBMS with SOAP (and WUS if you want an exception). These are pretty nice protocols, but not necessarily the right choice for all sorts of traffic. If you want to exchange large badges of data, you’ld rather choose something less complicated. If you want to have really high performance exchanging lots of small messages, the overhead of these protocols may be unacceptable. How about dealing with applications and systems that do not support these protocols? Should all organisations build (or buy) their own gateway to create EBMS over SOAP from their favorite protocols? I doubt that would be an efficient and effective solution.

    The Dutch Goverenment has also chosen to not implement a single central integration platform but to allow the different sectors to create one of those for their own needs. This makes ‘inter-sector-interoperability’ rather difficult. Also, each of these implementations is a rather difficult and expensive project while intra-governement-interoperability still isn’t garanteed. The need for an overarching ESB or EAI to interconnect the sector-based-systems would be the solution, however it isn’t planned.

    I believe that the selection of standardization should not be a positive selection for one or a few protocols, it should be a negative selection instead following the next set of rules:

    1. Disallow anything really bad (unsecure, unscalable, unstabile etc)

    2. Disallow anything proprietary or otherwise non-open

    3. Allow everything else, but prioritize by preference

    4. Make sure there’s an incentive to choose the preferred standards

    5. Accomodate the other allowed standards with a well governed, scalable, secure (etc) interoperability platform.

    I hope to here your thoughts on this and I hope you liked this post.

    4c685b3de1f98bc3665afa55cc11559d Information Overload, The Solution?


    Reblog this post [with Zemanta]

    Related posts…

    4c685b3de1f98bc3665afa55cc11559d Information Overload, The Solution?


    Share/Save/Bookmark

    Leave / read comments

Top Tags

[no tags]

wkossen

  • Visit wkossen's Xanga Site
    • Name: Willem
    • Member Since: 1/31/2007

Archives

Don't worry - your calendar is here… to see it in action just click "Save" above and refresh the page.

About Me

  • IT Consultant who plays in a Bluesband OR Blues mucisian with a job as IT Consultant. Looking for projects and looking for gigs.

Groups

[no groups]

Pulse

Photostrip

[no photos]

Recommended

[no recommendations]