deciphering rosettanet: a technical overview scott woodgate, microsoft

Deciphering RosettaNet:A Technical Overview

Scott Woodgate, Microsoft

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED.

Can You Answer These Questions?Can You Answer These Questions?

• What is the 30,000 foot view of the technology?

• What are the technical components?

• What challenges will I face?

• What can I expect from RosettaNet in the future?


30,000 ft View of the Technology30,000 ft View of the Technology

Myths

• RosettaNet concepts are extremely difficult to understand.

• There are many technical components.

• Development of the RosettaNet standards is virtually complete.



• It is conceptually very simple.

Create content

Wrap it

Send it

Trading Partner

Initiating trading partner prepares business document payload.




Create content

Wrap it

Send it

Trading Partner

Payload is placed inside XML- and MIME-based transport envelope …




Create content

Wrap it

Send it

Trading Partner

… and sent to trading partner URI using an agreed-upon transport: HTTP(S), SMTP, others in the future.




Create content

Wrap it

Send it

Receive it

Unwrap it

Process content

Trading Partner Trading Partner

Trading partner receives incoming envelope.




Create content

Wrap it

Send it

Receive it

Unwrap it

Process content


Envelope is “opened” to validate and expose processing information and business document payload.




Create content

Wrap it

Send it

Receive it

Unwrap it

Process content


Payload is validated and processed according to RosettaNet specifications …




Create content

Wrap it

Send it

Receive it

Unwrap it

Process content

Trading Partner Trading Partner… and a response is wrapped and returned to the initiating trading partner.




Create content

Wrap it

Send it

Receive it

Unwrap it

Process content

Trading Partner Trading PartnerConversation (exchange protocol or choreography) between trading partners continues according to RosettaNet specifications and may require several iterations.


Technical ComponentsTechnical Components

• Partner Interface Processes (PIPsTM)

• Dictionaries and Codes

• RosettaNet Implementation Framework (RNIF) Core


Technical Components - PIP™Technical Components - PIP™

• Partner Interface Process (PIP)

• PIPsTM (pronounced like Gladys Knight and the …)

• Encapsulate business processes

• Specify structure and format of business document payloads

• Specify activities, decisions, and roles for each trading partner involved in a particular business activity



Categorized by high-level business function (cluster) and sub-function (segment)

Cluster 3: Order Management

Segment A : Quote and Order Entry

Segment C : Returns and FinanceSegment B : Transportation and Distribution

PIP 3A1 - Provide QuotePIP 3A2 - Query Price and AvailabilityPIP 3A3 - Transfer Shopping CartPIP 3A4 - Manage Purchase OrderPIP 3A5 - Query Order StatusPIP 3A6 - Distribute Order Status



• What is the composition of a PIP?

• Distributed as downloadable .zip file from rosettanet.org website

• Specification (.doc) + errata document(s)

• XML DTDs describing schema of business document payload (.dtd)

• Message guidelines (.htm) – cardinality, code lists, definitions



• Specification uses Open-EDI Reference Model (ISO/IEC 14662) concepts

• Business Operational View (BOV)• Business aspects of business transactions

• Functional Service View (FSV)• Technical aspects of business transactions

• Implementation Framework View (IFV)• RosettaNet implementation aspects


From PIPTM3A4 Business Process Flow Diagram in BOVFrom PIPTM3A4 Business Process Flow Diagram in BOV


Table 3-3: Business Activity Performance Controls

Activity N

ame

Acknowledgmentof Receipt

Tim

e to A

ckn

ow

ledg

e A

cceptan

ce

Tim

e to P

erform

Retry C

ou

nt

Is Au

tho

rization

R

equ

ired

?

No

n-R

ep

ud

iation

of

Orig

in an

d C

on

tent?

No

n-

Rep

ud

iation

R

equ

ired

?

Tim

e to

Ackn

ow

ledg

e

BuyerCreate Purchase Order

Y 2hr 24hr 24hr 3 Y Y

BuyerCancel Purchase Order


Buyer Revise Purchase Order


Ro

le Na

me

From PIPTM3A4 Business Process Activity Controls in BOVFrom PIPTM3A4 Business Process Activity Controls in BOV


:Buyer

1. request(:PurchaseOrderRequestAction)

1.1. signal(:ReceiptAcknowledgement)

2. response(:PurchaseOrderAcceptanceAction)

2.1. signal(:ReceiptAcknowledgement)

:Seller

Purchase Order Request Dialog

