Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Restaurant Ontology

No description
by

Diana Videanu

on 18 March 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Restaurant Ontology

Property and Class Axioms
We can distinguish different type of classes and properties based on the way they relate to other classes and properties

Application

A franchisee which seeks to maintain a high standard throughout for their brand.


We envision our ontology to be used in something rather similar to a pizza express or zizzi’s environment.

SPARQL Queries
Classes
Properties
A property is a relation that describes the characteristics of a class. It's role is to connect classes and subclasses in a logical way. They can be object or data properties, and have different types.

We have multiple properties in our ontology. We also have a sub property.

A few examples.
Introduction
- Restaurant Ontology -

The domain of our ontology is purposefully done so it will suit all restaurants that are franchises hence they adhere to certain protocols.

All domain and ranges are denoted, as well as the sub classes - showed in the following diagram.
Restaurant Ontology
Staff Class & Co.
'isBookedBy' Property
Object property
Domain: Table
Range: Customer
Inverse: 'booked'
Customer and Booking Classes
Here, we can see the Customer class, as well as the Booking class. The Customer class contains customer information such as name, phone number and email. The Booking class contains all the reservation information.
'hasSalary' Property
Data property
Domain: Staff
Range: integer
This property has two particularities: it applies to the whole Staff class, and it has a restriction.
Subproperty example
Property Types
object: employs, proposes
datatype: hasSalary
annotation: we used for individuals
functional: hasCustomerEmail
inverse-functional: isBookedBy
Property Axioms
inverse: isBookedBy, booked
property chains: serves(caters o isBookedBy

Classes restrictions on properties
This allows for a better control on class definition:
universal:Item contains Menu
cardinality:caters(max 3), hasSalary>800
Class Axioms
disjoint: staff,table
complement: AlcoholicDrinks, NonAlcoholicDrinks
Scenarios

Zadd is a restaurant chain that has many franchises over the country.

Two scenarios which demonstrate the use of our programme:

Scenario 1: Alex

Scenario 2: Josie


SPARQL Queries
SPARQL Queries
PREFIX sw: <http://www.semanticweb.org/dragos_fotball/ontologies/2014/untitled-ontology-6>

SELECT ?staff ?salary
WHERE {
?staff sw:hasSalary ?salary.
}
ORDER BY DESC(?salary)
LIMIT 4
In this example, we can see that we have the Staff class, which contains all the employees of the Restaurant. Staff has subclasses, regrouping all the types of employees.
Identify what takeaways were worth more than 30 and what items they contained:
PREFIX sw: <http://www.semanticweb.org/dragos_fotball/ontologies/2014/untitled-ontology-6>

SELECT ?items ?cost
WHERE {
?takeaway sw:contains ?items
?takeaway sw:costOfTakeaway ?cost.
FILTER (?cost > 30).
}
Identify the four highest paid staff and show their salaries.
The purpose of SPARQL queries is to read the database and upon selected requirements to generate useful results.

In this case, SPARQL queries were written in order to find out information about the restaurant and/or its related properties and attributes.


According to the Semantic Web Terminology (w3.org), a class is a grouping, a set, of resources with similar characteristics.


In our ontology, we have multiple classes, which include for example Staff, Expenses, Inventory, Menu, Booking, Customer, Takeaway, Address etc...
They all have subclasses of their own and some of them have other subclasses.
'caters’ and ‘isBookedBy’ are subproperties of ‘serves’ because a waiter caters a table booked by a customer, the waiter serves that table. It creates a property chain as ‘caters’ and ‘isBookedBy’ result in ‘serves’.
The main principle of a franchise restaurant's features are intact due to the classes we have implemented such as:

Staff
Booking
Menu
Address
Expenses
Inventory

?
Questions
Full transcript