This document is a preview generated by EVS

Size: px

Start display at page:

Download "This document is a preview generated by EVS"

Emil Fields
5 years ago
Views:

1 CEN WORKSHOP CWA February 2008 AGREEMENT ICS English version Modelling for Automotive Repair Information Applications This CEN Workshop Agreement has been drafted and approved by a Workshop of representatives of interested parties, the constitution of which is indicated in the foreword of this Workshop Agreement. The formal process followed by the Workshop in the development of this Workshop Agreement has been endorsed by the National Members of CEN but neither the National Members of CEN nor the CEN Management Centre can be held accountable for the technical content of this CEN Workshop Agreement or possible conflicts with standards or legislation. This CEN Workshop Agreement can in no way be held as being an official standard developed by CEN and its Members. This CEN Workshop Agreement is publicly available as a reference document from the CEN Members National Standard Bodies. CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG Management Centre: rue de Stassart, 36 B-1050 Brussels 2008 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No.:CWA 15770:2008 D/E/F

2 Contents Page Foreword Scope References Terms, Conventions, Abbreviations and Acronym Model for Automotive Repair Information Applications (MARIA)...11 Annex A (informative) Physical Data Structures Examples...43 Annex B (informative) Terminology: Methodology for Developing, Using, and Maintaining a MARIA Terminology...49 Annex C (informative) Ontology Example...53 Annex D (informative) Future Extension Points for a Repair Information Service Identified by MYCAREVENT...54 Annex E (informative) Comments Received and Editor s Observations on CWA Modelling for Automotive Repair Information Applications...56 Bibliography

3 Foreword The proposal for this Workshop originates from MYCAREVENT, Mobility and Collaborative Work in European Vehicle Emergency Networks, a European Integrated Project, co-funded by the European Commission in the Sixth Framework Programme, for developing a mobile service world in the field of repair and maintenance of passenger vehicles. 1 Standardization is an integral part of the project and supported by the Consortium of Partners of MYCAREVENT as a means of diffusing and disseminating knowledge and innovative approaches on technology. The MYCAREVENT project has 20 partners from nine European countries. The project partners are active in research and development for the automotive industry and its aftermarket as original equipment manufacturers (OEM), roadside assistance providers, software developers, communication specialists, academia, etc. The Workshop Agreement presents the results of the project s research in the modelling of automotive repair information applications. The Workshop details a generic information reference model as a basis for modelling repair information applications. This CEN Workshop Agreement has been drafted and approved by a Workshop of representatives of interested parties, the constitution of which is the MYCAREVENT project, Workshop members, those providing input during the public comment period. At the workshop closing plenary meeting held in Brussels on , some companies/organisations stated that, although the CEN Workshop is appreciated, further input is necessary to have a formal standard in this domain (either at the European or the international level). For any future standardization in this area, concerns raised by workshop participants must be taken into account. The comments on the CEN Workshop Agreement received during the public comments period are listed in Annex E of this document. This CEN Workshop Agreement is publicly available as a reference document from the National Members of CEN: AENOR, AFNOR, ASRO, BDS, BSI, CSNI, CYS, DIN, DS, ELOT, EVS, IBN, IPQ, IST, LVS, LST, MSA, MSZT, NEN, NSAI, ON, PKN, SEE, SIS, SIST, SFS, SN, SNV, SUTN and UNI. Comments or suggestions from the users of the CEN Workshop Agreement are welcome and should be addressed to the CEN Management Centre. 1 For more information on the Project refer to 3

4 Introduction This Workshop Agreement details a Model for Automotive Repair Information Applications (MARIA) that provides a core information model for the modelling of repair information applications in the automotive domain. MARIA is a generic and integrated information reference model, an abstract reference information model that is specialized for use in a particular implementation or repair information delivery application of the model. The Workshop Agreement is based on the results of the MYCAREVENT project s research in the modelling of automotive repair information applications, as detailed by the project s Generic and Integrated Information Reference Model (GIIRM). The model defines the core classes of information, and the relationships between those classes, that are used to describe vehicle faults and symptoms occurring in vehicle systems and the repair information associated with repairing those vehicle systems. Adjuncts to MARIA are defined to enable its implementation and use: Information Bundles (IB) to exchange instance data about the core classes, an ontology to represent MARIA in a machine-readable form that supports rule-based inference over the objects of the domain, and a default Terminology that allows data to be taken from disparate source systems to be integrated at the data and semantic levels for use in the implementation context. An application of the model specialises MARIA in order to meet the requirements of the implementation context. This Workshop Agreement documents the process by which the model is specialised for use, that is applied, and provides a methodology for how to use and apply the model (by sub-classing the core classes of MARIA, for exchanging metadata about instances of the classes in the model, for developing the ontological representation of the model, and for developing and using terminology in the metadata messages and in the ontology). Annexes to the Workshop Agreement provide examples of XML artefacts for message schema and ontology, and a methodology for Terminology development. 1 Scope This Workshop Agreement describes the process of developing a general ontology for information, available across a specific domain of the automotive industry and the related after-market, that is to be used for repair, maintenance, and diagnosis services and products used within passenger cars. The concept and the process described can be transferred to specifications for ontologies of other types of motor vehicles, other sectors of the market, or other domains. The Workshop scope is set by the Workshop Business Plan, Workshop Objectives, where it states the intention of the Workshop and the bounds of the work. 2 References 2.1 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 edition of the referenced document (including any amendments) applies. ISO 704:2000, Terminology work Principles and methods ISO 860:1996, Terminology work Harmonization of concepts and terms 4

