Microsoft PowerPoint - XML99.ppt

Size: px

Start display at page:

Download "Microsoft PowerPoint - XML99.ppt"

粉坟松
5 years ago
Views:

1 in the Rough Harmonizing XML Tag Semantics via UDEF Intelligent Identifiers Ron Schuldt,

2 XML Interest Domains Accounting Education Electronic Data Interchange Enterprise Resource Planning Finance Healthcare Human Resources Insurance News Real Estate Science Travel Web Applications Others

3 The Problem Overlapping Standards XML-EDI STEP X12/EDIFACT Other XML Standards Legacy Data

4 Why Harmonize Tags? To take advantage of XML s potential for finding the information or data diamond in the rough Within the enterprise Across enterprises Semantically equal tags are necessary across multiple interest domains Enterprise address Enterprise name Product attributes... Hundreds of other key tags

5 Proposed Approach Global intelligent data index - like barcode OASIS and XML.ORG managed Optional mapping of DTD tags when submitted to XML.ORG registry and repository Index added as option to each tagged data element Built on rules based Universal Data Element Framework (UDEF) Developed within CALS Tested within Electronic Industries Association Conforms to ISO/IEC data element naming principles

6 UDEF Participants CALS ISG - Developed UDEF Industry Ron Schuldt (Chair) - Lockheed Martin Barbara Barman (Vice Chair) - Raytheon Rob Bryant - DynCorp Ruey Chen - David Taylor Research Center Bob Hodges - Texas Instruments Neal McNamara - Analysis & Technology Inc. Bud Orlando - TRW Madelyn van der Bokke - ASEC George Walther - Lockheed Martin Government Norma Kornwebel - PM JCALS Dinah Beres - NAWC Steve Waterbury - NASA EIA - Applied UDEF Industry Ron Schuldt (Chair) - Lockheed Martin Rick Lang - Texas Instruments Pam Stanfield - Lockheed Martin Gary O Hara - Hughes Space and Comm Tony DiPerna - Ericsson Communications Ken McTee - Texas Instruments Cindy Hauer - Mevatec Corp Fred Bahrs - CMstat Corporation Doug Drury - ITT Federal Services Lee LeClair - Texas Instruments Government Deborah Cornelius - US Army Missile Cmd C. H. VanLandingham - NOAA Nat l Wea Svc

7 What is the UDEF? Rules based approach for naming data elements - for example: part number, delivery date and country code are transformed to more rigorous names when the rules of UDEF are applied Uses tree structure taxonomies that easily transform into an intelligent universal identifier

8 UDEF Objects and Properties Entity = 0 Asset = 1 Document = 2 Enterprise = 3 Environment = 4 Human = 5 Law/Rule = 6 Place = 7 Process = 8 Product = 9 Program = 10 Condition = 11 + From DoD M-1 Amount = 1 Angle = 2 Area = 3 Code = 4 Coordinate = 5 Date = 6 Dimension = 7 Identifier = 8 Mass = 9 Name = 10 Quantity = 11 Rate = 12 Temperature = 13 Text = 14 Time = 15 Volume = 16 Weight = 17

9 Document Object Example DOCUMENT (2) Drawing Specification Software Noted h Control a Engineering b List Source a Controlling Graphic Parts a b Noted a c Assembly d c j Item System a Military b f Configuration Support Controlling Reference a e a Unique Source-Code c Component e Data Index b c Primary a i b d Program a k

10 Date Property Example DATE (6) Approval Assembly 1 2 De-Classification 3 Security 1 Classification Downgrade 4 Publication 5 Security Data 1 1 Expiration Classification Royalty Security 1 Release Rights Design 2 Actual Promised Scheduled Government 1

11 Universal ID is Key Universal ID is the KEY - allows for an unlimited number of aliases - no system needs to change its data element names - mapping to UDEF is based on semantic equivalence Registered Names Provides Bar Code like index to global data Alias 1 Alias 2 Alias 3 Universal ID = Alias n

12 Mapping Examples X12 & EDIFACT Data Elements country code invoice number- assigned by issuer purchase order type code postal code location qualifier location identifier contract effective date expiry date of import license item number - product item number -service price UDEF ID e.7_4 bd.2_ d.t.2_33.4 7_ _ _8.4 e.2_13.6 a.be.2_6.6 9_8 f.9_8 9_2.1 UDEF ID MIL-STD STD-2549 X12 (EDI) System A g.9_8 g.9_9 y.3_9 e.2_8 f.g.9_11 2_33.4 Part Product Identifier Part Product Name Contract Document Identifier Component Product Quantity Document Type Code Product/Service ID Product/Service Name Entity (Supplier) Name Buyer s Contract Number Report Type Code Part No Supplier Contract No Doc Type

13 Require Registration Service System A External Supp-ID Conceptual Supplier-ID Physical REGISTRATION SERVICE Registered Name Supplier ENTERPRISE Purchaser Assigned IDENTIFIER Registered Universal ID y.3_ System B External Sup-Num Conceptual Supplier_Number Physical Propose that OASIS and XML.ORG provide this service

14 Some of the Benefits UDEF Indexed Data Elements (XML Tags) Rapidly aligned Language independent Provide ID required by ISO/IEC Allow rapid comparison of XML schema content Support harmonization across domains UDEF Top Level Objects & Properties Intuitive Tested Provide a common frame of reference to establish context (key to semantics)

<4D6963726F736F667420506F776572506F696E74202D20C8EDBCFEBCDCB9B9CAA6D1D0D0DEBDB2D7F92E707074>

<4D6963726F736F667420506F776572506F696E74202D20C8EDBCFEBCDCB9B9CAA6D1D0D0DEBDB2D7F92E707074> 软件架构师研修讲座胡协刚软件架构师 UML/RUP 专家 szjinco@public.szptt.net.cn 中国软件架构师网东软培训中心小故事 : 七人分粥当前软件团队的开发现状和面临的问题软件项目的特点解决之道 : 从瀑布模型到迭代模型解决项