Notes from "The Everybody Fluid Engage Brainstorming Meeting"

Jess Mitchell jess at jessmitchell.com
Tue May 19 20:33:34 UTC 2009


Clayton's notes from our CATT museum brainstorming session read like a  
thorough use case -- have a look.

Best,
Jess
~~~~~~~~~~~~~~~~~~~~~~
Jess Mitchell
Boston, MA, USA
Project Manager / Fluid Project
jess at jessmitchell.com
/ w / 617.326.7753  / c / 919.599.5378
jabber: jessmitchell at gmail.com
http://www.fluidproject.org
~~~~~~~~~~~~~~~~~~~~~~




Begin forwarded message:

> From: Clayton H Lewis <Clayton.Lewis at Colorado.EDU>
> Date: May 7, 2009 12:53:57 AM EDT
>
> Pat loves cats and is a regular visitor to the CATT museum. Pat  
> can't read very well, but fortunately the CATT museum uses Fluid  
> Engage technology. Pat has a profile online with an identity  
> provider that supplies an information presentation preference  
> profile that indicates that she prefers simplified language... this  
> profile is not specific to Fluid Engage, but can be used by any  
> compliant site that Pat visits on the Web.
>
> Pat is given an RFID badge on entry to the museum. Because Pat is a  
> member of the museum, her RFID badge number is also entered into her  
> online account at the museum. Also at that time Pat  selects the  
> Fluid Engage visitor app on her iPhone, and the app accesses the  
> Fluid Engage visit registration site. (If Pat does not have an  
> active session, the phone also establishes a session with the  
> identity provider, so that sites Pat visits can obtain her  
> information presentation preference profile.) The phone provides  
> crude location information to Fluid Engage (it's indoors, but the  
> phone can get a rough fix via wifi address), good enough to tell the  
> site that Pat is at the CATT museum (the Fluid Engage site knows the  
> location of the museum). Fluid Engage queries the CATT museum to get  
> the number of the last issued badge, which is Pat's, and sends this  
> badge number to Pat's phone.
>
> Now Pat's phone knows Pat's RFID badge number, and can query the  
> Fluid Engage site for location specific information for the badge,  
> which is tracked by the location system in the museum.
>
> When Pat approaches an exhibit that has audio commentary, the phone  
> plays appropriate content, delivered in simple language, honoring  
> Pat's information presentation preference profile. Pat does not have  
> to operate any controls or find any control numbers to get the  
> commentary for the exhibit, and she doesn't have to do anything to  
> select commentary that is composed in a style that she can understand.
>
> Pat particularly enjoys the exhibit on Lord Nelson's catts. The  
> exhibit includes a mannequin representing Lord Nelson, with six  
> catts on various parts of his person. As Pat approaches that exhibit  
> she sees a "take photo" button, and her phone plays a message  
> inviting her to stand in next to Lord Nelson and press that button.  
> When she does so a picture of her, with Lord Nelson and the catts,  
> appears on her phone, and is saved when she moves away from the  
> exhibit.
>
> When Pat returns home after her visit, and accesses the museum Web  
> site, she is recognized as a member (because of id and password  
> information stored on her home computer). Information about her  
> visit, including the picture she took of herself with Lord Nelson  
> and the catts, is available to her on the museum site. She can  
> replay commentary about any of the exhibits, or hear commentary on  
> exhibits she did not visit, by selecting a picture of the exhibit on  
> a map of the museum on the site. Because the site accesses Pat's  
> online identity, and  hence Pat's information presentation  
> preferences, the version of the commentary and other information  
> that Pat hears is appropriate to her.
>
> Clayton Lewis
> Professor of Computer Science
> Scientist in Residence, Coleman Institute for Cognitive Disabilities
> University of Colorado
> http://www.cs.colorado.edu/~clayton
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20090519/63ec59ea/attachment.html>


More information about the fluid-work mailing list