Rechercher (2007-2014)

lundi 3 décembre 2007

QR Code Reader pour Iphone

Il se concocte en ce moment un QR Code Reader en open source pour l'Iphone.

6 commentaires:

  1. iMatrix for iPhone
    Change your mind on data handling

    imatrix blog

  2. cela n'a rien à voir...
    c'est de l'indirect !

  3. Le mode direct n'est pas breveté. Le mode indirect est breveté par Neomedia aux États-Unis. Google n'est pas assez fou quand même. Plusieurs joueurs vont attendre voire le dénouement sur la poursuite de vol de brevet sur Scanbuy.

  4. effectivement, tout l'enjeu est de savoir si le mode indirect peut être breveté...

    Par rapport à iMatrix for Iphone, voici la réponse de Alexis, l'un des fondateurs de Semapedia :
    Hey JA,

    good find but while imatrix looks like what we are looking from the
    outside, it is NOT what we want - As

    Let me explain:
    imatrix is using QR Codes. Yes.
    imatrix is a general QR Code reader then? No.
    imatrix is standard compliant? No, the application behaves not as

    imatrix is encoding URLs, SMS, Phonenumbers directly into the code.
    imatrix is encoding id-strings (e.g. 1232229039292929191919119) into
    the codes which are ONLY useful when I have the actual imatrix reader.
    Yes. is the only place on the internet that can resolve
    "158303057237567360764349620" to an actual meaningful thing (such as a
    URL). Yes.
    If is down none of their codes can be resolved to the
    actual thing (URL, vcard, etc..)

    So what?
    This is (probably) a businessmodel where there is (yet another)
    proprietary code (check out and for another example) that ONLY works with the
    reader of one vendor.

    So, for example if I scan
    with my very capable Quickmark Reader, it will just display
    "158303057237567360764349620". I'll be like 'heh?' what am I gonna do
    with 158303057237567360764349620?

    Semapedia has seen many of such proprietary island-solutions that try
    to create a artificial namespace ONTOP of URIs. This creates
    dispersion in the market and confusion with the enduser.

    Reading the FAQ;

    Q:Why do you use code as index (ID) only?
    The most important reason for that is a fact that our solution must be
    compatible with plenty of different mobile phones on the market.
    Because of several limitations like weak Java spanshoot possibilities,
    low processing power of phone's CPU, lack of memory and poor quality
    of images for close objects, we have to use simple, easily detectable
    code. It means compact but well scaled.
    Also, most of content is on the web and, hence, there is no sense to
    keep all data in the code itself. Using code as ID only makes system
    more scalable and more dynamic.

    There is so much I could say about this, but from my point of view the
    last sentence is simply not correct: "Using code as ID only makes
    system more scalable and more dynamic.". Nope, sorry. It is not.
    Indeed a bottleneck is being created if there needs to be a central
    ( resolving component to the game. DNS has proved itself
    to be very scalable by being a distributed protocol and avoiding
    centralized bottlenecks.

    As a solution to imatrix I think it should support *both* their own ID-
    based codes as well as plain old - standard-compliant - QR Codes that
    encode the URL directly...

  5. Merci pour les commentaires d'Alexis. Malheureusement, je connais très bien le point de vue des 2 fondateurs de Semapedia. Il n'y a rien de nouveau là-dessus.

    Je ne serais pas surpris si HP réussissait à inviter Google à se joindre à la formation de MC2.

  6. Je ne pense pas que les 2 écosystèmes soient incompatibles, direct et indirect. Ce sont des usages et des des modèles (techniques et économiques) différents