Vazaar Project Blog » News http://www.vazaar-project.org/blog The semantic store Thu, 02 Sep 2010 02:15:14 +0000 en hourly 1 Blog info updated http://www.vazaar-project.org/blog/archives/354 http://www.vazaar-project.org/blog/archives/354#comments Fri, 13 Aug 2010 22:46:20 +0000 Tomás Vírseda http://www.vazaar-project.org/blog/?p=354 Screenshots for current development version and download info updated.

–
May the cloud be with youSimilar Posts:

posted in News by Tomás Vírseda Leave A Comment
©2010 Vazaar Project Blog. All Rights Reserved.
]]> Screenshots for current development version and download info updated.

–
May the cloud be with youSimilar Posts:

]]> http://www.vazaar-project.org/blog/archives/354/feed 0 Vazaar 0.4.8: a new release for testing http://www.vazaar-project.org/blog/archives/317 http://www.vazaar-project.org/blog/archives/317#comments Sat, 10 Jul 2010 23:30:19 +0000 Tomás Vírseda http://www.vazaar-project.org/blog/?p=317 Vazaar icon logo

Hi,

another version of Vazaar is out for testing. Get it while hot. There are a lot of changes respect older versions. Now, you can manage easily your notes, diary, bookmarks an other resources. Also, you can display them as graph of connected resources or as a list. Resources can be imported/exported to/from other persons.

Don’t hesitate to email me with your comments (kaskaras @ gmail.com). Please, visit my launchpad project page for more info, report bugs, ask questions, etc.

.

How to get it

  • Direct link to download
  • From repository: bzr branch lp:~kaskaras/trunk/vazaar vazaar-readonly
  • From Pypi (updating)

How to install it

Once unpacked in any arbitrary directory:

  • Exectute it by running: ./bin/vazaar
  • Install it system-wide by running: sudo python setup.py install

Similar Posts:

Attached Files:

posted in News by Tomás Vírseda Leave A Comment
©2010 Vazaar Project Blog. All Rights Reserved.
]]> Vazaar icon logo

Hi,

another version of Vazaar is out for testing. Get it while hot. There are a lot of changes respect older versions. Now, you can manage easily your notes, diary, bookmarks an other resources. Also, you can display them as graph of connected resources or as a list. Resources can be imported/exported to/from other persons.

Don’t hesitate to email me with your comments (kaskaras @ gmail.com). Please, visit my launchpad project page for more info, report bugs, ask questions, etc.

.

How to get it

  • Direct link to download
  • From repository: bzr branch lp:~kaskaras/trunk/vazaar vazaar-readonly
  • From Pypi (updating)

How to install it

Once unpacked in any arbitrary directory:

  • Exectute it by running: ./bin/vazaar
  • Install it system-wide by running: sudo python setup.py install

Similar Posts:

Attached Files:

]]> http://www.vazaar-project.org/blog/archives/317/feed 0 What is coming in the next version http://www.vazaar-project.org/blog/archives/298 http://www.vazaar-project.org/blog/archives/298#comments Sun, 23 May 2010 16:50:59 +0000 Tomás Vírseda http://www.vazaar-project.org/blog/?p=298 Despite of the fact I don’t post in this weblog most often I think I haven’t wasted my spare time (my current work isn’t related with anything about this, yet). Instead it has been very productive and I am very happy with last results. In the end, I’m starting to see something useful.

Most of time, I’ve been reading more and more about NEPOMUK and playing with SPARQL queries. I have to recognize that it not that simple as I thought in a first moment but I’ll talk about this [intlink id="41" type="category" target="_self"]later[/intlink].

I have something to say about RDFLib: it is wonderful. From time to time I have to deal with some glitches but, most of them, are related to my own code. Anyway I am not using all the potential that this library offers.

Current work:

  • Vazaar is more stable than before. But (there is always a but) sometimes it crashes with a “segment fault”. This behavior is random and it is related with ‘Website’ resources.
  • Resources are not added directly to database. Before that, resources are passed to a queue. That means that you can enqueue new resources without waiting to finish the last one. Despite of Vazaar is designed to work with threads sometimes the GUI is blocked. This part is the most difficult and annoying thing that I’ve found. Someone smartest than me should take a look to the code.
  • By now, it is only possible to create/edit pimo:Notes (it’s finished but needs a deep revision)
  • “Copy & Paste” mode is working very well. If you copy any text from anywhere from your Desktop it will be added as a note. But Vazaar can recognize if it is more than simple text: if you copy an URL, the text will be added as a Website or if you copy a file from Nautilus the text will be added as a resource depending on its mimetype.
    Also, clipboard monitoring can be toggled at any time.
  • One of the most important features that I want for Vazaar is the possibility of displaying the resources content. Right now, Vazaar is able to display text-based resources (like the source code from a given program), audio, video, images or websites. Other resources like OpenOffice.org documents, compressed files, ISO images, etc. are executed in its own program.
  • Backup & Restore of your knowledge database. Although it is working very well it is not finished yet.
  • Basic D-Bus support implemented. Although I haven’t yet decided an API, in the future, others applications will be able to interact with Vazaar to query its database, add resources, etc. …
  • A basic but extensible plugin system based on hooks is available and working. I have tested it developing smalls plugins which extends the funcionality (send notes to twitter, extend menus, ..). In the future I hope to extend the funcionality of Vazaar by releasing plugins instead of releasing new version of this application.
  • The SPARQL Editor have been improved: now it groups triples according to its subject.
  • New icons to describe resources
  • I’ve developed a new Tag Cloud widget. Websites are analyzed getting their tags (if any). Tags are saved as resources as well.
  • I’ve started to define the PersonalInformationModel. The Knowledge Database must know who is the owner of (meta)data. This is necessary to share info with other people. Right now it is defined by a set of triples which define a pimo:PersonalInformationModel, which has a pimo:hasOwner. The owner is defined by a nfo:Contact
  • Another feature that I am trying to handle is related to bug lp:425877 in lauchpad. I’m trying to keep Vazaar window size as small as possible in order to be used in small devices.

Work to be done before releasing the next 0.5 version:

  • Be able to handle other kinds of resources like: pimo:BlogPost (diary entries), pimo:Topic, pimo:Person and pimo:PersonGroup (nco:Contacts), pimo:Organization, pimo:Project, pimo:Event, pimo:Meeting, tmo:Task, and tmo:TaskGroups, nfo:Bookmark and pimo:Collection
  • Be able to define relations between resources
  • Temporal bags: a way to make operations over different resources at the same time. Think in it as virtual collections of resources.
  • Annotate resources. Any kind of resource can have any number of annotations.
  • Support for i18n (make Vazaar translatable)

I’ll try to develop all of this along the summer and I hope to have the new version ready for production before next Ubuntu release. Also, I hope to have Debian packages ready to install easily. At the same time, Vazaar be able to be installed from Pypi.

If you are interested in the development of this application (and you are really welcome), take a look to my Launchpad webpage. Check out lp:~kaskaras/vazaar/trunk for last bits (bzr branch lp:~kaskaras/vazaar/trunk)Similar Posts:

posted in News by Tomás Vírseda Leave A Comment
©2010 Vazaar Project Blog. All Rights Reserved.
]]> Despite of the fact I don’t post in this weblog most often I think I haven’t wasted my spare time (my current work isn’t related with anything about this, yet). Instead it has been very productive and I am very happy with last results. In the end, I’m starting to see something useful.

Most of time, I’ve been reading more and more about NEPOMUK and playing with SPARQL queries. I have to recognize that it not that simple as I thought in a first moment but I’ll talk about this [intlink id="41" type="category" target="_self"]later[/intlink].

I have something to say about RDFLib: it is wonderful. From time to time I have to deal with some glitches but, most of them, are related to my own code. Anyway I am not using all the potential that this library offers.

Current work:

  • Vazaar is more stable than before. But (there is always a but) sometimes it crashes with a “segment fault”. This behavior is random and it is related with ‘Website’ resources.
  • Resources are not added directly to database. Before that, resources are passed to a queue. That means that you can enqueue new resources without waiting to finish the last one. Despite of Vazaar is designed to work with threads sometimes the GUI is blocked. This part is the most difficult and annoying thing that I’ve found. Someone smartest than me should take a look to the code.
  • By now, it is only possible to create/edit pimo:Notes (it’s finished but needs a deep revision)
  • “Copy & Paste” mode is working very well. If you copy any text from anywhere from your Desktop it will be added as a note. But Vazaar can recognize if it is more than simple text: if you copy an URL, the text will be added as a Website or if you copy a file from Nautilus the text will be added as a resource depending on its mimetype.
    Also, clipboard monitoring can be toggled at any time.
  • One of the most important features that I want for Vazaar is the possibility of displaying the resources content. Right now, Vazaar is able to display text-based resources (like the source code from a given program), audio, video, images or websites. Other resources like OpenOffice.org documents, compressed files, ISO images, etc. are executed in its own program.
  • Backup & Restore of your knowledge database. Although it is working very well it is not finished yet.
  • Basic D-Bus support implemented. Although I haven’t yet decided an API, in the future, others applications will be able to interact with Vazaar to query its database, add resources, etc. …
  • A basic but extensible plugin system based on hooks is available and working. I have tested it developing smalls plugins which extends the funcionality (send notes to twitter, extend menus, ..). In the future I hope to extend the funcionality of Vazaar by releasing plugins instead of releasing new version of this application.
  • The SPARQL Editor have been improved: now it groups triples according to its subject.
  • New icons to describe resources
  • I’ve developed a new Tag Cloud widget. Websites are analyzed getting their tags (if any). Tags are saved as resources as well.
  • I’ve started to define the PersonalInformationModel. The Knowledge Database must know who is the owner of (meta)data. This is necessary to share info with other people. Right now it is defined by a set of triples which define a pimo:PersonalInformationModel, which has a pimo:hasOwner. The owner is defined by a nfo:Contact
  • Another feature that I am trying to handle is related to bug lp:425877 in lauchpad. I’m trying to keep Vazaar window size as small as possible in order to be used in small devices.

