W3C home > Mailing lists > Public > public-webplatform@w3.org > July 2013

Re: CSS values and units

From: Julee Burdekin <jburdeki@adobe.com>
Date: Mon, 29 Jul 2013 13:19:55 -0700
To: Eliezer Bernart <eliezerbernart@gmail.com>, "public-webplatform@w3.org" <public-webplatform@w3.org>
Message-ID: <CE1C1C52.89FFC%jburdeki@adobe.com>
Thanks much, Eliezer! Folks: this is one of the items we want to have done
for the CSS properties project. So your attention to this is much
appreciated.

Regards.

Julee
----------------------------
julee@adobe.com
@adobejulee





-----Original Message-----
From: Eliezer Bernart <eliezerbernart@gmail.com>
Date: Friday, July 26, 2013 3:25 PM
To: WebPlatform Public List <public-webplatform@w3.org>
Subject: CSS values and units
Resent-From: WebPlatform Public List <public-webplatform@w3.org>
Resent-Date: Sunday, July 28, 2013 6:18 AM

>Hello everyone,
>
>Some time ago Lea made an observation about duplicate pages, mostly of
>them about CSS data types, in that occasion Doug and I updated the
>css/units and css/data_types pages making a little bit more clear and
>organized. [0]
>
>This week on IRC channel, Julee and I talked again about this subject,
>and how we all are seeing on the mailing list a lot of questions about
>data types and units organization. Starting from W3C documentation
>that already exists, we elaborated a structure to discuss the best
>model inside Webplatform docs for that information.
>
>Right now the pages that point to these contents are (some of them
>created by me and Doug in the last update):
>
>+ Data Types = http://docs.webplatform.org/wiki/css/data_types
>       - Text values = /css/data_types/text
>       - Color units = /css/data_types/color
>       - Length units = /css/data_types/length
>       - Angle units = /css/data_types/angle
>       - Numeric units = /css/data_types/numeric
>       - Resolution units = /css/data_types/resolution
>       - Time units = /css/data_types/time
>       - Frequency units = /css/data_types/frequency
>
>+ Units = http://docs.webplatform.org/wiki/css/units
>
>
>Based on CSS Values and Units[1] and Syntax and basic data types[2],
>the structure proposed is:
>
>/css/values
>        |_ /textual
>                    |_ /keywords
>                                |_ css-wide keywords
>                                |_ author-defined identifiers
>                    |_ /string
>                    |_ /url
>        |_ /numeric
>                    |_ /integer
>                    |_ /number
>                    |_ /percentage
>                                |_ %
>        |_ /length
>                    |_ absolute
>                                |_ cm, mm, in, pt, pc, px
>                    |_ relative
>                                |_ em, ex, ch, rem
>                                |_ vw, vh, vmin, vmax
>        |_ /others
>                    |_ /angle
>                                |_ deg, grad, rad, turn
>                    |_ /frequency
>                                |_ Hz, kHz
>                    |_ /resolution
>                                |_ dpi, dpcm, dppx
>                    |_ /time
>                                |_ s, ms
>        |_ /modules
>                    |_ color [3]
>                                |_ colors_by_hue
>                                |_ colors_by_name
>                                |_ colors_by_saturation
>                                |_ user-defined_system_colors
>                    |_ image [4]
>                    |_ position [5]
>        |_ /notations
>                    |_ attr
>                    |_ calc
>                    |_ counter
>                    |_ toggle
>
>(New pages are represented by '/' before the name)
>
>In the modules node there are the data types that are defined in other
>specifications, so, should we can just put those at the top level
>after |_/css (i. e.: color, position) or do you think there's
>information that would live on a modules page, and then these data
>types live under modules?
>
>It's important remember that the values under notation's node
>represent complex data types, in module's node the ones which have
>information defined in other pages, and the others nodes are composed
>by the primitive values.
>
>About the units page [6], I think that is important keep in a page all
>the possible values, with a link to the data type that each one
>represents. These unit pages would live under their related data type.
>I believe that the actual structure is perfect, what do you think?
>
>Then there are data types on SVG. There is some differences to data
>types on CSS, so probably these others informations should be at
>/svg/[data_type], following some structure in the same way as CSS,
>just so we do not mix up the things.
>
>About the pages' content, themselves, there are some things missing:
>how-to examples, some better descriptions, some units. But let's work
>on the structure first.
>
>Thanks for the attention. All feedback and opinions will be welcome.
>This is a really important point that needed to be defined.
>
>[0] = 
>http://lists.w3.org/Archives/Public/public-webplatform/2013Jun/0055.html
>[1] = http://www.w3.org/TR/css3-values/
>[2] = http://www.w3.org/TR/CSS2/syndata.html#values
>[3] = http://docs.webplatform.org/wiki/css/color
>[4] = http://www.w3.org/TR/css3-images/
>[5] = http://www.w3.org/TR/css3-background/#the-background-position
>[6] = http://docs.webplatform.org/wiki/css/units
>
>Eliezer
>
>@eliezerbernart
>eliezerb
>
>
Received on Monday, 29 July 2013 20:22:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:52 UTC