Skip to toolbar

Community & Business Groups

Automotive Ontology Community Group

The Automotive Ontology Working Group is an informal group of individuals and corporations who want to advance the use of shared conceptual structures in the form of Web ontologies for better data interoperability in the automotive industry, and this at Web scale. In particular, we want to develop extension proposals for so that automotive information can be better understood by search engines and OWL Web ontologies for the automotive industry. Also, we want to provide a forum for bringing together researchers and practitioners who are working on advancing the field.

Group's public email, repo and wiki activity over time

Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.

No Reports Yet Published

Learn more about publishing.

Chairs, when logged in, may publish draft and final reports. Please see report requirements.

Publish Reports

Our II Community Conference Call – The Survey to choose the best day and time !

Dear Participants in our Community Group,

Please respond to this short survey that will help us to choose the best day & time for the Call:

The main theme for the call is:

How to accelerate the adoption of in the Automotive Industry Digital Platforms

More specific call agenda will follow early this week.


Draft of application with latest automotive extensions is available

Hi everybody,

Some time ago we received suggestion that it would be easier to comment on the automotive extension to if we had draft versions of the application.

We have recently created it. Please find it at: for core and for auto extension.

As for an example, here is one of the recently changed properties:

We are looking forward to inclusion of the changes into production site for !


Latest changes to automotive extension after the community review process

Dear All,

It comes a bit later than I expected, nonetheless I’m happy to inform you that as the results of our discussions here we are now proposing the following changes to types and properties related to our automotive extension:

  1. Description for has been changed, because there is no UN/CEFACT Common Code for g/km.Before:
    ‘The CO2 emissions in g/km. The property uses a number instead of a QuantitativeValue, since g/km is the dominant unit of measurement, and there is no UNCEFACT Common Code for g/km.’After:
    ‘The CO2 emissions in g/km. When used in combination with a QuantitativeValue, put “g/km” into the unitText property of that value, since there is no UN/CEFACT Common Code for “g/km”.’
  2. The text “This should be considered a pre-final preview release; final changes may be made after wider community review.” has been removed from the extension home page.
  3.” has been renamed to ““.
  4. and its predefined instances:

    have been moved to

There is also an issue being discussed on the GitHub whether should be in the core or in the extension. As soon as this is resolved and some errors related to this property range and domain, we will lunch the Pull Request that will end this phase of Community review.

Thanks to all for your remarks !


Finalization of review process

Dear All,

We came to the end of the review process. There were few changes proposed, and after some discussion we have one change to make (thanks to Tom Adamich):

Broaden the range of emmisionsCO2 property.

We suggest adding QuantitativeValue to the range of emmisionsCO2 property. One could then use “name” or “valueReference” to relate to test protocols or standards.
This change also requires modification of property description.

We will now proceed to get this change accepted and activated !

Stay tuned !




A simple list of terms – to make your review easier

Dear All,

To help with the review we just launched, please find a simple indented list of all terms in
We use red color for types, turquoise for individua and default color for properties.
All terms are hyperlinks to respective description.

Hope this helps !


Community review of

Dear All,

Let’s initiate a process of GAO community review of extension.
The final shape of the extension can be explored at

For easy visual inspection of the extension you can go to: or
(The later post includes description how to work with FreeMind on the extension – if you liked to play with a Mind Map representation of the schema !)

Whenever you find some very important term (type or property) related to cars missing from the extension, or you would name or define existing property differently, please let us know.

The comments can go directly to:  or to this post.
We will collect and respect them all !

Our intention is to close this review process in about 2 weeks (i.e. until ~ October 18th), organize the second teleconference and finally inform team about the community group position.


The first stage of GAO development process: “bag-of-concepts”

Dear All,

Please find some important remarks and a technical guidance about the initial phase of works on GAO. Feel free to comment on that matters – our goal is to create the process that is not too complicated and assumes use of simple tools (at least in the beginning)

1. Some ontological remarks

We start building GAO from collecting the concepts recognised as relevant within the automotive domain.

