W3C home > Mailing lists > Public > ietf-discuss@w3.org > May 1999

Groupware URIs

From: Jacob Palme <jpalme@dsv.su.se>
Date: Sun, 2 May 1999 01:22:26 +0200
Message-Id: <199905012322.BAA22760@info.dsv.su.se>
To: discuss@apps.ietf.org
Cc: SeniorOnline technical mailing list <sol-tech@ambra.omega.it>
We are working on a groupware application. In this
application, a groupware user always uses the groupware
server, in which this user is registered. But the user can
see groupware objects in other groupware servers. Since the
user interface is web-based, the users use URIs to get to
groupware objects (=forums, contributions, users).

These URIs are constructed by combining the URL of the
user's local groupware server, with the URL of the object.

On server cmc.dsv.su.se there is a forum named free-speech.
On server web4groups.at, a user is participating in this forum.
This user will then use the following URL to get to this forum:

If a user at cmc.dsv.su.se access the same groupware object,
they use the URL

Thus, there are different URLs for the same groupware object,
depending om where a user's local groupware is. But it would
be nice to have some kind of designation of an object which
does not change this way. We have done this by specifying
a new URN or URL scheme named "gw" (for groupware).

Thus, in the above case, the gw URL for this groupware object
would be gw://cmc.dsv.su.se/free-speech.

Ordinary web browser will not understand gw: URIs, unless
they are helped by a directory which tells them which is
the local groupware server for that user. Knowing that,
they can construct the right URL for this user, i.e.
convert gw://cmc.dsv.su.se/free-speech to, for example,

Question 1: Is this the right way to go?

Question 2: The "gw:" URI scheme, is it a new URL
scheme or a new URN scheme?
Jacob Palme <jpalme@dsv.su.se> (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/~jpalme
Received on Saturday, 1 May 1999 19:23:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:08:06 UTC