Re[19]: css with attribues [hardware]

David,

DD> It would require major rewrites for many user agents.
>> Following your logic,
>> community must not enter new attributes into tags,
>> because it would require major rewrites for many user agents.
DD> Adding new attributes to the markup language wouldn't
DD> require some user agents to completely change the way they process
DD> the page.
>> "Append attributes from css-file to tree" is also "adding"
>> (but not "change" - as you are writing).
>> Also, as i already said, authors don't use standards,
>> while browsers don't support them.
DD> if a user agent doesn't support CSS
DD> it doesn't matter (since information is not lost).

  When standard appends new attribute into tag,
UA can ignore it without fail of work.
  When standard appends new attribute into css,
also UA can ignore it without fail of work.
  Old (known) attributes in tags are saved in both cases.
Old (known) attributes can be withdrawn from tags also in both cases
(deleted in first case and moved in last case).

  You are expecting, that if my proposal will become standard,
authors of sites will make some attributes invisible for current UA
by moving them into css, will harm to themselves ?
They can make this even now, today !!
And really they will move, when this motion will not withdrawal.
I.e. when new UA will appear.

---

>> User gets benefit (unnecessary to keep separation in brain),
DD> As mentioned, this is a disadvantage.

Excuse me, explain, how "unnecessary to keep separation in brain"
is "disadvantage".

>> 1) CAS will reduce manual job
>> ("multiply to quantity of population, than to quantity of
>> pages on sites - and you will get real number of duplications,
>> which are quite not little")
DD> As mentioned, there doesn't appear to be any significant saving on
DD> the amount of effort authors have to go to.

Translate me, please, your complex english :)

DD> (b) What about "realtime" UAs?
>> It is UA, which give results to end of time,
>> which user can (or want) wait.
>> E.g. if UA is browers, then result is rendering,
>> time is equal 1 second;
>> if UA is electronic storage, then result is filling database,
>> time depends of destination of this storage
>> (in any case, it is much more, than 1 second).
DD> The result is irrelevant to my point. The point is that user agents
DD> (such as Lynx) will no longer be able to simply take the HTML
DD> document and parse it, outputting the result as they go.

What is common between definition of my term and
inability to parse html-file without css-file ?

---

>> 2) CAS allow to write groups, got as result of classification,
>> and so promote structurezed thinking.
DD> I have no idea what you mean by this.

I wanted to say, that author itself will distribute characteristics
(attributes-properties) into .htm and .css , dependently of
particularity of his (unique) site.



Dmitry Turin
SQL5      (5.9.1)  http://sql50.euro.ru
HTML6     (6.5.1)  http://html60.euro.ru
Unicode7  (7.2.1)  http://unicode70.euro.ru
Computer2 (2.0.2)  http://computer20.euro.ru

Received on Thursday, 17 January 2008 13:17:21 UTC