Today I finally plugged-in the Yahoo Boss Mashup Framework into the Google App Engine environment. Google App Engine (GAE) provides a pretty sweet yet simple platform for executing Python applications on Google's infrastructure. The Boss Mashup Framework (BMF) provides Python API's for accessing Yahoo's Search API's as well remixing data a la SQL constructs. Running BMF on top of GAE is a seemingly natural progression, and quite arguably the easiest way to deploy Boss - so I spent today porting BMF to the GAE platform.
See also http://bossy.appspot.com/qa?query=who+is+brad+pitt+married+to
Sprout is the quick and easy way for anyone to build, publish, and manage widgets, mini-sites, mashups, banners and more. Any size, any number of pages. Include video, audio, images and newsfeeds and choose from dozens of pre-built components and web services.
Many RDF toolkits provide SPARQL/Update functionality and move from simple query operations to more powerful data manipulation. SPARQLScript goes another step further and enables or simplifies the implementation of
* semantic Mashups,
* custom, portable rule and inference scripts using a SPARQL-based syntax
* Output templates for RDF data and SPARQL query results
* RDF/SPARQL-driven Yahoo! Pipes-like systems
The idea behind wectar is the fusion of two worlds, dmoz.org (open directory project) and delicious.com. This fusion is seen by us as a mutual enrichment of two stages in the evolution of the world wide web. What makes both of these two great services for sure true pioneers of web 3.0 is their generosity of making their unique knowledge available for mashups like wectar. Obviously wectar couldn't be without this generosity. We hope that we can repay this kindness to some extend by promoting both services through our web site.
Piggy Bank is a Firefox extension that turns your browser into a mashup platform, by allowing you to extract data from different web sites and mix them together.
Piggy Bank also allows you to store this extracted information locally for you to search later and to exchange at need the collected information with others.
This article posits a definition and theory for "Library 2.0". It suggests that recent thinking describing the changing Web as "Web 2.0" will have substantial implications for libraries, and recognizes that while these implications keep very close to the history and mission of libraries, they still necessitate a new paradigm for librarianship. The paper applies the theory and definition to the practice of librarianship, specifically addressing how Web 2.0 technologies such as synchronous messaging and streaming media, blogs, wikis, social networks, tagging, RSS feeds, and mashups might intimate changes in how libraries provide access to their collections and user support for that access.
Inspired by Yahoo's Pipes, DERI Web Data Pipes implement a generalization which can also deal with formats such as RDF (RDFa), Microformats and generic XML.
DERI Pipes are Open Source Software, ad as such they can be easily extended and applyed in use cases where a local deployment is needed.
DERI Pipes provides a rich web GUI where pipes can be graphically edited, debugged and invoked. The execution engine is also available as a standalone JAR, which is ideal for embedded use.
DERI Pipes, in general, produce as an output streams of data (e.g. XML, RDF,JSON) that can be used by applications. However, when invoked by a normal browser, they will provide a end user GUI for the user to enter parameter values and browse the results
mSpace is an interaction model designed to allow a user to navigate in a meaningful manner the multi-dimensional space that an ontology can provide. mSpace offers potentially useful slices through this space by selection of ontological categories.
Relevant content from around the web brought to you as you're typing.
API allows to bring these related Images, Articles, Hyperlinks and Tags to your Application.
As we enter the brave new world of software-as-a-service and software-based-on-services (like mash-ups and composite applications), there is a burden that information technology departments must bear that often goes unacknowledged--operational complexity.