What will be there in V 2.0 (70% work done)

Code: AiCMSWorld003

What will be there in V 2.0 (70% work done)

NOTE: Please do not judge the upcoming text by looking at V1.0's logic and algorithms. The algorithms and working in V 2.0 are entirely different. We are actually working on two branches at a time.
 
This is the Dream Version. We started with a vision that this version would be 1.0. But soon, we realized that the real thinking system will not understand the content in the format we know now. The whole content presentation will be changed. Now, the content should have some measurable characteristics suitable for our AI system. Adapting to such a tricky development of content and digital presence will be hard for the users. So we broke the whole part in three versions. First version is just to introduce the concept of Dimensions, Content relations and adaptive fuzzy logic. By releasing this pre-system, we will be having a community that can continue to work with this system. We have done almost all the research and testing of our working codes with happy faces. This version will be including the following features and will be released by the end of this (2014) year.
 
What's planned is in Version 2.0?

  • Self selection of important factors: Currently, we are defining various factors into the system, like visitor's country, time of visit, OS of the user, the browser used, etc. These are trigger parameters to start thinking about a person and their orientation and take the initial perception. As for the rest, the system learns by the user's behaviour on the site and updates knowledge about the visitor. But V2.0 will be equipped with self assessment of important factors. The CMS itself will gather all important factors that should be taken into account. If the technology updates and the browsers provide other information which is sent to the server, then it will also be automatically taken as triggering parameter. If that information works out to be important, then it will be shared to other xEpan CMSs.
  • Knowledge sharing and community building: This is an automated process done by xEpan itself with other xEpan instances. By means of our own centralized system, each instance can find other xEpan instances and can communicate with them (if the developer or the administrator gives permission). They share data with other xEpans that do not belongs to their own industry. Thus, it lays down a foundation of friendship between the CMSs. Now, the xEpan instance whose data is giving you better goal rate becomes a good friend of your xEpan instance. So, more time will be spent with this friend (entertaining more requests and giving more bandwidth to this friend and sharing more data with this friend rather than other friends).
  • Shares new algorithms and factors with good friends: This can be in terms of getting more information about a visitor from any new web-service launched that gives information about visitors in detail (like today various geological information services available, that can return geological information from the IP). If a CMS comes to know, or is fed to know about such information by a developer, it may share that information to another xEpan which it considers a best friend.
  • Parental Control: This gives us a better control on our CMS that we (administrators) can control as a threshold to communicate and the level of data and knowledge to be shared with friends.
  • Performance: This is a real critical task for us to manage. So far, the performance is good but the data interchanging and processing is a bottleneck to us. Since our learning algorithms are unique they are not a problem, but we are assuming that by the time this system matures, we will be having more powerful servers.
  • A Coder's Library: These tools will be like controlled viruses that friends (xEpan Friends) will circulate to fetch more information about the visitor. Say, These codes may have tricks to fetch the data from all the open tabs to know more about what that particular user is up to. If the systems and browsers, against which the hack is being implemented, find it out and stop it, then xEpan will make a negative remark with the current configuration of the execution. So, based on overall remarks, if it is found that browsers below a particular version are vulnerable to this threat, xEpan will try a trick to know whether a user is using such versions or not, and with its own learning process, this code will be circulated to it's xEpan friends.
  • Pre-Trained Mindsets to purchase: One of our teams is working on storing the experience gained without storing the historical data. For example, if we get pinched by a needle, it hurts and we remember the location, but after a few years we only remember the pain produced by the pinching of a needle, but not the way we were pinched in the past. So, we are planning to sell the minds which remember the experiences, as well as gains it's own experience. It is equivalent to hiring an expert with experience of 1 year, 5 years or 10 years, or like hiring a graduate or an MBA.
 
 
And no, this is not science fiction. We are launching this whole system tentatively by the end of this (2014) year. We are aware that our working pace is slow, and that we still have to work more on optimizing the performance in terms of speed and accuracy. This can be solved by out of the box thinking and approaching.
 
"The solutions of big problems are simple, but explanations of simple things are always complex" -Gowrav Vishwakarma
 
 
Research Done: 70%
Coding Done: 20%
Date: 2014-10-12