Minutes – Z39.86 Advisory Committee Conference Call

Date: 02 March 2005
Time: 9:00 – 10:10 EST
Venue: telcon
Scribe: George Kerscher
Last Edited: 15 March 2005
Status: Version 1

Attendees

Advisory Committee:

Participating Experts:

Apologies:

Agenda

The agenda was distributed to the Advisory Committee's list on March 1, 2005. there were no amendments in advance of the call.

There were no additions to the proposed agenda.

3. Confirmation of Date and Time for Next Call

Gk reminded the committee that the next call be held on April 6, 2005.

SMIL Working Group Report

Note: Marisa provided this written report of the oral report provided on the call.

SMIL F2F Summary

February 28 - March 1, 2005
Boston, USA

Attendees from DAISY:

This report prepared by Marisa.

Overview

The working group spent approximately one day brainstorming for SMIL version-next and preparing the requirements skeleton. Other agenda items were to respond to comments about SMIL 2.1 and plan the next F2F.

Some potential goals for SMIL 3 (as given by the group)

Discussion points relevant to DAISY

Notes on SMIL and DAISY

In general, our requirements for SMIL features fall into the following categories:

Comments

Note: Mark Hakkinen is the editor for the requirements of SMIL next.

API Development

George provided a report of discussions with Hiroshi in Geneva and the DAISY Board in Hamburg.

There are a number of developments in the SMIL world. AMI may join with Ambulent player (CWI smil player)., Hiroshi has hired Daniel Wick, the programmer working on the Limsee2 authoring tool from INRIA. There are opportunities for collaboration between the DAISY/NISO community and the mainstream.

Hiroshi is proposing a meeting in Japan for the experts from DAISY and the mainstream for some time in May. There was a long discussion of possible dates.

ACTION: George will work with Hiroshi and identify possible dates for the group.

2005 Version status

Michael informed the committee earlier that the 2005 specification passed NISO. It is now with ANSI for approval. This is normally a fast process.

Michael has a number of action items associated with the specification now that it is approved.