# Re: *Revised* minutes, URI working group

John A. Kunze (jak@violet.berkeley.edu)
Wed, 28 Dec 1994 17:04:19 -0800

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Michael Mealling: "Re: Library Standards and URIs"
- Previous message: Dirk Herr-Hoyman: "Re: Library Standards and URIs"
- Maybe in reply to: Larry Masinter: "*Revised* minutes, URI working group"
- Next in thread: minutes@cnri.reston.va.us: "Re: *Revised* minutes, URI working group"

    Date: Wed, 28 Dec 1994 17:04:19 -0800

    From: jak@violet.berkeley.edu (John A. Kunze)

    Message-Id: <199412290104.RAA29745@violet.berkeley.edu>

    To: uri@bunyip.com

    Subject: Re: *Revised* minutes, URI working group

Thanks, Karen, for doing the minutes. I have some minor changes
for the Z39.50 section, noted below.

-John
===============
> Subject: *Revised* minutes, URI working group
> From: Larry Masinter <masinter@parc.xerox.com>
> Date: Wed, 28 Dec 1994 13:41:03 PST
...
> of being a stateful protocol. Thus the two URLs are for creating a
> session and retrieval. If a URL is sent for retrieval, either an
> existing session will be used or a session creating URL will be sent
> first.

of being a stateful protocol. Thus the two URLs are for creating a
session and performing a retrieval. If a URL is used for retrieval,
an existing session may be used instead of creating a new session.

> registered by IANA, but until the standard accepted and the procedure

registered by IANA, but until the standard is accepted and the procedure

> There was a certain amount of discussion about the fact that WAIS URLs
> are only retrieval URLs and that they are viewing the whole database
> as a resource, in our terms. It is also possible to do this in a
> Z39.50 URL scheme. [^^^^^^^^ unclear right now -jak]
>
> The Z39.50 implementors' group will meet in January and discuss the
> comments from the IETF.

There was a certain amount of discussion about the fact that WAIS URLs
are only retrieval URLs and that they are viewing the whole database
as a resource, in our terms. More than one person wished to know
whether this were also possible to do in a Z39.50 URL scheme.

The suggestion was made to switch to a more common and modern syntax
within the opaque string, especially regarding use of '&' and '?'.

The Z39.50 Implementors' Group will meet in January and discuss the
comments from the IETF.

- Next message: Michael Mealling: "Re: Library Standards and URIs"
- Previous message: Dirk Herr-Hoyman: "Re: Library Standards and URIs"
- Maybe in reply to: Larry Masinter: "*Revised* minutes, URI working group"
- Next in thread: minutes@cnri.reston.va.us: "Re: *Revised* minutes, URI working group"