Vazaar Project Blog » pygtk http://www.vazaar-project.org/blog The semantic store Thu, 02 Sep 2010 02:15:14 +0000 en hourly 1 New custom timeline widget http://www.vazaar-project.org/blog/archives/558 http://www.vazaar-project.org/blog/archives/558#comments Thu, 02 Sep 2010 02:15:14 +0000 Tomás Vírseda http://www.vazaar-project.org/blog/?p=558 Tired of looking for a timeline widget in PyGTK for Vazaar I’ve decided to develop it  by myself.

It’s very simple: 1 calendar and 3 treeviews.

The user clicks a day in the calendar and with the selected date Vazaar asks to the database for those resources created that day, the day before and the day after.

Here is a screenshot:

vazaar-timeline_0

You can find an example in the repository.Similar Posts:

Attached Files:

  • Vazaar Timeline

    A timeline for vazaar showing resources for selected, previous and next day.

posted in GUI by Tomás Vírseda Leave A Comment
©2010 Vazaar Project Blog. All Rights Reserved.
]]> Tired of looking for a timeline widget in PyGTK for Vazaar I’ve decided to develop it  by myself.

It’s very simple: 1 calendar and 3 treeviews.

The user clicks a day in the calendar and with the selected date Vazaar asks to the database for those resources created that day, the day before and the day after.

Here is a screenshot:

vazaar-timeline_0

You can find an example in the repository.Similar Posts:

Attached Files:

  • Vazaar Timeline

    A timeline for vazaar showing resources for selected, previous and next day.

]]> http://www.vazaar-project.org/blog/archives/558/feed 0 PyGTK XDot Widget http://www.vazaar-project.org/blog/archives/527 http://www.vazaar-project.org/blog/archives/527#comments Thu, 19 Aug 2010 15:15:54 +0000 Tomás Vírseda http://www.vazaar-project.org/blog/?p=527 XDot es un magnífico componente para representar grafos interactivos con Python, Graphviz y GTK.

De la web del autor:

xdot.py is an interactive viewer for graphs written in Graphviz’s dot language.

It uses internally the graphviz’s xdot output format as an intermediate format, and PyGTK and Cairo for rendering.
xdot.py can be used either as a standalone application from command line, or as a library embedded in your python application.

Features

  • Since it doesn’t use bitmaps it is fast and has a small memory footprint.
  • Arbitrary zoom.
  • Keyboard/mouse navigation.
  • Supports events on the nodes with URLs.
  • Animated jumping between nodes.
  • Highlights node/edge under mouse.

Este código ilustra como usar el widget en una aplicación. En la mía, genero dinámicamente el código dot según los nodos (recursos) que haya eligido el usuario. En los adjuntos puedes encontrar otro ejemplo mezclando rdflib y xdot:

import gtk # gtk bindings
import xdot # xdot library

class FooXDot(xdot.DotWidget):
    def __init__(self, func):
        xdot.DotWidget.__init__(self)

        # Filters allowed: ‘dot’, ‘neato’, ‘twopi’, ‘circo’, ‘fdp’
        self.set_filter(‘circo’)
        self.connect(‘clicked’, func)

    def display_dot(self):
        # Header
        dc_head = """digraph Vazaar {\ncharset="UTF-8";\n"""

        # Relations
        dc_body = """"user1" -> "tennis";\n"""
        dc_body = """"user1" -> "basket";\n"""
        dc_body += """"user1" -> "soccer";\n"""
        dc_body += """"user2" -> "basket";\n"""
        dc_body += """"user2" -> "soccer";\n"""
        dc_body += """"user3" -> "tennis";\n"""
        dc_body += """"user3" -> "soccer";\n"""
        dc_body += """"user4" -> "karate";\n"""
        dc_body += """"user4" -> "soccer";\n"""
        dc_body += """"user4" -> "tennis";\n"""

        # Key Nodes
        # people
        dc_body += """"user1" [URL="%s", url="%s", label="%s", shape="box", \
                    style="filled", fillcolor="yellow"];\n""" % (‘user1′, ‘user1′, ‘John’)
        dc_body += """"user2" [URL="%s", url="%s", label="%s", shape="box", \
                    style="filled", fillcolor="yellow"];\n""" % (‘user2′, ‘user2′, ‘Steven’)
        dc_body += """"user3" [URL="%s", url="%s", label="%s", shape="box", \
                    style="filled", fillcolor="yellow"];\n""" % (‘user3′, ‘user3′, ‘Paul’)
        dc_body += """"user4" [URL="%s", url="%s", label="%s", shape="box", \
                    style="filled", fillcolor="yellow"];\n""" % (‘user4′, ‘user4′, ‘Thomas’)
        # plays
        dc_body += """"tennis" [URL="%s", url="%s", label="%s", shape="circle", \
                    style="filled", fillcolor="green"];\n""" % (‘tennis’, ‘tennis’, ‘Tennis’)
        dc_body += """"basket" [URL="%s", url="%s", label="%s", shape="circle", \
                    style="filled", fillcolor="lightblue"];\n""" % (‘basket’, ‘basket’, ‘Basket’)
        dc_body += """"soccer" [URL="%s", url="%s", label="%s", shape="circle", \
                    style="filled", fillcolor="hotpink"];\n""" % (‘soccer’, ‘soccer’, ‘Soccer’)
        dc_body += """"karate" [URL="%s", url="%s", label="%s", shape="circle", \
                s   tyle="filled", fillcolor="white"];\n""" % (‘karate’, ‘Karate’, ‘Karate’)

        # Fotter
        dc_footer = "}"

        # Join all parts
        xdot_code = dc_head + dc_body + dc_footer

        # Update widget with the new dot code
        self.set_dotcode(xdot_code)

