Cultural Heritage in REGional NETworks REGNET T1.4: Development of the system specification

Cultural Heritage in REGional NETworksCultural Heritage in REGional NETworks

REGNETREGNET

T1.4: Development of the system T1.4: Development of the system specificationspecification

October 2001 Project presentation REGNET

2

ContentsContents

ProcessRegnet organisationAnalysis

Use caseFunctional architecture

Technical architectureRequirementsTechnical architectureWeb services, ebXML, Topic Map, Wap


REGNETREGNET

ProcessProcess


4Architecture oriented processArchitecture oriented process

Business

Design

Implementation …

Engineering

TechnologyAnalysis

Business architecture

Functionalarchitecture

Logicalarchitecture

Systemarchitecture

Deploymentarchitecture

Technicalarchitecture

Softwarearchitecture

Business needs,

Organization

Functionalneeds

Object structuring and modeling rules

Use Casescategories

Business categories

Technicalcategories

Physical

platform

Technicalneeds

Architectural principles

Physicalarchitecture

Software

platform

Materialneeds

Physicalarchitecture


REGNETREGNET

OrganisationOrganisation


6

REGNET organisationREGNET organisation


7Building blocksBuilding blocks

REGNET - ElectronicPublication Subsystem

RE

GN

ET

- On

tolo

gy

(Meta

da

ta) S

ub

sy

stem

REGNET - eBusiness Data Management

REGNET - Cultural Heritage Data Management

REGNET - PORTAL

Subsystem - 2

Subsystem - 3Subsystem - 4

Data Entry

Harvester

ThesauriAuthority Files

Meta Data

Configurator

ParameterBusiness Cases Meta Data

Schemata

User DataProvider Data

DataBaseMana-gement

DataBaseMana-gement Meta Data

Subsystem - 5

Search Engine

Configurator

ParameterBusiness Cases

Subsystem - 7

catalogue

DataBaseMana-gementCatalogue

Meta Data

Subsystem - 6

B2BB2C

Configurator

ParameterBusiness Cases

Subsystem - 9

ProductsServices

DataBaseMana-gement Products

Services

Subsystem - 1

Digital ContentMeta Data

DataBaseMana-gement Digital Content

Meta Data

Subsystem - 8

WorkflowProduct Spec.

Produc-tion

Process

Th

e RE

GN

ET

Bu

ildin

g B

lock

s


8

ComponentsComponentsRegnetNetwork

RegnetSystem1..*

1

1..*

1

Component

Node1..*

1

1..*

1

1..*

1

1..*

1


9

REGNET organisationREGNET organisation

Ontology Master Node

Manage ontology data

Cultural Service Centers

CIO1

CSC 1 CSC 2 CSC 3

Cultural Institutions and Organisations

CIO2 CIO3CIO4 CIO5

CIO6

<<ebXML>>

<<ebXML>><<ebXML>> <<ebXML>>

<<ebXML>>

<<ebXML>>

<<ebXML>> <<ebXML>>

<<copy>><<copy>>

<<copy>>OO

Outsourcing organisation

<<ebXML>>


REGNETREGNET

ANALYSISANALYSIS


11

AnalysisAnalysis

ActorsAn actor in a use case is an external agent that uses or interacts with the system.

Use CaseDescribe the sequence of events of an actor using a system to complete a process.

Are a narrative description of a business process.

Use case diagram


12

ActorsActors

aUser Content Provider Museum's Professional

Artist's community

Library's Professional

Archive's Professional

Administrator

Customer

Supplier

Manufacturer

Services firm

CSC Technician

Visitor


13

Use Case diagram (example)Use Case diagram (example)

Access

(from Use Cases)

defines trade terms and conditions

aAdministrator

(f rom Actors)

aSupplier

(f rom Actors)

manages access rights and profiles

aUser

(f rom Actors)

registers as MarketPlace supplier


14Functional ArchitectureFunctional Architecture

RegNet-Site

Electronic PublishingOntology System

Cultural Heritage Data Management

Portal eBusiness Data Management

Connector

DataGeneration

Search &Retrieval

e-Business

Portal

KnowledgeBase

RepositoryManagement

ReferenceSystem

ProductCatalogue

Management

Procurement& Delivery

ElectronicPublishing

Regnet Connector


REGNETREGNET

Technical ArchitectureTechnical Architecture


16

Main technical requirementsMain technical requirements

Easy management of new functionalities

Distributed and modular architecture

Integration:B2B: collaborative environment

A2A: legacy system

Consortium skill

Security

Internationalisation


17Technical architectureTechnical architecture

Regnet Portal

eBusiness

EBusiness data

eBusiness

Procurement and delivery

Product catalogue

management

Repository CH data management

Data generation

Ontology data

Search and retrieval

Reference system

Repository management

Catalogue

Ontology

Knowledge base access

Reference system access

Electronic publishing

Electronic publishing

Regnet Connector

SOAP/XML

SO

AP

/XM

L

