- From: Stephane Corlosquet <scorlosquet@gmail.com>
- Date: Thu, 11 Mar 2010 16:42:27 -0500
- To: Dan Brickley <danbri@danbri.org>
- Cc: public-rdfa@w3.org
- Message-ID: <1452bf811003111342q2668e878ka40dd2c6e091245b@mail.gmail.com>
Hi Dan, Have you looked at http://www.loomp.org/? One side effect you have to deal with if you want to have parsable RDFa in your blog post is that you cannot annotate the whole post with say property="content:encoded", which is popular practice in RSS. The only work around is to specify datatype="" and end up with a plain literal, losing all the formatting etc. See related thread on the topic [1]. Steph. [1] http://lists.w3.org/Archives/Public/public-rdfa/2010Feb/0004.html On Sun, Dec 27, 2009 at 9:53 AM, Dan Brickley <danbri@danbri.org> wrote: > Hi folks, > > I'm investigating possibilities for Web-based HTML editing UIs that > support RDFa. > > http://danbri.org/words/2009/12/23/507 has some notes and examples > around Wordpress, which uses a rich text editing widget called > TinyMCE. > > Since this already has a simulated 'pop up' for editing the properties > of a link to external page, it seems a good basis for extension with > typed links etc. > > One natural question that then crops up, is whether to build something > initially just for document-valued properties (eg. > foaf:schoolHomepage), or also to try supporting links to non-documents > which might be identified only indirectly. See blog post for details > of that. > > If anyone here has time to explore this or thoughts on what might be > useful first steps, do please let me know (ideally in public here). > > cheers, > > Dan > >
Received on Thursday, 11 March 2010 21:43:48 UTC