Context Navigation

Changes between Version 4 and Version 5 of OWL

v4	v5
7	7
8	8	= OWL use cases =
	9	== Modeling ==
	10	Ontologies are created to fix terms in their meaning. So that confusion about their definition is avoided.
	11	Many ontologies are written in the OBO format an easily human readable text format. For example GO is defined in OBO.
	12	OWL is a more formal definition of an Ontology. This gives it a lot of powerful features that one can use. While also incurring
	13	a steep learning curve.
	14
9	15	== Reasoning ==
10	16
11		== Inferring Logic ==
	17	OWL allows reasoning over statement using description logic. That means that one does not need to encode all implied information in your system to be able to get conclusive data.
	18
	19	e.g.
	20	jenny a :woman
	21	jenny :hasMother mum;
	22	mum a :mother;
	23
	24	In a classical system without reasoning when asking the question select ?s where {?p rdf:Type :woman}; will only answer jenny.
	25
	26	After adding the following OWL axiom.
	27	:mother owl:subClassOf :woman
	28
	29	The answer would become
	30	jenny and mum.
	31	As the axiom leads to the inference that mum is a :Woman. So the new triple
	32	mum a :woman
12	33
13	34	== Constraint Validation ==
	35
	36	Lets add a simple constraint too the Ontology. Being rather conservative.
	37	:man owl:disjointWith :woman
	38
	39	That means if we had made a mistake filling our triple store and we had added a.
	40	mum a :man
	41	our OWL logic would raise a contradiction.
	42
	43	A product meant for this is
14	44	[http://clarkparsia.com/pellet/icv]