Minutes – Z39.86 Advisory Committee Conference Call

Date: 2006 May 03
Time: 9:00 – 10:10 EST
Venue: telcon
Scribe: Laurie Sherve
Last Edited: 2006 May 04
Status: Version 2

Attendees

Advisory Committee:

Participating Experts:

Apologies:

Agenda

Confirmation of Date and Time for Next Call

GK proposed that the next call be held on 2006 June 07.

Welcome

To Daniel Farrington from Dolphin.

Chris Wilder-Smith has left CAST and the zed committee. CAST will eventually assign someone else to the zed committee.

dtbook-2005-1 Errata Proposal

Action: Laurie to update issues database once the dtd is posted
Action: Markus is requested to include a specific date (yyyy/mm/dd) or "closure date" as the last day for voting on the proposed solution to an issue.
Action: Laurie will coordinate with Markus to add closure dates to issues on the web site.

Markus updated the dtbook-2005-1 errata proposal, adding issues #52, #129,and updating issue #120. He asked for a vote on the proposed solutions for issues #[52]:Title attribute does not allow an id, #[119]:lang attribute, #[48]:Specification reference wrong - RFC 1556, and #[65]:DTD problem and missing spec definition. The committee members could vote a yes or no on the proposed solution. Silence indicates absentia.

Only "yes" votes were recorded for the four proposed solutions to issues #119, #48, #65 and #52. These four issues were non-controversial, and others in the list require more discussion.

As voting closes for each proposed solution, the issue in the dtbook-2005-1 errata proposal is updated as [closed].

After the resolution of all dtd issues, the new dtbook-2005-2 will be placed on the web site, but its existence will not be announced. After dtbook2005-2 is posted, all resolved issues will be moved to a status of "Resolved".

Testing dtbook2005-2

Dave asked what sort of testing should be done on dtbook2005-2. We have to validate the dtd, but there are no test books to check for forward or backwards compatibility, and regression testing. There are some new dtbook documents at tpb and at CAST.

Dave would like to see test documents that "exercise" as much of the dtd as possible. The tests would look at all elements in the dtd in as many combinations that make sense.

We have never taken the time to adequately test a dtd. One method of testing is to release the new dtd "into the wild" and see what issues come back. George would like the new dtd to undergo DMFC testing, and asked that it be incorporated into the DMFC prior to release. ZedVal needs to be updated to support the new dtd.

Dolphin reading tools will support the 2005 version of the specification. The production tools do not yet support the 2005 version of the spec. Testing will be done with handmade books, and hopefully some content from tpb.

Announcements of Updated Specifications and Documentation

Action: George and Laurie to contact NISO to and find out what is needed for a spec maintenance announcement.

NISO will post maintenance updates for us once we are ready to make the announcement. George and Laurie to contact Cynthia and Pat (acting director) of NISO to and find out what is needed for this announcement.

George felt that the release of the Structure Guidelines written by Dave and Lynn and the release of dtbook-2005-2 should be announced together. Neither are ready for release. The Structure Guidelines update are not complete, and we cannot release the dtd until all dtd issues are resolved.

Dave pointed out that the documentation is not part of the standard . Therefore, the release of new documentation does not warrant a NISO statement and the change in dtd would only require an editorial change in the specification. Lloyd felt that documentation work should not hold up an announcement on specification changes.

Decision: When something is ready to go, it will be released as long as there is no dependency on other items. This is a principle we can use moving forward with maintenance items.

Items identified for next meeting

	  Discussion regarding the zed committee f2f.