EB 與 RosettaNet 簡介 葉慶隆 大同大學 資訊工程系

RosettaNet2 前言 電子商務的發展 – 從提供型錄式資訊服務的電子商店 (B2C) ，演進到企業間 (B2B) 商業處理自動化。 企業間商業標準架構應運而生， –RosettaNet 、 ebXML 、 BizTalk 。 Transport, routing, packaging Business processes, business documents Company A Company B Transport, routing, packaging Business processes, business documents ERP

RosettaNet3 不用網際網路的商業情節 郵遞 系統 Company A Company B 傳真 電話 Company A Company B

RosettaNet4 以瀏覽器為基礎的企業間電子商務 Web server Company A ERP Company B 顧客端

RosettaNet5 程式對程式交談的企業間電子商務 Transport, routing, packaging Business processes, business documents Company A Company B Transport, routing, packaging Business processes, business documents ERP

RosettaNet6 B2B EC 演進 EDI Business process and document integration  商業應用程式間的交談，達成企業間商業交易  建立在標準的商業流程及商業文件之上，  因此標準的制定，便形成 B2B EC 的重要工作

RosettaNet7 B2B EC 標準架構 商業處理層 – 標準商業流程及商業文件， 技術服務層 – 安全可靠的溝通管道，做為上層運 作的基礎 商業處理層 技術服務層 B2B EC 標準架構 各種標準 – 水平整合 : ebXML – 產業垂直整合 : RosettaNet ( 資訊技術、電子零組件、及半導 體製造業 ) – 技術服務架構 :BizTalk Framework

RosettaNet8 ebXML 完整的 B2B EC 架構 1999 年 9 月由聯合國制定電子商務標準的組織 OASIS 和 UN/CEFACT 共同推動的企業間電子商務標準。 EbXML 主要任務在於提供一個開放式的 XML 底層架構， 以利各方在安全、一致的環境下達成共通的電子商務 資訊互動。 其基本訴求為使用 XML 技術，提供不同規模的企業間 的垂直和水平整合。提供低成本的軟體製作，供中小 企業之用，也顧到大企業的需求。通用性的處理程序、 用語、及編碼。制定註冊機制以達成開放性及提高互 通性。提供安全的遞送路徑、封包方式以確保商業訊 息送收的安全。

RosettaNet9 ebXML 完整的 B2B EC 架構

RosettaNet10 ebXML 完整的 B2B EC 架構 ebXML infrastructure 需要 以下成分 1. 交易夥伴的資訊（ CPP 與 CPA ） 2. 商業過程與資訊模型 3. 核心元件與核心資料庫的機能 4. 註冊機制及儲存庫的機能 5. 訊息服務的機能 Discovery step In B2B EC 構建商業情節 技術服務平台

RosettaNet11 RosettaNet 一個非營利協會所制定的企業間電子商務標準 主要目的是為高科技的資訊技術、電子零組件、及半導體製造產 業建立供應鏈管理體系。 RosettaNet 所定的 B2B EC 是一個具有上層商業處理與下層技術 服務的整體架構。 在上層商業處理方面，主要在於制定企業夥伴間標準商業處理程 序。 – 依照功能性共分成七群 (cluster) 核心商業處理程序，包括交易夥伴及 商品資訊之收集、維護，產品資訊之分送及更新，訂單管理，庫存 管理，市場資訊管理，售後服務及支援，製造資訊之交換。 – 每一群又分成幾個段 (segment) ，每段含有幾個夥伴間程序介面 (partner interface process, PIP) 。 – 每個 PIP 定義程式對程式間以 XML 標準商業文件為基礎的對話程序。

RosettaNet12

RosettaNet13 RosettaNet 從商業運作的角度來看， 一個 PIP 主要內容是特定 的商業工作流程及其流程 中所帶動的文件 為求文件一致， RosettaNet 定義了商業 和技術字典，前者為提供 商業詞彙，後者為各行業 的技術用語 RosettaNet 制定了 RNIF (RosettaNet Implementation Framework) ，當中定義了 工作平台間訊息交換協定 (protocol) ，以支應上層 PIP 在文件遞送上的基礎

RosettaNet14 RosettaNet 對照前面 ebXML 的架構， RosettaNet 提供完整的商業 處理程序及工作平台，也就是第六步 RosettaNet 並不制定註冊機制及 CPP/CPA ，因此在 商業夥伴的探索及建立夥伴關係上必須靠人工達成 –UDDI(Universal Description, Discovery Integration) by IBM, Microsoft and Ariba 另一個 B2B EC 標準 BizTalk Framework 則是制定了 相當於 RNIF 角色的下層技術服務 –Microorsoft BizTalk Server 2000

RosettaNet15 RosettaNet 宗旨及任務 宗旨 –Dynamic, flexible trading networks –Operational efficiency –New business opportunities 任務 – 促進網際網路商業標準的合作發展及快速建置 – 創造共通的商業語言及開放式的電子化商業程序，為全球高 科技交易網路帶來利益及提昇演進的腳步

