View
12
Download
0
Category
Preview:
Citation preview
Martin Heppmhepp@computer.org
The GoodRelations Ontology: Making Semantic Web-based E-Commerce a Reality
http://purl.org/goodrelations/
Martin Heppmhepp@computer.org / http://www.heppnetz.de
1
Martin Heppmhepp@computer.org
E-Commerce on the Web
2
Enterprise 1
Structured
Data on
Products and
Services
(purchased
and offered)
Enterprise 2
Structured
Data on
Products and
Services
(purchased
and offered)
World Wide Web
Martin Heppmhepp@computer.org
E-Commerce on the Semantic Web
3
Enterprise 1
Structured
Data on
Products and
Services
(purchased
and offered)
Enterprise 2
Structured
Data on
Products and
Services
(purchased
and offered)
World Wide Web
Product Specifications: Type of Product, Features etc.
Details of the Offering: Price, Eligible Regions, etc.
Martin Heppmhepp@computer.org 4
2001-2008:Semantic Web & E-Commerce: Lots of Papers, Limited Impact
Martin Heppmhepp@computer.org
Use Cases
• Commodity offers
• Services offers
• Product model data interchange
5
We sell some
sleeping bags.
We sell some instances of the Marmot
sleeping bag model 1234.
We sell a particular
used instance of the Marmot sleeping bag model 1234.
We clean and repair
sleeping bags.
Martin Heppmhepp@computer.org
Required Ontologies• An ontology for product
types and features
• by function, usage, or nature
• An ontology for offer specifications
• An offer is basically a relation between
• an agent,
• a set of objects,
• a set of property rights,
• an audience, and
• a set of terms and conditions.
6
Martin Heppmhepp@computer.org
eClassOWL and GoodRelations
• eClassOWLfoo:myTVSet instanceOf eclassowl:TVSet
• GoodRelationsfoo: MillerInc goodrelations:offersToSell foo:myTVSet
7
Martin Heppmhepp@computer.org
Competency Questions
• Overview
• Upper Ontology Part
• Domain Ontology Part
8
GoodRelations: An Ontology for Describing Products and Services Offers on the Web 331
Scenario 4: A particular Web resource represents (1) the description of a particular range of products, determined either by product classes, makes and models, or prop-erty ranges, and (2) a concrete offer to provide a certain type of service for this range of products (e.g. maintenance, repair, or disposal). Such Web resources are usually within the domain name space of local dealers.
2.2 Competency Questions
Next, we specify the scope and purpose of the GoodRelations ontology using competency questions, which is a standard technique in ontology engineering methodologies [8]. The questions were discussed with stakeholders, namely the developers of recommender systems, operators of Web shops, and other domain experts.
CQ1: Which retrievable Web Resources describe an offer
• {to sell | to provide the service of | to repair | to maintain | to lease out | to dis-pose}
• {a concrete individual | some unknown individuals} of • a {given good | given service | spare part for a given good | consumables and
supplies for a given good} described by a {type of good | specific make and model}
• that meet certain requirements on {properties | intervals for properties} • for which the offering party accepts a given method of payment and • provides a certain method of delivery • to {consumers | retailers} • in a given {country | region}?
CQ2: For which time frame is the offer valid?
CQ3: Which types of customers are eligible?
CQ4: Which are the eligible customer regions?
CQ5: Which shipping / delivery methods are available?
CQ6: Which methods of payment are accepted?
CQ7: For any such offer, what is the price and currency for a given quantity, delivery region, and type of customer, per unit of measurement? Does the price include VAT and sales taxes?
CQ8: What is the shipping charge and currency for a given delivery method to a given region? Does it include VAT?
CQ9: What is the payment charge and currency for a given payment method? Does it include VAT?
CQ10: What is the mail address and which are the contact details of the offering business entity?
CQ11: Which are the locations from which the product or service is being provided, what are the contact details and opening hours of each location?
+ Upper Ontology Part
Martin Heppmhepp@computer.org
Requirements / Features
9
• Support for ranges and units of measurements• Support for all common business functions, like sell, lease, dispose, repair, etc.• Compatible with eclassOWL and unspscOWL• Supports all ISO 4217 currencies• Supports defining eligible regions• Suits both for explicit instances, product models, and anonymous instances• Supports common delivery and shipping methods• Supports accepted payment methods• Offerings can be constrained to certain eligible business entities• A warranty promise, i.e., its duration and scope can be specified• Different prices for different types of customers or for different quantitities can be expressed• Charges for certain payment or delivery options can be specified; the latter also individually per
region.• Support for product bundles, for all kinds of units of measurements (2 kg butter + 2 cellphones for €
99 would be no problem).• Compatible with international standards: ISO 3166, ISO 4217, UN/CEFACT, eCl@ss, and UNSPSC• Minimal requirements on reasoner support - any RDF-S-style reasoner, OWL DLP, DL, or ter Horst
reasoner will work.• Supports price ranges, list prices, time-zones, EAN/UCC/UPC codes, GLN/ILN, and DUNS
Martin Heppmhepp@computer.org
Data, Standards, Ontologies
10
Martin Heppmhepp@computer.org
Core Conceptual Structure
• Business Entities
• Offerings
• Products and Services
• Web Resources
11
Martin Heppmhepp@computer.org
Domain Capture
12
Martin Heppmhepp@computer.org
Design Considerations
• Suitable Ontology Language
• Ranges and Intervals; Datatypes
• Models, Classes, Instances
• Existential Quantification
• N-Ary Relations
• Licensing
13
Martin Heppmhepp@computer.org
Suitable Ontology LanguageRequirements:
• Must work with Semantic Web infrastructure as available today
• Must work with lightweight, RDFS-style reasoners
• Combining the ontology with ontologies or knowledge bases in OWL DL should not lead to a model beyond DL (e.g. OWL Full)
• Avoid layering problems between RDFS and OWL
14
Approach: Use OWL DL syntax for RDF-S elements, i.e. a subset of the closure of OWL DLP:
owl:Ontologyowl:Classowl:ObjectPropertyowl:DatatypePropertyrdfs:subClassOfrdfs:subPropertyOfrdfs:comment rdf:datatyperdf:type
Martin Heppmhepp@computer.org
Ranges and Intervals
15
hasValue rdfs:SubPropertyOf hasMaxValue, hasMinValue
Martin Heppmhepp@computer.org
Models, Classes, Instances, and Existential Quantification
16
ex:mySony100
toy:TVSet
gr:ProductOrService
rdf:type
gr:ActualProductOrServiceInstance
gr:ProductOrServiceModel
gr:ProductOrServicesSomeInstancesPlaceholder
rdfs:subClassOf
rdfs:subClassOf
rdfs:subClassOf
rdfs:subClassOf
rdf:type
ex:TheSony100Model
ex:SomeSony100s
rdf:type
rdf:type
rdf:type
rdf:type
Requirement: Use the same library of features for
models and products
Problem: Inferring feature defaults for product instances from the product
model if specified.
Martin Heppmhepp@computer.org
Product Bundles
17
Martin Heppmhepp@computer.org
N-Ary Relationships
18Martin Heppmhepp@computer.org
includesObject amountOfThisGoodOffering
ProductOrServiceInstance
typeOfGood
QuantityTypeAndQuantityNode
hasUnitOfMeasurement
Unit of Measurement
Martin Heppmhepp@computer.org
License
• Goal: Give adopters certainty about permanent, royalty free access to the ontology
• Approach: Creative Commons Attribution 3.0 license.
19Martin Heppmhepp@computer.org
Martin Heppmhepp@computer.org
Reusing Existing Consensus
• Lot of pre-existing consensus
• Countries
• Currencies
• Locations
• Two basic approaches for reuse
• As ranges for literal values
• Replication as ontological instances
20
Martin Heppmhepp@computer.org
Minimal Example
21
BusinessEntity_1 Offering_1TypeAndQuantity
Node_1
QuantitativeValueFloat_1
UnitPriceSpecification_1
MySony100TVSet
gr:offers
http://www.electronics.com
rdfs:seeAlso gr:hasBusinessFunction gr:hasPriceSpecification
toy:TVSet
30
gr:hasValue
"CMT""
gr:hasUnitOfMeasurement
1.0
toy:hasScreenSize
"C62"
"C62"
200.0
""EUR""
rdf:type
gr:typeOfGood
rdf:type
rdfs:subClassOf
gr:includesObject
gr:Sell
gr:ProductOrService
gr:ActualProductOrServiceInstance
GoodRelations
Ontology
Products and
Services Ontology
Particular Offering
(Data)
gr:amountOfThisGood
gr:hasUnitOfMeasurement
gr:hasUnitOfMeasurement
gr:hasCurrencyValue
gr:hasCurrency
Martin Heppmhepp@computer.org
Pick-up in Industry and Academia
• Smart Information Systems
• ebSemantics
• Yahoo! SearchMonkey
• Virtuose Sponger Catridges for Amazon, eBay, and others expected
• etc.
22
Martin Heppmhepp@computer.org
Diffusion Strategy• Make Creating GoodRelations
Data Easy
• GoodRelations Annotator and Validator
• Exporters for popular Web Shops (using Triplify)
• Converters for Catalog Data Interchange Standards
• Recipes and Patterns
23
• Make Creating GoodRelations Data Attractive
• Search Engine Vendors
• Recommender Systems
• Foster the Development of Compatible Vocabularies
• eClassOWL
• ebSemantics
• myOntology
Martin Heppmhepp@computer.org
Client-side Rendering vs. Content Negotiation
24
Martin Heppmhepp@computer.org
Discussion and Future Extensions
• Richer Axiomatisation?
• Disjointness Axioms etc.
• Microformats Variant?
25
Martin Heppmhepp@computer.org
Additional Information
• Web Page
• Ontology
• Language Reference
• Primer
• Recipes
• Wiki
26
http://purl.org/goodrelations/
Martin Heppmhepp@computer.org
References1. 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 (forthcoming), Springer LNCS, Vol 5268, pp. 332-347.
2. Hepp, Martin: Products and Services Ontologies: A Methodology for Deriving OWL Ontologies from Industrial Categorization Standards, in: Int'l Journal on Semantic Web & Information Systems (IJSWIS), Vol. 2, No. 1, pp. 72-99, January-March 2006.
3. Hepp, Martin: The True Complexity of Product Representation in the Semantic Web, in: Proceedings of the 14th European Conference on Information System (ECIS 2006), June 12-14, 2006.
4. Hepp, Martin: ProdLight: A Lightweight Ontology for Product Description Based on Datatype Properties, Proceedings of the 10th International Conference on Business Information Systems (BIS 2007), April 25-27, 2007, Poznan, Poland, in: Abramowicz, Witold (Ed.): BIS 2007, Springer LNCS, Vol. 4439, pp. 260-272, 2007.
These and other papers are available at http://www.heppnetz.de/publications/
27
Martin Heppmhepp@computer.org
Thank you!http://purl.org/goodrelations/
Martin Heppmhepp@computer.org / http://www.heppnetz.de
28
Recommended