Design of lookup instance

Richard Braman
[hidden email]
561.748.4002 (voice)

http://www.taxcodesoftware.org
Free Open Source Tax Software

-----Original Message-----
From: Richard Braman [mailto:[hidden email]]
Sent: Tuesday, February 21, 2006 3:51 PM
To: [hidden email]
Subject: [ops-users] Design of lookup instance

Heres my problem/use case

 

I have two static "lookup" instances

1 containing a <taxtable>

the other an <earned-income-credit-table.>

 

I will be using the table(s) the same way to look up the <tax> or the <credit> using the respective table.  Each instance has an id to keep em seperated

 

assume I have 4 seprate nodes called

<filing-status>

<income>and

<tax>

<credit> in my <instance>

 

The logic for looking up the <tax> or the <credit> is the same, so I will use <tax> as an example.  I need help determining the best way to structure the data in

<taxtable>

 

based on the value of <income> and <filing-status> I need to lookup the value in the <taxtable> to set the value of <tax>

The <taxtable> data has the following features for each <item> and there are 2164 <item>s

an <income-equal-or-greater-than> element which is the lower limit of income for the stated tax

an <income-less-than> element which is the upper limit of income for the stated tax

a <tax-single> element which holds the amount of <tax> if the filer is single

and a <tax-married-filing-jointly> element which holds the amount of <tax> if the filer is married

 

The logic goes like this:

If <income> falls between <income-equal-or-greater-than> and <income-less-than>

then <tax> is equal to either <tax-single> if <filing-status> =1 or <tax-married-filing-jointly> =2

 

i have

<xforms:bind id="tax" nodeset="('main-instance')/form/tax" calculate="This is my question, What would be the xpath expression, and what would be the best way to structure <taxtable> to make the lookup most efficient and to minimize instance size">

 

Here is a crack at the xPath.  I don't know if it is right.  This assumes <taxable> looks like this

<taxtable>

<item>

<income-equal-or-greater-than>0</income-equal-or-greater-than> 

<income-less-than>5</income-less-than>

<tax-single>0</tax-single>

<tax-married-filing-jointly>0</tax-married-filing-jointly>

</item>

....more items

</tax-table>

 

if instance('main-instance')/form/income >= instance('taxtable')/item/income-equal-or-greater-than

&&  instance('main-instance')/form/income < instance('taxtable')/item/income-less-than

&& instance('main-instance')/form/filing-status = 1

instance('taxtable')/item/tax-single

 

 

if instance('main-instance')/form/income >= instance('taxtable')/item/income-equal-or-greater-than

&&  instance('main-instance')/form/income < instance('taxtable')/item/income-less-than

&& instance('main-instance')/form/filing-status = 2

instance('taxtable')/item/tax-married-filing-jointly

 

Is is possible to have to xPath ifs in the same xforms calculate

 

I am designing, so I can call the nodes in <tax-table> whatever I want and I can structure it whatever way is best, maybe the nodes should be attributes.

 

Your comments are appreciated.

 

 

 

 

 

 

Richard Braman
[hidden email]
561.748.4002 (voice)

http://www.taxcodesoftware.org
Free Open Source Tax Software

 

test-taxtable-logic.xhtml (2K) Download Attachment

-----Original Message-----
From: Richard Braman [mailto:[hidden email]]
Sent: Tuesday, February 21, 2006 6:03 PM
To: [hidden email]
Subject: RE: [ops-users] Design of lookup instance

I created the attached file to play with my prototype for this part of my app, but I am getting a strange error on my local copy of OPS

XForms error: Node is not an element or attribute

see http://24.75.221.234:8080/taxcode/1040ez/test for example

 

I ran the file in orbeons sandbox, and it doesn't show up.  I know it has something to do with the CSS, because I had to remove all of the user defined css code in the themes.xsl file to get it to show up on my OPS.

 

I have tried just about everything I know of to get arid of the error, but it is being pesky.  I also notice that the initial value for <income> in my instance isn't showing up,

that has to have something to do with it.

 

 

-----Original Message-----
From: Richard Braman [mailto:[hidden email]]
Sent: Tuesday, February 21, 2006 3:51 PM
To: [hidden email]
Subject: [ops-users] Design of lookup instance

Heres my problem/use case

 

I have two static "lookup" instances

1 containing a <taxtable>

the other an <earned-income-credit-table.>

 

I will be using the table(s) the same way to look up the <tax> or the <credit> using the respective table.  Each instance has an id to keep em seperated

 

assume I have 4 seprate nodes called

<filing-status>

<income>and

<tax>

<credit> in my <instance>

 

The logic for looking up the <tax> or the <credit> is the same, so I will use <tax> as an example.  I need help determining the best way to structure the data in

<taxtable>

 

based on the value of <income> and <filing-status> I need to lookup the value in the <taxtable> to set the value of <tax>

The <taxtable> data has the following features for each <item> and there are 2164 <item>s

an <income-equal-or-greater-than> element which is the lower limit of income for the stated tax

an <income-less-than> element which is the upper limit of income for the stated tax

a <tax-single> element which holds the amount of <tax> if the filer is single

and a <tax-married-filing-jointly> element which holds the amount of <tax> if the filer is married

 

The logic goes like this:

If <income> falls between <income-equal-or-greater-than> and <income-less-than>

then <tax> is equal to either <tax-single> if <filing-status> =1 or <tax-married-filing-jointly> =2

 

i have

<xforms:bind id="tax" nodeset="('main-instance')/form/tax" calculate="This is my question, What would be the xpath expression, and what would be the best way to structure <taxtable> to make the lookup most efficient and to minimize instance size">

 

