W3C home > Mailing lists > Public > www-xsl-fo@w3.org > December 2010

Re: rec 1.1 7.7.4

From: Dave Pawson <dave.pawson@gmail.com>
Date: Fri, 10 Dec 2010 11:38:37 +0000
Message-ID: <AANLkTikPXxm0DbnvptQZFcsKYy3SHwM82KbmFC+Q3UQH@mail.gmail.com>
To: Tony Graham <Tony.Graham@menteithconsulting.com>
Cc: www-xsl-fo@w3.org
On 10 December 2010 11:06, Tony Graham
<Tony.Graham@menteithconsulting.com> wrote:
> On Fri, Dec 10 2010 09:16:29 +0000, dave.pawson@gmail.com wrote:

>> What does || mean? Are they alternataives? Why are two bars necessary.


>> Replacing them with single bar would make it consistent with the
>> remainder of the models?
>
> There are many property value definitions that use "||" when
> alternatives aren't mutually exclusive.


> Your reworking doesn't sufficiently indicate that you can have both
> 'underline' and 'overline' (and others).  If "underline | no-underline"
> is mutually exclusive, then you've made it look like everything is
> mutually exclusive.

Understood. So to understand the semantics I need to
understand those used in CSS 2?
Not a sensible choice IMHO.




>
>> Is it really necessary to copy CSS fancies?
>
> It was: "XSL builds on the prior work on Cascading Style Sheets".

One aspect of which is this ?


>
> One person's fancies is another person's bread and butter.  If you come
> to XSL with familiarity with the CSS2 spec, then "||" is familiar to
> you, just as when you are familiar with XML content models, then
> "#PCDATA" is familiar to you.  XSL could have invented new syntaxes for
> every little thing, but I contend that it's not the purpose of a spec to
> redefine every other spec on which it depends,

I'm sure there are better models to choose from Tony.

I do hope 2.0 makes a better one.

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
Received on Friday, 10 December 2010 11:39:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 10 December 2010 11:39:05 GMT