V2/A Minutes - 10/12/2000 & 10/13/2000

Task Group A: Interface Element Substitution and Remote Console

Thursday, 10/12/2000

1) Overview URCC (Universal Remote Console Communication), Gregg

URCC means that the whole interface is replaced by a remote device. The protocol is text-based (Unicode).

Accessor initiates:

• Reset Who is out there?
• List (send list of available commands at this point in time)
• Act: do #5 from the list (if action), send text for #5 (if it is a block/field)

The list is unicode (text) so it can be presented either visually or auditorially or tactilely.

If there is a keyboard or other buttons on the device, they all would show up in your list. Since this protocol is basically all "Pick From List" (PFL) the interface must be represented (or an equivalent interface created which is) PFL in nature. If you can't then you have a problem.

Target device, data types sent back to accessor:

• Error
• One moment (when busy processing a command it received)
• List changed (when the available choices or displayed information changes)
• Block of text (when a block of text is requested)
• Table (when a list is requested it is provided in table form)

URCC Level concept:

• Level 1: (verbal only interface). Minimum requirement for a target device to provide.
• Level 2: additional columns in the table (list) with geometric shapes and locations of interface components. Enables simple graphical layout for interface components.
• Level 3: download code (dynamic interface).

Multilingual: each device could have these commands in different languages.

2) Discussion

• Agreement: we should have a minimal level that is extensible.
• We should also address device discovery.
• Problem with complex screens (web pages), how to deal with many items? Idea: group items hierarchically and indicate hierarchical grouping with an additional column in the table containing numbers for different levels (e.g. 1.1.3.4.5). Also provide information about group labels.
• MS Word is a good example of a complex interface. A dumb accessor could access and operate word but it would present a very long linear list of commands and would be tedious. A smart accessor could group items and provide access in a much more efficient manner.
• We should have an own discussion list. Also a list of open issues. Also a web site.
• Kelsey appointed as "security person".

Open issues:

• discovery & security
• complex interfaces
• internationalization
• real-time, time-dependent information
• motor problem
• parallel interfaces
• path-dependent commands (state-dependent commands)
• path independent command sets
• upgradeability
• security
• fault-tolerance
• denial-of-service

Friday, 10/13/00

3) Administrative

• Gregg does not want to take the chair, because he wants to be free for discussing the URCC ideas and chair needs to be less involved in discussions.
• Gottfried appointed as chair. Gregg and Kelsey will be (not exclusively) our spokespersons.
• Sharon: NIST has an office of standards. They can get all standards. Sharon appointed as "research person".
• Nasser, Shari, Gregg: appointed as "editors".
• Information infrastructure: Mailing list for information exchange, NetMeeting for teleconferencing, plus an additional repository for maintaining structured information.
• We may need research about existing patents. This is a marketing issue, so we will delegate this to the Strategy group.
• Shari will coordinate the scope & requirements doc.

4) Discussion: Wayne's 4-box model

Without a thorough understanding of the model semantics, we struggled with its terminology.

• "User Interface" instead of "User Experience"
• "Offered Service / Outcome (product function)" instead of "Requested Service".

We need a better understanding of this model. Wayne will send us a tutorial for that purpose.

5) To Do's

• Gregg: send the URCC model out to all members, with description of layers.
• Gottfried: Maintain member list of task group A: we and everybody (not necessarily within V2) who wants to be a member of this working group.
• Kelsey: looks at possibility of web-based document tracking for tele conferences.
• Kelsey, Nasser, Gottfried: Repository - possibilities?
• Sharon: Taxonomy of devices.
• Gottfried: Distribute a patent of Neal Scott
• Gottfried: Request for Bill LaPlant. We would like further discussion about IPR in the next V2 plenary session. Is there any NCITS written policy? Copy?
• Shari: coordinate scope & requirements document
• Nasser: provide telephone number for teleconf on Friday, 10/27.

6) Next appointments

Teleconf on Friday, Oct. 27th, 1-3pm ET.

Gottfried Zimmermann, 10/27/2000