Ben Adida wrote: > Stefano Mazzocchi wrote: >> The appeal in separating the data from the page comes from the fact that >> it's easier to imagine somebody (say, a college professor) embedding >> exhibit into their web pages and then use some other web service (say >> google spreadsheet or equivalent) to keep their data up to speed.... or >> even just publish their bibtex file and let exhibit+babel do the rest. > > With a simple enough HTML+RDFa template, isn't it effectively all data?
Sure, but we are talking about you own home page... wouldn't you want it to be all pretty and at the very least in tune with the rest of your site? like yours, hint hint :-) >> The step of having to generate an HTML+RDF/A table out of that data >> *and* have to embed it into their HTML page *and* post it/ftp it/webdav >> upload it over to their homepage is a *much* less attractive scenario, >> so unattractive, in fact, that I doubt such data would be kept in synch >> and even less that the exhibit data would become *the* place where such >> person stores his/her data primarily. > > You're right, but I don't think the Bibtex use case is very good right > now, either, since you still have to manually convert to JSON ehm, not really. Exhibit is now coupled with Babel, a RESTful web RDFfization web service that we run so that it can do conversion on the fly. Sure it wouldn't scale if the entire world did that, but for now it's pretty good (and it works with all sort of other stuff that we don't have, or don't want to write, a js parser for) > and then you're not Google-searchable. > >> I have nothing against embedding RDF/A or eRDF in HTML... I just wish >> there was a way to keep the concern of maintaining the presentation >> layer separate from the concern of maintaining the data model without >> sacrificing the google availability for the two combined. > > Well, I tend to think of HTML+RDFa as being effectively data at this > point. I know what you're saying, and I agree the process needs to be > improved, though. I agree with DavidK that server side include seems to be the simplest possible choice that achieves both needs: complete presentation / data separation and google findability of the nice page. >> If only Google used Crowbar :-( > > and indexed application/xhtml+xml, and.... :) Maybe it's time to write our own search engine :-) -- Stefano Mazzocchi Digital Libraries Research Group Research Scientist Massachusetts Institute of Technology E25-131, 77 Massachusetts Ave skype: stefanomazzocchi Cambridge, MA 02139-4307, USA email: stefanom at mit . edu ------------------------------------------------------------------- _______________________________________________ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