5 ISO :2000, Terminology work Vocabulary Part 1: Theory and application ISO 3779, Road vehicles; Vehicle identification number (VIN) Content and structure ISO 14721:2003, Space data and information transfer systems Open archival information system Reference model ISO :2005, Road vehicles Communication between vehicle and external test equipment for emissions-related diagnostics Part 6: Diagnostic trouble code definitions ISO , Road vehicles Communication between vehicle and external equipment for emissions-related diagnostics Part 7: Data link security ISO 15764, Road vehicles Extended data link security ISO 20828, Road vehicles Security certificate management ISO/DIS , Road vehicles Open diagnostic data exchange Part 1: Data model specification ISO/DIS series, Road vehicles Modular vehicle communication interface (MVCI) ISO/IEC :2003, Information technology Metadata registries (MDR) Part 3: Registry metamodel and basic attributes lso/lec :2005, Information technology Metadata registries (MDR) Part 5: Naming and identification principles ISO/IEC 14662:2004, Information technology Open-edi reference model 2.2 Other references The following referenced documents are not classified as normative references; they are, though, indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. IETF RFC 3986:2005, Uniform Resource Identifier (URI): Generic Syntax IETF RFC 4646:2006, Tags for Identifying Languages IETF RFC 4647:2006, Matching of Language Tags SAE J 2534/1, Recommended Practice for Pass-Thru Vehicle Programming World Wide Web Consortium Recommendation: 2004, Extensible Markup Language (XML) 1.0 (Fourth Edition). ( query date ) World Wide Web Consortium Recommendation: 2004, OWL Web Ontology Language Reference. ( query date ) World Wide Web Consortium Recommendation: 2004, Resource Description Framework (RDF): Concepts and Abstract Syntax. ( query date ) World Wide Web Consortium Recommendation: 2004, XML Schema Part 1: Structures Second Edition. ( query date ) World Wide Web Consortium Recommendation: 2004, XML Schema Part 1: Datatypes Second Edition. ( query date ) 5

6 2.3 References to MYCAREVENT documents The following documents developed by the MYCAREVENT project have provided source material for this Workshop Agreement. These documents are available from the MYCAREVENT project website. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) available from the Public Documents area of the MYCAREVENT website ( applies. CEN WS/IMA:2007, CEN/ISSS Workshop on Modelling for automotive repair Information Applications (WS/IMA), Business Plan (version 1). CEN/ISSS WS/IMA N 07/001 rev ( query date ) MYCAREVENT DL 3.4:2005, Deliverable 3.4 Terminology and Methodology for Populating the Generic Information Model. Final Release, Version MYCAREVENT DL 3.5:2006, Deliverable 3.5 Data Structure and XML Structure Definitions for MYCAREVENT (Focus Schematic Diagrams). Final Release, Version Terms, Conventions, Abbreviations and Acronym 3.1 Terms and definitions For the purposes of this document, the following terms and definitions apply association A semantic relationship between two classes (ISO/IEC :2003) attribute A characteristic of an object or entity (ISO/IEC :2003) attribute instance A specific instance of an attribute (ISO/IEC :2003) attribute value The value associated with an attribute instance (ISO/IEC :2003) characteristic Abstraction of a property of an object or of a set of objects (ISO/IEC :2003) NOTE Characteristics are used for describing concepts class A description of a set of objects that share the same attributes, operations, methods, relationships, and semantics (ISO/IEC :2003) composite attribute An attribute whose datatype is non-atomic (ISO/IEC :2003) 6

This document is a preview generated by EVS

This document is a preview generated by EVS CEN WORKSHOP CWA 15748-12 July 2008 AGREEMENT ICS 35.240.50 Supersedes, February English version Extensions for Financial Services (XFS) interface specification - Release 3.10 - Part 12: Camera Device