RosettaNet16 RosettaNet 是什麼 RosettaNet 是由超過 400 家資訊技術業、 電子零組 件業、及半導體製造業廠商所組成的協會，共創及推 廣開放式的電子標準商業程序 RosettaNet 名稱是以 the Rosetta Stone 而得名, RosettaNet 創造電子商務標準語言，包括商業程序及 商業文件 – 促成供應鏈電子化 – 建立有彈性的交易夥伴關係 – 降低成本、提昇產量

RosettaNet17 RosettaNet 標準內容為何 RosettaNet 標準是集合高科技公司的專業知識，共創 而成的非獨占性的電子商務方案，其內容包括 – 商業及技術字典 RosettaNet Business Dictionary 、 RosettaNet Technical Dictionary – 下層技術服務架構 RosettaNet Implementation Framework (RNIF) – 商業訊息及程序規範 RosettaNet Partner Interface Processes ™ (PIPs ™ ) 以上標準規範可由 免費取得

RosettaNet 的技術面

RosettaNet19 RosettaNet 的技術概念 備妥 內容 放入信封 送出 交易夥伴 提出需求的交易夥伴準備 好商業文件，載明需求內 容

RosettaNet20 RosettaNet 的技術概念 Trading Partner 備妥 內容 放入信封 送出 交易夥伴 備妥的商業文件包裝成 XML 及 MIME 規格做成的傳 輸信封內

RosettaNet21 RosettaNet 的技術概念 Trading Partner 備妥 內容 放入信封 送出 交易夥伴 用預定的埠際協定 (HTTP(s) 、 SMTP 等 ) 送到 交易夥伴的 URI

RosettaNet22 RosettaNet 的技術概念 Trading Partner 備妥 內容 放入信封 送出 交易夥伴 交易夥伴收到信件 Trading Partner 收文 解開信封 處理內容 交易夥伴

RosettaNet23 RosettaNet 的技術概念 Trading Partner 備妥 內容 放入信封 送出 交易夥伴 Trading Partner 收文 解開信封 處理內容 交易夥伴 解開以檢驗信封內的處理 資訊及商業文件是否正確

RosettaNet24 RosettaNet 的技術概念 Trading Partner 備妥 內容 放入信封 送出 交易夥伴 Trading Partner 收文 解開信封 處理內容 交易夥伴 根據 RosettaNet 規範處理 驗證過後的商業文件及程 序

RosettaNet25 RosettaNet 的技術概念 Trading Partner 備妥 內容 放入信封 送出 交易夥伴 Trading Partner 收文 解開信封 處理內容 交易夥伴 將回應的內容以信封包裝 後回覆

RosettaNet26 RosettaNet 的技術概念 Trading Partner 備妥 內容 放入信封 送出 交易夥伴 Trading Partner 收文 解開信封 處理內容 交易夥伴 交易夥伴間以此模式，依 照 RosettaNet 規範繼續交 談直到完成商業程序

RosettaNet27 RosettaNet 的技術構件 Partner Interface Processes (PIPs TM ) Dictionaries and Codes RosettaNet Implementation Framework (RNIF) Core

RosettaNet28 技術構件 ─PIP 整合式的商業程序，其中規範了 – 商業文件的結構及格式 – 參與商業活動的交易夥伴的活動、決策、及角色扮 演

