Editor's note: Minutes received 4/8/93. These minutes have not been edited and the attendee list has not been appended. Reported by Chris Weider Minutes from the IIIR meeting in Columbus, OH, March 29, 1993 Agenda: 1: Introduction and correction of minutes from last meeting 2: Resource Transponders 3: Vision of Integrated Information Services document 4: Start work on Taxonomy document 5: Internet Information Framework 6: AOB 1: There were no corrections offered to the minutes from Washington. 2: Chris Weider discussed his Resource Transponder internet draft. Scott Kaplan of FTP mentioned that a similar concept was already under development in the Service Location Protocol working group for modems and other hardware; Weider agreed to look at the SLP stuff to see if there was any synergy. 3: Peter Deutsch presented the Vision of Integrated Information Services document that he and Chris Weider had developed. It was mentioned that this architecture provides a trivial level of interoperability between currently deployed services, and can provide a foundation for integrating new services. Also, in the discussions of the 'Axioms of Information Services', an axiom was added by the group: "Users want to have the ability to look under the hood". 4: The taxonomy document's contents were discussed; it was finally settled that it would categorize the various available tools by functionality (along several different schemes) and would point out gaps in the current tool mix in light of the architecture provided in the Vision document. Although there was not a universal consensus that such a document was needed, there was a rough consensus that such a document could teach us a lot about what tools we have and what tools we need. Peter Deutsch and Chris Weider volunteered to take a first cut at the paper for Amsterdam. 5: Chris Weider discussed the Internet Information Framework developed by the IESG and several working group chairs. This framework lays out the administrative structure for working groups working in the information services area. In particular, a new working group will not be formed for every information services protocol developed; instead IIIR will take the responsibility of documenting new and existing protocols and shepherding their standardization. Examples of the protocols IIIR will cover include GOPHER (RFC 1436), World Wide Web, and Z39.50. As there are active communities for these protocols, IIIR will simply help the standardization process and may also serve as a mediator if many incompatible versions of the same base protocol appear. For those new protocols which are needed by the integration effort or are identified in the taxonomy paper, IIIR will work with the IESG to determine if a new working group should be formed or if the work can be done in IIIR. 6: There was no other business.