Work to be done before releasing the next 0.5 version:

  • Be able to handle other kinds of resources like: pimo:BlogPost (diary entries), pimo:Topic, pimo:Person and pimo:PersonGroup (nco:Contacts), pimo:Organization, pimo:Project, pimo:Event, pimo:Meeting, tmo:Task, and tmo:TaskGroups, nfo:Bookmark and pimo:Collection
  • Be able to define relations between resources
  • Temporal bags: a way to make operations over different resources at the same time. Think in it as virtual collections of resources.
  • Annotate resources. Any kind of resource can have any number of annotations.
  • Support for i18n (make Vazaar translatable)

I’ll try to develop all of this along the summer and I hope to have the new version ready for production before next Ubuntu release. Also, I hope to have Debian packages ready to install easily. At the same time, Vazaar be able to be installed from Pypi.

If you are interested in the development of this application (and you are really welcome), take a look to my Launchpad webpage. Check out lp:~kaskaras/vazaar/trunk for last bits (bzr branch lp:~kaskaras/vazaar/trunk)Similar Posts:

]]> http://www.vazaar-project.org/blog/archives/298/feed 0 Vazaar 0.4 (aka Sacabambaspis) released http://www.vazaar-project.org/blog/archives/214 http://www.vazaar-project.org/blog/archives/214#comments Sun, 06 Sep 2009 00:16:05 +0000 Tomás Vírseda http://www.vazaar-project.org/blog/?p=214 Hi everybody,

a new version of vazaar have been released for testing purposes. Although it’s stable you can consider it as proof of concept.

This version is a redesign of the previous one. While the old one was developed in C, the new one is being developed with Python. Also, I’ve been studying a new approach. Instead of work with tags and tagging operations, the new version is powered by the semantic web vision, ideas and tools.

I’d like to highlight RDFLib, a RDF library containing an RDF triple store and RDF/XML parser/serializer which deals with the logic of the application.

Go to the Download page to get it. Check the screenshot page as well.

Development is carried out at Lauchpad.

Now that I understand how a semantic model works I have more and better ideas to implement.

Next version will be released, hopefully, before this year ends.

Enjoy it.Similar Posts:

posted in News by Tomás Vírseda Leave A Comment
©2010 Vazaar Project Blog. All Rights Reserved.
]]> Hi everybody,

a new version of vazaar have been released for testing purposes. Although it’s stable you can consider it as proof of concept.

This version is a redesign of the previous one. While the old one was developed in C, the new one is being developed with Python. Also, I’ve been studying a new approach. Instead of work with tags and tagging operations, the new version is powered by the semantic web vision, ideas and tools.

I’d like to highlight RDFLib, a RDF library containing an RDF triple store and RDF/XML parser/serializer which deals with the logic of the application.

Go to the Download page to get it. Check the screenshot page as well.

Development is carried out at Lauchpad.

Now that I understand how a semantic model works I have more and better ideas to implement.

Next version will be released, hopefully, before this year ends.

Enjoy it.Similar Posts:

]]> http://www.vazaar-project.org/blog/archives/214/feed 0 About Vazaar 0.4 Beta development http://www.vazaar-project.org/blog/archives/75 http://www.vazaar-project.org/blog/archives/75#comments Tue, 09 Jun 2009 16:30:08 +0000 Tomás Vírseda http://www.vazaar-project.org/blog/?p=75 After months of improving my skills with Python and PyGTK and reading documents about semantic web and its integration with Desktops Interfaces (like GNOME or KDE) a lot of improvements have been made in Vazaar. This is an overview of the current state of development.

The presentation layer, the GUI, is more difficult to develop than I’ve ever thought. Althought the concept is simple: given any kind of data, transform them into triples (subject, predicate, object) and operate with them, the time consumed to create an infrastructure around the program has been very high.

As resources can be added at any time, I had to develop a system of queues (qIn and qOut). Furthermore, I had to deal with very high responsiveness times. It’s very annoying when the GUI gets frozen because the kernel is working in other stuff. So I had to implement threads (one thread for the kernel and another thread for the GUI). Along the way, I’ve found a lot of code (see source code in Launchpad) which has helped me to carry on.

In some way, I would like to forget these kind of glitches when I’m developing a Desktop application (not a kernel module). Maybe I’ve learnt something about gtk threads but nothing interesting for this project. Never mind…

I’m still reading some documents and asking about how to create a data model around NEPOMUK. By using the semantic web paradigm things change a lot. There are no database records or tables. Instead there are thousands (or hundreds of thousands) of triples.

But it looks easiest than I thought, at the moment.

Everything is a resource (even collections). A resource has a unique identifier (UUID objects according to RFC 4122). Every resource belong to a unique Nepomuk class. They are a small subset of classes with their properties. Examples of Nepomuk classes are:

  • nfo:Feed
  • nfo:Website
  • nfo:RemoteDataObject
  • nfo:Image
  • nfo:Audio
  • nfo:Clipboard (this class doesn’t belong to NFO but I need it until I find a smart solution for copypaste operations).

As I say before, a collection is a resource. It belongs to the class Collection from PIMO namespace and use the property nie:hasLogicalPart to link resources.

Example of a single resource:

<nfo:Image rdf:about="vazaar://7971c05a-3a69-469e-875c-5ec76b0d0cfb">
    <nao:created>2009-06-09 17:34:51</nao:created>
    <nie:title>comment-icon.png</nie:title>
    <nao:lastModified>2009-06-09 17:34:51</nao:lastModified>
    <nie:mimeMedia>image</nie:mimeMedia>
    <nfo:fileUrl>/home/kaskaras/Documentos/vazaar-export-r303/data/icons/comment-icon.png</nfo:fileUrl>
    <nfo:fileBasename>comment-icon</nfo:fileBasename>
    <nfo:fileScheme>file</nfo:fileScheme>
    <nfo:fileName>comment-icon.png</nfo:fileName>
    <nfo:fileExtension>png</nfo:fileExtension>
    <nfo:fileSize>3269</nfo:fileSize>
    <nfo:belongsToContainer>/home/kaskaras/Documentos/vazaar-export-r303/data/icons</nfo:belongsToContainer>
    <nie:mimeSubtype>png</nie:mimeSubtype>
    <nie:mimeType>image/png</nie:mimeType>
</nfo:Image>

And here and example of a collection:

<pimo:Collection rdf:about="vazaar://9fcea6ca-cc79-4259-baff-6c025319a36e">
    <nao:created>2009-06-09 17:35:13.338280</nao:created>
    <nie:title>/home/kaskaras/Escritorio/screenshots</nie:title>
    <nao:lastModified>2009-06-09 17:35:13.338280</nao:lastModified>
    <nie:hasLogicalPart>
      <nfo:Image rdf:about="vazaar://15e820cb-398c-4917-b162-3b6d10cd8054">
        <nao:created>2009-06-09 17:35:13</nao:created>
        <nie:title>Pantallazo.png</nie:title>
        <nao:lastModified>2009-06-09 17:35:13</nao:lastModified>
        <nie:mimeMedia>image</nie:mimeMedia>
        <nfo:fileUrl>/home/kaskaras/Escritorio/screenshots/Pantallazo.png</nfo:fileUrl>
        <nfo:fileBasename>Pantallazo</nfo:fileBasename>
        <nfo:fileScheme>file</nfo:fileScheme>
        <nfo:fileName>Pantallazo.png</nfo:fileName>
        <nfo:fileExtension>png</nfo:fileExtension>
        <nfo:fileSize>188465</nfo:fileSize>
        <nfo:belongsToContainer>/home/kaskaras/Escritorio/screenshots</nfo:belongsToContainer>
        <nie:mimeSubtype>png</nie:mimeSubtype>
        <nie:mimeType>image/png</nie:mimeType>
      </nfo:Image>
    <nie:hasLogicalPart>
    <nie:hasLogicalPart>
    <nie:hasLogicalPart>
    <nie:hasLogicalPart>
 </pimo:Collection>

Right now, no problems working with this model. It is simple and I think that powerful. But I haven’t finished of defining the basic core of properties for a given resource (single or collection). Thinking in the future of this application, I would like to expose public resources through a SPARQL End Point so another semantic application will be able to ask it. It shouldn’t be so hard as I’ve seen a couple of python libraries to implement it. But the most important now is to have a solid model which I can work with.

Summing up, this is the result of the of the current code:

Start Here

Start Here

Make your own SPARQL queries

Make your own SPARQL queries

Basic Import support

Basic Import support

Basic Export support

Basic Export support

About Vazaar

About Vazaar

Syntax Highlighting for your sourcecode-based resources

Syntax Highlighting for your sourcecode-based resources

Basic support for image displaying

Basic support for image displaying

It’s a prototype. Don’t expect too much. In the next weeks  I’ll try to work in the GUI adding visual improvements and new funcionalities.Similar Posts:

Attached Files:

posted in News by Tomás Vírseda Leave A Comment
©2010 Vazaar Project Blog. All Rights Reserved.
]]> After months of improving my skills with Python and PyGTK and reading documents about semantic web and its integration with Desktops Interfaces (like GNOME or KDE) a lot of improvements have been made in Vazaar. This is an overview of the current state of development.

The presentation layer, the GUI, is more difficult to develop than I’ve ever thought. Althought the concept is simple: given any kind of data, transform them into triples (subject, predicate, object) and operate with them, the time consumed to create an infrastructure around the program has been very high.

As resources can be added at any time, I had to develop a system of queues (qIn and qOut). Furthermore, I had to deal with very high responsiveness times. It’s very annoying when the GUI gets frozen because the kernel is working in other stuff. So I had to implement threads (one thread for the kernel and another thread for the GUI). Along the way, I’ve found a lot of code (see source code in Launchpad) which has helped me to carry on.

In some way, I would like to forget these kind of glitches when I’m developing a Desktop application (not a kernel module). Maybe I’ve learnt something about gtk threads but nothing interesting for this project. Never mind…

I’m still reading some documents and asking about how to create a data model around NEPOMUK. By using the semantic web paradigm things change a lot. There are no database records or tables. Instead there are thousands (or hundreds of thousands) of triples.

But it looks easiest than I thought, at the moment.

Everything is a resource (even collections). A resource has a unique identifier (UUID objects according to RFC 4122). Every resource belong to a unique Nepomuk class. They are a small subset of classes with their properties. Examples of Nepomuk classes are:

  • nfo:Feed
  • nfo:Website
  • nfo:RemoteDataObject
  • nfo:Image
  • nfo:Audio
  • nfo:Clipboard (this class doesn’t belong to NFO but I need it until I find a smart solution for copypaste operations).

As I say before, a collection is a resource. It belongs to the class Collection from PIMO namespace and use the property nie:hasLogicalPart to link resources.

Example of a single resource:

<nfo:Image rdf:about="vazaar://7971c05a-3a69-469e-875c-5ec76b0d0cfb">
    <nao:created>2009-06-09 17:34:51</nao:created>
    <nie:title>comment-icon.png</nie:title>
    <nao:lastModified>2009-06-09 17:34:51</nao:lastModified>
    <nie:mimeMedia>image</nie:mimeMedia>
    <nfo:fileUrl>/home/kaskaras/Documentos/vazaar-export-r303/data/icons/comment-icon.png</nfo:fileUrl>
    <nfo:fileBasename>comment-icon</nfo:fileBasename>
    <nfo:fileScheme>file</nfo:fileScheme>
    <nfo:fileName>comment-icon.png</nfo:fileName>
    <nfo:fileExtension>png</nfo:fileExtension>
    <nfo:fileSize>3269</nfo:fileSize>
    <nfo:belongsToContainer>/home/kaskaras/Documentos/vazaar-export-r303/data/icons</nfo:belongsToContainer>
    <nie:mimeSubtype>png</nie:mimeSubtype>
    <nie:mimeType>image/png</nie:mimeType>
</nfo:Image>

And here and example of a collection:

<pimo:Collection rdf:about="vazaar://9fcea6ca-cc79-4259-baff-6c025319a36e">
    <nao:created>2009-06-09 17:35:13.338280</nao:created>
    <nie:title>/home/kaskaras/Escritorio/screenshots</nie:title>
    <nao:lastModified>2009-06-09 17:35:13.338280</nao:lastModified>
    <nie:hasLogicalPart>
      <nfo:Image rdf:about="vazaar://15e820cb-398c-4917-b162-3b6d10cd8054">
        <nao:created>2009-06-09 17:35:13</nao:created>
        <nie:title>Pantallazo.png</nie:title>
        <nao:lastModified>2009-06-09 17:35:13</nao:lastModified>
        <nie:mimeMedia>image</nie:mimeMedia>
        <nfo:fileUrl>/home/kaskaras/Escritorio/screenshots/Pantallazo.png</nfo:fileUrl>
        <nfo:fileBasename>Pantallazo</nfo:fileBasename>
        <nfo:fileScheme>file</nfo:fileScheme>
        <nfo:fileName>Pantallazo.png</nfo:fileName>
        <nfo:fileExtension>png</nfo:fileExtension>
        <nfo:fileSize>188465</nfo:fileSize>
        <nfo:belongsToContainer>/home/kaskaras/Escritorio/screenshots</nfo:belongsToContainer>
        <nie:mimeSubtype>png</nie:mimeSubtype>
        <nie:mimeType>image/png</nie:mimeType>
      </nfo:Image>
    <nie:hasLogicalPart>
    <nie:hasLogicalPart>
    <nie:hasLogicalPart>
    <nie:hasLogicalPart>
 </pimo:Collection>

