In an ideal world (ie, one with an infinite number of coders :), babel would be "inside" exhibit. Exhibit would natively read all the formats that babel currently translates. There is no technical barrier to this, and it would enhance the tool by letting authors publish in whatever structured data representation they wanted and edit it in real time without having to got through an interaction with a translation service.
In this non-ideal world, the reason for babel is that a number of fast-enough parsing tools, such as the one babel uses to translate bibtex to rdf, exist in java that do not exist in javascript. Since David Huynh had finite time, he used them. Just as exhibit has a library of different views, it would be natural for it to have a library of parsers for different structured data formats. So I could say <script src="http://static.simile.mit.edu/exhibit/api/exhibit-api.js?views=timeline&parser=bibtex"; type="text/javascript"></script> and then <link href="mybib.js" type="application/bibtex" rel="exhibit/data" /> All that is standing in our way is the lack of an army of programmers :) derek | idea company wrote: > David, > That might work indeed. However, I was thinking something on par with > say how Timeline was using an XML file, using something similar instead > of a JSON file. It would also be easier to create, edit and manage it > in a live environment, making it possible for multiple exhibit authors. > A simple xml editor could be created to edit and update a file in use. > That way, users wouldn't have work around a spreadsheet and either > export it with Babel or get access to the google spreadsheet and do all > the publish/republish. Just a thought, might be out of the scope of the > project. > Cheers, > +dk > > Derek Kinsman > The Idea Company > > New Media Designer > > http://www.ideacompany.ca/ > http://boring.ambitiouslemon.com/ > 1.416.371.5652 > > > > David Huynh wrote: > >> Oh that might work! So, maybe something like this? >> >> <head> >> <link rel="exhibit/data" type="application/json" >> href="my-data.json" /> >> >> <link rel="exhibit/google-spreadsheets-data" type="application/jsonp" >> >> href="http://spreadsheets.google.com/feeds/list/o08841867754116283182.6102151849127695926/od6/public/basic?alt=json-in-javscript"; >> /> >> >> <!-- Just for you, Google! --> >> <link rel="alternate" type="application/rss+xml" title="RSS 2.0" >> >> href="http://www.foo.com/convert-exhibit-json-to-rss?url=http://people.csail.mit.edu/dfhuynh/my-data.json"; >> /> >> >> <link rel="alternate" type="application/rss+xml" title="RSS 2.0" >> >> href="http://spreadsheets.google.com/feeds/list/o08841867754116283182.6102151849127695926/od6/public/basic"; >> /> >> </head> >> >> >> How confident are we that this will work? >> >> David >> >> _______________________________________________ >> General mailing list >> [email protected] >> http://simile.mit.edu/mailman/listinfo/general >> >> >> > _______________________________________________ > General mailing list > [email protected] > http://simile.mit.edu/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
