nlp


Related to this much older post about realtime translation, Kintrans is yet another dimension of this type of capability.

 

silver balls...

Image by play4smee via Flickr

The December episode of the Semantic-Link podcast was a review of the past year, and a look forward.  The framework for the discussion was:

  • What company, technology or issue caught your attention in 2011
  • Are we “there” yet?
  • What are people watching for 2012

Notable attention grabbers were: schema.org and its impact on who pays attention (i.e. SEO space); linked data (and open data); increase in policy maker awareness of the need to pay attention to interoperability issues; commercial integration of technology (ontologies plus nlp capabilities) to leverage unstructured content; and of course Siri (a key example of such integration…).

In terms of where we are in the progression of the semantic technology realm, the general sentiment was that Siri represents the beginning of inserting UI in the process of leveraging semantics, by making the back end effort invisible to the user.  And looking forward, the feeling seems to be that we’ll see even more improved UI, stronger abilities in analysis and use of unstructured content, greater integration and interoperability, and data-driven user navigation, and Siri clones.

Give a listen, and be sure to express your opinion about a) topics that should be covered in the future, and b) the ways you would like to interact or participate in the discussion (see dark survey boxes).

Enhanced by Zemanta
Marbles - Schulenburg, Texas

Image by adamj1555 via Flickr

While I’m still actually waiting to get “in”, I have a couple of comments regarding Google+, from outside the Circle.

From descriptions of this Google Social Networking effort (following Orkut, Wave and Buzz), key elements as of now are: Circles (think of them as groups of people within your network); Sparks (which are topics or areas of interest); Hangouts (video chat rooms); Huddles (group chat); and Instant Upload (automatic mobile photo syncing).

Considering potential for integrating capability across product areas has always been most intriguing to me.  In serving them up “together”, G+ makes it that much more likely for capabilities to be used together.

First, and I think most interesting, is the way that the concept of Circles melds the idea of a network of friends/connections with tagging/categorization so that, without having the clunky thinking of classifying or inviting people to groups, the user is able to achieve the elusive sense of having multiple personas representable within one system.   Some people maintain their professional network in one system (LinkedIn, for example), and their personal network in another (e.g. facebook).  Others maintain multiple accounts in a single system in order to segregate their “work” online presence from their “family” or “personal play” selves.  For those who already maintain multiple Google accounts, G+ lets you log into multiple accounts at once.  I have yet to see how well you can interact in ways that cross over account lines.
Image representing Twine as depicted in CrunchBase

Image via CrunchBase

The second area of note is the way that Sparks re-frames the idea of Alerts in a way that subtly shifts the nature of the material that results from them from being one-off emails or links — that you might dig into or forward on — to material that relate to particular areas of interest, which presumably parallel or align with groupings of people you associate with around those topics.  Twine had used the approach of integrating topic areas and social groupings for alerts – but these were groups that potential recipients would have to join.  In G+, the “proximity” to the Circles aspect, and the fact that those Circles are unique to the individual, and don’t require reciprocation, make for a compelling scenario for the “push” side of the equation. (At the same time, I see some potential issues in terms of “pull” and management by those on the receiving end).

Together, Sparks and Circles could take us a lot closer to a dream system I yearned for a few years back, that I referred to as a Virtual Dynamic Network.  In this, rather than having defined groups that you would need to join (which would send you related material along with much you would prefer to do without), material you both receive and send would be routed based on what it is about and how it is classified. I would love to see distinct sets of controls for in-bound vs out-bound content.
I won’t know until I get to try it, but ideally G+ will enable you to tie Sparks to Circles for you.  I’m also hoping you’re able to group your Circles – to relate and arrange them even hierarchically (consider: a large Circle for your work persona, which might contain multiple Circles for various client or team categories; or a large personal Circle, with sub-Circles for family, local friends, remote friends, classmates – all with overlap management to avoid multiply-sent content).

Hangouts and Huddles are by nature “social” already, for which you’ll presumably be able to seamlessly leverage Circles.  As with topical material, Instant Upload brings your photo content automatically one step closer to where you are sharing.  Success of all this as a social platform depends significantly on integration between the parts for seamless use by a user across capabilities – for example, adding someone who is participating on a video call or chat right into one or more of the Circles touched or represented by the other participants on that call or chat.