Regnet Front-End Regnet Back-End


18

Engineering point of viewEngineering point of view

Portal: Apache/JetSpeed

Nodes: PHP, Java/J2EE

Ontology: TopicMap (XTM), SHOE

Database: XML DataBase

Middleware:Web Services: SOAP, WSDL, UDDI

B2B collaboration: ebXML

Catalogue exchanges: catXML


REGNETREGNET

Web ServicesWeb Services


20

What are Web ServicesWhat are Web Services

Why?Allow Internet integration of heterogenous systems to improve partners exchange

How?By marshalling with XML and HTTP business services in order to be remotely queried by external clients.

GoalAllows to build application in an Application Services Providers spirit


21

The winner stackThe winner stack

HTTP HTTP for Internet protocol (+ SMTP, FTP) XMLXML for data (+ binary if necessary: images, sound …)SOAPSOAP (Simple Object Access Protocol) for envelop and queryWSDL WSDL (Web Service Description Language) (Web Service Description Language) for standard descriptionUDDIUDDI (Universal Description, Discovery and Integration) for publication / search / retrieval

Security: HTTP/SSL


22

SOAPSOAP

SOAP: Simple Object Access Protocol

Standard W3C

Allows RPC over Internet by using HTTP (or SMTP, FTP) and XML to support query and answer.

What SOAP is not:

Don’t specify message semantic

Independent of programming langages

Don’t replace CORBA, or DCOM, or RMI

A SOAP message is XML composed of:

An optional header

A body which includes the query or the answer


23

Service-Oriented ArchitecturesService-Oriented Architectures

Service-Oriented Architectures & Web service collaborations

1 2

3

Registry

RequesterProvider

PublishUDDIWSDL

InquireUDDIWSDL

Invoke

SOAP


24The Business Value of Web The Business Value of Web ServicesServices

Interoperable systems were in principle possible before, using solutions such as CORBA or EDI

So, why Web Services?

Easier to create and deploy

Language and platform neutrality

HTTP servers everywhere

Widely accepted standards

Firewalls already accept HTTP


REGNETREGNET

ebXMLebXML


26

Mission:To provide an open XML-based infrastructure enabling the global use of electronic business information in an interoperable, secure and consistent manner by all parties.Enables entreprises of any size, in any location to meet and conduct business through the exchange of XML-based messages

Technologies:UML for modelisationXML for exchanged informationInternet protocol: HTTP, SMTP, FTP, …


27

Registry and repositoryRegistry and repository

Registres: 2 partsRegistry ServicesRegistry Services: access services

Registry Information ModelRegistry Information Model: data models

Distributed registries:Private

Public

Registry store:Companies profiles (CPP)

Technical agreements between companies (CPA)

Domain or community vocabulary and process


28

Profiles (1/2)Profiles (1/2)

Capabilities of companies:CPPCPP: Collaboration Protocol Profile

CPACPA: Collaboration Protocol Agreement

CPPCPP: Capapility of a company to do eBusinness in the form of business processes of an industry or business domain (UML, XML)

CPACPA: Set of concrete possible interaction between partners.


29

Profiles (2/2)Profiles (2/2)


30

Core ComponentCore Component

Common business terms, nouns, concept and give them a neutral name

Date, time

Defined in XML

Allows to build complex data structure


31

Business processBusiness process

Business processes defined choregraphy of exchanged documentsModelisation with UML, optional traduction to XMLAs UN/CEFACT OPEN-EDI model:

Business Operational View (BOV): business relationship between companies.Functionnal Service View (FSV): information technology aspects of the relationship to support BOV.


REGNETREGNET

Wireless accessWireless access


33


34

HTTP

Wireless

Portal

Content

JSP Servlet

Client

WAE User

Agent

Midlet WML

Request URL

Response (document) XML

Portal

Content

JSP Servlet

Client

WAE User

Agent

Midlet WML

Gateway

Encoders And

Decoders

XML

Encoded Request

Encoded Response

Request URL

Response

(document)

WSP HTTP

Wireless Wired

Portal technical architecturePortal technical architecture


REGNETREGNET

Topic MapTopic Map


36

Topic Maps (XTM)Topic Maps (XTM)

ISO IEC 13250Add semantic to large amount of unorganized informationOptimized for navigationTopic:

Anything that is a nounMany links with all its occurrences (XPointers)Have namesGrouped into topic typesRelated using associations

XTM: XML Topic Maps (1999)


37

Topic Map ComponentsTopic Map Components

Theme

InformationObject

(f rom Use Case View)

SuperType

Occurrence

role : StringTopName

Topic

id : String is-a

Association

AssociationRole

role : StringInstanceOf

0..1

InstanceOf

0..1

Scope

0..n

InstanceOf

0..1

Specifies1..n

Scope

0..n

is-a

Scope

0..n

Types 0..n


38Topic MapTopic Map

Documents

Cultural Heritage in REGional NETworks REGNET T1.4: Development of the system specification