DOCSLIB.ORG

Storing Hytime Documents in an Object-Oriented Database

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Storing Hytime Documents in an Object-Oriented Database app eared in: Pro c. of the 3rd International Conference on Information and Knowledge Management (CIKM) '94, Maryland, MD, 1994.1 Storing HyTime Do cuments in an Ob ject-Oriented Database Klemens Bohm, Karl Ab erer GMD-IPSI Dolivostrae 15, 64293 Darmstadt Germany fkb o ehm, ab [email protected] Using examples Abstract from the area of This article is about so hypertext hypertext modelling. yp ermedia-do cument storage system has to meet An op en h should ease un- ts that are not satis ed by existing systems: it requiremen derstanding. 1 has to supp ort non-generic hyp ermedia do cumenttyp es , i.e. do cumenttyp es enriched with application -sp eci c se- mantics. It has to provide hyp ermedia-do cument access Figure 1: Sample Structure in an Argumentation Space metho ds. Finally, it has to allow the exchange of hyp erme- dia do cuments with other systems. On a technical level, an ob ject-oriented database-management system, on a logical sophisticated. Usually systems for hyp ertext-do cumenthan- level, a well established ISO standard, namely HyTime, is dling consist of three layers, a storage layer,an application used to satisfy the requirements mentioned ab ove. By means layer and a presentation layer [DeS86 ]: hyp erengines are the of the example of do cuments incorp orating hyp ertext struc- middle layer. With some hyp erengines, the storage layer is tures we discuss the impact of taking such an approachon made up with databases [ScS90 , MaS92 ]. With other ones, representation and pro cessing within the database system. this is not the case [SSS93 ]. 1 Intro duction In hyp ertext-do cuments of di erenttyp es the hyp erob- jects have sp ecial semantics in addition to the canonical fea- In the recent past the proliferation of the hyp ertext para- tures. In [SHT89] four spaces corresp onding to the di er- digm for representation of information has b een facilitated ent design activities within an authoring pro cess are identi- by technological advances. The main di erence b etween ed: the content space,the planning space, the argumen- conventional do cuments and hyp ertext do cuments is that tation space and the rhetorical space. These spaces are in the rst case the do cument structure as p erceived bythe part of SEPIA, a co op erativehyp ermedia authoring envi- reader is linear. In the second case, there is a graph struc- ronmentdevelop ed at our institute [Str+92]. An argumen- ture. To apply the hyp ertext paradigm hyperengines have tation space inter alia contains facts (`datum') and asser- b een develop ed. Hyp erengines administer the hyp ertext- tions (`claim'). There are not only di erentnodetyp es, but 2 sp eci c structures such as no des, links and anchors which also di erentlinktyp es: a so-link is a directed binary link will b e referred to as hyperobjects. They contain the realiza- from a datum to a claim. Figure 1 contains an example of a tion of generic op erations. An example for a no de op eration so-link. Other link typ es in the argumentation space are the is the calculation of the transitive closure, i.e. the identi ca- to-link and the contradicts-lin k. A contradicts- contributes tion of all no des in a do cument that can b e reached by link link links two no des with discrepantcontent. In the other traversal from that no de. Hyp erengines di er in the internal spaces the hyp erob ject's semantics likewise is sp ecial. In the representation of the hyp erob jects. Furthermore, op erations sequel we will refer to an argumentation-space structure, i.e. re ecting the hyp erob jects' semantics maybemoreorless ahyp ertext structure whose comp onents are claims, so-links 1 etc. as an argumentation-spacedocument. In our terminology,withhyp ermedia do cuments the content of the no des maybemultimedia data as opp osed to hyp ertext do cuments. In existing systems hyp erob jects' do cument-typ e-sp eci c 2 The edges of such a kind of graph structure are called links. Links semantics tends to b e hardco ded in the presentation layer. do not necessarily link no des in their entirety, but also structures Hence, exchanging hyp erdo cuments of non-generic typ es, within no des as, say, several words or sentences. The link ends are e.g. argumentation-space do cuments b etween hyp erengines called anchors [Con87]. or applying a hyp erengine in di erent contexts is not yet conceivable. We for our part envisage a hyp erengine sup- p orting hyp erob jects with partly sp ecial semantics based on a database system. Wewant to comply to a format for hy- p erdo cuments satisfying the following basic requirements: non-genericity, orientation towards hyp ermedia do cument storage and pro cessing, acknowledgement asan(interna- tional) standard. Hence, wehavechosen SGML/HyTime. document The problems we approach and solutions we give are fairly orthogonal to the particular format chosen. title abstract intro hytime ... With SGML (`Standard Generalized Markup Language') ... [ISO86, Her94] do cumenttyp es can b e de ned. In essence, authorlist affiliation title paragraph on paragraph on cument-type de nitions (DTDs) are attributed gram- SGML do ... hyperengines argumentation t structure. However, nothing mars sp ecifying the do cumen ... spaces author1 tics of do cument comp onents, which is said ab out the seman author2 ... ... ... are called elements in the SGML context. The HyTime Standard (`Hyp ermedia/Time-based Do cument Structuring Language') [ISO92, NKN91] basically is a list of SGML Figure 2: Tree Structure Corresp onding to this Do cument element-typ e de nitions for, say, links or presentation sched- ules. These elementtyp es are referred to as architectural forms. Their semantics is xed by the standard. - In this <!ELEMENT asdoc (node|so|contra|contrib)*> article we fo cus on the basic link features the HyTime stan- -- `asdoc' short for `argumentation-space dard provides. This facilitates a comparison of our concepts document', contra' is GI of 'contradicts-link', to conventional approaches to hyp erdo cument storage. We 'contrib' is GI of 'contributes_to-link' are, however, not aware of any related work on this topic (def.s omitted) -- dealing with di erenthyp ertext-do cumenttyp es. <!ELEMENT node CDATA> <!ATTLIST node id ID #REQUIRED In this article we describ e the database application frame- type (position|claim|datum) work for HyTime-do cument storage we are currently work- #REQUIRED> ing on. We concentrate on the following asp ects. <!ELEMENT so EMPTY> <!ATTLIST so claim IDREF #REQUIRED 1. In [ISO92, Ko e+93 ] it has b een mentioned that Hy- datum IDREF #REQUIRED> Time pro cessing can b e accelerated by means of an ... internal representation. Our ob jectiveistodevelop hyp ermedia-sp eci c index structures to sp eed up ac- cess op erations. We will explain that having more than Figure 3: Fragment of an SGML Do cumentTyp e De nition one internal representation of HyTime-architectural forms' for Argumentation-Space Do cuments instances to cho ose from maybeadvantageous. 2. We do not restrict ourselves to a set of xed hyp ertext the list of a no de's children the content of the element.In- structures: dynamic mo di cations of SGML/HyTime ternal no des are nonterminal elements. All elements have do cuments shall b e doable. With our approachboth atyp e, e.g. section or paragraph. With SGML the logi- the collection of do cuments and the set of do cument cal structure of do cuments of a certain typ e can b e de ned. typ es can b e mo di ed at runtime. In essence the content model of an element type is a reg- 3. Op erations are part of the database application : In ular expression sp ecifying how the contentofanelement other words, the database has the semantic control of that typ e may lo ok like. An element-typ e name is also over do cument comp onents. called generic identi er (GI). The element-typ e de nitions in a DTD may b e completed by the de nition of attributes. The platform on which realization will b e based is an ob ject-oriented database-management system (OODBMS) - Figure 3 contains a p ossible DTD for argumentation- the OODBMS VODAK develop ed at our institute [Kla+93 , space do cuments. Lines starting with `<!ELEMENT'intro duce KAN93]. By using a DBMS database features such as con- an elementtyp e together with its content mo del: instances currency control or querying capabiliti es are available. Even of asdoc contain a list whose elements are either instances though we limit ourselves to the description of the HyTime of elementtyp e node, so etc. CDATA is a terminal element hyp erlink features other facets of hyp ermedia do cuments re- typ e more or less comparable to the data typ e STRING. ected in HyTime, like spatial and temp oral relationship s, `<!ATTLIST' indicates the b eginning of attribute de nitions. can b e approached in the same way. For instance, elements of typ e node have an attribute of typ e ID and an attribute type of typ e (positionjclaimjdatum). The structure of this article is the following: the next Attributes of typ e ID are unique identi ers of the element section is an overview of the HyTime conception together they b elong to. An attribute of typ e IDREF is an ID refer- with examples from the hyp ertext area. In Section 4, our ence, one of typ e IDREFS a list of ID references.
Load more

