W3C home > Mailing lists > Public > www-style@w3.org > January 2008

Re[24]: css with attribues [software]

From: Dmitry Turin <sql4-en@narod.ru>
Date: Mon, 21 Jan 2008 00:30:48 +0300
Message-ID: <2126359090.20080121003048@narod.ru>
To: www-style@w3.org


>> If you will delete signature from header/footnote of each page,
>> except last page, then you will save information !!
>> but author will claim, because reason of marketing
>> (he want, what advertisement would climb into eyes).
DD> So some content is duplicated on multiple pages. That doesn't make it
DD> presentational.

This is root of our disagreement.

>>>>>> Multiple repeated attributes ON CONCRETE SITE are 'look' ONLY,
>>>>>> independently of how W3's officials specify them.
DD> I rather system the OED would disagree with you.


>>>>>> DD> presentation in CSS and semantics in HTML works just
>>>>>> DD> fine, with little duplication of effort
>>>>>> Please, 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> there is very
>> DD> little in the way of attributes which are duplicated from page to
>> DD> page which are not either (a) presentational or (b) accompanied by
>> DD> elements and content.
DD> don't you accept that your proposal would have
DD> negligible benefit if implemented?



>>>>>> Let attributes in css will be media-specific.
>> Whole appropriateness:
>> CSS wholely covers (satisfies) needs, appearing at merging attributes
>> and properties into single space. And '@media all {' in
>>          @media all {
>>            tag { attr: val }
>>          }
>> means, that possibilities of CSS is wider, then needs of merging.
DD> it also does a number of
DD> things which makes it incompatible with it.

For example ? There is full compartability:
current CSS will particular part of CSAS !?

>>>>>> DD> "I am writing CSS, therefore I am describing how the
>>>>>> DD> semantics should be represented to the user".
>>>>>> Yes, but with redundant 'style='.
>>>> DD> Authors do not have to use style attributes
>>>> DD> (and generally should not use them).
>>>> I.e. create unique class for unique place of site ?
>> DD> There are various ways that selectors can be crafted to match
>> DD> elements. Classes might come into it.
>> You can write properties either in tag,
>> or in definition of class, isnt't it ?
>> What is the third way, about which you are speaking ?
DD> You seem to be confusing a class (or a class selector) with a rule-
DD> set. You might want to reread those parts of the HTML and CSS  
DD> specifications.

I will not guessing about your objection - objection must be concrete.
I'm listening you.

>>>>>> DD> CSS expert working on the look
>>>>>> DD> while HTML experts work on the content
>>>>>> My signature at the end of each letter is content or look ??!!
>>>> DD> It is content.
>>>> It is look. Even existance of XSL says about my rightness !!
>> DD> No, it is content. Possibly not primary content ...
>> How many types of content can you separate ??
>>   You can accept convention, that any look is content -
DD> No. Content (written in HTML) has an appearance (written in CSS).

You use terms in back direction:
all, written in HTML, is content; all, written in CSS, is look.
But content itself and look itself are category of thinking -
items must be bring to content or look depending of mental
characteristics (instead of depending of written language).

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 Monday, 21 January 2008 06:05:13 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:33 UTC