ACM Home Page
Please provide us with feedback. Feedback
Using SVG as the rendering model for structured and graphically complex web material
Full text PdfPdf (124 KB)
Source Document Engineering archive
Proceedings of the 2003 ACM symposium on Document engineering table of contents
Grenoble, France
SESSION: Document formatting table of contents
Pages: 88 - 91  
Year of Publication: 2003
ISBN:1-58113-724-9
Authors
Julius C. Mong  University of Nottingham, Nottingham, UK
David F. Brailsford  University of Nottingham, Nottingham, UK
Sponsors
SIGWEB: ACM Special Interest Group on Hypertext, Hypermedia, and Web
SIGIR: ACM Special Interest Group on Information Retrieval
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 1,   Downloads (12 Months): 39,   Citation Count: 4
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/958220.958236
What is a DOI?

ABSTRACT

This paper reports some experiments in using SVG (Scalable Vector Graphics), rather than the browser default of (X)HTML/CSS, as a potential Web-based rendering technology, in an attempt to create an approach that integrates the structural and display aspects of a Web document in a single XML-compliant envelope.Although the syntax of SVG is XML based, the semantics of the primitive graphic operations more closely resemble those of page description languages such as PostScript or PDF. The principal usage of SVG, so far, is for inserting complex graphic material into Web pages that are predominantly controlled via (X)HTML and CSS.The conversion of structured and unstructured PDF into SVG is discussed. It is found that unstructured PDF converts into pages of SVG with few problems, but difficulties arise when one attempts to map the structural components of a Tagged PDF into an XML skeleton underlying the corresponding SVG. These difficulties are not fundamentally syntactic; they arise largely because browsers are innately bound to (X)HTML/CSS as their default rendering model. Some suggestions are made for ways in which SVG could be more totally integrated into browser functionality, with the possibility that future browsers might be able to use SVG as their default rendering paradigm.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
W3C Working Draft of Scalable Vector Graphics 1.2 http://www.w3.org/TR/SVG12/
 
2
Tagged PDF - Standard Structure Types PDF Reference (Third Edition) version 1.4 (Chapter 9.7.4), Adobe Systems Incorporated, ISBN 0-201-75839-3, Addison-Wesley, December 2001.
 
3
W3C SVG Test Suite http://www.w3.org/Graphics/SVG/Test/
 
4
Mobile SVG Profiles: SVG Tiny and SVG Basic W3C Recommendations 14 January 2003 http://www.w3.org/TR/SVGMobile/
 
5
SVG 1.2 - Multiple Pages http://www.w3.org/TR/SVG12/#multipage


Collaborative Colleagues:
Julius C. Mong: colleagues
David F. Brailsford: colleagues

Peer to Peer - Readers of this Article have also read: