The Auto-ID Lab at MIT is using Codeplex to release open source projects. What is CodePlex? CodePlex is Microsoft's open source project hosting web site. You can use CodePlex to create new projects to share with the world, join others who have already started their own projects, or use the applications on Codeplex site and provide feedback. The URL for the AUTO-ID repository on Codeplex is http://www.codeplex.com/autoid
EPCIS Data Generation Tools
This package contains two projects:
1- EPCIS EVENT DATA MODEL:
This project encapsulates the object model that is compliant with the EPCIS specification.
2- EPCIS DATA GENERATOR:
This project provides tools to automatically generate EPCIS Events for the different steps of the supply chain.
EPCIS SoapTestingClient
The SOAP Client builds test SOAP messages for the EPCIS Server. The package includes over 100 queries. Both, the outgoing and return message are written to the console. ProjectLink
The EPCIS 1.0 Specification defines specific functionality that a valid EPCIS Implementation must provide. Branch 0 and 1 outline the specific requirements that must be tested as defined by the specification.
There are four main branches for our testing, the source code supports two branches:
Test Branch 0 – Capturing Application
•0A – Capturing Application using HTTP binding, Project Link
Test Branch 1 – Capture Server
•1A – Capture Server using HTTP binding, Project Link
The REST binding brings a new level of accesibility to the EPCIS
data model. The REST paramaters match the SOAP/XML binding. The binding
is modeled as follows.
REST
Requests are composed by serializing the request component – often in
xml or object model – and composing a URL (Uniform Resource Locator).
The figure below depicts the process: 1) compose a request object; 2)
serialize request content into a URL; 3) make an HTTP request using the
composed URL; 4) server side, deserialize the content contained in the
URL request; 5) bind URL content to EPCIS object model; 6) process and
serve request. Below is a long list of possible requests. Each REST
request is adjacent to the XML/SOAP request for comparison.
Project Link
LLRP Object Model
Follow the link to read a paper on the LLRP Object Model design!
Walk the Pedigree Object Model
Pedigree specifies an architecture for the maintenance and exchange of electronic pedigree documents for use by pharmaceutical supply chain participants.
ALE Object Model
The role of the ALE interface within the EPCglobal Network™ Architecture is to provide independence between the infrastructure components that acquire the raw EPC data, the architectural component(s) that filter & count that data, and the applications that use the data.
EPCIS Object Model
The goal of EPCIS is to enable disparate applications to leverage Electronic Product Code (EPC) data via EPC-related data sharing, both within and across enterprises.
Class Diagram
Application level events class diagram
Class Diagram
Electronic product code information service class diagram