# callback called after user clicks in a node
def on_url_clicked(widget, keynode, event):
    print ‘Key Node:’, keynode

if __name__ == ‘__main__’:
    # create widget and display dot code
    xdot = FooXDot(on_url_clicked)
    xdot.display_dot()
    xdot.show_all()

    # gtk stuff
    window = gtk.Window()
    window.resize(800, 600)
    window.connect(‘destroy’, gtk.main_quit)
    window.show_all()

    # Embed XDot widget
    window.add(xdot)

    # Get fun
    gtk.main()

Resultado:

XDot widget in action

Código fuente de otro ejemplo: xdot.zipSimilar Posts:

Attached Files:

posted in GUI by Tomás Vírseda Leave A Comment
©2010 Vazaar Project Blog. All Rights Reserved.
]]> XDot es un magnífico componente para representar grafos interactivos con Python, Graphviz y GTK.

De la web del autor:

xdot.py is an interactive viewer for graphs written in Graphviz’s dot language.

It uses internally the graphviz’s xdot output format as an intermediate format, and PyGTK and Cairo for rendering.
xdot.py can be used either as a standalone application from command line, or as a library embedded in your python application.

Features

  • Since it doesn’t use bitmaps it is fast and has a small memory footprint.
  • Arbitrary zoom.
  • Keyboard/mouse navigation.
  • Supports events on the nodes with URLs.
  • Animated jumping between nodes.
  • Highlights node/edge under mouse.

Este código ilustra como usar el widget en una aplicación. En la mía, genero dinámicamente el código dot según los nodos (recursos) que haya eligido el usuario. En los adjuntos puedes encontrar otro ejemplo mezclando rdflib y xdot:

import gtk # gtk bindings
import xdot # xdot library

class FooXDot(xdot.DotWidget):
    def __init__(self, func):
        xdot.DotWidget.__init__(self)

        # Filters allowed: ‘dot’, ‘neato’, ‘twopi’, ‘circo’, ‘fdp’
        self.set_filter(‘circo’)
        self.connect(‘clicked’, func)

    def display_dot(self):
        # Header
        dc_head = """digraph Vazaar {\ncharset="UTF-8";\n"""

        # Relations
        dc_body = """"user1" -> "tennis";\n"""
        dc_body = """"user1" -> "basket";\n"""
        dc_body += """"user1" -> "soccer";\n"""
        dc_body += """"user2" -> "basket";\n"""
        dc_body += """"user2" -> "soccer";\n"""
        dc_body += """"user3" -> "tennis";\n"""
        dc_body += """"user3" -> "soccer";\n"""
        dc_body += """"user4" -> "karate";\n"""
        dc_body += """"user4" -> "soccer";\n"""
        dc_body += """"user4" -> "tennis";\n"""

        # Key Nodes
        # people
        dc_body += """"user1" [URL="%s", url="%s", label="%s", shape="box", \
                    style="filled", fillcolor="yellow"];\n""" % (‘user1′, ‘user1′, ‘John’)
        dc_body += """"user2" [URL="%s", url="%s", label="%s", shape="box", \
                    style="filled", fillcolor="yellow"];\n""" % (‘user2′, ‘user2′, ‘Steven’)
        dc_body += """"user3" [URL="%s", url="%s", label="%s", shape="box", \
                    style="filled", fillcolor="yellow"];\n""" % (‘user3′, ‘user3′, ‘Paul’)
        dc_body += """"user4" [URL="%s", url="%s", label="%s", shape="box", \
                    style="filled", fillcolor="yellow"];\n""" % (‘user4′, ‘user4′, ‘Thomas’)
        # plays
        dc_body += """"tennis" [URL="%s", url="%s", label="%s", shape="circle", \
                    style="filled", fillcolor="green"];\n""" % (‘tennis’, ‘tennis’, ‘Tennis’)
        dc_body += """"basket" [URL="%s", url="%s", label="%s", shape="circle", \
                    style="filled", fillcolor="lightblue"];\n""" % (‘basket’, ‘basket’, ‘Basket’)
        dc_body += """"soccer" [URL="%s", url="%s", label="%s", shape="circle", \
                    style="filled", fillcolor="hotpink"];\n""" % (‘soccer’, ‘soccer’, ‘Soccer’)
        dc_body += """"karate" [URL="%s", url="%s", label="%s", shape="circle", \
                s   tyle="filled", fillcolor="white"];\n""" % (‘karate’, ‘Karate’, ‘Karate’)

        # Fotter
        dc_footer = "}"

        # Join all parts
        xdot_code = dc_head + dc_body + dc_footer

        # Update widget with the new dot code
        self.set_dotcode(xdot_code)

