Moderator:

Robert Cailliau - <cailliau@www1.cern.ch>

This page maintained by:

Bipin C. DESAI <bcdesai@cs.concordia.ca>

LIST OF PARTICIPANTS:

• Tony JOHNSON <tonyjohnson@slac.stanford.edu>

• Dan CONNOLLY <connolly@hal.com>

• Julius HRIVNOC <julius.hrivnoc@cern.ch>

• Iim Berners-Lee <timbl@ww3.cern.ch>

• Michael DOLAN <miked@cerfnet.com>

• Stuart WEIBEL <weibel@oclc.org>

• John ELLSON <john.ellson@att.com>

• Richard SCHMALGEMEIER <rgs@pagel.com>

• Fabrice de COMARMOND <fabrice@src.und.edu>

• Peter DOMEL <doemel@informatik.uni.frankfurt.de>

• Malcolm MCAFEE <paideia@inter.nl.net>

• Andy BOVINGDON <bov@x.co.uk>

• Chris SCHEYBELER <chris@x.co.uk>

• Eric KATZ <ekatz@ncsa.uiuc.edu>

• Bertrand IBRAHIM <bertrand@cui.unige.ch>

• Heinrich STAMERJOHANNS <stamer>@merlin.physik.uni.oldenburg>

• Charles ASHLEY <charles-ashley@learned.co.uk>

• Detlef KROMKER <haller@igd.fhg.de>

• Hans JOSEPH <joseph@igd.fhg.de>

• Henry HOUH <hhh@mit.edu>

• Wendy HALL <wh@ecs.soton.ac.uk>

• David DE ROURDE <dder@ecs.soton.ac.uk>

• Harold SKARDAL <harold@ftp.com>

• Bipin C. DESAI <bcdesai@alcor.concordia.ca>

• David GREAVES <d.greaves@npe.nucphys.nl>

• Herbert VAN ZUL <h.zijl@elsevier.nl>

• Javier ROMEU <jromeu@info.ent.com>

• Per Einar DYBVIK <per.dybvik@nta.no>

• Haakon LIE <howcome@hal.nta.no>

• Nadine GRANGE <grange@earn.net>

• Alon SLATER <afs@cee.hw.ac.uk>

• Vincent QUINT <vincent.quint@imag.fr>

• Murray MALONEY <murray@sco.com>

• Phil NEUMAN <philn@sco.com>

• Brian BEHLENDORF <brian@wired.com>

• Gisle AAS <gisle.ass@nr.no>

• Jean-Pierre PORTE <jpp@ceernvm.cern.ch>

• Morten DAHL <morten.dahl@fundp.ac.be>

• Lee NEWBERG <l-newberg@unchicago.edu>

• Bipin C. DESAI <bcdesai@cs.concordia.ca>

• Larry JACKSON <jackson@ncsa.uiuc.edu>

• Guy SINGH <guy@x.co.uk>

• Frederic JANSSENS <fjanss@iridia.ulb.ac.be>

• Yuri RUBINSKY <yuri@sq.com>

• Bob STAYTON <bobs@sco.com>

• Paul Andre PAYS <paul-andre.pays@inria.fr>

• Barre LUDVIGSEN <borrel@dhhalden.no>

• David MARTIN <dem@hep.net>

Issues Raised/Topics Discussed:

In addition to this list, a parallel list, with extensive comments, is also available. It was generated by Tim Berners-Lee.

• Semantic Header/Search System: Bipin C. DESAI

Semantic header is a portion of each document which should contain some information which would be useful in searching for a document based on a number of commonly used critria. The information from this portion of the document could be used by various indexing schemes to help locate appropriate documents with minimum effort.

The format of the semantic header, which is delimited by the tags <semhdr> .... </semhdr> is positionally independent and a given header must have at least one entry for each of the items such as author, subject, URL etc. See http://www.cs.concordia.ca/bcd/semantic-header.html for additional details.

• Facilities for entereing mathematical equations and tables in HTML

• Permanent names(Lasting names) as in unique object identifiers for pepetuity

• Style sheets

• Security/accounting

• CGI in clents

• Document boundries/printing by documents-linear ordering: Guy Singh

The primary advantages are

a) being able to print a 'book' or 'chapter'. Not all users want to view information on-line. Sometimes it is not appropriate, e.g., reviewing a document is much easier on hard copy. Annotation functionality in current browsers is not powerful enough to allow editorial review.

b) Search within a book. This can be faked by placing the html files within a directory or set of directories and then using cgi-bin scripts to search this area. This is not always possible though, e.g., You want to use parts of the Web in your definition of a book and/or chapter. You could copy them over but..

i) The author might not want you to.

ii) The page/s might be out of date since you copied them over.

• HTTP as a file system

• Authoring systems/tools

• Character sets - ISO LAtin/Extended Symbol fonts

• Searching multiple clients/relevance feedback while searching

• Return to common Library

• Multiple thread transfer

• Server-side "include", Macro expansion function

• User profiles

• Geometric graphics

• In-line chemical images

• Multi authoring system/collabration/version control

• PS conversion in base library (HTML -> PS)

• Group annotation

• Representation of multimedia documents, Composite/recursive

• Link semantics

• Dynamic generation of hyperlinks

• Fragment access

• Multiple transfer requests- efficiently

• Interactive extension of HTTP (allow asychronous updates)

• Extensible User Interface/Toolbox

• User controls in documents

• Link names

• Scripting Languages

• Client side ISMAP handling - Bertrand Ibrahim

This could be done by extending the HTML syntax, in particular the "IMG" tag, to include the possibility for the author of a document to easily associate HREF links to different areas of an image, without necessitating access to the HTTP server define a mapping. The syntax could be something like:

<IMG SRC="MyPicture" ALT="..." RECT=(x1,y1,x2,y2) HREF="..." CIRC=(cx,cy,r) HREF="..." ... OTHER HREF="...">

where x1,y1 are the upper left corner coordinates of a rectangle and x2,y2 those of the lower right corner. cx and cy are the coordinates of the center of a circle and r is its radius.

with the possibility of having more than one RECT and/or CIRC field before each HREF field. The last HREF could be preceded by "OTHER" to define the link to follow when the user clicks in an area of the image that doesn't belong to any of the RECT or CIRC areas defined.

• Maintenance of infostructure for growing WWW

Summary:

This was a very lively workshop with more particiption than is indicated by the list given above. (This was due to the fact that some people did not know about the list and others had to leave before they had a chance to put their names on the list. I'll add them in the list if they communicate with me.)

We spent over an hour and half going around the room and soliciting from each participant their priritioes. These priritioes were paraphrased and written on an ordinary blackboard by Robert. At the end of this complete round, we tried to combine some of the priorities and reduce it to a manageable size. This was quickly given up as being infeasible and the list was left in its original form.

At this time, I have no idea as to which participant had mentioned which priority. My role, as a manager of this page, is to give some flesh to this list. I'll do so as I hear from the participant or any one else.