Ripples

Image by Bill Gracey via Flickr

Leveraging other capabilities such as linguistic processing of AdSense (and G+ may already have this in the works) it would not be a stretch for the content in your interactions to generate suggestions for Sparks which you could simply validate — places or people in photos, words in chats, terms that show up in content within Spark items.  From there, it wouldn’t be far to being able to interact with your life through what I might call a “SparkMap” — reflecting relationships between terms within your areas of interest.

 

UPDATE: I’m now in, as of Friday afternoon, July 8. So now I’ll be playing, with more ideas to come…

Additional links:

  • How to Get Started with Google+… (socialmediaexaminer.com)
  • A good ScobleEncounter listen (scobleizer on cinch.fm)
  • Quite a collection of tips growing on this public google doc
  • Enhanced by Zemanta

    Early in my career, when working as a data jockey with an economic consulting firm, I was on a team for a particular project where, I’ll always remember, we were referred to (in the New York Times) as “nitpicking zealots”.  While I knew it was meant as a criticism, I took the reference then (as now, for that matter), as a complement – emphasizing the attention-to-detail in our analysis.

    The American manual alphabet in photographsImage via Wikipedia

    For me, that focus has long been coupled with heavy emphasis on usefulness (ok, and logic) as a driving factor in doing or creating anything.  “Stick-in-mud” – maybe.  “Drive you nuts” – sure, the family says this sometimes…  But things just need to make sense.

    So it shouldn’t surprise me (or anyone else) that, in my recent Experience Design mini-masters  project, I had an overriding need for the product idea my team was to come up with, to be of real use and value.  The first task was to evaluate whether design principles had been followed in the creation of a particular product (the Roadmaster – a single-line scrolling text display for use on a car).  Then we were to apply these design principles to come up with a different product/application making use of the technology for the context.  We performed our review by considering the Roadmaster’s affordances (what the design suggested about its use); its mapping of controls to meaning or functionality;  whether it provided feedback during use; its conceptual model and obviousness of purpose; any forcing functions, limters or defaults.  Having developed a “sense” of the product, as it was, we were embarked on the design effort by adding interviews/surveys to gather research on potential market need/desire.

    Without getting into our conclusions about the Roadmaster product itself, of particular interest is where we ended up going with our design as a result of performing our own contextual inquiry.  Some great ideas emerged among the different teams, for which each team prototyped their design (using Axure), performed usability testing, and presented results.  Most of the teams designed mainly for social-media driven applications.  With our own goals including not just usability, but the usefulness factor mentioned above, we discovered potential in re-purposing the device – to be directed not to other drivers, but to the driver of the vehicle in which it is installed.  Specifically, to aid hearing impaired drivers – whether for receiving guidance from a driving instructor, instructions from a gps, or conversing with a passenger.

    The design, which at one point we dubbed the “iDrive” (for reasons that will reveal themselves), involves mounting of the scrolling text display out in front of and facing the driver, and integration of speach-to-text conversion, so that as words were spoken, the driver would see these words displayed out in front of them, without their having to turn to see the hands or lips of a person commnicating with them, nor would they have to look away from the road to read directions on a gps screen.  In its simplest form, the design calls for an iPhone (or similar) application to perform the voice-to-text conversion, transmitting the resulting text to the display for the driver.  An extension of this concept could incorporate detection and display of other sounds, such as a honk, and which direction it is coming from. Since the program, we’ve found that the required voice-to-text conversion capability, in a mobile app (e.g. for the iPhone) as we called for in the design, does exist, so with the combination of the technologies (display, conversion, mobile application, and gps capability), the serving the hearing-impaired-driver market in this way should be within reach.

    A side-note to this post: The faculty of the UXD program, Dr. Marilyn Tremaine, Ronnie Battista, and Dr. Alan Milewski, helped to revealed for me that the formal processes of experience design, and particularly contextual inquiry, parallel closely with what I’ve sought to achieve through the joining of the disciplines of Usability, Value Network Analysis (perspectival), and a dash of Semantic (extensible and interoperable) thinking.

    http://static.zemanta.com/readside/loader.js

    Reblog this post [with Zemanta]

    Next Page »