1、 TECHNICAL REPORT IECTR 61908First edition 2004-11The technology roadmap for industry data dictionary structure, utilization and implementation Reference number IEC/TR 61908:2004(E) Publication numbering As from 1 January 1997 all IEC publications are issued with a designation in the 60000 series. F
2、or example, IEC 34-1 is now referred to as IEC 60034-1. Consolidated editions The IEC is now publishing consolidated versions of its publications. For example, edition numbers 1.0, 1.1 and 1.2 refer, respectively, to the base publication, the base publication incorporating amendment 1 and the base p
3、ublication incorporating amendments 1 and 2. Further information on IEC publications The technical content of IEC publications is kept under constant review by the IEC, thus ensuring that the content reflects current technology. Information relating to this publication, including its validity, is av
4、ailable in the IEC Catalogue of publications (see below) in addition to new editions, amendments and corrigenda. Information on the subjects under consideration and work in progress undertaken by the technical committee which has prepared this publication, as well as the list of publications issued,
5、 is also available from the following: IEC Web Site (www.iec.ch) Catalogue of IEC publications The on-line catalogue on the IEC web site (www.iec.ch/searchpub) enables you to search by a variety of criteria including text searches, technical committees and date of publication. On-line information is
6、 also available on recently issued publications, withdrawn and replaced publications, as well as corrigenda. IEC Just Published This summary of recently issued publications (www.iec.ch/online_news/ justpub) is also available by email. Please contact the Customer Service Centre (see below) for furthe
7、r information. Customer Service Centre If you have any questions regarding this publication or need further assistance, please contact the Customer Service Centre: Email: custserviec.ch Tel: +41 22 919 02 11 Fax: +41 22 919 03 00 TECHNICAL REPORT IEC TR 61908First edition 2004-11The technology roadm
8、ap for industry data dictionary structure, utilization and implementation PRICE CODE IEC 2004 Copyright - all rights reserved No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in w
9、riting from the publisher. International Electrotechnical Commission, 3, rue de Varemb, PO Box 131, CH-1211 Geneva 20, Switzerland Telephone: +41 22 919 02 11 Telefax: +41 22 919 03 00 E-mail: inmailiec.ch Web: www.iec.ch X For price, see current catalogue Commission Electrotechnique Internationale
10、International Electrotechnical Commission 2 TR 61908 IEC:2004(E) CONTENTS FOREWORD.4 1 Scope.7 2 Normative references .7 3 Overview 7 3.1 Dictionaries and Libraries7 3.2 The IEC Dictionary 8 3.3 The ECALS Dictionary.9 3.4 The RosettaNet Dictionary.9 3.5 The Global Dictionary situation analysis 9 3.6
11、 The interoperability experiment .11 3.7 Phase I mapping results 12 3.8 Phase II Dictionary Interchange results .12 3.9 Phase III Formal harmonization results13 4 Background 13 4.1 Evaluation techniques .13 4.2 Proposed participation.14 4.3 Proposed process flow 14 4.4 Reports .14 4.5 Timing.15 5 In
12、troduction of the actual programme experiment .15 6 Procedure used for Section A experiment (RosettaNet to ECALS and MERCI) .15 6.1 Queries (Use case queries) both MERCI and ECALS 17 6.2 Queries (3-level queries) .18 6.3 Output files (created by ECALS)19 6.4 RosettaNet to MERCI (IEC) queries 20 6.4.
13、1 Specific mappings .21 6.4.2 Identification of missing values22 6.4.3 Qualification properties without mapping .22 6.4.4 Result presentation .22 6.4.5 Mapping problems .24 6.5 Evaluation of RosettaNet to ECALS exchange.24 6.5.1 TRP (transport, routing, packaging) issues 25 6.5.2 Mapping issues (RN-
14、ECALS).25 6.5.3 Query-Response rule differences.25 6.5.4 Mapping issues (RN-ECALS).25 6.5.5 Mapping issues (ECALS RN) Preliminary26 6.5.6 Mapping issues (ECALS RN) Preliminary26 7 Procedure used for Section B experiment (ECALS to RosettaNet and MERCI) .27 7.1 Queries (Use case queries, both RosettaN
15、et and MERCI) .28 7.2 Queries (3-level queries) .28 7.3 Output files (created by RosettaNet)28 7.4 ECALS to MERCI (IEC Queries)29 7.4.1 Procedure used for Section B experiment (ECALS to MERCI) .29 7.5 Output files (created by MERCI)30 TR 61908 IEC:2004(E) 3 7.6 Evaluation techniques (ECALS to Rosett
16、aNet) 32 7.6.1 Mapping issues (ECALS to RosettaNet).32 7.6.2 Message translation issues (ECALS to RosettaNet).32 7.6.3 Maintenance of mapping tables (ECALS to RosettaNet) 32 7.6.4 Contents are not provided enough (ECALS to RosettaNet) 33 7.6.5 Additional comments (ECALS to RosettaNet) 33 7.7 Evaluat
17、ion technique (ECALS to MERCI).33 8 Procedure used for Section C experiment.33 9 Phase III evaluations 35 10 Conclusions35 10.1 Cooperative spirit statement35 10.2 Lessons learned35 10.2.1 Dictionaries vs. Libraries .35 10.2.2 Discontinuity in class structures.36 10.2.3 Product complexity (viewpoint
18、s ) .36 10.2.4 Transportation mechanisms (software tools)36 10.2.5 Search engine capabilities.37 10.3 Importance of interoperability 38 11 Recommendations38 12 Epilogue.39 Annex A (informative) Open and interoperable domain dictionaries initiative40 Figure 1 Data element pyramid 11 Figure 2 Process
19、flow for Phase II, Section A RosettaNet and ECALS .16 Figure 3 Process flow for Phase II, Section A RosettaNet and MERCI .16 Figure 4 ECALS response process.19 Figure 5 MERCI response process.21 Figure 6 Process flow for Phase II Section B ECALS to RosettaNet .27 Figure 7 Process flow for Phase II S
20、ection B ECALS to MERCI .28 Figure 8 RosettaNet response process 28 Figure 9 Process flow for Phase II Section B ECALS to MERCI .30 Figure 10 Example of a Google search engine finding a microprocessor supplier.37 Table 1 Dictionary hierarchy and status (January 2003).10 Table 2 Selection of classes
21、15 Table 3 Example of 3 level query .19 Table 4 Example of detailed results of ECALS response20 Table 5 Selected classes populated in the MERCI database 21 Table 6 Example of MERCI mapping table for 22 Table 8 Mapping of properties completed by ECALS29 Table 9 Mapping of properties completed by MERC
22、I (Class XJA644, Dynamic RAMs) .31 Table 10 Section C mapping between RosettaNet and MERCI (IEC)34 4 TR 61908 IEC:2004(E) INTERNATIONAL ELECTROTECHNICAL COMMISSION _ THE TECHNOLOGY ROADMAP FOR INDUSTRY DATA DICTIONARY STRUCTURE, UTILIZATION AND IMPLEMENTATION FOREWORD 1) The International Electrotec
23、hnical Commission (IEC) is a worldwide organization for standardization comprising all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international co-operation on all questions concerning standardization in the electrical and electronic fields. To th
24、is end and in addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC National
25、 Committee interested in the subject dealt with may participate in this preparatory work. International, governmental and non- governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for Standardization (ISO)
26、 in accordance with conditions determined by agreement between the two organizations. 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus of opinion on the relevant subjects since each technical committee has representation fro
27、m all interested IEC National Committees. 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC Publications is accurate, IEC cannot be he
28、ld responsible for the way in which they are used or for any misinterpretation by any end user. 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to the maximum extent possible in their national and regional publications. Any d
29、ivergence between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter. 5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any equipment declared to be in conformity with an IEC Publicati
30、on. 6) All users should ensure that they have the latest edition of this publication. 7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and members of its technical committees and IEC National Committees for any personal injury, property
31、 damage or other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC Publications. 8) Attention is drawn to the Normative references cited in this
32、 publication. Use of the referenced publications is indispensable for the correct application of this publication. 9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent rights. IEC shall not be held responsible for identifying any or
33、all such patent rights. The main task of IEC technical committees is to prepare International Standards. However, a technical committee may propose the publication of a technical report when it has collected data of a different kind from that which is normally published as an International Standard,
34、 for example “state of the art“. IEC 61908, which is a technical report, has been prepared by IEC technical committee 93: Design Automation. The text of this technical report is based on the following documents: Enquiry draft Report on voting 93/195+195A/DTR 93/205/RVC Full information on the voting
35、 for the approval of this technical report can be found in the report on voting indicated in the above table. This publication has been drafted in accordance with the ISO/IEC Directives, Part 2. TR 61908 IEC:2004(E) 5 The committee has decided that the contents of this publication will remain unchan
36、ged until the maintenance result date indicated on the IEC web site under “http:/webstore.iec.ch“ in the data related to the specific publication. At this date, the publication will be reconfirmed, withdrawn, replaced by a revised edition, or amended. A bilingual version of this publication may be i
37、ssued at a later date. 6 TR 61908 IEC:2004(E) INTRODUCTION In order for a standard to be effective, there need to be utilization and implementation. In todays global economy the leading edge companies forge ahead with their agenda and many times produce what are known as pseudo-standards. Whether dr
38、iven by an individual company (i.e. Microsoft) or a consortia group, the ability to satisfy a customer need is their main focus and goal. This, in many instances, puts the groups developing standards in a “catch-up” mode while they make sure that industry has accepted the new concept, domain or tech
39、nology. Unfortunately, although there may be better ideas developed during the standardization process or the playing field be levelled by the standard requirement, there is a “reluctance to change” by those organizations or individuals that have invested a good number of resources in developing or
40、implementing the new concept. If the standard defines physical performance requirements or conformance details, the contractual agreements between members of the supply chain handle these according to an implemented revision level. Many engineering hours are spent in determining the variation betwee
41、n an existing version and a new change proposal, to ascertain whether the change is compatible with the implemented processes, or whether the change would require a major process overhaul. The effort to change, many times, impacts business relationships and thus support of the next revision of the s
42、tandard. When it comes to software these issues become more complex, and take on market share, technical competence, business process, and competitive rhetoric significance. Instead of working together to help the industry, many times the players work to enhance their own position. This is counter p
43、roductive to helping the electronic industry make sound decisions and continue to follow along the path of outsourcing much of the supply chain transactions, whether purchasing, fabrication, assembly or testing of electronic hardware. In order to clearly define the difference between a dictionary an
44、d a library; a dictionary contains only meta data (data about data supported by an Information model of such entries). So the definition according to a certain methodology is given of a specific characteristic, for instance “terminal diameter” For such a characteristic, the identification, descripti
45、on and value representation shall be defined. What is not given in the dictionary is the actual value(s) of diameters of something. A library is like a catalogue. It uses dictionary entries to be built into the database. In a library you find the characteristics with their values, so you can compare
46、 components of different manufacturers on their characteristics. TR 61908 IEC:2004(E) 7 THE TECHNOLOGY ROADMAP FOR INDUSTRY DATA DICTIONARY STRUCTURE, UTILIZATION AND IMPLEMENTATION 1 Scope This Technical Report is applicable to the technology roadmap for industry data dictionary structure, utilizat
47、ion and implementation. This report covers one aspect of industry relationships; that of data dictionaries. A data dictionary is made up of information about products. The products can be electronic components, base material, clothing, chemicals or any product that can be described in terms of an in
48、dustry understood descriptive name (element) and the characteristics that make up that part (attributes). Another item that helps data dictionaries become very efficient is to reuse the characteristics (attributes) in more than one element. Reuse of information is desirable in any implementation str
49、ategy in order to reduce search time for the implementation software. The topic of discussion, therefore, in this report is the status, completeness, implementer goals, and standardization efforts related to electric components. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest e
