InterNational Committee for Information Technology Standards
INCITS Secretariat, Information Technology Industry Council (ITI)
1250 Eye St. NW, Suite 200, Washington, DC 20005
Telephone 202-737-8888; Fax 202-638-4922;
Email: incits@itic.org


DOC: V2/03-0039
Date: October 21, 2002

Project: Administrative
Ref Doc: V2/02-0052, V2/02-0053
Reply to: Joe Roeder, V2 Secretary
Email: jroeder@nib.org

Subject: MINUTES of INCITS V2 PLENARY MEETING #9

Meeting Location:
This meeting was hosted by NIST at the NIST campus in Gaithersburg MD.

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/01-SD-01 - List of Members and Contact Information

V2 members

Janina Sajka, AFB, p
Mike Burks, AT&T, p
Charles Sheppard, Dept of Commerce, P
Bill LaPlant, Dept of Commerce, A/ Chair, INCITS-V2
Alfred Gilman, Free Desktop Accessibility Working Group (FDAWG), A
Shari Trewin, IBM, P
Cynthia Waddell, ICDRI, A
Katie Haritos-Shea, Katie Haritos-Shea consultant, p/ Vice chair, incits-V2
Joe Roeder, NIB, P/ Secretary, INCITS-V2
John A. Chapman, SHARE INC, P
Gregg Vanderheiden, Trace Research & Development Center, P
Gottfried Zimmermann, Trace Research & Development Center, A

Observers and guests

Brad Myers, Carnegie-Mellon/ Pebbles project
Frank Farance, Farance, Inc./ Chair, ISO-IEC JTC1 SC36
Judith Newton, NIST/ Chair, INCITS-L8
Fernando Podio, NIST/ Chair, INCITS M1
Vince Stanford, NIST Smart Space Laboratory
Tom Karygiannis, NIST Computer Security Department
Perrine Roucoux, NIST
Malcolm Raymond, Performance Technologies Group/ IT-Test Consortium
Liddy Nevile , university of melbourne/ chair, dublin core accessibility special interest group
Andrew Arch, Vision Australia Foundation
ed price, wireless rerc

A quorum of voting members attended on all days.

 

3. Approval of the Agenda.

Ref:

V2/02-0052 - Draft Agenda for meeting #9 of V2, 9/30-10/4/2002

LaPlant asked that the agenda for plenary #8 be accepted.

The agenda was accepted by unanimous consent.