Recommended publications
  • SGML As a Framework for Digital Preservation and Access. INSTITUTION Commission on Preservation and Access, Washington, DC
    DOCUMENT RESUME ED 417 748 IR 056 976 AUTHOR Coleman, James; Willis, Don TITLE SGML as a Framework for Digital Preservation and Access. INSTITUTION Commission on Preservation and Access, Washington, DC. ISBN ISBN-1-887334-54-8 PUB DATE 1997-07-00 NOTE 55p. AVAILABLE FROM Commission on Preservation and Access, A Program of the Council on Library and Information Resources, 1400 16th Street, NW, Suite 740, Washington, DC 20036-2217 ($20). PUB TYPE Reports Evaluative (142) EDRS PRICE MF01/PC03 Plus Postage. DESCRIPTORS *Access to Information; Computer Oriented Programs; *Electronic Libraries; *Information Retrieval; Library Automation; Online Catalogs; *Preservation; Standards IDENTIFIERS Digital Technology; *SGML ABSTRACT This report explores the suitability of Standard Generalized Markup Language (SGML) as a framework for building, managing, and providing access to digital libraries, with special emphasis on preservation and access issues. SGML is an international standard (ISO 8879) designed to promote text interchange. It is used to define markup languages, which can then encode the logical structure and content of any so-defined document. The connection between SGML and the traditional concerns of preservation and access may not be immediately apparent, but the use of descriptive markup tools such as SGML is crucial to the quality and long-term accessibility of digitized materials. Beginning with a general exploration of digital formats for preservation and access, the report provides a staged technical tutorial on the features and uses of SGML. The tutorial covers SGML and related standards, SGML Document Type Definitions in current use, and related projects now under development. A tiered metadata model is described that could incorporate SGML along with other standards to facilitate discovery and retrieval of digital documents.
    [Show full text]
  • The Impact of XML on Library Procedures and Services
    The impact of XML on library procedures and services Eric van Herwijnen January 16, 2000 CERN, Geneva, Switzerland Contents 16/01/2000 1. Introduction open-2000-067 2. XML and its family 3. XML as the lingua franca for electronic document delivery 4. XML as a general purpose exchange language 5. XML as a language for describing data 6. Conclusions Notes Introduction In recent years, digital technologies such as the World Wide Web have revolutionized the way that libraries are used and organized. For example, in the High Energy Physics world, the omnipresence of the TeX text processing system and the availability of the Internet have achieved that all preprints are now electronically distributed and retrieved via the Internet. This development took both publishers and libraries by surprise. Now that the distribution of information is being taken care of by the HEP community, scientific publishers are forcing themselves out of this market by continuing to increase their journal prices. The organization of peer review is the only role left for the publisher and even this role could soon be taken away from them. Paul Ginsparg already claimed in 1994 that "certain physics journals currently play NO role whatsoever for physicists. Their primary role seems to be to provide a revenue stream to publishers, a revenue stream invisibly siphoned from overhead on research contracts through library systems..." If there are no more printed journals to store on shelves, the role of the library in the preprint publication process also becomes less clear. Since preprints are stored in full-text form, servers offer very good search capabilities, as good as those of a conventional library.
    [Show full text]
  • Framework for a Music Markup Language Jacques Steyn Consultant PO Box 14097 Hatfield 0028 South Africa +27 72 129 4740 [email protected]
    Framework for a music markup language Jacques Steyn Consultant PO Box 14097 Hatfield 0028 South Africa +27 72 129 4740 [email protected] ABSTRACT Montgomery), FlowML (Bert Schiettecatte), MusicML (Jeroen van Rotterdam), MusiXML (Gerd Castan), and Objects and processes of music that would be marked with MusicXML (Michael Good), all of which focus on subsets a markup language need to be demarcated before a markup of CWN. ChordML (Gustavo Frederico) focuses on simple language can be designed. This paper investigates issues to lyrics and chords of music. MML (Jacques Steyn) is the be considered for the design of an XML-based general only known attempt to address music objects and events in music markup language. Most present efforts focus on general. CWN (Common Western Notation), yet that system addresses only a fraction of the domain of music. It is In this paper I will investigate the possible scope of music argued that a general music markup language should objects and processes that need to be considered for a consider more than just CWN. A framework for such a comprehensive or general music markup language that is comprehensive general music markup language is XML-based. To begin with, I propose the following basic proposed. Such a general markup language should consist requirements for such a general music markup language. of modules that could be appended to core modules on a 2 REQUIREMENTS FOR A MUSIC MARKUP needs basis. LANGUAGE Keywords A general music markup language should Music Markup Language, music modules, music processes, S music objects, XML conform to XML requirements as published by the W3C 1 INTRODUCTION S use common English music terminology for The use of markup languages exploded after the element and attribute names introduction of the World Wide Web, particularly HTML, S which is a very simple application of SGML (Standard address intrinsic as well as extrinsic music objects General Markup Language).
    [Show full text]
  • (V1) - Text Processing: Office and Publishing Systems Interface
    Committee: (V1) - Text Processing: Office and Publishing Systems Interface National Designation Title (Click here to purchase standards) ISO/IEC Document V1 :[] Information technology - Document Container File -- Part 1: Core CD 21340-1 :[] Information technology - Extensions of Office Open XML File Formats - Part 1: CD 30114-1 Guidelines :[] Information technology - Extensions of Office Open XML - Part 2: Character CD 30114-2 Repertoire Checking INCITS/ISO 8879:1986:[R2009] Information Processing - Text and Office Systems - Standard Generalized Markup IS 8879:1986 INCITS/ISO/IEC 8879:1986/AM Information Processing - Text and Office Systems - Standard Generalized Markup IS 8879:1986/AM1:1988 1:1988:[2010] Language (SGML) - Amendment 1 INCITS/ISO/IEC 8879:1986/COR Information Processing - Text and Office Systems - Standard Generalized Markup IS 8879:1986/COR 1:1996 1:1996:[2010] Language (SGML) TECHNICAL CORRIGENDUM 1 INCITS/ISO/IEC 8879:1986/COR Information Processing - Text and Office Systems - Standard Generalized Markup IS 8879:1986/COR 2:1999 2:1999:[2010] Language (SGML) TECHNICAL CORRIGENDUM 2 INCITS 207-:1991[S2012] Alternate Keyboard Arrangement for Alphanumeric Machines N/A Created: 11/16/2014 Page 1 of 11 Committee: (V1) - Text Processing: Office and Publishing Systems Interface National Designation Title (Click here to purchase standards) ISO/IEC Document INCITS/ISO/IEC 9541-2:2012:[2013] Information technology - Font information interchange - Part 2: Interchange format IS 9541-2:2012 INCITS/ISO/IEC 9541-3:2013:[2013] Information
    [Show full text]
  • Proceedings of the Hypertext Standardization Workshop January 16-18, 1990 National Institute of Standards and Technology
    NIST Special Publication 500-178 A111Q3 3fiTSbfl . v^uiripuc^r Systems Proceedings of the Hypertext Technology Standardization Workshop U.S. DEPARTMENT OF COMMERCE January 16-18, 1990 National Institute of Standards and National Institute of Standards Technology and Technology Nisr Judi Moline NIST * Dan Benigni PUBLICATIONS Jean Baronas NATIONAL INSTrrUTE OF STANDARDS & TECHNOLOGY Reseso'di Mormatkm Center Gakhersburg, MD 20899 DATE DUE . _ r Demco, Inc. 38-.293 NIST Special Publication 500-178 Proceedings of the Hypertext Standardization Workshop January 16-18, 1990 National Institute of Standards and Technology Judi Moline, Dan Benigni, and Jean Baronas, Editors Hypertext Competence Project National Computer Systems Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899 March 1990 U.S. DEPARTMENT OF COMMERCE Robert A. Mosbacher, Secretary NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director Reports on Computer Systems Technology The National Institute of Standards and Technology (NiST) (formerly the National Bureau of Standards) has a unique responsibility for computer systems technology within the Federal government. NIST's National Computer Systems Laboratory (NCSL) develops standards and guidelines, provides technical assistance, and conducts research for computers and related telecommunications systems to achieve more effective utilization of Federal information technology resources. NCSL's responsibilities include development of technical, management, physical, and administrative standards and guidelines for the cost-effective security and privacy of sensitive unclassified information processed in Federal computers. NCSL assists agencies in developing security plans and in improving computer security awareness train- ing. This Special Publication 500 series reports NCSL research and guidelines to Federal agencies as well as to organizations in industry, government, and academia.
    [Show full text]
  • XML and Applications 2014/2015 Lecture 12 – 19.01.2015 Standards for Inter-Document Relations
    Some more XML applications and XML-related standards (XLink, XPointer, XForms) Patryk Czarnik XML and Applications 2014/2015 Lecture 12 – 19.01.2015 Standards for inter-document relations XPointer – addressing documents and their fragments XInclude – logical inclusion of documents within other documents XLink – declarative relations between documents and their fragments 2 / 22 XPointer The standard defines addressing XML documents and their fragments using standard URI syntax: http://www.sejm.gov.pl/ustawa.xml#def-las 3 W3C recommendations dated 2002-2003: XPointer Framework http://www.w3.org/TR/xptr-framework/ XPointer element() Scheme http://www.w3.org/TR/xptr-element/ XPointer xmlns() Scheme http://www.w3.org/TR/xptr-xmlns/ XPointer xpointer() Scheme http://www.w3.org/TR/xptr-xpointer/ (neverending?) Working Draft 3 / 22 XPointer – xpointer scheme xpointer scheme allows to address elements using XPath: http://www.sejm.gov.pl/ustawa.xml#xpointer(/art[5]/par[2]) xmlns scheme adds namespace declarations to the above: ustawa.xml#xmlns(pr=http://www.sejm.gov.pl/prawo) xpointer(/pr:art[5]/pr:par[2]) 4 / 22 XPointer – element scheme Element carrying ID attribute with given value: document.xml#element(def-las) Element with given position (absolute or relative to element carrying ID with given value): document.xml#element(/1/4/3) document.xml#element(def-las/2/3) Short syntax: document.xml#def-las document.xml#/1/4/3 document.xml#def-las/2/3 5 / 22 XInclude Including external XML documents (or their fragments) in another XML document. Similar to entities, but: normal element markup, no special syntax, no need to declare anything in DTD, nor to have DTD at all Main capabilities: including complete documents (identified by URL) or their fragments (pointed by XPointer) including XML tree (default) or raw text defining content to be used in case of an error Supported by many parsers, including Java (JAXP).
    [Show full text]
  • NEDLIB Glossary
    NEDLIB Glossary Authors: José Luis Borbinha, National Library of Portugal Fernando Cardoso, National Library of Portugal Nuno Freire, INESC Date of Issue: 22 February 2000 Issue: 1.0web Total Number of Pages: 46 NEDLIB Glossary TABLE OF CONTENTS TABLE OF CONTENTS...............................................................................................................................................................................i Abstract ................................................................................................................................................................................................2 Keywords..............................................................................................................................................................................................2 1. Concepts ..................................................................................................................................................................................................2 1.1 Index of Terms ............................................................................................................................................................................2 1.2 Terms Relationship ....................................................................................................................................................................6 1.3 Glossary ....................................................................................................................................................................................13
    [Show full text]
  • Does the World Need More XML Standards? Francis Cave Chair, ISO/IEC JTC 1/SC 34 Document Description and Processing Languages ISO/… What?
    Does the world need more XML standards? Francis Cave Chair, ISO/IEC JTC 1/SC 34 Document description and processing languages ISO/… what? ISO International Organization for Standardization IEC International Electrotechnical Commission ISO/IEC JTC 1 The one (and only) Joint Technical Committee of ISO and IEC Formed in 1987 by the merger of separate ISO and IEC Technical Committees, to collaborate on ICT standardization ISO/IEC JTC 1/SC 34 A Sub-committee of JTC 1 Document Description and Processing Languages It all started fifty years ago… 1967 Early ideas on separation of document content from document format (William W. Tunnicliffe, Graphical Communications Association) 1969 Goldfarb, Mosher and Laurie invent GML at IBM 1971 GCA established the “System X” committee under Tunnicliffe, which eventually led to the development of GenCode® 1973 Initial release of GML as an IBM product 1978 IBM published the DCF GML User’s Guide, written by Goldfarb, which became the basis of the first working paper submitted for standardization of what would become SGML History of SC 34: https://jtc1historyblog.wordpress.com/sc-34/ 1980s: SGML becomes ISO 8879 1982 International STM Group hosted the first conference on SGML in Amsterdam; Goldfarb and the ANSI SGML committee sought European support for the development of SGML as an International Standard 1983 GCA publish Standard 101-1983 GenCode and the Standard Generalized Markup Language 1984 SGML submitted to ISO; an international Working Group was formed to work on drafting, convened initially
    [Show full text]
  • Three SGML Metadata Formats: TEI, EAD, and CIMI
    Three SGML metadata formats: TEI, EAD, and CIMI A Study for BIBLINK Work Package 1.1 December 1996 Lou Burnard and Richard Light BIBLINK study of SGML metadata formats Page 1 Prefatory Note BIBLINK Work Package 1 (Study of Metadata) is intended to identify, describe, and compare current approaches to the encoding of metadata, with a view to making recommendations. Amongst the many different approaches currently in use, those based on the Standard Generalized Markup Lamguage (SGML: ISO 8879) appear to offer the widest range of features and the broadest potential for cross-sector applicability. This additional detailed study on three SGML-based formats was therefore commissioned to supplement the survey reported on in Work Package 1. This report consists of a brief overview of each of the three schemes studied, some general discussion of the technical aspects of using SGML in a production environment, and a detailed feature by feature comparison of the three schemes with respect to a number of key attributes identified by the Biblink project. A bibliography with pointers to further reading on each of the three schemes is also provided. Richard Light was responsible for the original draft of the report, and for the information on CIMI and EAD. Lou Burnard was responsible for final editing of the report and for the information on TEI and SGML. Thanks are due to John Perkins, Daniel Pitti, and Rachel Heery for helpful suggestions during the preparation of the report. 1 Introduction 2 2 Overview of the schemes studied 2 2.1 The Text Encoding
    [Show full text]
  • Portable Documents: Problems and (Partial) Solutions
    ELECTRONIC PUBLISHING, VOL. 8(4), 343±367 (MARCH 1996) Portable documents: problems and (partial) solutions DAVID W. BARRON Department of Electronics and Computer Science University of Southampton Southampton SO17 1BJ UK SUMMARY The paper presents a wide-ranging survey of the issues that arise in producing portable doc- uments, including multimedia and hypermedia documents. It is directed at practitioners, and the approach is therefore pragmatic, based on the current state of the art; the paper does not attempt to provide a comprehensive survey of all previous work on this topic. The nature of an electronic document is discussed,and the various kinds of portability that may be required are de®ned. Ways in which portability can be achieved in a variety of restricted contexts are presented,including approachesto portability based on international and de facto industry stan- dards. The likely success of the competing standards is assessed. Finally the paper addresses the question of whether complete document portability is achievable, or even necessary. KEY WORDS Portability, SGML, Standards, OpenDoc, ODA, HyTime 1 INTRODUCTION Corporate information is increasingly viewed, shared, distributed and managed electroni- cally ± a recent estimate [1] suggests that eighty percent of all corporate information today exists in digital form. Commercial publishers are moving towards CD-ROM as an alter- native to paper, especially for reference and entertainment publications, and the `digital library' is foreshadowed by the emergence of electronic versions of scienti®c journals and research papers. This move towards electronic documents highlights the need for portabil- ity of such documents over disparate hardware and software platforms, if the maximum bene®t is to be obtained from this new technology.
    [Show full text]
  • Adaptable Hypermedia with Web Standards and Tools Page 1 of 8
    Adaptable Hypermedia with Web Standards and Tools Page 1 of 8 active web home || papers || posters Adaptable Hypermedia with Web Standards and Tools Lloyd Rutledge, Lynda Hardman, Jacco van Ossenbruggen and Dick C.A. Bulterman CWI P.O. Box 94079 1090 GB Amsterdam, The Netherlands E-mail: {lloyd,lynda,jrvosse,dcab}@cwi.nl The World Wide Web offers the promise, and more and more the reality, of a widely distributed and widely accessible digital library of related hypermedia data. In order for this data to be stored, accessed and played it should not be encoded as final form presentations, since these consume storage space and cannot easily be adapted to variations in presentation-time circumstances such as user characteristics, changes in end-user technology and the interactions of the user at presentation time. Instead, a more presentation independent approach needs to be taken that allows the dynamic generation of presentations that are derived from a presentation-independent description and are adapted to run-time circumstances. A collection of standards exists that address this possibility and its related challenges. The ISO standard HyTime (Hypermedia/Time-based Structuring Language) [10] specifies the representation of hypermedia documents in a presentation independent format. HyTime is used to a small but steady degree by private industry for large-scale text document collections. The widespread adoption of HyTime is inhibited because there are few widely available tools for processing it, there are few examples of its use, and few widely available systems exist that can generate hypermedia presentations from it. The ISO standard DSSSL (Document Style Semantics and Specification Language) [11] defines the transformation of electronic documents into formats that present them.
    [Show full text]
  • Session 2: Markup Language Technologies
    XML for Java Developers G22.3033-002 Session 2 - Main Theme Markup Language Technologies (Part II) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda Q Summary of Previous Session Q Errata: <pages> tag, XML 2.0, XML Applications !? Q History and Current State of XML Standards Q Advanced Applications of XML Q XML’s eXtensible Style Language (XSL) Q Character Encodings and Text Processing Q XML and DBMSs Q Course Approach ... Q XML Application Development Q XML References and Class Project Q Readings Q Assignment #1a (reminder?) 2 Q Assignment #1b (1 week) 1 Summary of Previous Session Q XML Generics Q Course Logistics, Structure and Objectives Q History of Meta-Markup Languages Q XML Applications: Markup Languages Q XML Information Modeling Applications Q XML-Based Architectures Q XML and Java Q XML Development Tools Q Summary Q Class Project Q Readings Q Assignment #1a 3 Old History Q Formatting Markups Q Rendition notations (e.g., LaTeX, TeX, RTF, MIF) Q Compatible with standard text editors Q Processed into presentations (printout, or electronic display) Q WYSIWYG Q What You See Is “ALL” You Get Q Meta-Markup Language Q GML (Goldfarb, Mosher, Lorie - IBM 1969) Q Generalized (i.e., indep. of systems, devices, applications) Q Markups (i.e., information related to struct. & content Q Language (i.e., methodology with formal syntax) Q Validation capabilities (1974) 4 2 SGML Q SGML (1978 - 10/15/86) Q Used by DoD for Continuous Acquisition and Lifecycle Support (CALS) Q http://www.oasis-open.org/cover/general.html Q SGML DTD or Schema <!DOCTYPE tutorials [ <!ELEMENT tutorials – (tutorial+)> <!ELEMENT tutorial – (title, intro, chap+)> <!ELEMENT title – O (#PCDATA)> <!ELEMENT intro – O (para+)> <!ELEMENT chap – O (title, para+)> <!ELEMENT para – O (#PCDATA)> ]> 5 SGML Markup <tutorials> <tutorial> <title>XML TUTORIAL <intro> <para>Required first paragraph of intro.
    [Show full text]