Good day- 

each has its own benefits, but (in my considered view), i would opt for ontology considering that we are dealing with the 'knowledge' aspect. Ontology based modelling adds the artificial intelligence component and more, and  i feel is more flexible and versatile in relation to the phenomenon of 'Knowledge'. The Mathematical approach would be good in terms of predictive capabilities but it all depends on what you wish to achieve by your knowledge modelling. Perhaps run a search on MEta vs Ontology' 'in relation' to what you wish your knowledge model capabilities to be. Since knowledge is versatile can be measured in a variety of ways, i personally wouldn't want to limit it to a mathematical design but more a flexible Ontology based platform.

OK..... and what you think...what will be more suitable for designing complete architecture or framework ? In ontology we can extract the components in model, whereas we can use those extracted components in any modelling language (formal/informal) by using meta modelling techniques.. so i guess we can merge both of them as well.....

Hi

you can see this document

good luck

Hi Asad,

yes, i agree with your point made to my initial comment.

Mr. Hinds Document is quite interesting as well.

All the best.

SS

Hello Asad,

Ontology and mathematical models are not mutually exclusive and using one does not preclude the use of the other.. There is a place in an ontological framework for models and model bases, which are analogous to databases and knowledge bases. Knowledge repositories can benefit from both.

Best regards,

Marion

Hello,

you may want to have a look at SPIN, which offers metamodelling capabilities that can be used to complement the open world reasoning of standard reasoners for ontologies. In a blog post I recently discussed the related problem of defining a schema for an RDF-based visualisation language (RVL) within the RDF technical space (i.e. without using conventional metamodelling languages). For now I ended up using SPIN, which allows me for reusing (for example) the types already existing in the ontologies, while constraints can be added with SPIN constraints. However, currently, there is also progress on the development of a W3C standard (SHACL) to replace much of what is possible with SPIN.

Cheers,

Jan

http://spinrdf.org/spin.html

http://www-st.inf.tu-dresden.de/semvis/blog/?p=332

http://www.w3.org/2014/data-shapes/wiki/Main_Page

Hi! I think that if the focus is in knowledge representation of the domain, where the  knowledge involved may be complex, ambiguous, etc., the use of ontologies to give a formal and clear semantics is a good idea.

Best! Ana

Hi,

Discussion goes interesting as well as complex i guess...... if we hold one side (say meta modelling) we should go for architecture side as well for better results. Also there are many model based framework / languages and tools which supports meta modelling like EMF, etc.

so, the point is, we need such a solution which supports the Programmer (Developers) first, secondly if it support the complete project methodology process it will be additional feature. Currently we need to focus on developers track. which tool or technology will me more beneficial ?