Semantic Turkey is a Firefox extension for Knowledge Management and Acquisition, based on Semantic Web Technologies.
It can also be seen as a "bookmark system on steroids", which allows you to separate the WHAT (people, events, organizations...any kind of thing) that you are interested in, from the WHERE (the pages that you bookmark that contain information about them).
While traditional bookmarking always ends up in tons of page which are rather difficult to organize, with ST you can define your personal domain of interest through a conceptual representation called ontology. You can then add objects to the ontology, describe them through attributive properties or connect them through relational properties, and, at the same time, keep track of (bookmark) the pages where you find information about them. These operations need not to be performed in a strict order: with very simple drag&drops, you can add new objects while you find them on the web.
The xpi of Semantic Turkey is platform independent, though it requires a Java Virtual Machine with support for "live-connect".
Product's homepage
Requirements:
· Mozilla Firefox
What's New in This Release: [ read full changelog ]
· modified getSubClasses request from Cls.java for showing chosen labels instead of the class qname
· fixed a BUG in the response packaging in the server to always reply with properly UTF-8 encoded characters
· fixed BUG in SPARQL panel (on client, UI project) preventing language tagged property values to be shown (javscript null pointer exception)
· added a new updateRoutine (see UpdateRoutines in resources package) for specifying the ModelType of main-project if it is not present (that is, if the main-project comes from an earlier version of SemanticTurkey)
· added support for SKOS / SKOS-XL
· removed constraint on "at least a type (not owl:Thing) for each resource", now owl:Thing is always visible
· added support for OWLART API ModelConfiguration
· new support for graph view of the ontology through a new applet based on Jung graph java library
· improved Mac compatibility (still considered unstable)
· improved assignment of values from properties, by inferring proper range type from both type of the range and of the property itself
· support for content negotation (now import functionality always asks for proper RDF format, by inferring it from the file extension, default is RDF/XML)
Find us on Google+