Right now, no problems working with this model. It is simple and I think that powerful. But I haven’t finished of defining the basic core of properties for a given resource (single or collection). Thinking in the future of this application, I would like to expose public resources through a SPARQL End Point so another semantic application will be able to ask it. It shouldn’t be so hard as I’ve seen a couple of python libraries to implement it. But the most important now is to have a solid model which I can work with.

Summing up, this is the result of the of the current code:

Start Here

Start Here

Make your own SPARQL queries

Make your own SPARQL queries

Basic Import support

Basic Import support

Basic Export support

Basic Export support

About Vazaar

About Vazaar

Syntax Highlighting for your sourcecode-based resources

Syntax Highlighting for your sourcecode-based resources

Basic support for image displaying

Basic support for image displaying

It’s a prototype. Don’t expect too much. In the next weeks  I’ll try to work in the GUI adding visual improvements and new funcionalities.Similar Posts:

Attached Files:

]]> http://www.vazaar-project.org/blog/archives/75/feed 0 New home for Vazaar http://www.vazaar-project.org/blog/archives/57 http://www.vazaar-project.org/blog/archives/57#comments Mon, 08 Jun 2009 22:09:24 +0000 Tomás Vírseda http://www.vazaar-project.org/blog/?p=57 Nine months after my last post, I’ve got a new home for Vazaar.

It lives now at https://launchpad.net/vazaar

I want to use the infrastructure provided by Ubuntu to accelerate the development and subsequent integration into
Ubuntu or Debian repositories.

Hope it be useful for everybody.Similar Posts:

posted in News by Tomás Vírseda Leave A Comment
©2010 Vazaar Project Blog. All Rights Reserved.
]]> Nine months after my last post, I’ve got a new home for Vazaar.

It lives now at https://launchpad.net/vazaar

I want to use the infrastructure provided by Ubuntu to accelerate the development and subsequent integration into
Ubuntu or Debian repositories.

Hope it be useful for everybody.Similar Posts:

]]> http://www.vazaar-project.org/blog/archives/57/feed 0 My SVN is gone! http://www.vazaar-project.org/blog/archives/33 http://www.vazaar-project.org/blog/archives/33#comments Wed, 03 Sep 2008 17:46:19 +0000 Tomás Vírseda http://www.vazaar-project.org/blog/?p=33 I don’t know what is going on but my svn repository hosted in Dreamhost is gone  :-(

patience

Edit Saturday, September 06 2008:

Well, finally, I know what happend. My hosting company deciced to upgrade their 32bits Debian OS to 64bits and it failed. A lot. I haven’t lost anything but the svn is misconfigurated. So I’ve changed my repository to google code.

Please, update your bookmarks. You can access to the repository here:
svn checkout http://vazaar.googlecode.com/svn/trunk/ vazaar-read-only

or check this page:

http://code.google.com/p/vazaar/

Sorry about thatSimilar Posts:

posted in News by Tomás Vírseda Leave A Comment
©2010 Vazaar Project Blog. All Rights Reserved.
]]> I don’t know what is going on but my svn repository hosted in Dreamhost is gone  :-(

patience

Edit Saturday, September 06 2008:

Well, finally, I know what happend. My hosting company deciced to upgrade their 32bits Debian OS to 64bits and it failed. A lot. I haven’t lost anything but the svn is misconfigurated. So I’ve changed my repository to google code.

Please, update your bookmarks. You can access to the repository here:
svn checkout http://vazaar.googlecode.com/svn/trunk/ vazaar-read-only

or check this page:

http://code.google.com/p/vazaar/

Sorry about thatSimilar Posts:

]]> http://www.vazaar-project.org/blog/archives/33/feed 0 Revisión: 117. Estado del proyecto http://www.vazaar-project.org/blog/archives/22 http://www.vazaar-project.org/blog/archives/22#comments Thu, 14 Feb 2008 13:23:24 +0000 Tomás Vírseda http://www.vazaar-project.org/blog/archives/22 Bueno, después de casi dos meses, puedo decir que he avanzado un poco más. Para no quemarme, aburrirme o morir en el intento voy alternando entre la programación de la interfaz gráfica y el motor de la aplicación.

La parte gráfica de momento es un laboratorio. Me limito a saber leer correctamente los recursos de la base de datos semántica, interpretar lo que me duvuelven las consultas y presentarlo chapuceramente al usuario. Voy a tener que buscar o hacerme bastantes widgets a medida. De momento me he creado una nube basada en una Gtk.Table donde represento los datos y sus frecuencias. Bastante útil, por cierto.

En relación al motor de la aplicación hay tres grandes cambios:

