@aaronesilvers @aelmhorst Glad to see another Hodag in the Tech World! We do more than just text quickly!
QWrap: A good conversation with a lot of smart people involving #xAPI Thank you all for making it possible!
Q7: # "Experience Tracking" is the missing component - currently that is #xAPI
Q6. #xAPI itself doesn't provide a privacy concern, but the consequences of tracking more data is increased privacy concerns
Q5: Agree, especially if whomever is determining ROI can compare desired behavior with actual behavior using #xapi
Q4: Because #xAPI generates so much data, we need to look at new solutions to aggregate them. I think it starts with community-driven verbs
@aaronesilvers In technical ways, I agree, but in the cases of data transfer, we have a much clearer picture with natural language w/ #xapi
Q3: By using natural language rather than static data fields, the intent of #xAPI data can be more easily determined by humans
Q2. I think one of the biggest problems #xAPI solves is the ability to look at learning outside the confines of a "course".
Q1. True! we're still looking for things #xAPI cannot track :)
Q0: Andy Johnson, ADL, interested in designing fun learning experiences with #xAPI
RT @MayraAixaVillar: We are about to start! Be part of the 1st social learning experience on Twitter that is all about #xAPI 12 pm EST http…
Q7) I'm not going to play favorites with #xAPI supporters, but you can see a list of who contributed to the spec: github.com/adlnet/xAPI-Spec/…
Q6) #xAPI statements are permanent. They aren't re-created over time, they can only be aggregated differently to produce new meaning.
Q5) #xAPI #WordJumble BREVity, describing how statements should be granular in nature (hey had to be different)
Q3) What CAN'T #xAPI b used 4? 2 Me The most interesting thing would be spotting trends in personal and group behaviors, novices and experts
Q2) If anyone wants a historical view of #xAPI: tincanapi.wikispaces.com/