# callback called after user clicks in a node
def on_url_clicked(widget, keynode, event):
    print ‘Key Node:’, keynode

if __name__ == ‘__main__’:
    # create widget and display dot code
    xdot = FooXDot(on_url_clicked)
    xdot.display_dot()
    xdot.show_all()

    # gtk stuff
    window = gtk.Window()
    window.resize(800, 600)
    window.connect(‘destroy’, gtk.main_quit)
    window.show_all()

    # Embed XDot widget
    window.add(xdot)

    # Get fun
    gtk.main()

Resultado:

XDot widget in action

Código fuente de otro ejemplo: xdot.zipSimilar Posts:

Attached Files:

]]> http://www.vazaar-project.org/blog/archives/527/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 GUI improvements http://www.vazaar-project.org/blog/archives/146 http://www.vazaar-project.org/blog/archives/146#comments Sun, 02 Aug 2009 14:02:17 +0000 Tomás Vírseda http://www.vazaar-project.org/blog/?p=146 After a long weekend coding and trying new design ideas finally I think I got a nice GUI. At least for the StartHere module:

Screenshot for last development version (commit 316)

There are still too much glitches in the GUI but I’m trying to fix them as I go. But for now, I feel satisfied. Queries against the model are working as expected.

After clicking in any stats button you get a nice visual for your resources. In next commits, you will be able of choosing one the two kinds of views: ListViews and IconViews. By default, the IconView is preferred.

More ideas are coming like content filtering, properties tagcloud, timeline widget, etc…

At this moment, you can only add new resources by copy&paste operations. An improved dialog for this operation is in the way. Resources can be selected for be deleted. If the selected resource is a collection, all resources which belong to this collection will be deleted. There is no actions popup menu yet but it’s planned.

I’m thinking if a Trash resource is worth. NEPOMUK brings especial classes for this cuestion. I need check twice these. Anyway, it wouldn’t be very difficult.

One of the most important things now is to code common operation for resources: tagging, annotations, relations between them and how to display their content. For example, display text or an image is easy to do but it is not very easy to display websites content. There is not a good browser widget ready to use in PyGTK yet. I put my hope in webkit bindings for Python.Similar Posts:

Attached Files:

posted in GUI by Tomás Vírseda Leave A Comment
©2010 Vazaar Project Blog. All Rights Reserved.
]]> After a long weekend coding and trying new design ideas finally I think I got a nice GUI. At least for the StartHere module:

Screenshot for last development version (commit 316)

There are still too much glitches in the GUI but I’m trying to fix them as I go. But for now, I feel satisfied. Queries against the model are working as expected.

After clicking in any stats button you get a nice visual for your resources. In next commits, you will be able of choosing one the two kinds of views: ListViews and IconViews. By default, the IconView is preferred.

More ideas are coming like content filtering, properties tagcloud, timeline widget, etc…

At this moment, you can only add new resources by copy&paste operations. An improved dialog for this operation is in the way. Resources can be selected for be deleted. If the selected resource is a collection, all resources which belong to this collection will be deleted. There is no actions popup menu yet but it’s planned.

I’m thinking if a Trash resource is worth. NEPOMUK brings especial classes for this cuestion. I need check twice these. Anyway, it wouldn’t be very difficult.

One of the most important things now is to code common operation for resources: tagging, annotations, relations between them and how to display their content. For example, display text or an image is easy to do but it is not very easy to display websites content. There is not a good browser widget ready to use in PyGTK yet. I put my hope in webkit bindings for Python.Similar Posts:

Attached Files:

]]> http://www.vazaar-project.org/blog/archives/146/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