Re[3]: css with attribues [general]

Brad,

>>> Unfortunately, there is an undercurrent of opinion on this list
>>> (or perhaps even a theme of the CSSWG) that authors must be  
>>> protected from themselves, and that the Web must be protected from
>>> authors. It rears
>> That shouldn't be surprising as I think that one of the main
>> reasons for introducing CSS in the first place was to remove  
>> presentational attributes from HTML.
BK> That's true. At the time, there was no other way to have distinctive,
BK> well-designed pages

Oy boy!
I expected, that main reasons to segregate
(not to develop in future) were
 to reduce manual job,
 to follow structurized thinking,
 to ecomonize traffic at least,
but to domesticate (tame) users - i can't expect this !!

BK> I don't necessarily agree that CSS should include all the attributes
BK> of HTML

Actually, nature of presentational parameters (now properties) and
repeated attributes are different. And if to think consecutively,
it's necessary to segregate them into different place of consciousness
and into different capacity at keeping.

But current practice is so, that it's _possible_ (not consecutive)
to store them in one capacity. In exchange for one capacity,
we get rid of necessity to separate manually into capacities.

---

BK> if we want to include some ideas from HTML
BK> attributes that we haven't already, then that should be done  
BK> formally, on a case-by-case basis

'formally' and 'case-by-case' (individually) are opposite.

We can group all repeated attributes formally,
but we must individually move into other group.

BK> CAS ... is well
BK> beyond the scope of this working group, and should remain so.

Inter-discipline science against-the-will must be entered
into known discipline to get financing :)



Dmitry Turin
SQL5      (5.10.0)  http://sql50.euro.ru
HTML6     (6. 5.2)  http://html60.euro.ru
Unicode7  (7. 2.1)  http://unicode70.euro.ru
Computer2 (2. 0.2)  http://computer20.euro.ru

Received on Thursday, 24 January 2008 10:14:01 UTC