ebXML Registry and Repository
R
E
G
R
E
P
발표: 김 종락
2001.3.19
(주) 이노디지털 jjlkim@innodigital.co.kr tel : 3772-6131
R
ebXML Architecture
E
G
R
E
P
Business Business Core Data
Process Context For Messages Built With Blocks
Register
Designtime
Implement one BP Designtime
Partner Role Implement other
Specification Partner Roles
CPP CPA CPP
Business Business
Service Transport Service
Interface Interface
Package
Internal Business Internal Business
App App
Runtime
R
E
One of Simple Scenario
G
R
E
P
• Supplier Convert Biz processes to RR/BP
• Supplier & Registry Register Profile with RR
• Buyer & Registry Register/Retrieve Profiles
• Buyer & Registry Get information about seller
• Buyer & Seller CPA negotiation
• Buyer & Seller Exchange business documents as
per the automotive vertical use case and/or the
retail vertical use case
R
Architecture of ebXML Collaborations
E
G
R
E
P
BP CC RegRep
BPEng Process CPP
Definition
Process Partner
Evolution Discovery
Electronic
Process Business Partner
Management Collaboration Sign-Up
BPM CPA
Process Electronic
Execution Plug-in
BSI
TRP/
BSI
R
E
Design Time to Run Time
G
R
E
P
Business Core
Context
Process Components
1 4 9 Define
Existing Business
BP Tool
Process Doc
2 Convert to 5 Convert to 8 10
Create Doc
Query CC XML
XML XML
3 6 7 11
Registration Registration Retrieve BP Registration
Registry
Repository
12 Retrieve TP 15
Registration
Role
13 Link Form TP 14
Business
Service Profile
Business Business
Service Service
16 Execute
TR&P Business
Process
TR&P
Information Model Public View
R
E
G
R
E
P
a dynamic way
to add arbitrary attributes
DUNS number, SS Number
Or Alias Name of Organization
R
E
Information Model Inheritance View
G
R
E
P
Object Versionable
AuditableIdentity AuditableEvent RegistryEntry
IntrinsicObject ExtrinsicObject
Package Organization ClassificationNode Association ExternalLink
Classification
R
E
G
R
Information Model
Classification View
E
P
Object
Versionable
IntrinsicObject Classification Interface
Interface 0..* 0..* RegistryEntry
ClassificationNode
classificatioNodes classifiedObject
0..1 0..*
0..*
associatedObjects
Parent
Association
classification scheme supporting
single level as well as multi-level classifications
R
E
Context sensitive classification
G
R
E
P
:Classfication
context fromObjectRef
toObjectRef
isLocatedIn:ClassficationNode acmePartProfile:RegistryEntry
japan:ClassficationNode
shipTo:ClassficationNode myParcelServicePartProfile:RegistryEntry
toObjectRef
context
fromObjectRef
:Classfication
R
E
G
R
Classification Instance
Diagram
E
P
cppToIndustryClassifiication:Classfication
sourceObject targetObject
yourDadcarIncCPP:ExtrinsicObject industry: ClassficationNode
R
E
G
R
Classification Scheme (Context) Usage
E
P Example
• Industry Find all Parties in Automotive industry
• Process Find a ServiceInterface that implements a Process
• Product Find a business that sells a product
• Locale Find a Supplier located in Japan
• Temporal Find Supplier that can ship with 24 hours
• Role Find All Suppliers that have a role of “Seller”
R
E
XML Filtered Query
G
R
E
P
• RegistryQuery
– RegistryEntryQuery
– AuditableEventQuery
– ClassificationNodeQuery
– RegistryPackageQuery
– OrganizationQuery
• GetRegistryEntry
• GetRepositoryItem
• Registry Filters
• XML Clause
Constraint Representation
R
E
G
R
E
RegistryEntryQuery
P
R
E
G
R
E
P
GetRegistryEntry
R
E
What’s been done in Vancouver
G
R
E
P
• RIM Related
– Vote btn SQL query and XML Filterd
Query Majority support for XMLFilterd
Query
– Hot Debate over Repository Modeling
Extrinsic Object is enough to keep
meta data about the contents residing
somewhere outside repository
R
E
What’s been done in Vancouver
G
R
E
P
• Area to be elaborated more
– Internalization
– External Code link
– (1) the coding scheme values are not native to the registry or
– (2) the SO does not wish to contribute the classification value to the
ClassificationNode tree.
– Audit trail
• Term Change
– Managed Object Registry Entry
– Managed Object Content Repository Item
R
E
G
R
Changes After Vancouver
from RIMv0.54 v0.58
E
P
-Classification is now a sibling of Association instead of sub-class (fig 2). It's
interface definition now adds attributes classifiedObject (was inherited
sourceObject) and classificationNode (was inherited targetObject). Removed
pre-defined association types CLASSIFIED_BY and CLASSIFIES. Updated
various figures. Of note is the context sopecific classification figure which had a
mistake.
-Added slotType attribute to slot. Updated slot use in light weight classification (and
RS section on I18N) to use specific slotTypes.
-Added statement on contentURU attribute that it must be resolvable by the registry.
-Changed all enumeration to be Classification scheme based. They are all
extensible now
-path attribute in ClassificationNode now says it is an XPATH syntax
R
E
G
R
E
P
For Innovations in Business
by DIGITAL Velocity