28.06.2013 Views

Papers in PDF format

Papers in PDF format

Papers in PDF format

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Professional Electronic Publish<strong>in</strong>g <strong>in</strong> Hyper-G<br />

The Next Generation Publish<strong>in</strong>g Solution on the Web<br />

Klaus Schmaranz<br />

(Graz University of Technology, Austria<br />

kschmar@iicm.tu-graz.ac.at)<br />

Abstract:<br />

The first part of the paper identifies disadvantages of first generation Web publish<strong>in</strong>g solutions that have to be<br />

overcome for professional publication providers. Us<strong>in</strong>g Hyper-G for distribution of electronic documents opens the way<br />

to the first fully <strong>in</strong>tegrated professional publish<strong>in</strong>g solution on the Web. User and group access rights as well as bill<strong>in</strong>g<br />

mechanisms are <strong>in</strong>tegrated <strong>in</strong> the server, l<strong>in</strong>ks are bidirectional and annotations to exist<strong>in</strong>g documents are possible<br />

without chang<strong>in</strong>g the documents' contents. Hyperl<strong>in</strong>ks are supported <strong>in</strong> arbitrary document types besides hypertext<br />

which opens the way to new publish<strong>in</strong>g paradigms beyond the paper based approach. Naturally a rich set of structure<br />

and search mechanisms is provided. On this basis a set of tools has been developed that supports electronic referee<strong>in</strong>g,<br />

automatic hyperl<strong>in</strong>k creation, glossary l<strong>in</strong>ks and table of contents generation nearly fully automatically. All the data<br />

prepared on a Hyper-G server can then simply be exported to CD-ROM without any additional effort which allows<br />

hybrid Web/CD-ROM publications.<br />

1 Motivation<br />

Electronic publish<strong>in</strong>g is today one of the boom<strong>in</strong>g branches on the Web. Web surfers will f<strong>in</strong>d lots of electronic<br />

paperware on their ride through the servers. However most of the Web sites that serve electronic publications are run by<br />

universities and only a few are operated by publish<strong>in</strong>g companies on an evaluation basis free of charge.<br />

Hav<strong>in</strong>g a closer look at the way electronic publish<strong>in</strong>g is done today one will mostly f<strong>in</strong>d HTML or <strong>PDF</strong> documents that<br />

are very similar to their paper based counterparts. Often a search eng<strong>in</strong>e is provided to make location of <strong>in</strong>terest<strong>in</strong>g<br />

papers easier, all other benefits of do<strong>in</strong>g publish<strong>in</strong>g electronically are mostly neglected. For the reader of electronic<br />

publications nearly no value is added compared to paper based articles. Worse than that - consider<strong>in</strong>g HTML documents<br />

the possibility to do high quality pr<strong>in</strong>touts for archival purposes is lost. This is surely not enough to make electronic<br />

publish<strong>in</strong>g on the Web a success.<br />

Distribut<strong>in</strong>g electronic documents on the Web is considered to be cheaper than publish<strong>in</strong>g on paper [see Odlyzko 95],<br />

additionally turnaround time from submission of an article to the f<strong>in</strong>al published version is considered to be<br />

significantly shorter than for paper based publications. As experience with J.UCS [see Section 5] shows, this is certa<strong>in</strong>ly<br />

not true for high quality publications that are refereed. In this case referee<strong>in</strong>g, corrections by the authors and<br />

resubmission are the most time consum<strong>in</strong>g parts of document preparation. Once the paper is ready for publication<br />

hyperl<strong>in</strong>ks have to be <strong>in</strong>serted <strong>in</strong> the electronic version, which is <strong>in</strong> first generation systems still done by hand because<br />

appropriate tools are miss<strong>in</strong>g. Both referee<strong>in</strong>g and hyperl<strong>in</strong>k creation can be speeded up when us<strong>in</strong>g the right tools as<br />

can be seen later.<br />

Hyperl<strong>in</strong>ks <strong>in</strong> first generation Web systems are represented by URLs (Uniform Resource Locators) [see Berners-Lee 94]<br />

that are unidirectional and embedded <strong>in</strong> documents. This approach implies that l<strong>in</strong>ks can easily po<strong>in</strong>t to nowhere (the<br />

``this document has disappeared syndrome''). Us<strong>in</strong>g URNs (Uniform Resource Names) <strong>in</strong>stead of URLs is the solution<br />

to this problem. URNs do not longer po<strong>in</strong>t to the physical location of a document on a server but add another level of<br />

<strong>in</strong>direction by def<strong>in</strong><strong>in</strong>g unique location <strong>in</strong>dependent names for documents.<br />

Embedd<strong>in</strong>g hyperl<strong>in</strong>ks <strong>in</strong> documents has the disadvantage that only document <strong>format</strong>s designed to be hyperl<strong>in</strong>kable<br />

allow navigation through cyberspace as is the case with HTML. Unfortunately a lot of <strong>format</strong>s used for different<br />

document types were designed long before anybody knew about the Web. This <strong>in</strong>cludes all image <strong>format</strong>s like TIFF,<br />

GIF, JPEG, [see Murray 94], it also <strong>in</strong>cludes all video <strong>format</strong>s such as MPEG as well as one of the most widespread<br />

<strong>format</strong>s for professional publish<strong>in</strong>g: PostScript [see Adobe 90]. The way out of this dilemma is to have a separate l<strong>in</strong>k<br />

database and consider l<strong>in</strong>ks to be overlays. This automatically makes all document <strong>format</strong>s hyperl<strong>in</strong>kable because<br />

documents and l<strong>in</strong>ks are handled separately.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!