gives possibility to duplicate html-element
(with elements, enclosed into it).
Attribute repeat can be added to any element
accompanying to it).
because mechanism of XForms is too sophisticated, burdened by two artificial manners:
'binding' and 'constraining values'.
Both these manners over-sophisticate and should be used optional.
Besides that, restriction of values is already developed in WebForms2
(attribute pattern and new values of attribute type
of tag input),
and there is no necessity to dublicate these possibilities.
WebForms in existing state allows only to duplicate html-element,
but not to fill duplicated copies by
entered earlier through this document into some database.
I offer to add this possibility and to enter attributes
(specifies identifier of element data with data) and
(specifies name of attribute, containing
rights of access to record,
e.g, value read of attribute means,
that fields of record are inaccessible to edit,
and it's impossible to delete record itself by
Accordingly value of attribute repeat-start
should be interpreted as quantity of empty (not filled) html-elements,
existing besides those, which are filled by attribute repeat-data.
Any user, who enter data, needs right to update, because he can make mistake
during inserting values. Anyone, who update fields, can write senseless values
or assign "null" into them - both that, and another is equivalent to deleting of
record. Right to update without right to read is looks very strange. Therefore
right to update is senseless without rights to delete and to read and should be
complemented by them - we shall name such whole right as right to operate
(operate = update + delete + read).
For comportability with database of server, WebForms2 should send the same constructions
(<orderproduct= quantity= >),
which browser was receive
(practice of indexes in xml-constructions primaraly perverted, irrelevance).