(See attachment - FINAL AGENDA FOR V2 PLENARY MEETING #9 at the end of these minutes)

 

4. Approval of the Minutes for plenary meeting #7.

Ref:

V2/02-0051 - Draft Minutes for plenary meeting #8 of V2, 6/27-28/2002)

LaPlant asked that the minutes be accepted as presented.

Motion: (Sheppard, Trewin) that the minutes as presented be approved.

The motion passed by unanimous consent.

 

5. Review of action items.

Ref:

v2/sd-03 - V2 ACTION ITEMS LIST /Summary of action item from plenary #8

This item was not taken up during the plenary.

ACTION ITEM: (LaPlant V2C) update the status of the action items. {P9/5}

 

6. Administrative Reports

6.1 Chair Remarks.

6.1.1 Vice Chair.

LaPlant introduced Katie Haritos-Shea as the new Vice chair of INCITS-V2.

 

6.2 Roll Call of Members in Jeopardy Due to Failure to Attend Meetings.

This item was not taken up during the plenary.

 

6.3 Draft Annual Report to INCITS .

LaPlant distributed the annual report to V2C for comments.  He will need authoorization from the managers group to put the report together and to submit it to INCITS. The report is due at the INCITS board meeting in November to which technical committee officers will be invited.

 

6.4 New member recruiting.

This item was not taken up during the plenary.

 

6.5 INCITS Training.

This item was not taken up during the plenary.

 

7. Review of Related Activities

7.1 ISO/IEC JTC1 SC 35 User interfaces Sub Committee

Ref:

http://comelec.afnor.fr/servlet/ServletForum?form_name=cForumPage&file_name=Z62A%2Findex.htm&login=invite&password=invite - ISO/IEC JTC 1/SC 35

LaPlant discussed the history of SC 35 and the proposal that V2 should become the U.s. technical advisory group (TAG) to SC 35.

ACTION ITEM: (LaPlant) contact INCITS staff about the status of action regarding SC 35 and talk with IEEE/sc7 about software engineering. {P9/7.1}

 

7.2 Web Accessibility Initiative

Ref:

http://www.w3.org/WAI/ - Web Accessibility Initiative Home Page

Haritos-Shea gave a report on W3C activities that have relevant overlap with V2. These include:

 

During some discussion about digital signatures, Burks noted there are major difficulties and provided a reference to a paper by Cynthia Wadell at http://www.icdri.org/CynthiaW/questions_about_electronic_signa.htm

Haritos-Shea noted there needs to be a convergence of several standards and technologies and success depends on coordination with other groups.

 

7.3 IEEE Activities

7.3.1 IEEE P2001 Web Engineering Best Practices Guidelines

Ref:

http://computer.org/standards/Internet/index.htm - Internet Practices Standards Working Group

No report.

 

7.3.2 IEEE P802.1x Wireless networking

Ref:

http://www.ieee802.org/dots.html - IEEE 802 Working Group & Executive Committee Study Group Home Pages

No report.

 

7.4 Accessibility Forum

Ref:

http://accessibilityforum.org/ - Accessibility Forum Home Page

No report.

 

7.5 Federal Electronic and Information Technology Accessibility Standards

Ref:

http://www.access-board.gov/sec508/508standards.htm#PART 1194 - Electronic and Information Technology Accessibility Standards

No report.

 

7.6 Universal Plug and Play Forum

Ref:

http://www.upnp.org/ - Universal Plug and Play Forum
http://www.upnp.org/events/default.asp - Universal Plug and Play Forum Events and Related Industry Events

See V2A report.

MOTION: (Zimmermann, Trewin) that someone report status of V2 activities to UP&P and that Zimmermann is one of the possible candidates to do this.

The motion passed by unanimous consent.

 

7.7 ISO/IEC JTC1 SC 36

Ref:

http://jtc1sc36.org/ - ISO-IEC JTC1 SC36 Home Page

See item 8.1.4 ISO/IEC JTC1 SC 36 Learning Technology Standards Program of Work.

 

7.8 Other

7.8.1 Metadata

7.8.1.1 Dublin Core

Ref:

http://dublincore.org/ - Dublin Core Metadata Initiative (DCMI)
http://www.imsproject.org/ - IMS Global Learning Consortium, Inc.

Liddy Nevile described the background and activities of the Dublin Core. There was extensive discussion of metadata and areas of mutual interest between V2 and Dublin Core.

MOTION (LaPlant,Vanderheiden) that V2 establish a formal liaison with the Dublin Core for furthering activities of mutual interest.

The motion passed by unanimous consent.

 

7.8.1.2 INCITS L8 Metadata

Ref:

http://www.incits.org/tc_home/l8.htm - INCITS L8 - Metadata
V2/02-0075 Slides for Judy Newton presentation at P9

View Slides for Judy Newton presentation at P9

Judy Newton gave a presentation on L8 during the metadata workshop of the plenary. See the presentation slides.

 

7.8.1.3 DAML-S - DARPA Agent Markup Language

Ref:

http://www.daml.org/ - DARPA Agent Markup Language Home page

No report.

 

7.8.2 XForms

Ref:

http://www.w3.org/TR/xforms/ - XForms 1.0

See V2A report.

 

7.8.3 Pervasive Computing

Ref:

http://www.pervasive2002.org/ - International Conference on Pervasive Computing (Pervasive 2002)

See item 8.1.2 Presentation on Pervasive Computing.

 

7.8.4 INCITS M1 Bio Metrics

Ref:

http://www.incits.org/tc_home/m1.htm - M1 - Biometrics

See item 8.1.1 Presentation on  Bio Metrics.

 

7.8.5 OASIS Human Markup Language

Ref:

http://www.oasis-open.org/committees/humanmarkup/index.shtml - OASIS - Committees - HumanMarkup TC

No report.

 

8. Presentations

8.1 Technical presentations

8.1.1 Presentation on  Bio Metrics

Ref:

V2/02-0066 Slides for Fernando Podio presentation at P9

View Slides for Fernando Podio presentation at P9

Fernando Podio of NIST's Information Technology Laboratory, chair of INCITS M1 - Biometrics and Co-Chair of the US Biometric Consortium gave a presentation on the current standards activity in biometric identification. See the presentation slides.

 

8.1.2 Presentation on Pervasive Computing

Ref:

http://www.nist.gov/smartspace/ - NIST Smart Space Laboratory

Vince Stanford of the NIST Pervasive Computing program discussed their initiatives in networking, pervasive software and pervasive integration. Multi modal user app spaces and pervasive devices with dynamic networking are moving toward supporting a multi faceted access to computers. The function of the 'smart flow' system is to provide standardized data format and data transport mechanisms that allow sophisticated component recognition technology to come together in a mobile, ubiquitous and secure network infrastructure.

Stanford has three basic projects: pervasive distributed software, dynamic networking and multimodal integration. He gave several examples and his presentation was followed by discussions.

Stanford invited V2 delegates to visit his labs for a demonstration and to see where they do the metrics research for standards development.

 

8.1.3 Trace URC Prototype

Ref:

http://sarah.trace.wisc.edu/v2websim-standalone/ - Trace's Web simulation prototype

Zimmermann spoke about the prototyping work Trace has been doing for over a year to support V2. He said prototyping is done to find technical solutions and to make sure The V2 work is reproducible. We would like more independent prototyping to build a pool of implementations.

Trace will soon provide V2 a link for their prototype code after they checked out any copyright issues. The licensing agreement will just  requires that any changes be documented. This prototype work is based on AAIML 3.0 and Trace will work on the new model later this year.

Zimmermann demonstrated the prototype with some common household appliances. Using a HAVI network, he showed how the discovery phase worked and presented the available devices to the URC. He demonstrated controlling devices with voice commands and spoke about adding synonyms and verbal confirmations to improve the user experience. He added that 2 URCs could interact with the target together and changes made by one URC would be reflected on the other.

 

8.1.4 ISO/IEC JTC1 SC 36 Learning Technology Standards Program of Work

Ref:

http://jtc1sc36.org/ - ISO-IEC JTC1 SC36 Home Page

V2/02-0069 Excerpt from UML on Use Cases

Farance said the following JTC1 subcommittees are involved in areas relevant to V2.

He said he can show how these existing standards activities address a numbar of the problems of interest to V2 and how they can be used. He said also that he can point out areas where some aspects of these problems have not been addressed.

In SC 25/WG 1, The approach on home electronic systems is to use data models to separate semantics from binding. These models range from well-defined standardized versions to proprietary, manufacturer-specific versions. One way to deal with this is with metadata registries.

The data models use a "lexicon" which describe each of the features of the device. Using a loose analogy where the overall binding structure is the grammar and the lexicon is the set of words that fit into the grammar, then each of these can be standardized separately. In theory particular bindings can be apply generically to specific lexiconss, which are organized as standard data registries.

With this standard in place you have a description of how things can talk to each other. How you get access to this standard is an implementation issue. It does not matter if the standard is incorporated in a ROM of a small device or if the device is capable of communicating with a local server or with the web and figuring out what is in the lexicon.

Farance said using these standards to configure for the needs of the user has 2 aspects.

First, under SC 36 Preferences have been define for the needs of learning technologies and these could be easily extended for the present and future needs of V2. These need not be defined all at once, but can be extended incrementally.

Second, preferences can be communicated with a combination of participant identifiers and locale identifiers. Participant identifiers are standardized under SC 36 and identify humans. This identification could be by name, but not necessarily because of privacy and security issues. Locale identifiers are standardized under SC 22/WG 20 (and WG 15) and identify who you are, where you are and what your capabilities ar. Locale identifiers will be a topic for an upcoming JTC1 plenary.

Farance recommended V2 use all these existing standards structures and address any missing parts needed to meet V2 requirements.

 

8.2 Ad hoc task group reports

8.2.2 V2A - AIAP-URC Editing

Ref:

V2/02-0070 Slides for V2A Report at P9

View Slides for V2A Report at P9

Trewin reported on the work of V2 since the last plenary and described the new architecture developed during a 2-day workshop (see presentation slides).

MOTION: (Trewin) that V2 continue to develop the new architecture for AIAP-URC as proposed by V2A in its report.

The motion passed by unanimous consent.

 

8.2.2 V2B - Framework

Ref:

V2/02-0071 Slides for "Finding the Data Issues"- by Gilman at P9

View Slides for "Finding the Data Issues"- by Gilman at P9

Gilman reported on the 2-day Device Independence workshop at w3c which he and Zimmermann attended. There was discussion on author techniques and how to serve to different devices. Gilman pointed out how different devices is similar to different human needs and preferences. He said the W3C group is interested and gave a positive reception to V2 ideas.

Gilman discussed the new architecture. See the presentation slides.

 

8.2.3 V2C - Managers

Ref:

V2/02-0072 Managers Conference Call notes from 7/11-9/9/2002

LaPlant said the activities of V2C are contained in the minutes of the managers conference call metings.

ACTION ITEM: (Roeder) attach minutes of the managers conference calls to the plenary minutes. {P9/8.2.3}

 

8.2.4 V2D - Discovery

Ref:

V2/02-0073 Slides for V2D Report at P9
V2/02-0074 Draft AIAP-URC working docs 4.1 through 4.3 & related documents
http://www.itl.nist.gov/twiki/bin/view/NCITSV2/MasterListOfOpenAndClosedIssues

View Slides for V2D Report at P9

Zimmermann reported on the Discovery task group which held 3 work sessions since the last plenary and which is assigned 9 previous open issues and 9 new open issues.

Farance, noting the reference to RFC 1766 in closed issue 56, said this reference is superceded by RFC 3066.

Zimmermann led a review and discussion of the proposed solutions for the following issues (for details, refer to "AIAP-URC-ClosedIssues-V4.3.doc" in V2/02-0074).

Issue 92: Structure for service model

There were no modifications to the proposed solution.

issue 121: Application controlled timed events

There were no modifications to the proposed solution.

issue 123: Target selection

There were no modifications to the proposed solution.

issue 124: Connection and disconnection

Zimmermann said V2D chose to drop the term "physical connection" and simply use "connection" as defined by ANSI. Farance said in general better definitions would be in ISO IEC 2382, the information technology vocabulary. Following some discussion Zimmermann recommended concluding this issue and dealing with the terminology question separately.

Farance said he would look at the glossary and mentioned his work with glossary for INCITS-K5. Gilman noted that the V2 glossary group would be very interested in information from Farance about the database repositories that are used for glossaries.

issue 125: Reset service command

There were no modifications to the proposed solution.

issue 126: URC disconnect event

There were no modifications to the proposed solution.

issue 127: Loss of connection

There were no modifications to the proposed solution.

issue 149: Text equivalent for target labeling

There were no modifications to the proposed solution.

issue 150: Required target properties by target type

Zimmermann referred to a table in chapter 10 of the AIAP-URC draft document. He said this section about target properties to be exposed for discovery are metadata and we could look at how to represent this metadata so it fits with Dublin Core.

There was discussion about whether the target location needed to be a network address and this was taken as a new issue.

The name of the target raised questions about culturally linguistic adaptable environments and whether this should be a single entry or an array of entries. This will be taken as a new issue.

During the discussion of target categories, Farance recommended coordination with the work of SC 35 regarding the open EDI material on how to refer to entities and how to incorporate ISO 6523 (the world wide registry of registries).

The set of keywords for target functionality provoked a general discussion on the mandatory vs. optional designations. Farance suggested some items should be optional with guidance notes.

The discussion about the manufacturer codes indicated more work is needed and will be taken as an issue for the metadata group. Farance again referenced ISO 6523, information technology, structure for the identification of organizations and organization parts, and to part 1 which is the identification of organization identification schemes .

After the explanation of the product ID codes, Farance noted that this data element was being overloaded and recommended restructuringd to have 3 separate elements for product type, version number and serial number. This was taken as an issue for further work.

For verbal location information, Farance recommended using ISO 19115, geographic information- metadata.

For geo-coordinates reference is again made to ISO 19100 series.

issue 155: Unit identification code necessary?

This is related to the discussion on product ID codes in the previous issue.

issue 158: Target properties for devices vs. services

Zimmermann said there was no need to address this issue because it was covered by the expansion of the table of target properties to include devices and services. The result was the table discussed in the previous issue.

issue 181: Single vs. multi-user targets in discovery phase

There were no modifications to the proposed solution.

issue 182: Target abort session

There were no modifications to the proposed solution.

MOTION: (Zimmermann) that V2 plenary approve the solutions for issues as proposed by V2D as modified or as referred to new open issues.

The motion passed by unanimous consent.

MOTION: (Zimmermann) that V2 approve a new version 5.0 of the current AIAP-URC specification that evolves from the conditions that were approved by the previous motion with an amended caveat referencing a description to be developed of the new framework architecture.

The motion passed by unanimous consent.

ATCION ITEM, Zimmermann will be the coordinating editor for preparing version 5 of the draft AIAP-URC specification and coordinating the resolved issues.

ATCION ITEM, Trewin will produce the draft description of the new framework.

 

8.2.5 V2E - Editing

Haritos-Shea reviewed the documentation process for standards development by an INCITS technical committee. The required documents of immediate concern to V2 include:

Haritos-Shea is also working with Roeder and Sajka on modifications to V2 web site. LaPlant and Haritos-Shea will talk to INCITS staff about any IPR issues that may affect how public we can make our documents. Farance suggested the SC36 web site as an example. Ref: http://www.jtc1sc36.org/

 

8.2.6 V2G - Glossary/scenarios

LaPlant said we may need to replace Kindricks but he has not been able to contact him to confirm this.

LaPlant said we do not yet have a template for scenarios. Farance suggested looking at the UML specifications for an example template for use case and provided an Excerpt (Ref: V2/02-0069).

Nevile offered an example use case scenario (Ref: V2/02-0077). Farance said he will pass this scenario on to SC25 working group 1 to get feedback and perhaps a variant case with home electronics.

 

8.2.7 V2M - Metadata

Ref:

V2/02-0076 Draft V2 Metadata Working Paper (version0.3)

Sheppard said V2M held 3 telecoms and developed a draft working document for metadata. Roucoux presented the metadata document. V2M also held a 2-day workshop as part of this plenary.

Future effort will focus on the metadata document and better understanding of the 5 domains of information identified in the workshop. With aid from Dublin Core and others, they will work out how to integrate metadata into the V2 design.

ACTION ITEM: (Sheppard) make sure Myers and Farance are on V2 reflector list. {P9/8.2.7}

 

8.2.8 V2S - Security

Chapman said SHARE decided for budgetary reasons to resign from V2. He will continue to dialog and participate in teleconferences until V2 finds someone to take over the security work group. He will also send a CD of all the materials he collected for V2S.

Tom Karygiannis of the NIST computer security department joined for a general discussion on security methods and how they relate to V2. He said there are 4 basic requirements for security: confidentiality, availibility, authenticity and reliabillity. He recommended following the link on the CERTS site called "octave"- to find an aid for risk assessment.

 

9. Discussion of tasks and priorities

9.1 Working Sessions

Ref:

V2/02-0077 URC Use Case Scenario presented at P9 by Nevile
V2/02-0078 Gilman's Diagram presented at P9
V2/02-0079 Trewin work plan

There was discussions on what to do with draft #5 of AAIML and the recommendation was made to post it with a disclaimer that significant changes are coming. There was also discussion about making information about V2 and the new architecture easier for the public to access. LaPlant said V2 officers will work on making the V2 web site mor organized and open to the public.

ACTION ITEM: (LaPlant Haritos-Shea Roeder Sheppard) work out distribution of plenary presentation documents. {P9/9.1}

A pointer to the 2 cloud description will be provided for the minutes.

ACTION ITEM: (Zimmermann) provide pointer for 3 model descriptions. {P9/9.1}

There was further discussion of the new architecture and how to plan the work for developing the draft standard document. Zimmermann referred to a spreadsheet with a rough work plan for V2 remodeling that he posted to the V2A reflector. (Ref: http://www.itl.nist.gov/div896/emaildir/v2a/msg00491.html).

Zimmermann recommended V2 work on metadata as a whole, not as a work group. A telecom will be set up for 3-5 PM (ET) on 10/9/2002.

MOTION: (Trewin, Haritos-Shea) that V2 establish the managers ad hoc group for the period up to the next plenary, consisting of assigned area editors as defined by the "clouds" as described in the architecture plus the V2 officers plus anyone who wants to joine.

The motion passed by unanimous consent.

 

10. Pending Items.

10.1 Planning for Implementors' Workshop

Vanderheiden gave a title for the CSUN panel and an abstract description was developed.

The CSUN proposal was approved without objections

ACTION ITEM: (Vanderheiden Trewin) complete the CSUN proposal. {P9/9.1}

There was discussion about how to publish version 5.0 of AAIML.

ACTION ITEM: (Haritos-Shea Roeder LaPlant) check with INCITS on IPR issues with posting version 5 of the AIAP-URC documents. {P9/9.1}

MOTION: (Trewin,Gilman) that the V2 managers group is authorized to act on behalf of the V2 plenary between the end of plenary #9 and the beginning of plenary #10.

The motion passed by unanimous consent.

V2C will decide how to handle the question of publication.

MOTION: (Vanderheiden, Trewin) to create an ad hoc working group of the whole [named V2A] and to appoint Zimmermann and Trewin co chairs with the power to act as editors in proposing changes [to the draft AIML-URC document] and to convene a series of conference call working sessions.

The motion passed by unanimous consent.

MOTION: (Vanderheiden, Haritos-Shea) to create V2M and V2S to continue discussions in areas of metadata and security, respectively.

The motion passed by unanimous consent.

Per recommendation from Gilman actions on V2G and V2M are deferred.

 

10.2 V2 Server.

No report.

 

11. New Items.

Haritos-Shea invited HP/Compaq to join V2. Mark Engles of the HP program office is leading on their accessibility engineering efforts and will be the contact person for future V2 activities.

ACTION ITEM: (LaPlant Haritos-Shea) contact HP about joining V2. {P9/9.1}

ACTION ITEM: (LaPlant Haritos-Shea) write a letter to Nevile establishing the Dublin Core as a liaison to V2. {P9/9.1}

ACTION ITEM: (LaPlant Haritos-Shea) contact Sun Micro Systems representatives about the new AIAP architecture which will accommodate JAVA and rich media content. {P9/9.1}

 

12. Future Meetings.

Plenary #10 is planned for January 19-20, 2003, at the end of the ATIA conference in Orlando, Florida, pending a commitment by a host. A fallback to the ATIA venue is somewhere in DC.

ACTION ITEM: (managers) arrange plenary #10 in Orlando colocated with ATIA. {P9/12.1}

LaPlant said he accepted on behalf of V2 the responsibility for finding a representative for the joint ITIC-ATIA committee to develop an AT-E&IT API.

Plenary #11 will be in March, 2003, and colocated with CSUN in Los Angeles, California.

Plenary #12 will be colocated with the June 19-23, 2003, RESNA conference in Atlanta, Georgia.

Plenary #13 is planned for October, 2003, at the Trace center in Madison, Wisconsin.

The next V2 managers conference call meeting will be 4-6 PM (ET) on October 16, 2002.

 

13. Summary of Action Items

Ref:

http://www.incits.org/tc_home/v2htm/docs/V2/sd-03/v2sd03_P009.htm - Summary Table Form of V2 ACTION ITEMS LIST for P9
http://www.incits.org/tc_home/v2htm/docs/V2/sd-03/v2sd03_P009_T.htm - Summary Text Form of V2 ACTION ITEMS LIST for P9

 

14. Adjournment

V2 plenary #9 adjourned at 4 PM (ET) on Friday, October 4, 2002.

 

attachments:

v2020052R3 - FINAL AGENDA FOR V2 PLENARY MEETING #9