This document discusses XML and provides an introduction and overview. It defines what a markup language is, describes the history and features of SGML and limitations of HTML. XML is presented as being extensible and overcoming drawbacks of HTML. The key steps to create an XML document are outlined, including the XML declaration, root element, defining elements and attributes, and verifying the document structure. Components of an XML document like entities, character data types, and DOCTYPE declarations are also summarized.
What is XML
• XML stands for EXtensible Markup Language
• XML was designed to carry data, not to display data
• XML developed by the World Wide Web
Consortium (www.W3C.org)
• XML like HTML is a mark up language, but
unlike HTML it doesn’t have predefined
elements
XML Versions
version XML 1.0 was initially defined in 1998
version XML 1.1 was initially published on 4th Feb 2004
Example language of xml structure
XHTML
WML AND WAP
SVG
Uses XML
WEB DEVELOPER
TRANSPORTING AND SHARING DATA
STORING DATA
DOCUMENTATION
ANDROID DEVELOPER
XML Doc Advantages
Easy data sharing, text documents are readable between any device.
Easy to learn.
Extendable.
Freedom to define tags.
Easy searching.
Disadvantages of XML
The redundancy may affect application efficiency through higher storage, transmission and processing costs.
XML Document Components
The various components of an XML document used for representing data in a hierarchical order are:
Processing Instruction (PI)
Tags
Elements
Content
Attributes
Entities
Comments
XML Document Object Model (DOM) is a standard for accessing and navigating XML code. All structured documents have a DOM system. The DOM simply defines the objects and properties in code, so parsers can identify and understand the individual parts. The DOM presents an XML document as a tree-structure. Knowing the XML DOM is a must for anyone working with XML.
IP Licensing - Presentation by Dr. Kalyan C. Kankanala
Contact Us for Intellectual Property Services
BananaIP Counsels
Regd Office
No.40,3rd Main Road,JC Industrial Estate,
Kanakapura Road,Bangalore – 560 062.
Email: contact@bananaip.com
Telephone: +91-80-26860414 /24/34
What is XML
• XML stands for EXtensible Markup Language
• XML was designed to carry data, not to display data
• XML developed by the World Wide Web
Consortium (www.W3C.org)
• XML like HTML is a mark up language, but
unlike HTML it doesn’t have predefined
elements
XML Versions
version XML 1.0 was initially defined in 1998
version XML 1.1 was initially published on 4th Feb 2004
Example language of xml structure
XHTML
WML AND WAP
SVG
Uses XML
WEB DEVELOPER
TRANSPORTING AND SHARING DATA
STORING DATA
DOCUMENTATION
ANDROID DEVELOPER
XML Doc Advantages
Easy data sharing, text documents are readable between any device.
Easy to learn.
Extendable.
Freedom to define tags.
Easy searching.
Disadvantages of XML
The redundancy may affect application efficiency through higher storage, transmission and processing costs.
XML Document Components
The various components of an XML document used for representing data in a hierarchical order are:
Processing Instruction (PI)
Tags
Elements
Content
Attributes
Entities
Comments
XML Document Object Model (DOM) is a standard for accessing and navigating XML code. All structured documents have a DOM system. The DOM simply defines the objects and properties in code, so parsers can identify and understand the individual parts. The DOM presents an XML document as a tree-structure. Knowing the XML DOM is a must for anyone working with XML.
IP Licensing - Presentation by Dr. Kalyan C. Kankanala
Contact Us for Intellectual Property Services
BananaIP Counsels
Regd Office
No.40,3rd Main Road,JC Industrial Estate,
Kanakapura Road,Bangalore – 560 062.
Email: contact@bananaip.com
Telephone: +91-80-26860414 /24/34
Media and Information Literacy (MIL) - Intellectual Property, Fair Use, and C...Arniel Ping
Media and Information Literacy (MIL) Legal, Ethical, and Societal Issues in Media and Information (Part 1)
Topics:
1. Intellectual Property in International
and Local Context
2. Fair Use and Creative Commons
LEARNING COMPETENCIES:
1. explain intellectual property and its different types (SSHS);
2. explain copyright, fair use, etc.vis-a-vis human rights (MIL11/12LESI-IIIg20);
3. discuss current issues related to copyright vis-à-vis gov’t./provide sectors actions (MIL11/12LESI-IIIg21);
4. put into practice their understanding of the intellectual property, copy right, and fair use guidelines (MIL11/12LESI-IIIg17); and
5. explain actions to promote ethical use of media and information (MIL11/12LESI-IIIg22);
Intellectual Capital: Define, Understand and Capture ItSmarter-Companies
Intellectual capital is the driving force behind our economy today. This presentation from Mary Adams of Intellectual Capital advisors helps you visualize your IC and put it to work in your business.
XML Introduction,Syntax of XML,Well formed XML Documents,XML Document Structure,Document Type Definitions,XML Namespace,XML Schemas,DOM(Document Object Model)
Node.js là một hệ thống phần mềm được thiết kế để viết các ứng dụng internet có khả
năng mở rộng, đặc biệt là máy chủ web. Chương trình được viết bằng JavaScript, sử dụng kỹ
thật điều khển theo sự kiện, nhập/xuất không đồng bộ để tối tiểu tổng chi phí và tối đại khả
năng mở rộng. Node.js bao gồm có V8 JavaScript engine của Google, libUV, và vài thư viện
khác.
It took me about one and a half year to update my cheat sheet about clean code and TDD.
But now, it’s here.
The cheat sheet has grown quite a bit and now contains principles, patterns, smells and guidelines for
clean code
class and package design
TDD – Test Driven Development
ATDD – Acceptance Test Driven Development
Continuous Integration
I had to re-layout the sheets because maintenance became a nightmare (yes, very ironic).
Reference: http://www.planetgeek.ch/2013/06/05/clean-code-cheat-sheet/
Các câu chuyện toán học - Tập 3: Khẳng định trong phủ địnhBình Trọng Án
Bộ Sách Các câu chuyện Toán học của nhóm tác giả Đỗ Mạnh Tùng, Nguyễn Bá Đô, Nguyễn Văn Túc, Hồ Châu. Bộ sách gồm 6 tập:
Tập 3: Khẳng định trong phủ định.
Tỷ lệ vàng - một phát hiện vĩ đại của hình họcBình Trọng Án
“Hai phát hiện vĩ đại nhất của hình học, một là định lý Pythagore, và hai là tỷ lệ vàng – một thứ có thể so sánh là quý như vàng, còn thứ kia có giá trị như một viên ngọc quý” - Kepler
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
2. Core XML / Chapter 1 / Slide 2 of 352
Chapter Objectives -1
Discuss markup language
List and explain drawbacks of HTML
Discuss the architecture of XML documents
List the benefits of XML
Discuss Parser
3. Core XML / Chapter 1 / Slide 3 of 353
Chapter Objectives -2
Build a complete XML Document:
Character Data
Comments
Processing Instructions
Entities
General Entities
Parameter Entities
The DOCTYPE Declarations
4. Core XML / Chapter 1 / Slide 4 of 354
History of Markup
Documents recorded
using paper and pen
Typesetters formatting
documents
Tools used by typesetters
to format a document
5. Core XML / Chapter 1 / Slide 5 of 355
Markup Language
A Markup language defines the rules that help to add
meaning to the content and structure of documents.
They are classified as:
Stylistic Markup – It determines the presentation of the
document
Structure Markup – It defines the structure of the
document
Semantic Markup – It determines the content of the
document
6. Core XML / Chapter 1 / Slide 6 of 356
SGML
Generalized Markup Language (GML) is the
system of formatting documents.
GML was fine-tuned and came to be known
as Standard Generalized Markup Language
(SGML).
SGML is the source of origin of all markup
languages
7. Core XML / Chapter 1 / Slide 7 of 357
Features of SGML
It describes markup language, which allows
authors to create their own tags that relate to
their content.
It needs a separate file that will contain all
the rules for the language, for its
interpretation
A SGML application is markup language
derived from SGML.
8. Core XML / Chapter 1 / Slide 8 of 358
HTML
HTML is the most famous markup language derived
from SGML.
It was created to mark up technical papers so that
they could be transferred across different platforms
for the scientific community.
It is now also used by those non-scientific users who
are concerned about their document’s presentation.
9. Core XML / Chapter 1 / Slide 9 of 359
Drawbacks of HTML
Fixed tag set
Presentation technology does not relate to the
contents
It is flat
Clogging
HTML is not international
Data interchange is impossible
Does not have a robust linking mechanism
HTML is not reusable
10. Core XML / Chapter 1 / Slide 10 of 3510
HTML and XML code Examples
<UL>
<LI> TOM CRUISE
<UL>
<LI> CLIENT ID : 100
<LI> COMPANY : XYZ Corp.
<LI> Email : tom@usa.net
<LI> Phone : 3336767
<LI> Street Adress: 25th
St.
<LI> City : Toronto
<LI> State : Toronto
<LI> Zip : 20056
</UL>
</UL>
<Details>
<CONTACT>
<PERSON_NAME>TOM CRUISE
</PERSON_NAME>
<ID> 100 </ID>
<Company>XYZ Corp. </Company>
<Email> tom@usa.net</Email>
<Phone> 3336767 </Phone>
<Street> 25th St. </Street>
<City> Toronto </City>
<State> Toronto </State>
<ZIP> 20056 </ZIP>
</CONTACT>
</Details>
HTML Code XML Code
11. Core XML / Chapter 1 / Slide 11 of 3511
XML -1
XML stands for Extensible Markup Language.
It overcomes all the drawbacks of HTML.
It allows the user to define their own set of tags, and also
makes it possible for others (people or programs) to
understand it.
It is more flexible than HTML.
It inherits the features of SGML and combines it with the
features of HTML.
It is a smaller version of SGML.
12. Core XML / Chapter 1 / Slide 12 of 3512
XML -2
XML is a metalanguage and it describes other
languages.
The data contained in an XML file can be displayed
in different ways.
It can also be offered to other applications for further
processing.
Style sheets help transform structured data into
different HTML views. This enables data to be
displayed on different browsers.
13. Core XML / Chapter 1 / Slide 13 of 3513
XML Architecture - 1
XML supports three-tier architecture for handling
and manipulating data.
It can be generated from existing databases using a
scalable three-tier model.
XML tags represent the logical structure of data that
can be interpreted and used in various ways by
different applications.
The middle-tier is used to access multiple databases
and translate data into XML.
14. Core XML / Chapter 1 / Slide 14 of 3514
XML Architecture -2
15. Core XML / Chapter 1 / Slide 15 of 3515
XML – A Universal data format
HTML is a single markup language, but XML is a
family of markup languages.
Any type of data can be easily defined in XML.
XML is popular because it supports a wide range of
applications and is easy to use.
XML has a structured data format, which allows it to
store complex data
16. Core XML / Chapter 1 / Slide 16 of 3516
Benefits of XML
The three-tier architecture has easier
scalability and better security.
The benefits of XML are classified into the
following:
Business benefits
Technological benefits
17. Core XML / Chapter 1 / Slide 17 of 3517
Business Benefits
Information sharing:
Allows businesses to define data formats in XML
Provides tools to read, write and transform data between
XML and other formats
XML inside a single application:
Powerful, flexible and extensible language
Content Delivery:
Supports different users and channels, like digital TV,
phone, web and multimedia kiosks
18. Core XML / Chapter 1 / Slide 18 of 3518
Technological Benefits
Technological
Benefits
Re-use of data
Separation of data and
presentation
ExtensibilitySemantic
information
19. Core XML / Chapter 1 / Slide 19 of 3519
XML Document Structure
An XML document is composed of sets of “entities”
identified by unique names.
All documents begin with a root or document entity.
Entities are aliases for more complex functions.
Documents are logically composed of declarations,
elements, comments, character references, and
processing instructions.
20. Core XML / Chapter 1 / Slide 20 of 3520
Well formed and Valid Documents
An XML document is considered as well formed, if a
minimum set of requirements defined in the XML
1.0 specification are satisfied.
The requirements ensure that correct language terms
are used in the right manner .
A valid XML document is a well-formed XML
document, which conforms to the rules of a
Document Type Definition (DTD).
DTD defines the rules that an XML markup in the
XML document must follow.
21. Core XML / Chapter 1 / Slide 21 of 3521
Parsers - 1
Parsers help the computer interpret an XML
file.
<?xml
version=“1.0”?
>
<nxn>
</nxn>
Editor with the
XML document
Parsed document
viewed in the browser
XML document parsed by the
parser
Their are two types of parsers:
Non Validating parser
Validating parser
22. Core XML / Chapter 1 / Slide 22 of 3522
Parsers - 2
XML
file
Other related
files (like DTD
file)
Parsers load the XML
and other related files
to check whether the
XML document is well
formed and valid
Data tree
23. Core XML / Chapter 1 / Slide 23 of 3523
Data versus Markup
<NAME> Tom Cruise </NAME>
Markup
Data
24. Core XML / Chapter 1 / Slide 24 of 3524
Creating an XML Document
To create an XML document:
State an XML declaration
Create a root element
Create the XML code
Verify the document
25. Core XML / Chapter 1 / Slide 25 of 3525
Stating an XML Declaration
Syntax
<?xml version=“1.0” standalone=“no” encoding=“UTP-8”?>
‘Standalone’ and ‘encoding’ attributes are
optional, only the version number is mandatory
‘Standalone’ – is the external declaration
‘Encoding’ - specifies the character encoding
used by the author
XML 1.0 version is default
26. Core XML / Chapter 1 / Slide 26 of 3526
Creating a Root Element
There can only be one root element
It describes the function of the document
Every XML document must have a root
element
Example
<?xml version=“1.0” standalone=“no” encoding=“UTP-8”?>
<BOOK>
</BOOK>
27. Core XML / Chapter 1 / Slide 27 of 3527
Creating the XML Code -1
It is the process of creating our own elements
and attributes as required by our application.
Elements are the basic units of XML content.
Tags tell the user agent to do something to the
content encased between the start and end tag.Opening Tag Content Closing Tag
<TITLE> Aptech Ltd </TITLE>
Element
Parts of an
element
28. Core XML / Chapter 1 / Slide 28 of 3528
Creating the XML Code -2
Rules govern the elements:
At least one element required
XML tags are case sensitive
End the tags correctly
Nest tags Properly
Use legal tags
Length of markup names
Define Valid Attributes
29. Core XML / Chapter 1 / Slide 29 of 3529
Verify the document
The document should follow the
XML rules; otherwise it will not be
read by the browser or by any other
XML reader
30. Core XML / Chapter 1 / Slide 30 of 3530
Comments
This is information for the understanding of
the user, and is to be ignored by the
processor.
Syntax
<!- - Write the comment here -- >
Example
<!-- don't show these
<NAME>KATE WINSLET</NAME>
<NAME>NICOLE KIDMAN</NAME>
<NAME>ARNOLD</NAME>
-->
<NAME>TOM CRUISE</NAME>
The example given will
display only the name TOM
CRUSIE, and others are
treated as comments.
31. Core XML / Chapter 1 / Slide 31 of 3531
Processing Instruction
A processing information is a bit of information meant
for the application using the XML document.
These instructions are directly passed to the application
using the parser.
The XML declaration is also a processing agent.
<?xml:stylesheet type=“text/xsl”?>
Name of application Instruction information
32. Core XML / Chapter 1 / Slide 32 of 3532
Character Data
The text between the start and end tags is
defined as ‘character data’.
Character data may be any legal (Unicode).
Character data is classified into:
PCDATA
CDATA
33. Core XML / Chapter 1 / Slide 33 of 3533
PCDATA
It stands for parsed character data.
PCDATA is text that will be parsed by a Parser.
Tags inside the text will be treated as markup and
entities will be expanded.
Entity Name Character
< <
> >
& &
" "
' '
Predefined entities
34. Core XML / Chapter 1 / Slide 34 of 3534
CDATA
It means character data.
It will not be parsed by the Parser.
CDATA are used to make it convenient to include
large blocks of special characters.
The character string ]]> is not allowed within a
CDATA block as it will signal the end of the CDATA
block.
<SAMPLE>
<![CDATA[<DOCUMENT>
<NAME>TOM CRUISE</NAME>
<EMAIL>tom@usa.com</EMAIL>
</DOCUMENT>]]>
</SAMPLE>
Example
35. Core XML / Chapter 1 / Slide 35 of 3535
Entities
Entities are used to avoid typing long pieces of text
repeatedly within a document.
There are two categories of entities:
General entities
Syntax
<!ENTITY ADDRESS "text that is to be represented
by an entity">
Parameter entities
Syntax
<!ENTITY % ADDRESS "text that is to be represented by an entity">
36. Core XML / Chapter 1 / Slide 36 of 3536
Examples of Entities
An example of Parameter entities
< CLIENT = "&APTECH;" PRODUCT
= "&PRODUCT_ID;" QUANTITY
= "15">
Entity declaration
Syntax
%PARAMETER_ENTITY_NAME
;
Example
%address;
An example of a General entity
<!ENTITY full_address " My
Address 12 Tenth Ave. Suite 12
Paris, France">
Entity declaration
Syntax
&ENTITY_NAME;
Example
&address;
37. Core XML / Chapter 1 / Slide 37 of 3537
The DOCTYPE declarations
The <!DOCTYPE [..]> declaration follows the XML
declaration in an XML document.
Syntax
<?xml version="1.0"?>
<!DOCTYPE myDoc [
...declare the entities here....
<myDoc>
...body of the document....
</myDoc>
Example
<!DOCTYPE CUSTOMERS [
<!ENTITY firstFloor "15 Downing St Floor 1">
<!ENTITY secondFloor "15 Downing St Floor 2">
<!ENTITY thirdFloor "15 Downing St Floor 3">
]>
38. Core XML / Chapter 1 / Slide 38 of 3538
Attributes
An attribute gives information about an
element.
Attributes are embedded in the element start
tag.
An attribute consists of an attribute name
and attribute value.
Example
<TV count="8">SONY</TV>
<LAPTOP count="10">IBM</LAPTOP>
39. Core XML / Chapter 1 / Slide 39 of 3539
Summary-1
A markup language defines a set of rules that adds
meaning to the content and structure of documents
XML is extensible, which means that we can define our
own set of tags, and make it possible for other parties
(people or programs) to know and understand these tags.
This makes XML much more flexible than HTML
XML inherits features from SGML and includes the
features of HTML. XML can be generated from existing
databases using a scalable three-tier model. XML-based
data does not contain information about how data should
be displayed
An XML document is composed of a set of “entities”
identified by unique names
40. Core XML / Chapter 1 / Slide 40 of 3540
Summary-2
A well-formed document is one that conforms to the basic
rules of XML; a valid document is a well-formed
document that conforms to the rules of a DTD (Document
Type Definition)
The parser helps the computer to interpret an XML file
Steps involved in the building of an XML document are:
Stating an XML declaration
Creating a root element
Creating the XML code
Verifying the document
Character data is classified into PCDATA and CDATA
41. Core XML / Chapter 1 / Slide 41 of 3541
Summary-3
Entities are used to avoid typing long pieces of text repeatedly
in a document. The two types of entities are:
General entities
Parameter entities
The <!DOCTYPE […]> declaration follows the XML
declaration in an XML document.
An attribute gives information about an element