DOCSLIB.ORG

Lecture 4 Creating Markups with XML and CSS

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Lecture 4 Creating Markups with XML and CSS References: Parsing and Querying XML Documents in SML ,Ch1 Creating Markup with XML,Ch5 in XML how to program Cascading Style Sheets (CSS), ch4 in XML how to program Originality of XML a W3C standard to complement HTML origins: structured text SGML motivation: HTML describes presentation XML describes contents HTML4.0∈ XML ⊂ SGML http://www.w3.org/TR/2000/REC-xml-20001006 (version 2, 10/2000) 7 Steps to XML Mastery 1. Read before you write --- RSS, SVG 2. Display for the Web --- CSS, XHTML 3. Transform with XSLT --- XPATH, XSLT 4. Apply parsing power --- SAX, DOM 5. Add web services --- UDDI, SOAP 6. Employ the semantic web --- RDF, OWL 7. Ensure XML security --- XML encryption HTML <h1> Bibliography </h1> <p> <i> Foundations of Databases </i> Abiteboul, Hull, Vianu <br> Addison Wesley, 1995 <p> <i> Data on the Web </i> Abiteoul, Buneman, Suciu <br> Morgan Kaufmann, 1999 HTML describes the presentation XML <bibliography> <book> <title> Foundations… </title> <author> Abiteboul </author> <author> Hull </author> <author> Vianu </author> <publisher> Addison Wesley </publisher> <year> 1995 </year> </book> … </bibliography> XML describes the contents XML Terminology tags: book, title, author, … start tag: <book>, end tag: </book> elements: <book>…<book>,<author>…</author> elements are nested empty element: <red></red> abbrv. <red/> an XML document: single root element well formed XML document: if it has matching tags XML: Attributes <book price = “55” currency = “USD”> <title> Foundations of Databases </title> <author> Abiteboul </author> … <year> 1995 </year> </book> attributes are alternative ways to represent data XML: Ids and References <person id=“o555”> <name> Jane </name> </person> <person id=“o456”> <name> Mary </name> <children idref=“o123 o555”/> </person> <person id=“o123” mother=“o456”><name>John</name> </person> ids and references in XML are just attributes XML: CDATA Section Syntax: <![CDATA[ .....any text here...]]> Example: <example> <![CDATA[ some text here </notAtag> <>]]> </example> Char. data in a CDATA section is not processed by the parser. XML: Entity References Syntax: &entityname; Example: <element> this is less than &lt; </element> &lt; < Some entities: &gt; > &amp; & &apos; ‘ &quot; “ &#38; Unicode char XML: Processing Instructions Syntax: <?target argument?> Example: <product> <name> Alarm Clock </name> <?ringBell 20?> <price> 19.99 </price> </product> The info. contained in a PI is passed to the application using the XML and provides additional application-specific information about the document. XML: Comments Syntax <!-- .... Comment text... --> Yes, they are part of the data model !! They are not processed by the parser! XML Namespaces (1/2) Resolve naming collisions problem http://www.w3.org/TR/REC-xml-names (1/99) name ::= [prefix:]localpart <book xmlns:isbn=“www.isbn-org.org/def”> <title> … </title> <number> 15 </number> <isbn:number> …. </isbn:number> </book> XML Namespaces (2/2) syntactic: <number> , <isbn:number> semantic: provide URL for schema <tag xmlns:mystyle = “http://…”> … defined here <mystyle:title> … </mystyle:title> <mystyle:number> … </tag> XML What For and How? XML is designed for platform-independent exchange of information over Internet Each element is associated with a content model, which is a regular expression over element type and #PCDATA representing text Processing of XML document Parsing Processing Output generation Programming practice Section 5.9: case study of a day planner application Getting familiar with some parser, such as msxml, Xceres, JAXP, and XML4J Supplements to XML Syntax (1/6) Unicode An extension to ASCII character set Supports all spoken languages A major step forward in the internationalization Documents that use encoding other than UTF-8 or UTF-16 must start with an XML declaration <?xml version=“1.0” encoding=“ISO-8859-1”?> Supplements to XML Syntax (2/6) Entity references The name of entity is between an ampersand character and a semicolon, e.g. &amp; For the application, the entity reference is replaced by the content of the entity &us; ≡ “United States” if the value of us is pre- defined as “United States” &#x; provides a hexadecimal representation of the character set, called character reference <?xml version=“1.0” encoding=“ISO-8859-1”?> Supplements to XML Syntax (3/6) Special Attributes xml:space for those applications that discard duplicate spaces, value is either preserve or default xml:lang is used to indicate the language of the content’s content. For example, <p xml:lang=“en-GB”> … </p> Supplements to XML Syntax (4/6) Processing Instructions (PI) Is a mechanism to insert non-XML statements, such as scripts, in the documents. The processing instruction is enclosed in <? and ?>, the first name is the target. XML declaration is a processing instruction <?xml version=“1.0” encoding=“ISO-8859-1”?> Supplements to XML Syntax (5/6) Processing Instructions (PI) Is a mechanism to insert non-XML statements, such as scripts, in the documents. The processing instruction is enclosed in <? and ?>, the first name is the target. XML declaration is a processing instruction <?xml version=“1.0” encoding=“ISO-8859-1”?> Supplements to XML Syntax (6/6) Four Common Errors Forget end tags XML is case sensitive No space in the name of element Quotes are required for attribute value Cascading Style Sheets (CSS) Reference: XML How to Program, ch4 Rendering XML without HTML HTML browsers know how the title element appears, they need not to be told how to style element. XML has no pre-defined set of elements, it needs to be told how to style each element. Both CSS and XSL-FO solve the rendering problem. CSS describes directly how to render documents onscreen or on paper XSLT stylesheet converts the XML elements into, say, HTML elements for display. XSL-FO enhances the styling function. Style declaration CSS specifies the style of page elements separately from the structure of a document or “separates styling from the page content” or “separation of structure from presentation” Style declaration Inline style Style element in head part External style linking Inline style Inside body section, using style attribute, such as <p style=“font-size:20pt”>this is…</p> <p style=“font-size:20pt; color:#0000ff”> this is… </p> Style element in head section <!DOCTYPE HTML ---> <html> ------ <head> <title>….</title> <style type=“text/css”> em {background-color:#8000ff; color: white} h1 {font-family: arial, san-serif} p {font-size:14pt} .special {color: blue} (for style class) </style> </head> ----------- Type attribute of element Style The type attribute specifies the MIME type of the stylesheet. MIME is a standard for specifying the format of content: text/css, text/html, text/javascript, and image/gif. Regular text style sheets use text/css Font-family property arial sans-serif serif (times new roman, Georgia) cursive (script) fantasy (critter) monospace (courier, fixedsys) Font-size in (inches) cm (centimeters) mm (millimeters) pt (points=1/72 in) pc (picas=12pt) Relative length measure em: the size of the font ex: x-height of the font %: percentage Conflicting styles Precedence Author > user > user agent (browser) Child’s or descendant’s properties have greater specificity than those defined for parent or ancestor elements Inheritance Styles for parent and ancestor elements are inherited by child and descendant elements. External style sheet linking An external style sheet is defined, say styles.css, Including the style sheet file in the head section of a html (xml) document <link rel =“stylesheet” type = “text/css” href = “styles.css”> <?xml-stylesheet href = “styles.css” type = “text/css” ?> The Style Sheet File Selectors CSS rules are associated with elements through sectors. Properties Enclosed in curly brackets { } Each property has a name followed by a : Comments Enclosed in /* and */ Positioning Elements (1/2) CSS introduces the position property and a capability called absolute positioning <p><img src=“i.gif” style=“position: absolute; top: 0px; left: 0px; z-index: 1” alt= “first positioned image”></p> <p style= “position: absolute; top:50px; left:50px; z-index:3; font-size:20pt” > positioned text </p> Positioning Elements (2/2) Z-index value indicates the layer over lapping (bigger number outer layout) If no z-index, later element is displayed in front of those that occur earlier Top, left, right, bottom are relative to its containing block for relative positioning Relative positioning Usually used in superscript, subscript, such as span {color: red; font-size: 6em; height: 1em} .super {position: relative; top: -1ex} Defined in between <style type=“text/css”> and </style> of the head section, one may apply the relative position as: <span class=“super”>****</span> which will result in the text at the end of this sentence is in superscript Background (1/2) <style type=“text/css”> body {background-image: url(logo.gif); background-position: bottom right: background-repeat: no-repeat; background-attachment: fixed;} P {font-size: 18pt; color: #aa5588; text: 1em; font-family: arial, san-serif} .dark {font-weight: bold} </style> </head> <body> <p> <span class=“dark”>……….</span> </p> </body> Backgrounds (2/2) Grouping element: span (inline level element) and div (block level element) Font-style: none, italic, oblique Font-weight: bold, normal, bolder, lighter Background-repeat: repeat, no-repeat, repeat-x,
Recommended publications
  • XML a New Web Site Architecture

    XML a New Web Site Architecture

    XML A New Web Site Architecture Jim Costello Derek Werthmuller Darshana Apte Center for Technology in Government University at Albany, SUNY 1535 Western Avenue Albany, NY 12203 Phone: (518) 442-3892 Fax: (518) 442-3886 E-mail: [email protected] http://www.ctg.albany.edu September 2002 © 2002 Center for Technology in Government The Center grants permission to reprint this document provided this cover page is included. Table of Contents XML: A New Web Site Architecture .......................................................................................................................... 1 A Better Way? ......................................................................................................................................................... 1 Defining the Problem.............................................................................................................................................. 1 Partial Solutions ...................................................................................................................................................... 2 Addressing the Root Problems .............................................................................................................................. 2 Figure 1. Sample XML file (all code simplified for example) ...................................................................... 4 Figure 2. Sample XSL File (all code simplified for example) ....................................................................... 6 Figure 3. Formatted Page Produced
  • XML Signature/Encryption — the Basis of Web Services Security

    XML Signature/Encryption — the Basis of Web Services Security

    Special Issue on Security for Network Society Falsification Prevention and Protection Technologies and Products XML Signature/Encryption — the Basis of Web Services Security By Koji MIYAUCHI* XML is spreading quickly as a format for electronic documents and messages. As a consequence, ABSTRACT greater importance is being placed on the XML security technology. Against this background research and development efforts into XML security are being energetically pursued. This paper discusses the W3C XML Signature and XML Encryption specifications, which represent the fundamental technology of XML security, as well as other related technologies originally developed by NEC. KEYWORDS XML security, XML signature, XML encryption, Distributed signature, Web services security 1. INTRODUCTION 2. XML SIGNATURE XML is an extendible markup language, the speci- 2.1 Overview fication of which has been established by the W3C XML Signature is an electronic signature technol- (WWW Consortium). It is spreading quickly because ogy that is optimized for XML data. The practical of its flexibility and its platform-independent technol- benefits of this technology include Partial Signature, ogy, which freely allows authors to decide on docu- which allows an electronic signature to be written on ment structures. Various XML-based standard for- specific tags contained in XML data, and Multiple mats have been developed including: ebXML and Signature, which enables multiple electronic signa- RosettaNet, which are standard specifications for e- tures to be written. The use of XML Signature can commerce transactions, TravelXML, which is an EDI solve security problems, including falsification, spoof- (Electronic Data Interchange) standard for travel ing, and repudiation. agencies, and NewsML, which is a standard specifica- tion for new distribution formats.
  • XML Information Set

    XML Information Set

    XML Information Set XML Information Set W3C Recommendation 24 October 2001 This version: http://www.w3.org/TR/2001/REC-xml-infoset-20011024 Latest version: http://www.w3.org/TR/xml-infoset Previous version: http://www.w3.org/TR/2001/PR-xml-infoset-20010810 Editors: John Cowan, [email protected] Richard Tobin, [email protected] Copyright ©1999, 2000, 2001 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Abstract This specification provides a set of definitions for use in other specifications that need to refer to the information in an XML document. Status of this Document This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C. This is the W3C Recommendation of the XML Information Set. This document has been reviewed by W3C Members and other interested parties and has been endorsed by the Director as a W3C Recommendation. It is a stable document and may be used as reference material or cited as a normative reference from another document. W3C's role in making the Recommendation is to draw attention to the specification and to promote its widespread deployment. This enhances the functionality and interoperability of the file:///C|/Documents%20and%20Settings/immdca01/Desktop/xml-infoset.html (1 of 16) [8/12/2002 10:38:58 AM] XML Information Set Web. This document has been produced by the W3C XML Core Working Group as part of the XML Activity in the W3C Architecture Domain.
  • XML for Java Developers G22.3033-002 Course Roadmap

    XML for Java Developers G22.3033-002 Course Roadmap

    XML for Java Developers G22.3033-002 Session 1 - Main Theme Markup Language Technologies (Part I) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Course Roadmap Consider the Spectrum of Applications Architectures Distributed vs. Decentralized Apps + Thick vs. Thin Clients J2EE for eCommerce vs. J2EE/Web Services, JXTA, etc. Learn Specific XML/Java “Patterns” Used for Data/Content Presentation, Data Exchange, and Application Configuration Cover XML/Java Technologies According to their Use in the Various Phases of the Application Development Lifecycle (i.e., Discovery, Design, Development, Deployment, Administration) e.g., Modeling, Configuration Management, Processing, Rendering, Querying, Secure Messaging, etc. Develop XML Applications as Assemblies of Reusable XML- Based Services (Applications of XML + Java Applications) 2 1 Agenda XML Generics Course Logistics, Structure and Objectives History of Meta-Markup Languages XML Applications: Markup Languages XML Information Modeling Applications XML-Based Architectures XML and Java XML Development Tools Summary Class Project Readings Assignment #1a 3 Part I Introduction 4 2 XML Generics XML means eXtensible Markup Language XML expresses the structure of information (i.e., document content) separately from its presentation XSL style sheets are used to convert documents to a presentation format that can be processed by a target presentation device (e.g., HTML in the case of legacy browsers) Need a
  • Introduction to XML

    Introduction to XML

    Introduction to XML CS 317/387 Agenda – Introduction to XML 1. What is it? 2. What’s it good for? 3. How does it work? 4. The infrastructure of XML 5. Using XML on the Web 6. Implementation issues & costs 2 1. What is it? Discussion points: First principles: OHCO Example: A simple XML fragment Compare/contrast: SGML, HTML, XHTML A different XML for every community Terminology 3 1 Ordered hierarchies of content objects Premise: A text is the sum of its component parts A <Book> could be defined as containing: <FrontMatter>, <Chapter>s, <BackMatter> <FrontMatter> could contain: <BookTitle> <Author>s <PubInfo> A <Chapter> could contain: <ChapterTitle> <Paragraph>s A <Paragraph> could contain: <Sentence>s or <Table>s or <Figure>s … Components chosen should reflect anticipated use 4 Ordered hierarchies of content objects OHCO is a useful, albeit imperfect, model Exposes an object’s intellectual structure Supports reuse & abstraction of components Better than a bit-mapped page image Better than a model of text as a stream of characters plus formatting instructions Data management system for document-like objects Does not allow overlapping content objects Incomplete; requires infrastructure 5 Content objects in a book Book FrontMatter BookTitle Author(s) PubInfo Chapter(s) ChapterTitle Paragraph(s) BackMatter References Index 6 2 Content objects in a catalog card Card CallNumber MainEntry TitleStatement TitleProper StatementOfResponsibility Imprint SummaryNote AddedEntrySubject(s) Added EntryPersonalName(s) 7 Semistructured Data Another data model, based on trees. Motivation: flexible representation of data. Often, data comes from multiple sources with differences in notation, meaning, etc. Motivation: sharing of documents among systems and databases.
  • Web API Protocol and Security Analysis Web

    Web API Protocol and Security Analysis Web

    EXAMENSARBETE INOM DATATEKNIK, GRUNDNIVÅ, 15 HP STOCKHOLM, SVERIGE 2017 Web API protocol and security analysis Web API protokoll- och säkerhetsanalys CRISTIAN ARAYA MANJINDER SINGH KTH SKOLAN FÖR TEKNIK OCH HÄLSA Web API protocol and security analysis Web API protokoll- och säkerhetsanalys Cristian Araya and Manjinder Singh Degree project in Computer science First level, 15hp Supervisor from KTH: Reine Bergström Examiner: Ibrahim Orhan TRITA-STH 2017:34 KTH The School of Technology and Health 141 52 Flemingsberg, Sweden Abstract There is problem that every company has its own customer portal. This problem can be solved by creating a platform that gathers all customers’ portals in one place. For such platform, it is required a web API protocol that is fast, secure and has capacity for many users. Consequently, a survey of various web API protocols has been made by testing their performance and security. The task was to find out which web API protocol offered high security as well as high performance in terms of response time both at low and high load. This included an investigation of previous work to find out if certain protocols could be ruled out. During the work, the platform’s backend was also developed, which needed to implement chosen web API protocols that would later be tested. The performed tests measured the APIs’ connection time and their response time with and without load. The results were analyzed and showed that the protocols had both pros and cons. Finally, a protocol was chosen that was suitable for the platform because it offered high security and fast connection.
  • Renderx XEP User Guide XEP User Guide

    Renderx XEP User Guide XEP User Guide

    RenderX XEP User Guide XEP User Guide © Copyright 2005-2019 RenderX, Inc. All rights reserved. This documentation contains proprietary information belonging to RenderX, and is provided under a license agreement containing restrictions on use and disclosure. It is also protected by international copyright law. Because of continued product development, the information contained in this document may change without notice.The information and intellectual property contained herein are confidential and remain the exclusive intellectual property of RenderX. If you find any problems in the documentation, please report them to us in writing. RenderX does not warrant that this document is error- free. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means - electronic, mechanical, photocopying, recording or otherwise - without the prior written permission of RenderX. RenderX Telephone: 1 (650) 328-8000 Fax: 1 (650) 328-8008 Website: http://renderx.com Email: [email protected] Table of Contents 1. Preface ................................................................................................................... 9 1.1. What©s in this Document? .............................................................................. 9 1.2. Prerequisites ................................................................................................ 9 1.3. Acronyms ................................................................................................... 10 1.4. Technical Support
  • XSLT Can Be One of the Following Five Types

    XSLT Can Be One of the Following Five Types

    XPath Quick Reference Node Types Nodes can be of the following types: NodeType Name String Value root Concatenation of alI text nodes in the document element Element name Concatenation of alI text nodes descended from the element attribute Attribute name Attribute value text Text cornrnent Text held within the comment processing Processing Text in the processing instruction after the space after the instruction target targetname narnespace Namespace prefix Namespace URI Object Types Values in XSLT can be one of the following five types: Object Type Description boolean true or false number A floating-point number: a double-precision 64-bit format IEEE 754 value Table continued on following page Appendix A Object Type Description string A sequence of XML characters node set An unordered collection of nodes result tree fragment The root node of a generated node tree The various object types can be converted to each other by the following rules. Object Boolean Number String boolean 1 if the boolean is , true' if the boolean is true, O if the true, 'false' if the boolean is false boolean is false number false ifthe A string version of the number is O or number with no leading or NaN, otherwise trailing zeros; 'NaN' if the true number is NaN, , Infinity' if the number is infinity, and '-Infinity' ifthe number is negative infinity string false ifthe The number held string is an empty by the string, as string, otherwise long as it is a valid true XPath number (which doesn't include exponents or grouping separators) ; otherwise NaN node set true if the node The result of The string value of the first set holds nodes; converting the node in the node set false ifthe string value of the node set is empty first node in the node set to a number result tree true The result of The string value of the re suit fragment converting the tree fragment string value of the re suIt tree fragment to a number Booleans, numbers, and strings cannot be converted to node sets or result tree fragments.
  • TU07 XML at The

    TU07 XML at The

    ApacheCon 2004 November 2004 XML at the ASF Ted Leung [email protected] Copyright © Sauria Associates, LLC 2004 1 ApacheCon 2004 November 2004 Overview xml.apache.org ws.apache.org Xerces XML-RPC Xalan Axis FOP WSIF Batik JaxMe Xindice cocoon.apache.org Forrest XML-Security Cocoon XML-Commons Lenya XMLBeans Copyright © Sauria Associates, LLC ApacheCon 2004 2 There are three major XML focused projects at the ASF. Originally there was one project, xml.apache.org. Earlier this year, the Cocoon and web services projects were formed. Xml.apache.org contains a number of projects that are general purpose XML tools. Most of these tools are based on specifications from the World Wide Web Consortium. This includes XML itself, XSLT, XSL Formatting object, Scalable Vector Graphics, and XML Signature and XML Encryption The web services project, ws.apache.org contains projects that cluster around standards for dealing with Web Services, including SOAP and XML-RPC The Cocoon project is oriented around the Cocoon Web publishing framework which is basd on XML, XSLT, and a number of other XML related technologies. I’m not going to be able to give you any deep technical details regarding all of these projects. Instead, I’m going to try to describe what these projects are, what standards they implement, and talk about situations where you might use them. Unless I say otherwise, I’m going to be covering the Java projects. There are a few projects which have C/C++ versions and I’ll mention that where applicable. Copyright © Sauria Associates,
  • The OWASP Foundation OWASP XML External Entity Attacks (XXE)

    The OWASP Foundation OWASP XML External Entity Attacks (XXE)

    AppSec Germany 2010 XML External Entity Attacks (XXE) Sascha Herzog Compass Security AG [email protected] OWASP +41 55 214 41 78 20.10.2010 Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP Foundation http://www.owasp.org XML External Entity Attacks (XXE), Sacha Herzog AppSec Germany 2010 Agenda Introduction Server2Server Communication – Web Services Client2Server Communication – Web 2.0 (AJAX) XML Basics DTD XML Schema XML Attacks Generator Attacks XML Parser Attacks Mitigation Xerces Hardening OWASP OWASP AppSec Germany 2010 Conference XML External Entity Attacks (XXE), Sacha Herzog AppSec Germany 2010 B2B / Server2Server XML Data Exchange in Web Services B2B integration with XML documents SOAP Services ORDER XML Shop Internet Supplier CONFIRM XML Example Order processing systems OWASP OWASP AppSec Germany 2010 Conference XML External Entity Attacks (XXE), Sacha Herzog AppSec Germany 2010 B2B / Server2Server Example: Web Service Integration of Web Services into portal (Stock Quotes) Data or presentation oriented Remote Portlets can be distinguished. OWASP OWASP AppSec Germany 2010 Conference XML External Entity Attacks (XXE), Sacha Herzog AppSec Germany 2010 XMLHttpRequest / Client2Server XML Data Exchange XMLHttpRequest Object JavaScript OWASP OWASP AppSec Germany 2010 Conference XML External Entity Attacks (XXE), Sacha Herzog AppSec Germany 2010 Web 2.0 - Data Exchange Formats Upstream Data Format Web 2.0 GET & POST(form, txt/xml, soap-xml) Downstream Data Format Web 2.0 html,css,xml,java-script,json,custom OWASP OWASP AppSec Germany 2010 Conference XML External Entity Attacks (XXE), Sacha Herzog AppSec Germany 2010 XML Basics: Introduction XML is a standard for exchanging structured data in textual format <?xml version="1.0" encoding="UTF-8"?> <order> <product>1234</product> <count>1</count> <orderer> <contact>Jan P.
  • Securely Streaming SVG Web-Based Electronic Healthcare Records Involving Android Mobile Clients

    Securely Streaming SVG Web-Based Electronic Healthcare Records Involving Android Mobile Clients

    146 JOURNAL OF EMERGING TECHNOLOGIES IN WEB INTELLIGENCE, VOL. 1, NO. 2, NOVEMBER 2009 Securely Streaming SVG Web-Based Electronic Healthcare Records involving Android Mobile Clients Sabah Mohammed and Jinan Fiaidhi Department of Computer Science, Lakehead University, Thunder Bay, Ontario P7B 5E1, Canada {mohammed, jfiaidhi}@lakeheadu.ca Osama Mohammed Department of Software Engineering, Lakehead University, Thunder Bay, Ontario P7B 5E1, Canada [email protected] Abstract— Although Electronic Healthcare Records (EHRs) system to provide it in a paper fashion. Healthcare has technology largely facilitates patient care by providing long relied upon paper based record systems which have clinicians with the ability to review a more complete medical become cumbersome and expensive to manage and record, interoperability and privacy issues present present significant challenges related to speed of significant barriers to their implementation. This article accessibility and security. Thus the emerging benefit of proposes the open source SVG (Scalable Vector Graphics) standard for representing electronic healthcare records for mobile Internet technology to healthcare is to provide interoperability purpose where security can be enforced mobile access to medical records. Again, using mobile using lightweight SAX streaming filters. The SVG filters are technology means that the treatment process can be sped based on the Java SAX API to push pieces of the SVG to the up and the potential for medical errors can be reduced. encryption/decryption handlers. The SAX handlers can With motivations such as patient privacy protection and filter, skip tags, or encrypt tags partially or universally at laws like the US Health Insurance Portability and any time from the stream of the SVG EHRs.
  • Xpath Overview

    Xpath Overview

    XXPPAATTHH OOVVEERRVVIIEEWW http://www.tutorialspoint.com/xpath/xpath_overview.htm Copyright © tutorialspoint.com XSL Before learning XPath, we should first understand XSL which stands for EXtensible Stylesheet Langauge. It is similar to XML as CSS is to HTML. Need for XSL In case of HTML document, tags are predefined such as table, div, span and browser knows how to add style to them and display them using CSS styles. But in case of XML document, tags are not predefined. In order to understand and style an XML document, World Wide Web Consortium W3C developed XSL which can act as XML based Stylesheet Language. An XSL document specifies how a browser should render an XML document. Following are the main parts of XSL. XSLT - used to transform XML document into various other types of document. XPath - used to navigate XML document. XSL-FO - used to format XML document. What is XPath The XPath is an official recommendation of the World Wide Web Consortium W3C. It defines a language to find information in an XML file. It is used to traverse elements and attributes of an XML document. XPath provides various types of expressions which can be used to enquire relevant information from the XML document. Structure Definations - XPath defines the parts of an XML document like element, attribute, text, namespace, processing-instruction, comment, and document nodes Path Expressions XPath provides powerful path expressions select nodes or list of nodes in XML documents. Standard FunctionsXPath provides a rich library of standard functions for manipulation of string values, numeric values, date and time comparison, node and QName manipulation, sequence manipulation, Boolean values etc.