On Tue, 26 Jun 2007 05:23:43 +0100, David Karger <[EMAIL PROTECTED]> wrote:
> I don't see that we need to think about _a_ canonical format at all. > There are many different dimensions of quality of various input formats, > and none will do well on all of them. As long as exhibit can input and > output all of them, The serialization of the data can change as the user > and usage of the data changes. +1 I think there are potential situations where a canonical format is useful (perhaps Ben could elucidate some of these?), but for Exhibit, I don't think you need or want a canonical non-js format - the easier it is to input or output whatever you have and whatever you need, the better. Mike, is there a reason for a canonical format in this context that I'm missing? nb: there's an eRDF importer as well as an RDFa one. I'm not sure if David's moved it to svn yet, but it's in the same state of usefulness as the RDFa one; that is to say, importing data from the same page seems to work reliably enough, but there's still a cross-browser niggle with safari 1-2.0 when it comes to importing eRDF/RDFa from other local pages (importing cross-domain isn't possible clientside afaik, though it can be done by piping GRDDLable eRDF/RDFa through something like triplr.org and feeding that to the exhibit). Yours Keith _______________________________________________ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
