Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

rdf - Mixing EquivalentClass and SubClass in OWL -


i'm curious mixing subclassof , equivalentclass in class description, , how reasoner behave.

specifically, if have both equivalentclass , subclassof assertion same class, both equivalentclass , subclassof conditions need satisfied individual classified in class, or equivalentclass?

or bad practice?

for example (declarations omitted):

objectpropertyrange(:format :bar) objectpropertyrange(:format owl:thing) equivalentclass(:foo objectsomevaluesfrom(:format :bar)) subclassof(:foo :sna) 

i want ensure in case below, :x classified :foo, because both equivalentclass , subclassof assertions satisfied:

classassertion(:x :sna) objectpropertyassertion(:format :x :somebar) 

but :y not, because subclassof not satisfied:

classassertion(:y :notasna) objectpropertyassertion(:format :y :someotherbar) 

thanks,

jonathan

i don't understand question i'll try clarify things. first of all, following axioms seem irrelevant question (and second redundant anyway because owl:thing property's range):

objectpropertyrange(:format :bar) objectpropertyrange(:format owl:thing) 

the other thing equivalentclasses-axioms can seen syntactic sugar subclassof-axioms, e.g.

equivalentclasses(c1 c2) 

is logically equivalent to

subclassof(c1 c2) subclassof(c2 c1) 

so can rewrite equivalentclasses as:

subclassof(objectsomevaluesfrom(:format :bar) :foo) subclassof(:foo objectsomevaluesfrom(:format :bar)) 

this maybe simplify understanding of entailments ontology makes.

now, if say:

classassertion(:x :sna) objectpropertyassertion(:format :x :somebar) 

i assuming want say:

classassertion(:x :sna) classassertion(:somebar :bar) objectpropertyassertion(:format :x :somebar) 

this entails :x both :foo , :sna, possible because :foo subclass of :sna.

when say

classassertion(:y :notasna) objectpropertyassertion(:format :y :someotherbar) 

i assume mean:

classassertion(:y :notasna) classassertion(:someotherbar :bar) disjointclasses(:notasna :sna) objectpropertyassertion(:format :y :someotherbar) 

this logical inconsistency because :y entailed :foo (which subclass of :sna), @ same time :y asserted in class disjoint :sna.

note didn't use knowledge that

subclassof(:foo objectsomevaluesfrom(:format :bar)) 

which followed equivalentclasses-axiom.


Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -