W3C home > Mailing lists > Public > www-archive@w3.org > August 2008

RE: [whatwg] Creative Commons Rights Expression Language

From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
Date: Fri, 22 Aug 2008 22:30:44 +0200
To: "'Ben Adida'" <ben@adida.net>
Cc: "'Julian Reschke'" <julian.reschke@gmx.de>, "'Ian Hickson'" <ian@hixie.ch>, "'Bonner, Matt'" <matt.bonner@hp.com>, "'Dan Brickley'" <danbri@danbri.org>, "'Tab Atkins Jr.'" <jackalmage@gmail.com>, "'Henri Sivonen'" <hsivonen@iki.fi>, <www-archive@w3.org>
Message-ID: <B40368FF55264788BB59091565FED825@POCZTOWIEC>

Why do you call inline metadata standalone?
I can see two ways to bind the metadata to the markup:
1. For elements with nonempty content, you can embed this script into the
2.The IMG elements are not subject to CC licenses because they do not
constitute main content but they serve as replacements for various user
interface elements.  However, if you insist, you could have <IMG
license="your XML">.  That would make a viable solution.
It seems your main problem is that you cannot put the licenses into
proprietary formats and you want to put the burden on HTML, seeking to put
the data as close to the reference to the describing document as possible
and hoping that that will make the license "relevant".  I do not like this
catch-and-patch attitude at all.  This is far from being a systematic
solution.  It is crucial for the relevance of metadata that the license tag
gets attached firmly onto the documents described.  The META tag can be used
for HTML; other data formats should provide their own ways to do that.

-----Original Message-----
From: Ben Adida [mailto:ben@adida.net] 
Sent: Friday, August 22, 2008 10:03 PM
To: Kristof Zelechovski
Cc: 'Julian Reschke'; 'Ian Hickson'; 'Bonner, Matt'; 'Dan Brickley'; 'Tab
Atkins Jr.'; 'Henri Sivonen'; www-archive@w3.org
Subject: Re: [whatwg] Creative Commons Rights Expression Language

Kristof Zelechovski wrote:
> The script can be specified in the src attribute of the SCRIPT element or
> embedded inline in some cases (e.g. when the inline content does not
> the text "</script").  The content of the SCRIPT element would contain the
> metadata directly as XML text.

See my answer to Ian on DRY. We don't want standalone metadata. We want
to mark up the content the user already see. That's crucial for
maintaining the relevance of the metadata.

Received on Friday, 22 August 2008 20:34:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:33:32 UTC