A list of requirements to help make the OPs vision a reality might be:-
1. Separation of concerns (ie, make it trivial to separate the Data and the View components from the surrounding html clutter). Currently it can be a pain to extract data from the DOM.
2. Allow the Data component to express arbitrary data shapes, including at least:
- 2-D tables
- n-dimensional data tables
- groups of related tables and schema (for a relational database)
- sparse data sets
- lists
- trees
- graphs
A lisp-like representation of data would provide adaptability to arbitrarily shaped data.
3. Make it easy to use:-
The webpage coder would write
<html>
<head>
<data name="data1">...lisp-like-data-structure...</data>
</head>
<body>
<view name="view1" data="data1">...view-code...</view>
</body>
</html>
If no View-code was provided in the html then a default OS/browser View would be used.
3. Ideally HTML would provide native support for the Data and View primitives.
Failing that then it could be provided by a script (hosted on a single website, to ensure consistency of interpretation).
4. Ideally the OS would provide support for the Data and View primitives, in the GUI and in the command line.
Failing that then these could be provided as user programs.
5. Encourage webpage developers to use the new <data> and <view> primitives by deprecating <table> ;)
1. Separation of concerns (ie, make it trivial to separate the Data and the View components from the surrounding html clutter). Currently it can be a pain to extract data from the DOM.
2. Allow the Data component to express arbitrary data shapes, including at least: - 2-D tables - n-dimensional data tables - groups of related tables and schema (for a relational database) - sparse data sets - lists - trees - graphs
A lisp-like representation of data would provide adaptability to arbitrarily shaped data.
3. Make it easy to use:- The webpage coder would write <html> <head> <data name="data1">...lisp-like-data-structure...</data> </head> <body> <view name="view1" data="data1">...view-code...</view> </body> </html>
If no View-code was provided in the html then a default OS/browser View would be used.
3. Ideally HTML would provide native support for the Data and View primitives. Failing that then it could be provided by a script (hosted on a single website, to ensure consistency of interpretation).
4. Ideally the OS would provide support for the Data and View primitives, in the GUI and in the command line. Failing that then these could be provided as user programs.
5. Encourage webpage developers to use the new <data> and <view> primitives by deprecating <table> ;)