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 schema.org 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.

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

The call details …

9 AM PDT (California), 12 PM EDT (New York), 6 PM CET (Paris) time.

GoTo Meeting:

https://global.gotomeeting.com/join/822884949

 2.  Use your microphone and speakers (VoIP) – a headset is recommended.  Or, call in using your telephone.

Austria: +43 1 2530 22500
Australia: +61 2 8355 1039
Belgium: +32 (0) 42 68 0180
Canada: +1 (647) 497-9379
Denmark: +45 32 72 03 69
Finland: +358 (0) 923 17 0555
France: +33 (0) 170 950 589
Germany: +49 (0) 692 5736 7301
Ireland: +353 (0) 15 360 757
Italy: +39 0 230 57 81 80
Netherlands: +31 (0) 207 941 375
New Zealand: +64 9 282 9510
Norway: +47 21 93 37 37
Spain: +34 932 75 1230
Sweden: +46 (0) 852 500 516
Switzerland: +41 (0) 225 4599 60
United Kingdom: +44 (0) 330 221 0099
United States: +1 (224) 501-3318

Access Code: 822-884-949

Audio PIN: Shown after joining the meeting

 Meeting ID: 822-884-949

Agenda for tomorrow’s call

Dear All,

The main theme of our call has not changed and is:

How to accelerate the adoption of auto.schema.org in the Automotive Industry Digital Platforms

However, after some discussions I had with some people, I propose to modify a bit the agenda (Point 5):

  1. The status of schema.org and automotive schema.org extensions
  2. Key message – building TRUST of clients in automotive DATA through auto.schema.org
  3. Plan for the adoption of auto.schema.org to automotive Digital Platforms:

    1. Implementation guidelines
    2. Consulting services
    3. Post-implementation follow-ups
  4. Additional quick benefits from auto.schema.org data consumption:

    1. New kind of analytics – presentation of a POC with GA
    2. Enhanced search over the data space for automotive websites – the presentation of the idea
  5. Future extension of auto.schema.org terms – first draft (see our Wiki at: https://www.w3.org/community/gao/wiki/Main_Page)
  6. Discussion

“See” you all tomorrow at:

9 AM PDT (California), 12 PM EDT (New York), 6 PM CET (Paris) time.

GTM link is here: https://global.gotomeeting.com/join/822884949

Mirek

Agenda for the Community Conference Call

The call main theme:
How to accelerate the adoption of auto.schema.org in the Automotive Industry Digital Platforms

  1. The status of schema.org and automotive schema.org extensions
  2. Key message – building TRUST of clients in automotive DATA through auto.schema.org
  3. Plan for the adoption of auto.schema.org to automotive Digital Platforms:

    1. Implementation guidelines
    2. Consulting services
    3. Post-implementation follow-ups
  4. Additional quick benefits from auto.schema.org data consumption:

    1. New kind of analytics – presentation of a POC with GA
    2. Enhanced search over the data space for automotive websites – the presentation of the idea
  5. Future of GAO Ontology – new ideas 
  6. Discussion

 Estimated Time – 90 minutes

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:

http://ml.ms/gao_call

The main theme for the call is:

How to accelerate the adoption of auto.schema.org in the Automotive Industry Digital Platforms

More specific call agenda will follow early this week.

Mirek

Draft of schema.org 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 schema.org if we had draft versions of the schema.org application.

We have recently created it. Please find it at: http://sdo-gao.appspot.com/ for core and http://auto.sdo-gao.appspot.com/ for auto extension.

As for an example, here is one of the recently changed properties:
http://auto.sdo-gao.appspot.com/emissionsCO2

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

Mirek

Latest changes to schema.org 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 schema.org types and properties related to our automotive extension:

  1. Description for http://auto.schema.org/emissionsCO2 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. http://auto.schema.org/specialUsage” has been renamed to “http://auto.schema.org/vehicleSpecialUsage“.
  4. http://schema.org/CarUsageType and its predefined instances:http://schema.org/RentalVehicleUsage
    http://schema.org/DrivingSchoolVehicleUsage
    http://schema.org/TaxiVehicleUsage

    have been moved to auto.schema.org.

There is also an issue being discussed on the GitHub whether http://schema.org/vehicleSpecialUsage 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 !

Mirek