Posted:January 25, 2010

Updates Posted to Sweet Tools, SWEETpedia

Sweet Tools Listing

Minor Updates Provided to these Standard AI3 Datasets

If you are like me, you like to clear the decks before the start of major new projects. In Structured Dynamics‘ case, we actually have multiple new initiatives getting underway, so the deck clearing has been especially focused this time.

As a result, we have updated Sweet Tools, AI3‘s listing of semantic Web and -related tools, with the addition of some 30 new tools, updates to others, and deletions of five expired entries. The dataset now lists 835 tools. And, as before, there is also now a new structured data view via conStruct (pick the Sweet Tools dataset).

We have also updated SWEETpedia, a listing of 246 research articles that use Wikipedia in one way or another to do semantic-Web related research. Some 20 new papers were added to this update.

Please use the comments section on this post to suggest new tools or new research articles for inclusion in future updates. Markup

Updates Posted to Sweet Tools, SWEETpedia




Minor Updates Provided to these Standard AI3 Datasets If you are like me, you like to clear the decks before the start of major new projects. In Structured Dynamics‘ case, we actually have multiple new initiatives getting underway, so the deck clearing has been especially focused this time. As a result, we have updated Sweet […]

see above


7 thoughts on “Updates Posted to Sweet Tools, SWEETpedia

  1. Is the bibliography available in any structured formats? e.g. BibTex

    The Wikipedians maintain some very similar bibliographies:

    Have you considered keeping your list in a wiki or other collaborative environment so that it could be maintained as a group effort? If it had some support for provenance/history, that would also relieve you of having to remember to attribute the sources for the various entries.

    Lastly, a minor correction – “Lexical Authorities in an Encyclopedic Corpus: A Case Study with Wikipedia” is almost certainly this blog post

  2. Hi Tom,

    No, at this time, the Wikipedia stuff is not in structured form. (The Sweet Tools are.) I will likely do so, as the length is getting long (though I’m only adding increments that I periodically encounter), and I have gotten more structured for other listings as they have reached the tipping point.

    If you want to create a structured version, I would gladly give you my internal wiki stuff or post links to whatever you produce.

    The Wikipedia links you cite reference my listing and others have been updating based on what I find.

    As for collaboration, I agree that is generally the best practice. I look to the Wikipedia listings you cite for this. But, frankly, I find many, many more than what crowdsourcing provides there. I also have no machinery on this blog site for multiple authors. Since this stuff is part and parcel for my company’s efforts, I actually want to touch every paper myself, not merely provide a compilation.

    (Also, I have done collaboration with Sweet Tools via GDocs, but that has been less than stellar IMO.)

    Thanks for the Bellomi link; now updated.

  3. Hi Mike,

    Please consider adding RDF.rb, a new public-domain Ruby library, to the Sweet Tools exhibit. For your convenience, here is the relevant metadata:

    Description: RDF.rb is a pure-Ruby library for working with Resource Description Framework (RDF) data.
    Category: IDE/Programming Environment
    Primary Language: Ruby
    FOSS?: Yes

  4. Knoodl facilitates community-oriented development of OWL based ontologies and RDF knowledgebases. It also serves as a semantic technology platform, offering a JAVA service-based interface or a SPARQL-based interface so that communities can build their own semantic applications using their ontologies and knowledgebases. Knoodl is a product of Revelytix, Inc. and is hosted in the Amazon EC2 cloud and is available for free. It can also be licensed for private use. For more information, visit the Revelytix web site or contact

    Knoodl’s capabilities include:

    Cloud-based application (Amazon EC2)
    Ontology editing
    Ontology import/export
    Collaboration and queryable threaded discussions
    Role-based security
    Choice of scalable RDF stores (Jena, Mulgara, or Oracle)
    Ontology Guided Search
    SPARQL Endpoints
    HTTP service for graph updates
    SPARQL query wizard
    User designed views of query results

  5. Mike, you already have TopBraid Composer included in your listing. However, TopQuadrant offers a number of other products which have not been listed: TopBraid Live, TopBraid EVN, SPARQLMotion and TopSPIN

    TopBraid Live is an enterprise SOA-capable Semantic Web application platform optimized for delivering dynamic model-based applications. With TopBraid Live, you can quickly implement solutions that integrate data, content, application services and user interactions. More information is available at:

    We believe TopBraid Live fits in the category “Composite App/Framework” while TopBraid Composer is probably a better fit for “Ontology/Vocabulary Editor” or IDE category.

    Another entry for the “Ontology/Vocabulary Editor” is TopBraid Enterprise Vocabulary Net (EVN). Where TopBraid Composer is a very powerful Eclipse plugin for expert users, TopBraid EVN is a web-based system that targets a different user base.

    TopBraid Enterprise Vocabulary Net (TopBraid EVN) is a web-based solution for simplified development and management of interconnected controlled vocabularies. It supports business stakeholders who need to collaborate on defining and linking enterprise vocabularies, taxonomies, thesauri and ontologies used for information integration, customization and search. More information is available at:

    TopBraid Ensemble (TBE) is the quickest route from an ontology to a working web application. Once you have your ontology, optionally with some RDF data, all that remains to be done is pointing a web browser to one of the pre-configured application templates. Applications pre-packaged with Ensemble let you navigate through semantic models and corresponding data, using trees, grids and search form components. They can also include maps and graph visualization and query builder components.

    TopBraid Ensemble (applications are not for browsing only. They feature model-driven edit forms, drag and drop and auto-complete operations. All TBE applications offer full multi-user support. Ensemble applications work with any data store supported by the TopBraid Suite and with all popular web browsers. Pre-packaged applications are merely a starting point with Ensemble. Using only a web browser, you can easily customize applications by adding, removing and reconfiguring components, popup dialog boxes, and additional pages to create multi-page applications. More information at:

    Ensemble may fit in the category you are calling “Browser (RDF, OWL or semantic)” or since TBE applications fully support multi-user editing and collaboration, a better fit may be “Wikis and -related” category or even “Data Presentation”.

    SPARQLMotion is visual a scripting language and an engine for semantic data processing. Scripts implementing sophisticated data services and processing such queries and data transformations can be quickly assembled with easy to use graphical tools saving weeks of development time. More information is available at:

    SPARQLMotion fits in your “Mashup/Meshup Framework” category

    TopSPIN is an inference engine that works with SPARQL Rules (aka SPIN). SPARQL Rules are constraints and inference rules on Semantic Web models implemented using SPARQL. Constraints use SPARQL ASK, rules use SPARQL CONSTRUCT and SPARQL Update (DELETE, INSERT). Also supported are meta-modeling capabilities that allow users to define their own SPARQL functions and query templates without having to write Java code. TopSPIN inferences directly over RDF data without a need to transform RDF into some other format as it is commonly done with other inference engines. It provides incremental inferencing and explanations. More information is available at: There is an open source SPIN API at

  6. Hi Michael,

    May I suggest you to have a look at our semantic tagger at Methods and algorithms are described in some papers but this one is the more accurate with the actual version of our system:

    Canadian AI 2011 – May 2011 – Automatic Semantic Web annotation of named entities
    (referenced here and downloadable here

    Vary nice site and survey.


Leave a Reply

Your email address will not be published. Required fields are marked *