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? > 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, 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. > If only Google used Crowbar :-( and indexed application/xhtml+xml, and.... :) -Ben _______________________________________________ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
