OASIS TECHNICAL COMMITTEE
FORMAT OF AUTOMOTIVE REPAIR
INFORMATION
Terminology and Vocabulary Requirements
Specification
Document Control
Deliverable Code
Author(s)
Date
Version
SC3-D1
John Chelsom; Richard Shorter
31-10-2002
Version 1.1
Notes:
This document is a deliverable of the OASIS TC – Format of Automotive Repair Information, and uses
a standard document template. Not all deliverables are documents, but those that are should use this
template to help with tracking and version management.
Deliverables from the project are assigned codes to allow tracking and reference of versions. A list of
all coded deliverables and project documents will be maintained by the programme managers. The
deliverables will be decided by the project sub-committees and assigned codes by the Programme
Managers. The following convention is used for the coding
SC1-Dx
SC2-Dx
SC3-Dx
SC4-Dx
Deliverables for sub-committee 1 – Use Cases and Requirements
Deliverables for sub-committee 2 – Architecture and Specification
Deliverables for sub-committee 3 – Terminology and Vocabulary
Deliverables for sub-committee 4 – Accessibility
Version numbers should be assigned starting with 1.0 and incremented with each new version
circulated by the author(s). A version note should be added for each new version on page 2.
Please put the correct title on the front page and in the header on subsequent pages. The title field can
be updated by selecting File|Properties and updating the Title field in the Summary tab. Then update
the fields on the front page and header.
Please use heading styles Heading 1, Heading 2, etc for the titles of sections.
The table of contents on page 2 can be updated by right clicking and selecting Update.
SC3-D1 Terminology and Vocabulary Requirements Specification
Version
1.0
1.1
Note
First version – a basic template for the deliverable
Template with some content in it
Contents
1. Introduction ................................................................................................................ 3
2. Requirements ............................................................................................................. 3
2.1 Terminology for Content ..................................................................................... 4
2.1.1
General ................................................................................................... 4
2.2 Terminology for Meta Data ................................................................................. 4
2.2.1
General ................................................................................................... 4
2.3 Language Management ........................................................................................ 4
2.3.1
General ................................................................................................... 4
OASIS Technical Committee - Format of Automotive Repair Information
Page 2
SC3-D1 Terminology and Vocabulary Requirements Specification
1. Introduction
Requirements may be categorised according to their priority:
E
I
essential
important
D
desirable
N
Nice-to-have
The system must implement this requirement to be accepted.
The system should implement this requirement; some deviation
from the requirement as stated may be acceptable.
The system should implement this requirement, but may be
accepted without it.
An optional feature that would enhance the solution but is not
significant for system acceptance.
2. Requirements
1. This subcommittee recommends that SAE J1930 is used as a basis for vocabulary.
It has already been adopted as ISO standard 15031-2. It covers emissions related
components and is available in English, French, and Russian.
a. Because European manufacturers exporting vehicles to the United States
are already required to provide documentation in accordance with this
standard, it is difficult to see how any other standard could be acceptable
unless it is a superset of this vocabulary and terminology.
b. The J1930 emphasis is on gasoline engine emissions. Extensions to cover
components unique to European diesel engines, including pipeline
injection and common rail systems, may be required. Somebody needs to
investigate this. [Recommendation: a consortium of the manufacturers.]
c. J1930 primarily covers vocabulary. Extensions to cover commonly used
terminology may be required. Somebody needs to investigate this.
[Recommendation: The aftermarket representatives should make
recommendations.]
2. The subcommittee requires direction from the Commission on precisely which
languages will be required.
3. A body needs to be set up and funded to translate the extended set of ISO15031-2
vocabulary and terminology into all the required languages.
a. This body will be required to liase with the manufacturers to ensure that
proposed translations are acceptable. The criteria for acceptability will
that in all languages the proposed term must be clear, unambiguous, and
not easily confused with a similar term that has been used previously with
a different meaning.
4. The manufacturers agree, in principle, to use the new vocabulary and terminology,
particularly if it is incorporated into the ISO standard, for new documentation
produced after an agreed date.
a. For technical and administrative reasons, different manufacturers will
agree to different introduction dates.
OASIS Technical Committee - Format of Automotive Repair Information
Page 3
SC3-D1 Terminology and Vocabulary Requirements Specification
2.1 Terminology for Content
2.1.1 General
Ref.
2.1.1.1
Requirement
Priority
2.2 Terminology for Meta Data
2.2.1 General
Ref.
2.2.1.1
Requirement
Priority
2.3 Language Management
2.3.1 General
Ref.
2.3.1.1
Requirement
OASIS Technical Committee - Format of Automotive Repair Information
Priority
Page 4