W3C home > Mailing lists > Public > public-rdfa@w3.org > November 2008

Re: A roadmap for RDFa in Drupal core

From: Stephane Corlosquet <stephane.corlosquet@deri.org>
Date: Wed, 12 Nov 2008 21:11:45 +0000
Message-ID: <491B4691.8030406@deri.org>
To: Manu Sporny <msporny@digitalbazaar.com>
CC: public-rdfa@w3.org

Hi Manu,

Thanks for your feedback.
> A couple of comments/questions:
>
> - You should give admins the option to enable/disable RDFa output for
>   SIOC/FOAF/etc. Disabling RDFa output, however, shouldn't change the
>   DOCTYPE in case one of the content authors wants to explicitly embed
>   RDFa via the content editor.
>   
Keeping the same DOCTYPE makes things easier for the reasons you
mention, and that's how it's done so far in the current patch. Disabling
RDFa output will be done on a per attribute basis to allow greater
control on what's annotated. The challenge here is to keep the UI simple
for the user/admin.
> - Will Drupal now be the largest implementation of GRDDL?
>   
That would be great. At least that's what we are all hoping for!
> - I think the biggest problem that all CMSes are going to have is
>   WYSIWYG editing of RDFa. Are there plans for this yet? I haven't
>   really seen this done in an intuitive way - just wondering if you guys
>   had put some thought into it.
>   
someone mentioned this idea in the Drupal semantic web group:
http://groups.drupal.org/node/16553
but that's the only thing I'm aware of so far.
> - "RDFa in content types and fields" - this is a fantastic way to
>   automatically mark up content. You might consider being able to
>   enable/disable this on a per-entry basis - people might not want
>   to make certain entries machine-readable/crawl-able.
>   
It will be for sure switchable on a content type basis.
"enable/disable this on a per-entry basis" - do you mean entry as on a
page basis? It's easier with an example: say I have a content type
"artist" with a field "name". The field "name" is RDFa enabled. Did you
mean to be able to disable it on a per-artist basis?


Stéphane.


Manu Sporny wrote:
> Stephane Corlosquet wrote:
>   
>> Following up on the recent excitements of the Drupal community and Dries
>> in particular, I've posted what could be a roadmap for implementing RDFa
>> in the next version of Drupal core. I am very keen on getting feedback
>> from the RDFa community in order to make sure I haven't overlooked anything.
>>
>> http://groups.drupal.org/node/16597
>>     
>
> Looks great, Stephane! I didn't think that you guys would move so
> quickly... it's great to see some RDFa traction in Drupal. I think your
> approach is solid.
>
>   
>> Feel free to comment with ideas and opinions. There are also some open
>> questions which go beyond the scope of Drupal itself. 
>>     
>
> A couple of comments/questions:
>
> - You should give admins the option to enable/disable RDFa output for
>   SIOC/FOAF/etc. Disabling RDFa output, however, shouldn't change the
>   DOCTYPE in case one of the content authors wants to explicitly embed
>   RDFa via the content editor.
> - Will Drupal now be the largest implementation of GRDDL?
> - I think the biggest problem that all CMSes are going to have is
>   WYSIWYG editing of RDFa. Are there plans for this yet? I haven't
>   really seen this done in an intuitive way - just wondering if you guys
>   had put some thought into it.
> - "RDFa in content types and fields" - this is a fantastic way to
>   automatically mark up content. You might consider being able to
>   enable/disable this on a per-entry basis - people might not want
>   to make certain entries machine-readable/crawl-able.
>
> -- manu
>
>   
Received on Wednesday, 12 November 2008 21:13:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:15:01 UTC