INCITS/V2
Technical Committee
Information Technology Access Interfaces
March 3, 2003
Reply to: Joe Roeder, V2
Secretary
Email: jroeder@nib.org
DOC: V2/02-0040
MINUTES of INCITS V2 PLENARY MEETING #10
Meeting Location: This meeting was hosted by Madentec, Inc. at the Radisson Hotel Orlando, Orlando, FL in conjunction with the ATIA Conference 2003 at the same venue.
Meeting Dates:
1. Call to Order.
Bill LaPlant, V2 Chair, called the meeting to order and welcomed the members and guests.
2. Introduction of attendees.
Ref:
V2 members
Liaisons
Observers and guests
3. Approval of the Agenda.
Ref:
LaPlant proposed revising the agenda schedule to do most of the presentations on the first day (Sunday) with a short work session at the end of the day. Presentations will continue on Monday, then the plenary will reconvene on Wednesday and Thursday as a committee of the whole at NIST in Gaithersburg for the DC/V2 Metadata roadmap workshop. The administrivia will be taken up at the end of the plenary on Thursday. The proposed agenda and modified schedule was accepted by unanimous consent.
4. Approval of the Minutes for plenary meeting #9
Ref:
The Minutes for plenary meeting #9 were not complete and will be presented at plenary meeting #11.
5. Review of action items
Ref:
No activity on this item.
6. Administrative Reports.
6.1 Chair Remarks.
6.1.1 Vice Chair.
Ref:
Haritos-Shea addressed the plenary and spoke about her role as Vice Chair of V2. She also gave a brief overview of the standards process and documentation.
View slides - Vice chair report for P10
6.2 Roll Call of Members in Jeopardy Due to Failure to Attend Meetings.
No activity on this item.
6.3 Draft Annual Report to INCITS.
Ref:
No activity on this item.
6.4 New member recruiting.
No activity on this item.
6.5 INCITS Training.
No activity on this item.
7. Review of Related Activities.
7.1 ISO/IEC JTC1 SC 35, User interfaces Sub Committee.
Ref:
LaPlant said SC 35, "user interfaces" is a subcommittee of JTC1 and V2 asked to be appointed the U.S. technical advisory group (TAG) to SC 35. When LaPlant has the authority from ANSI to correspond with the chair of SC 35 he will notify V2.
ACTION ITEM: (LaPlant) contact ANSI to get authority to correspond with the chair of ISO IEC SC 35. [P10/7.1]
The TAG has an International Representative (IR) who is an officer appointed by INCITS. Zimmermann has volunteered for this position and Trace has agreed to provide his support. LaPlant asked for the consent of V2 to forward Zimmermann's offer of volunteering for the IR position to INCITS.
MOTION: (chair) V2 gives consent for the chair of V2 to recommend to INCITS the appointment of Dr. Gottfried Zimmermann to the position of international representative for the U.S. TAG to JTC1 SC 35 and to forward his volunteer statement.
The motion passed by unanimous consent.
ACTION ITEM: (LaPlant) correspond with INCITS Secretariat recommending that Dr. Zimmermann be appointed IR for the U.S. TAG to JTC1 SC 35. [P10/7.1]
Sajka said Dr. Zimmermann is the perfect candidate to be the IR.
7.2 Web Accessibility Initiative.
Ref:
No activity on this item.
7.3 IEEE P1621 Standard for User Interface Elements in Power Control of Electronic Devices Employed in Office/Consumer Environments.
Ref:
No activity on this item.
7.4 Accessibility Forum.
Ref:
No activity on this item.
7.5 Access Board Proposed Electronic and Information Technology Accessibility Standards.
Ref:
No activity on this item.
7.6 Universal Plug and Play Forum.
Ref:
No activity on this item.
7.7 Other.
7.7.1 Metadata.
See item 8.2.7 V2M - Metadata.
7.7.1.1 Dublin Core.
See the DC/V2
Metadata Roadmap Workshop - 22/23-Jan-2003 at
http://www.dc-anz.org/access-roadmap/
7.7.1.2 INCITS L8 Metadata.
No activity on this item.
7.7.1.3 DAML-S.
No activity on this item.
7.7.2 XForms.
No activity on this item.
7.7.3 Pervasive Computing.
No activity on this item.
7.7.4 INCITS M1 Bio Metrics.
No activity on this item.
7.7.5 OASIS User Interface Markup Language.
No activity on this item.
8. Presentations.
8.1 Technical presentations.
8.1.1 Presentation on Pervasive Computing.
No activity on this item.
8.2 Ad hoc task group reports.
8.2.1 V2A - AIAP-URC Editing.
Ref:
Trewin introduced the V2A report, which was in 2 parts. The first part included a walk through of 2 example scenarios to give a feel for how things are shaping up. The second part presented a modified work plan for discussion and adoption.
Zimmermann walked through the TV example scenario.
Price walked through the elevator example scenario
Trewin reviewed the elevator example in more detail.
View slides for Elevator Details
Following are some highlights from the discussions that took place after the V2A presentations.
Price noted that a location technology was considered as an enhancement but needs more study. LaPlant said in the V2A archives, he has a posting that gives links for companies that have internal building location technologies. Price said location tracking raises privacy issues.
Regarding elevator wait time, Seagriff said building administrators might not want to give that kind of control to users. Trewin said when a door wait time feature is not available, then the interface would likely have a 'hold door' button that the user would need to press repeatedly as they enter the elevator.
Gilman said if user has a tier 4 smart card in their URC, they could register their ID with the hotel and use the URC as a passkey to their room or to restricted floors. This might still need a location system, as the hotel might not want guests to open a room when they are elsewhere. Gilman said we have to think in terms of the URC as an alternative to a security token device. There was more discussion and Trewin said we will come back to this topic at a future time.
Haritos-Shea asked if the target could cache the session for future use. Trewin said that it is likely the URC will remember the interactions and fill in values for particular targets. LaPlant talked about smart cache and said with the way technology is going cache could be very large.
There was discussion about the translation service and Trewin said the example is meant to show there are different ways to reach the same result. If target does not have much resources, The URC can still get translations elsewhere. Gilman said this points to data engineering and the interface to a supplemental resource as a work item. He said we have data engineering issues with not just metadata but all the data that is touched. What are the feasible and reasonable ways these can be brought up and linked together?
Haritos-Shea said we could also look at loading translation programs or dictionaries onto the URC. Zimmermann said this is a feature we can leave open for URC manufacturers to distinguish their products. Gilman said the URC might eventually have a lot of capacity. On the other hand, the protocol needs to be in modular blocks so smart cards and the like [devices with limited capacity] are capable of executing the piece of the protocol they need.
Zimmermann said working with scenarios is very helpful. He invited anyone to submit additional scenarios they want worked on. There was discussion of a scenario for a surgeon in a smart operating room and the notion of URC services being imbedded in a smart room or smart house. LaPlant said with the current architecture, it doesn't matter where the intelligence [of the URC] is located. LaPlant said an ATM scenario will bring out the critical security and privacy issues which we need to address.
Zimmermann led a discussion on terminology. The group agreed to use the collective term "socket elements" to refer to the different data objects exchanged between the target and the URC. At one point in the discussion, the types of socket elements were said to include variables and streams; streams were said to include continuous streams and events; events were said to include commands and notices. Attention was brought to a posting by Farance, which said these terms are defined in ISO/IEC 2382 Information Technology Vocabulary and refined in other ISO/IEC standards as:
- data elements (whether variable-, array-, file-, stream-, etc. based)
- services (e.g., commands, (live) objects, etc.).
The group decided to refer the rest of the terminology discussion to V2A and V2G.
Trewin presented the V2A work plan, which was then discussed by the plenary.
Following are some highlights from the discussion.
Haritos-Shea suggested consideration of GPS in phase 2. LaPlant added that this should include internal location technologies.
Haritos-Shea suggested future considerations include other modalities, such as vibration, smell and taste.
Vanderheiden voiced concern about introducing rich media into help text. He said help text should also follow the criteria for presentation independence. Gilman said the rich media problem for help is not a separate work item. We are trying to create a core, which is sufficient and independent of rich media, and trying to work out the association between rich media and that core. The solutions to those problems will apply to help text.
MOTION: (V2A) that V2 work toward producing a first public draft for comment that includes the items outlined in phase 1 of the work plan.
The motion passed by unanimous consent.
8.2.2 V2B - Framework.
No activity on this item.
8.2.3 V2C - Managers.
ACTION ITEM: (Roeder) update the V2 managers action items list.
8.2.4 V2D - Discovery.
No activity on this item.
8.2.5 V2E - Editing.
No activity on this item.
8.2.6 V2G - Glossary/scenarios.
No activity on this item.
8.2.7 V2M - Metadata.
Ref:
Sheppard reported on the accomplishments of V2M
Roucoux reported on the NIST prototype project.
view slides - plenary10PartOfV2mReport
view slides - Smart Space scenario
8.2.8 V2.1 - Security.
Ref:
Lawson gave a presentation on security issues.
VIEW SLIDES 10th Plenary V2 Orlando.htm
9. Discussion of tasks and priorities.
9.1 Working Sessions.
See agenda item 8.2.2 for work with V2A.
For minutes of DC/V2
metadata roadmap workshop, see
http://www.dc-anz.org/access-roadmap/.
10. Pending Items.
10.1 Planning for Implementors' Workshop.
No activity on this item.
10.2 V2 Server.
LaPlant said Sajka is our official web master and we are in the process of getting an independent web presence at www.V2Access.org.
Sajka said the site will have public and private areas and asked if V2 wants password for the entire site or for each area. LaPlant said have passwords for the entire group except for voting. Sajka will create one password for the entire group with the option to change periodically.
Sajka said the site would also have Wiki. LaPlant said when V2Access is working, we will shut down the INCITS site for V2.
11. New Items.
MOTION: (Trewin, Haritos-Shea) to recreate ad hoc V2A to do the work of phase 1 of the work plan.
The motion passed by unanimous consent.
MOTION: (Gilman, Sajka) to create V2.1, the Security subcommittee of V2 charged with the security aspect of the work of V2.
The motion passed by unanimous consent.
LaPlant appointed Lawson chairman of V2.1 and asked for approval from the plenary.
MOTION: (LaPlant, Haritos-Shea) that the plenary report the appointment of Bill Lawson, alternate for AT&T, as chairman of V2.1 Security subcommittee for V2.
The motion passed by unanimous consent.
ACTION ITEM: (LaPlant Haritos-Shea Roeder) notify INCITS of the creation of V2.1 and of the appointment of its chairman. {P10/11}
MOTION: (Price, Haritos-Shea) to establish the following ad hoc groups with the chairs and assigned tasks as indicated:
The motion passed by unanimous consent.
12. Future Meeting.
12.1 March, 2003, CSUN, Los Angeles, CA.
LaPlant said we might need a sponsor because CSUN turned the room back to the hotel.
ACTION ITEM: (Zimmermann) ask Vanderheiden to contact Bud Reiser about CSUN support for V2. {P10/12.1}
12.2 June, 2003, RESNA, Atlanta, GA.
Plenary #12 will be held June 17-18, 2003 at Georgia Tech in Atlanta, Georgia.
12.3 October, 2003, Trace, Madison, WI.
Plenary #13 has open dates in October, 2003, and will be at Trace in Madison, Wisconsin.
13. Summary of Action Items.
Ref:
VIEW Summary Table Form of V2 ACTION ITEMS LIST for P10
View Summary Text Form of V2 ACTION ITEMS LIST for P10
14. Adjournment.
The plenary recessed to reconvene on Wednesday as a committee of the whole for the DC/V2 metadata roadmap workshop at NIST in Gaithersburg, MD.
Plenary meeting #10 of V2 adjourned on January 23, 2003, at 5:02 PM (ET).
ATTACHMENTS: