Daniel G. Teivelis [email protected].

Daniel G. [email protected]

W3C‘s Semantic Web ArchitectureW3C‘s Semantic Web Architecture

Semantic Web: An Extension of the WWWSemantic Web: An Extension of the WWW

semantic – the meaning

metadata – data about data

ontology – giving context, vocabulary

taxonomy – classification

knowledge – the whole experience

artificial intelligence – examining and learning online, living systems

Semantic Web: Special TerminologySemantic Web: Special Terminology

Semantic Web: Building BlocksSemantic Web: Building Blocks

www evolves to semantic webwww evolves to semantic web

Explain the Semantic Web in Business Terms!

Web AspectsWeb Aspects

The Good Universally accepted

Improving performance and standardization

The Bad Application integration over the Web

Vendor bickering over protocols and tools

The Ugly Definition of meaning and semantics for knowledge representation

Automatic content transformation

How do average users find the information they need amidst a flood of irrelevant matter? Quickly, Easily, Consistently?

We need to build Publish & Find Engines With a reasonable amount of effort / cost

Within a reasonable amount of time

But how?

The Key Challenge - StillThe Key Challenge - Still

Centralized Easier to manage on a small scale (one company)

Hard to get agreements between corporations

Cannot scale to the size of a global knowledge base

Decentralized Distributed effort

Common denominator approach

Some fuzziness allowed to achieve versatility

Semantic

Web

Approaches for Knowledge RepresentationApproaches for Knowledge Representation

„The Semantic Web is not a separate Web but an extension of the current one, in which information is given well-defined meaning, better enabling computers and people to work in cooperation“

Source: Scientific American: The Semantic WebTIM BERNERS-LEE, JAMES HENDLER and ORA LASSILA http://www.sciam.com/2001/0501issue/0501berners-lee.html

The Semantic WebThe Semantic Web

„The Semantic Web will enable machines to COMPREHEND semantic documents and data, not human speech and writings.“



The Web Initially built for humans

Scales from the Desktop to the World

Inherently weak when supporting machine to machine communication

Key enabler for further Web-Evolution to the Semantic Web Structured Markup

Meta Data

Knowledge about Knowledge

Available Frameworks XML (Extensible Markup Language)

Resource Description Framwork (RDF)

Ontologies (Taxonomies and Inference rules)


The Three Cornerstones of The Semantic WebThe Three Cornerstones of The Semantic Web

Scope: A foundation for processing metadata

Mission: To provide interoperability between applications that exchange machine-

understandable information on the Web

Strategy: To emphasize facilities to enable automated processing of Web resources

RDF (Resource Description Framework)RDF (Resource Description Framework)

has

have

Identified by UniqueResourceIdentifiers

each

RDF FundamentalsRDF Fundamentals

Describedin XML

Documentsdriven by XML

Schemas

ExampleExample

Resource discovery to provide better search engine capabilities,

Cataloging for describing the content and content relationships available at a particular Web

site, page, or digital library,

Intelligent software agents to facilitate knowledge sharing and exchange

Content rating describing collections of pages that represent a single logical "document"

RDF Application AreasRDF Application Areas

Other application areas: Describing intellectual property rights of Web pages,

Expressing the privacy preferences of a user

Expressing privacy policies of a Web site

In short Wherever XML is being used or consdidered for use right now.

What you gain is S.P.E.E.D

RDF Application AreasRDF Application Areas

„An ontology is a document or file that formally defines the relations among terms“

The Result: OntologiesThe Result: Ontologies


Simple?

Trivial even?

So . . .So . . .

What the Semantic Web is NOT ... The Semantic Web is not Artificial

Intelligence The Semantic Web does not allow

arbitrary complexity The Semantic Web is not something that

will ever be complete

The Semantic Web – A RoadmapThe Semantic Web – A Roadmap

What the Semantic Web IS ... A great vision Something that will be built over time An emergent property of the global effort

towards standardization around XML

Source: John Thackera: the design challenge of pervasive computing:http://www.doorsofperception.com/projects/chi/

The Story of the FrogThe Story of the Frog

The water we are inThe water we are in

We produce 1 ExaByte of Information per year Source: Stanford University Study

60% of programming time is wasted on extracting and moving data from point A to point B Source: Gartner Group Study

50% of world economy depends on Office Work manipulating data by hand Source: MIT research

The Semantic Web: The Semantic Web: Simple in concept , but massive in scaleSimple in concept , but massive in scale

Semantic Web Awareness (Semantic Web Awareness (Informal research among IT decision makersInformal research among IT decision makers))

Business Relevance of Semantic Web Components (Business Relevance of Semantic Web Components (personal opinionpersonal opinion))

The Semantic Web ConundrumThe Semantic Web Conundrum

The Key QuestionThe Key Question

TBI

EAI

B2N

W3C

ERP

CRM

ERM

ECMB2E

E2E

XML

B2B

WAP

J2E

B2CBPM

Market OverviewMarket Overview

U.D.D.I.

XML

S.O.A.PW.S.D.L.

XSLTXBRL

The breakthrough: „The breakthrough: „Shattering the 3-letter-barrier for acronyms!Shattering the 3-letter-barrier for acronyms!““

EAI

SCM

W3C

ERPCRM

ERM

ECM

B2E

.NET

B2B

WAP

J2E

B2C

UDDI

SOAP

BPM

Bringing things into perspective „Bringing things into perspective „one to bind them & one to rule them all ...one to bind them & one to rule them all ...““

Integration costs consume an average of 24 percent of yearly IT budgets.

More than half of the InfoWorld readers polled believe that Web services will make integration cheaper, easier, and faster.

For at least the next couple of years, traditional integration technologies will evolve in parallel with Web services.

Defining XML vocabularies and business processes now, both for internal use and for connections to partners, will make the later transition to Web services much easier.

Infoworld AnalysisInfoworld Analysis

The story of The Elephant ...The story of The Elephant ...

A matter of perspective ...A matter of perspective ...

Corporate Elephants have ...Corporate Elephants have ...

Different Integration Angles ...Different Integration Angles ...

Process = Application PLUS Data Process MINUS Data = Application

Process MINUS Application = Data

Applications MUST keep the process independent of data!

Data MUST keep the process independent of applications!

Quantum Integration EquationQuantum Integration Equation

You cannot cleanly separate Data, Applications and Process ... They are forever intertwined by 4 decades of legacy application development

COBOL Applications (Process and Data)

Stored Procedures in RDBMS (Process and Data)

Proprietary workflow applications (Process descriptions)

This is creating a huge problem for any customer!

Fact is ...Fact is ...

Customers will maintain their transaction systems „forever“ Must accept that data, application and process are interlinked

Customers are building / buying new applications That are based on standards that keep data, applications and process separated

Customers are building up „Integration Centers“ To integrate new and existing systems

To take advantage of commodity content and applications

Market StatusMarket Status

D a t a A p p l i c a t i o n s P r o c e s s e s

Main Solution IngredientMain Solution Ingredient

Scale Up 500 Million Servers 1 Billion Users 20 Billion Devices 200 Trillion transactions

Scale Out Distributed Data

Distributed Applications

Distributed Processes

Server-Centric Process-Centric

Key Issues for IT: Key Issues for IT: Scale Up and Scale OutScale Up and Scale Out

Old Server-Centric Architectures Business process drives humans Humans drive

applications Applications drive functions Functions drive

data No human, no data,

no transaction

New Process-Centric Architectures Data drives functions

Functions drive applications

Applications drive business processes

Business processes drive transactions

Humans review transactions

This can only scale up! This is how to scale out!

How to scale out ...How to scale out ...

Y.C.G.T.F.H.

Aside: Big conceptual changes like this have happened before:Aside: Big conceptual changes like this have happened before:

Some implementaton are at riskSome implementaton are at risk

To take full advantage of XML It is not enough to „map“ existing data to XML! It is not enough to have an XML interface to the application! It is not enough to describe your process in XML documents!

You need a new concept A concept that allows data to drive the business

AutomaticallyBased on Standards

You can‘t get there from here ...You can‘t get there from here ...

A key component for Process-Centric Architectures:A key component for Process-Centric Architectures:

The XML Document The XML Document is the foundation for process-centric architecturesis the foundation for process-centric architectures

So ..., XML is great for techies, but what do customers want ?So ..., XML is great for techies, but what do customers want ?

Business Agility means The ability to rapidly transform your business

Integrate and extend existing business processes

Easily re-purpose existing information assets for new initiatives and products

Quickly tie in external information and application resources

Conduct your business independent of IT infrastructure issues such as platforms, applications, security, scalability, integrity etc.

Integration is the foundation of Business Agility!

What customers want: What customers want: Unlimited Business AgilityUnlimited Business Agility

Business Aspects Define Business Processes as services that will be ...

Standardized

Documented

Evolved

Begin thinking in „open online services“

Credit request

Support request

Contract request

Purchasing request

Business Service Center AspectsBusiness Service Center Aspects

Technical Aspects Implement services as Web-Ready Application Interfaces

Collect information about services in services repository

Integrate existing applications into single view

Integrate external applications into services centers

Business Service Center AspectsBusiness Service Center Aspects

XMLi – XML Based IntegrationXMLi – XML Based Integration

Summary: Summary: The Semantic Web – A Call to Action !The Semantic Web – A Call to Action !

Total Office Integration

Who? What? How?

XML • Self-describing data

• Universally accessible

Web Services• Self-describing logic

• Flexible architecture

• Maximum reuse of existing systems

Metadata

(Information about information)

• Where is it located

• How is it accessed

Semantics

(How the information is used)

• Who uses it

• How do they use it

• Is there related information

XMLi Integration StrategyXMLi Integration Strategy

LEGACY APPLICATIONS

WebService

Generation

Adapters

Wrapping

Mapping

PACKAGED APPLICATIONS

CUSTOMAPPLICATIONS

InformationResources

LEGACY APPLICATIONS

XML Adapters

• Legacy Applications• ADABAS-Natural

• COBOL-CICS

• DB2/IMS/VSAM

• AS/400

• Packaged Applications• ERP

• CRM

• SFA

• SCM

• Custom Applications• RDBMS

• EDI

• Files

XMLi Integration Strategy – Step 1: Web Services GenerationXMLi Integration Strategy – Step 1: Web Services Generation

XML Broker

• Structure and content validation

• Intelligent routing

• Transformation and aggregation

• Security filters, digital signatures and encryption

• Enterprise messaging

• Guaranteed delivery

• Enterprise Security

EnterpriseService

Bus

Transformation

Routing

Messaging

Storage

Indexing

Querying

XML Repository

• Document and message persistence

• Storage and management of XML and non-XML data

• Optimized queries and caching

• Transactions and Locking

• Security and High Availability

XMLi Integration Strategy – Step 2: Services Oriented IntegrationXMLi Integration Strategy – Step 2: Services Oriented Integration

Dynamic Data Aggregation

and Distribution

• Utilize metadata to dynamically generate access

• Aggregates results into a single XML view

• Provides bi-direction update capability

• Provides multi-channel output distribution

Metadata Repository

• Data Dictionary

• Web Services Registry (UDDI)

• Business Dictionary

• Security Administration

• Configuration Management (WebDAV)

Channels

PORTALS

APPLICATIONS

MOBILE

PRINT

GRAPHICS

DOCUMENTS

Output

XML/HTML

EMAIL

EnterpriseInformationIntegration

AggregationFilters

Distribution

Data Dictionary

Business TermsUsers & Roles

Service Registry

Metadata

XMLi Integration Strategy – Step 3: Information IntegrationXMLi Integration Strategy – Step 3: Information Integration

WebService

Generation

AdaptersWrapping

Mapping

EnterpriseService

Bus

TransformationRouting

Messaging

EnterpriseInformationIntegration

Information Integration

AggregationFilters

Distribution

Channels

PACKAGED APPLICATIONS

LEGACY APPLICATIONS

CUSTOMAPPLICATIONS

Data Dictionary

Business TermsUsers & Roles

Service Registry

InformationResources

EXTERNALSERVICES

PORTALS

APPLICATIONS

MOBILE

PRINT

GRAPHICS

DOCUMENTS

Output

XML/HTML

EMAILMetadata

StorageIndexing

Querying

XMLi: Total Business IntegrationXMLi: Total Business Integration

apps: intra/internet, km, search sys. , multi.pub.devices, detecting …

benefits: increased revenue by providing fast and accurate search results. relevance is

extremely high and the breadth of results is kept to a minimum.

decreased effort and expense at time of categorizing documents. with data relationships pre-defined, you need only link into the “web of meaning” at one location. as the ontological database is increased, the effort needed to categorize and classify documents decreases.

increased relevance leads to reduction in cost of re-acquiring information. employees looking to educate themselves on a new subject area can do so more efficiently.

automatic interoperability

reduced time and resources needed for full integration

visualize relationships

Semantic Web: Expected BenefitsSemantic Web: Expected Benefits

File Transfers Porgram coding

Message Oriented Middleware (MOM) Program coding

Enterprise Application Integration (EAI) Proprietary scripts

Enterprise Service Bus (ESB) XSLT Stylesheets

Application Integration

Terc

hnolo

gic

al E

volu

tion

Semantic Web: Where is the semantic information?Semantic Web: Where is the semantic information?

Manual Reports Program coding

Extraction/Transform/Load (ETL)

Proprietary scripts

Federated Researches Search routines

Semantic Integration Information model

Application Integration T

ech

nolo

gic

al Evolu

tion

Semantic Web: Where is the semantic information?Semantic Web: Where is the semantic information?

Cliente

ProdutosContatos

ProblemasEnvios

PerfilDa

Empresa

Contatodo

Usuário Cria

Resolvido por

TemEntregue por

Ver também

PossuiTem

InformaçãoSobre

ProdutoDescreve

Informaçãosobre

Competidores

Ver também

Resolve

Contatode

Envio

Informaçãode Contato

Entregue a

Correções

Entregue por

Usa

Contatode

Vendas

Compra

Vendedor

Vende

Gerencia

CustomerSupport Cria

Contatos

Tem

Atualiza

Suporta

Suporta

Vende para


Modelo Físico

Importa Metadados

Mapeia no Modelo de Negócio

Contrói Pesquis

a

ImplementaWeb Service

Integrator Studio

Aplicação do Usuário

Web Service

Servidor Semântico

Modelo de Negócio

Metadados

Início

Fim

Semantic Web: Semantic Integrator StudioSemantic Web: Semantic Integrator Studio

Semantic Web: A Semantic Web: A Brave New WorldBrave New World for information usage for information usage

Daniel G. [email protected]

Daniel G. Teivelis [email protected].

Documents

Transcript of Daniel G. Teivelis [email protected].