W3C home > Mailing lists > Public > public-html@w3.org > November 2008

Re: budget to implement HTML6

From: Dmitry Turin <html60@narod.ru>
Date: Tue, 04 Nov 2008 20:32:33 +0300
To: public-html@w3.org
Message-Id: <6081225819953@webmail6.yandex.ru>

Changes of two related projects (SQL5 & HTML6), not reflected in documentation yet.

===60

in regard to
http://html60.euro.ru/site/html60/en/author/looker_eng.htm

http://sql50.euro.ru/site/sql50/en/author/mtd_eng.htm


  instead of
<table name="M" action="./scriptM.cgi" portion="50" visual="20" id="id1">
<table name="S" action="./scriptS.cgi" portion="40" visual="10" master="id1">
  the following construction must be implemented
<table name="M">
<table name="S">
  with CSS
table[name=M] { online:yes; portion:50; visual:20 }
table[name=S] { online:yes; portion:40; visual:10; master:M }
  communication must be implemented via SQL5 over TCP
  (look at slides #27-28 of http://sql50.euro.ru/sql5.16.4.pdf)
  without closing TCP-connection after obtaining XML-document

  as well as instead of
<table name="M" action="./scriptM.cgi" portion="50" visual="20" id="id1">
<table name="N" action="./scriptN.cgi" portion="50" visual="20" id="id2">
<table name="P" action="./scriptP.cgi" portion="50" visual="20" id="id3">
<table name="S" action="./scriptS.cgi" portion="40" visual="10" master="id1 id2 id3">
  the following construction must be implemented
<table name="M">
<table name="N">
<table name="P">
<table name="S">
  with CSS
table[name=M] { online:yes; portion:50; visual:20 }
table[name=N] { online:yes; portion:50; visual:20 }
table[name=P] { online:yes; portion:50; visual:20 }
table[name=S] { online:yes; portion:40; visual:10; master:M N P }


  instead of sament
<_ name= event= arg= >
  the following bament must be sent
<?mtd name= event= arg= /?>
  because saments are saved in database, but baments are not
  (we don't need to save temporary service information)
  
  as well as instead of
<_ name= event= arg= >
<a a1= a2= a3=>
  the following construction must be sent
<?mtd name= event= arg= >
<a a1= a2= a3=>
</?mtd>

  as well as instead of
<_ name="S" event="TableDown" arg="40">
<m m1="v15_1"  m2="v15_2"  m3="v15_3">
<n n1="v23_1"  n2="v23_2"  n3="v23_3">
<p p1="v47_1"  p2="v47_2"  p3="v47_3">
  the following construction must be sent
<?mtd name= event= arg= >
<m m1= m2= m3= >
<n n1= n2= n3= >
<p p1= p2= p3= >
</?mtd>


  instead of
<a  a1= a2= a3="tiger.jpg">
<file name="a3" filename="tiger.jpg">Y29udGVudHMgb2YgZmlsZTEudHh0</file>  
  the following construction must be implemented
<a  a1= a2= a3="tiger.jpg">
<?file attr="a3" value="tiger.jpg" xml:size= >Y29udGVudHMgb2YgZmlsZTEudHh0</file>  


  instead of
<table    name="A" action="./script.cgi"  portion="50" visual="20">
  <select name="B" action="./script2.cgi" portion="40" visual="10">a2</select>
</table>
  the following construction must be implemented
<table    name="A"/>
  with CSS
table [name=A] { online:yes; portion:50; visual:20 }
table [name=A] { §a2: B }                            /* 'portion', 'visual' are inherited */

  in addition to mentioned, statement
table [name=A] { §a2: B C }
  means, that "C" is master table for "B", "B" is master table for "§a2",
  and that browser represents content "C" before content "B" to choose sub-set of "B"
  

  in addition to mentioned in paper (HTML6), each 1-st click on column header
  (e.g. concerning to xml-attribute @a2) sends bament
<?mtd name= event=asc  arg=a2/?>
   each 2-nd click sends bament
<?mtd name= event=dsc  arg=a2/?>
   each 3-rd click sends bament
<?mtd name= event=none arg=a2/?>

  in addition to mentioned in paper (MTD),
  following bament forces to resent data, having appended ascendant sorting by field @a2
<?mtd name= event=asc  arg=a2/?>
  following bament forces to resent data, having appended descendant sorting by field @a2
<?mtd name= event=dsc  arg=a2/?>
  and following bament forces to resent data, having subtracted sorting by field @a2
<?mtd name= event=none arg=a2/?>

---

in regard to
http://html60.euro.ru/site/html60/en/author/combo_eng.htm

http://sql50.euro.ru/site/sql50/en/author/mtd_eng.htm


  instead of
<select name="C" action="./script2.cgi" portion="40">
  the following element must be implemented
<select name="C">
  with CSS
ul[name=A] { online:yes; portion:40 }
  communication must be implemented via SQL5 over TCP
  (look at slides #27-28 of http://sql50.euro.ru/sql5.16.4.pdf)
  without closing TCP-connection after obtaining XML-document


  instead of sament
<_ name= event= arg= >
  the following bament must be sent
<?mtd name= event= arg= /?>
  because saments are saved in database, but baments are not
  (we don't need to save temporary service information)

  as well as instead of
<_ name= event= arg= >
<option id= value=>word40<option>
  the following construction must be sent
<?mtd name= event= arg= >
<option id= value=>word40<option>
</?mtd>


---

in regard to
http://html60.euro.ru/site/html60/en/author/tree_eng.htm

http://sql50.euro.ru/site/sql50/en/author/mtd_eng.htm


  instead of
<ul name="A" action="./script.cgi">
  the following element must be implemented
<ul name="A">
  with CSS
ul[name=A] { online:yes }
  communication must be implemented via SQL5 over TCP
  (look at slides #27-28 of http://sql50.euro.ru/sql5.16.4.pdf)
  without closing TCP-connection after obtaining XML-document

  instead of sament
<_ name= event= arg= >
  the following bament must be sent
<?mtd name= event= arg= /?>
  because saments are saved in database, but baments are not
  (we don't need to save temporary service information)

---

in regard to
http://html60.euro.ru/site/html60/en/author/looker_eng.htm

http://html60.euro.ru/site/html60/en/author/tree_eng.htm

http://sql50.euro.ru/site/sql50/en/author/mtd_eng.htm


  in addition to mentioned in papers, tree as master element for table is possible
ul   [name=A] { online:yes }
table[name=S] { online:yes; portion:40; visual:10; master:A }
  and browser sends at user actions
<?mtd name=S event= arg= >
<li id=1>
</?mtd>
  it's supposed, that foreign key of database table "S" refers to
  primary key of database table "A"

  database table, corresponding to HTML-tree, consists of only two fields -
  of primary key (extracted as @id), and of any other field with any name
  (extracted as content of element LI)

--other HTML6 additions

  pressing browser botton "back" not only display previos XML-document, but also sends bament
<?back/?>
  (which rollback transaction in DBMS to previos 'select ...')
  
  bottons to append and remove table row must be implemented in menu of browser window
  (implementation in way of WebForms2 is optional)
  
  property 'save' means, that at pressing ^S, html/xml-document will be saved with entered values
input { save:yes }

===50

in regard to
http://sql50.euro.ru/sql5.16.4.pdf (slide #31,etc)

  in addition to mentioned in pdf-document, statement
SELECT ... COMMENTING.
  extracts additional record from table as first xml-element,
  attributes of which contain comments, specified for each field earlier by statement
COMMENT tab/@fld BY "column title";
  this first xml-element contains additional service xml-attribute '_=comment'.
  usually comments are specified for html-tables, instead of html-trees

--

in regard to
http://sql50.euro.ru/sql5.16.4.pdf (slide #18)
http://html60.euro.ru/site/html60/en/author/tabfile_eng.htm (Sending of form)
http://html60.euro.ru/site/html60/en/author/cube_eng.htm    (Sending of form)

  Obtaining single xml-element (instead of xml-tree) with primary key (PK) for DBMS table (specified in some xml-attribute) means the following:
*) if this PK is already in DBMS table, then DBMS *updates* fields of record with this PK
*) if this PK is not in table (this usually means, that record with this PK was already deleted),
  then DBMS *inserts* this xml-element under new PK (obtained from sequence for this PK), i.e. PK will be changed during insertion.

--

in regard to
http://sql50.euro.ru/sql5.16.4.pdf (slide #31-32, 39(Another output), 40)
http://html60.euro.ru/site/html60/en/author/forxml_eng.htm

http://html60.euro.ru/site/html60/en/author/quest_eng.htm#webforms_data (<data id="records">...</data>)

  Each 'select ...' extracts data into LAN or WAN.
  (instead of 'insert ... select ...' and 'select ... into ...', coping data into internal DBMS table).
  Each 'select ... union ... select ...' interpreted as single extraction of xml into LAN or WAN.
  Each extraction of data into LAN or WAN is automatically:
*) anticipated by content of field 'beginning' of system table 'SysXmlFormatting'
*) ended by content of field 'end' of system table 'SysXmlFormatting' and
*) by bament <?newdocument/?> (to inform client, e.g. browser, about end of document)
P.S.
Other field of system table 'SysXmlFormatting' is URL
(which specifies browser URL; 'null' means all URL and is applied,
only if 'SysXmlFormatting' does not contain record with exact URL).

--

in regard to
http://sql50.euro.ru/sql5.16.4.pdf (slide #173)

  Authentification (obtaining username and password, slide #173) must be implemented by baments
  (look at slides #26-27) and is described nowhere.
 
--other SQL5 additions

  in addition to mentioned in pdf-document, each 'select ...' (extracting data into LAN/WAN) is savepoint.
  DBMS rollbacks to this savepoint, having obtained bament
<?back/?>

  in addition to mentioned in pdf-document, permissions for field are controlled
GRANT/REVOKE SELECT/INSERT/UPDATE ON tab/@fld FOR user1;

  in addition to mentioned in pdf-document, if table "b" below is created
--------------------------
| b1 | b2 |      b3      |
|------------------------|
|         | a1 | a2 | a3 |
|------------------------|
|                        |
|                        |
--------------------------
  then expression
IMPLY b/@b3 as b/@b3/@a2;
  influence so, that any 'SELECT @b3 FROM b' will extract only one elementary field (@a2) 
  instead of all branch elementary fields (@a1, @a2, @a3),
  i.e. mentioned statement will be equivalent to 'SELECT @b3/@a2 FROM b'.
  it's for multi-language applications (@a1, @a2, @a3 contain notes in different languages)
  
  DBMS creates separete CSS-file "username.css" for each user "username" in local (for DBMS) directory.
  All accessable database fields (for user "username") are listed in this file as ¶fieldname
  [instead of §fieldname, because DBMS does not know,
  what fields are service (like @colspan, @rowspan) or
  are values of properties (like in http://html60.euro.ru/site/html60/en/author/chart_eng.htm),
  and what fields contain data for visualization -  
  so mark ¶ acts like comment for this xml-attribute),
  except fields, which are primary keys in database, and which are always specified (and never ignored) as invisible.
  Fields, calculated upon other fields and don't saved really, specified as calculated by browser upon other fields.
  CSS-files are available for editing for DBMS administrator.



Dmitry (SQL50, HTML60)
Received on Tuesday, 4 November 2008 17:33:21 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:59 UTC