Final Semantic Web Unit1 - QuestionsandAnswer Booklet - R18
Final Semantic Web Unit1 - QuestionsandAnswer Booklet - R18
Ans: A Semantic Web is a web of data that can be processed directly or indirectly by
machines.
The Semantic Web as a logical extension of the current Web instead of a distant possibility.
The Semantic Web is both achievable and desirable.
According to the vision of Tim Berners-Lee we can define the Semantic Web as a machine
processable web of smart data.
We can also further define smart data as data that is application-independent, composable,
classified, and part of a larger information ecosystem (ontology).
The World Wide Web Consortium (W3C) has established an Activity dedicated to
implementing the vision of the Semantic Web. The following diagram shows an example of
Semantic Web with Web of documents and Web of data.
Ans: The Semantic Web is not just for the World Wide Web.
It represents a set of technologies that will work equally well on internal corporate
intranets.
The Semantic Web will resolve several key problems facing current information
technology architectures.
Information Overload
Information overload is the most obvious problem in need of a solution, and technology
experts have been warning us about it for 50 years.
Stovepipe Systems
A stovepipe system is a system where all the components are hardwired to only work
together.
Ans: The first step is a paradigm shift in the way we think about data. Historically, data has
been locked away in proprietary applications.
Data was seen as secondary to processing the data. This incorrect attitude gave rise to
the expression “garbage in, garbage out,” or GIGO. GIGO basically reveals the flaw in the
original argument by establishing the dependency between processing and data.
The following Figure displays the progression of data along a continuum of increasing
intelligence and also four stages of the smart data continuum.
B) Describe about the Web Services fitness into the Semantic Web.
Ans: Web services are software services identified by a URI that are described, discovered,
and accessed using Web protocols.
The important point about Web services is that they consume and produce XML. Thus, the
first way that Web services fit into the Semantic Web is by furthering the adoption of XML,
or more smart data.
Semantic Web technologies will be necessary to solve the Web service discovery problem.
We may have projects that could share lessons learned, provide competitive intelligence
information, and save us a lot of time and work.
Information sharing and communication are paramount in any organization, but as most
organizations grow and collect more information, this is a major struggle.
We all understand the importance of not reinventing the wheel, but how many times
have we unintentionally duplicated efforts? When organizations get larger, communication
gaps are inevitable.
With a little bit of effort, a corporate knowledge base could at least include a registry of
descriptions of projects and what each team is building.
Imagine how easy it would be for the employees to be able to find relevant information.
Using Semantic Web enabled Web services can allow us to create such a registry.
A side effect of having such a knowledge base is the ability of software programs to
automate administrative tasks.
Booking travel, for example, is an example where the Semantic Web and Web services
could aid in making a painful task easy.
Making travel arrangements can be an administrative nightmare. Everyone has personal
travel preferences and must take items such as the following into consideration:
Transportation preference (car, train, bus, plane)
Hotel preference and rewards associated with hotel
Airline preference and frequent flyer miles
Hotel proximity to meeting places
Hotel room preferences (nonsmoking, king, bar, wireless network in lobby)
Rental car options and associated rewards
Price (lodging and transportation per diem rates for the company)
3. A) Define XML.
1. Logical assertions
2. Classification
3. Formal class models
4. Rules
5. Trust
C) Demonstrate on Well-Formed Document and Valid Document in XML.
Ans: Well Formed XML Documents: A well-formed XML document complies with all the
W3C syntax rules of XML (explicitly called out in the XML specification as well-formedness
constraints) like naming, nesting, and attribute quoting.
A valid XML document references and satisfies either a DTD (Document Type Definition)
or an XML schema.
A "well formed" XML document is not the same as a "valid" XML document.
A "valid" XML document must be well formed. In addition, it must conform to a
document type definition or schema.
Ans: Namespaces are a simple mechanism for creating globally unique names for the elements
and attributes of the markup language.
This is important for two reasons: to deconflict the meaning of identical names in
different markup languages and to allow different markup languages to be mixed together
without ambiguity.
Unfortunately, namespaces were not fully compatible with DTDs, and therefore their
adoption has been slow.
The current markup definition languages, like XML Schema, fully support namespaces.
The actual namespace is a unique Uniform Resource Identifier (URI). Here is a
sample namespace declaration:
<xsd:schema xmlns:xsd=“http://www.w3.org/2001/XMLSchema”>
B) Describe the primitive data types of XML Schema.
Ans: There are many built-in data types defined in the XML Schema specification. The
following Table lists the most common primitive data types.
The following example shows the employe schema for employee details.
employee.xsd
1. <?xml version="1.0"?>
2. <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" >
3. <xsd:element name="employee">
4. <xsd:complexType>
5. <xsd:sequence>
6. <xsd:element name="name" type="xsd:string"/>
7. <xsd:element name="salary" type="xsd:float"/>
8. <xsd:element name="Designation" type="xsd:string"/>
9. </xsd:sequence>
10. </xsd:complexType>
11. </xsd:element>
12. </xsd:schema>
Inference in Semantic Web: Inference is the process of inferring or discovering new facts
about the existing data based on a set of rules.
Applying rules and logic to semantic data requires standard, embeddable inference
engines. These programs will execute a set of rules on a specific instance of data using
an ontology.
An early example of these types of inferencing engines is the open-source software
Closed World Machine (CWM).
B) Compare DTD and XSD.
Ans:
DTD vs XSD
There are many differences between DTD (Document Type Definition) and XSD (XML Schema
Definition). In short, DTD provides less control on XML structure whereas XSD (XML schema)
provides more control.
XML is spreading through the all areas of the enterprise, from the IT department to the
intranet, extranet, Web sites, and databases.
XML has become integrated with the majority of commercial products on the market,
either as a primary or enabling technology.
The current and future impact of XML in 10 specific areas are given bellow.
Data exchange and interoperability.
XML has become the universal syntax for exchanging data between organizations. By
agreeing on a standard schema, organization can produce these text documents that can be
validated, transmitted, and parsed by any application regardless of hardware or operating
system.
E-business
Business-to-business (B2B) transactions have been revolutionized through XML. B2B
revolves around the exchange of business messages to conduct business transactions.
There are dozens of commercial products supporting numerous business vocabularies
developed by RosettaNet, OASIS, and other organizations.
Enterprise Application Integration (EAI).
Enterprise Application Integration is the assembling of legacy applications, databases,
and systems to work together to support integrated Web views, e-commerce, and Enterprise
Resource Planning (ERP).
Enterprise IT architectures.
The impact of XML on IT architectures has grown increasingly important as a bridge
between the Java 2 Enterprise Edition (J2EE) platform and Microsoft’s .NET platform.
Large companies are implementing both architectures and turning to XML Web services
to integrate them.
Additionally, XML is influencing development on every tier of the N-tier network. On
the client tier, XML is transformed via XSLT to multiple presentation languages like Scalable
Vector Graphics (SVG).
Instead of just meta data, we will have an information stack composed of semantic
levels. We are currently at Level 1 with XML Schema, which is represented as
modelling the properties of our data classes.
We are capturing and processing meta data about isolated data classes like purchase
orders, products, employees, and customers.
On the left side of the diagram, we associate a simple physical metaphor to the state
of each level.
Level 1 is analogous to describing singular concepts or objects.
In Level 2, we will move beyond data modelling (simple meta data properties) to
knowledge modelling. This includes the Resource Description Framework (RDF)
and taxonomies.
Ans: The Document Object Model (DOM) Parser is a language-neutral data model and
application programming interface (API) for programmatic access and manipulation of
XML and HTML.
The Document Object Model is an in-memory representation of an XML or HTML
document and methods to manipulate it.
DOMs can be loaded from XML documents, saved to XML documents, or dynamically
generated by a program.
An XML parser is a software library or package that provides interfaces for client applications to
work with an XML document. The following diagram shows the role of a parser.
The DOM has steadily evolved by increasing the detail of the representation, increasing the
scope of the representation, and adding new manipulation methods. This is accomplished by
dividing the DOM into conformance levels, where each new level adds to the feature set.