W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2008

[whatwg] Creative Commons Rights Expression Language

From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
Date: Thu, 21 Aug 2008 21:45:14 +0200
Message-ID: <D2E1D8ADDB4F498B88D92C83BD353E24@POCZTOWIEC>
I was trying to explain the rejection of namespaces in general because it is
a general decision.  It is not enough to make sure this particular use case
does not cause problems.
AFAIK, you can make a legacy browser that supports custom elements and
scripting to display a progress bar.  This probably means you partially
right: Lynx, NCSA Mosaic and MacWeb cannot render a progress bar element.

-----Original Message-----
From: Ben Adida [mailto:ben@adida.net] 
Sent: Thursday, August 21, 2008 9:36 PM
To: Kristof Zelechovski
Cc: 'Dan Brickley'; 'Tab Atkins Jr.'; 'Bonner, Matt'; 'WHAT-WG'; 'Ian
Hickson'; hsivonen at iki.fi
Subject: Re: [whatwg] Creative Commons Rights Expression Language

Kristof Zelechovski wrote:
> If I understand it correctly, we do not have a problem with the colon as a
> namespace separator.  Our problem is that "a:x" sometimes means the same
> "b:x" and there is no reasonable way to make legacy browsers support this.

But... legacy browsers have no way to display a Progress Bar either, right?

RDFa does *not* affect how something is rendered. It just tells you what
portions of the page mean what exactly (this is a license, this is a
tag, etc...) So we're okay if legacy browsers don't understand it, they
can simply ignore it. In fact, even new browsers can ignore RDFa,
leaving the job to an extension. But of course, everyone is much better
off if RDFa can be validated in HTML/XHTML.

Received on Thursday, 21 August 2008 12:45:14 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:04 UTC