W3C home > Mailing lists > Public > www-style@w3.org > July 2011

[css3-images] Serialization

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 13 Jul 2011 17:38:44 -0700
Message-ID: <CAAWBYDDM8p+r6GTqcekk_gWavCWGktckwZeKP_94cUsAGH2STA@mail.gmail.com>
To: www-style list <www-style@w3.org>
I've been privately talking with Sylvain about the fact that Image
Values specifies how to serialize everything defined in it, and the
fact that the general strategy employed there (in general, be verbose
and precise) conflicts with the approach Anne outlined in CSSOM (in
general, omit things when possible).  Sylvain was concerned about this
mismatch.

Additionally, he was concerned that my definitions deferred several
things to other specs (how to serialize <url>, <color>, <length>,
<bg-position>, etc.), but these weren't actually defined, which meant
that it was impossible to actually test the serializations.

As such, I'm about to mark the serialization chapter as informative
rather than normative.  While I feel that having consistency in
serialization is important, it's not more important to Image Values
than it is to any other spec.  If Image Values should be blocked until
the more basic serialization problems are resolved, then so should
*every* spec we produce.

I've listed serialization as a topic to discuss at the upcoming f2f,
so we can decide on the overall strategy, both what we should do
(terse or verbose) and where it should be defined (a central OM
module, or in each spec).

~TJ
Received on Thursday, 14 July 2011 00:39:38 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:42 GMT