Johan Sundström wrote: > On 2/11/07, David Karger <[EMAIL PROTECTED]> wrote: > > >> if these are all about the same data, it isn't clear to me that there is >> value to having all the alternate links---it isn't like the use of alt >> in html which suggests different ways to display info by differently >> abled browsers; clearly anything that can handle the data in one syntax >> can handle it in any syntax. >> > > Um, no? It's more like languages. I have excellent native support for > Swedish, great support for English, rudimentary support for French and > even less Japanese. I don't speak a word of Lebanese, but some people > do. Web citizens like browsers and search engine spiders are much the > same, but with data formats. Exhibit might handle all these syntaxes, > but were it only for the benefit of Exhibit we put them there there > wouldn't be call for anything beyond json in the first place. > Of course, the whole "alt" syntax suggests you are thinking of web browsers, which run javascript, which can therefore incorporate the exhibit parsers, so handle all the syntaxes :) > >> So, we want to separate being able to name a particular blob of data (eg a >> particular table or file) from being able to specify which names appear >> inside a given xibit. >> > > Now I might be lost, though. The only problem I raised and wanted to > solve here is to tie all separate data sources listed in to a specific > exhibit (or possibly multiple exhibits; they might, for instance, want > to share some schema files and data subsets). Names were borrowed from > CSS as an example of a way to achieve that. > > I think what I say is that I care for the latter issue. I think my > mentioning the HTML title attribute might have invited a whole can of > worms in the opportunities for miscommunications department; let me > withdraw that wording again. :-) > I was attempting to point out that ultimately we may want to map many data blobs into many exhibits---so there are potentially two different kinds of names to think about: names of data blobs and names of xibits. We could just use the urls of the data blobs as their names, or we could give shorter names-of-convenience to them when we first ref them. If we name the data blobs, then for each exhibit we can list the names of the data blobs that belong in the exhibit. If we name the exhibits, then for each data blob we can list the exhibits that contain it. If we name both blobs and exhibits, we can do even messier things :)
_______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