From PIPTM3A4 Business Transaction Dialog in FSVFrom PIPTM3A4 Business Transaction Dialog in FSV


Purchase Order Request Dialog

Table 5‑1: Business Message and Communications Specification

# Business Message Guideline

Dig

ital S

ign

ature

Req

uired

?

SS

L

Req

uired

?

1. Purchase Order Request Guideline Y Y

1.1 Receipt Acknowledgement GuidelineY Y

2. Purchase Order Acceptance Guideline Y Y

2.1 Receipt Acknowledgement Guideline Y Y

From PIPTM3A4 IFVFrom PIPTM3A4 IFV


From PIPTM3A4 XML DTDFrom PIPTM3A4 XML DTD

<!ENTITY % common-attributes "id CDATA #IMPLIED" >

<!ELEMENT Pip3A4PurchaseOrderAcceptance (

PurchaseOrder ,

fromRole ,

toRole ,

thisDocumentGenerationDateTime ,

thisDocumentIdentifier ,

requestingDocumentIdentifier ,

GlobalDocumentFunctionCode ,

requestingDocumentDateTime ) >

<!ELEMENT PurchaseOrder (

deliverTo? ,

comment? ,

GlobalPurchaseOrderStatusCode ,


Name Definition

deliverTo The partner to which the product must be delivered.

cityName The name of a city.

addressLine1 The first line of a physical address.

addressLine2 The second line of a physical address.

addressLine3 The third line of a physical address.

regionName The name of a state or province within a country.

comment Free form textual comment attached to a business document.

packListRequirements Free form textual description, on the pack list, of requirements relating to the packing of the product.

shipFrom DUNS®+4 number of the location where the product is to be shipped from.

productUnit A unit of product, e.g. an each or a package.

countryOfOrigin Country where product originates.

contractIdentifier The unique number than identifies a contract.

From PIPTM3A4 Message Guidelines – Business PropertiesFrom PIPTM3A4 Message Guidelines – Business Properties


PIP™ SummaryPIP™ Summary


Create content

Wrap it

Send it

Receive it

Unwrap it

Process content


A PIP specifies the structure and format of the business document payload for a particular business activity.

The business content is an XML document.

It also specifies the exchange protocol between trading partners for that activity.


Technical Components - DictionariesTechnical Components - Dictionaries

Why Use Dictionaries and Codes?

Simply…

• To ensure the consistency of information exchanged between trading partners when executing PIPsTM.


Technical Components - DictionariesTechnical Components - Dictionaries

• It is conceptually very simple…

Create content

Wrap it

Send it

Receive it

Unwrap it

Process content


DictionaryDictionary


Codes and DictionariesCodes and Dictionaries

• Partner Identification (DUNS®)

• Product Identification– Product Number (GTIN)– Product Classification (UN/SPSC)– Product Descriptions (Dictionaries)


Where are they used?Where are they used?

• Partner Identification (DUNS®) – used by PIPsTM to uniquely identify trading partners and their locations

• Product Identification (GTIN) – used by PIPs to identify products

• Product Identification (UN/SPSC) – used by Product Information PIPs (Cluster 2) as classification schema


Partner IdentificationPartner Identification

• DUNS® Numbering– “Data Universal Numbering System”– Managed by DUN and Bradstreet

(www.dnb.com)– Nine Digit Number– No Embedded Intelligence– Guaranteed Unique Partner Identifier– Used in Every RosettaNet PIPTM

http://www.dnb.com/dnbhome.htm


DUNS® NumberingDUNS® Numbering

• DUNS® Use Worldwide– 62 Million DUNS numbers worldwide– 26.4 Million in Europe– 23.3 Million in the United States– 4.6 Million in Asia Pacific– 1.6 Million in Canada– 753 Thousand in Latin America– 135 Thousand in the Middle East– 114 Thousand in Africa


DUNS® NumberingDUNS® Numbering

• DUNS® Numbers are Available for “Any Business Location with Unique, Separate and Distinct Operations”

• Not Assigned to Multiple Departments at a Single Location or to Unstaffed Locations


DUNS® + 4 NumberingDUNS® + 4 Numbering

• Extension to DUNS® Numbering

• Controlled by Individual Organization

• Used to Identify Specific Locations or Departments within an Organization


DUNS® Number ExampleDUNS® Number Example

00-825-575 4------------- - | | | ----> Check Digit

|

---------------> Company Identification


DUNS® + 4 Number ExampleDUNS® + 4 Number Example

00-825-575 4 1234---------- - ---- | | | | | | | | ---> Extension * | | | ------> Check Digit | -------------> Company ID

* Extension is Company Assigned


DUNS® Number AdvantagesDUNS® Number Advantages

• Universal Partner Identifier

• Pass Unchanged Through Supply Chain

• Supports “Meta-Customer” Identification– POS / Resale Reporting– Contracts and Pricing


Product SpecificationProduct Specification

• GTIN– Global Trade Item Number– Managed by:

• EAN International(www.ean.be)

• Uniform Code Council (UCC)(www.uc-council.com)

http://ean.eurosecure.net/intro.html



• GTIN– Fourteen Digit Number– No Embedded Intelligence– Guaranteed Unique Product Identifier– Used in Many RosettaNet PIPsTM


Manufacturer’s PartManufacturer’s Part

2 QSP 16 T J 1 222- --- -- - - - ---| | | | | | | | | | | | | ---> Resistance Value - 2200 ohms| | | | | -----> Circuit Designator – Independent Circuit| | | | --------> TR Tolerance 5% and | | | | TCR 100 PPM / C| | | ----------> Packaging Type - Tube| | ------------> Number of Terminals - 16| ----------------> Package Style - QSOP -------------------> Product Class – Thin-Film on Silicon


GTINGTIN

• Global Trade Item Number 0 0678088 20464 3

- ------- ----- -| | | || | | -----> Check Digit| | --------> Sequential Identifier| ---------------> Company Identifier ---------------------> Always ‘0’ in RosettaNet (Other industries use for

“packaging code”)


GTIN AdvantagesGTIN Advantages

• Single Product Identifier Throughout Supply Chain

• Catalog “Owner” Responsible for GTIN

• Eliminates Unnecessary Cross-References

• Future Impacts in Customer Labeling



• UN/SPSC– Hierarchical product classification scheme: individual

commodities represent unique instances of larger classes and families

– 2-digit identification sequence per level– Levels: Segment, family, class, commodity– www.un-spsc.net


UNSPSCUNSPSC

32 12 16 06 XX-- -- -- -- -- | | | | | | | | | ----> Service Type (see below) | | | -------> Fixed thin film resistors | | ----------> Resistors | -------------> Printed components ----------------> Electronic Components and Supplies

Service Type:10 - Rental or Lease11 - Maintenance or Repair12 – Manufacturer13 – Wholesale14 – Retail15 – Recycle16 – Installation17 - Service Parts


Technical DictionariesTechnical Dictionaries

• RosettaNet Technical Dictionary (Information Technology (IT) & Electronic Components (EC))

– Organizes product descriptions into reusable atomic properties and relationships

– Used to search electronic catalogs, maintain technical information databases, generate technical spec sheets, etc.



• Technical Dictionary– Parametric Database of Product Characteristics– Describes Product Form, Fit and Function– Electronically Searchable

• Product Configuration / Design PIPsTM


Technical Dictionary ExampleTechnical Dictionary Example

Product Class: RESISTOR–FIXED – NETWORKS

Class Characteristics:- Rated Dissipation: 0.100 Watt @ 70 C- Resistance: 2200 Ohms- Resistance Tolerance: 5%- Rated Voltage: 14.83V- Limiting Element Voltage: 50V Max- Category Temperature Range: -55 C to +125C- Temperature Coefficient: 100 PPM / C- Resistor Interconnection: Independent Circuit- Terminal Placement: QSOP- Number of Resistance Elements: 8- Number of Terminals: 16- Rated Dissipation for the Network: 0.75 watts @ 70C- Terminal Shape: gull-wing- Resistive Material: Metal Film (Thin-Film)


Technical Dictionary AdvantagesTechnical Dictionary Advantages

• Electronically Searchable Catalog

• Supports More Detail than Part Number

• Can be Integrated with Product Data Management (PDM) and Computer Aided Design (CAD)


POLICY• PKI• TPA• Compliance

SPECS.

IT S

peci

fic

Dic

tiona

ry

and

PIPs

• Network Protocols Base Spec.

• PIP Metamodel• PIP Design patterns • Network Component

Communications Reference Model

EC

Sp

ecif

icD

icti

on

ary

and

PIP

s

RNIF LAYERS

Core

Common

Supply Chain


Technical Components - RNIFTechnical Components - RNIF

• RosettaNet Implementation Framework Core

• RNIF (usually pronounced R-NIF)

• RNIF 1.1 Defines RosettaNet Object (RNO),RNIF 2.0 Defines RosettaNet Business Message

• Specifies how to transport RosettaNet Objects and Business Messages between trading partners’ network applications

• (Remember those PIPsTM? This is how the Business Document Payload is packaged and transported.)




Create content

Wrap it

Send it

Receive it

Unwrap it

Process content


The RNIF specifies an XML- and MIME-based “envelope” in which to put the business document payload.



RosettaNet Object (RNO)

Service Header

Preamble Header + +

Digital Signature

RNIF Version ID + +

PIPTM1B1PIP2A1

PIP3A2PIP3A4

MIME Packaging

Service Message

RosettaNet Business Message

Service Header

Preamble Header

+

MIME Packaging

Encrypted Payload

Container

Delivery Header

Digital Signature

S/MIME Envelope

+ + +

RNIF 1.1 RNIF 2.0

+

Attach-ments

Service Content

RosettaNet

Business Document




Service Header

Preamble Header + +

Digital Signature

RNIF Version ID + +

PIPTM

1B1PIP2A1

PIP3A2PIP3A4

MIME Packaging

Service Message


Service Header

Preamble Header

+

MIME Packaging

Encrypted Payload

Container

Delivery Header

Digital Signature

S/MIME Envelope

+ + +

RNIF 1.1 RNIF 2.0

+

Attach-ments

Service Content

RosettaNet Business Document

The Preamble is the first component of the service message and contains elements that are global to the RosettaNet service and elements that are common to the Service Header and the Service Content.

The Preamble Header is an XML document.



Service Header

Preamble Header + +

Digital Signature

RNIF Version ID + +

PIP1B1PIP2A1

PIP3A2PIP3A4

MIME Packaging

Service Message


Service Header

Preamble Header

+

MIME Packaging

Encrypted Payload

Container

Delivery Header

Digital Signature

S/MIME Envelope

+ + +

RNIF 1.1 RNIF 2.0

+

Attach-ments

Service Content


Technical Components - RNIFTechnical Components - RNIFThe Service Header contains:

• Process Controls• Transaction Controls• Action Controls• Signal Controls

The Service Header is an XML document.



• Process Controls identify the RosettaNet PIPTM, version, sender and receiver services, process instance ID, etc.

• Transaction Controls contain info relating to the transaction like global transaction code, instance ID, etc.

• Action Controls contain info related to a specific PIP action. (like is this request or response)

• Signal Controls contain info related to a specific PIP signal. (like what kind of signal is this)



OSI LayeredUbiquitous Communications

Reference Model

Internet and WWWProtocol Stack

RosettaNet Layerse-Business Communications

Reference Model

Network Layer

Data Link Layer

Physical Layer

Application Layer

Session Layer

Transport Layer

HTTPS

SSLv3

TCP/IP

HTTP

Process Layer

Transfer Layer

Agent Layer

Service Layer

Security Layer

Action/Signal Layer

Transaction Layer



Service Header

Preamble Header + +

Digital Signature

RNIF Version ID + +

PIPTM1B1PIP2A1

PIP3A2PIP3A4

MIME Packaging

Service Message


Service Header

Preamble Header

+

MIME Packaging

Encrypted Payload

Container

Delivery Header

Digital Signature

S/MIME Envelope

+ + +

RNIF 1.1 RNIF 2.0

+

Attach-ments

Service Content


Technical Components - RNIFTechnical Components - RNIFThe RosettaNet Business Document or Service Content is the business document payload as defined by a particular PIP. Under RNIF 2.0, it may refer to attachments or consist of non-RosettaNet content.

The RosettaNet Business Document is an XML document.



Service Header

Preamble Header + +

Digital Signature

RNIF Version ID + +

PIP1B1PIP2A1

PIP3A2PIP3A4

MIME Packaging

Service Message


Service Header

Preamble Header

+

MIME Packaging

Encrypted Payload

Container

Delivery Header

Digital Signature

S/MIME Envelope

+ + +

RNIF 1.1 RNIF 2.0

+

Attach-ments

Service Content


Technical Components - RNIFTechnical Components - RNIFMIME-Version: 1.0Content-Type: Multipart/Related; boundary="RN-part-boundary"; type="Application/x-RosettaNet“Content-Description: This is the RosettaNet business message

--RN-part-boundary Content-Type: Application/XML; RNSubType="preamble-header" Content-Description: This is the Preamble Header part of the business message

[The Preamble Header goes here]

--RN-part-boundary Content-Type: Application/XML; RNSubType="service-header" Content-Description: This is the Service Header part of the business message

[The Service Header goes here]

--RN-part-boundary Content-Type: Application/XML; RNSubType="service-content" Content-Description: This is the Service Content part of the business message

[The Business Content goes here]

--RN-part-boundary--



Service Header

Preamble Header + +

Digital Signature

RNIF Version ID + +

PIPTM1B1PIPTM2

A1PIPTM

3A2PIPTM

3A4

MIME Packaging

Service Message


Service Header

Preamble Header

+

MIME Packaging

Encrypted Payload

Container

Delivery Header

Digital Signature

S/MIME Envelope

+ + +

RNIF 1.1 RNIF 2.0

+

Attach-ments

Service Content


MIME-Version: 1.0Content-Type: application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7mContent-Transfer-Encoding: base64Content-Disposition: attachment; filename=smime.p7m

MIAGCSqGSIb3DQEHA6CAMIACAQAxgDCCASACAQAwgYgwgYIxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMREwDwYDVQQHEwhNb25yb3ZpYTEMMAoGA1UEChMDU1RDMRQwEgYDVQQLEwtEZXZlbG9wbWVudDEnMCUGA1UEAxMeU1RDIFRlc3QgQ2VydGlmaWNhdGUgQXV0aG9yaXR5AgECMA0GCSqGSIb3DQEBAQUABIGADytB2IkYlPqgivlcnQiCPJxWDcshCKUaOm9/k07detAfX0f1LaEA23qFolSmevKrNZcUlMfm32HTUdZQpHj9Iy8da5GNI9OW+5EB7W7XoiJgyfeD6m2X3UfwnPJJUnOlC6klVBzpalFHXOw5rK2ZeGIGjiPiIq4p1DmkKlfLle4wggEgAgEAMIGIMIGCMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5pYTERMA8GA1UEBxMITW9ucm92...




Service Header

Preamble Header + +

Digital Signature

RNIF Version ID + +

PIPTM

1B1PIP2A1

PIP3A2PIP3A4

MIME Packaging

Service Message


Service Header

Preamble Header

+

MIME Packaging

Encrypted Payload

Container

Delivery Header

Digital Signature

S/MIME Envelope

+ + +

RNIF 1.1 RNIF 2.0

+

Attach-ments

Service Content



The version ID identifies RosettaNet Implementation Framework version for interoperability purposes. Part of the RNIF 2.0 Preamble Header serves the same purpose.




Service Header

Preamble Header + +

Digital Signature

RNIF Version ID + +

PIP1B1PIP2A1

PIP3A2PIP3A4

MIME Packaging

Service Message


Service Header

Preamble Header

+

MIME Packaging

Encrypted Payload

Container

Delivery Header

Digital Signature

S/MIME Envelope

+ + +

RNIF 1.1 RNIF 2.0

+

Attach-ments

Service Content


The digital signature is constructed using PKCS #7.



Service Header

Preamble Header + +

Digital Signature

RNIF Version ID + +

PIPTM

1B1PIPTM

2A1PIP3A2PIP3A4

MIME Packaging

Service Message


Service Header

Preamble Header

+

MIME Packaging

Encrypted Payload

Container

Delivery Header

Digital Signature

S/MIME Envelope

+ + +

RNIF 1.1 RNIF 2.0

+

Attach-ments

Service Content


The RosettaNet Object is created by concatenating the Version ID, Service Message, Signature Length and Signature.

The RosettaNet Object is sent to the trading partner using HTTPS …




Service Header

Preamble Header + +

Digital Signature

RNIF Version ID + +

PIPTM

1B1PIP2A1PIP3A2

PIP3A4

MIME Packaging

Service Message


Service Header

Preamble Header

+

MIME Packaging

Encrypted Payload

Container

Delivery Header

Digital Signature

S/MIME Envelope

+ + +

RNIF 1.1 RNIF 2.0

+

Attach-ments

Service Content


…while the RosettaNet Business Message wraps everything using standard MIME packaging.

The RosettaNet Business Message may be sent using HTTP, HTTPS or SMTP (other protocols to be specified in the future).




Validation

• Preamble grammar/content

• Service Header grammar

• Service Header content and sequence

• Service Content grammar/schema using both DTD(s) and message guidelines

• Service Content content


RNIF 2.0RNIF 2.0

• RNIF 1.1 was a workable solution

• RNIF 2.0 is more comprehensive

• Fix deficiencies & inconsistencies in RNIF 1.1

• Add richer and needed functionality

• Use established standards whenever possible


RNIF 2.0RNIF 2.0

• Support for multiple transfer protocols

– Transfer-independent message format (MIME & S/MIME)

– Support for both SMTP and HTTP(S)

– FTP, message queues, and others in the future

– Transfer-level headers for debugging


RNIF 2.0RNIF 2.0

• Support for end-to-end and persistent encryption

• S/MIME-based packaging for digital signatures and content enveloping

• Support for attachments and message manifest

• Support for 3rd party (hub-based) routing (due to Delivery Header)


RNIF 2.0RNIF 2.0

• Support for registry-driven requests

• Ability to ship 3rd party business content in RosettaNet PIPsTM (Action Messages)

• Signal-level error codes


RNIF 2.0 - ChangedRNIF 2.0 - Changed

• RNO (RosettaNet Object) format for packing digital signatures replaced with standard S/MIME based packaging

• X.509v1 certificate handling required. X.509v3 (extensions) optional

• Use of correct MIME headers with transport (multipart/related), as RNO is gone


RNIF 2.0 - ChangedRNIF 2.0 - Changed

• Eliminated inconsistencies in headers:

– Nested Process, Transaction, ActionControl and ServiceRoute blocks properly

– Eliminated several unused / not needed headers (e.g.Txn-Instance-Id)

– Use consistent names with PIPTM specs:• e.g. Activity vs. Transaction.


RNIF 2.0 - SameRNIF 2.0 - Same

• Solution providers must still support HTTP and HTTPS at a minimum

• Three basic message parts: Preamble-Header, Service-Header, and Service-Content

• MIME-based packing and use of multipart/related content-type


RNIF 2.X - Possible Future(s)RNIF 2.X - Possible Future(s)

• Use of W3C XML-Schema

• Use of XML-DSIG specification

• Additional transport protocol support

• Publish/Subscribe, Broadcast, Multicast, Poll & Pull message exchange models, in addition to peer-to-peer


• Convergence opportunities in the transfer, routing, and packaging layer

• Expanded support for intelligent intermediaries

RNIF 2.X - Possible Future(s)RNIF 2.X - Possible Future(s)


Next Generation of RNIFNext Generation of RNIF

• RNIF 2.x or 3.0

– Support for Multiple TRPs– Well-developed TPA guidelines– XML Standards Delivery Format– Complex Process Support– Collaborative Process Support– More Comprehensive Security Model


ChallengesChallenges

• There are many “standards” from which to choose.

• The specifications are being improved, which means they are changing.

• Some aspects of the specifications are ambiguous.

• The readability of the existing documentation needs to be improved.

• The enterprise readiness effort for RosettaNet implementations is often underestimated.


In The Future For RosettaNetIn The Future For RosettaNet

• Possible convergence with other standards

• Other vertical markets besides Information Technology (IT), Electronic Components (EC), Semiconductor Manufacturing (SM)

• Increased global presence and support

• Compliance badging program, currently in development


Summary – Remember These? Summary – Remember These?


• What are the technical components?

• What challenges will I face?

• What can I expect from RosettaNet in the future?


Summary Summary


Create content

Wrap it

Send it

Trading Partner

Receive it

Unwrap it

Process content

Trading Partner

Create content

Wrap it

Send it

Receive it

Unwrap it

Process content


Summary Summary

What are the technical components?

• Partner Interface ProcessesTM (PIPsTM)


• RosettaNet Implementation Framework (RNIF) Core


Summary - PIP™Summary - PIP™

• Partner Interface Process (PIP)

• Encapsulate business processes

• Specify structure and format of business document payloads

• Specify activities, decisions, and roles for each trading partner involved in a particular business activity


Summary - Dictionaries and CodesSummary - Dictionaries and Codes


• Machine-readable and non-machine readable

• To ensure the consistency of information exchanged between trading partners when executing PIPsTM


Summary - RNIF CoreSummary - RNIF Core

• RosettaNet Implementation Framework Core

• Defines RosettaNet Object (RNO, 1.1) and RosettaNet Business Message (2.0)

• Specifies how to transport RosettaNet Objects and Business Messages between trading partners’ network applications

• This is how PIPTM payload is packaged and transported

deciphering rosettanet: a technical overview scott woodgate, microsoft

Documents

ft view

foot view

trading partner uri

business function cluster

trading partners

rosettanet specifications

rosettanet standards

deciphering rosettanet