RosettaNet29 技術構件 ─PIP 分類方式是依照高階商業功能 (cluster) 及次功能 (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

RosettaNet30 技術構件 ─PIP PIP 規範是可供下載的.zip 檔放在 rosettanet 網 站，內容包括 – 規格書 (.doc) + 勘誤表 –XML DTD 說明商業文件的結構內容 – 訊息使用說明 編碼、定義、訊息出現次數

RosettaNet31 技術構件 ─PIP 規範是遵循 Open-EDI Reference Model (ISO/IEC 14662) 的概念制定而成，包括 – 商業運作觀點 (Business Operational View, BOV) 以商業角度看待商業交易 – 功能服務觀點 (Functional Service View, FSV) 以技術角度看待商業交易 – 製作架構觀點 ( Implementation Framework View, IFV) RosettaNet 下層技術服務製作的架構

RosettaNet32 PIP BOV

RosettaNet33 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 PIP TM 3A4 在 BOV 下的程序控制

RosettaNet34 :Buyer 1. request(:PurchaseOrderRequestAction) 1.1. signal(:ReceiptAcknowledgement) 2. response(:PurchaseOrderAcceptanceAction) 2.1. signal(:ReceiptAcknowledgement) :Seller Purchase Order Request Dialog PIP TM 3A4 FSV 下的商業交易對話

RosettaNet35 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 PIP TM 3A4 IFV

RosettaNet36 PIP TM 3A4 XML DTD <!ELEMENT Pip3A4PurchaseOrderAcceptance ( PurchaseOrder, fromRole, toRole, thisDocumentGenerationDateTime, thisDocumentIdentifier, requestingDocumentIdentifier, GlobalDocumentFunctionCode, requestingDocumentDateTime ) > <!ELEMENT PurchaseOrder ( deliverTo?, comment?, GlobalPurchaseOrderStatusCode,

RosettaNet37 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 PIP TM 3A4 訊息使用說明 – 訊息出現次數

RosettaNet38 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. PIP TM 3A4 訊息使用說明 – 商業屬性

RosettaNet39 PIP 摘要 Trading Partner 備妥 內容 放入信封 送出 交易夥伴 Trading Partner 收文 解開信封 處理內容 交易夥伴 PIP 規定一個特定商業活動商 業文件的結構及格式 商業文件表示成 XML 文件 PIP 也規定交易夥伴間交 換文件的協定

RosettaNet40 技術構件 ─ 字典 Trading Partner 備妥 內容 放入信封 送出 交易夥伴 Trading Partner 收文 解開信封 處理內容 交易夥伴 字典

RosettaNet41 標準碼及字典 交易夥伴識別號 (DUNS®) 產品識別號 – 產品編號 (GTIN) – 產品分類 (UN/SPSC) – 產品說明 (Dictionaries)

RosettaNet42 標準碼及字典的使用時機 交易夥伴識別號 (DUNS®) –PIPs TM 用來識別交易夥伴及其位址 產品識別號 (GTIN) –PIPs 用來識別產品 產品識別號 (UN/SPSC) – 產品資訊類的 PIP (Cluster 2) 用其來當作類別代號

RosettaNet43 交易夥伴之識別 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

RosettaNet44 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

RosettaNet45 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

RosettaNet46 DUNS ® + 4 Numbering Extension to DUNS ® Numbering Controlled by Individual Organization Used to Identify Specific Locations or Departments within an Organization

RosettaNet47 DUNS ® Number Example | | | ----> Check Digit | > Company Identification

RosettaNet48 DUNS ® + 4 Number Example | | | | | ---> Extension * | | | > Check Digit | > Company ID * Extension is Company Assigned

RosettaNet49 DUNS ® Number Advantages Universal Partner Identifier Pass Unchanged Through Supply Chain Supports “Meta-Customer” Identification –POS / Resale Reporting –Contracts and Pricing

RosettaNet50 Product Specification GTIN –Global Trade Item Number –Managed by: EAN International ( Uniform Code Council (UCC) (

RosettaNet51 Product Specification GTIN –Fourteen Digit Number –No Embedded Intelligence –Guaranteed Unique Product Identifier –Used in Many RosettaNet PIPs TM

RosettaNet52 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

RosettaNet53 GTIN Global Trade Item Number Always ‘0’ in RosettaNet (Other industries use for “packaging code” Company Identifier Sequential Identifier Check Digit

RosettaNet54 GTIN Advantages Single Product Identifier Throughout Supply Chain Catalog “ Owner ” Responsible for GTIN Eliminates Unnecessary Cross-References Future Impacts in Customer Labeling

RosettaNet55 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 –

RosettaNet56 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

RosettaNet57 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.

RosettaNet58 Product Specification Technical Dictionary –Parametric Database of Product Characteristics –Describes Product Form, Fit and Function –Electronically Searchable Product Configuration / Design PIPs TM

RosettaNet59 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)

RosettaNet60 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)

RosettaNet61 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

RosettaNet62 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.)

RosettaNet63 Technical Components - RNIF Trading Partner 備妥 內容 放入信封 送出 交易夥伴 Trading Partner 收文 解開信封 處理內容 交易夥伴 RNIF 制定以 XML 及 MIMI 為 依據的 “ 信封套 ” ，以便放入 商業文件

RosettaNet64 Technical Components - RNIF RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP TM 1 B1 PIP2A1 PIP3A 2 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

RosettaNet65 Technical Components - RNIF RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP TM 1 B1 PIP2A1 PIP3A 2 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.

RosettaNet66 Technical Components - RNIF RosettaNet Object (RNO) Service Header Preamble Header ++ Digital Signature RNIF Version ID ++ PIP TM 1 B1 PIP2A1 PIP3A 2 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 Service Header contains: Process Controls Transaction Controls Action Controls Signal Controls The Service Header is an XML document.

RosettaNet67 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)

RosettaNet68 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

RosettaNet69 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.

RosettaNet70 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--

RosettaNet71 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

RosettaNet72 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.

RosettaNet73 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.

RosettaNet74 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

RosettaNet75 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

RosettaNet76 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

RosettaNet77 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

RosettaNet78 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

RosettaNet79 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)

RosettaNet80 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

RosettaNet81 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

RosettaNet82 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.

RosettaNet83 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

RosettaNet84 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

RosettaNet85 Convergence opportunities in the transfer, routing, and packaging layer Expanded support for intelligent intermediaries RNIF 2.X - Possible Future(s)

RosettaNet86 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

RosettaNet87 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.

RosettaNet88 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

RosettaNet89 Summary What are the technical components? Partner Interface Processes TM (PIPs TM ) Dictionaries and Codes RosettaNet Implementation Framework (RNIF) Core

RosettaNet90 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

RosettaNet91 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

RosettaNet92 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