Title: The OASIS Symposium on the Future of XML Vocabularies
1The OASIS Symposium on the Future of XML
Vocabularies
Multi-Layer XML Data Model for EPC/RFID Ash
Parikh Robert Smik
2Presentation Agenda
- Introductions
- The Next-Gen Supply Chain
- What Makes XML Ideally Suited for EPC/RFID Data?
- The Multi-Layer Data Model Vocabulary And Schemas
For EPC/RFID - The MLDM and Other OASIS Standards Working
Together In The EPC/RFID Domain - Benefits of the MLDM
- QA
3Introductions
4About Us
- Speakers
- Ash Parikh (ash.parikh_at_rainingdata.com)
- Director of Development And Technology -
Enterprise Applications Group, Raining Data
Corporation - Robert Smik (robert.smik_at_rainingdata.com)
- Lead Architect - Enterprise Applications Group,
Raining Data Corporation - Raining Data Corporation
- A Public XML, Web Services and Data Management
Software Company - Over 30 Years of Successful Operating History
- 22m Revenue Per Year
- Public Company (RDTA)
- Customers Successes Across All Industries
- Active on Standards Bodies / Orgs
- OASIS, EPCGlobal, W3C, MIT Auto-ID Labs,, JCP,
CDISC, HL7
5The Next-Gen Supply Chain
6The Next-Gen Supply Chain Is
- The Next-Gen Supply Chain Is Made Up Of New
Technologies That Provide A Greater Degree Of - AUTOMATION
- VISIBILITY
- CONTROL
- The Next-Gen Supply Chain Is Designed To Remove
- TIME,
- COST,
- COMPLEXITY
- . Out Of The Equation
7Our Hypothesis
- The Issue Is That Many Existing And Valuable
Technologies And Standards Are Converging.
- Supply Chain Planning (SCP)
- Supply Chain Event Management (SCEM)
- Supply Chain Integration (SCI)
- Supply Chain Execution Systems (SCES)
- Warehouse Management Systems (WMS)
- Manufacturing Resource Planning Systems (MRP)
- Transportation Management Systems (TMS)
- Global Trade Identification Number (GTIN)
- Global Location Number (GLN)
- Global Data Synchronization Network (GDSN)
- Product Information Management (PIM)
- Customer Relationship Management (CRM)
- Order Management Systems (OMS)
- Enterprise Resource Planning Systems (ERP)
- Web Services Definition Language (WSDL)
- Business Process Execution Language (BPEL)
- E-Business Xtensible Mark-up Language (ebXML)
- Automatic Identification and Capture (AIDC)
- Radio Frequency Identification Systems (RFID)
- Object Naming Service (ONS)
- Electronic Product Code (EPC)
- To Realize Real ROI, The Next-Gen Supply Chain
Should Focus On Using These Technologies To Drive
Visibility And Control Of - Goods
- Funds
- Information
8Next-Gen Supply Chain And The Technology
Evolution
- The Opportunity
- 90 Of Real Gains In Deploying RFID/EPC Solutions
Will Happen In The COLLABORATION Zone. - The Challenge
- Using XML And Web Services Technologies To Work
Together In A Standards-Based Manner To Improve
The Velocity And Flow Of Funds, Goods And
Information Throughout Complex Global Supply
Chains While Reducing Production, Distribution
and Inventory Costs.
9What Makes XML Ideally Suited for EPC/RFID Data?
10XMLs Relevant Benefits For EPC/RFID
- EPC/RFID Data and Supply-Chain Applications In
The Domain - Most of the EPC/RFID Standards Are XML-Based
- Data Should Be Represented In An Hierarchical
Structure - Involves Multiple Data Types EPC, Sensor,
Location, PO, ASN, ePedigree, etc. - Requires Querying and Transformation Of Data
- XML And Related Technologies Such As XQuery,
XSLT - XML Can Embed Multiple Data Types
- XML Can Embed Existing Data
- XML Can Represent Data In A Hierarchical
Structure - XML Can Re-Use Technology And Enable Inter-System
Integrations - XQuery Can Provide A Single Point Of Access To
All Enterprise Systems - XQuery / XSLT Can Be Used To Transform Into and
From Multiple Formats - XQuery Allows the Comparison And Aggregation Of
Data - XML And Related Technologies Have Rapid Adoption
By The Industry
11The Multi-Layer Data Model Vocabulary And Schemas
For EPC/RFID A Joint Research Effort Between
Raining Data Corporation And MIT Web Services
WAN SIG Tentative Release Date July 2005
12The Next-Gen Supply Chain EPC/RFID
EPC NETWORK FUNCTIONAL STACK
FEDERATED EPC NETWORK
13The Multi-Layer Data Model Layers
COARSE GRAINED
XML
XML
GRANULARITY OF INFORMATION AND EVENTS
XQUERY
FINE GRAINED
14APPLICATION LEVEL EVENT (ALE) INTERFACE
- ALE Main API Class will look like this
- define(specnameString, specECSpec) void
- undefined(specNameString) void
- getECSpec(specNameString) ECSpec
- getECSpecNames() List //returns a list of spec
names - subscribe(specNameString, notificationURIstring)
void - unsubscribe(specNameString, notificationURIstrin
g) void - poll(specNameString) ECReports
- immediate(specECSpec) ECReports
- getSubscribers(specNameString) List //of
notification URIS - getStandardVersion() String
- getVendorVersion() String
-
- ECSpec details
- readers List //list of logical reader names
- boundaries ECBoundarySpec
- reportSpecs List //list of one or more
ECReportSpec instances - includeSpecInreport Boolean
ECBoundarySpec, specifies how the beginning and
end of event cycles are to be determined startTri
gger ECTrigger repeatPeriod
ECTime stopTrigger ECTrigger duration
ECTime stableSetIntervals ECTime point
15APPLICATION LEVEL EVENT CONT.
- ECTime, denotes a span of time measured in
physical time units - duration long
- unit ECTimeUnit ? milliseconds
- ECReportSpec, specifies one report to be returned
from executing an event cycle. An ECSpec contains
a list of one or more ECReportSpec instances - reportName string
- reportSet ECReportSetSpec
- filter ECFilterSpec
- group ECGroupSpec
- output ECReportOutputSpec
- reportIfEmpty Boolean
- reportOnlyOnChange Boolean
- ECReportSetSpec CURRENT ADDITIONS DELETIONS
- ECFilterSpec, specifies what EPCs are to be
included in the final report. - IncludePatterns List //list of epc patterns
- excludePatterns List //list of epc patterns to
exclude
16Event Master Data
17Capture - Core Event Types
- EPCISEvent - is intended to serve as a generic
base class for all event types in this module as
well as others. - ObjectEvent - represents an event that happened
to one or more entities denoted by EPCs.
Includes list of EPCs in this object. - AssociationEvent - represents an event that
implies an association between one or more
entities denoted by EPCs. Example aggregation
(different EPCs) - QuantityEvent - represents an event concerned
with a specific quantity of entities sharing a
common EPC class, but where the individual
identities of the entities are not known.
(Individual not reported)
18EPCIS Query Interface
19Schema For L1 Raw EPC/Sensor Data Feed Events
20Schema For L2 EPC Filtered Events
21Schema For L3 EPC Business Events
22Schema For L4 EPC Edge Events
23Schema For L5 EPC Coordination Events
24Schema For L6 Enterprise Application Events
25The MLDM And Other OASIS Standards Working
Together In The EPC/RFID Domain
26The OASIS Standards And The MLDM
CPPA
REQUIREMENTS AND CAPABILITIES OF THE WEB
SERVICE/ TRADING PARTNER AGREM.
WS-BPEL/eb BP
BUSINESS PROCESS AND SERVICE ORCHESTRATION.
ebXML REGISTRY
DISCOVERY AND AGGREGATION
ebMSH
TRANSACTIONS (ACID)
COORDINATION OF WORK BETWEEN WEB SERVICES
ROUTING OF MESSAGES
SOAP
MESSAGE PAYLOAD
EPC NETWORK AND MLDM FUNCTIONAL STACK
OASIS WEB SERVICES STANDARDS STACK
LOGICAL STACK
27Benefits Of The MLDM
28Benefits Of The MLDM
- The MLDM Recommends A Standards-Based XML Model
For Data And Metadata - It Can Be Used For Representing Information And
The Flow Of Information In A Value Chain Covering
All Domains - It Can Be Combined With Other XML-Based Standards
To Enable 100 COLLABORATION Between
Collaborators In The Value Chain - It Can Be Used To Represent And Model Events and
Business Processes Ranging From Coarsest To
Finest In Granularity
29The OASIS Symposium on the Future of XML
Vocabularies
Multi-Layer XML Data Model for EPC/RFID Ash
Parikh Robert Smik