The concepts will be collected in a conceptual map called „bag-of-concepts”. Adding the new concepts to the conceptual map, we can take advantage of the or go beyond the set of concepts we have there. The first set of concepts is stored in file.

By the collaborative development we shall create the conceptualisation of the automotive domain shared by all the participants of Automotive Ontology Community Group.

At this stage of GAO development process we shall not impose any semantical structure on the bag-of-concepts. The concepts are to be loosely linked by one relation which covers all the SKOS-like hierarchical and associative relations such as “broader”, “narrower” and “(somehow) related”.

Of course, in the end, GAO is intended to be a formal specification (RDF(S) or OWL) of the conceptualisation of the automotive domain (shared by all the participants of Automotive Ontology Community Group). So just after the community decides the work on the conceptual map of the domain was completed, we shall transform the bag-of-concepts into the first version of GAO

2. A brief technical guidance

At this stage to contribute to GAO it is enough to have the most up-to-date conceptual map of GAO concepts represented by the mind mapping diagram (see file). The file can be easily modified by FreeMind tool (available here: file is located in GitHub GAO-GAO repository (see: The path is:

bag-of-concepts mindmap –> freemind files –>

It is recommended to use a GitHub software (win: or mac: to access and modify GAO-GAO repository. You can use standard

  • “pull” to grab any changes from the GAO-GAO repository and to merge them into your local repository
  • “push” to send your contribution from your local repository to GAO-GAO one.

If you prefer you can also open/submit an issue suggesting some changes or send your files by e-mail directly to

Further steps of GAO development process will be discussed during the next teleconference (see GAO Community Charter:

Informal summary of our first Community Group Conference Call

Our first community group conference call was convened on Thursday July 30, 12 PM EDT. We had about 10 participants.

After a brief introduction of all participants we have discussed the following matters:

  1. The current status of automotive vocabularies, both in the core ( and in the forthcoming extension (
  2. The planned deliveries after the first
  3. The potential change of the work plan to include brainstorming as the first step to build the initial “bag-of-concepts” that, together with concepts we already have in, will form the seed for GAO vocabulary.
  4. The use of GitHub as the collaborative tool for our common development.
  5. The use of FreeMind as the supporting tool for brainstorming.

Referring to matters (1) and (2) Martin Hepp explained that while we can propose some modifications to automotive vocabularies, particularly to the forthcoming extensions, we should not make revolutionary changes. Both core and are reviewed extensions and there is always a risk of long review processes and a danger promoting terms that are not important from global search engines perspectives. Martin also explained that more manufacturer specific terms can us Property-Value ( mechanism.

The rest of the call was devoted to the plans to introduce brainstorming process as a first step in going beyond the set of terms we have in In that context, the use of “mind mapping” diagrams was recommended as they do not presuppose any specific kind of relation (like is_a relation) in the initial collection process.

The use of FreeMind tool (available here) has been proposed.

The initial diagrams for vocabularies and first attempt to create a bag of concepts for GAO were presented.

The current content of the two GitHub repositories:

is limited to Freemind native files (‘mm’ extension)

The next call is planned after summer holidays in September. Meanwhile the practical methods of building the set of terms will be proposed by us so that we can start fully productive activity after the next call.

The diagrams presented during the call:

1) Current core set of terms:


schema.car2) Proposed (awaiting publication) set of terms:

(Note: there are some small difference between the diagram and current proposal)

3) The first trial set of terms for GAO brainstorming:




Our community collaboration resources at GitHub

Hello All,

We had a very nice and informative first Community Group Conference call last week (The summary is coming here soon).

One of the results of the call is that we agreed to use GitHub as our repository of electronic materials, source code, future ontology files etc.

Our profile is and has been temporarily assigned to the email account (until we practically figure out how to use our internal email facility of this group for such purposes).

There are two repositories:  – related to matters (both core and extension – – related to the development of GAO ontology.

Both contain source files for FreeMind tool (available here) that we will use for sketching the structure and content of our vocabularies as the initial tool for brainstorming. I will shortly describe it all in the call summary.

Anyone from this community group who plans to contribute to the development (all are warmly welcomed) please send the respective request to me (