Re: RDFa, FUD and ethics

Thank you all for the variety of examples and feedback. I agree that giving
some tangible benefits of RDFa is the way to go. There is in fact a module
allowing people to choose their license:
http://drupal.org/project/creativecommons though it does not come with core.
Like Mark said, relevant RDFa modules will emerge though I will rather push
for existing modules that people already use to add RDFa support
(add GoodRelations in Drupal Commerce, support RichSnippets in the SEO
module, put ogp in the Facebook module), most of these modules already
exist, some of them have already started to look at RDFa. As for the Drupal
distributions, they will also have to make that choice, though it'll be
easier as they'll have a specific use case at hand, e.g. news - the
complaint was about core itself, which could be used for any use case
really. As for warning the users during the installation, I'll see if that
addresses their concerns, though I doubt we will have time to add that
feature in core at this point.

Thanks for bouncing ideas, it really helps. We'll try to get the licensing
in RDFa to be part of Drupal 8 core (with various choices per Keith/Sergey's
comments)...

Steph.

On Mon, Aug 9, 2010 at 7:01 PM, Keith Alexander
<k.j.w.alexander@gmail.com>wrote:

> Hi,
>
> On Mon, Aug 9, 2010 at 10:10 PM, Mark Birbeck
> <mark.birbeck@webbackplane.com> wrote:
>
> >
> > Is it not possible to make one of the configuration questions a clear
> > question about whether the user would like to enable certain features?
> > I don't mean "Would you like RDFa support?", but more like "Would you
> > like to allow sites to crawl your xyz data so that they can foobar?"
> > There could be some links and explanatory text so that people knew
> > what is going on, and how they would benefit from exposing their data.
> >
>
> Since RDFa is only exposing data that is already public, and since "do
> you want RDFa?" might be an over-technical question for some people, a
> good way of making Drupal users aware of the possibility for re-using
> the data they publish could be to ask them to give it a  license (or
> waiver [1]), making the terms for that reuse explicit.
>
> A parallel could be the way Flickr gives users the ability to attach
> various licenses to their own photos, but whereas the Flickr default
> is the most restrictive option (full copyright),  it would probably be
> more appropriate for the Drupal default to be a very permissive
> option, like CC0 [2].
>
> Are there already plans for including license/waiver declarations in the
> RDFa?
>
>
> Keith
>
>
> [1] http://vocab.org/waiver/terms/
> [2] http://creativecommons.org/choose/zero/
>