Search
Subscribe

Bookmark and Share

About this Blog

As enterprise supply chains and consumer demand chains have beome globalized, they continue to inefficiently share information “one-up/one-down”. Profound "bullwhip effects" in the chains cause managers to scramble with inventory shortages and consumers attempting to understand product recalls, especially food safety recalls. Add to this the increasing usage of personal mobile devices by managers and consumers seeking real-time information about products, materials and ingredient sources. The popularity of mobile devices with consumers is inexorably tugging at enterprise IT departments to shifting to apps and services. But both consumer and enterprise data is a proprietary asset that must be selectively shared to be efficiently shared.

About Steve Holcombe

Unless otherwise noted, all content on this company blog site is authored by Steve Holcombe as President & CEO of Pardalis, Inc. More profile information: View Steve Holcombe's profile on LinkedIn

Follow @WholeChainCom™ at each of its online locations:

« Consortium seeks to holistically address food recalls | Main | Top 12 Discussions - Data Ownership in the Cloud »
Thursday
May202010

Internet Identity Workshop 10 - Favorite Tweets

I unfortunately wasn't able to attend IIW 10 but did some retweeting. Here they are in chronological order -

  • RT @marcedavis learned that #infocards support LOA2 and LOA3 ("Level Of Assurance") and #OpenID does not. #iiw @ http://twb.cc/s/712 2:09 PM May 17th via tweebus
  • RT @nobantu IIW 10 - is 3 days of Open Space in the Techie Community - specifically On Line Identity - been happening for 5 yrs now #openspace #iiw 2:19 PM May 17th via web
  • RT @xmlgrrl One refreshing thing about #IIW vs other conferences: the f'in salty language. 2:57 PM May 17th via Twitter for iPhone
  • RT @mjsoaps I don't know what's more important, Identity or Reputation #IIW 7:03 PM May 17th via web
  • RT @idworkshop Day 2 of #iiw is going to be AMAZING! Here is the twitter list of attendees http://twitter.com/idworkshop/iiw10 9:37 AM May 18th via web
  • RT @xmlgrrl Once again finding myself recommending Chris Palmer's EXCELLENT talk on fixing HTTPS. Trust On First Use (TOFU)! http://is.gd/ceSc8 #iiw 12:26 PM May 18th via Twitter for iPhone
  • RT @IdentityWoman INTRO to Internet Identity Workshop 10 now up online. http://slidesha.re/cGQ3AR #iiw please retweat 5:20 PM May 18th via web
  • RT @gffletch OH "Every distributed system begets a centralized system created to make the distributed system useful" (or something like that) #iiw 7:13 PM May 18th via Twitter for iPhone
  • RT @paulmadsen Put 20 non-techies in a room and its only matter of time before somebody says 'its not a technical problem'. You never hear reverse #iiw [May 19th] via Twee
  • RT @xmlgrrl Rights and obligations of membership are nontechnical but tech may enable them (e.g. can you "unsay" something in a thread?) #iiw [May 19th] via Twitter for iPhone
  • RT @xmlgrrl =JeffH suggests looking at "operational transformation" work to solve the tech problems here. http://is.gd/cgoN5 #iiw [May 10th] via Twitter for iPhone
  • RT @rolfvb Thankyou Kaliya, thankyou #iiw - just fantastic! These seeds will lead to wonderful fruit. /cc @IdentityWoman #identity #data #privacy [May 19th] via Twitter for iPhone

I highlighted, above, the introductory presentation by Kaliya Hamlin to the workshop. Well worth a look.

For my take on IIW9 held last November, take a look at Data Identity & Supply Chains in this blog.

And for even more comments and discussion about the IIW and the "identity movement", check out the Data Ownership in the Cloud networking group on LI.

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>