in040334
------------
v2040008r extract.html
INCITS/V2 Technical Committee
Information Technology Access Interfaces
February 2, 2004
Reply to: Joe Roeder, V2 Secretary
Email: jroeder@nib.org
DOC: V2/04-0008r
MINUTES of INCITS V2 PLENARY MEETING #14
Meeting Location: This meeting was hosted by the National Institute of Standards
and Technology, Gaithersburg, Maryland.
Meeting Dates:
Wednesday, January 14, 2004 - 9:00 AM - 6:00 PM (ET) NIST, Building 304 Room
126, Gaithersburg, Maryland.
Thursday, January 15, 2004 - 9:00 AM - 6:00 PM (ET) NIST, Building 304 Room
126, Gaithersburg, Maryland.
_____
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
Bill LaPlant, Dept of Commerce, A/ Chair, INCITS-V2
Alfred S. Gilman, Free Desktop Accessibility Working Group (FDAWG), A
Chris Hofstader, Freedom Scientific, P
Shari Trewin, IBM, P
Katie Haritos-Shea, Katie Haritos-Shea Consultant, P/ Vice chair, incits-V2
Joe Roeder, NIB, P/ Secretary, INCITS-V2
Ed Price, RERC on Mobile Wireless Technologies for Persons with Disabilities,
P
Gregg Vanderheiden, Trace Research & Development Center, P
Gottfried Zimmermann, Trace Research & Development Center, A
V2 has 18 members and a quorum is 6. With 9 members present, a quorum exists.
Liaisons
Liddy Nevile, Latrobe University and DCMI/ chair, Dublin Core accessibility
special interest group
Observers and guests
Charles Sheppard, Dept of Commerce/NIST
Perrine Roucoux, NIST
Mary Theofamos, Dept of Commerce/NIST
Jeremy Johnson, Georgia Tech, IMTC/Wireless RERC
3. Approval of the Agenda.
Ref:
V2/03-0091r1 - Revised Draft Agenda for meeting #14 of V2, 1/14-15/2004
The following modifications were made to the agenda:
added item 8.6.6 Consumer Electronics Show - CES (Vanderheiden)
removed item 9.1.1
changed 'V2.1' to 'V2S' in item 9.2.5
added 9.2.6 V2P (Vanderheiden)
changed item 11.1 to 11.1 Future directions (Vanderheiden)
The agenda as revised was approved unanimously. See attachment, "Final
agenda for plenary #14 of V2, 1/14-15/2004".
_____
...
_____
12. New Items.
12.1 Draft Project Proposals
LaPlant provided 5 draft proposals for new projects. These were discussed
and modified by the plenary (see attachments xx through xx).
12.1.1 Project Proposal to Develop a New Standard Alternate Interface Access
Protocol -Universal Remote Console (AIAP-URC) Specification
Ref: V2/03-0092 INCITS/V2 Project Proposal for AIAP-URC
MOTION (Price, Haritos-Shea) to proceed with the development of a new American
national standard, titled "Universal Remote Console", as approved as amended
by plenary #14.
The motion passed by unanimous consent.
12.1.2 Project Proposal to Develop a New Standard Alternate Interface Access
Protocol -Standard User Interface Socket Description
Ref: V2/03-0093 INCITS/V2 Project Proposal to Develop a New Standard Alternate
Interface Access Protocol —Standard User Interface Socket Description
MOTION (Price, Haritos-Shea) to proceed with the development of a new American
national standard, titled "User Interface Socket Description", as approved
as amended by plenary #14.
The motion passed by unanimous consent.
12.1.3 Project Proposal to Develop a New Standard Alternate Interface Access
Protocol -Standard Presentation Template
Ref: V2/03-0094 INCITS/V2 Project Proposal to Develop a New Standard
Alternate Interface Access Protocol —Standard Presentation Template
MOTION (Price, Haritos-Shea) to proceed with the development of a new American
national standard, titled "presentation template", as approved as amended
by plenary #14.
The motion passed by unanimous consent.
12.1.4 Project Proposal to Develop a New Standard Alternate Interface Access
Protocol -Standard Resource Description
Ref: V2/03-0095 INCITS/V2 Project Proposal to Develop a New Standard
Alternate Interface Access Protocol —Standard Resource Description
MOTION (Price, Haritos-Shea) to proceed with the development of a new American
national standard, titled "Resource Description", as approved as amended
by plenary #14.
The motion passed by unanimous consent.
12.1.5 Project Proposal to Develop a New Standard Alternate Interface Access
Protocol -Standard Target Properties Sheet
Ref: V2/03-0096 INCITS/V2 Project Proposal to Develop a New Standard
Alternate Interface Access Protocol —Standard Target Properties Sheet
MOTION (Price, Haritos-Shea) to proceed with the development of a new
American national standard, titled "Target Property Sheet specification",
as approved as amended by plenary #14.
The motion passed by unanimous consent.
ACTION ITEM: (LaPlant) send notification form to INCITS regarding approval
of 5 projects and drafts to be sent in 2 weeks. [P14/12.1.5]
12.2 Vote to submit the latest version of the draft AIAP-URC standard to
INCITS
A letter ballot will commence in about 2 weeks when all the edits
are incorporated.
13. Future Meeting.
13. March, 2004, CSUN, Los Angeles, CA (Plenary #15)
_____
...
_____
15. Adjournment
V2 Plenary #14 meeting ended at 5:45 PM (ET).
ATTACHMENTS:
Final agenda for plenary #14 of V2, 1/14-15/2004
_____
INCITS_V2_Terms_of_Reference-extract.html
Terms of Reference - INCITS/V2
Information Technology Access Interfaces Technical Committee
Presentation Template
A standard form of UIID that is modality-independent.
[Definition from 'Protocol to Facilitate Operation of Information and Electronic
Products through Remote and Alternative Interfaces and Intelligent Agents
– Presentation Templates'] XML document that contains modality-independent
presentation information for a User Interface Socket Description, for example
grouping and ordering of elements. It is expressed using the Presentation
Template Markup Language (PreTML).
Core Presentation Template
A Presentation Template that is required in an AIAP-URC Portal. A core
presentation template is expressed using the basic profile of the Presentation
Template Markup Language (PreTML-Basic) and is subject to additional conformance
conditions specified in this document. [from V2-URC]
Presentation Template Markup Language, PreTML
[Definition from 'Protocol to Facilitate Operation of Information and Electronic
Products through Remote and Alternative Interfaces and Intelligent Agents
– Presentation Templates'] An XML Language for specification of Presentation
Templates.
The language is specified in the associated document 'Protocol to Facilitate
Operation of Information and Electronic Products through Remote and Alternative
Interfaces and Intelligent Agents – Presentation Templates'.
Presentation Template Markup Language – Basic Profile, PreTML-Basic
[Definition from 'Protocol to Facilitate Operation of Information and Electronic
Products through Remote and Alternative Interfaces and Intelligent Agents
– Presentation Templates'] A restricted profile of the PreTML language.
It is specified in the associated document 'Protocol to Facilitate Operation
of Information and Electronic Products through Remote and Alternative Interfaces
and Intelligent Agents – Presentation Templates'.
Protocol to Facilitate Operation of Information and Electronic Products through
Remote and Alternative Interfaces and Intelligent Agents
A set of standards for the discovery, selection, configuration, presentation,
and operation of user interfaces. [from V2-URC]
Resource
An identifiable object of a user interface that is used as an atomic entity
in the construction of a concrete user interface. Resources include
Label Resources, Help Resources, Access Key Resources and Keyword Resources.
A Resource may be of any form, including text, images, sounds, animations
and video clips. [from V2-URC]
Supplemental Resource
A Resource made available externally to a Portal. [from V2-URC]
Standard Resource
A Resource in V2-URC standard format, as specified in the associated document
'Protocol to Facilitate Operation of Information and Electronic Products
through Remote and Alternative Interfaces and Intelligent Agents – Resource
Descriptions'. [from V2-URC]
Access Key Resource
A Resource that specifies a single character that can be used in combination
with a URC-specific mechanism to move the focus to an element of an interface.
When an access key is bound to a command, entering the access key will activate
the command. [from V2-URC]
Help Resource
A Resource intended to be used to provide help to a user of a Target.
[from V2-URC]
Keyword Resource
A Resource that specifies a keyword pertaining to a referenced element.
[from V2-URC]
Label Resource
A resource used to label, identify or present an element in a user interface.
For example, the label "John F Kennedy International Airport" could be used
to present the value "JFK", or the label "Destination" could be used to identify
an input field where the user must enter a travel destination. [from
V2-URC]
Portal Core Label, Core Label
A label resource required to be present for a Portal to be V2-URC compliant.
[from V2-URC]
Supplemental Label
A label resource made available externally to a Portal. [from V2-URC]
Resource Description
[Definition from 'Protocol to Facilitate Operation of Information and Electronic
Products through Remote and Alternative Interfaces and Intelligent Agents
– Resource Descriptions'] A Resource Description describes a given Resource
in terms of its properties, including in what context the Resource may be
applied. A Resource Description is described in the Resource Description
Framework (RDF) format.
Resource Description Framework, RDF
A specification being developed by the W3C to provide an infrastructure to
support metadata on the Internet and WWW. See http://www.w3.org/RDF/.
Resource Service
A service that provides resources from Target manufacturers, URC manufacturers
and any third parties, beyond the resources that are provided by a Target
in its local network environment. [from V2-URC]
Resource Service Description
[Definition from 'Alternate Interface Access Protocol – Standard Resource
Descriptions'] A description of and reference to a resource service that
can be queried for Resources. A Resource Service Description is given
in the Resource Description Framework (RDF) format.
Resource Sheet
[Definition from 'Protocol to Facilitate Operation of Information and Electronic
Products through Remote and Alternative Interfaces and Intelligent Agents
– Resource Descriptions'] A file that contains Resource Descriptions.
A Resource Sheet is described in the Resource Description Framework (RDF)
format.
Resource Sheet Collection
[Definition from 'Protocol to Facilitate Operation of Information and Electronic
Products through Remote and Alternative Interfaces and Intelligent Agents
– Resource Descriptions'] A file or part of a file that contains references
to Resource Sheets and other Resource Sheet Collections. Resource Sheet
Collections can be used as hierarchical "directories" of Resource Sheets,
facilitating the selection of appropriate Resource Sheets by a URC or Resource
Service. Each Resource Sheet Collection provides hereby a "scent" of
the properties of the directly or indirectly referenced Resource Sheets.
A Resource Sheet Collection is described in the Resource Description Framework
(RDF) format.
A Resource Sheet Collection description is based on the Resource Description
Framework (RDF). See the separate document "Protocol to Facilitate
Operation of Information and Electronic Products through Remote and Alternative
Interfaces and Intelligent Agents – Resource Descriptions" for details on
Resource Sheet Collections.
Socket, User Interface Socket, V2-URC Socket, Standard User Interface Socket
The portion of a Portal that provides access to and control of a functional
unit of the Target. All of the control and interaction with the Portal
of the Target, including all information flow, is achieved with and through
the Portal's Socket.
[Definition from 'Protocol to Facilitate Operation of Information and Electronic
Products through Remote and Alternative Interfaces and Intelligent Agents
– User Interface Socket Description'] An abstract concept that, when implemented,
exposes the functionality and state of a Target in a machine-interpretable
manner.
Socket Description
A specification that describes the functions and properties of a Socket.
A Socket Description is expressed in XML with the markup language specified
in the associated document 'Protocol to Facilitate Operation of Information
and Electronic Products through Remote and Alternative Interfaces and Intelligent
Agents – User Interface Socket Description. [from V2-URC]
Target
A device or service that can be remotely accessed by a Universal Remote Console
(URC).
[Definition from 'Protocol to Facilitate Operation of Information and Electronic
Products through Remote and Alternative Interfaces and Intelligent Agents
– User Interface Socket Description'] A device (e.g. VCR) or service (e.g.
online phone directory) that the user wishes to use.
Private Target
A Target that is available to a specific set of users. For example,
a copier in an office, a TV in a hotel or a microwave oven in a private home.
[from V2-URC]
Public Target
A Target that is available to any member of the public. For example,
an information kiosk, ATM or ticket vending machine. [from V2-URC]
Target Properties Sheet, TPS
A document containing information on a Target that is necessary for discovery
of and access to the Target and its Portals via V2-URC. There is one
Target Properties Sheet per Target. [from V2-URC]
Universal Remote Console, URC
A device or software through which the user accesses a Target. The
URC complies with the V2-URC specification and is capable of rendering a
user interface for any V2-URC compliant Target. It is “universal” in
the sense that it can be used to control any V2-URC compliant target.
It is assumed that users will choose a URC capable of meeting their personal
interaction requirements. [from V2-URC]
Universal Remote Console Specification of the Protocol to Facilitate Operation
of Information and Electronic Products through Remote and Alternative Interfaces
and Intelligent Agents, V2-URC
A set of documents specifying a standard that enables remote User Interfaces
and remote control of network-accessible electronic devices and services
through a Universal Remote Console (URC). [from V2-URC]
User Interface, UI
The means by which a user interacts with a Target. The interface includes
information displayed to the user, values the user can enter or manipulate,
and all other actions the user can instruct the Target to take. [from
V2-URC]
User Interface Implementation Description, UIID
A description for implementing a user interface to a Target