- Para no bloquear la parte gráfica estoy implementando hilos. Deberían llamarse líos.
- He adoptado el uso de colas para todas las peticiones de trabajo.
- Vazaar dispone de un sistema de plugins.

Los hilos es una de las partes más problemáticas y la quiero eliminar en cuanto pueda. Lo natural sería tener un motor que funcione independientemente de la parte gráfica.

La solicitud de trabajos (jobs) se van enconlando y procesando por el DataProvider. Este módulo se encarga de procesar los argumentos y dedcidir de qué tipo de recurso se trata: fichero, directorio, remoto y string. Dependiendo del tipo y el numero de argumentos pasados se llama al módulo Resources donde se construyen colecciones o recursos únicos. Las colecciones albergan dos o más recursos. Uno de los problemas que me ha resuelto la cola es permitir que el usuario pueda trabajar cómodamente mientras se van añadiendo recursos. Por ejemplo, todo lo que corte o pegue quedará automáticamente almacenado como recurso. Automáticamente, el programa se encarga de identificarlo y clasificarlo.

El sistema de plugins era necesario desde un primer momento. Desde que arranca la aplicación hasta que termina hay muchos eventos que atender y muchos recursos que descubrir. Está basado en las setuptools y por medio de ‘capabilities’ el sistema se puede extender. Hasta ahora el sistema de plugins funciona para dar soporte en la extracción de metadatos al módulo Resources y para presentar unas simples estadísticas.

Hoy por hoy el interfaz va unido al motor de la aplicación lo cual no es una buena idea pero de momento no tengo los conocimientos suficientes para montar un servidor de rdf. Lo cual sería una buena idea de cara a montar un servidor público/privado de un repositorio personal o de implentar su compartición vía p2p. Lo dejo para el ToDo.

SPARQL promete como sistema de consulta pero estoy encontrándome con problemas de rendimiento. Rdflib dispone de varios backends para almecanar la información del grafo: en memoria, (des)serializado en n3, rdfxml, etc., en una bbdd SleepyCat con ficheros planos y otro para MySQL. El primero sería impensable pues se comería toda la memoria del sistema. Puedo asegurar que (des)serializando tampoco (aunque de esta manera se aprende a leer e interpretar el propio grafo). El backend de Sleepycat es el que estoy usando ahora y de momento no me está convenciendo. Me parece lento y en la medida de lo posible no pienso aceptar tiempos de respuesta mayores al segundo. Por lo tanto me queda la opción de probar MySQL.

Si quieres ver estas ideas implementadas echa un vistazo al protipo 0.4p1:

svn co http://vazaar-project.org/svn/trunk/devel/0.4p1/ vazaar

Cada día más cerca de sacar algo en claro.

Un saludoSimilar Posts:

posted in News by Tomás Vírseda Leave A Comment
©2010 Vazaar Project Blog. All Rights Reserved.
]]> Bueno, después de casi dos meses, puedo decir que he avanzado un poco más. Para no quemarme, aburrirme o morir en el intento voy alternando entre la programación de la interfaz gráfica y el motor de la aplicación.

La parte gráfica de momento es un laboratorio. Me limito a saber leer correctamente los recursos de la base de datos semántica, interpretar lo que me duvuelven las consultas y presentarlo chapuceramente al usuario. Voy a tener que buscar o hacerme bastantes widgets a medida. De momento me he creado una nube basada en una Gtk.Table donde represento los datos y sus frecuencias. Bastante útil, por cierto.

En relación al motor de la aplicación hay tres grandes cambios:

- Para no bloquear la parte gráfica estoy implementando hilos. Deberían llamarse líos.
- He adoptado el uso de colas para todas las peticiones de trabajo.
- Vazaar dispone de un sistema de plugins.

Los hilos es una de las partes más problemáticas y la quiero eliminar en cuanto pueda. Lo natural sería tener un motor que funcione independientemente de la parte gráfica.

La solicitud de trabajos (jobs) se van enconlando y procesando por el DataProvider. Este módulo se encarga de procesar los argumentos y dedcidir de qué tipo de recurso se trata: fichero, directorio, remoto y string. Dependiendo del tipo y el numero de argumentos pasados se llama al módulo Resources donde se construyen colecciones o recursos únicos. Las colecciones albergan dos o más recursos. Uno de los problemas que me ha resuelto la cola es permitir que el usuario pueda trabajar cómodamente mientras se van añadiendo recursos. Por ejemplo, todo lo que corte o pegue quedará automáticamente almacenado como recurso. Automáticamente, el programa se encarga de identificarlo y clasificarlo.

El sistema de plugins era necesario desde un primer momento. Desde que arranca la aplicación hasta que termina hay muchos eventos que atender y muchos recursos que descubrir. Está basado en las setuptools y por medio de ‘capabilities’ el sistema se puede extender. Hasta ahora el sistema de plugins funciona para dar soporte en la extracción de metadatos al módulo Resources y para presentar unas simples estadísticas.

