> Not sure why you're going via JSON to HTML though. May be you are wondering that based on the example above. The actual parsed object is more complex: It's nested objects and some of those objects have seq type members.
I am thinking that JSON would be a good intermediate format. The final HTML is for sharing the parsed data for others to study. Idea is to convert JSON into HTML tables (which can contain nested tables). I need to still finalize the structure of the nested data. > To parse it into JSON all you need to do is change how the Record type is > generated, should be pretty easy. +1 I haven't yet reached that point. But yes, the Json type is easy to play with.
