Semantic Database realizes the Semantic Web vision of Sir Tim Berner Lee. This space will hold the thoughts and ideas that comes to me while talking to different people who are interested in this topic. Semantic DB is an attempt to create a Database(knowledge base) where each data elements are related to every other elements based on meaning. I am Still working on it. If you are reading this then pls feel free to write your comment on the posts you are reading.

Facebook Badge

Search This Blog

Loading...

About Me

Samir Kumar Mishra

To
make a significant contribution in the area of Semantic Web, Artificial
Intelligence and Inferencing. My current research interest includes
building a representation model for heterogeneous data and inference
those data elements (facts).

In 15 yrs of Industry experience I worked on Delphi and MS technology
for 9+ yrs and almost 4.5 yrs on Java/J2EE as Technical
Architect/Specialist with various companies. Worked with clients based
in EU, North America, Asia-Pacific, India etc. Currently based in
Brisbane (Australia).

- Strong ability to take up a complex problem and break it into smaller and manageable solution.
- Capability to be a contributor at any level and in any area of a project life cycle.
- Strong ability to deliver the quality product under demanding and Tight schedule projects.
- Currently making my way into the world of Artificial Intelligence, Multi-Agent systems, Semantic Web and Web 4.0
- Managed development team(s) consisting of 3 to 46 members.
- Extensive hands on experience working with companies adhering to
quality standards like SEI-CMM Level 5, ISO 9000-2000 and Six Sigma.
- Assessed with Australian Computer Society as System Designer

Specialties

Specialize in System and Architecture design for Multitier and Distributed Systems.
Adapting and practicing new Technology and methodology.

System Architecture, Object Modeling, Java, Delphi.
Motivating team members to be research oriented while continuing with normal day-to-day work.

Mentoring team for Out of Box Thinking and strive for continuous improvement.

Delivering a Tight schedule, High pressure project on time and meeting High Quality Standards.

Followers

Thursday, January 06, 2011

Its been quite some time since I did a blog post. It took me a while to understand what I want to get out of my reasoning engine. After spending considerable amount of time to understand how reasoning engine should work, I came up with these (mentioned below) points to summarize how the reasoning engine should behave.

How to Select the entities for Reasoning? This includes the mention of what kind of entities we are interested in, what is the selection criteria for those entities to be filtered from others in the knowledgebase etc.

What information is needed from those objects? Not all attributes of the entities are useful in output result. We need to be specific about what attributes we are interested in from the selected entities.

How the details needs to be presented in output? The representation of output object (entity).

What level of detail is good enough? We need to define a boundary where we can say the detail presented is sufficient enough for us to proceed further.

What can be derived directly and what can be derived indirectly?

That's all for now. Will try to post regularly now (one of my new year resolution). Until Next Time... !!!

11
comments:

Samir, I have started looking at the same issue. We are building a membership site for entrepreneurs, small biz owners, startups, etc. on a joomla platform. I have just started designing the dbase anticipating web 3.0 - lets talk. Bill

It was very useful for me. Keep sharing such ideas in the future as well. This was actually what I was looking for, and I am glad to come here! Thanks for sharing the such information with usdoctor reviews by patientsfind doctor list