View this PageEdit this PageUploads to this PageHistory of this PageHomeRecent ChangesSearchHelp Guide

Meetings with Beth

Meeting notes with Beth, 05/07/01
  • WWW is convince can access from desktop

  • Why do we want to use the RWWW, why the web on the go? (scenario)

o Information I place can be either serendipitous (might need it in future) or explicit (needed next time we meet)

o Serendipitous information (spatial, no need to start interaction)

§ Is the serendipitous information the hook or the focus? (Do we want to use the information to get the users attention or do we want to use the information as the information itself.)

o Context (location + additional info)

§ Location can be used to store information (esp in case of might need in future info, world wide filing cabinet!)

o Placing information where it is needed

o Low cognitive processing (language translation)

  • What type of interaction (this can be split in how to display the information and how the user interacts with the information)

o 3 Different things to look at when considering states

§ What are the stages?

§ What activates the stages?

§ What UI mechanism is used to convey states

o Interaction and organization

§ Priority queue (currently the information is not sorted in any way, but in the future the information should be sorted according to some user preferences. Unclear if we should display information from at least each channel, or clump everything together and pick highest priorities. Should channels have priority multipliers in this case?)

§ Channels (currently channels are provided by a remote process, and can be toggled on and off from there, the information comes from there as well, future this should be user preferences)

§ Selecting info (glance) (currently a node can be in 4 different stages, not selected, object of focus (indicated by an growing red circle), selected (indicated by a yellow circle) and stored for later retrieval (indicated by a green circle))

§ Hierarchy’s of information (vs. flat) (currently we display all the information, should we only display high level information and allow the user to expand this by looking at a node (for instance looking at a node about a restaurant shows all reviews and a more detailed menu)

§ Remembering what we looked at (currently the only method for keeping a log is to push all pages you are interested in, can we use something like Rekimoto’s timemachine?)

§ When do we look at the information (see the list of possible machines)

§ Twinkling stars (currently we display the information as small twinkling stars to prevent the screen from cluttering up. Can the user select these stars? And see them?).

§ Conveying mode of interaction (select, display) (currently there are no distinct modes of interaction, the user is always in gaze mode that allows them to select a node)

§ Different levels of displaying information (stars, small icon, big icon in fixed location and page in bodyspace) and how to signal to the user that an information node is displayed elsewhere (currently done with the circles around them)

§ How to symbolize the link between the different icons and what is on screen (line from gaze cursor with title of information to the information node, no link from currently selected information node to the text in upper left corner)

§ Multiple nodes (information overload) do we really have moments where the filtering will still leave to much information, and is all this information related?)

§ Color coding of channels and stars (currently each channel has a color associated and the twinkling stars are painted with the same color)

§ Positioning non spatial data (currently this is displayed on fixed whiteboards in the room)

§ Non interference with physical objects (currently not done, in future we want to use geometry from space server to put up invisible walls and hide info that is not visible)

§ Getting users attention when things change (currently the channel that wants the users attention will flash)

  • Privacy issues

o Association of ‘private’ info with house/person (for instance when walking around listing phone numbers next to houses).

  • Different methods of accessing the RWWW

o Desktop

§ No connection of physical and virtual information

§ No serendipitous information

§ Not location aware

§ Allows for previewing of information

§ High resolution, well know interfaces

o Handheld

§ No serendipitous information

§ Hard to know where the user is looking

§ User initiated

§ High resolution, well know interfaces

o Non spatialized Head Worn Display

§ Often task specific

§ Fixed location for information

o AR

§ 24 x 7

§ Spatialized information

§ Information can be blocking users view

§ Lower resolution

Scenario’s
Imagine walking around in the city. You finally decided to buy a house. Wearing a HMD you walk around in the city and look at neighborhoods. You walk past houses and notice little popups. The popups list who is living in the house, if they are renting how much they pay, and how many people live in this house.

A little further down the road you see the house you are interested in. Again when you get closer to the house you will see information about the house. You see the report from the inspector and arrows pointing you to problem areas. When looking at the gas meter you see the last few months of utility bills (compared to average’s in the area).

Once you enter the house you can see the layout of the furniture as the last person who lived in the place had it.



During the last couple of years you received email from mailinglists and friends about places to visit in the world. Looking at the information you picked the things that interested you and placed them in the world, in close proximity to the location what they describe, or what it is relevant to.

Unexpectedly you get invited for a conference in Japan. Being intrigued by Japan you decided to accept the invitation and spend an extra week touring Japan. Once the conference is over the fun begins. Walking around Tokyo you notice a note you placed last year about a nice restaurant. Later in the week you walk to the train station to get a ticket on the bullit train. Standing at the ticket counter you notice a little piece of text describing phonetically how to say in Japanese that you want a return ticket.

Arriving at your final destination you get out of the train, and look around. You notice the signposts and a note next to it translating one signpost that points into the direction of the temple you are interested in visiting.



Papers
Spaceservers, system oriented paper, ISWC
UI details 3 stages
General principles