Re: My departure + the future of Timeline and Exhibit
Hi David, David Huynh wrote: Hi all, As you might know, I have recently finished my Ph.D. study, and within a few months I'll be moving on to a real job at Metaweb. Tremendous congratulations! It is fantastic that the open community will still be able to benefit from your considerable skills while at Metaweb! Best of luck, David! Mike ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Re: Questions on exhibit capacity and performance
Ryan and Mark, It might be worthwhile posting up a new page on the wiki with known counts for various Exhibits. I think the ant one I looked at recently was about 650 records, as is my semantic tools one [1] (but it also has thumbnails, which slows presentation). As far as I know, these are the two largest, but perhaps there are some other big ones that have not yet been documented on this list (or that I overlooked). In any event, a wiki page with some examples might help others to look at the variety being deployed (format, size, facets, images, etc.) and then determine for their own circumstances what a good sizing number might be. Mike [1] http://www.mkbergman.com/?page_id=325 Ryan Lee wrote: As Robert notes, finding a hard limit is probably infeasible given the nature of the web and browsers. However, in terms of orders of magnitude, we have a general perception that 1,000 is a killjoy, a few hundred can be nice, and the ground between depends on your computer's specs. There's nothing formal behind that breakdown, and other anecdotal experiences are welcome to help flesh out a more useful picture. Robert Forkel wrote: i doubt there could be really comprehensive testing of this issue, because the environment it depends on - javascript in browsers - is too varied. even in the case of firefox 2.0.x, which i am using, it depends on the number and kind of installed plugins, the number of opened tabs, the time the browser has been running, ... On Dec 10, 2007 7:53 PM, Mark Feblowitz [EMAIL PROTECTED] wrote: Has anyone done any testing to see whether/how/where exhibit performance degrades as the number of items or the total size of the exhibits grows? This could be very valuable in deciding whether/how to use exhibit. Thanks, Mark ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Another Benchmark on Exhibit Sizes
I just posted an update on the Exhibit-powered Sweet Tools [1], which now includes 650 listings including thumbnails, description text, and multiple fields. I know the issue of Exhibit performance and size comes up frequently in this forum; Exhibit appears to work OK at this scale. Also, I noticed some improvements in the RDF/XML export. Thanks, David! (There still are some issues with embedded image references, but those are easily fixed with some global text replacements to deal properly with namespaces.) [1] http://www.mkbergman.com/?p=410 and http://www.mkbergman.com/?page_id=325 ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Exhibit 2.0 - Google spreadsheet + WP
I just updated to the v2 beta of Exhibit. My Sweet Tools listing
(http://www.mkbergman.com/?page_id=325) is perhaps different than some
in that its source data is obtained from a Google spreadsheet and it is
published within WordPress.
The migration went smoothly, and the migration instructions
(http://simile.mit.edu/wiki/Exhibit/2.0/Migration) were easy to follow.
However:
1. I first needed to make reference to the spreadsheet in new v. 2.0
style; see
http://simile.mit.edu/mediawiki/index.php?title=Exhibit/How_to_make_an_exhibit_from_data_fed_directly_from_a_Google_Spreadsheetaction=editsection=5
2. Then, unlike the migration instructions, I needed to change (for
example) body ex:ondataload = window.exhibit =
Exhibit.create('President');, which was actually closer to body
onload = Exhibit.create (null,
null).loadGoogleSpreadsheetsData('http://spreadsheets.google.com/feeds/list/o15870720903820235800.6608843240919541064/od6/public/basic');
in my case, to *simply* body. Then, the migration instructions say to
insert a replacement. This does *not* work for Google spreadsheets; do
not insert anything.
3. I also needed to trap and substitute for when ampersands occur in
URLs for the RDF exporter (instructions not provided herein; likely not
applicable to many).
4. Also, I would like to know how to adjust the properties (valign, for
example) of the ol/li record number to the left of the
exhibit-titleView-body class.
I have not updated the Simile wiki with these changes or instructions
because I do not know how universal they may be and don't want to mess
up the current announcements and all that accompanies it. I'll leave
that up to the various project folks. :)
Nonetheless, this was a fairly complicated migration, an unusual
environment, and much tailored CSS and other local stuff. Nice job,
Simile, and David!
(BTW, David, congratulations on the new Ph.D.! ;) )
Mike
___
General mailing list
General@simile.mit.edu
http://simile.mit.edu/mailman/listinfo/general
Re: Longwell and Ontologies
Stefano, To be entirely honest with you, not a lot lot of thought went into any of the ontologies that we have created here at SIMILE... I know it sounds weird, but the main reason for Longwell to use ontologies that have a http://simile.mit.edu URI prefix is have short-hand labels for URIs so that the interface looks prettier and more consistent. Thanks; at least I won't continue to probe your archives for further background. :) I will also not give further attention to skosext. Sometimes negative results are as helpful as positive ones. That process lead to no new ontologies for Longwell and to nothing substantially different in the way we RDFized the datasets used... but lead to this blog post about the quality of metadata that I wrote on my blog: http://www.betaversion.org/~stefano/linotype/news/95/ I recall reading this quite a bit ago; good stuff; still true. (BTW, the listing of metadata schemas was *very* helpful, but it's interesting that the repository has dropped from 898 sources to 225 in 18 mos, and very little use outside of OAI and the LOC at that!) You should ask Mark, really. I'm the only other person here that ever touched SKOS (when RDFizing the Barton catalog) but I would consider myself a newbie other than a pro in that respect. Do you know if Mark still monitors this forum, or should I make outreach directly? Thanks, Mike ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Re: [fyi] google does index iframe content
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? Keith, Probably my use of canonical creates more confusion than it helps. I'm no believer in one ring to rule them all and understand many data formats and serializations will appear in the wild and should be supported if market/use share is sufficient. Some of my recent writings supporting a range of ontology formalisms affirm this argument. (However, that is a different matter for the software developer; she needs to decide what the 'canonical' internal representation form should be.) What I meant to refer to in my excited response to Ben was simply the view or presentation layer. With Exhibit, the view is driven by JS and is not indexed by standard crawlers. With RDFa (or eRDF, as well), it is indexed, plus the presentation can be seen by those that choose not to use JS. The purpose of RDFizers, Babel, GRDDL, etc., is to convert one data form to another data form. My understanding is that Exhibit works natively off of JSON. But, if you have Bibtex, Excel, N3, RDF/XML, or tsv, you can use Babel to convert to JSON; you can import Google spreadsheets directly to Exhibit with Exhibit's own converters; or you can use other means further upstream to convert a wild form into JSON, RDF/XML, whatever. In fact, I seem to recall a couple of your own cool posts where you have literally a chain of conversions from multiple sources in order to get the data in a form ultimately necessary by the app. The only thing I was trying to muse about in the misuse of the word canonical was whether RDFa could become that conversion target, with Exhibit in turn working off of RDFa rather than JSON. (Or, perhaps more appropriately, the conversion of RDFa to JSON!). That's where my rhetorical question about roundtripping to JSON arose. My only real point was how/what to offer users as a format target that both displays independent of JS and Exhibit could use. As for the need to remove friction that you and Stefano mention, of course, absolutely! Mere mortals want automated background tools to do all of this. But, if those tools existed, I for one would use them to convert my lightweight data sources to Exhibit displays that I could also post as indexable HTML. Mike ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Re: [fyi] google does index iframe content
Hi All, Could this possibly mean that RDFa becomes the best and nearest import and export form for Exhibit? The first layer of the onion outside of Exhibit that gives an HTML option in every case? In other words, can it become the non-JS canonical form off which Exhibit works? If so, that would suggest that all other formats should possibly resolve to RDFa, whether used by Exhibit or not. And, also, may that not also offer a general solution to the JS--Google indexing conundrum? I'm sure I'm missing something here, but I always love to think about what should be the canonical forms, the common denominators. What looks cool to me is that RDFa meets the RDF canonical test I've been worrying about on other forums, and it meets the Exhibit and indexing test for human display. Is this silly or stupid? For example, can JSON be easily roundtripped to RDFa??? If so, I could become a RDFa fanboy, too! (Or is there a fatal flaw in this thinking somewhere???) I think Keith is really doing some important stuff here, and thanks Ben for crystallizing what has been percolating for some time. Mike Ben Adida wrote: Stefano Mazzocchi wrote: Agreed, this iframe idea is not that useful if google sends you to a crappy HTML table page instead of your pretty exhibit-enabled one. So Keith Alexander's been working on an RDFa importer for Exhibit which should make it into v2, and it really seems like the ideal solution to this problem: make an ugly HTML table marked up with RDFa, let Google index that, and use Exhibit JS to transform that ugliness into the beautiful lens'ed view. You can even make the HTML table not so ugly so your non-JS-enabled friends can enjoy the data. All of this, and no data repetition. I know I'm an RDFa fanboy, so what am I missing? -Ben ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Knock 'em Dead at WWW 2007!
To All, I know everyone on this list appreciates the many great folks at MIT that contribute to our enjoyment about Piggy Bank, RDFizers, Exhibit, Timeline, Longwell, you name it, and the good friendship, and great and responsive code! Thanks to all of you, very, very much. There are certainly others who will be there, but I'd like to specifically thank David Huynh and wish him well on his Exhibit presentation. See David's reference about that here: http://simile.mit.edu/blog/?p=31 and also note the really cool past Exhibit display of WWW papers (this *really* deserves some promotion to the WWW 2007 folks!). Hey, guys. It is really up to each of us on this list to do what we can to let the world know what great stuff is happening here. I know, for myself, that I'm not a code jockey nor theoretical thinker in the same league as these folks. But, what I *do* know, is to a person, everyone associated with Simile is responsive and showing all of us how innovation, open source and multiple project code management can occur simultaneously. And, oh, BTW, most of these folks are also trying to carve out the time for family and advanced degrees Simile folks, you rock, and you get it! Thanks so much. I hope that the kudos and responses everyone gets in the hall at WWW 2007 show you just a fraction of how much all of us out there in the Web ether appreciate your super efforts. /*signed*/ All of us who benefit from your work ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Re: Exhibit 2.0 scissors
Hi David, David Huynh wrote: snip /snip Right now I'm leaning toward Florian's suggestion of a special mode. Say, if you hold down Shift, a few little controls appear on the item lenses to let you do things including copy off the data. I think if the scissors are such annoying then giving the option ex:copyIndividual=[true|false] we can almost guess what people will do. I wonder if there are other things people want to do beside copying... like send the data off to some other web site. Maybe if the user has installed Piggy Bank [1], then there's a button for saving the data into My Piggy Bank. You have my vote on Piggy Bank! :) Mike ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Re: blog/exhibit integration
Derek, Very nice! Let me add a vote of encouragement for an eventual write-up on using Exhibit with RoR apps. BTW, any comment on why you went with Radiant v. Mephisto (or others)? Mike derek | idea company wrote: Hi guys, just thought I'd let you know that at http://radiant.ideacompany.ca/ I've started merging 2 really cool apps together (Radiant CMS and Exhibit) nothing is up yet as I'm moving everything off of my localhost and over to my host. Radiant is a really easy to use Rails app and works really well for integrating with Exhibit (I think). I'm also going to write up my process for how I'm putting exhibit into it. I'm using the nobelist.js dataset, I hope you don't mind. And it's going to be using the 2.0 branch of exhibit. I love this stuff. It just means I'm working less and playing more. Cheers, Derek. ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Re: Exhibit Problems
Hi David, My Exhibit is also broken, and I have been using the release version for quite some time: http://simile.mit.edu/repository/exhibit/trunk/src/webapp/api/exhibit-api.js Do I need to update the reference? Thanks, Mike David Huynh wrote: Hi Derek, Sorry about that... I've been doing a lot of refactoring recently and I probably have broken something. I don't have time right now to guarantee that the development versions work in all cases. Would you mind moving back to the release version on static.simile.mit.edu? I'm hoping to get Exhibit 2.0 to alpha within 2 - 3 weeks... So this is crunch time :-) David derek | idea company wrote: Hi all, so I've just recently run into an issue. I'm not sure if a directory name was changed in the repository however I'm using the http://simile.mit.edu/repository/exhibit/tags/1.0.pre-ui-split/src/webapp/api/exhibit-api.js version, and it seems to no longer function. The page will start loading and it will bring up the working/loading image and then stop without loading anything after that. I haven't changed any code to the my exhibit in a while and it was working last night so I'm not sure what's going on. You guys can check it out at http://designr.sheridanc.on.ca/projects.php Cheers, Derek ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Apache and SemWeb (branch of Interesting Collection with faceted browser)
Stefano and Erik (and anyone else!), This is a *very* interesting thread and a wonderful site. I've poked around quite a bit on the Peel Library site and have not seen a description of how the site is built and with what components. Do you have a reference link? More broadly, I have looked at various Apache projects numerous times in the past trying to see how specific ones may relate to semantic Web efforts. But, as an outsider plus the general lack of informative material on the Apache site, I most often come away more confused than educated. Can either of you point me to some links or provide a basic dump on Apache projects (Solr, Cocoon, SolrForrest?, ???, ???) and their relation to SemWeb applications? And, Erik, do you know anything of Carrot2 and how it might relate as well? Thanks, Mike Erik Hatcher wrote: On Mar 19, 2007, at 12:13 PM, Stefano Mazzocchi wrote: http://tinyurl.com/2xcdzb I use this site for UI inspiration with facets, with map and timeline integration and the clever collapsing cloud. Note: the faceted browser is powered by Apache Solr. but of course! :) It would be (perhaps a Google SoC project?!) a great project to tie Solr to Exhibit tightly so that facets could be the full facet list even if only showing a sub-set of the documents, allow paging and sorting to bounce through the server too. Solr fully supports JSON search responses. Erik ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Re: Apache and SemWeb (branch of Interesting Collection with faceted browser)
Erik, Great info. I know it was a lot to ask; I hope others found your info useful as well. :) Erik Hatcher wrote: On Mar 19, 2007, at 3:04 PM, Michael K. Bergman wrote: This is a *very* interesting thread and a wonderful site. I've poked around quite a bit on the Peel Library site and have not seen a description of how the site is built and with what components. Do you have a reference link? I happen to know the developers of the site, Peter Binkley and Tricia Williams. We've met at various library-related meetings. They have posted on the solr-user list about this site and were an early adopter of facets even before they were built into Solr, using a hack I had created for Collex. But, as an outsider plus the general lack of informative material on the Apache site, I most often come away more confused than educated. No doubt its hard to navigate the guts. But projects like Lucene are key components in at least the Java-based semantic web engines (notably Kowari and Sesame, and Longwell too). Can either of you point me to some links or provide a basic dump on Apache projects (Solr, Cocoon, SolrForrest?, ???, ???) and their relation to SemWeb applications? And, Erik, do you know anything of Carrot2 and how it might relate as well? *whew* Carrot2 is a clustering engine. I don't have experience with it, so cannot comment there, other than to know it exists and has a great reputation. Solr is Lucene made easy to use from any environment, not just Java, and value adds a lot on top of Lucene with caching, filters, index reader/searcher management, document update management, and much more. Building indices is key to navigating lots of data, and Solr can rock and roll on indexing provided a domain is mapped into a document/field/term structure. So I think Lucene and Solr are very valuable components to the semweb tool chain. Cocoon is used by the Peel Library site for being the rendering side of things, conversing with Solr and formulating the response. It can tap into Solr very easily, with XML or JSON depending on which part of Cocoon is gonna digest the data, coming back from Solr. SolrForrest - don't know much about, though the publish pipeline sending content right into the search engine makes a lot of sense. Erik ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general -- __ Michael K. Bergman Web Scientist 380 Knowling Drive Coralville, IA 52241 mailto:[EMAIL PROTECTED] 319.339.0110 http://mkbergman.com __ ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Re: Exhibits invisible to Google
Done. The first draft of this documentation can be found at: http://simile.mit.edu/wiki/Exhibit/How_to_make_Exhibit_search_engine_%22friendly%22 Nothing is really solid, ever :) ... so I think anytime starting to document is good. If you have time, some preliminary documentation on our wiki would be greatly appreciated! Sometimes, just making the wiki page is already half of the battler :) Thanks, David ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Re: Exhibits invisible to Google
David, Massively cool; I should have paid closer attention to this thread about 1 month ago. Thanks. However, of course, I don't (does anyone?) want to simply post up a static version of a dynamic exhibit solely to get indexed by search engines. Somehow that feels like too much duplication. What I did on my web site was to have the full Exhibit version with sortable and filterable records, and then to create a separate static page with a simple table with live links as a kind of table of contents. Other layout distinctions are possible between the static and dynamic versions, but I do think different layouts help preserve respect for the user by providing a different access/view/display option. What I did on my actual site was to modify the starting spreadsheet to create these two versions, the dynamic Exhibit one fed directly from Google, the other smaller version cut-and-pasted into the static HTML. But, with Copy All, there are some additional and cooler options. I tried both with these strengths/trade-offs: 1. Generate HTML preserves all of the record info. With a few global SRs, I was easily able to style=display: none to select which info actually displays, and then make some minor changes to format differently (if, say, a more table listing view is desired). *Advantage:* preserves all content for indexing *Disadvantage:* takes some HTML manipulation and time 2. Generate a TSV file, import into Excel, remove columns with undesired fields, embed into static page. *Advantage:* fast and avoids Excel's crappy HTML/XML generation *Disadvantage:* some record content not indexed. While it would be helpful for my specific needs to request a feature that would allow individual data types to be selected for inclusion or not when doing a Copy All, I actually think that would clutter Exhibit and undercut its clean purpose. (Though I could foresee a separate utility down the road that could do Exhibit-related manipulations or processing. :)) Bottom line: what is there is very cool, and there is flexibility to the author to go multiple directions. Let me know if this portion is getting close to frozen, and I'll draft up some documentation for the wiki. Thanks, Mike David Huynh wrote: Hi Michael, You could go to your exhibit, scroll to the bottom, click Show all 500 items, scroll to the top, click Copy All, and choose Generated HTML of this View... Let me know if that works for you and does what you want... David Michael K. Bergman wrote: About 1/3 of the way into this thread about two months ago I made my last comment and then promised I would refrain from further bandwidth consumption. I was following Stefano's wise counsel of draft-delete-think. :) However, the reason for DavidH to start this thread in the first place remains. I just posted up a big update of my semantic tools listing using Exhibit, which gets a fair amount of traffic that I'd like Google to sustain. My answer (a kludge, really) to the indexing problem was to create a simple parallel table page with links and, as I had recommended in earlier posts, an adequate intro paragraph describing the nature of the exhibit on the Exhibit page itself. It would be great to have this parallel entry be able to be created through some Exhibit code or function, but actually what I did by hand was not too terrible (though an inelegant hack if one has greater skills!). As a stop gap until better options emerge, I'd still be happy to write up a temporary placeholder on the Simile wiki for this approach. (But I feel reluctant cluttering *real* new substance to the wiki without a sense it is valuable to the community.) Thoughts? Thanks, Mike ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general -- __ Michael K. Bergman Web Scientist 380 Knowling Drive Coralville, IA 52241 mailto:[EMAIL PROTECTED] 319.339.0110 http://mkbergman.com __ ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Re: Exhibits invisible to Google
About 1/3 of the way into this thread about two months ago I made my last comment and then promised I would refrain from further bandwidth consumption. I was following Stefano's wise counsel of draft-delete-think. :) However, the reason for DavidH to start this thread in the first place remains. I just posted up a big update of my semantic tools listing using Exhibit, which gets a fair amount of traffic that I'd like Google to sustain. My answer (a kludge, really) to the indexing problem was to create a simple parallel table page with links and, as I had recommended in earlier posts, an adequate intro paragraph describing the nature of the exhibit on the Exhibit page itself. It would be great to have this parallel entry be able to be created through some Exhibit code or function, but actually what I did by hand was not too terrible (though an inelegant hack if one has greater skills!). As a stop gap until better options emerge, I'd still be happy to write up a temporary placeholder on the Simile wiki for this approach. (But I feel reluctant cluttering *real* new substance to the wiki without a sense it is valuable to the community.) Thoughts? Thanks, Mike ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Re: Exhibits invisible to Google
Hi David, I don't mean to be cavalier or dismissive of this concern, but the truth is that MOST dynamic content (from Ajax or underlying databases) has always been invisible to crawlers, Google or otherwise. The co-called 'deep Web' or 'invisbile Web' has been written about for years (some by me). Estimates are that 'deep Web' content may range from 2x to 10x or more of the surface Web' content that is discoverable by crawlers. Indeed, I rather suspect that most data in Google spreadsheets itself is unindexed by Google (use the site:http://spreadsheets.google.com search; only about 700 sites are listed, which I suspect have had links embedded in standard static pages). Since the content in an Exhibit display is equivalent to a standard database record, the availability of the records themselves should not be of terrible concern (like individual addresses in an address book or individual events). However, it is LIKELY important that the overall nature of the database itself is important. Thus, one good practice is to make sure that an Exhibit display has an intro section in standard HTML describing the datasets and the display, or be linked to by another page that provides a similar description. Another alternative is to create a sitemap with a separate page showing some information for all of the records in the database (this can be an unobtrusive link to the JSON records themselves; while ugly, the content would still get indexed). At any rate, there ARE good practices to overcome the crawl limitations of dynamic content. I definitely would not call this perhaps the biggest impediment to adoption for Exhibit since it is shared by so many sites and applications. If you are concerned, you can check the crawl status of a Web site on Google by going to: https://www.google.com/webmasters/tools/sitestatus. That screen will also take you to a series of Webmaster options provided by Google (more if you can verify you are the site owner). So, I don't recommend any changes be made directly to the Exhibit code itself. If desirable, I could draft a short note for the wiki that could inform Exhibit users of what steps (including SEO) they might take better capturing some of the items above. Thanks, Mike David Huynh wrote: Hi all, Exhibit suffers from the same Achilles heel as other Ajax applications: the dynamic content that gets inserted on-the-fly is totally invisible to Google. My whole web site is now invisible to Google :-) Perhaps this is the biggest impediment to adoption. ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Re: Exhibit: Semantic Web Tools Listing on WordPress
Hi David,
Cool, those fixes seem to have worked. I would have hunted for hours
through the CSS before finding them. Thanks. (So that is the function
of showAll!).
I still want to:
-- ad thumbs to each entry
-- background highlight new listings (tried your trick, but could not
get to work)
-- upper right justify the thumbs in each record, and
-- substitute a 'no thumbs' image when missing.
I'm happy to do what I can to promote this to the broader WP community.
(I have done so in the past with some success.) But I do think it is
critical to package the message correctly (and do it quickly!).
Perhaps we should start another thread with the sole purpose of crafting
a one paragraph teaser. Here's one attempt:
No Database? No Problem!
With just a few simple steps, even the most novice blog author can now
embed structured data -- such as sortable and filtered table displays,
thumbnails, maps, timelines and histograms -- in her blog posts and blog
pages. Using the innovative, new Exhibit lightweight structured data
publishing framework from MIT's Simile project
(http://simile.mit.edu/exhibit/), you can now create rich data
visualizations of web pages using only HTML (and optional CSS and
Javascript code). Exhibit requires no traditional database technology,
no server-side code, and no need for a web server. Check out this post
(http://www.mkbergman.com/?p=326) to see how easy it is to embed this
exciting new breakthrough in your own WordPress blog!
Maybe it also makes better sense to write a better tutorial and include
it on the general Exhibit site.
Thoughts? Let me know how I can help.
Thanks, Mike
David Huynh wrote:
David
P.S. To speed up the initial rendering of the list, you might want to
set ex:showAll=false so that only the first 10 items are shown. Also,
on Windows, the facets don't display properly in both IE and Firefox
because there seems to be an interference from line 565 of
http://ww.mkbergman.com/wp-content/themes/ai3/style.css. Maybe an extra
rule like this would fix it:
#exhibit-browse-panel img {
padding: 0px;
}
etc.
___
General mailing list
General@simile.mit.edu
http://simile.mit.edu/mailman/listinfo/general
Re: Exhibit: Semantic Web Tools Listing on WordPress
To All EXHIBITIONists, I'm wanting to continue the ol' momentum on today's blog postings and email traffic. Specifically, does Johan, Derek, David or Danny have any objections to my publicly mentioning on my blog their comments in this forum today or incipient tools developments? Also, any one else is welcome to chime in for a basic roundup I plan to post either late tonight or early tomorrow. (I finally got the database and thumbnails cleaned up and now am ready to push it forward.) I'm hoping someone can also diagnose the Exhibit/Sweet Tools display problems with Opera and Safari. Thanks, Mike Danny Ayers wrote: Marvellous work! On 23/01/07, *David Huynh* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: David Huynh wrote: Mike-- Thank You! Wow! This is simply awesome! This is the first of its kind! This deserves many blog posts, I believe. :-) OK, I'm not Danny Ayers and my blog doesn't get read by millions of people, but I've tried to do my share :-) http://dfhuynh.wordpress.com/2007/01/23/calling-all-exhibitionists/ Ok, I bit: http://dannyayers.com/2007/01/23/new-things ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
Exhibit: Semantic Web Tools Listing on WordPress
To All, David, thanks so much for your great work on Exhibit and your very helpful tutorials. Also, thanks to many others of you on this forum for discussing and providing tips on how to use Exhibit. I have just posted my listing of 375+ semantic Web and -related tools on my WordPress blog using Exhibit with direct updates from a Google spreadsheet. The actual online Exhibit tools database may be found at: http://www.mkbergman.com/?page_id=325 How I did it and some other background info is found on this post: http://www.mkbergman.com/?p=326 I was also very complimentary to David Huynh and the rest of the Simile team on an earlier posting: http://www.mkbergman.com/?p=323 I'm still having some minor CSS issues and have some further enhancements that I will be working on and (perhaps) seeking assistance from this forum. I simply find Exhibit to be one of the more innovative advances in recent memory. I hope to be able to do what I can to help promote it. David, and team, thanks again! This is really remarkable stuff. Mike -- __ Michael K. Bergman Web Scientist 380 Knowling Drive Coralville, IA 52241 mailto:[EMAIL PROTECTED] 319.339.0110 http://mkbergman.com __ ___ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
