Gnizr 2.3.0 Milestone 3 release is now available for download and evaluation. There is no new feature implementation in this release. However, few bugs have been fixed. Other open issues are to be answered in the new year.
Hello World tutorial is now ready
As we mentioned in our previous post, through out the release of gnizr 2.3, we will develop the necessary documentations to help developers to program with gnizr -- adding new functions or altering its existing behavior.
The Hello World tutorial is the first in our series. It teaches you how to setup the necessary development environment for programming with gnizr API. The set of tools that we recommended should help you to be more productive in rapid prototyping and testing. Combining the power of Maven, Eclipse, WebWork and Spring, the tutorial showcases the implementation of a Hello World WebWork action in few lines of coding.
Get started with gnizr programming.
Wednesday, December 26, 2007
Friday, December 21, 2007
Monitor gnizr Devleopment and Say Hello World
Since the public release of gnizr 2.2.0 on Dec. 7th, 2007, within 2 weeks, we received ~4000 downloads. Thank you for everyone's interest in gnizr. Some users voiced their questions in our user group, and some others commented on our Wiki pages and submitted Issue reports.
New Mailing List
Today we created a separate mailing list for tracking issue changes and SVN commits. Subscribe to this list to receive immediate notifications when users submit new issue reports and we commit changes to SVN.
http://groups.google.com/group/gnizr-dev-tracking
New Developer Documenations
As reported in our Twitter stream, we are in the process rolling out gnizr developer documentations. Our goal is to provide information to help developers to extend gnizr by either adding new functions or altering its existing behavior.
We begin with an overview of the gnizr design and its database model. We then describe instructions on how to set up a build environment for rapid prototyping and testing -- fyi. we use the same settings in our development. Getting things started, we created a Hello World tutorial to showcase how you can take this building environment into action.
All documentations are in the editing process. We will complete the Hello World tutorial when we release gnizr 2.3.0-M3.
We are very excited about what gnizr can do for the open source community. Not only we want to make it the best open source social bookmarking and mashup application, but also we want to provide a free and open source educational tool for people to experiment with social web technologies and innovate new applications to exploit the power of Web 2.0 and the Semantic Web.
New Mailing List
Today we created a separate mailing list for tracking issue changes and SVN commits. Subscribe to this list to receive immediate notifications when users submit new issue reports and we commit changes to SVN.
http://groups.google.com/group/gnizr-dev-tracking
New Developer Documenations
As reported in our Twitter stream, we are in the process rolling out gnizr developer documentations. Our goal is to provide information to help developers to extend gnizr by either adding new functions or altering its existing behavior.
We begin with an overview of the gnizr design and its database model. We then describe instructions on how to set up a build environment for rapid prototyping and testing -- fyi. we use the same settings in our development. Getting things started, we created a Hello World tutorial to showcase how you can take this building environment into action.
All documentations are in the editing process. We will complete the Hello World tutorial when we release gnizr 2.3.0-M3.
We are very excited about what gnizr can do for the open source community. Not only we want to make it the best open source social bookmarking and mashup application, but also we want to provide a free and open source educational tool for people to experiment with social web technologies and innovate new applications to exploit the power of Web 2.0 and the Semantic Web.
Thursday, December 13, 2007
Gnizr 2.3.0 Milestone 2
Gnizr 2.3.0 Milestone 2 is now available for evaluation.
Key Changes
More Documentations, Please.
We are in the process documenting gnizr API, its design and internal implementation. We hope this will help developers who want to integrate gnizr into their enterprise systems or add new functions to gnizr.
There are many different ways to extend gnizr. We have identified at least four. Because different approaches will require different kinds of documentation -- e.g., Java API doc, architectural design discussion and programming best practice.
Currently we are documenting the design and implementation of gnizr user management and user authentication function. If you're interested in other aspects of gnizr development, please drop us an email, we will do our best to put your request on the top of our todo list.
Key Changes
- Added Ajax support to allow links in an OpenSearch result page to be bookmarked.
- OpenSearch services selected by a user will be remembered in the subsequent search requests.
- Several bug fixes
More Documentations, Please.
We are in the process documenting gnizr API, its design and internal implementation. We hope this will help developers who want to integrate gnizr into their enterprise systems or add new functions to gnizr.
There are many different ways to extend gnizr. We have identified at least four. Because different approaches will require different kinds of documentation -- e.g., Java API doc, architectural design discussion and programming best practice.
Currently we are documenting the design and implementation of gnizr user management and user authentication function. If you're interested in other aspects of gnizr development, please drop us an email, we will do our best to put your request on the top of our todo list.
Thursday, December 6, 2007
Gnizr 2.2.0 Final Release is Now Available
We are happy to announce the final release of gnizr 2.2.0.
How to install, how to use and where to ask for help.
Some Numbers
At Image Matters we have been testing gnizr on a daily basis. Our local gnizr installation is a central place for IM employees to save bookmarks and share information.
Our gnizr currently hosts:
Yes, 20K unique bookmarks. No, we are not bookmark-addicts. Not all bookmarks are created by human users. Some of which are created by gnizr robot via RSS crawling.
Some News
Last month, gnizr was used in EPA Extreme Social Networking Challenge. If you have new ways to use gnizr, let us know.
How to install, how to use and where to ask for help.
Some Numbers
At Image Matters we have been testing gnizr on a daily basis. Our local gnizr installation is a central place for IM employees to save bookmarks and share information.
Our gnizr currently hosts:
| # of Bookmarks | 20,023 |
| # of Tags | 1546 |
| # of Geo-Markers | 2267 |
| # of Tag Relations | 319 |
Yes, 20K unique bookmarks. No, we are not bookmark-addicts. Not all bookmarks are created by human users. Some of which are created by gnizr robot via RSS crawling.
Some News
Last month, gnizr was used in EPA Extreme Social Networking Challenge. If you have new ways to use gnizr, let us know.
Tuesday, December 4, 2007
Use SKOS for Search Term Suggestion
We have added a new feature in gnizr 2.3.0 that suggests search terms based on user-defined SKOS tag relation hierarchy. Search is an important feature in gnizr, which provides a means for the users to find bookmarks that are created by others in the community. To help users to find information, we must solve two problems: 1) allow users to find information beyond resources that exist within a gnizr community, 2) provide search assistance to users when navigating through a massive amount of information.
We attempt to solve the first problem by embracing OpenSearch technology, which is a powerful way to mashup search results from multiple search engines. To solve the second problem, we are experimenting a Semantic Web approach that exploits relationships between tags.
This approach works as the follows. When a gnizr web application is deployed for a specific community, the system administrator defines a domain ontology for the community in terms of tags and tag relations. In gnizr this is achieved by editing tag relations. When a user conducts search, the search system analyzes the input search term (treating it as a list of tags) and recommends new search terms (i.e., tags) that are either related-to, is narrower than or is broader than the input search term.
Here is a set of screenshots of an actual use case.
NOTE: when you're at the flickr pages, click on the "All Sizes" icon to see a high-resolution image of the screenshot.
Domain Ontology for 2008 US President Election
Let's assume that we are deploying a gnizr web application for sharing bookmarks related to the 2008 US President Election. The system administrator 'gnizr' defines a simple domain ontology in terms of tags and tag relations.
Screenshots:
Gnizr user "Harry Chen" does a search on the term 'democratic'. Using the OpenSerach interface, results from multiple search engines are mashed-up in a single page. On the top of search result, he finds a set of system suggested search terms -- i.e., terms related-to, is narrower than and is broader than 'democratic'.
Screenshots:
The described feature is still in its early stage of development. It will be available for evaluation in our next milestone release gnizr-2.3.0-M2. Let's us know what you think.
We attempt to solve the first problem by embracing OpenSearch technology, which is a powerful way to mashup search results from multiple search engines. To solve the second problem, we are experimenting a Semantic Web approach that exploits relationships between tags.
This approach works as the follows. When a gnizr web application is deployed for a specific community, the system administrator defines a domain ontology for the community in terms of tags and tag relations. In gnizr this is achieved by editing tag relations. When a user conducts search, the search system analyzes the input search term (treating it as a list of tags) and recommends new search terms (i.e., tags) that are either related-to, is narrower than or is broader than the input search term.
Here is a set of screenshots of an actual use case.
NOTE: when you're at the flickr pages, click on the "All Sizes" icon to see a high-resolution image of the screenshot.
Domain Ontology for 2008 US President Election
Let's assume that we are deploying a gnizr web application for sharing bookmarks related to the 2008 US President Election. The system administrator 'gnizr' defines a simple domain ontology in terms of tags and tag relations.
democratic
related to: republican, government, liberal
narrower: clinton, edwards
broader: politics
republican
related to: conservative, moderate
narrower: anti:clinton, pro:Giuliani, pro:Romney
clinton:
related to: anti:cliton, edwards, election
broader: person
Screenshots:
- Create/Edit tag relations
- Defining the narrower relations for tag 'democratic'
- Defining the related-to relations for tag 'democratic'
Gnizr user "Harry Chen" does a search on the term 'democratic'. Using the OpenSerach interface, results from multiple search engines are mashed-up in a single page. On the top of search result, he finds a set of system suggested search terms -- i.e., terms related-to, is narrower than and is broader than 'democratic'.
Screenshots:
- Following the suggestion, Harry finds bookmarks related to 'republican'
- Looks up other resources on the Yahoo! Web Search
- All 'republican' -- OpenSearch result mashup
The described feature is still in its early stage of development. It will be available for evaluation in our next milestone release gnizr-2.3.0-M2. Let's us know what you think.
Subscribe to:
Posts (Atom)