reg-repreg-rep ebxml registry and repository ecom seminar saturday 11/11/2000
TRANSCRIPT
REG-REP
ebXML Registry and ebXML Registry and RepositoryRepository
ECOM SeminarSaturday 11/11/2000
REG-REP
Presented byPresented by
Scott NiemanProject Leader: ebXML Registry and Repository
Solutions Director: e-Business Integration
Norstan Consulting
REGREP Mission StatementMission Statement
• The ebXML registry and repository project team will deliver requirements and specifications for the creation and use of a registry and repository. The registry and repository will be comprehensive, distributed, business analysis driven, and support the runtime and development viewpoints of the ebXML architecture.
REGREP Project ObjectiveProject Objective
• To define the business and functional requirements for an ebXML registry and repository
• XML-based interfaces to interact with the registry and repository
REGREP Deliverable ScopeDeliverable Scope
• Develop a functional requirement document – use cases and other UML artifacts – detailed prose describing how to use the system – XML Interfaces: application-programming interface
• Multi-phased approach for the specification of supporting services – limited to essential features
• ebXML does not intend to implement a registry and repository itself
REGREP Work Items: SpecificationsWork Items: Specifications
• Business Requirements (complete)
• UML Model– Business Domain Model– ebXML Registry Services; XML Service
Interfaces– ebXML Repository Information Model
REGREP Business RequirementsBusiness Requirements
• Storage of items in their original form• Distributed Registries; “single global repository” no longer a valid
concept in Internet age• Apply Best Practices;
– reuse of best of breed if possible– Future proof specifications
• Features• Allow the query and retrieval of items• Support a standards development workflow• Allow the comparison of object to a checklist of features; e.g., ensure
consistent UML models• Allow the transformation to / from different forms, e.g., UML/XMI to
XML, tpaML formation • Allow the discovery of a registry’s specific interfaces/ capabilities• Provide a logging mechanism such as transactional events
REGREP
Architecture: Distributed Architecture: Distributed RegistriesRegistries• Publish and Subscribe Architecture• Association of objects between registries• Metadata Exchange
– XMI probable
• Monitor of events– Versioning– Submission of like-objects
• Publish via ebXML Messaging Service• Multi-level subscription
– Service Interfaces– Collections of like-objects– Individual objects
REGREP
Registry of Registries
Repository
Search App
Repository …
OASIS or other official site
Return list of hits plus all repositories that were not accessed. From there the user could link to the document of choice.
1
2
3Repository
Original document in intended format including multimedia attachments
Registry
Registry
Repository
Repository Repository …Repository
Registry …
A global search may go through potentially thousands of registries each of which may in turn have thousands of repositories.
DNS-like Registry of DNS-like Registry of RegistriesRegistries
REGREP Business DomainBusiness Domain
• Define the scope of the “system”– Driven by ebXML Architecture– Driven by ebXML Requirements
• High Level Use Cases• Actor Generalizations; hierarchical view of all role
players• Domain Package Diagram; partitions use cases and
services that support them– ebXML Specified Services– Registration Authority Specified Services; value added
• Traceable to the Business Requirements
REGREP Domain Use CaseDomain Use Case
• Register Company
• Submit Object• Store Object• Classify Object• Subscribe• Retrieve• Map between
Specifications
Software Developer(f rom Actors)
Semantic Mapping Specialist(f rom Actors)
Subscribe to Service Interfaces
Submitting Organization
(f rom Actors)
Submit Object
Generate Software CodeCreate Mapping between one or more Registered Objects
ebXML-Compliant Business Application
(f rom Actors)
Party
(f rom Actors)
Register Company
Classify Submission
(f rom Submission)
Store Registered Object
<<includes>>
Search and Retrieve Object
<<extends>><<extends>>
Administer Registry and Repository
Registration Authority
(f rom Actors)
REGREP Actor GeneralizationActor Generalization
Party
Guest User
Sof tware Dev eloper
Administrator
ebXML-Compliant Business Application
Registration Authority
<<instantiates>>
Business User
Sof tware Agent
Business Process Analy st
Common Business Object Dev eloper
Business Domain Expert
Semantic Mapping Specialist
Security Policy is managed the RA
Legal Policy
acts on behalf
<<depends>>
Technical Modeler Technical Assessment
Submitting Organization
Responsible Organization
Corporation
Industry Consortium
2..n
0..*
2..n
0..*
0..*0..*
• ISO 11179 terminology
• Extended as needed
REGREP Domain Package DiagramDomain Package Diagram
• Used to organize use cases and state machines– Services– UI– Applications
• Services are dependent on each other– Messaging– Storage– Security
Registry<<Service>>
Repository<<Service>>
Business Application
<<Application>>Development Tool<<Application>>
Mapping Tool<<Application>>
Submission<<UI>>
Specification / Standards Development Life Cycle
<<UI>>Public
Availability
<<UI>>
ebXML Messaging<<ebXML-TRP>>
Company Registration
<<UI>>
Application Programming Interface Definition
(from Design Workflow)
RA Administration
<<UI>>
REGREP Registry ServicesRegistry Services
• Life cycle management• Query• Interface Discovery Service • Logging• Publish• Subscription• Library Control System• Transformation• Workflow• Quality Assurance Service
Transformation<<Service>>
Quality Assurance
<<Service>>Workflow
<<Service>>
Query<<Service>>
Interface Discovery
<<Service>>
Library Control System
<<Service>>
Life Cycle Management
<<Service>>
Logging<<Service>>
Publish<<Service>>
Subscribe<<Service>>
Security<<Service>>
REGREP
ebXML Registry ebXML Registry SpecificationsSpecifications• ebXML Business Domain Specification
– ebXML specified services vs. RA specified services
• ebXML Registry Services• ebXML Registry Information Model
ebXML Project Teams Software Developers
ebXML Registryand Repository
Business Domain
ebXML Registry andRepository
ProjectPlan
ebXML RegistryServices
Specification
ebXML RepositoryInformation Model
Specification
ebXML BusinessRequirements
ebXML TechnicalArchitecture
REGREP ebXML Specified ServicesebXML Specified Services
• Life cycle management
• Query
• Interface Discovery Service
• Logging
• Publish
• Subscription
REGREP
ebXML Registry Service - ebXML Registry Service - InterfacesInterfaces
Party Registration
Object Life Cycle Querying ObjectsAuthentication &
AuthorizationEnables Pub-Subon Registry Data
Interface Discovery
REGREP
Life-Cycle Management Life-Cycle Management ServiceService• Storage of anything that can be classified;
including classification schemes themselves• Submission• Classification via metadata• Classification of single object by multiple
schemes• Metadata versioning; draft, public review,
standard/ specification• Object versioning; new, deprecation of prior
version
REGREP Life cycle ManagementLife cycle Management
Library Control System
(from Registry)
<<Service>>
This could be a file system
Repository Server would use LCS Service if available
Update Object
(f rom Repository )
Create Object
(f rom Repository )
Copy Object
(f rom Repository )
Delete Object
(f rom Repository )
Version Item
Reserve ObjectCheck Out
[isAlreadyCheckedOut=True]
<<extends>>
Check In
Repository Server
(f rom Repository )
[if LCS exists]
[if LCS exists]
[if LCS exists]
LCS Proxy
[if LCS exists]
[if LCS exists]
[if LCS exists]
Create Version History Report
[if LCS exists]
• Typical use cases for object life cycle
REGREP Query ServiceQuery Service
• Ad-hoc Query Construction via Classification Scheme • URI Specific• Browsing via Classification Scheme• Indexing by Classification Scheme• Metalevel independent Schemes support
– Multiple Viewpoints; pickNewRoot() allows support of Topic Maps
– Schemes at all OMG metalevels M0, M1, M2, and M3 (e.g., ebXML BP, UML metamodel, MOF)
• Canonical Query Syntax required– No intent to reinvent the wheel– OQL and Quilt are candidates
REGREP Query Use CaseQuery Use Case
• Guest Users– Ad hoc– Collections– Metadata– Objects
• Applications– Metadata– Objects
Manage Collection
Determine relevancy of items
Create Collection
Retrieve from Repository
Formulate Query
Execute Query
ebXML-Compliant Business Application
(f rom Actors)
Search
Select Item from Collection
Retrieve metadata
Guest User
(f rom Actors)
Retrieve Item
<<extends>>
REGREP Interface Discovery ServiceInterface Discovery Service
• This service will allow the discovery of the set of implemented interfaces and detailed operations for a particular registry instance
• Registries are not required to implement ALL of the ebXML Registry Service interfaces
• This may be represented as an XML document, similar to Web Services Description Language without the slippery stuff (SOAP)
REGREP Logging ServiceLogging Service
• Logging of events
• Many types of events
• Single API for all services to call
• XML based syntax
• Model to be defined
REGREP Subscription ServiceSubscription Service
• Allows a Party to subscribe to a Registry and public accessible events– Versioning of an object– Submission of like-objects
• Party can use a check-box approach to subscribe based on roles
REGREP Publish ServicePublish Service
• Allows the monitoring of defined events similar to a listening service
• May listen to logging service events only• Forcing the registry to know when, how, and
who to publish to may not scale • Details to be refined
REGREP
Registration Authority Registration Authority Specified ServicesSpecified Services
• Library Control System
• Transformation
• Workflow
• Quality Assurance Service
REGREP
Library Control System Use Library Control System Use CaseCase
• Classic versioning environment
• Reservation• Message based
alerts
Version Item
Create Version History Report
LCS ServerCheck In
Check Out Reserve Object
[isAlreadyCheckedOut=True]<<extends>>
Promote to Specification
Alert
[if existsReservation= True then Alert.Reservation(1) else void]<<extends>>
[if timeCheckedOut > MaxAllowed]
<<extends>>
<<uses>>
[isPromoted=True] ebXML TRP Proxy
(f rom Messaging Serv ice)
<<uses>>Developer
(f rom Actors)
Registry Proxy
(f rom Registry )
ebXML TRP Server
(f rom Messaging Serv ice)
<<uses>>
notify
[isPromoted=True]
<<extends>>
REGREP Transformation ServicesTransformation Services
• Provide various forms of transformations including– UML to XML generation
• business process definitions• XML Schema and DTD generation
– Trading partner agreement formation
• NOT for production runtime data; i.e., NOT for purchase order, invoice, etc. transformations
REGREP
Trading Partner Agreement Trading Partner Agreement formationformation
Trading Partner Profile
1
Trading Partner Profile
2
TransformationRules
Trading Partner
Agreement**
SourceDestination
**Legal Constraint Prevent Storage of TPA in Repository
• Transformation of two trading partner profiles• Scenario: Trading Partner 1 queries and discovers
Trading partner 2• TPA consummated; sent to Trading Partner 2 for
review and acceptance
REGREP
Conversion of UML Models to Conversion of UML Models to XMLXML
• Business process definitions• XML Schema and DTD generation• Populate classification scheme
XML Schema
XMI(MOF.DTD)
TransformationRules
XML Process Definition
Source Destination
**Classification Scheme assignment or population if metalevel >M0
Populate Classification
Scheme**
REGREP Workflow ServiceWorkflow Service
• Cross reference to the actor instances, their roles, and the services that they are allowed to access
• Supports use cases that are interactions to registry services (<<UI>>, <<Application>> packages)
• Typical scenarios:– Submission of objects by SO– Classification by SO– Elaboration of Classification by RA– Assignment of object review to RA individual– Promotion of submission to new work item, NWI to
specification, review cycles, etc.
REGREP Quality Assurance ServiceQuality Assurance Service
• Allows the definition of a checklist of required elements for a Managed Object
• Allows a submitted object to be parsed and compared to a checklist of required elements; this uses the transformation service
• Scenario: XMI submission of UML model conforming to UN/CEFACT Modelling Methodology
• Output may be a list of missing items
REG-REP
Registry Information Registry Information ModelModel
REGREP
Repository Information Repository Information ModelModel
• Based heavily on ANSI ASC X3.285– Submission to ISO 11179– Refinement of OASIS (XML.ORG) Information
Model
• Key concepts– Classification Scheme support– Managed Objects
• Storage of anything– Flexible associations– Subscription to managed objects (in progress)
REGREP
ebXML Reg-Rep Information ebXML Reg-Rep Information ModelModel
An object instance stored outside the registry, e.g.
on the web
e.g businesses, services, templates, protocol
definitions, schemas, etc
Ability to Group related objects
together as collection
Classifies an object, classifications can be
grouped into hierarchiesA submission may be
more than one Managed object
e.g. a Party that submitted something
Ability to associate items
to others
REGREP
Information Model: Object Information Model: Object Class DiagramClass Diagram
Object<<Interface>>
ManagedObject<<Interface>>
Submission<<Interface>>
External Object<<Interface>>
Association<<Interface>>
Classification<<Interface>>
Organization<<Interface>>
Package<<Interface>>
Versionable<<Interface>>
IntrinsicObject<<Interface>>
ExtrinsicObject<<Interface>>
Contact<<Interface>>
ClassificationNode<<Interface>>
Special Type of Association where the “to” is a ClassificationNode
An object instance stored outside the registry, e.g. on the web
Special Type of ManagedObject critical to the Registry itself
REGREP AssociationsAssociations
• Managed Object to one or more Classification schemes
• Object to Object• Object to Collection of Objects• Classifications to other Classification to
provide context to a classification
REGREP
Traditional Classification Traditional Classification SchemeScheme
• TaxonomiesIndustry
HealthCare Automotive Retail
Geography
USA Japan Europe
Ford:objectChevy:object
Toyota:objectNissan:object BMW:object
REGREP
Examples Classification Examples Classification SchemesSchemes• Business Process Models*
– Industry, international, standards
• Business Message specifications*– XML, EDI; protocol specific– UML; protocol independent
• Trading Partner Profiles*– Capabilities including product service, transport, business process
scenarios, business messages, security
• UML Profiles – metamodels– Stereotypes, tagged values, syntax, semantics, model management
• Common Business Objects• Patterns
– Hillside Community Pattern Language
*ebXML Areas
REGREP Business Use CasesBusiness Use Cases
• Interact with use case ACROSS services• User Interface Based
– Submission– Work in Progress– Ad-hoc Query– Technical Specification Review
• Application to Registry Based– Business Application; e.g., software agents– Mapping Tools; tpaML formation; specification
transformation rule development– Software Development IDE
REGREP
Submission Use Case Submission Use Case DiagramDiagram
software check; returns results
Technical Assessment
(f rom Actors)
Check item against metamodel
(f rom Quality Assurance)
Withdraw Submission
Clarify Item
View Submissions
Validate Item
(f rom Quality Assurance)
Assign/Reject Submission
<<extends>>
Classify Submission
<<extends>>
View Submission Status
<<extends>>
<<extends>>
Research Submission<<extends>>
<<includes>>
Submitting Organization
(f rom Actors)
notify
comments
comments
Submit Object
Transfer
Store Object
(f rom Storage Serv ice)
Create Object
(f rom Repository )
<<includes>> <<includes>>
• example
REGREP
Company Registration Use Company Registration Use Case DiagramCase Diagram
Perform Conformance TestReview Organization Creditials
Register as Submitting Organization Register ebXML Business
ApplicationAuthorize Registration Request
<<extends>><<extends>>
Registration Authority
(f rom Actors)
Submitting Organization
(f rom Actors)
notify
Software Developer(f rom Actors)
notify
Review Intent for Submission Types
Review Registration Status
(f rom Security Serv ice)
[if RA]
<<extends>>
• Viewpoints:– SO creates
Specifications– SO creates software
REG-REP
What about Universal What about Universal Definition, Discovery, Definition, Discovery,
and Integration and Integration (UDDI]??(UDDI]??
REGREP Comparing UDDI & ebXMLComparing UDDI & ebXML
UDDI
•White and Yellow pages -Business & Service definitions•Binding Templates describe how to exchange messages•Flexible categorization of businesses and services•Specific categorizations defined•SOAP based APIs for registration and search – concrete syntax•Protocol for Replication between operators•Agreement to operate/replicate registries
ebXML
•Reg-Rep can hold Business and Service specifications plus much more•TP (CPP) used to define message exchange for Reg-Rep•Flexible categorization of anything in registry •Ability to submit any classification schemes; BP, CC, TP important•General Service Interface definitions, mapped to TRP & XML DTDs•Distributed; No replication; publish-subscribe interactions•No need to replicate; information owner manages their own knowledge
REGREP
Possible UDDI Binding to Possible UDDI Binding to ebXML Reg-RepebXML Reg-Rep
UDDI Client ebXML RegistryClient
UDDI Appl
find_businessgetClassifiedObjects(Business)
REGREP
Plan: Registry Business Plan: Registry Business DomainDomain
Registry Information Model
(QRT 15-12-2000)
V1.0
Geneva Meeting
V2.0
Vienna Meeting
•Actor Generalization•Domain Use Case•Package Diagram•ebXML Registry Services•RA Registry Services
•State Machines•Conformance Requirements
REGREP
Plan: Registry Information Plan: Registry Information ModelModel
Registry Information Model
(QRT 15-12-2000)
V1.0
Geneva Meeting
V2.0
Vienna Meeting
•Manage Object•Manage submissions•Manage XML based classification schemes•Classify Managed Object
•Alternative contextual Naming•Collection based operations (deprecation)•External Coding Schemes
REGREP Plan: Registry ServicesPlan: Registry Services
Registry Information Model
(QRT 12-1-2001)
V1.0
Geneva Meeting
V2.0
Vienna Meeting
Object Management Service
•Create•Deprecate•Approve•Register Company•Versioning
•Alternative contextual Naming
Query Service •Drill down•Ad-hoc query (adoption of a standard syntax)
•Keyword
Interface Discovery •Discover Services•Bootstrapping•Beacon
•Discover Operations within Services
REGREP
Plan: Registry Services Plan: Registry Services (cont)(cont)
Registry Information Model
(QRT 12-1-2001)
V1.0
Geneva Meeting
V2.0
Vienna Meeting
Security Service •Authentication •Role- based authorization
Publish / Subscribe
Service
•Perhaps in Phase1 if time permits
•Subscribe•Publish
Logging Service •Logging from any service