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





DOC: V2/01-0006
Date: March 3, 2001

Project: N/A
Ref. Doc: V2/00-003
Reply to: Bill LaPlant, V2 convener
 mailto:Bill.LaPlant@census.gov; blaplant@mindspring.com
MINUTES NCITS V2 PLENARY MEETING #3

Meeting Location:
National Institute of Standards and Technology (NIST)
Lecture Room F, ADMIN (101) Building and
Room B111, Building TECH 225
Gaithersburg, Maryland 20899-0001

Meeting Dates:
Wednesday, February 7, 2001 - 9:00 AM - 5:00 PM (EST) (Lecture Room F - Building ADMIN 101)
Thursday, February 8, 2001 - 9:00 AM - 5:00 PM (EST) Room B111, (Building TECH 225)

1. Call to Order - Meeting called to order at 9:00 AM by Bill LaPlant

2. Introduction of Members and Observers
[Note, (P)=Principal, (A)=Alternate, (L)=Liaison, (O)=Observer, (X)=Ex Officio]

2.1 Members attending )Ref:V2/SD01 "V2 Member Organizations and Contact Information")

2.2 Other Attendees

3. Approval of the Agenda (Ref: V2/01-0001 "

Draft Agenda for meeting #3 of V2, 2/7-8/2001")

LaPlant advised that in future, the committee will use consent agenda, which means consent is assumed unless corrections are made known.  The rule is a 2 weeks notice will be given on the consent agenda.

 

The agenda was amended to add item
"8.2 Presentation on JAVA/JINI (Peter Korn)" (scheduled on Wednesday at 2:30 PM) and item
"8.3 Presentation on Universal Plug and Play (Nasser Ghazi, Brenden, McKean)" (scheduled Wednesday at 1 PM)

Roeder found additional action items in the minutes and asked that they be added to the list to be review.  The following was added:

 

5.26 ACTION ITEM: LaPlant will draft a policy for participation by

telecommunications for consideration by NCITS/V2. [P2/5.11]

the altered agenda was accepted and later amended to include

"10.1 Document management.  Ghazi, Sheppard, and Zimmermann)"

(See ATTACHMENT- FINAL AGENDA FOR V2 PLENARY MEETING #3"AT THE END OF THESE MINUTES)

 

4. Approval of the Minutes for meeting #2 (ref: V2/00-0013 "Draft Minutes for plenary meeting #2 of V2, 12/7-8/2000")


Trewin asked that section 6, paragraph 9 of the minutes be modified to indicate that, while IBM cast a dissenting vote on creation of V2, IBM Does not have the reservation now.

The minutes were accepted as modified.

 

 

5. Review of Action Items
5.1 ACTION ITEM: LaPlant will provide a pointer to the voting record of NCITS on the V2 project proposal. [p1/4]


Done.

5.2 ACTION ITEM: LaPlant and Roeder will make project scope document clearer. [p1/4]

Done.

5.3 ACTION ITEM: Gilman will draft and post to work-def reflector a memo for w3 liaison letter saying what is overlap and type of expertise needed; will coordinate with Urban. [p2/5.4]

On going.  LaPlant to furnish comments.

5.4 ACTION ITEM: Rideout, Vanderheiden and Roeder will organize FAQ and V2 website to make V2 effort more understandable. [p1/10.1]

On going.  Modify to remove Rideout.

5.5 ACTION ITEM: Rideout will do security privacy liaison for V2 and post reports to the reflector. [p1/10.1]

Overcome by events. Rideout/BAE Systems resigned from V2.  A liaison on security is still needed for V2.

NEW ACTION ITEM: LaPlant will find someone to do security privacy liaison for V2.

5.6 ACTION ITEM: LaPlant will keep V2 informed on section508 developments. [p1/13.8]

On going.

5.7 ACTION ITEM: LaPlant and Ms. Laskowski will communicate conference information to ad hoc group leaders.  [p1/10.2] [Note from Roeder: this item might have been unclear. My notes refer to information about setting up a government sponsored phone conference or phone bridge]

Done.

5.8 ACTION ITEM: Zimmermann will post the remote console standard requirements list (as it resulted from the plenary discussion) to the V2 work-def reflector. [P2/8.1.2]

On going.

5.9 ACTION ITEM: Vanderheiden will post his ATIA presentation materials to the V2C reflector. [P2/6]

Done.

5.10 ACTION ITEM: All on the V2C reflector will review and comment on the Vanderheiden ATIA presentation materials. [P2/6]

Done. A quick turn around!   Vanderheiden requests that all furnish more comments to improve document for use on the V2 website.  This item will be retained and modified to say "All: Review and comment on the Vanderheiden ATIA presentation. post comments on the work-def reflector. Vanderheiden urges all to furnish more comments
to improve document for use on V2 website."

 

5.11 ACTION ITEM: LaPlant will draft 2 letters to NCITS about copyright issues re EDAPTA and Stanford. [P2/6]
Carry over.  LaPlant made calls to NCITS, but no response received yet.

5.12 ACTION ITEM: Gilman will provide Roeder with a reference to the XML protocol on the W3C web site. [P2/7.2]

Done. See section 7.2 of plenary #2 minutes.

5.13 ACTION ITEM: LaPlant will provide a link to the web engineering best practices meeting. [P2/7.3]

Done. See section 7.3 of plenary #2 minutes.

5.14 ACTION ITEM: LaPlant provide usability checklist to Roeder for minutes. [P2/7.3]

Done.

5.15 ACTION ITEM: Urban will give document with McCoy's new model to Roeder for minutes. [P2/8.1.3]

Ongoing.


5.16 ACTION ITEM: All members word-smith the purpose and scope on work-def reflector by December 20. [P2/9.0]

Ongoing. This item will be modified to say "All: Word-smith the purpose and scope on the TWiki site."

5.17 ACTION ITEM: Urban will be editor for the final wording of purpose and scope. [P2/9.0]

Carry over.

5.18 ACTION ITEM: Burks to provide more information about AT&T WorldNet access devices. [P2/9.0]

Carry over.

5.19 ACTION ITEM: Roeder to post the list of ad hoc members. [P2/9.1]

Done.

5.20 ACTION ITEM: Kindrick will post on work-def reflector the diagrams for unifying factors. [P2/9.2]

Done.

5.21 ACTION ITEM: Gilman will post the ad hoc V2C report to the work-def reflector. [P2/9.2]

Overcome by events.

5.22 ACTION ITEM: Sheppard and Lakowski will look further to determine if UN taxonomy model is appropriate for V2. [P2/9.2]

On going.  this item will be modified to add "
and will look at draft ANSI ISO/IEC handbook 71."


5.23 ACTION ITEM: Ghazi will make arrangements for teleconferencing the next plenary meeting. [P2/11]

On going.

5.24 ACTION ITEM: Urban will check conference room availability at CSUN. [P2/11]

Done.

5.25 ACTION ITEM: Sheppard will check arrangements for a meeting room at NIST for the next plenary. [P2/11]

Done.

5.26 ACTION ITEM: LaPlant will draft a policy for participation by

telecommunications for consideration by NCITS/V2. [P2/5.11]

Ongoing.  this item will be modified to add "LaPlant will specify procedures for electronic participation to ensure attendance takes place.  Chapman will send LaPlant copy of law text on electronic meeting attendance."

6. Administrative Reports (LaPlant, Urban, Roeder)

Urban reported on the progress to set meeting at CSUN.  V2will get a meeting time for the last 2 days of the conference.  V2 members attending will meet as an ad hoc committee of the whole.  LaPlant said he might be able to attend.

 

Roeder reported  on updates to the V2 website, which includes a standard NCITS Technical Committee format with a link to a V2 working site.  The working site has the plenary meeting announcement with a link to the NIST site for meeting directions and registration, plus a link to the document register in the password protected area.  The public site has a list of member organizations, and the private site has a similar list but with delegate names and contact information.

 

Gilman suggested V2  integrates the website with document management and added that V2 need to find a replacement for kelsey Rideout who had volunteered to provide web design support.

 

LaPlant suggested V2 could have an alternate (non-NCITS) site with more open access for non members.

 

LaPlant reported that the call for volunteers for the Chair of V2 is closed.  Because there was only 1 volunteer (LaPlant), NCITS must now vote on the appointment.  LaPlant is still the acting chair. 

As soon as the NCITS vote is over, there will be call for Vice Chair, Secretary, Vocabulary Reporter, and International Representative.

NEW ACTION ITEM: LaPlant will check NCITS rules on which TC officers are appointed and which are elected. [P3/6.]


7. Review of Related Activities
7.1 Access Board Proposed Electronic and Information Technology Accessibility Standards (ref: "Final 508 standards issued" (

Vanderheiden reported on his presentations at the Access Technology Industry Association (ATIA) conference.  Wakefield's session on 508 was scheduled at the same time and not many Access Technology vendors were at Vanderheiden's talk.  The main purpose, to communicate with Access Technology vendors, was not served.  Vanderheiden suggested V2 needs good descriptions put on the web, printed and mail to Access Technology vendors.  The descriptions should use diagrams and a few key phrases.  The time to do this is about 3 months hence when V2 is further along.

LaPlant added that the GSA consensus activity will be underway by then, which may support access technology people in participation with V2.

 

Gilman suggested that the CSUN conference is a good time to get access technology vendors interested.  Others added that resna, SIG-CHi and the Microsoft advisory committee gatherings would also be opportunities.

 

NEW ACTION ITEM: Urban will nail down room number at CSUN, put together announcement package for review by next Management ad hoc conference call. [P3/7.1]

 

NEW ACTION ITEM: Roeder will get from Urban electronic version of Vanderheiden presentation and attach to minutes. [P3/7.1]

 

Laskowski recommended  putting the Vanderheiden presentation up on the V2 working website, but added that the graphics need to be fully describe in text.  Vanderheiden said he could use his notes on the first version of the slide presentation.

 

LaPlant reported on section 508 consensus development and testing profiles.  The universal access working group(UAWG) sets the agenda for implementation.  He said there are a number of possible activities for ERIM

and that there is a fast track for proof of concept.  The aim is to develop methodologies and performance based metrics for pre-testing products.  The planned kick off meeting at NIST is delayed to April.

 

NEW ACTION ITEM: Gummadi will post to work def the announcement that went to the Universal Access Working Group (UAWG) on the planned kick off meeting of the ADIT project, which will be at NIST in April. [P3/7.1]

 

Roeder asked about the "micro purchase" exception if the proposed FAR regulations.  LaPlant remarked that some agencies are not happy with the exception, which is a 2 year exclusion from 508 standards for purchases under $2,500.  He added that split purchases are not allowed.  The "micro purchase" exception is not covered in the law and thus offers no protection from suits.  

(see 39.X04(a) of the proposed FAR changes)

 

Peet said her colleague at MITRE will do a report on accessibility.

 

LaPlant said a federal XML working group will use XML for tagging.  As we look at how information on Access Technology is shared, a registry or a tagging method might be a way to do this.  Registries were studied in the group that preceded V2 and it is important for V2 members to become knowledgeable of ITA-SG archived documents.

 

The European Union (EU) wants a policy on the formats of international standards, reports, official documents, etc. that give consideration to aging and disabled populations.  this is another framework on what categories need to be considered and LaPlant referenced the  draft ANSI ISO/IEC handbook 71.  LaPlant asked Roeder to attach to the minutes the message on the status of the handbook, which is in PDF format. (Ref: V2/01-0005 "Report of January 2001 meeting on ISO/ IEC Guide 71")

 

7.2 Web Accessibility Initiative (ref: "Web Accessibility Initiative (WAI) Home Page")

Gilman said the WAI made a motion to form a device independent activity targeted to voice interaction, smaller devices, etc.  He noted that it is important to get a WAI liaison.


7.3 IEEE P2001 Web Engineering Best Practices Guidelines (ref: "Internet Practices Standards Working Group")

LaPlant provided pointer to the current draft IEEE best practices which is a standing document so keep checking that URL.

 This group have agreed to work informally with V2 on an accessibility specific document, either under IEEE or V2.

Meiers submitted a document containing extracts of all the places in the current draft of IEEE STANDARD 2001 that address accessibility. (Ref: 

V2/01-0004 "Accessibility References in Draft IEEE Standard 2001 Revision dated November 2000")

He noted that IEEE has a default 5 year review cycle.

 

7.4 Other

No other reports offered.


8. Presentations
8.1 ad hoc Group Reports
8.1.1 ad hoc A

Zimmermann reported that ad hoc A held a phone meeting, not a net meeting, and there was not a consensus on architecture.  They discussed a 4 part architecture and focused on RC (remote console/accessor).  They looked at the underlying protocol, leaning toward XML as a basis.

 

Zimmermann proposed a road map for a prototype wireless RC.

 

The objectives are:

 - iterative development of RC standard

 - determine if AIAP may have separate standard or one broad standard

 - begin as a prototype test bed, use later as a reference

 

The iteration is a cycle of 6 processes:

1. requirements analysis,

2. prototype implementation,

3. prototype evaluation,

4. integration of results into standards,

5. integration into overall standard of V2,

6. loop iteratively.

 

Some assumptions noted are:

 - build on existing standards,

 - PCIP underlying protocol,

 - server/client architecture,

 - does not imply html standard,

 - XML based language,

 - While it was noted that web servers can exist on a chip, use of such a chip is not assume.

 

Some milestones proposed are:

stage 1. setting up architecture (simple, not complex; target device an IP server)

phase 2, move to wireless (Bluetooth; laptop simulating target device; hand held for accessor)

stage 3: target, plus 2 proxies (JINI or UPNP)

stage 4: xform integration

 

Some benefits noted are:

 - separation of data model from presentation, better for braille display,

 - contains a card concepts from mobil technology experience,

 - allows multiple formats.

 

Zimmermann said this would need someone with JINI or UPNP coding ability.

 

Vanderheiden said this proposal is an attempt to capture what has been said, to try to make AIAP technology independent and have more than 1 platform.  He pointed out that there is legacy equipment already out there and it is easier to use layers that are already around.

 

Gilman spoke about X-form, which encodes dialog on the form, then client only needs to render it.  This is all exploratory and still have problems with the broad mix and match between users and targets.

 

8.1.2 ad hoc B

No report- covered in action items.

 

8.1.3 ad hoc C

No report- covered in action items.


8.2 Presentation on JAVA/JINI.

Peter Korn gave a presentation on a JAVA/JINI approach to user interface (UI) services.  some highlights included:
 - allows devices without knowledge of each other to discover and connect,

 - very scalable,

 - works with uni-cast and multi-cast discovery,

 - can run on RMI or PCPIP but not required,

 - the target is a service, which can be hardware or software,

 - target can be client to another target,

 - a look up directory service is required in the loop.

 

The look up service gives a lease (keeps net traffic low; if lease expires, the service is dropped from the net).  An accessor looks up a service, downloads JAVA code, then runs the JAVA code in a secure context.  The accessor then communicates directly to the service.

 

The service knows the UI architecture.  this can work over any network used by the service and the accessor.  The accessor could have a private connection to a surrogate.

 

A portions of a Real Player demo (Ref: "Global Explorer Press Conference"), was shown to illustrate how this works.  In this demonstration, the devices spoke LonWork.

 

The JINI service could download an XML surrogate.  an advantage is that it is easily updated for new devices.

An accessor needs JINI for walking along discovery, triangulation.  Korn remarked that Zucotto Wireless, Inc., (Ref: "Zucotto Wireless, Inc.") "ducotto.com makes an "Xpresso" (TM) chip set implementing JAVA and Bluetooth.  This could be in a dongle on a serial port to handle legacy products.  The dongle is then a surrogate server. 

Note, proxy means proxy to the server or target device; surrogate means surrogate to the client or accessor device.

 

Korn said an AIAP standard need to pick the "wire"; such as, AIAP on Bluetooth or 802.11.  He added that the method of discovery needs to be standardized too.  Vanderheiden said this may be a labeling issue; e.g.,  "AIAP-Bluetooth".  LaPlant said these will be the first 2 items of the open issues list.

 

8.3 Presentation on Universal Plug and Play

Ghazi introduced Brenden, McKean and Mike Freedmman of the Microsoft Accessibility Group for the Microsoft presentation on Universal Plug And Play (UPNP).

 

Some highlights of the presentation included:

 - UPNP runs on XML protocol,

 - designed for major and small appliances,

based on notions of control or monitor points, of a bridge, and of defined services.

 

A device is viewed as a physical or logical container that provide services.  The service is the functional part of the device.  Inputs to service include state variables and actions.  UPNP is not wedded to windows- could be used on other OS.

 

Limitations include:

1. intended for device to device communication and is not human friendly,

2. user still needs to know how to use the target device,

3. uses state variables, no hierarchy,

4. does not address user interface, is a control protocol,

5. fixed number of state functions, not clear how it could work with ATMs

 

LaPlant said members can use work-def for follow up questions about UPNP.

 

Later the Microsoft team began a presentation on "Canonical UI".  Details of this subject were deferred until a question of IPR is resolved.

 

NEW ACTION ITEM: Ghazi, Kaneko will Send slide show of February 7 presentation to v2 members.  Will advise V2 in writing if canonical user interface work will be contributed to open standard; Kaneko will send document to Ghazi, who can decide and forward to V2.
Urban will Follow up with Ghazi on canonical user interface release document.
Urban will Coordinate with Ghazi on Microsoft hosting April 6 working ad hoc meeting in Redland, WA. [P3/8.3]

 

9. Discussion of tasks and priorities

9.1 plenary discussion of ad hoc A, B and C.

Urban led a plenary discussion on the proposal for a prototype wireless RC.

 

The purpose of a prototype is to explore and develop options for the AIAP standard.  A prototype will also help communicate what V2 is doing and recruit participants. the group discussed what agreements were necessary and made several formal motions about the process that will be followed.  Formal votes will be taken on core assumptions.  An informal agreement process will be used for details.   

 

Vanderheiden made the following motion:

 

That all technical information, not required to be public, that is published
regarding standard(s) that V2 is developing will be based on formal votes.


LaPlant seconded the motion which passed by simple majority

 

Vanderheiden then made a motion to create a set of core assumptions, including the scope over which they apply, which we agree to by formal vote, and such core assumptions shall be
made public. 

 

Peet seconded the motion. Following discussion the motion carried by simple majority.

The following motion was made by Laskowski and seconded by Chapman

To agree to use experimental prototypes as a way to explore the development
of V2 standard(s). 

 

this motion passed by unanimous consent.

Vanderheiden then motioned:


That other procedural matters be handled by the management ad-hoc committee, who will post any policy or procedure recommendations to the Work-Def reflector for a 14 öday review period, with ãNEW POLICYä in the subject line, after which they are considered to be adopted by consent in the absence of posted objections. Objections shall contain ãOBJECTIONä or
ãCONCERNä in the subject line of the message. This motion shall appear in all new policy e-mails

the motion was seconded by Chapman and was passed by unanimous consent.

 

A discussion took place about establishing new standing documents for

1 action items
2 open issues
3 research opportunities

These lists will be set up in standing documents and will have pointers to them in the minutes and agenda.  As they are completed, items will be dropped off of the standing documents.  The open issues document will have 3 categories: 1 things decided, 2 things not decided and 3 things that will not be decided.


Vanderheiden suggested the placement of any information on the V2 public web site should be decided by formal vote or by NCITS standard.  Meiers recommended formal votes only on technical information, but not for administrative information.  LaPlant said that the open issues document, the research opportunities document, and not the action items document, should be on the public area of the V2 web site.  There was agreement that the secretary will maintain a list of : open issues, action items, &
research opportunities as V2 standing document. The management Ad-Hoc is tasked with determining the degree of public access to this information.

 

9.2 Working Sessions

There were further discussions on the prototype.  the following document was begun and will be continued on the TWiki site..

 

<<Document begins>>

Current Core Assumptions/Decisions:
-Maximum extent possible ö use standards
-Use Prototypes as a way to explore the development of V2 standard(s)
Exploratory Directions:
- Remote Console
o IP
o HTTP
o XML
o Presentation Independent User Interface Data Structure? (model)
o UPNP Canonical Interface?
o UIML??

To be decided:
- Multi-stage adaptations of interfaces?
- OSI model language?
- modular decomposition of the standard
- architecture
Assumed to NOT be specified as part of our standard:
-Physical Layer

Implementation guidelines:
-Physical layer?
Questions:
Is it practical to Implement IES over IP/HTTP?
How does this relate to 508?
How do morphing technologies tie in..?
How do we create a rich interface environment (re: scalability to
complex/GUI UI?)
How do we deal with alternate GUI interfaces
What is the better approach for accessibility:
a) user accessible GUI
b) presentation-independent user interface description bearing
restrictions regarding complex user interfaces
or some intermediary

<<document ends>>

NEW ACTION ITEM: Urban will clean up and distribute document developed at end of plenary to work def reflector. [P3/9.2]

 

Zimmermann said he reviewed UIML and recommended not using it at this time.

 

NEW ACTION ITEM: Zimmermann will write memo that describes his evaluation of UIML as related to current AIAP development. [P3/9.2]

 

Zimmermann presented an overview of the TWiki set up for V2.  The TWiki home page for V2 is www.itl.nist.gov/twiki/bin/view/NCITSV2/WebHome.  The user logs on with the network ID and password.  (Note, Zimmermann posted the ID and password to the WORK-DEF reflector on February 08, 2001 4:11 PM).

 

To add comments, TWiki creates a link made with the user's first and last name.

 

Zimmermann discussed the requirements doc, on TWiki (Ref: "RequirementsForRemoteConsoleStandard")

 

NEW ACTION ITEM: Trewin will rewrite comment to requirements document.  [P3/9.2]

 

NEW ACTION ITEM: Gilman will create new proposed language changes to requirement 2. [P3/9.2]f

 

Gilman Provided an URL to the  Character Model for the World Wide Web 1.0.

 

NEW ACTION ITEM: Vanderheiden will provide more explanation [detail?] for protocol requirement for human comprehensible text/characters; Vanderheiden's comment in requirements document may need to be broken up into 2 parts. [P3/9.2]

 

LaPlant suggested that for unclear comments, the main editor give notice on WORK-DEF to commentator to explain rationale, otherwise comment will be removed after 14 days.

 

NEW ACTION ITEM: Management ad hoc will decide deadline period for finalizing items on requirements doc. [P3/9.2]

 

NEW ACTION ITEM: Zimmermann will move note from requirements 16 into technical document. [P3/9.2]

 

NEW ACTION ITEM: Management ad hoc will decide if comments on collaboration documents should contain suggested text change and rationale, not just state concerns. [P3/9.2]

 

Urban said we should start breaking out general from technical requirements.

 

NEW ACTION ITEM: ALL will Review and comment on requirements document on TWIKI by March 1. [P3/9.2]


10. New Items.

NEW ACTION ITEM: LaPlant will Send warning letter to non-attendants citing NCITS rule that will forfeit committee membership. [P3/9.1]

 

"10.1 Document management.  Ghazi, Sheppard, and Zimmermann)"

 

11. Future Meetings

Subject to confirmation by laPlant, the next plenary meeting will be on May 10 and 11, 2001, at NIST in gaithersburg, Maryland.  the second choice is May 8 and 9, 2001.

 

Microsoft offers to host a meeting of an ad hoc committee of the whole to work with their canonical user interface group  This meeting will be on April 6, 2001, at Microsoft in Redmond, Washington.  This venue was chosen to take advantage of the SIG/CHI conference.

 

NEW ACTION ITEM: The managers ad hoc committee was reconstituted with all members.  Zimmermann is the leader and the first conference call will be on February 16, 2001, at 3 PM (EST).

Urban asked Zimmermann to coordinate with Ghazi.

 

NEW ACTION ITEM: Zimmermann will talk to Ghazi about net meeting prior to next ad hoc V2A meeting.  [P3/11.]


12. Summary of Action Items (Ref: V2 Action Items)

ACTION ITEM#3: Gilman will draft and post to work-def reflector a memo for w3 liaison letter saying what is overlap and type of expertise needed; coordinate with Urban. [p2/5.4] LaPlant to furnish comments. [P3/5.3]

ACTION ITEM#4: Roeder and Vanderheiden will organize FAQ and V2 website to make V2 effort more understandable. [p1/10.1] [P3/5.4]

ACTION ITEM#6: LaPlant to keep V2 informed on section508 developments. [p1/13.8]

ACTION ITEM#8: Zimmermann will post the remote console standard requirements list (as it resulted from the plenary discussion) to the V2 work-def reflector. [P2/8.1.2]

ACTION ITEM #10: All: Review and comment on the Vanderheiden ATIA presentation. post comments on the work-def reflector. Vanderheiden urges all to furnish more comments
to improve document for use on V2 website. [P2/6] [P3/5.10]

ACTION ITEM#11: LaPlant will draft 2 letters to NCITS about copyright issues re EDAPTA and Stanford. [P2/6]

ACTION ITEM #15: Urban will give document with McCoy's new model to Roeder for minutes. [P2/8.1.3]

 

ACTION ITEM #16: All: Word-smith the purpose and scope on the TWiki site. [P2/9.0]

ACTION ITEM #17: Urban will be editor for the final wording of purpose and scope. [P2/9.0]

ACTION ITEM #18: Burks will provide more information about AT&T WorldNet access devices. [P2/9.0]

ACTION ITEM #22: Lakowski and Sheppard will look further to determine if UN taxonomy model is appropriate for V2. [P2/9.2] and will look at draft ANSI ISO/IEC handbook 71. [P3/5.22]

ACTION ITEM #23: Ghazi will make arrangements for teleconferencing the next plenary meeting. [P2/11]

ACTION ITEM #26: LaPlant will draft a policy for participation by telecommunications for consideration by NCITS/V2. [P2/5.11] LaPlant Will specify procedures for electronic participation to ensure attendance takes place; Chapman will send LaPlant copy of law text on electronic meeting attendance. [P3/5.26]

ACTION ITEM #27: LaPlant will Find someone to do security privacy liaison for V2. [p1/10.1] [p3/5.5]

ACTION ITEM #30: LaPlant will Check NCITS rules on which TC officers are appointed and which are elected. [P3/6.]


ACTION ITEM #31: Urban will Nail down room number at CSUN, put together announcement package for review by next Management ad hoc conference call. [P3/7.1]

ACTION ITEM #32: Roeder will Get from Urban electronic version of Vanderheiden presentation and attach to minutes. [P3/7.1]

ACTION ITEM #33: Gummadi will post to work def the announcement that went to the Universal Access Working Group (UAWG) on the planned kick off meeting of the ADIT project which will be at NIST in April. [P3/7.1]

 

ACTION ITEM #35: Ghazi, Kaneko will Send slide show of February 7 presentation to v2 members.  Will advise V2 in writing if canonical user interface work will be contributed to open standard; Kaneko will send document to Ghazi, who can decide and forward to V2.
Urban will Follow up with Ghazi on canonical user interface release document.
Urban will Coordinate with Ghazi on Microsoft hosting April 6 working ad hoc meeting in Redland, WA. [P3/8.3]

 

ACTION ITEM #36: LaPlant will Send warning letter to non-attendants citing NCITS rule that will forfeit committee membership. [P3/9.1]

 

ACTION ITEM #40: Zimmermann will Talk to Ghazi about net meeting prior to next ad hoc V2A conference call.

ACTION ITEM #41: Urban will clean up and distribute document developed at end of plenary to work def reflector. [P3/9.2]

 

ACTION ITEM #42: Zimmermann will Write memo that describes evaluation of UIML as related to current AIAP development. [P3/9.2]

ACTION ITEM #43: Trewin will rewrite comment to requirements document.  [P3/9.2]

 

ACTION ITEM #44: Gilman will Create new proposed language changes to requirement 2. [P3/9.2]

ACTION ITEM #46: Vanderheiden will Provide more explanation [detail?] for protocol requirement for human comprehensible text/characters; Vanderheiden's comment in requirements
document may need to be broken up into 2 parts. [P3/9.2]

ACTION ITEM #47: Management ad hoc will Decide deadline period for finalizing items on requirements doc. [P3/9.2]

ACTION ITEM #48: Zimmermann will Move note from requirements 16 into technical document. [P3/9.2]

ACTION ITEM #49: Management AD HOC will Decide if comments on collaboration documents should contain suggested text change and rationale, not just state concerns. [P3/9.2]

ACTION ITEM #50: ALL will Review and comment on requirements document on TWIKI by March 1. [P3/9.2]

 

13. Adjournment

 

Meeting #003 of V2 adjourned at 5:30 PM on Thursday, February 8, 2001.

 

SUMMARY OF REFERENCE LINKS IN THESE MINUTES

 

V2/SD01 "V2 Member Organizations and Contact Information"

 URL: http://www.ncits.org/tc_home/v2htm/XV2docs/v2SD01.htm

 

V2/00-0013 "Draft Minutes for plenary meeting #2 of V2, 12/7-8/2000"

 URL: http://www.ncits.org/tc_home/v2htm/XV2docs/v200013.htm

 

V2/01-0001

"Draft Agenda for meeting #3 of V2, 2/7-8/2001"

 URL: http://www.ncits.org/tc_home/v2htm/XV2docs/v201001.htm

 

V2/01-0004

"Accessibility References in Draft IEEE Standard 2001 Revision dated November 2000"

 URL: http://www.ncits.org/tc_home/v2htm/XV2docs/v201004.htm

 

V2/01-0005

"Report of January 2001 meeting on ISO/ IEC Guide 71"

 URL: http://www.ncits.org/tc_home/v2htm/XV2docs/v201005.htm

 

 URL: http://www.ncits.org/tc_home/v2htm/XV2docs/v201005.htm

 

"Final 508 standards issued"

 URL: http://www.access-board.gov/news/508-final.htm

 

"Web Accessibility Initiative (WAI) Home Page"

 URL: http://www.w3.org/WAI/

 

"Internet Practices Standards Working Group"

 URL: http://computer.org/standards/Internet/index.htm

 

"Global Explorer Press Conference"

 URL: http://playlist.broadcast.com/makeplaylist.asp?id=766598&segment=19043

 

TWiki home page for V2

URL: http://www.itl.nist.gov/twiki/bin/view/NCITSV2/WebHome

 

"RequirementsForRemoteConsoleStandard"

 URL: http://www.itl.nist.gov/twiki/bin/view/NCITSV2/RequirementsForRemoteConsoleStandard

 

 



Send any comments on this document to mailto:jroeder@nib.org

ATTACHMENT- FINAL AGENDA FOR V2 PLENARY MEETING #3

 

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



 


Doc: V2/01-00001
Date: January 8, 2001
Project: Administrative
Ref. Doc:  V2/01-00002
Reply to: Bill LaPlant
Phone: 301-457-4887; 703-360-9184
email: bill.laplant@census.gov


DRAFT AGENDA
NCITS V2 IT Access Interfaces Technical Committee
Meeting Number 3

Location:
National Institute of Standards and Technology
Room B111, Building TECH 225 and
Lecture Room F, Building ADMIN 101
Gaithersburg, Maryland 20899-0001
301-975-3265 (Dorothy Snyder) or
301-975-4535 (Sharon Laskowski)

Meeting Dates:
Wednesday, February 7, 2001 - 9:00 AM - 1:00 PM (EST) (Room B111 - Bldg TECH 225)
Wednesday, February 7, 2001 - 2:00 PM - 5:30 PM (EST) (Lecture Room F - Bldg ADMIN 101)
Thursday, February 8, 2001 - 9:00 AM - 10:30 AM (EST) (Room B111 - Bldg TECH 225)
Thursday, February 8, 2001 - 12:00 PM - 5:30 PM (EST) (Room B111 - Bldg TECH 225)

Meeting Registration: Register

1. Call to Order (Mr. William LaPlant - Convener)

2. Introduction of attendees.
Ref: V2/00-SD-1 List of Members and Contact Information

3. Approval of the Agenda.
Ref: V2/01-00001  (this document)

4. Approval of the Minutes for meeting #2 ref: V2/00-00013 "Draft Minutes for plenary meeting #2 of V2, 12/7-8/00)"

5. Review of Action Items

5.1 ACTION ITEM: LaPlant will provide a pointer to the voting record of NCITS on the V2 project proposal.
5.2 ACTION ITEM: LaPlant and Roeder will make project scope document clearer.
5.3 ACTION ITEM: Gilman will draft and post to work-def reflector a memo for w3 liaison letter saying what is overlap and type of expertise needed; will coordinate with Urban.
5.4 ACTION ITEM: Rideout, Vanderheiden and Roeder will organize FAQ and V2 website to make V2 effort more understandable.
5.5 ACTION ITEM: Rideout will do security privacy liaison for V2 and post reports to the reflector.
5.6 ACTION ITEM: LaPlant will keep V2 informed on section508 developments.
5.7 ACTION ITEM: LaPlant and Ms. Laskowski will communicate conference information to ad hoc group leaders. [Note from Roeder: this item might have been unclear. My notes refer to information about setting up a government sponsored phone conference or phone bridge]
5.8 ACTION ITEM: Zimmermann will post the remote console standard requirements list (as it resulted from the plenary discussion) to the V2 work-def reflector.
5.9 ACTION ITEM: Vanderheiden will post his ATIA presentation materials to the V2C reflector.
5.10 ACTION ITEM: All on the V2C reflector will review and comment on the Vanderheiden ATIA presentation materials.
5.11 ACTION ITEM: LaPlant will draft 2 letters to NCITS about copyright issues re EDAPTA and Stanford.
5.12 ACTION ITEM: Gilman will provide Roeder with a reference to the XML protocol on the W3C web site.
5.13 ACTION ITEM: LaPlant will provide a link to the web engineering best practices meeting.
5.14 ACTION ITEM: LaPlant will include usability check list in V2 annual report.
5.15 ACTION ITEM: Urban will give document with McCoy's new model to Roeder for minutes.
5.16 ACTION ITEM: All members word-smith the purpose and scope on work-def reflector by December 20.
5.17 ACTION ITEM: Urban will be editor for the final wording of purpose and scope.
5.18 ACTION ITEM: Burks to provide more information about AT&T WorldNet access devices.
5.19 ACTION ITEM: Roeder to post the list of ad hoc members.
5.20 ACTION ITEM: Kindrick will post on work-def reflector the diagrams for unifying factors.
5.21 ACTION ITEM: Gilman will post the ad hoc V2C report to the work-def reflector.
5.22 ACTION ITEM: Sheppard and Lakowski will look further to determine if UN taxonomy model is appropriate for V2.
5.23 ACTION ITEM: Ghazi will make arrangements for teleconferencing the next plenary meeting.
5.24 ACTION ITEM: Urban will check conference room availability at CSUN.
5.25 ACTION ITEM: Sheppard will check arrangements for a meeting room at NIST for the next plenary.
5.26 ACTION ITEM: LaPlant will draft a policy for participation by

telecommunications for consideration by NCITS/V2. [P2/5.11]

6. Administrative Reports (LaPlant, Urban, Roeder)

7. Review of Related Activities

7.1 Access Board Proposed Electronic and Information Technology Accessibility Standards ref: http://www.access-board.gov/sec508/508index.htmProposed Standards for Federal Electronic and Information Technology (LaPlant)

7.2 Web Accessibility Initiative ref: http://www.w3.org/WAI/   Web Accessibility Initiative (WAI) Home Page (LaPlant)

7.3 IEEE P2001 Web Engineering Best Practices Guidelines ref: http://computer.org/standards/Internet/index.htm
Internet Practices Standards Working Group   (Meiers)

7.4 Other

8. Presentations

8.1 ad hoc Group Reports

8.1.1 ad hoc A (Zimmermann)

8.1.2 ad hoc B (Gilman)

8.1.3 ad hoc C (Urban)

8.2 Presentation on JAVA/JINI (Peter Korn)
8.3 Presentation on Universal Plug and Play (Nasser Ghazi, Brenden, McKean)

9.  Discussion of tasks and priorities (Urban)

9.1 plenary discussion of ad hoc A, B and C.

9.2 Working Sessions

10. New Items.

10.1 Document management.  Ghazi, Sheppard, and Zimmermann)

11. Future Meetings

12. Summary of Action Items

13. Adjournment


Schedule

Wednesday AM
1, 2, 3, 4, 5, 6

Wednesday PM
7, 8, 9

Thursday AM
9 (continued)

Thursday PM
9 (continued), 10, 11, 12, 13