Aperture is a Java framework for extracting full-text content and
metadata from various information systems (e.g. file systems, web sites,
mail boxes) and the file formats (e.g. documents, images) occurring in
these systems.

https://aperture.sourceforge.net/

Today, on 12th November 2007, we publish the first beta release, marking the point where aperture is being applied in projects. The new version number is 1.0.1.

This release bears the mark of the Nepomuk Social Semantic Desktop - a major intiative combining research institutes and commercial companies from around Europe. Aperture is used as one of the pillars of a next-generation platform that changes the way people can organize and use the data stored on their computers. The input from the Nepomuk Community drove us to implement a host of new features that make Aperture more useful, more flexible and more powerful.

New Features

• Aperture has been migrated to use the newly developed
  Nepomuk Information Element Ontology framework. This
  added a new level of precision and expressiveness to the
  output of Aperture components. The ontology itself
  is endorsed by the Nepomuk Consortium, well documented
  and maintained.
• The output is now thoroughly tested with an extensible
  rdf validator for compliance with the ontology. This
  allowed us to fix a number of bugs that made certain
  properties appear in places they didn't belong
• the data source configuration API has been overhauled and
  is now much more easy to use
• A new facility that allows clients to implement dynamic
  GUIs for data source configuration.
• New JpgExtractor that extracts EXIF annotations from JPG
  files
• four new experimental crawlers (Flickr, Bibsonomy,
  del.icio.us and Apple IPhoto).
• host of small improvements and bug fixes

Another improvement is a public wiki for documentation,
tutorials and FAQ.
https://aperture.wiki.sourceforge.net/

Updated dependencies

• Sesame 2.0 beta-6 (was beta-4)
• RDF2Go 4.4.6
• RDF2Go driver for sesame
• A metadata-extractor-2.4.0-beta-1 library used by the
  JPGExtractor
• POI has been update to 3.0-FINAL
• flickrapi-1.0b4 used by the FlickrCrawler
• DFKIUtils 2.0 some XML-related utilities are used by the website crawlers
• nrlvalidator-0.1 the validator used by the unit tests
• infsail-0.1 and unionsail-0.1 dependencies of the
  validator

Download here.

Best regards
Antoni Mylka
Christiaan Fluit
Leo Sauermann

The semantic web is about URIs, and every idea needs a URI. Each of my blog posts already got one, but now also in printed form. Look to the lower right, a mobile-phone readable QR code.



Technically this all is age-old and I loved it already years ago when semapedia had its "uh-ah". The Nipponese, in the meantime, went for the full monty and covered their island coast-to-coast with QR codes, so we have to catch up.

For my mother of all cell phones E70, I use the i-nigma reader (ha, another enigma pun) because it was listed on Nokias page on barcode apps.

To hack twoday.net to render them I added a table after the blogposts in the "manage" menu - change template (html) - story.display - add somewhere this code (generated using i-nigma generator):

<!-- barcode -->
<img style="float:right" src="https://212.179.113.209/QRCode/img.php?d=URL%3Ahttp%3A%2F%2Fleobard.twoday.net%2Fstories%2F<%
story.id %>&c=blogcode&s=4" alt="QR barcode linking to this story. Useful when
printed." />

The leobard.twoday.net part needs to be replaced. It can probably be simplified by replacing the whole uri with <%
story.href %> but then I feared that the URL-encoding would break.

Next task for all Semantic Web lovers: print out and clue barcodes to all physical things that deserve a URI. And don't fuck it by picking an uncool URI, pick a cool uri for the semantic web.

Wir vergeben einen

HiwiJob/ Praktikum: Ein Wiki für den Semantic Desktop.

Der Semantic Desktop erlaubt dem Benutzer, Dokumente seines Arbeitsplatzes (Dateien, Webseiten, Adressen, Termine...) beliebig zu
verknüpfen und mit weiten Informationen zu versehen. Als Schnittstelle
zum Benutzer dient dabei ein persönliches Wiki, das entsprechend
erweitert wird.

Die Arbeit erfolgt in Zusammenarbeit mit anderen Entwicklern und ist
größtenteils praktischer Natur. Die Fähigkeit zum selbständigen
Implementieren sowie zum schnellen Einarbeiten in existierende
Frameworks ist Voraussetzung. Zur Koordination der Entwicklung
wird ein Softwareentwicklungsportal benutzt. Die erstellte Software ist
größtenteils Open Source.
Anforderungen

• Erfahrung mit Java, JSP, JavaScript, Tomcat
• Erfahrung mit Open SourceProjekten (Dokumentation etc.)

Kontakt
Leo Sauermann
Deutsches Forschungszentrum für Künstliche Intelligenz
Forschungsbereich Wissensmanagement
Trippstadter Straße 122, Raum 3.04
Tel.: +49 631 20575-116
sauermann@dfki.unikl.de

Johannes Grenzfurthner and Frank A. Schneider had a gig yesterday at Sparte4 in Saarbrücken.

Luckily, they texted me at 4pm while sitting in the train, and I had the chance to watch them and make pics.

here is the set:
https://www.flickr.com/photos/leobard/sets/72157602882491541/

Walter Rafelsberger who runs the meta portal of media polemic has blogged about His Holy Grail of PIM.

Excerpt:
One thing I have in mind would be a microformats/AJAX/xmlrpc/API/etc. powered Wiki with focus on ease of use and service integration. The SemanticWiki implementations are heading in the right direction, but they still feel more like proofs of concept and not really usable in terms of usability.

That said, for the moment I decided to switch from one evil to many small little devils. Here's what I use for PIM for now.

Yep! read on ....
link