...
We strongly prefer JSON but we can produce XML if you buy us a beer.
We have tested the DEV implementation against a random sample of 1% of the Treasurers data and the success rate is about 95%.
You can see the unit tests here.
We get parse failures on addresses like this one: PMB 169 3701 SACRAMENTO ST
In the next iteration I am planing on including geocoding and zip code look up.
Examples
Here Below are validation links to 10 random addresses from the Treasurer's database:.
1501 HOWARD ST
PMB 169 3701 SACRAMENTO ST
1560 DAVIDSON AVE
331 CORTLAND AVE
2000 FILLMORE ST
1017 DIVISADERO ST
1618 UNION ST
2250 PINE ST
559 PACIFIC AVE
157 NOE ST
1000 18TH
The JSON is formatted for readability but your browser may obscure that.
The way to see the nicely formated JSON is to right click on the web page and select "view source".
The Chrome browser has a nice feature here:
view-source:http://10.250.60.189/validate/streetAddress/1560%20DAVIDSON%20AVE/