20002000 interfacing registry systems december 2000

Interfacing Registry SystemsInterfacing Registry Systems

December 2000December 2000

VisionVision

“A semantic registry is the key foundation block upon which global electronic business exchanges will be built”.

MissionMission

• Collaboration - give industry groups and

enterprises the ability to share business

semantic information and business process

interfaces.

• Semantics - provide universal infrastructure

that seamlessly delivers semantic integration

into business applications.

• Interfaces - open deployment machine-to-

machine and user web enabled visual.

eBusiness Registry Legal eBusiness Registry Legal RoleRole

• Service that manages and secures business

interaction information in a consistent way

that is compliant with emerging international

standards and technical specifications.

• Provides the means to expose and discover

interchange profiles and distribute and share

common information.

Gap AnalysisGap Analysis

• Subscription Registries – Microsoft Biztalk™ registry and OASIS XML.org provide only limited librarian authority and controls.

• Local registry – provides your own domain, services and presence, that links into and extends what the central registries offer.

• Plus – partner profile management and XML A2A machine interfaces give direct support for dynamically driven eBusiness applications.

AudienceAudience

• Business Analysts – manage business process definitions and partner interchange profiles; classify content by industry domain.

• Business Users – can find what they need to initiate business processes using simple menus and choices.

• Programmers – can publish formal software definitions of process components.

Registry Functional ModelRegistry Functional Model

BusinessAnalyst

Web Interface

InformationProfiles

Distribution

Administration

Program LevelSemantics

Information Engine

Industry Business StandardsRegistry Protocol StandardsebXML, ISO11179, OASIS,

UDDI, xCBL, RosettaNet, Biztalk

Software Developers

Interchange

Web Interface – provides information discovery by classification and domain with intelligent searching.

Administration – allows secure management of the information content

XML interface – callable API that provides automated XML driven content retrieval and submission.

Registry Distribution – allows sharing and distribution of information content.

Registry ComponentsRegistry Components

Registry LayersRegistry Layers

UMLTools

XML Content

Metadata Information Registry/Repository

Web User InterfaceProgram API Support

Business Transaction Generators

Dictionary Content

Transformation Services

Scripting

Domains

Content Discovery

Topics and Packages

Dynamic Process Component Enabling

Industry Dictionary

Business Processes

Business Transactions

Business Forms

HTML forms

XML Calls

Modelling and Workflow Integration

Information Store

Tools and services

High level modelling systems integration

Business Process Definitions

Workflow Control

Interchange Profiles

Communications Layer

2000 ISO11179 IntegrationISO11179 Integration

Strategies and Approaches

Leveraging the Leveraging the ISO11179ISO11179 SemanticsSemantics

• Expose ISO11179 Registry semantics via XML business centric interface.

• Allow programming and development staff to link ISO11179 semantics to XML schema syntax details.

• Provide machine-to-machine API for semantic content exchange.

• Clearly define mission separation for registries – ISO11179, ebXML, OASIS.

ebXML integration ebXML integration approachapproach

ISO11179Registry

ebXML Registry

ebXML interface service

ebXML transport layer

Semantic content store

XML semantic content

PUSHExtractor

XML interface serviceMarked content domain for extractionClassification synchronization

ClassificationsAssociations

Information Interaction Information Interaction ModelModel

C la s s ific a tio nS c he m e

C o ntent Desc rip tio nsR egis try C o ntent

R egis try C o ntent

C o ntent Desc rip tio ns

C la s s ific a tio nIns ta nc e

Classification ModelClassification Model

Registry Classification

Classification Scheme

Classification Instance

Logical Associations or Physical Associations

A classification depends upon a pre-existing specification of a hierarchy of values, names, and codes called a classification scheme. A classification scheme can have an associated classification-instance that is a specific XML structure

ebXML Classification DTDebXML Classification DTD

<!ENTITY % BasicTypes SYSTEM "ebXML-basic-types.dtd">%BasicTypes;<!ENTITY % RegistryHdr SYSTEM "ebXML-metadata-registry-hdr.dtd"><!ELEMENT Classification (RegistryEntryProperties, Classifier+)><!ELEMENT Classifier (Classifier | Classifiers | EMPTYcontent)><!ATTLIST Classifier

Nodename CDATA #REQUIREDNodetype (Member | Classification) "Member"UID CDATA #IMPLIEDNodevalue CDATA #IMPLIEDDescription CDATA #IMPLIED

><!ELEMENT Classifiers (Classifier+)><!ELEMENT EMPTYcontent EMPTY>%RegistryHdr;

What ebXML doesWhat ebXML does

• Trading Profile Management and Discovery.

• Business Process Collaboration.

• Exchange of XML business semantic knowledge.

Communications LayerCommunications Layer

• Support for emerging standards

– ebXML Registry interactions protocol

– ebXML Transport layer (MIME/http based).

– W3C XP Transport layer (SOAP/xml based).

ebXML Information ModelebXML Information Model

OASIS Information ModelOASIS Information Model

OASIS request interface OASIS request interface DTDDTD

Extended secure request DTDExtended secure request DTD

Extended secure response Extended secure response DTDDTD

Relationship of and use of Relationship of and use of GUID/UIDGUID/UID

• Content within the Registry must give access to discovery down to the attribute level via a consistent methodology. In order to enable this functionality, the use of Unique Identifiers (UIDs) is required for all items

• These UID references are implemented as XML attributes, expressed as fixed value attributes for each of the physical XML elements and structures.

• Note: ebXML Registry is currentyl planning to use a machine generated 132 byte GUID that is a random string, not suitable for traditional labelling uses as in ISO11179.

SummarySummary

• Need– extended XML interface that provides selective

controlled access to semantic content of interchanges and business processes.

– Interface design that leverages ISO11179, ebXML and OASIS information models.

– Simple consistent specification for implementers.

• Issues– Classification and Associations– UID and content notation synchronization

• Further thoughts:

– david.webber@XMLglobal.com

Thank Thank youyou

The XML Global Advantage™The XML Global Advantage™

20002000 interfacing registry systems december 2000

Documents

pc interfacing

eng3640 microcomputer interfacing week #5 general...

oasis/ebxml registry information model v2.02 bug … ·...

week #4 parallel io interfacing eng3640 microcomputer...

introduction to...

unit - 5 8051 interfacing andapplications interfacing...

edusatmaterial interfacing

interfacing sensor

interfacing peripherals to computer system or disk...

micro interfacing

06 interfacing

boilermate boilermate 20002000 - gledhill response

interfacing with c++ -...

· pdf file8255 ppi, various modes of operations and...

interfacing 7

interfacing 8255

accolade accolade 20002000 - gledhill spares

boilermate boilermate 20002000 - home - · pdf...

motor interfacing

microcontroller interfacing