This page is part of www.productontology.org/, a huge, precise dictionary of product types for advertising your products or services with schema.org or the GoodRelations e-commerce standard.
Share on
www.productontology.org/
On this page: Usage(schema.org/Microdata, RDFa, Facebook) Contact Information Caching Policy License Acknowledgments References
URI www.productontology.org/id/Vehicle
rdfs:subClassOf gr:ProductOrService, schema.org/Product
rdfs:label Vehicle (as a class of products of services)
Translation(s):
مركبة@ar;
Транспартны сродак@be;
Превозно средство@bg;
যানবাহন@bn;
Karbed@br;
Vozilo@bs;
Vehicle@ca;
Vozidlo@cs;
Cerbyd@cy;
Køretøj@da;
Fahrzeug@de;
Όχημα@el;
Vehiklo@eo;
Vehículo@es;
Sõiduk@et;
Ibilgailu@eu;
وسیله نقلیه@fa;
Ajoneuvo@fi;
Sõidoriist@fiu-vro;
Véhicule@fr;
車@gan;
Vehículo@gl;
כלי תחבורה@he;
वाहन@hi;
Vozilo@hr;
Kendaraan@id;
Farartæki@is;
乗り物@ja;
Kumbi@kg;
ವಾಹನ@kn;
차량@ko;
Vehiculum@la;
Ekúmbi@ln;
Transporto priemonė@lt;
വാഹനം@ml;
वाहन@mr;
Fargreie@nn;
Kjøretøy@no;
Pojazd@pl;
Veículo@pt;
Vehicul@ro;
Транспортное средство@ru;
Otoo@sg;
Vozidlo@sk;
Vozilo@sl;
Vozilo@sr;
Fordon@sv;
వాహనము@te;
Воситаҳои нақлиёт@tg;
ยานพาหนะ@th;
Taşıt@tr;
Транспортний засіб@uk;
ناقل@ur;
Xe@vi;
载具@zh;
車@zh-yue;
rdfs:comment
A vehicle (from ) is a device that is designed or used to transport people or cargo. Most often vehicles are manufactured, such as bicycles, cars, motorcycles, trains, ships, boats, and aircraft. Vehicles that do not travel on land often are called craft, such as watercraft, sailcraft, aircraft, hovercraft, and spacecraft. Land vehicles are classified broadly by what is used to apply steering and drive forces against the ground: wheeled, tracked, railed, or skied. ISO 3833- 1977 is the standard, also internationally used in legislation, for road vehicles types, terms and definitions (Source: Wikipedia, the free encyclopedia, see en.wikipedia.org/wiki/Vehicle)
Note: The extraction of the abstract from the Wikipedia page may sometimes yield imperfect results. We are improving the algorithm regularly.
is rdfs:domain of gr:category gr:color gr:condition gr:depth gr:hasEAN_UCC-13 gr:hasGTIN-14 gr:hasMPN gr:hasManufacturer gr:hasStockKeepingUnit gr:height gr:isAccessoryOrSparePartFor gr:isConsumableFor gr:isSimilarTo gr:weight gr:width
is rdfs:range of gr:includes gr:isAccessoryOrSparePartFor gr:isConsumableFor gr:isSimilarTo
Note: This is a generic list. Some of the properties may not be applicable to this particular type of object.
[back to top]
[back to top]
One of the most powerful usages of the class definitions from this site is to describe the type of your page and product for the schema.org product markup in Microdata syntax much more precisely.
Simply add the full URI of a class from this site, e.g. www.productontology.org/id/Vehicle as an additional type as follows:
<div itemscope itemtype="schema.org/Product"> <link itemprop="www.w3.org/1999/02/22-rdf-syntax-ns#type" class="www.productontology.org/id/Vehicle" /> <!-- other schema.org properties go in here --> </div>
Note: In HTML5, it is valid to use the <link> element in the body of a HTML document.
Here is a complete example:
<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> <title>An offer to sell a / some Vehicle</title> </head> <body> <div itemscope itemtype="schema.org/Product" itemid="#product"> <link itemprop="www.w3.org/1999/02/22-rdf-syntax-ns#type" class="www.productontology.org/id/Vehicle" /> <span itemprop="name">.. a short name for the object ...</span> Product description: <span itemprop="description">... a longer description ...</span> <div itemprop="offers" itemscope itemtype="schema.org/Offer" itemid="#offer"> <span itemprop="price">$19.99</span> <a itemprop="availability" class="schema.org/InStock"></a>In stock </div> </div> </body> </html>
@prefix foaf: <xmlns.com/foaf/0.1/> . @prefix xsd: <www.w3.org/2001/XMLSchema#> . @prefix pto: <www.productontology.org/id/> . @prefix gr: <purl.org/goodrelations/v1#> . @prefix foo: <example.com/> . # The object foo:myObject a <www.productontology.org/id/Vehicle> ; a gr:SomeItems ; gr:name "... a short name for the object ..."@en ; gr:description "... a longer description ..."@en . # The agent (person or company) who is offering it foo:ACMECorp a gr:BusinessEntity ; gr:legalName "ACME Corp" ; gr:offers foo:Offer . # The offer to sell it foo:Offer a gr:Offering ; gr:includes foo:myObject; foaf:page <URI_of_the_page_containing_the_offer.com>; gr:hasBusinessFunction gr:Sell ; gr:validFrom "2011-01-24T00:00:00+01:00"^^xsd:dateTime ; gr:validThrough "2011-12-24T00:00:00+01:00"^^xsd:dateTime ; gr:hasPriceSpecification [ a gr:UnitPriceSpecification ; gr:hasCurrency "USD"^^xsd:string ; gr:hasCurrencyValue "19.99"^^xsd:float ; gr:validThrough "2011-12-24T00:00:00+01:00"^^xsd:dateTime ] .
Note: Replace gr:SomeItems (purl.org/goodrelations/v1#SomeItems) by gr:Individual if you are describing a unique object of that kind (e.g. antique furniture).
[back to top]
<!DOCTYPE html> <html version="HTML+RDFa 1.1" xmlns="www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> <title>An offer to sell a / some Vehicle</title> </head> <body> <div xmlns:rdf="www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="www.w3.org/2000/01/rdf-schema#" xmlns:foaf="xmlns.com/foaf/0.1/" xmlns:gr="purl.org/goodrelations/v1#" xmlns:pto="www.productontology.org/id/" xmlns:foo="example.com/" xmlns:xsd="www.w3.org/2001/XMLSchema#"> <!-- The agent (person or company) who is offering it --> <div about="#ACMECorp" typeof="gr:BusinessEntity"> <div property="gr:legalName">ACME Corp</div> <div rel="gr:offers"> <!-- The offer to sell it --> <div about="#offer" typeof="gr:Offering"> <div rel="gr:hasBusinessFunction" resource="purl.org/goodrelations/v1#Sell"></div> <div rel="gr:includes"> <!-- The object --> <div about="#myObject" typeof="www.productontology.org/id/Vehicle"> <div rel="rdf:type" resource="purl.org/goodrelations/v1#SomeItems"></div> <div property="gr:description" xml:lang="en">... a longer description ...</div> <div property="gr:name" xml:lang="en">.. a short name for the object ...</div> </div> </div> <div rel="foaf:page" resource="URI_of_the_page_containing_the_offer"></div> <div rel="gr:hasPriceSpecification"> <div typeof="gr:UnitPriceSpecification"> <div property="gr:hasCurrency" content="USD" datatype="xsd:string">$ </div> <div property="gr:hasCurrencyValue" datatype="xsd:float">19.99</div> <div property="gr:validThrough" content="2011-12-24T00:00:00+01:00" datatype="xsd:dateTime"></div> </div> </div> <div property="gr:validFrom" content="2011-01-24T00:00:00+01:00" datatype="xsd:dateTime"></div> <div property="gr:validThrough" content="2011-12-24T00:00:00+01:00" datatype="xsd:dateTime"></div> </div> </div> </div> </div> </body> </html>
Note: Replace gr:SomeItems (purl.org/goodrelations/v1#SomeItems) by gr:Individual if you are describing a unique object of that kind (e.g. antique furniture).
[back to top]
<?xml version="1.0" encoding="UTF-8" ?> <rdf:RDF xmlns:gr="purl.org/goodrelations/v1#" xmlns:pto="www.productontology.org/id/" xmlns:xsd="www.w3.org/2001/XMLSchema#" xmlns:foaf="xmlns.com/foaf/0.1/" xmlns:foo="example.com/" xmlns:rdf="www.w3.org/1999/02/22-rdf-syntax-ns#"> <!-- The object --> <rdf:Description rdf:about="example.com/myObject"> <rdf:type rdf:resource="www.productontology.org/id/Vehicle"/> <rdf:type rdf:resource="purl.org/goodrelations/v1#SomeItems"/> <gr:name xml:lang="en">... a short name for the object ...</gr:name> <gr:description xml:lang="en">... a longer description ...</gr:description> </rdf:Description> <!-- The agent (person or company) who is offering it --> <gr:BusinessEntity rdf:about="example.com/ACMECorp"> <gr:legalName>ACME Corp</gr:legalName> <gr:offers rdf:resource="example.com/Offer" /> </gr:BusinessEntity> <!-- The offer to sell it --> <gr:Offering rdf:about="example.com/Offer"> <gr:includes rdf:resource="example.com/myObject" /> <foaf:page rdf:resource="URI_of_the_page_containing_the_offer"/> <gr:hasBusinessFunction rdf:resource="purl.org/goodrelations/v1#Sell"/> <gr:validFrom rdf:datatype="www.w3.org/2001/XMLSchema#dateTime"> 2011-01-24T00:00:00+01:00</gr:validFrom> <gr:validThrough rdf:datatype="www.w3.org/2001/XMLSchema#dateTime"> 2011-12-24T00:00:00+01:00</gr:validThrough> <gr:hasPriceSpecification> <gr:UnitPriceSpecification> <gr:hasCurrency rdf:datatype="www.w3.org/2001/XMLSchema#string">USD</gr:hasCurrency> <gr:hasCurrencyValue rdf:datatype="www.w3.org/2001/XMLSchema#float">19.99</gr:hasCurrencyValue> <gr:validThrough rdf:datatype="www.w3.org/2001/XMLSchema#dateTime"> 2011-12-24T00:00:00+01:00</gr:validThrough> </gr:UnitPriceSpecification> </gr:hasPriceSpecification> </gr:Offering> </rdf:RDF>
Note: Replace gr:SomeItems (purl.org/goodrelations/v1#SomeItems) by gr:Individual if you are describing a unique object of that kind (e.g. antique furniture).
[back to top]
prefix foaf: <xmlns.com/foaf/0.1/> prefix xsd: <www.w3.org/2001/XMLSchema#> prefix pto: <www.productontology.org/id/> prefix gr: <purl.org/goodrelations/v1#> prefix foo: <example.com/> # Find the cheapest offer for a Vehicle SELECT * WHERE{ ?company gr:offers ?offer . ?offer a gr:Offering . ?offer gr:hasBusinessFunction gr:Sell . OPTIONAL {?offer rdfs:label ?label } . OPTIONAL {?offer gr:name ?label } . OPTIONAL {?offer rdfs:comment ?label } . OPTIONAL {?offer gr:description ?label } . ?offer gr:hasPriceSpecification ?p . ?p a gr:UnitPriceSpecification . ?p gr:hasCurrency ?currency . ?p gr:hasCurrencyValue ?price . ?offer gr:includes ?product . ?product a <www.productontology.org/id/Vehicle> . } ORDER BY (?price) LIMIT 10
[back to top]
You can also use the class definitions from this site for better describing the type of your page or product for the Facebook Open Graph Protocol.
Simply define the namespace prefix pto: in the <html> element of your page
<html version="HTML+RDFa 1.1" xmlns="www.w3.org/1999/xhtml" xmlns:pto="www.productontology.org/id/" >
and use the compact URI (CURIE) pto:Vehicle in combination with og:type as follows:
<meta property="og:type" content="pto:Vehicle"/>
A complete example is here.
[back to top]
Univ.-Prof. Dr. Martin Hepp
E-Business and Web Science Research Group
Chair of General Management and E-Business
Universität der Bundeswehr München
Werner-Heisenberg-Weg 39
D-85579 Neubiberg, Germany
Phone: +49 89 6004-4217
eMail: mhepp(at)computer.org (preferred mode of communication)
Web: www.heppnetz.de/
Web: www.unibw.de/ebusiness/
[back to top]
In order to minimize the load on the Wikipedia API, all requests are cached internally for 12 hours. This means that changes to the English Wikipedia will be available in this service within 12 hours or less if the same entry has been requested before. Classes not requested within the last six hours are always guaranteed to be in sync with the latest version in Wikipedia.
The RDF/XML dump file is updated every 12 hours only.
[back to top]
The class definition text is taken from Wikipedia, the free encyclopedia under a Creative Commons Attribution-ShareAlike 3.0 Unported (CC BY-SA 3.0) license. Accordingly, the ontology class definitions are available under the very same license.
[back to top]
Thanks to Stefano Bertolo, Julien Chaumond, Bob Ferris, Kingsley Idehen, Axel Polleres, Andreas Radinger, Alex Stolz, and Giovanni Tummarello for very valuable feedback, and to Katharina Siorpaes and Daniel Bachlechner, who contributed to the initial analysis of the stability of Wikipedia URIs back in 2007.
The work on The Product Types Ontology has been supported by the German Federal Ministry of Research (BMBF) by a grant under the KMU Innovativ program as part of the Intelligent Match project (FKZ 01IS10022B).
[back to top]
Wikipedia: Vehicle, available at en.wikipedia.org/wiki/Vehicle.
Hepp, Martin: GoodRelations: An Ontology for Describing Products and Services Offers on the Web, Proceedings of the 16th International Conference on Knowledge Engineering and Knowledge Management (EKAW2008), Acitrezza, Italy, September 29 - October 3, 2008, Springer LNCS, Vol 5268, pp. 332-347.
Hepp, Martin; Siorpaes, Katharina; Bachlechner, Daniel: Harvesting Wiki Consensus: Using Wikipedia Entries as Vocabulary for Knowledge Management, IEEE Internet Computing, Vol. 11, No. 5, pp. 54-65, Sept-Oct 2007.