Deciphering RosettaNet: A Technical Overview Scott Woodgate, Microsoft

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 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?

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 30,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.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 30,000 ft View of the Technology It is conceptually very simple. Create content Wrap it Send it Trading Partner Initiating trading partner prepares business document payload.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 30,000 ft View of the Technology It is conceptually very simple. Create content Wrap it Send it Trading Partner Payload is placed inside XML- and MIME-based transport envelope …

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 30,000 ft View of the Technology It is conceptually very simple. 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.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 30,000 ft View of the Technology It is conceptually very simple. Create content Wrap it Send it Receive it Unwrap it Process content Trading Partner Trading partner receives incoming envelope.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 30,000 ft View of the Technology It is conceptually very simple. Create content Wrap it Send it Receive it Unwrap it Process content Trading Partner Envelope is “opened” to validate and expose processing information and business document payload.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 30,000 ft View of the Technology It is conceptually very simple. Create content Wrap it Send it Receive it Unwrap it Process content Trading Partner Payload is validated and processed according to RosettaNet specifications …

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 30,000 ft View of the Technology It is conceptually very simple. Create content Wrap it Send it Receive it Unwrap it Process content Trading Partner … and a response is wrapped and returned to the initiating trading partner.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 30,000 ft View of the Technology It is conceptually very simple. Create content Wrap it Send it Receive it Unwrap it Process content Trading Partner Conversation (exchange protocol or choreography) between trading partners continues according to RosettaNet specifications and may require several iterations.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components Partner Interface Processes (PIPs TM ) Dictionaries and Codes RosettaNet Implementation Framework (RNIF) Core

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - PIP™ Partner Interface Process (PIP) PIPs TM (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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - PIP™ 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 Finance Segment B : Transportation and Distribution PIP 3A1 - Provide Quote PIP 3A2 - Query Price and Availability PIP 3A3 - Transfer Shopping Cart PIP 3A4 - Manage Purchase Order PIP 3A5 - Query Order Status PIP 3A6 - Distribute Order Status

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - PIP™ 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - PIP™ 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. From PIP TM 3A4 Business Process Flow Diagram in BOV

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Table 3-3: Business Activity Performance Controls Activity Name Acknowledgment of Receipt Time to AcknowledgeAcceptanceTime to PerformRetry CountIs AuthorizationRequired?Non-Repudiation ofOrigin and Content? Non-RepudiationRequired?Time toAcknowledge Buyer Create Purchase Order Y2hr24hr 3YY Buyer Cancel Purchase Order Y2hr24hr 3YY Buyer Revise Purchase Order Y2hr24hr 3YY Role Name From PIP TM 3A4 Business Process Activity Controls in BOV

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. :Buyer 1. request(:PurchaseOrderRequestAction) 1.1. signal(:ReceiptAcknowledgement) 2. response(:PurchaseOrderAcceptanceAction) 2.1. signal(:ReceiptAcknowledgement) :Seller Purchase Order Request Dialog From PIP TM 3A4 Business Transaction Dialog in FSV

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Purchase Order Request Dialog Table 5 ‑ 1: Business Message and Communications Specification # Business Message Guideline DigitalSignatureRequired?SSLRequired? 1.Purchase Order Request Guideline YY 1.1Receipt Acknowledgement Guideline YY 2.Purchase Order Acceptance Guideline YY 2.1Receipt Acknowledgement Guideline Y Y From PIP TM 3A4 IFV

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. From PIP TM 3A4 XML DTD <!ELEMENT Pip3A4PurchaseOrderAcceptance ( PurchaseOrder, fromRole, toRole, thisDocumentGenerationDateTime, thisDocumentIdentifier, requestingDocumentIdentifier, GlobalDocumentFunctionCode, requestingDocumentDateTime ) > <!ELEMENT PurchaseOrder ( deliverTo?, comment?, GlobalPurchaseOrderStatusCode,

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 1 PurchaseOrder |-- deliverTo.PhysicalAddress | |-- GlobalLocationIdentifier 4 1 ||-- cityName.FreeFormText 5 1 | |-- addressLine1.FreeFormText | |-- addressLine2.FreeFormText | |-- addressLine3.FreeFormText 8 1 | |-- GlobalCountryCode | |-- NationalPostalCode 10 1 | |-- regionName.FreeFormText |-- comment.FreeFormText |-- packListRequirements.FreeFormText n |-- ProductLineItem n | |-- shipFrom.GlobalLocationIdentifier From PIP TM 3A4 Message Guidelines - Cardinality TM

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 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 PIP TM 3A4 Message Guidelines – Business Properties

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. PIP™ Summary It is conceptually very simple. Create content Wrap it Send it Receive it Unwrap it Process content Trading Partner 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.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - Dictionaries Why Use Dictionaries and Codes? Simply… To ensure the consistency of information exchanged between trading partners when executing PIPs TM.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - Dictionaries It is conceptually very simple… Create content Wrap it Send it Receive it Unwrap it Process content Trading Partner Dictionary

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Codes and Dictionaries Partner Identification (DUNS®) Product Identification –Product Number (GTIN) –Product Classification (UN/SPSC) –Product Descriptions (Dictionaries)

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Where are they used? Partner Identification (DUNS®) – used by PIPs TM 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Partner Identification DUNS® Numbering –“Data Universal Numbering System” –Managed by DUN and Bradstreet ( –Nine Digit Number –No Embedded Intelligence –Guaranteed Unique Partner Identifier –Used in Every RosettaNet PIP TM

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. DUNS® 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. DUNS® 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. DUNS® + 4 Numbering Extension to DUNS® Numbering Controlled by Individual Organization Used to Identify Specific Locations or Departments within an Organization

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. DUNS® Number Example | | | ----> Check Digit | > Company Identification

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. DUNS® + 4 Number Example | | | | | ---> Extension * | | | > Check Digit | > Company ID * Extension is Company Assigned

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. DUNS® Number Advantages Universal Partner Identifier Pass Unchanged Through Supply Chain Supports “Meta-Customer” Identification –POS / Resale Reporting –Contracts and Pricing

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Product Specification GTIN –Global Trade Item Number –Managed by: EAN International ( Uniform Code Council (UCC) (

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Product Specification GTIN –Fourteen Digit Number –No Embedded Intelligence –Guaranteed Unique Product Identifier –Used in Many RosettaNet PIPs TM

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Manufacturer’s Part 2 QSP 16 T J | | | | | | | | | | | | | ---> Resistance Value 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. GTIN Global Trade Item Number | | | | | | | -----> Check Digit | | > Sequential Identifier | > Company Identifier > Always ‘0’ in RosettaNet (Other industries use for “packaging code”)

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. GTIN Advantages Single Product Identifier Throughout Supply Chain Catalog “Owner” Responsible for GTIN Eliminates Unnecessary Cross-References Future Impacts in Customer Labeling

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Product Specification 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 –

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. UNSPSC XX | | | | | | | | | ----> Service Type (see below) | | | > Fixed thin film resistors | | > Resistors | > Printed components > Electronic Components and Supplies Service Type: 10 - Rental or Lease 11 - Maintenance or Repair 12 – Manufacturer 13 – Wholesale 14 – Retail 15 – Recycle 16 – Installation 17 - Service Parts

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical 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.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Product Specification Technical Dictionary –Parametric Database of Product Characteristics –Describes Product Form, Fit and Function –Electronically Searchable Product Configuration / Design PIPs TM

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Dictionary Example Product Class: RESISTOR–FIXED – NETWORKS Class Characteristics: - Rated Dissipation:  C - Resistance: 2200 Ohms - Resistance Tolerance:  5% - Rated Voltage: 14.83V - Limiting Element Voltage: 50V Max - Category Temperature Range: -55 C to +125C - 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: C - Terminal Shape: gull-wing - Resistive Material: Metal Film (Thin-Film)

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Dictionary Advantages Electronically Searchable Catalog Supports More Detail than Part Number Can be Integrated with Product Data Management (PDM) and Computer Aided Design (CAD)

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. POLICY PKI TPA Compliance SPECS. IT Specific Dictionary and PIPs Network Protocols Base Spec. PIP Metamodel PIP Design patterns Network Component Communications Reference Model EC Specific Dictionary and PIPs RNIF LAYERS Core Common Supply Chain

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical 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 PIPs TM ? This is how the Business Document Payload is packaged and transported.)

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - RNIF It is conceptually very simple. Create content Wrap it Send it Receive it Unwrap it Process content Trading Partner The RNIF specifies an XML- and MIME-based “envelope” in which to put the business document payload.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - RNIF RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP TM 1 B1 PIP2A1 PIP3A2 PIP3A4 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.1RNIF Attach- ments Service Content RosettaNet Business Document

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - RNIF RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP TM 1B1 PIP2A1 PIP3A2 PIP3A4 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.1RNIF 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.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP1B1 PIP2A1 PIP3A2 PIP3A4 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.1RNIF Attach- ments Service Content RosettaNet Business Document Technical Components - RNIF The Service Header contains: Process Controls Transaction Controls Action Controls Signal Controls The Service Header is an XML document.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - RNIF Process Controls identify the RosettaNet PIP TM, 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)

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - RNIF OSI Layered Ubiquitous Communications Reference Model Internet and WWW Protocol Stack RosettaNet Layers e-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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP TM 1 B1 PIP2A1 PIP3A2 PIP3A4 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.1RNIF Attach- ments Service Content RosettaNet Business Document Technical Components - RNIF The 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.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP1B1 PIP2A1 PIP3A2 PIP3A4 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.1RNIF Attach- ments Service Content RosettaNet Business Document Technical Components - RNIF MIME-Version: 1.0 Content-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--

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP TM 1 B1 PIP TM 2 A1 PIP TM 3A2 PIP TM 3A4 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.1RNIF Attach- ments Service Content RosettaNet Business Document MIME-Version: 1.0 Content-Type: application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=smime.p7m MIAGCSqGSIb3DQEHA6CAMIACAQAxgDCCASAC AQAwgYgwgYIxCzAJBgNVBAYTAlVTMRMwEQYD VQQIEwpDYWxpZm9ybmlhMREwDwYDVQQHEwhN b25yb3ZpYTEMMAoGA1UEChMDU1RDMRQwEgYD VQQLEwtEZXZlbG9wbWVudDEnMCUGA1UEAxMe U1RDIFRlc3QgQ2VydGlmaWNhdGUgQXV0aG9y aXR5AgECMA0GCSqGSIb3DQEBAQUABIGADytB 2IkYlPqgivlcnQiCPJxWDcshCKUaOm9/k07d etAfX0f1LaEA23qFolSmevKrNZcUlMfm32HT UdZQpHj9Iy8da5GNI9OW+5EB7W7XoiJgyfeD 6m2X3UfwnPJJUnOlC6klVBzpalFHXOw5rK2Z eGIGjiPiIq4p1DmkKlfLle4wggEgAgEAMIGI MIGCMQswCQYDVQQGEwJVUzETMBEGA1UECBMK Q2FsaWZvcm5pYTERMA8GA1UEBxMITW9ucm92... Technical Components - RNIF

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP TM 1B1 PIP2A1 PIP3A2 PIP3A4 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.1RNIF Attach- ments Service Content RosettaNet Business Document Technical Components - RNIF The version ID identifies RosettaNet Implementation Framework version for interoperability purposes. Part of the RNIF 2.0 Preamble Header serves the same purpose.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - RNIF RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP1B1 PIP2A1 PIP3A2 PIP3A4 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.1RNIF Attach- ments Service Content RosettaNet Business Document The digital signature is constructed using PKCS #7.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP TM 1B1 PIP TM 2A1 PIP3A2 PIP3A4 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.1RNIF Attach- ments Service Content RosettaNet Business Document 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 … Technical Components - RNIF

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP TM 1B1 PIP2A1 PIP3A2 PIP3A4 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.1RNIF Attach- ments Service Content RosettaNet Business Document …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). Technical Components - RNIF

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Technical Components - RNIF 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RNIF 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RNIF 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RNIF 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 3 rd party (hub-based) routing (due to Delivery Header)

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RNIF 2.0 Support for registry-driven requests Ability to ship 3 rd party business content in RosettaNet PIPs TM (Action Messages) Signal-level error codes

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RNIF 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RNIF 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 PIP TM specs: e.g. Activity vs. Transaction.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. RNIF 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Convergence opportunities in the transfer, routing, and packaging layer Expanded support for intelligent intermediaries RNIF 2.X - Possible Future(s)

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Next 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Challenges 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.

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. In 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Summary – Remember These? 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?

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Summary What is the 30,000 foot view of the technology? 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Summary What are the technical components? Partner Interface Processes TM (PIPs TM ) Dictionaries and Codes RosettaNet Implementation Framework (RNIF) Core

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. 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

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Summary - Dictionaries and Codes Dictionaries and Codes Machine-readable and non-machine readable To ensure the consistency of information exchanged between trading partners when executing PIPs TM

PRESENTATION TITLE © COPYRIGHT 2001 ROSETTANET. ALL RIGHTS RESERVED. Summary - 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 PIP TM payload is packaged and transported