Here is a crack at the xPath.  I don't know if it is right.  This assumes <taxable> looks like this

<taxtable>

<item>

<income-equal-or-greater-than>0</income-equal-or-greater-than> 

<income-less-than>5</income-less-than>

<tax-single>0</tax-single>

<tax-married-filing-jointly>0</tax-married-filing-jointly>

</item>

....more items

</tax-table>

 

if instance('main-instance')/form/income >= instance('taxtable')/item/income-equal-or-greater-than

&&  instance('main-instance')/form/income < instance('taxtable')/item/income-less-than

&& instance('main-instance')/form/filing-status = 1

instance('taxtable')/item/tax-single

 

 

if instance('main-instance')/form/income >= instance('taxtable')/item/income-equal-or-greater-than

&&  instance('main-instance')/form/income < instance('taxtable')/item/income-less-than

&& instance('main-instance')/form/filing-status = 2

instance('taxtable')/item/tax-married-filing-jointly

 

Is is possible to have to xPath ifs in the same xforms calculate

 

I am designing, so I can call the nodes in <tax-table> whatever I want and I can structure it whatever way is best, maybe the nodes should be attributes.

 

Your comments are appreciated.

 

 

 

 

 

 

Richard Braman
[hidden email]
561.748.4002 (voice)

http://www.taxcodesoftware.org
Free Open Source Tax Software

 

-----Original Message-----
From: Richard Braman [mailto:[hidden email]]
Sent: Tuesday, February 21, 2006 8:45 PM
To: [hidden email]
Subject: RE: [ops-users] Design of lookup instance

Well, I at least got arid of the XForms error: Node is not an element or attribute error.  My XPath still needs work though.

It seems like you cannot define your instance right inside in the model, you have to use the src="oxf://path-to-instance"

or it busts.  Why is this?

-----Original Message-----
From: Richard Braman [mailto:[hidden email]]
Sent: Tuesday, February 21, 2006 6:03 PM
To: [hidden email]
Subject: RE: [ops-users] Design of lookup instance

I created the attached file to play with my prototype for this part of my app, but I am getting a strange error on my local copy of OPS

XForms error: Node is not an element or attribute

see http://24.75.221.234:8080/taxcode/1040ez/test for example

 

I ran the file in orbeons sandbox, and it doesn't show up.  I know it has something to do with the CSS, because I had to remove all of the user defined css code in the themes.xsl file to get it to show up on my OPS.

 

I have tried just about everything I know of to get arid of the error, but it is being pesky.  I also notice that the initial value for <income> in my instance isn't showing up,

that has to have something to do with it.

 

 

-----Original Message-----
From: Richard Braman [mailto:[hidden email]]
Sent: Tuesday, February 21, 2006 3:51 PM
To: [hidden email]
Subject: [ops-users] Design of lookup instance

Heres my problem/use case

 

I have two static "lookup" instances

1 containing a <taxtable>

the other an <earned-income-credit-table.>

 

I will be using the table(s) the same way to look up the <tax> or the <credit> using the respective table.  Each instance has an id to keep em seperated

 

assume I have 4 seprate nodes called

<filing-status>

<income>and

<tax>

<credit> in my <instance>

 

The logic for looking up the <tax> or the <credit> is the same, so I will use <tax> as an example.  I need help determining the best way to structure the data in

<taxtable>

 

based on the value of <income> and <filing-status> I need to lookup the value in the <taxtable> to set the value of <tax>

The <taxtable> data has the following features for each <item> and there are 2164 <item>s

an <income-equal-or-greater-than> element which is the lower limit of income for the stated tax

an <income-less-than> element which is the upper limit of income for the stated tax

a <tax-single> element which holds the amount of <tax> if the filer is single

and a <tax-married-filing-jointly> element which holds the amount of <tax> if the filer is married

 

The logic goes like this:

If <income> falls between <income-equal-or-greater-than> and <income-less-than>

then <tax> is equal to either <tax-single> if <filing-status> =1 or <tax-married-filing-jointly> =2

 

i have

<xforms:bind id="tax" nodeset="('main-instance')/form/tax" calculate="This is my question, What would be the xpath expression, and what would be the best way to structure <taxtable> to make the lookup most efficient and to minimize instance size">

 

Here is a crack at the xPath.  I don't know if it is right.  This assumes <taxable> looks like this

<taxtable>

<item>

<income-equal-or-greater-than>0</income-equal-or-greater-than> 

<income-less-than>5</income-less-than>

<tax-single>0</tax-single>

<tax-married-filing-jointly>0</tax-married-filing-jointly>

</item>

....more items

</tax-table>

 

if instance('main-instance')/form/income >= instance('taxtable')/item/income-equal-or-greater-than

&&  instance('main-instance')/form/income < instance('taxtable')/item/income-less-than

&& instance('main-instance')/form/filing-status = 1

instance('taxtable')/item/tax-single

 

 

if instance('main-instance')/form/income >= instance('taxtable')/item/income-equal-or-greater-than

&&  instance('main-instance')/form/income < instance('taxtable')/item/income-less-than

&& instance('main-instance')/form/filing-status = 2

instance('taxtable')/item/tax-married-filing-jointly

 

Is is possible to have to xPath ifs in the same xforms calculate

 

I am designing, so I can call the nodes in <tax-table> whatever I want and I can structure it whatever way is best, maybe the nodes should be attributes.

 

Your comments are appreciated.

 

 

 

 

 

 

Richard Braman
[hidden email]
561.748.4002 (voice)

http://www.taxcodesoftware.org
Free Open Source Tax Software