XML

Extensible Markup Language

ISAS presented
by
-Swaminathan.PL
-Saranya.N
Data is only valuable...

…when it can be transformed

into useful information and
then into knowledge.
-Bryan Caporlette - Sequoia Software
 What is XML?
• XML is a markup language for documents containing structured
information.
• Structured information contains both content (words, pictures, etc.)
and some indication of what role that content plays (for example,
content in a section heading has a different meaning from content
in a footnote, which means something different than content in a
figure caption or content in a database table, etc.). Almost all
documents have some structure.
• A markup language is a mechanism to identify structures in a
document. The XML specification defines a standard way to add
markup to documents.
• XML specifies neither semantics nor a tag set. In fact XML is really
a meta-language for describing markup languages.
 Origin of XML
• World Wide Web Consortium (W3C)
XML Working Group
• Work begun in 1996
• Version 1.0 Recommendation released on 10 Feb 98
• Second Edition on 6 Oct 00
http://www.w3.org/TR
• Extensible Markup Language (XML) is a simple, very flexible
text format derived from SGML (ISO 8879).
• Originally designed to meet the challenges of large-scale
electronic publishing, XML is also playing an increasingly
important role in the exchange of a wide variety of data on the
Web and elsewhere.
 Limitations of HTML
• Limited number of tags.
• Browsers are forgiving.
• Browser developers may be tempted to add
new tags that only work with their product.
• Can’t customize layout from the clients
side.
• Product comparison
 Advantages of XML
• Data Reusability
Single Source - Multiple output
• Targeted Retrieval
Documents authored by, not about
• Flexibility
• Accessibility
• Portability
 XML and HTML
• HTML tells how data should look,
but XML tells you what it means.
• XML applies context to the data
and separates data content from
data presentation.
• XML provides a hierarchical Data in XML
structure.
• However, XML is not designed to
replace HTML.

StyleSheets

Layout in
HTML
 XML and EDI
• Not a replacement for EDI

• Small and Medium sized Enterprises may

deploy XML before looking to EDI

• XML developers are using the lessons

learned from EDI
 XML Technologies: Validation
• DTD: Document Type Definition
– Defines the permissible tagging structure for a
document
– Borrowed from SGML
– example
• XML Schemas
– Will ultimately replace DTDs, more flexible
– Developed specifically to validate XML
– example
 Document Type Definitions
• Defined by its elements
• A DTD is a series of definitions for element
types, attributes, entities and notations.
• Set of rules which may be very stringent or
flexible
• XML Documents do not require DTDs
• DTD’s may be part of the document or may be
externally referenced.
 XML Schema
• Part 1 : Structures
Describe the relationships and semantics
of the data.

• Part 2 : Datatypes
Define the primitive and generated
datatypes.
 XML Technologies: Display

• CSS - Cascading Style Sheets

– Pro: Easily define display properties of an XML element
– Con: Not very powerful
– Web browser only
– example
• XSL – Extensible Stylesheet Language
– Pro: can transform XML into any other markup
language. (powerful)
– Con: more complicated to use
– example
 Cascading Style Sheets
name {display: block;
font-family: Arial;
font-size: 14pt;
margin-top: 20px;}

phone {color: #cc0000;

font-style: italic;
font-size: 16pt;
position: relative;
left: 10px;}
SAMPLE:
<NAME>
<FIRST>Marion</FIRST>
<MIDDLE>A.</MIDDLE>
<LAST>Royal</LAST>
</NAME>
<AGENCY>GSA</AGENCY>
<PHONE>
<AREA_CODE>202</AREA_CODE>
<PREFIX>208</PREFIX>
<NUMBER>4643</NUMBER>
</PHONE>
 XSL
Extensible Stylesheet Language
• Controls presentation of data
• Can enable multiple types of devices to
view your content
• Can convert between different XML
formats (useful in data interchange)
• “Learning Stylesheets is like finding the square
root of pi with Roman Numerals” Walker White -
Oracle
 Runtime Data Request
(3)
(8) START (2) TL checks the integrity of the
Script on page Servlet on page process, retrieves the
does XML -> HTML (1)
calls TrustLogic template XML from data
transform and Browser
process to repository, updates XML
presents data to requests protect data to with data, encrypts and
user page
send to user signs as specified.
HTML
Internet
Internet *.jsp
Trust XML *.jsp
Logic
Agent
(7) XML HTML XML Trust
Agent verifies Logic
signature on +
(6) Protected XML Server
data and Web
Applet on XML Application data (blob)
decrypts page invokes XML form
Server (4) XML template
TL Agent and Encrypted and
passes it HTML with
embedded XML signed data passed
protected back to application
embedded (5) for transmission to
data Protected data browser.
passed to browser as
embedded value on Data
page Storage
 Workflow
6
On user data request,
4 retrieve XML, perform 9
Data Stored Under Key “Translation” to Data Stored Under
Role Key(s) Encrypt Data Under Role Key(s)
User Key

1 2 3 5 7 8
Authorize Provide Role Return Data Authorize Data Sent Under Return Data
User to a Role Key(s) to Encrypt Encrypted Under User to a Role User’s Key & Encrypted Under
Data Role(s) Provide Role Role(s)
Keys
Service oriented architecture

Shared service oriented architecture

(fx http, XML, SOAP, WSDL, UDDI)
 PROTECTED XML

<XML> App
App App App
Database
<Content/>
<Context/> <Context
/>

<Content/> TL Secure
<Presentation/>
Database
<Actions/>
1 2 <Keys/> <Actions/>
Authenticate User <Presentation/> <Keys/>
User and Requests
Authorize to a </XML>
Data
Role In
InTrustLogic
TrustLogic all
allXML
XML objects
objects
3 needed
needed by the application are
stored in
by
a
the application
database where
are
stored in a database where
Return they
they are
aresigned
signed by
by TrustLogic
TrustLogic
Protected and
and the signature isis verified
the signature verified
XML at
at run-time to ensure their
run-time to ensure their
User User User integrity
integrity
 XSL Transformations
XML

XML XSL Transformation Plain Text

WML PDF

HTML SGML
Technology Leaders Driving XML
Application
Application Native XML
Integration
Integration Native XML
Applications
Applications

e-Commerce Content
Content
e-Commerce Management
Management
 ebXML Development

United Nations Centre for the

Facilitation of Procedures
and Practices for Accelerating the adoption of
Administration, Commerce Core Technology Standards industry standards
and Transport 100+ member companies

IT Supply Chain

ASC X.12 EDI

The XML Industry Portal

Sponsored by IBM, Sun, Oracle, SAP, ...
A vendor-neutral XML schema
clearinghouse.
Info on how to apply XML in industrial
and comercial settings.
 Design Goals for XML
• 1. XML shall be straightforwardly usable over the Internet.
• 2. XML shall support a wide variety of applications.
• 3. XML shall be compatible with SGML.
• 4. It shall be easy to write programs which process XML documents.
• 5. The number of optional features in XML is to be kept to the
absolute minimum, ideally zero.
• 6. XML documents should be human-legible and reasonably clear.
• 7. The XML design should be prepared quickly.
• 8. The design of XML shall be formal and concise.
• 9. XML documents shall be easy to create.
• 10. Terseness in XML markup is of minimal importance.
Appendix
Demo technical details
Current Activities : Encrypted
XML database
Key Translation Detail
Run Time Data Request Flow
of Events
Low Lifetime Cost
Trust Domain Policy
 References
• Http:XML.GOV
• http://www.w3.org
• http://www.xml.com
• http://www.ibm.com/developer/xml/
• http://biztalk.com/
• http://www.oasis-open.org/

[email protected]
202.208.4643