- From: Julee Burdekin <jburdeki@adobe.com>
- Date: Thu, 1 Aug 2013 05:47:34 -0700
- To: Doug Schepers <schepers@w3.org>
- CC: Eliezer Bernart <eliezerbernart@gmail.com>, Lea Verou <lea@w3.org>, PhistucK <phistuck@gmail.com>, "public-webplatform@w3.org" <public-webplatform@w3.org>
Hi, Doug: Is there something we can do currently to tag the values (cm, em, deg, dpi) that are within a page so that we can transclude them? I know that right now we can make something a heading and point to it. Also, regarding svg/css convergence, is there something we should do now to combine the two? Thanks. Julee Sent from my iPad On Jul 31, 2013, at 9:43 PM, "Doug Schepers" <schepers@w3.org> wrote: > Hi, Eliezer– > > This all looks fine to me. I do want to make the high-level comment that > we can have organizational semantics (tagging and clustering) without > this being reflected in the URL hierarchy. So, I agree with Lea and > PhistucK that we should default to a shallower URL structure when we > can, and encode the semantics as clusters; this would let us address > PhistucK's idea that one item might be in multiple categories. > > Regarding SVG, the goal is to converge on a single version of data types > for style: those of CSS. So, let's be very careful before creating > additional structures that need to be maintained separately. > > Thanks again for working on this! > > Regards- > -Doug > > On 7/30/13 5:22 PM, Eliezer Bernart wrote: >> Hello everyone, >> >> Thanks for the feedback! >> >> So, I made some updates in the scheme: >> >> /css/values >> |_ /keyword >> |_ css-wide keywords >> |_ author-defined identifiers >> |_ /string >> |_ /url >> |_ /integer >> |_ /number >> |_ /percentage >> |_ % >> |_ /length >> |_ absolute >> |_ cm, mm, in, pt, pc, px >> |_ relative >> |_ em, ex, ch, rem >> |_ vw, vh, vmin, vmax >> |_ /angle >> |_ deg, grad, rad, turn >> |_ /frequency >> |_ Hz, kHz >> |_ /resolution >> |_ dpi, dpcm, dppx >> |_ /time >> |_ s, ms >> |_ /color >> |_ /image >> |_ /position >> >> >> Considering the fact that one unit always will be used with a same data >> type. I don't think that is a good idea to have a specific page to each >> unit, since we have no more than one or two paragraphs of content, group >> in the respective values page sounds much better. >> >> And, I do agreed with have a /css/values/color, imagining that this page >> only have content related with the "color data type", the same to image >> and position. About the hsl(), it's more relevant keep it in the >> functions section, since every color function returns a color value. >> >> Thanks again Lea, PhistucK and Julee. >> >> Eliezer >> >> @eliezerbernart >> eliezerb > > >
Received on Thursday, 1 August 2013 12:48:02 UTC