Hoy por hoy el interfaz va unido al motor de la aplicación lo cual no es una buena idea pero de momento no tengo los conocimientos suficientes para montar un servidor de rdf. Lo cual sería una buena idea de cara a montar un servidor público/privado de un repositorio personal o de implentar su compartición vía p2p. Lo dejo para el ToDo.

SPARQL promete como sistema de consulta pero estoy encontrándome con problemas de rendimiento. Rdflib dispone de varios backends para almecanar la información del grafo: en memoria, (des)serializado en n3, rdfxml, etc., en una bbdd SleepyCat con ficheros planos y otro para MySQL. El primero sería impensable pues se comería toda la memoria del sistema. Puedo asegurar que (des)serializando tampoco (aunque de esta manera se aprende a leer e interpretar el propio grafo). El backend de Sleepycat es el que estoy usando ahora y de momento no me está convenciendo. Me parece lento y en la medida de lo posible no pienso aceptar tiempos de respuesta mayores al segundo. Por lo tanto me queda la opción de probar MySQL.

Si quieres ver estas ideas implementadas echa un vistazo al protipo 0.4p1:

svn co http://vazaar-project.org/svn/trunk/devel/0.4p1/ vazaar

Cada día más cerca de sacar algo en claro.

Un saludoSimilar Posts:

]]> http://www.vazaar-project.org/blog/archives/22/feed 0 Initial import http://www.vazaar-project.org/blog/archives/5 http://www.vazaar-project.org/blog/archives/5#comments Thu, 01 Nov 2007 21:41:56 +0000 Tomás Vírseda http://www.vazaar-project.org/blog/archives/5 Por fin me he decidido a hacer el Initial import de lo que tengo en este momento. Tan solo una prueba de concepto para aprender a manejarme con python, rdf y pygtk.

Se trata de un explorador/visor de ficheros (si se lo puede llamar así) ala web semántica. Mapea un directorio dado en un grafo y muestra los triples, metadatos encontrados* y una imagen del grafo del directorio actual.

Este módulo (al que he llamado swx) se encargará en un futuro de añadir ficheros y directorios al repositorio central así como de proveer de metadatos la base de datos de conocimiento de Vazaar.

El código:

kaskaras@laptop:~/share/wc$ svn co http://vazaar-project.org/svn/trunk/
A    trunk/devel
A    trunk/devel/swx
A    trunk/devel/swx/vazaar.glade
A    trunk/devel/swx/RdfDir.py
A    trunk/devel/swx/file.xpm
A    trunk/devel/swx/namespaces.py
A    trunk/devel/swx/swx.py
A    trunk/devel/swx/folder.xpm
A    trunk/frozen
A    trunk/play
Revisión obtenida: 1

Pantallazo:

SWX module screenshot

* letra pequeña: obtiene pocos metadatos. Falta desarrollar el módulo que se encargue de esta parte

Actualización: instala las utilidades de Redland (no he conseguido hacer funcionar bien pydot) para ver convertir RDF a DOT y poder ver la imagen del grafo.Similar Posts:

Attached Files:

posted in News by Tomás Vírseda Leave A Comment
©2010 Vazaar Project Blog. All Rights Reserved.
]]> Por fin me he decidido a hacer el Initial import de lo que tengo en este momento. Tan solo una prueba de concepto para aprender a manejarme con python, rdf y pygtk.

Se trata de un explorador/visor de ficheros (si se lo puede llamar así) ala web semántica. Mapea un directorio dado en un grafo y muestra los triples, metadatos encontrados* y una imagen del grafo del directorio actual.

Este módulo (al que he llamado swx) se encargará en un futuro de añadir ficheros y directorios al repositorio central así como de proveer de metadatos la base de datos de conocimiento de Vazaar.

El código:

kaskaras@laptop:~/share/wc$ svn co http://vazaar-project.org/svn/trunk/
A    trunk/devel
A    trunk/devel/swx
A    trunk/devel/swx/vazaar.glade
A    trunk/devel/swx/RdfDir.py
A    trunk/devel/swx/file.xpm
A    trunk/devel/swx/namespaces.py
A    trunk/devel/swx/swx.py
A    trunk/devel/swx/folder.xpm
A    trunk/frozen
A    trunk/play
Revisión obtenida: 1

Pantallazo:

SWX module screenshot

* letra pequeña: obtiene pocos metadatos. Falta desarrollar el módulo que se encargue de esta parte

Actualización: instala las utilidades de Redland (no he conseguido hacer funcionar bien pydot) para ver convertir RDF a DOT y poder ver la imagen del grafo.Similar Posts:

Attached Files:

]]> http://www.vazaar-project.org/blog/archives/5/feed 0