rules from an xml file

[jonny]

I have a python code that manages some parameters using some variable
rules that may change from day to day. I'd like that the code will
self-modify according to rules parsed from a xml file:

example:

<rules>
<rule01>
<if>
<or>
<lessthan par_1="glicemyA tMorning" par_2="80"/>
<lessthan par_1="glicemyA tNight" par_2="80"/>
<and>
<greaterthan par_1="glicemyA tMorning" par_2="0"/>
<or>
<equalto par_1="urine" par_2="0"/>
<equalto par_1="urine" par_2="+/-"/>
<equalto par_1="urine" par_2="+"/>
</or>
</and>
</or>
</if>
<then>
<sendmessage>So mething is wrong!</sendmessage>
</then>
</rule01>
<rule02... </rule02>
<rule03... </rule03>
</rules>

Due to the fact that rules may change, I have to manage the python
program, parsing the whole xml file, and self-modify the python code
according to these variable rules.
How can I do?

[Diez B. Roggisch]

jonny wrote:

I have a python code that manages some parameters using some variable
rules that may change from day to day. I'd like that the code will
self-modify according to rules parsed from a xml file:

example:

<rules>
<rule01>
<if>
<or>
<lessthan par_1="glicemyA tMorning" par_2="80"/>
<lessthan par_1="glicemyA tNight" par_2="80"/>
<and>
<greaterthan par_1="glicemyA tMorning" par_2="0"/>
<or>
<equalto par_1="urine" par_2="0"/>
<equalto par_1="urine" par_2="+/-"/>
<equalto par_1="urine" par_2="+"/>
</or>
</and>
</or>
</if>
<then>
<sendmessage>So mething is wrong!</sendmessage>
</then>
</rule01>
<rule02... </rule02>
<rule03... </rule03>
</rules>

Due to the fact that rules may change, I have to manage the python
program, parsing the whole xml file, and self-modify the python code
according to these variable rules.
How can I do?

So, essentially you are creating a dynamic language? But you already have
one - python!

Who's responsible for creating these rules, and what do they allow to be
done? Because I'd rather use python snippets to define them, that you
compile using the exec-function.

If you insist on using XML, use some module like lxml to parse and create
your own language constructs.

Just a note: the use of "par_X" as attributes is unfortunate, to say the
least. It doesn't allow for easy argument swapping, can cause troubles
because you delete one attribute and miss renaming the others, and in
general it's not good design to have arbitrary numbers of parameters.

Instead, you better go with a nested param-tag.

Diez

[Marc 'BlackJack' Rintsch]

On Mon, 24 Sep 2007 13:42:05 +0200, Diez B. Roggisch wrote:

jonny wrote:

><rules>
<rule01>
<if>
<or>
<lessthan par_1="glicemyA tMorning" par_2="80"/>
<lessthan par_1="glicemyA tNight" par_2="80"/>
<and>
<greaterthan par_1="glicemyA tMorning" par_2="0"/>
<or>
<equalto par_1="urine" par_2="0"/>
<equalto par_1="urine" par_2="+/-"/>
<equalto par_1="urine" par_2="+"/>
</or>
</and>
</or>
</if>
<then>
<sendmessage>So mething is wrong!</sendmessage>
</then>
</rule01>
<rule02... </rule02>
<rule03... </rule03>
</rules>
[…]

[…]
Just a note: the use of "par_X" as attributes is unfortunate, to say the
least. It doesn't allow for easy argument swapping, can cause troubles
because you delete one attribute and miss renaming the others, and in
general it's not good design to have arbitrary numbers of parameters.

Quite the same is true for numbers in tag names. If you (the OP) need to
number the rules better use an attribute for the numbers.

Ciao,
Marc 'BlackJack' Rintsch

[Diez B. Roggisch]

Marc 'BlackJack' Rintsch wrote:

On Mon, 24 Sep 2007 13:42:05 +0200, Diez B. Roggisch wrote:

>jonny wrote:

>><rules>
<rule01>
<if>
<or>
<lessthan par_1="glicemyA tMorning" par_2="80"/>
<lessthan par_1="glicemyA tNight" par_2="80"/>
<and>
<greatertha n par_1="glicemyA tMorning" par_2="0"/>
<or>
<equalto par_1="urine" par_2="0"/>
<equalto par_1="urine" par_2="+/-"/>
<equalto par_1="urine" par_2="+"/>
</or>
</and>
</or>
</if>
<then>
<sendmessage>So mething is wrong!</sendmessage>
</then>
</rule01>
<rule02... </rule02>
<rule03... </rule03>
</rules>
[…]

[…]
Just a note: the use of "par_X" as attributes is unfortunate, to say the
least. It doesn't allow for easy argument swapping, can cause troubles
because you delete one attribute and miss renaming the others, and in
general it's not good design to have arbitrary numbers of parameters.

Quite the same is true for numbers in tag names. If you (the OP) need to
number the rules better use an attribute for the numbers.

I meant of course

<equalto>
<param>0</param>
<param>+</param>
</equalto>

Diez