Hi Ben,

Thanks for the pointers! That clears things up a bit. Let me know when 
your RDFa tool set is mature and I'll make Exhibit generate RDFa. :-) In 
the meantime, I'd be interested in helping out on a convincing pitch / 
scenario if you think that's useful...

David

Ben Adida wrote:
> David Huynh wrote:
> [...]
>   
>> Exhibit, in particular, is in the unique position of being able to
>> address publishing needs in many domains (whereas other SW publishing
>> frameworks focus primarily on single domains like publications or
>> contact information).
>>     
> Yes!
>   
>> The exhibits we have seen [2] are a testimony to
>> this claim--they show the long tail of structured data. Perhaps it is
>> Exhibit's unique position that we can use to compare RDFa with ...
>> microformats ... :-)
>>     
> Absolutely.
>   
>> Calories can be spent to make Exhibit generate RDFa. But I'm interested
>> in knowing the story that follows:
>>
>> 1. Once every exhibit serves up RDFa, then what? How can a naive user
>> benefit from that? What tools comparable to Operator for microformats
>> [3] does RDFa have to appeal to end users? If there is no tool yet, is
>> there any plan for them?
>>     
> This is purely a time-and-resources issue: we are developing various
> tools that parse RDFa and let you do interesting things, but we're not
> at the level of Operator yet. Of course, the so-called extensible
> framework for parsing microformats is going to make a *lot* more sense
> with RDFa... but that requires work.
>
> I have an RDFa clipboard demo that is still very rough. I'll post it
> when it's a bit more ready for public consumption.
>   
>> 2. Even when there are tools for collecting RDFa and doing something
>> with it, can those tools demonstrate, concretely through realistic
>> sample scenarios, RDFa's superiority over microformats?
>>     
> I think you'll see far more variety of metadata in RDFa, though for the
> end-user, the difference at first is going to be hard to tell. The main
> issue is, as you've pointed out, the long tail of metadata: can you
> express any metadata you want, letting the "good metadata" rise to the
> top? The web can be a lot more than a distributed calendar and address
> book. The benefit of RDFa is not as clear *today* to the end user as it
> will be tomorrow. That's what makes it hard to pitch
>> On behalf of naive users, I'm very fuzzy on those two issues, so any
>> pointer would be great! :-)
>>     
> I hope this helped a bit, and I'm happy to continue the conversation.
>
> -Ben
>   

_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general

Reply via email to