"Orthogonality and the DRY Principle"

XML is at the core of the emergence of a semantic web.
There is a nice explanation on Semaview web site:

"What is an ontology?<br>An ontology defines the terms used to describe and represent concepts. Ontologies are used to describe concepts as well as their inter-relationships. Being able to standardize the definition of real-world concepts becomes very powerful as you begin to investigate knowledge that spans across multiple domains."

Semaview "At-a-Glance" Illustration Series: The Semantic Web
Designed as a one minute overview of the Semantic Web, this illustration discusses a half dozen key points in language that can be understood by managers and techies alike.

<IMG SRC=http://www.semaview.com/img/diag_semwebexplained.gif>


Semaview "At-a-Glance" Illustration Series: RDF and XML
XML and RDF are two complimentary technologies being used to build an internet that is more intelligent. As a developer, you must decide which combinations of standards to use for your application. While XML is more widely adopted, and has many more tools and examples to reference, the addition of RDF gives your computer more knowledge about what your data actually means. This illustration discusses approximately a dozen key points in language that can be understood by managers and techies alike.
<IMG SRC=http://www.semaview.com/img/rdfxml_web.gif>

Quote from harrytrader:

The advantage of XML is that it can be more intelligent than rough datas since the datas can be turned into a programming langage notably it can be used to build an expert system rules engine. Also the orthogonality can be assured by using context which in fact is a core concept of XML query langage since a command result will depend on the context it is applied upon. Operationally the context is defined as a parental node. As I have said already context is what is of huge importance: a market's pattern will probably fail if the context is badly appreciated. Market's context is difficult to appreciate because there are many variables to be taken into account and that can conflict one with another, but by using it through XML it can benefit from the concept implemented by XML.

Many people stopped at concept levels because they don't know how to realise the concepts concretely. That's why idea is easy, realising them is more difficult. If you remember I have posted previous year this idea:

"Building Learning into Everyday Work
http://www.gurteen.com/gurteen/gurteen.nsf/0/92D41499A691935C802569910043207C/

I am building tools for my learning group inspiring from this idea which is coherent within the higher framework I am using which is famous Deming's PDCA wheel (Plan Do Check Action) of CONTINUOUS progress. "

So I have let a few months before maturing and realising the stuff but now I have a real thing prototype that works (it is not screencopy) and I'm hapy of the result. I'm not doing the job of programming myself so I had to wait for my associate or an other engineer to do the coding but as for the directives of conception it's me, it is also me that writes the rules of the expert system since only I have the knowledge to do so.

What I intend to add is configuring the tool either to be in learning mode for people new to the method, either in expert mode for people already accustomed to the system.
More...
 
The problem with XML is that it is really verbose: we now have 5000 lines of variables and program :mad: and it is not finished yet but the functionality is more my priority that optimising the coding part at the moment.

Quote from harrytrader:

XML of course is not presented to the user interface, it is only in the background for data and expert system storage (the knowledge base). The user interface will be something like this (the style of the dialog can be more or less serious this is the fun version) :
<IMG SRC=http://www.elitetrader.com/vb/attachment.php?s=&postid=430537>
The merlin wizard gives the analysis.

The man on the tea pot filled with gold transforms merlin's analysis into a trading plan.

The snake represents the "poke yoke" (Luto's thread):
http://www.elitetrader.com/vb/showthread.php?s=&postid=422879&highlight=poke+yoke#post422879

The engine is not finished yet: for example the target can be refined further but it gives an idea.
More...
 
Quote from harrytrader:

The problem with XML is that it is really verbose: we now have 5000 lines of variables and program :mad: and it is not finished yet but the functionality is more my priority that optimising the coding part at the moment.
More...

I will also get a headache to transfer some excel formulas into XML like this one :D. Hmm there is some characters that don't pass in the post so the formula is truncated.

IF((MAX($D20:I20)<J20)*((DVAR(INDEX(SR2_TRIE,EQUIV(J20,SR2_TRIE,-1)+1),2) = MAX($D20:I20))),";255.0.0;2;LT/d",IF((DVAR(INDEX(SR2_TRIE,EQUIV(J20,SR2_TRIE,-1)+2))= MAX($D20:I20))*(IF(ESTNA(RECHERCHEH(";255.0.0;2;LT/d",$B21:I21,1)),1,RECHERCHEH(";255.0.0;2;LT/d",$B21:I21,1)="")),";255.0.0;2;LT/d",""))&SI((J20>J18)*(J20<I20)*(I20>H20)*(J20>H20)*(J20>MAX($C18:I18)),";255.0.0;2;Feynman LT/d","")&SI((J17=10)*(J20>J18)*(J20<MAX($C20:I20)),";255.0.0;2;Feynman LT/d","")&SI(I20=MIN($D20:$M20)*(MAX(L20:$L20)>MIN($D18:$M18)),";0.255.0;2;Feynman LB/d","")&IF(I20=MAX($D20:$M20),";255.0.0;2;Feynman LT/d","") ...
 
One of the most elegant aspects of making money is that it comes down to only one action (hitting the T) as a consequence of considering two truly orthogonal sets.

Coupling DRY to the strategy just as elegantly follows from only using feedback repitition in non intimate ways. Avoiding intimacy is done by the isolation strategies found in decoupling and least connectedness.

Corruption through multiple definition is a trivial concern in any elegant approach. Vapid as a possibility.

If ET goes beyond beginner and novice to hot $hit levels of trading, we will see the true vitality of using orthogonality in a corroborating function.

Making money is totally based upon change over time. Assimilating periodicity that occurs in independant systems is what boldly introduces orthogonality as a structural strength not attainable unless independant systems are merged in a time bound "process".
 
You must log in or register to reply here.
Back
Top