- From: Al Gilman <asgilman@access.digex.net>
- Date: Thu, 5 Nov 1998 11:29:09 -0500 (EST)
- To: charlesn@srl.rmit.EDU.AU (Charles McCathieNevile)
- Cc: w3c-wai-ua@w3.org
to follow up on what Charles McCathieNevile said: > When the Guidelines define the term property (with values and > defaults) could it be made explicit that these are Style > properties? This may seem redundant, but they are such useful > general terms that we may want to reuse them, and it would be > annoying to tie them too tightly to styles. Yes, we should not simply assume that the reader has already defaulted to the CSS meaning for "property." On the other hand, it is easier to agree on what properties are as the user senses and perceives the user interface than to agree what properties are style and what are not. The writing in the UA Guidelines document should recognize that a partner document, CSS, uses "property" in a restricted sense. The document we are writing has to deal with the fact that there are two definitions for "property" that are possible the reader will apply when reading our document. We should write in a way which will make clear whether the general English or strict CSS sense of the term is meant wherever the spelling "property" appears. Al
Received on Thursday, 5 November 1998 11:28:55 UTC